Difference between revisions of "Context Data Model 1.1 Open Issues"

Revision as of 17:02, 29 January 2008

Related to higgins.owl

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.

Bugs

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

General

1. Need a simple-to-follow set of pictures that explain the data model
2. Anything on this page should be logged in bugzilla
3. Tom: we need to add a lot of definition to the Higgins Data Model pages. It should say, for exmaple, that your data types MUST and SHOULD existing data types. We need to reflect these changes within the Higgins Data Model pages.
4. Tony: We don't have a simplified description of the data model
5. Mixed attribute value data types
   1. Most agree that we should not mix [Paul reversed his opinion on this (he now agrees with allowing mixed types)]
      1. Daniel points out that it would still be good to pass type on each value add:
         1. http://dev.eclipse.org/mhonarc/lists/higgins-dev/msg03816.html
         2. http://dev.eclipse.org/mhonarc/lists/higgins-dev/msg03818.html (and follow-ups)
   2. Paul asserts that we have the ability already to specify a format constraint along with a data type. For example, one could say the data type of an attribute is normalizedString, but constrained to a pattern that looks like a telephone number
6. Many same-types attributes
   1. http://dev.eclipse.org/mhonarc/lists/higgins-dev/msg03806.html
7. Allow zero-valued attributes
   1. http://dev.eclipse.org/mhonarc/lists/higgins-dev/msg03810.html
8. Closed or open simple data types
   1. http://dev.eclipse.org/mhonarc/lists/higgins-dev/msg03821.html

See Also

• Higgins Home
• Higgins Data Model