This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Datatypes R2 Issue 11"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
Just derive from SC instead of ST | Just derive from SC instead of ST | ||
| + | |||
| + | Grahame is having second thoughts, Charlie McKay seemed to agree. And I certainly do to. I don't think there is a real use case for this. It's just complicated fluff. | ||
== Resolution == | == Resolution == | ||
Revision as of 16:15, 27 May 2007
Contents
Data Types Issue 11: Derive ADXP and ENXP from SC
Introduction
Address and Name parts should allow codes. Countries, states, delivery types, name prefixes and name suffixes may all have associated codes
? backward compatible.This element will be semantically backward compatible. However, making any schema change has the potential to break implementations which use tight schema validation
PM, PA
Discussion
Just derive from SC instead of ST
Grahame is having second thoughts, Charlie McKay seemed to agree. And I certainly do to. I don't think there is a real use case for this. It's just complicated fluff.
Resolution
Passed in INM 30/4/2007: Motion to Derive ADXP and ENXP from SC instead of ST
Links
Back to Data Types R2 issues
