WebOnt Candidate Core Requirements

Last modified: 12/13/01

The following list contains the requirements under consideration. For each requirement a short definition is provided. Some requirements also include additional issues.

R1. Shared ontologies
Ontologies are publicly available and different data sources can commit to the same ontology for shared meaning.
R2. Ontology extension
Ontologies can be extended by other ontologies in order to provide additional definitions.
R3. Ontology evolution
Ontologies can be changed over time and data sources can specify which version of the ontology they commit to.
R4. Ontology interoperability
Different ontologies may model the same concepts in different ways. The language should provide primitives for relating different representations, thus allowing data to be converted to different ontologies, and enabling a "web of ontologies."
R5. Inconsistency
Different ontologies may be contradictory, or different data sources may be contradictory. It should be possible to detect inconsistencies.
R6. Scalability
The language should be able to be used with large ontologies and large data sets.
R7. Ease of Use
The language should provide a low-learning barrier and have clear concepts and meaning. The concepts should be independent from syntax.
R8. Data persistence
The Web is constantly changing, so it would be useful to know the lifetime of information. This will be useful for agents to know when they must refresh their knowledge bases.
R9. Security
Ability to specify who can view and modify information. Have ontologies that can specify access control information.
R10. XML syntax
The language should have an XML serialization.
R11. Internationalization
The language should support ontologies in multiple languages.
R12. Ontology-based search
Ability to locate information using the ontology to structure queries? Or is this something else?
R13. Ontology querying
Ability to ask questions about the logical structure of the ontology? Or is this something else?
R14. Expressiveness
What can be expressed in the language and what reasoning capabilities should be expected in systems that fully implement it.
R15. Proof checking
Proofs can be described in the language and will be checkable.
R16. Trust
How to determine which information is reliable and/or believable. Must be able to know the sources of information and to express what supporting information is needed to believe something.
R17. Tagging
It is sometimes useful to attach additional information to a piece of data. For example, the source of the data, a time stamp, or a confidence level. Tagging is the ability associate such information.