OASIS Emergency Management TC

Expand all | Collapse all

RE: [emergency] HAVE Conformance vs. Documentation vs. Released Schemas

  • 1.  RE: [emergency] HAVE Conformance vs. Documentation vs. Released Schemas

    Posted 03-15-2010 17:31
    Lee,
     
    OK - lets spell this out in technical terms of schema - ignore I ever mentioned NIEM.
     
    Here's what you do.  In OASIS EDXL there is the HospitalResourcesStatus.
     
    Critically it is missing all the mission elements needed below for Haiti relief purposes.
     
    So what you do is create an extension schema - put in all those new components that you need urgently - then extend the definition of HospitalResourcesStatus to include those as additional choices.
     
    Import the extension schema into the OASIS EDXL XSD - and now you have what you need working - and you disseminate the extension schema for those systems that need to process the extended elements.
     
    You submit your extension schema to the TC as suggestion for inclusion in next release of EDXL.
     
    As a TC it is therefore beneficial to instruct people - here's how to extend our schema in a recommended way to meet emergency needs.  Please provide that as feedback to us when you do.

    Thanks, DW
     
     



  • 2.  Re: [emergency] HAVE Conformance vs. Documentation vs. Released Schemas

    Posted 03-15-2010 18:53
    David,

    What you are saying here is "fork the standard."  What you have described here is an excellent way to build an IEPD from NIEM or another previously defined IEPD. It is even a good way to model a needed change to a standard exchange.  But is is not  a good way to implement a standard. Because it is a one off that actually violates the standard schema, you have created a non-standard implementation fork if you build an actual exchange in this fashion.  If you are building a custom system to system exchange,  there is nothing wrong with this. If, however, you are building a multi-system reusable structure, this should only be the first step in establishing a potential new schema for submission to a standards process. Otherwise implementing it is customization, and not standardization. 

    R/s

    Gary

    On Mar 15, 2010, at 1:30 PM, David RR Webber (XML) wrote:

    Lee,
     
    OK - lets spell this out in technical terms of schema - ignore I ever mentioned NIEM.
     
    Here's what you do.  In OASIS EDXL there is the HospitalResourcesStatus.
     
    Critically it is missing all the mission elements needed below for Haiti relief purposes.
     
    So what you do is create an extension schema - put in all those new components that you need urgently - then extend the definition of HospitalResourcesStatus to include those as additional choices.
     
    Import the extension schema into the OASIS EDXL XSD - and now you have what you need working - and you disseminate the extension schema for those systems that need to process the extended elements.
     
    You submit your extension schema to the TC as suggestion for inclusion in next release of EDXL.
     
    As a TC it is therefore beneficial to instruct people - here's how to extend our schema in a recommended way to meet emergency needs.  Please provide that as feedback to us when you do.

    Thanks, DW