OASIS Emergency Management TC

 View Only

  • 1.  Emergency Management Vocabulary alignments?

    Posted 02-14-2008 14:27 
    I just found out that the NIEM V2.0 has a whole domain for Emergency Management that supports the National Incident-Based Reporting System (NIBRS).

You can use NIEM online tools to explore these:

 http://ncsconline.org/niemwayfarer  (best)

and also

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

There's a whole raft of information for emergency stuff - that we have - that is duplicative - such as vehicle, bed, etc.

I see others have already been here ahead of me.

So for example we have bed, vehicle, etc information - searching in Wayfarer shows those. 

Bed search results:

Matching Elements	
em:AdditionalCapacity24HrQuantity
em:AdditionalCapacity72HrQuantity
em:AvailableQuantity
em:BaselineQuantity
em:BedCapacity
em:BedCategoryCode
em:Capacity
em:CapacityStatusCode

Obviously we also have these in our schema.

Now of course the NIEM is a giant boat anchor of a XSD fur ball.

However - I could see the case for aligning to the dictionary - so that names/definitions are equivalent - so you have published 100% correspondence for interoperability.

This may be as simple as producing a spreadsheet with OASIS item and then the NIEM equivalent item... have we done that already?

Of course one may want to create subset schema that include only those definitions extracted from the NIEM xsd fur ball - and built as a standalone xsd that is maintained independently thru OASIS.

Is that essential what we have done?

Thoughts?

Just coming up the learning curve here!

Thanks, DW


  • 2.  RE: [emergency] Emergency Management Vocabulary alignments?

    Posted 02-14-2008 15:09 
    If I remember correctly, EDXL information was entered into NIEM sometime
back.  Some of it is incorrect, but no one was able to get it changed.

Anyone else?

Rich

Richard Vandame
Program Specialist
Standards & Technology Branch
Incident Management Systems Integration Division
DHS/FEMA
office: 202-646-7666
BB: 202-412-9072
richard.vandame@dhs.gov


    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


  • 3.  RE: [emergency] Emergency Management Vocabulary alignments?

    Posted 02-14-2008 15:42 
    Rich is correct - some EDXL messages were the first non-Justice content
entered into NIEM, before harmonization processes were defined.  At that
time, (to our surprise) the messages were broken apart and the elements put
in the EM domain as well as in core.  That's when we realized NIEM wasn't
addressing standard messages.  The content is now old and incorrect (to what
degree I don't know).

Since that time (2 years ago) there has been no governance, process or
funding to deal with this.  Though we forwarded a detailed proposal with
DHS-OIC and NIEM for EDXL alignment (EDXL consume and maintain NIEM as a
common data dictionary), I don't think it has moved forward.  That proposal
called for evolution into NIEM-compliant EDXL messaging standards through
re-use of NIEM data dictionary components, which are then evaluated as NIMS
“approved” messaging standards.  The intended result is grant language and
program alignment such that implementation of EDXL messaging standards by
any entity results in the sending and receiving system deemed as NIMS, NIEM,
OIC-program and OASIS compatible.  

Thanks,

Tim Grapes
Evolution Technologies, Inc.
Office:  (703) 654-6075
Mobile:  (703) 304-4829
tgrapes@evotecinc.com
http://www.evotecinc.com/


    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


  • 4.  RE: [emergency] Emergency Management Vocabulary alignments?

    Posted 02-14-2008 15:51 
    Thanks Tim for the explanation.  I am attaching the "released for 
public consumption."  Slide that describes the development 
process.  I am very hopeful that with all of the parties at the table 
at the EIC meeting next Wed, maybe some progress can be made as to 
how this needs to go forward.  Elysa
PS - didn't "attach" the slide since it is quite a large pdf.  I'll 
post it in the references document folder on the TC site.

At 09:41 AM 2/14/2008, Timothy Grapes wrote:
>Rich is correct - some EDXL messages were the first non-Justice content
>entered into NIEM, before harmonization processes were defined.  At that
>time, (to our surprise) the messages were broken apart and the elements put
>in the EM domain as well as in core.  That's when we realized NIEM wasn't
>addressing standard messages.  The content is now old and incorrect (to what
>degree I don't know).
>
>Since that time (2 years ago) there has been no governance, process or
>funding to deal with this.  Though we forwarded a detailed proposal with
>DHS-OIC and NIEM for EDXL alignment (EDXL consume and maintain NIEM as a
>common data dictionary), I don't think it has moved forward.  That proposal
>called for evolution into NIEM-compliant EDXL messaging standards through
>re-use of NIEM data dictionary components, which are then evaluated as NIMS
>"approved" messaging standards.  The intended result is grant language and
>program alignment such that implementation of EDXL messaging standards by
>any entity results in the sending and receiving system deemed as NIMS, NIEM,
>OIC-program and OASIS compatible.
>
>Thanks,
>
>Tim Grapes
>Evolution Technologies, Inc.
>Office:  (703) 654-6075
>Mobile:  (703) 304-4829
>tgrapes@evotecinc.com
>http://www.evotecinc.com/
>
>
    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


Related Content