Evan, (01)
> I have seen little discussion exploring architectures for an OOR.
> Perhaps this
> is because the requirements are still in flux. (02)
I've been negligent in not posting a list of high-level requirements I've
gleaned from what has been posted and the past three weeks presentations. (03)
Todd
========================================================================
Goals of the Open Ontology Repository
-------------------------------------
Provide an architecture and an infrastructure that supports the
a) Storing,
b) Sharing,
c) Searching,
d) Governance,
e) Management of Ontologies. (04)
Requirements, High Level - Candidate 2
-------------------------------------- (05)
Assumptions
-----------
1. Not all capabilities will be implemented at any single version.
2. The architecture will evolve. There will be multiple versions each
successor
implanting additional capabilities and/or evolving the previous version.
3. Instance data, which are themselves not ontologies, will not be stored in
the repository
4. The repository will meet the needs of operational or commercial systems.
5. Applicable standards will be used. (06)
General
-------
1. The repository architecture shall be scalable
2. The repository shall be distributed.
3. The specification of the repository shall be sufficiently detailed and
platform independent to allow multiple implementations.
4. The repository shall be capable of supporting ontologies in languages that
have reasoners.
5. The repository architecture shall support distributed repositories.
6. The repository architecture shall not require a hierarchical structure. (07)
Discovery
---------
1. The repository shall provide metadata capabilities to support
a. search capabilities,
b. governance process,
c. management (08)
2. The repository shall provide a content discovery mechanism that supports
discovery by
a) domain
b) author/creator/source
c) version
d) usage
e) language
f) terminology
g) quality (09)
Search
------
1. The repository shall provide a capability to
a. search locally
b. search globally (010)
2. The repository shall provide a capability to ‘browse’ a repository
a. locally
b. globally (011)
3. The repository shall provide a mechanism to support semantic searches. (012)
Subscription/Notification
-------------------------
1. The repository shall provide the ability for a user to subscribe to/for
alerts associated with one or more repository items.
2. The repository shall provide the ability for a user to subscribe to/for
automatic updates of one or more repository items. (013)
Management
----------
1. The repository shall provide a mechanism to enforce access policies
2. The repository shall provide a mechanism to enforce submission policies
3. The repository shall provide a mechanism to enforce governance policies
4. The repository shall provide a mechanism to enforce ‘tracking’ policies
5. The repository shall provide a mechanism to create usage reports
6. The repository shall provide syntax validation mechanisms
7. The repository shall provide a logical consistency checking mechanism
8. The repository shall provide a mechanism to automatically categorize a
submission
9.The repository shall provide a mechanism to maintain state change of
repository items (i.e. versioning)
10. The repository shall provide user and administrator access control
mechanisms (014)
Governance
---------
1. The repository shall provide explicit machine usable/accessible repository
semantics
2. The repository shall provide a mechanism to avoid intellectual property and
related legal issues/problems (015)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/oor-forum/
Subscribe: mailto:oor-forum-join@xxxxxxxxxxxxxxxx
Config/Unsubscribe: http://ontolog.cim3.net/mailman/listinfo/oor-forum/
Shared Files: http://ontolog.cim3.net/file/work/OOR/
Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository (016)
|