[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
Innovative Emergency Management, Inc.
Managing Risk in a Complex World
8555 United Plaza Blvd. Suite 100
From: Mark Carlson -
Conneva, Inc. [mailto:email@example.com]
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.
IEM CONFIDENTIAL INFORMATION PLEASE READ OUR NOTICE: