Difference (from revision 15 to 16)
Changed: 27c27
::The core approach for the Open Ontology Repository is a federated architecture with the flavor of service oriented architectures. This approach provides for distributed ontology storage, repository management and service support. {nid 1GIR}
|
:The core approach for the Open Ontology Repository is a federated architecture with the flavor of service oriented architectures. This approach provides for distributed ontology storage, repository management and service support. {nid 1GIR}
|
Changed: 29c29
:: The overall assessment of the community is to enable open, distributed, federated repositories, and to provide metadata for each ontology registered, as well as providing connections for logical services, inference engines etc. {nid 1GIS}
|
: The overall assessment of the community is to enable open, distributed, federated repositories, and to provide metadata for each ontology registered, as well as providing connections for logical services, inference engines etc. {nid 1GIS}
|
Changed: 31c31
:: Those who engage in the federation may include both open and closed content. All metadata required for sharing must be open. This metadata must include the access constraints. {nid 1GIT}
|
: Those who engage in the federation may include both open and closed content. All metadata required for sharing must be open. This metadata must include the access constraints. {nid 1GIT}
|
Changed: 33c33
:: Over the repository will be a upper ontology. The upper ontology is inclusive of both the Metadata of Ontologies and a Mapping Ontology. {nid 1GP1}
|
: Over the repository will be a upper ontology. The upper ontology is inclusive of both the Metadata of Ontologies and a Mapping Ontology. {nid 1GP1}
|
Changed: 37c37
: The requirements presented are important to {nid 1GQ5}
|
: The requirements presented are important to the enablement of wide-scale knowledge re-use. {nid 1GQ5}
|
Changed: 51c51
: Here we define the required mechanisms for repository management and a set of additonal management mechanisms that are highly recommended. The understanding is that as a repository and it's infrastructure evolve, more management support mechanisms will be included. {nid 1GQ6}
|
: Repository management has both required mechanisms for effective management and additonal management mechanisms that are highly recommended. The understanding is that as a repository and it's infrastructure evolve, more management support mechanisms will be included. {nid 1GQ6}
|
Changed: 59c59
:: 6. The repository shall provide user and administrator access control mechanisms {nid 1GJO}
|
:: 6. The repository shall provide a mechanism for user and administrator access control {nid 1GJO}
|
