This wiki has undergone a migration to Confluence found Here
Datatypes R2 Issue 74
Revision as of 23:48, 10 January 2007 by GrahameGrieve (talk | contribs)
Data Types Issue 54: 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.
Links
Back to Data Types R2 issues
