OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-ndrsc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: RE: [ubl-ndrsc] Bill&Eve's proposal on local/global elements


I anticipate having a lot of discussion with Tim and other members of the
LCSC about this issue. This will focus on the mapping between CCTs and the
information needed to fully document schema. In some cases, there will be a
clear mapping between the CCTs as described by ebXML and what appears in UBL
- in other areas we may need a variety of structures. This should be brought
clearly to light as we work up the next "harmonization" example.

The idea that we maintain a set of mappings that addresses this point as we
move forward is an excllent one: it may be impossible to really do Quality
Control on our library without having a clear and exact picture of these
mappings. When you recommend a set of RT-to-CCT correspondences, I think
that is closely related to these mappings.



-----Original Message-----
From: Eve L. Maler [mailto:eve.maler@sun.com]
Sent: Monday, January 28, 2002 8:50 AM
To: ubl-ndrsc@lists.oasis-open.org
Subject: Re: [ubl-ndrsc] Bill&Eve's proposal on local/global elements

The proposal (which did get adopted; Mavis will be following up with the
minutes soon) does not depend on the RTs being identical to the CCTs.  It
seems to me that there is a crude implied inheritance mechanism at work
here, with the CCT Numeric.Type being an ancestor of several of the RTs!

Since the RTs are more expressive and since the TC committed to maintaining
a clear list of the RTs UBL uses (recognizing that we may need to add some
to the syntax-specific nature of our work or for other reasons), it seems
to stick with RTs as part of our naming scheme.  The CCTs could end up being
referenced only in the dictionary documentation, and even then, if the CCTs
are less expressive, RTs work better there too.

I wonder, though, if it would be handy for us to explicitly keep track of
RT-to-CCT correspondence even after we start adding a few new RTs.


At 01:38 PM 1/26/02 -0600, Mike Rawlins wrote:
>One thing I do need to note, however, in case it did not come up in 
>There is *not* a one-to-one correspondence between CCTs and Representation 
>in the latest CC technical spec.   For example, the representation terms 
>Rate, and Value all "link" to the CCT Numeric.Type.  Date Time.Type and 
>also have such many-to-one links.  At first glance I'm not quite sure of
>impact that this has on the proposed scheme, but I have a feeling that it 
>to be considered.   If the scheme is in any way dependent on a one-to-one
>between types (XML schema type declarations and CCTs) and representation 
>it is going to have problems.
>BTW - I think this many-to-one relationship between representation terms 
>and CCTs
>is, at best, an awkward feature of the current CC spec and will so state 
>the public comment period.

Eve Maler                                    +1 781 442 3190
Sun Microsystems XML Technology Center   eve.maler @ sun.com

To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC