Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

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 7: Line 7:
 
==Related to higgins.owl's relationship to the IdAS API==
 
==Related to higgins.owl's relationship to the IdAS API==
 
# <none>
 
# <none>
 +
==See Also==
 +
* [[IdAS Data Model]]

Revision as of 11:00, 19 October 2006

Related to higgins.owl

  1. 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.
  2. 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?
  3. The 'source' metadata property is currently a SubjectRelationship (that points to a Digital Subject that is usually in some other Context). But there are times when we know more; when we know the source Attribute held by the "source" Digital Subject. Maybe we need 'sourceSubject' and 'sourceSubjectAttriubte'?
  4. We've not resolved how to declare user-defined Classes to be 'closed', that is instances of them should follow the class definition, but not include any other "extra" properties.

Related to higgins.owl's relationship to the IdAS API

  1. <none>

See Also

Back to the top