UBL Naming and Design Rules SC

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

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

    Posted 03-04-2004 16:38
     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] UBL: question on CCT language component


    Hi,
    
    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.
    
    -Anne
    
    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"
    >
    >
    >