This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Data Types R3 issues"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
* Collapse Abstract and ISO 21090 into a single specification partitioned according to SAIF (Grahame) | * Collapse Abstract and ISO 21090 into a single specification partitioned according to SAIF (Grahame) | ||
* Turn II.scope into a mandatory attribute [[User:Rene spronk|Rene spronk]] | * Turn II.scope into a mandatory attribute [[User:Rene spronk|Rene spronk]] | ||
| − | ** In MnM we discussed this and there are issues about making something mandatory that may be populated unsafely | + | ** In MnM we discussed this and there are issues about making something mandatory that may be populated unsafely (Lloyd) |
| − | * Add 'conformance' into datatype properties | + | * Add 'conformance' into datatype properties (Lloyd) |
| − | * Introduce idea of "implementation" or "closed community" constraints on datatypes | + | * Introduce idea of "implementation" or "closed community" constraints on datatypes (Lloyd) (but initiated by Grahame) |
Revision as of 08:45, 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)
- Introduce idea of "implementation" or "closed community" constraints on datatypes (Lloyd) (but initiated by Grahame)
