This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Datatypes R2 Issue 13"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
| − | ? backward compatible. | + | Move originalText from CD to ANY |
| + | |||
| + | There are many attributes for which a fully-encoded content won’t be available, but a free-text equivalent may be. It is also sometimes useful to capture the free text that led to a particular encoding so you know exactly what was typed/seen by the user. | ||
| + | |||
| + | ? backward compatible: Moving this element up the hierarchy will be semantically backward compatible. However, making any schema change has the potential to break implementations which use tight schema validation | ||
== Discussion == | == Discussion == | ||
| + | Move originalText from CD to ANY. Constrain it out in: ED, II, AD, EN | ||
| + | |||
| + | Alternative: Just add it to QTY? | ||
| + | |||
| + | == Disposition == | ||
| + | |||
| + | == Status == | ||
| + | |||
| + | Proposed | ||
== Links == | == Links == | ||
Back to [[Data Types R2 issues]] | Back to [[Data Types R2 issues]] | ||
Revision as of 03:46, 12 January 2007
Contents
Data Types Issue 13: Generalize originalText
Introduction
Move originalText from CD to ANY
There are many attributes for which a fully-encoded content won’t be available, but a free-text equivalent may be. It is also sometimes useful to capture the free text that led to a particular encoding so you know exactly what was typed/seen by the user.
? backward compatible: Moving this element up the hierarchy will be semantically backward compatible. However, making any schema change has the potential to break implementations which use tight schema validation
Discussion
Move originalText from CD to ANY. Constrain it out in: ED, II, AD, EN
Alternative: Just add it to QTY?
Disposition
Status
Proposed
Links
Back to Data Types R2 issues
