UBL Naming and Design Rules SC

Re: [ubl-ndrsc] Representation Terms

  • 1.  Re: [ubl-ndrsc] Representation Terms

    Posted 02-03-2004 09:23
     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] Representation Terms


    In thinking more about my previous e-mail,
    a) of course, with regard to the Amount,
    we do already have BIEs for various currencies.
    It makes we wonder whether there has been a
    reluctance to rely on those sparse supplementary
    component attributes for the CCT Amount
    and use separately declared Code BIEs for currency which
    do have all the necessary supplementary components 
    (in the CCT Schema, if not, now, in the 
    CC DT Schema).
    If my guess is right then maybe we are better off without
    the rest of the Supplementary Components in 
    Amount in order to avoid there being two ways to specify a currency.
    To do this wouldn't we need either for a restriction to
    be applied in the CC DT Schema or in the UBL DT Schema?
    *** Then we'd also need the reversal somehow of the 
    dropping of the supplementary components from the 
    CC DT (RT) Schema for Code or perhaps a way
    to use the CCT Code or to restrict the CCT (not CC
     DT) Code differently in the UBL DT Schema (including 
    the missing Supplementary Components) 
    and use that ***
    On that line (perhaps going too far - so close to final release)
    couldn't the same logic be applied to Measure
    and Quantity - to avoid the use of their CCT Supp Comps for
    UOM without the codelist mechanism:
    If the Code Supp Comps were fixed 
    we could restrict Measure and Quantity to have
    no code supplementary components
    Then we could add (the messy part?)
    Code-based BBIEs to the model to specify UOM
    Unlike Amount/Currency we'd have to do this for
    each and every Measure and Quantity (they could
    all be different) - perhaps creating an appropriate ABIE with
    Measure.Measure and UnitsOfMeasure.Code
     
    If someone says that the codelist methodology will rule
    out the need to specify codelists (not codes, obviously),
    I'm not so sure that a legal document wiould be allowed
    to have codelists which aren't specified in the document itself.
    This might, I *guess*, apply particularly to both
    currency and measure/quantity. Having Currency BBIEs is
    one thing but I'd guess they'd have in most global cases (albeit
    perhaps not including the USA
    where I've heard it is acceptable, at least in some cases,
    not to even speicfy the currency) to specify
    both currency and codelist (even if it's ISO 4217).
     
     
    Steve