OASIS Universal Business Language (UBL) TC

CLSC analysis of code list rules in NDR document

  • 1.  CLSC analysis of code list rules in NDR document

    Posted 04-14-2004 18:27
     MHonArc v2.5.0b2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    ubl message

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


    Subject: CLSC analysis of code list rules in NDR document


    We've just completed our CLSC weekly meeting and we've analyzed the code 
    list rules in the 20040414 NDR document cited here:
    
       http://lists.oasis-open.org/archives/ubl-clsc/200404/msg00008.html
    
    Re: CDLXXX: The xsd:schemaLocation MUST include the complete URI used to 
    identify the relevant code list schema.
    
       - we think this is not a specific code-list issue and that this issue
         is a global UBL issue and is being addressed by packaging
       - we observe that complete *relative* URI string values are used for
         xsd:schemaLocation and not complete *absolute* URI string values
    
    We observed that there is no "CDL4" rule and wondered if anything fell 
    through the cracks.
    
    Eagle-eyed Marty has discovered in the schema fragments that not all UBL 
    information items whose values should be coming from code lists are in fact 
    coming from code lists.  This is not a code list committee responsibility 
    (we think it is a Library Content issue) but we wondered aloud if there 
    ever was an NDR rule that stated "All information items whose values are 
    coded must come from code lists".
    
    Just one example that Marty quickly found is in 
    UBL-UnspecialisedDatatypes-1.0.xsd where the first element declared is 
    AmountType.  The attribute amountCurrencyID is declared for this element 
    but that attribute's type is not derived from CurrencyCodeContentType found 
    in UBL-CodeList-CurrencyCode-1.0.xsd ... we thought that it should be but 
    not being part of Library Content we were not sure if there was a conscious 
    decision not to do so.
    
    Are there other constructs that would need to be fixed?
    
    But, back to the original premise ... we believe as a committee that CLSC 
    is covering in our document the NDR rules related to code lists.
    
    ............... Ken
    
    --
    Public courses: Spring 2004 world tour of hands-on XSL instruction
    Each week:   Monday-Wednesday: XSLT/XPath; Thursday-Friday: XSL-FO
    Hong Kong May 17-21; Bremen Germany May 24-28; Helsinki June 14-18
    
    World-wide on-site corporate, govt. & user group XML/XSL training.
    G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
    Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/o/
    Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
    Male Breast Cancer Awareness  http://www.CraneSoftwrights.com/o/bc
    
    


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