OpenOntologyRepository (OOR) Initiative - Use Cases (189A)
This page defines use cases for OOR. (1892)
Use Cases which OOR will support (189B)
Ontology User (1HXZ)
Name: Find Ontology (1HY0)
Goal: Finding an ontology to meet pre-defined needs. Summary: Describes how a user of ontologies may find one to meet their needs. Actors: Ontology User Preconditions: A registry of ontologies Triggers: Need for an ontology Basic Course: A user of ontologies has developed requirements for an ontology and wishes to determine if an ontology exists that meets a majority of their requirements. They logon to an ontology repository and start searching. 0) The user logs on to an OOR instance. 1) The user navigates to a/the search page. 2) The user selects the most relevant search fields (e.g. domain, subject, creator, etc.) from parameter list provided. 3) The user enters their search criteria. 3) The search returns a list of possible candidate matches. Alternative Courses: The local OOR returns no results and promts the user to select federated OOR instances to search. Post Conditions: (1HY1)
Name: Browse a single Ontology (1HY2)
Goal: Browse a single ontology of the users choice. Summary: Describes how an interested party/user would find a ontology and view it. Actors: OOR User Preconditions: A instance of an OOR accessible to the user. Triggers: User is interested in locating an ontology and inspecting it to ascertain its 'goodness'. Basic Course: 0) The user logs on to an OOR instance. 1) The user navigates to a/the search page. 2) The user enter their search criteria (e.g. domain, subject, selected terms). 3) The search returns a list of possible candidate matches. 4) The user browses through the list and finds a possible candidate and selects it for further detailed inspection. 5) The OOR starts another browser tab with the selected ontology displayed for the user to view. Alternative Courses: a) The search of the local OOR returns no results. b) The search of federated OOR instances returns no results. Post Conditions: The user finds an ontology and downloads it. (1IWY)
Name: Add Comment for an Uncontrolled Review (1HY3)
Goal: Allow a user to comment or review an OOR ontology in an uncontrolled fashion. Summary: Describes how an interested party/user would would add an uncontrolled review of an OOR ontology. Actors: User Preconditions: A instance of an OOR accessible to the user. An OOR ontology whose identity is known to the user. Triggers: User is interested in add their review of an existing OOR ontology. Basic Course: 0) The user logs on to an OOR instance. 1) The user navigates to a/the search page. 2) The user enter the identity/identifier of the ontology upon which they wish to add a comment. 3) The search returns the identified ontologies page. 4) The user browses on the ontologies' page to the comment section. 5) The user adds their comments. 6) The user hits the 'Save' button. 7) The comments are added to the list of comments for the identified ontology and associated with the user's logon identity. Alternative Courses: The identified ontology no longer resides on the OOR instance. b) The identified ontology does not permit uncontrolled comments. Post Conditions: (1IWZ)
Name: Review an OOR Ontology (1IX0)
Name: Add Change Request (1HY4)
Ontology Designer (1HY5)
Name: Upload Ontology (1HY6)
Name: Update Ontology (1HY7)
Name: Create Mapping among existing ontologies (1HY8)
Name: Download Ontology (1HY9)
Name: Correct Ontology Errors (1HYA)
Ontology Agent (1IKZ)
- ... (189C)
Potential Use Cases (189D)
- use cases for MMI ontology repository (Google doc, currently under development). (1JG6)
- Woundontology (1KD6)
Input & Comments (1KD7)
- User Access Modes: Could describe various modes of accessing 1. a single local repository with one or more ontologies, 2. a single distributed and geospatially dispersed repository containing single or multiple repositories, 3. multiple distributed repositories owned by different owner organizations, 4. federated users from federated repositories. Some of these have been covered by FarrukhNajmi and RaviSharma and yet there is a need to make visual use cases for the same which are being considered by Community And also by RaviSharma. (1IRH)
- Repository access and functionality uses cases: In the categories above, the Browse capability and upload and update categories are already listed. Other modes could include for example 1. Browse only the Metadata about ontology, 2. Browse the Types of Ontology by any of selected metadata such as language, topic, domain or 3. By specific semantically meaningful "joins" or "Shared Concepts" for multiple ontologies 4. Use of external Ontology engines, search and inference engines and 5. External Tools from specific vendors or industry standard compliant solutions. 6. Developmental and production orientation for run time (say triples and SPARQL) considerations depicted as use cases, etc. RaviSharma. (1IRJ)
- Comment from RaviSharma: from OMV Report 2.4 http://ontoware.org/frs/?group_id=39&release_id=404 we get an idea of the predefined ontologies and we need to analyze if our usecases are in congruence or are there any additional types. 5.2.1 Pre-defined ontology types (1J4A)
Individuals of the class OntologyType refer to well-known classifications for ontologies in the literature. Currently the OMV model resorts to a classification on the generality levels of the conceptualization [5, 16]: • upper level ontologies describing general, domain-independent concepts e.g. space, time. • core ontologies describing the most important concepts in a specific domain • domain ontology describing some domain of the world • task ontology describing generic types of tasks or activities e.g. selling, selecting. • application ontology describing some domain in an application-dependent manner The class can be extended to support additional classifications (e.g. the one in [9]). (1KD9)
References & Related Links (1895)
- (1J3S)
- Access to ebXML reference. This Reference requires OASIS membership as this is probably still a work in process and not yet a published standard? Comment from RaviSharma (1J3T)