UBL Naming and Design Rules SC

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

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

    Posted 03-04-2004 16:55
     MHonArc v2.5.0b2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    ubl-ndrsc message

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


    Subject: Re: [ubl-ndrsc] Re: [ubl-lcsc] Re: [ubl-ndrsc] UBL: question on CCTlanguage component


    Table 8-2 shows both, one right after the other,  both type string.  I 
    thinkone problem with 8-2 is that it seems to have been alphabetized, as 
    opposed to being ordered by the structures it's defining!
    
    Ah, to me, though, looking at this table (8-2), following your logic, I 
    would expect there then to be language.content, and then maybe 
    language.code. identifier, as there is for amount.content and 
    amount.currency.identifier.   However, my logic expects more along the 
    lines of (eg) code.name.text and code.name.language, or datetime.content 
    and datetime.language.  So one of the first questions for me is 'What 
    types need to have language specified' and then, what components need to 
    have a language specified, and then make lanagues a supp component of 
    that type.  All the other types are grouped, as if they could be in a 
    structure, but language is just hanging out there on it's own.  I'll 
    have to look at this a bit more, but I don't see why language should be 
    separated out as you have it in this example - I'd think it would have 
    to be x.language...., or y.language. ..., not language.x....  because 
    the language has to apply to some aspect of some type, either the name 
    of the a components (text) or a format (date).  But perhaps I'm looking 
    at things the wrong way around...
    
    -Anne
    
    Tim McGrath wrote:
    
    > 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"
    >>
    >>
    >>