Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
INST2006 SEMANTIC WEB
Transcript of INST2006 SEMANTIC WEB
3 SUPER CLASSES
OUR ONTOLOGY DIAGRAM
What is an ontology?
Concept adapted for computer science from a wider field of philosophy
Often described as
‘a formal specification of a shared conceptualization’
A description of concepts and relationships between those concepts as seen in a particular field.
Ontologies are used for
systematization of information
, using a shared, regulated vocabulary.
, such as class hierarchy or restrictions, which further
Department of Management Science & Innovation
University College London
Modeling department's structure.
Focusing on degrees and modules offered.
Focusing on people that are part of MS&I.
Languages used: RDF, RDFS and OWL
3 main classes:
Person, Module, Degree
Participants of MS&I Department.
Modules provided by the department to its students.
Degrees available within MS&I Department.
Something to note here is the intersection class Teaching Assistant between Teaching Staff and PhD Student, since many PhD students at UCL happen to teach some of the seminars classes for the MSIN department. But since not all PhD students are teaching assistants and not all teaching assistants are PhD students we found the need to create this intersection to make the logical distinction.
Each Person, regardless of whether Student or Staff, has 3 datatype properties – “name” (as String), “ID” (as Integer) and “emailAddress” (as String). Each person can have only 1 value for “name”, 1 value for “ID”, but can have 1 or more values for “emailAddress”.
Undergraduate Student also has a datatype property of its own (besides name, ID and emailAddress) – “yearOfStudy” to identify the year of each undergraduate (recorded as an Integer). Each Undergraduate Student has only 1 value for “yearOfStudy”.
Each Student is linked to only a single Degree via the “undertakes” property. Each Student is linked to the Module via the “takes” property.
Each Undergraduate Student “takes” exactly 8 modules.
Student also has "isOverseenBy" property linked to the Staff sub-class of Person to identify the members of staff (1 or more) that have relationships with them, such a mentor.
Teaching Staff has a “teaches” property linked to Module, in order to record which modules they have taught.
Each Postgraduate Student can take 1 or many modules.
Student also has "isTaughtBy" property linked to the TeachingStaff sub-class of Staff, which links 1 or more lecturers to each of the student’s records.
The Person class is disjoint with Module and Degree classes.
Degree has 4 sub-classes:
BSc Degree, MSci Degree, MSc Degree and PhD Degree, all of which inherit all characteristics of Degree (degreeName and ucasCode).
Degree has 2 datatype properties that identify its name (“degreeName” as String) and UCAS code (“ucasCode”, as String).
Each degree has exactly one name and one UCAS code assigned to it.
Degree is disjoint with both Student and Module classes.
Module has no sub-classes of its own but has a set of properties that identify:
module code (“moduleCode”, restricted to String),
prerequisites (“prerequisites”, restricted to String),
the term in which the module can be taken (“termTaken”, restricted to Integer),
whether or not it is a postgraduate or undergraduate specific course (“level”, restricted to String)
the number of students enrolled on the module (“numberStudentsEnrolled”, restricted to Integer).
Module class also has the functional property “isPartOf” linking it to the Degree superclass, in order to record which Degrees this Module is specific to. Module could be part of 1 degree only.
The Module class is disjoint with Person and Degree classes.
Each module has exactly 1 value for “level”, 1 value for “moduleCode”, 1 value for “numberStudentsEnrolled” and 1 value for “prerequisites”.
Each module has a maximum of two attributes for "termTaken", depending if it can be taken in only one or both terms.
* One can be at the same time a member of both Teaching Staff and Administrative Staff
* One can be at the same time a member of any subclasses of Administrative Staff
* One can not be a member of more than 1 subclass of Teaching Staff
* One can be at the same time a member of both Staff and Student (for example, Teaching Assistant)
Tailored to the courses within the
Allows users to see all
in the university, and the related
Applied extensively for
With minor adaptations, our ontology can also be applied to
Application will be
undergraduates (BSc and BSci)
postgraduates (MSc, MSci, PhD)
Allows users to
for people within university by their
name and ID
Provide users the ability to see information about their
take or teach
Restrictions represent the structure of the department.
Students in the same year of a Degree programme are taking the same modules.
Students from other degrees are not able to choose them as their elective.
Moreover, the same Module can’t be compulsory for more than one Degree.
Possibility to create a more extensive library for the whole university.
The classes and relationships introduced can be used as a library, useful to describe similar modelling problems
Flexible framework that supports re-usability.
Declarative specification of a software system.
The use of our ontology in software engineering could be helpful for the creation of a specific system.