OASIS Emergency Management TC

  • 1.  RE: [emergency] EDXL HAVE and NIEM 2.1 dictionary =?UTF-8?Q?alignment=3F?=

    Posted 07-12-2009 20:12
    Lee,

    IMHO - that makes zero sense!  Band-aiding like that is nasty...

    Obviously best outcome is to put the HAVE pieces in NIEM 2.1

    Failing that - having an extended dictionary that includes the new HAVE pieces - so we can generate two wantlists.xml automatically.  One that works with the SSGT - and one that works locally - and will include the missing pieces as extensions.xsd into the subset schema.

    What we need poste haste though is the exact list of missing parts.  I have the cross-reference dictionary between EDXL HAVE and current NIEM 2.0 - that should work as pick list of things that need to be added.
     
    Thanks, DW




  • 2.  RE: [emergency] EDXL HAVE and NIEM 2.1 dictionary alignment?

    Posted 07-13-2009 00:38
    
    
    
    
    
    
    
    
    
    
    

    Uhmmm – isn’t that exactly what I just said we are doing?

    Thanks,

    Lee

     

    "I was wondering why that Frisbee was getting bigger - then it hit me."

    From: David RR Webber (XML) [mailto:david@drrw.info]
    Sent: Sunday, July 12, 2009 4:12 PM
    To: Lee Tincher
    Cc: emergency@lists.oasis-open.org
    Subject: RE: [emergency] EDXL HAVE and NIEM 2.1 dictionary alignment?

    Lee,

    IMHO - that makes zero sense!  Band-aiding like that is nasty...

    Obviously best outcome is to put the HAVE pieces in NIEM 2.1

    Failing that - having an extended dictionary that includes the new HAVE pieces - so we can generate two wantlists.xml automatically.  One that works with the SSGT - and one that works locally - and will include the missing pieces as extensions.xsd into the subset schema.

    What we need poste haste though is the exact list of missing parts.  I have the cross-reference dictionary between EDXL HAVE and current NIEM 2.0 - that should work as pick list of things that need to be added.

     

    Thanks, DW


    They are not – we have added in HAVE entities to the em domain and we also created an “adapter” to point to the actual OASIS standard.  This si being done so we can create a mirror IEPD of HAVE that has a one-to-one match…the idea is to create an XSLT that translates between the HAVE IEPD and the “real” standard that can be carried in the digest of a SOAP message….  

     

    Thanks,

    Lee

     

    "I was wondering why that Frisbee was getting bigger - then it hit me."

     

    From: David RR Webber (XML) [mailto:david@drrw.info]
    Sent: Sunday, July 12, 2009 12:46 AM
    To: emergency@lists.oasis-open.org
    Subject: [emergency] EDXL HAVE and NIEM 2.1 dictionary alignment?
    Importance: High

     

    Team,

     

    I've finally managed to crack the wantlist.xml processing against the online GTRI SSGT and NIEM 2.0 dictionary working for the HospitalStatus schema and using CAM compare to dictionary tool to reverse engineer the wantlist from the schema.

     

    http://niem.gtri.gatech.edu/niemtools/ssgt/SSGT-Generate.iepd#

     

    I've attached the sample wantlist.xml if you want to try this yourselves (click on the "Options" - far top right -  and then you will see a select file and load buttons).

     

    Now - when reviewing this - you will notice a raft of gml elements are missing (only a short list are there) - PLUS - there are many missing em: items.

     

    So the key questions is - are these all missing ones now added into the new NIEM 2.1 dictionary release that is scheduled for September?

     

    If not someone needs to contact GTRI very quickly this week - to make sure these will be added.

     

    And if we could get a beta test of the Access database of the new NIEM 2.1 then would be best so we can crosscheck it all.

     

    Thanks, DW



  • 3.  RE: [emergency] EDXL HAVE and NIEM 2.1 dictionary alignment?

    Posted 07-13-2009 00:42
    
    
    
    
    
    
    
    
    
    
    

    I am really confused by your response – I clearly state below that we are putting in the HAVE entities in NIEM – a corresponding IEPD is a natural progression – it will match HAVE but have a NIEM namespace – thus the adapter…I really think you should stop and try to understand before slinging arrows – I believe in good discussion – but I tend to try to be professional and civil…to a point.

    Thanks,

    Lee

     

    "I was wondering why that Frisbee was getting bigger - then it hit me."

    From: David RR Webber (XML) [mailto:david@drrw.info]
    Sent: Sunday, July 12, 2009 4:12 PM
    To: Lee Tincher
    Cc: emergency@lists.oasis-open.org
    Subject: RE: [emergency] EDXL HAVE and NIEM 2.1 dictionary alignment?

    Lee,

    IMHO - that makes zero sense!  Band-aiding like that is nasty...

    Obviously best outcome is to put the HAVE pieces in NIEM 2.1

    Failing that - having an extended dictionary that includes the new HAVE pieces - so we can generate two wantlists.xml automatically.  One that works with the SSGT - and one that works locally - and will include the missing pieces as extensions.xsd into the subset schema.

    What we need poste haste though is the exact list of missing parts.  I have the cross-reference dictionary between EDXL HAVE and current NIEM 2.0 - that should work as pick list of things that need to be added.

     

    Thanks, DW


    They are not – we have added in HAVE entities to the em domain and we also created an “adapter” to point to the actual OASIS standard.  This si being done so we can create a mirror IEPD of HAVE that has a one-to-one match…the idea is to create an XSLT that translates between the HAVE IEPD and the “real” standard that can be carried in the digest of a SOAP message….  

     

    Thanks,

    Lee

     

    "I was wondering why that Frisbee was getting bigger - then it hit me."

     

    From: David RR Webber (XML) [mailto:david@drrw.info]
    Sent: Sunday, July 12, 2009 12:46 AM
    To: emergency@lists.oasis-open.org
    Subject: [emergency] EDXL HAVE and NIEM 2.1 dictionary alignment?
    Importance: High

     

    Team,

     

    I've finally managed to crack the wantlist.xml processing against the online GTRI SSGT and NIEM 2.0 dictionary working for the HospitalStatus schema and using CAM compare to dictionary tool to reverse engineer the wantlist from the schema.

     

    http://niem.gtri.gatech.edu/niemtools/ssgt/SSGT-Generate.iepd#

     

    I've attached the sample wantlist.xml if you want to try this yourselves (click on the "Options" - far top right -  and then you will see a select file and load buttons).

     

    Now - when reviewing this - you will notice a raft of gml elements are missing (only a short list are there) - PLUS - there are many missing em: items.

     

    So the key questions is - are these all missing ones now added into the new NIEM 2.1 dictionary release that is scheduled for September?

     

    If not someone needs to contact GTRI very quickly this week - to make sure these will be added.

     

    And if we could get a beta test of the Access database of the new NIEM 2.1 then would be best so we can crosscheck it all.

     

    Thanks, DW