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's relationship to the IdAS API)
(→‎Related to higgins.owl)
Line 1: Line 1:
 
==Related to higgins.owl==
 
==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.
+
# 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 'sourceSubjectAttribute'?
−
# 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?
+
===Require moving to OWL-Full===
−
# 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'?
+
# Ability 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.
−
# 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.
+
# Ability to use user-defined XML Schema types in Attribute values (at present we are restricted to the base XML Schema data types)
 +
===Bugs===
 +
# Need to document that uniqueIdentifiers are immutable
 +
# Max cardinality of lastVerifiedFromSource and lastVerifyAttempt should be 1 not N
  
 
==Related to higgins.owl's relationship to the IdAS API==
 
==Related to higgins.owl's relationship to the IdAS API==

Revision as of 13:20, 1 January 2007

Related to higgins.owl

  1. 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 'sourceSubjectAttribute'?

Require moving to OWL-Full

  1. Ability 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.
  2. Ability to use user-defined XML Schema types in Attribute values (at present we are restricted to the base XML Schema data types)

Bugs

  1. Need to document that uniqueIdentifiers are immutable
  2. Max cardinality of lastVerifiedFromSource and lastVerifyAttempt should be 1 not N

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

  1. <none>

See Also

Retrieved from "https://wiki.eclipse.org/index.php?title=Context_Data_Model_1.1_Open_Issues&oldid=21702"

Back to the top