OASIS ebXML Messaging Services TC

RE: [ebxml-msg] Issue 56: Specification / Schema conflict resolution

  • 1.  RE: [ebxml-msg] Issue 56: Specification / Schema conflict resolution

    Posted 02-18-2002 13:53
    Dale,
    
    There are a few intertwined issues being discussed:
    
    1. Dispute Resolution
       We need a process to resolve disputes, whether it's spec/schema
       related or an interpretation issue or other.
    2. Method for communicating/issuing corrections
       (spec, schema and interpretations)
    3. Distribution of the "normative" schema.
    
    
    Regarding 1:
    
    During spec development I believe it's the TC's responsibility to resolve
    disputes using the standard consensus process. IMO, the TC should
    investigate issues and provide a resolution.
    
    AFTER a spec is released another process (hopefully one is defined by
    OASIS), is used to resolve issues with the spec and other related documents.
    Does OASIS already have such a process (Ian)? I suspect they do.
    
    Regarding 2:
    
    I'm assuming that OASIS standard processes dictate how specs and other
    related documents are distributed, including errata. We should consult the
    OASIS process for this.
    
    Regarding 3:
    
    I suspect people will cache schemas locally (I know I am) and individuals
    should be responsible for updating these schemas, after receiving
    notification of corrections via the process used in 2.
    
    Dick Brooks
    Systrends, Inc
    7855 South River Parkway, Suite 111
    Tempe, Arizona 85284
    Web: www.systrends.com <http://www.systrends.com>
    Phone:480.756.6777,Mobile:205-790-1542,eFax:240-352-0714