Datatypes R2 Issue 13
Data Types Issue 13: Generalize originalText
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
Move originalText from CD to ANY. Constrain it out in: ED, II, AD, EN
Alternative: Just add it to QTY?
Back to Data Types R2 issues