Case Study: National Student Registry
Description: The central management of students’ profiles (at the Ministry of Higher Education in Palestine) is becoming an urgent need in the last years. Many students in Palestine move from one university to another, and they need to transfer their academic records. Also, the ministry of needs to certify the diplomas and mark sheets of students. Moreover, there is a need to centrally manage/monitor students financial aids. Therefore, the ministry decided to build a National Student Registry, such that, each semester every university has to send the academic record of every student to the ministry of education. The ministry will then update and integrate the academic records according to the data combined from all universities into the national student registry. The ministry wants to specify a shared ontology in OWL; such that all universities can exchange their students profiles in RDF format and the data can be automatically validated and integrated after that. You need to build this ontology in OWL.
You are advised to start brainstorming on a paper to specify what a student record contains
(student, university, faculty, program, course, semester, marks, averages, and
the relationships between such concepts, as well as the business rules). You are required to use three different mark sheets from different universities, so to ensure that the resultant ontology cover the relevant exchanged information needed for this national registry. You are advised to first develop a conceptual model using ORM for this national registry, formalize the ORM schema in description logic, then translate the ORM schema into OWL. Furthermore, you are required to deliver two RDF files, each file representing the data in a mark sheet. These RDF files must commit/use the vocabulary defined the RDFs model. You are expected to re-use standard and common ontologies such as FOAF, DOAC, etc. and you should validate you OWL and RDF files using the online W3C RDF
validator.
Deliverable: A webpage describing the project and its components and how they should be used. The webpage should include the following sections:
Cover page:
Section 1 Project description: the above text might be used, but should be extended.
Cover page:
Section 1 Project description: the above text might be used, but should be extended.
Section 2 Academic Record Ontology:
Section 2.1 Representing the ontology in ORM: please describe the main concepts and the main rules and constraints - not only giving the ORM diagram.
Section 2.1 Representing the ontology in ORM: please describe the main concepts and the main rules and constraints - not only giving the ORM diagram.
Section 2.2: Representing the ontology in ORM: this section is 5 lines only -to describe why we need the ontology in OWL (and why ORM alone is not enough). the OWL code itself will be provided in Appendix 1.
Section 3 Validation and Reasoning:
Section 3.2 specifying the ontology in Description logic: this section is to provide ontology is description logic.
Section 3.1 Validation of and reasoning on the ontology: This section is to prove that the ontology is valid. First, explain what does mean that the ontology is satisfiable and how this can be checked using one of DL reasoner (e.g. Hermit or Racer), and provide a screenshot to prove that it is satisfiable. Then, change the ontology to make unsatisfiable - e.g., adding certain disjointness and/or cardinality constraints, and provide screenshots to show that this change made the ontology unsatisfiable.
Section 4: How to use the ontology- Two RDF cases: This section is 8 to 15 lines to explain how the ontology can be used; such that two RDF files to specify two separate marksheets - witten in terms of the OWL ontology. The two RDF files will be provided in Appendix 2. Is its advised to also put these two markseets as images.
Appendix 1 Ontology in OWL: this section constians the code in OWL. the OWL code should be validated using the standard RDF validator. a clickable icon should be provided such that when one clicks it shows the ontology validated using the RDF validator.
Appendix 1 RDF files: this section constians the RDF of the two cases. the RDF code should be validated using the standard RDF validator. a clickable icon should be provided such that when one clicks it shows the RDF validated using the RDF validator.
Section 3 Validation and Reasoning:
Section 3.2 specifying the ontology in Description logic: this section is to provide ontology is description logic.
Section 3.1 Validation of and reasoning on the ontology: This section is to prove that the ontology is valid. First, explain what does mean that the ontology is satisfiable and how this can be checked using one of DL reasoner (e.g. Hermit or Racer), and provide a screenshot to prove that it is satisfiable. Then, change the ontology to make unsatisfiable - e.g., adding certain disjointness and/or cardinality constraints, and provide screenshots to show that this change made the ontology unsatisfiable.
Section 4: How to use the ontology- Two RDF cases: This section is 8 to 15 lines to explain how the ontology can be used; such that two RDF files to specify two separate marksheets - witten in terms of the OWL ontology. The two RDF files will be provided in Appendix 2. Is its advised to also put these two markseets as images.
Appendix 1 Ontology in OWL: this section constians the code in OWL. the OWL code should be validated using the standard RDF validator. a clickable icon should be provided such that when one clicks it shows the ontology validated using the RDF validator.
Appendix 1 RDF files: this section constians the RDF of the two cases. the RDF code should be validated using the standard RDF validator. a clickable icon should be provided such that when one clicks it shows the RDF validated using the RDF validator.
Student who successfully finish this project will be able to:
- Represent and publish data in RDF
- Develop and share domain vocabulary in OWL
- Reuse existing vocabulary developed by others
- Use ORM to model OWL at the conceptual level
- Formalize the ontology (OWL and ORM) in Description Logic, and reason about this ontology using DL reasoners.
- Use semantic web technology in data integration scenarios (in egovernment case study)
Remark: This project does not show to model a good ontology (as this 'ontology' is really a schema), modeling good ontologies will be the subject of other lectures and projects.
Students' Projects in 2012:
No comments:
Post a Comment