This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Datatypes R2 Issue 55"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
== Introduction == | == Introduction == | ||
| + | |||
| + | Update mode and audit trail are documented '''where??''' | ||
| + | |||
| + | The XML ITS needs to describe how these can be represented in instances. | ||
| Line 8: | Line 12: | ||
== Discussion == | == Discussion == | ||
| + | '''Grahame''': the schema generator already adds these: | ||
| + | * an XML attribute called "updateMode" to attributes with the update mode flag set on them in the design. | ||
| + | * the XML attributes xxx to attributes with the audit trail flag set on them in the design. | ||
| + | We need to update the MNM documentation to clearly establish that these flags cannot be set on structural attributes. | ||
== Links == | == Links == | ||
Back to [[Data Types R2 issues]] | Back to [[Data Types R2 issues]] | ||
Revision as of 23:09, 16 May 2006
Data Types Issue 55: Update mode & Audit Trail
Introduction
Update mode and audit trail are documented where??
The XML ITS needs to describe how these can be represented in instances.
? backward compatible.
Discussion
Grahame: the schema generator already adds these:
- an XML attribute called "updateMode" to attributes with the update mode flag set on them in the design.
- the XML attributes xxx to attributes with the audit trail flag set on them in the design.
We need to update the MNM documentation to clearly establish that these flags cannot be set on structural attributes.
Links
Back to Data Types R2 issues
