UBL Naming and Design Rules SC

 View Only

RE: [ubl-ndrsc] NDR Checklist Clarification

  • 1.  RE: [ubl-ndrsc] NDR Checklist Clarification

    Posted 09-22-2003 03:50
     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] NDR Checklist Clarification


    Not much problem with the *intended* structure.  It appears
    that the two-level model might make accessing schema structures
    simpler, by allowing certain (2-level) assumptions on the structures
    to be made in programs and dependency checks.   But the downside
    may be in bloated bottom level, or a difficulty to create new
    2nd level modules to be linked into the top-level especially 
    in cases when the 2 levels are separately managed (e.g. top-level 
    being external agency and 2nd-level being user organisation).
    
    But R90's wordings as it is says, and prohibits, *more* than the 
    intended 2-level structure.  If it takes more words, then it'll
    have to be to express what Mark has clarified, what Tony has
    elaborated, and what Bill has confirmed.
    
    
    
    Best Regards,
    Chin Chee-Kai
    SoftML
    Tel: +65-6820-2979
    Fax: +65-6743-7875
    Email: cheekai@SoftML.Net
    http://SoftML.Net/
    
    
    On Sun, 21 Sep 2003, Burcham, Bill wrote:
    
    >>That's right Tony.  It's a two-level model.  Include is used at the first
    >>level (where needed) to compose the constituents of a namespace.  Import is
    >>used to reference foreign namespaces.  See chapter 11 of the Modularity,
    >>Namespace, and Versioning position paper, "Recommendation: Module Structure"
    >>for the details
    >>http://www.oasis-open.org/committees/download.php/1384/draft-burcham-modnamv
    >>er-08.zip
    >>
    >>