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 3: | Line 3: | ||
== Introduction == | == Introduction == | ||
| + | Address and Name parts should allow codes. Countries, states, delivery types, name prefixes and name suffixes may all have associated codes | ||
| − | ? backward compatible. | + | ? 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 == | == Discussion == | ||
| + | Just derive from SC instead of ST | ||
| + | |||
| + | == Disposition == | ||
| + | |||
| + | == Status == | ||
| + | |||
| + | Proposed | ||
== Links == | == Links == | ||
Back to [[Data Types R2 issues]] | Back to [[Data Types R2 issues]] | ||
Revision as of 03:43, 12 January 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
Disposition
Status
Proposed
Links
Back to Data Types R2 issues
