Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Context Data Model 1.1 Open Issues"
(→Related to Higgins.owl) |
(→Related to higgins.owl's relationship to the IdAS API) |
||
Line 5: | Line 5: | ||
==Related to higgins.owl's relationship to the IdAS API== | ==Related to higgins.owl's relationship to the IdAS API== | ||
− | # | + | # <none> |
Revision as of 11:55, 28 September 2006
Related to Higgins.owl
- Higgins.owl: we need to add the full set of DatatypeAttribute subclasses that correspond to the XML Schema types. We currently have only StringDatatypeAttribute, Base64BinaryDatatypeAttribute, NormalizedStringDatatypeAttribute but need to add all the rest.
- At present, other than having an Attribute subclass for each of the std OWL (XML Schema-based) literal datatypes, we have defined no ObjectAttribute subclasses. The question is should we go a bit further and define some very common complex types such as postalAddress? or even tricky singled-stringed values such as zipcode?
- We need to develop an example of an ontology that is based on higgins.owl but that emphasises how to model relationships between Digital Subjects
Related to higgins.owl's relationship to the IdAS API
- <none>