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-ndrsc] UBL: question on CCT language component


Sorry, I've been unable to get connectivity since the f2f until now, and 
also came down with a cold after the f2f, and am also on vacation, so 
I'm just going to quickly try to respond to what's been put out here in 
order and then I'll catch any subsequent responses on Sunday when I 
return home.

To respond to your this mail, Mark:

Then why is it not prefaced by the type name ( 
Indicator.Language.Identifier and Indicator.Language.Locale.Identifier) 
as for all the other types the content and supplementary components are 
prefixed by the type name?  Also, if what you say is the case, then we 
are misusing the language sc, since we use it in two occasions in the 
cct xsd, both for token/text types (eg. code/name), not indicator types. 
 Also, it makes the most sense to me to apply language to a text/string 
or derivation thereof type, not to an indicator.  And, according to xsd, 
language is a restriction on token (higher up than ID).

This is a bit more in line with you follow up message saying it's of 
type text, but it still doens't really answer my question.  It seems 
that this is such a flat table, but there is some implied structure that 
is not evident to me.  It would be best to see this in a tree or 
indented table.  I still don't quite get what language is supposed to be 
associated with, but we only have in in the cct xsd in an inconsistent 
way, as far as I can tell.


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.

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