UBL Naming and Design Rules SC

RE: [ubl-ndrsc] Bill&Eve's proposal on local/global elements

  • 1.  RE: [ubl-ndrsc] Bill&Eve's proposal on local/global elements

    Posted 01-31-2002 13:29
     MHonArc v2.5.2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    ubl-ndrsc message

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


    Subject: RE: [ubl-ndrsc] Bill&Eve's proposal on local/global elements


    Title: RE: [ubl-ndrsc] Bill&Eve's proposal on local/global elements
    Mark:
     
    If you look at the CCTs, you will see things like "Identifier".
     
    Take xCBL NameAddress as an example. We have two child elements that are "identifiers". One is a simple string type, called "external address identifier." The other is a more typical identifier that is used to supply a coded, official identifer for the addresee - a DUNS number, for example, using fields to specify code lists, etc.
     
    This may not even be the best example, but what it points out is this: we have a choice between making everything be represented by a single XSD structure, designed to agree ith our list of CCTs, in which case we get bloated structures with lots of unneccessary optional elements, and a consequent lack of ability to automatically validate, or we have more than one structure for certain of the CCTs.
     
    This is what I was trying to say with the phrase "variety of structures." Still nothing that couldn't be handled with a mapping table, however.
     
    Cheers,
     
    Arofan