RE: hey whilst we are all asking for things

Kremena,

Actually, using 11179 and CCTS will standardize the construct of the data element names as well as the metadata. The key is using those two ISO standards (yes ccts is ISO 15000-5 (Draft)) in conjunction with a recognized international standards body who maintains the vocabulary. UN/CEFACT TBG is beginning to build that vocabulary, and many standards bodies - including UBL - have committed to submitting their 11179/CCTS vocabularies to help that effort. I should also mention that many agencies in the US Government, as well as other governments have already committed to using this new approach.

Mark Crawford

Senior Research Fellow

LMI Government Consulting

Vice Chair UBL

Chair CEFACT ATG XML Working Group

Dean:

I'm not a developer to comment in detail but a general remark on
dictionaries: you will be well advised to stick to standards, even
unpalatable ones. EDIFACT is widely adopted (and because this is my job -
believe me, getting a standard adopted in a national legislation is a hell
of a lot of (paper)work). So even if your "customer. account. number" is
called something unpalatable like data element X.2354 in EDIFACT, you'd
better stick to X.2354, or otherwise take into consideration that the
Government of Tonga wants it to be called "customer's. account. number",
and in Nubia it is "account.number.for.customers", etc. - and code ALL
these ever changing exceptions (which you would have to follow in the
respective languages just to be competitive) in your routines.

Kremena

The ebxml-dev list is sponsored by OASIS <http://www.oasis-open.org> The
list archives are at http://lists.ebxml.org/archives/ebxml-dev/
To subscribe or unsubscribe from this list use the subscription manager:
<http://www.oasis-open.org/mlmanage/>