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: Describe 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. Alternative Courses: Post Conditions: (1HY1)
Name: Browse Ontology (1HY2)
Name: Add Comment/Uncontrolled Review (1HY3)
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)
- (1IRG)
- 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 respositories 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)
- (1IRI)
- 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 baout ontology, 2. Browse the Types of Ontology by any of selected metadata such as laanguage, topic, domain or 3. By specific semantically meaningful "joins" or "Shared Concepts" for multiple ontologies 4. Use of external Ontology engines, serach 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)
... (189E)