OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: FW: Suggestion: Add incidentKeyword to contentObject

Forwarding message from Mark Carlson…


Patti Iles Aymond, PhD
Senior Scientist
Bioterrorism Preparedness & Response

Innovative Emergency Management, Inc.

Managing Risk in a Complex World

8555 United Plaza Blvd.   Suite 100
Baton Rouge, LA 70809
(225) 952-8228 (phone)
(225) 952-8122 (fax)

From: Mark Carlson - Conneva, Inc. [mailto:conneva@gmail.com]
Sent: Thursday, January 26, 2006 11:37 AM
To: Aymond, Patti
Subject: Fwd: Suggestion: Add incidentKeyword to contentObject




I tried sending this message to the group, but the list server rejected my message.  Could you forward, please?



=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- =-=-=-=-=-=-=-=-


I'm quite sure everyone is hoping for no more changes to the EDXL-DE schema at this point.  However, as I have begun to work with the schema in our resourcing prototype, I have observed that while there are incidentID and incidentDescription elements in the contentObject, there is no provision to classify the incident using a valueListURN/value pair. 


This would seem to be necessary for consistency.  In other words, if it is a good idea to have an incidentDescription and incidentID in the contentObject, there should also be an optional incidentKeyword to classify the incident.




Mark Carlson



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]