UBL Naming and Design Rules SC

 View Only

RE: [ubl-ndrsc] [Fwd: Fwd: ISO 3166-1 -- Change of Alpha-3 CodeElement for Romania]

  • 1.  RE: [ubl-ndrsc] [Fwd: Fwd: ISO 3166-1 -- Change of Alpha-3 CodeElement for Romania]

    Posted 02-13-2002 07:36
     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] [Fwd: Fwd: ISO 3166-1 -- Change of Alpha-3 CodeElement for Romania]


    Title: RE: [ubl-ndrsc] [Fwd: Fwd: ISO 3166-1 -- Change of Alpha-3 Code Element for Romania]

    IMHO we are loosing sight of a very distinct difference between human readability/semantic clarity of tags and human readability/semantic clarity of data (codes).   It's not our data that we want human readable! There is no way that we can ensure or control semantic clarity of data, nor should we entertain any thoughts of trying to do so. 

    A tremendous amount of work has gone into establishing code lists to provide tokens for data values that are clear, unambiguous, and easily mapped to any language specific value of the code.  Avoiding using those code lists for data values and trying to establish English language equivalents just makes no sense, is counterproductive, and does not justify the small processing time savings for transformations from code to language equivalents. 



    Mark


    >