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-04-2004 16:45
     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


    In relation to the ccts xsd and those related xsds, I am simply trying 
    to identify the cct primitive types and our associated data types for 
    the supplementary components that weren't originally specified in those 
    files since we are unrestricting (and therefore now including) more of 
    those components than what we had in there going into the f2f.
    
    In those files up to the f2f were almost all token, a restriction on 
    normalizedString.  If  you expected it to be normalizeString, then, yes, 
    perhaps this was confused during the token vs. string discussions.  So 
    this maybe should be revisited?
    
    -Anne
    
    Stephen Green wrote:
    
    >Anne
    >
    >I'm worried that in all this we might inadvertently drop the LC/NDR
    >resolution to use xsd:normalizedString wherever there is the possibility
    >that more than one space need be preserved (having business meaning).
    >
    >I think it was decided for Identifier but there was less certainty about
    >using it for Code.
    >
    >*I note that most Supp Comps are identifiers.*
    >Perhaps this got neglected as changes were made to the Schemas and
    >then the omissions reinforced as we discussed xsd:token versus xsd:string.
    >
    >Steve
    >
    >