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] | [List Home]

Subject: RE: [ubl-lcsc] Re: [ubl-ndrsc] UBL: question on CCT language component

thats what I get for replying in a hurry - I looked at table 8-2 instead of table 8-1.  Language. Identifer is of type Code. Type.  Language. Locale. Identifer is of type Text. Type.  Sorry for the wrong anser earlier.


From: Tim McGrath [mailto:tmcgrath@portcomm.com.au]
Sent: Sun 2/29/2004 7:02 AM
Cc: anne.hendry@sun.com; ubl-lcsc@lists.oasis-open.org; ubl-ndrsc@lists.oasis-open.org
Subject: Re: [ubl-lcsc] Re: [ubl-ndrsc] UBL: question on CCT language component

I cannot find where it says they are indicator. Content???  di you mean Identifier. Content?

In the data model i derived fro the tables in 8-1 and 8-2, you will see that both Language.Identifier and Language.Locale.Identifier are Identifiers and therefore have an Identifer. Content (ie xsd:token).

This conundrum exposes the 'flat' structures we have built for CCTs and Rep. Terms , when they should have been more sophisticated.  That is, we should have had things like...


where the schema reflects the true structures of the CCTs and not the table

CRAWFORD, Mark wrote:

>Language supplementary components are of indicator. Content.
>Mark Crawford
>Research Fellow - LMI XML Lead
>W3C Advisory Committee, OASIS, RosettaNet Representative
>Vice Chair - OASIS UBL TC & Chair Naming and Design Rules Subcommittee
>Chair - UN/CEFACT XML Syntax Working Group
>Editor - UN/CEFACT Core Components
>Logistics Management Institute
>2000 Corporate Ridge, McLean, VA 22102-7805
>(703) 917-7177   Fax (703) 917-7481
>Wireless (703) 655-4810
>"Opportunity is what you make of it"
>-----Original Message-----
>From: Anne Hendry <anne.hendry@sun.com>
>To: ubl-lcsc@lists.oasis-open.org <ubl-lcsc@lists.oasis-open.org>; ubl-ndrsc@lists.oasis-open.org <ubl-ndrsc@lists.oasis-open.org>
>Sent: Sat Feb 28 01:16:14 2004
>Subject: [ubl-ndrsc] UBL: question on CCT language component
>   Hi,
>In matching up the UBL xsd datatype assignments to cct types, I could
>use some clarification on the 'language*' components.  All other
>components listed in table 8-2 of ccts 2.01 have a 'content' component
>and then some supplementary components.  However, language* components
>seem to be all supplementary, with no content component - they just
>appear as 'Language.Identifier' and 'Language.Locale.Identifier'.  So,
>then, going through the xsd representation of the Code type in table
>8-2, for example, I have all the attributes (supplementary components)
>of Code type accounted for, but there is one extra in the schema that is
>not in the cct 8-2 table.  That is 'languageID'.  Here is the xsd for
>the 'Code' element:
>- <xsd:simpleContent>
>- <xsd:extension base="xsd:token">
>  <xsd:attribute name="listID" type="xsd:token" use="optional" />
>  <xsd:attribute name="listAgencyID" type="xsd:token" use="optional" />
>  <xsd:attribute name="listAgencyName" type="xsd:token" use="optional" />
>  <xsd:attribute name="listName" type="xsd:token" use="optional" />
>  <xsd:attribute name="listVersionID" type="xsd:token" use="optional" />
>  <xsd:attribute name="name" type="xsd:token" use="optional" />
>  <xsd:attribute name="languageID" type="xsd:language" use="optional" />
>  <xsd:attribute name="listURI" type="xsd:anyURI" use="optional" />
>  <xsd:attribute name="listSchemeURI" type="xsd:anyURI" use="optional" />
>  </xsd:extension>
>  </xsd:simpleContent>
>The definition of the 'Language.Identifier' component in the ccts 8-2
>table defines it as "The indentifier of the language used in the
>corresponding text string."  Well, ok, there is a 'text' string (name)
>in the schema right above this that corresponds to the ccts entry in 8-2
>'Code.Name.Text'.  However, there are other 'text' strings (eg. in
>BinaryObject Name, etc) in 8-2 tha t don't seem to have a 'languageID'
>attribute attached.
>So my questions are:
>a) Why does Language.Identifier not have a content component?  It seems
>like somewhat of a free-floating supplementary component the way it is now.
>b) When/how do we choose to use the Language.Identifier?
>c) Along with Language.Identifier in table 8-2 there is
>'Language.Locale.Identifier', also a seemingly free-floating
>supplementary component.  Is it expected that wherever there is a
>Language.Identifier attribute needed/used there should also be a
>I am only looking at the cct schema. I'm assuming the rep terms schema
>is going away.  Is this a correct assumption and I should only look at
>cct?  What about the cc parameters schema - will that be auto-generated
>(or will that one be removed too)??
>An ne
>To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/ubl-ndrsc/members/leave_workgroup.php.
>To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/ubl-lcsc/members/leave_workgroup.php.

tim mcgrath
phone: +618 93352228 
postal: po box 1289   fremantle    western australia 6160

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