Difference between revisions of "Data Types R3 issues"

Revision as of 08:48, 13 January 2011

This is the register of known data types issues for release 3.

Please do not add entries to this list if your name is Lloyd. thanks

For now, just enter the change proposal as a single point in the list, with your name

Collapse Abstract and ISO 21090 into a single specification partitioned according to SAIF (Grahame)
Turn II.scope into a mandatory attribute Rene spronk
- In MnM we discussed this and there are issues about making something mandatory that may be populated unsafely (Lloyd)
Add 'conformance' into datatype properties (Lloyd)
- introducing idea of "conformance" (required, optional, not permitted) into the datatype properties. E.g. "You are conformant if you ignore displayName, but not if you ignore code"
Introduce idea of "implementation" or "closed community" constraints on datatypes (Lloyd) (but initiated by Grahame)
- implementers to be able to do things like constrain out the root when it's known. I.e. "non-worst case interoperability".

@@ Line 9: / Line 9: @@
 ** In MnM we discussed this and there are issues about making something mandatory that may be populated unsafely (Lloyd)
 * Add 'conformance' into datatype properties (Lloyd)
+**  introducing idea of "conformance" (required, optional, not permitted) into the datatype properties. E.g. "You are conformant if you ignore displayName, but not if you ignore code"
 * Introduce idea of "implementation" or "closed community" constraints on datatypes (Lloyd) (but initiated by Grahame)
+**  implementers to be able to do things like constrain out the root when it's known.  I.e. "non-worst case interoperability".