Draft Resource data dictionary

All,

Sorry, I know this is duplicate info, but I wanted to be sure this gets out there…

With the time constraints I am working with, I thought I might run out of time, so I developed the draft data dictionary in the attached excel format (part of which I had previously completed). Then I found a quick and easy way to copy that into the OASIS format, also attached. Both contain the same information - It may be more expedient to walk through the spreadsheet but capture changes in the document going forward. I also suggest for initial go-around we only touch on each Element, type, definition, comments, mapped rqmt and source if needed; just far enough to agree on the basis for a draft DOM. Then we can iterate back to the details.

Please note:

I added a row to the OASIS format showing mapping of each dictionary element to requirements
The OASIS template element “Usage” specifies both optionality and cardinality. I used two columns for this “Usage” and “Instances Allowed”. Because this is a reference model that will break out into several messages, usage/optionality will be more meaningful when defined for each individual message – I don’t think we should spend time during this first pass.
I did not populate “sub-elements” and “used in” because they need to wait for the DOM
Elements prefixed by “ARMS” refer to the FEMA Resource Typing effort. That structure is included in the dictionary to spark discussion whether all or part of that standard structure should be included in the standard, or handled via keyword.

Thanks,

Tim Grapes

Evolution Technologies, Inc.
Disaster Management egov Initiative

Science and Technology Directorate/OIC

Department of Homeland Security

Office: (703) 654-6075
Mobile: (703) 304-4829
tgrapes@evotecinc.com
tim.grapes@associates.dhs.gov

--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.2.5/284 - Release Date: 3/17/2006

emergency-msg message