Difference between revisions of "Datatypes R2 Issue 74"
| Line 14: | Line 14: | ||
Approved (Motion Grahame/Stan) | Approved (Motion Grahame/Stan) | ||
| + | |||
| + | The above is the R1 resolution, for R2 we need to revisit this and come up with a better solution, hopefully one that doesn't introduce new null flavors specific to certain data types. | ||
== Links == | == Links == | ||
Back to [[Data Types R2 issues]] | Back to [[Data Types R2 issues]] | ||
Revision as of 09:35, 30 April 2007
Data Types Issue 74: UNC NullFlavor
Introduction
Some users/developers/implementors are unable or too lazy to encode a CD properly. Other users would like to know so that they can be caught out later. So it would be nice to add a nullFlavor code to suggest that a receiver might well invest in recoding the concept.
Discussion
Disposition: For the moment, add a NullFlavor UNC. When CD & nullFlavor are re-organised to resolve the NullFlavor issues associated with OTH, this nullFlavor will probably be refactored in favor of a different approach to meet the same requirement.
Approved (Motion Grahame/Stan)
The above is the R1 resolution, for R2 we need to revisit this and come up with a better solution, hopefully one that doesn't introduce new null flavors specific to certain data types.
Links
Back to Data Types R2 issues
