OASIS Universal Business Language (UBL) TC

 View Only

Metadata for code lists in schemas

  • 1.  Metadata for code lists in schemas

    Posted 07-14-2006 02:15
     MHonArc v2.5.0b2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    ubl message

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


    Subject: Metadata for code lists in schemas


    Hi folks,
    
    I'm looking at the files created by GEFEG:
    
      http://www.oasis-open.org/committees/document.php?document_id=19139
    
    I note the following metadata for the code lists 
    (using ContainerSize as an example only because 
    it was this one that was invalidly produced that 
    brought this problem to my attention):
    
          <xsd:attribute name="listURI" type="xsd:anyURI"
                         fixed="../codelist/gc/ContainerSizeTypeCodeType.gc"
                         use="optional">
    
    The attribute is optional, but if it is specified 
    it has to be a fixed value, and the value specified is a *relative* URI.
    
    I think this is incorrect.  The code list 
    genericode files are not considered part of the 
    schemas so when someone installs their schemas 
    these files will not be around, and anyway I'm 
    guessing a relative URI would be relative to the 
    instance which also would not have the genericode files around.
    
    I think relative URI values are inappropriate for 
    *identifying* URIs ... yet we don't have absolute 
    URIs for our genericode files to use here.
    
    Does this value have to have a fixed value?
    
    Can we leave the attribute merely as optional and without a fixed value?
    
    And, on further inspection, I now note there are 
    fixed= values all over for code lists, yet the 
    code list value validation methodology needs 
    these to all be optional so that we have nothing 
    hardwired in the schemas regarding code 
    lists.  It is up to trading partners to specify 
    the metadata of the lists they choose to use.
    
    So ... may I remove the fixed= attributes from *all* code list metadata?
    
    If so, then I can change my massaging stylesheets 
    to remove the fixed= on all code list meta data declarations.
    
    We can then check the NDRs related to code lists 
    and make sure future builds come out this way.
    
    Please advise.
    
    Thanks!
    
    . . . . . . . . Ken
    
    --
    Registration open for UBL training:    Montr�al, Canada 2006-08-07
    Also for XSL-FO/XSLT training:    Minneapolis, MN 2006-07-31/08-04
    Also for UBL/XML/XSLT/XSL-FO training: Varo,Denmark 06-09-25/10-06
    World-wide corporate, govt. & user group UBL, XSL, & XML 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 Cancer Awareness Aug'05  http://www.CraneSoftwrights.com/o/bc
    Legal business disclaimers:  http://www.CraneSoftwrights.com/legal
    
    


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