ubl-ndrsc — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
RE: [ubl-lcsc] [code lists] drafct of section to put in documentation - for comment
MHonArc v2.5.0b2 -->ubl-ndrsc message
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ubl-lcsc] [code lists] drafct of section to put in documentation - for comment
- From: "Stuhec, Gunther" <[email protected]>
- To: "'Tim McGrath'" <[email protected]>, "CRAWFORD, Mark" <[email protected]>
- Date: Wed, 29 Oct 2003 15:30:32 +0100
Title: Message
Hello
Tim,
the
CCTS describes clearly, how we can define code lists in general (internal and
external). We, in UBL have the possibility (better we have the golden
opportunity) to put this definition into unambigous XML based naming and design
rules. There are accepted rules from NDRSC for defining code list schemas, which
are 100% conform to the CCTS.
This
rules allows everyone to define his own codelist uniquely and everyone can use
this codelists in their UBL-schemas without any modifications and restrictions.
The
members in the UN/CEFACT ATG2 are willingness to using the same rules for
defining code lists schema. If that accepted, than the most of the other groups
will use this rules. Why shouldn't we go this direction,
too?
Kind
regards,
Gunther
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]