UBL Naming and Design Rules SC

 View Only

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

  • 1.  Re: [ubl-lcsc] Re: [ubl-ndrsc] UBL: question on CCT language component

    Posted 03-09-2004 02:20
     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] Re: [ubl-ndrsc] UBL: question on CCT language component


    Actually, Language. Identifier shows up in *two* places in table 8-1, in 
    Code and in Text, but it only shows up once in table 8-2.  After having 
    spent the last couple of days pouring over this, I'm thinking that the 
    occurance of language in the Code row of table 8-1 is a mistake.  I 
    believe it should be, as it is in table 8-1, Text type, which is also 
    the only place the Language. Locale. Identifier is available.  But not 
    in both Text and Code.  It is the only component that shows up twice, 
    and it is without a preceding type name.  All the others have preceding 
    type names (which should, in this case, I believe, be Text 
    (Text.Language.Identifier).
    
    -A
    
    CRAWFORD, Mark wrote:
    
    >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
    >To: CRAWFORD, Mark
    >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...
    >
    ><Language>
    ><Identifier>
    ><Content>
    >EN
    ></Content>
    ></Identifier>
    ><LocaleIdentifier>
    ><Content>
    >US
    ></Content>
    ></LocaleIdentifier>
    ></Language>
    >
    >where the schema reflects the true structures of the CCTs and not the table
    >
    >
    >CRAWFORD, Mark wrote:
    >
    >  
    >
    >>Anne,
    >>
    >>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
    >>mcrawford@lmi.org
    >>http://www.lmi.org
    >>"Opportunity is what you make of it"
    >>
    >>
    >>