Document:
DRAFT-02-15-11-Minutes-IF-Subcommittee.doc

Draft (A preliminary unapproved sketch, outline, or version.)

Details

Submitted By Jeff Waters on 2011-03-01 1:45 pm UTC

Publication Type

None at this time.

Group / Folder

EM Infrastructure Framework SC / Resources

Modified by

Not modified.

Copy

This document is not a copy.

Technical Contact

None at this time.

Download Count

165

Download Agreement

None at this time.

Description

At today's meeting, Jeff reported that a working draft version 1 of the DE 2.0 has been posted. (See http://www.oasis-open.org/apps/org/workgroup/emergency-if/download.php/41140/EDXL-DE-v2.0-wd01.odt.) In addition to using the new OASIS template, the primary changes from the previous draft were the additions and revisions of the data dictionary tables resulting from the reorganized DE 2.0 schema. The following topics were discussed:

1. TOPIC: Should we document the common type elements in our DE 2.0 specification or reference and await for those common types to be defined in their own RIM-sponsored specification? (Answer: Reference and await the RIM-sponsored committee draft specification, because otherwise element documentation for these elements will be duplicated in multiple specs (e.g. DE and Sitreps ) and we could put the effort we would otherwise put into the documentation in the DE and put it into the RIM effort. Also the RIM only needs to move this to a committee “draft” specification, which means no public review is required.)

2. TOPIC: Should we use the word “default” to refer to our default value lists for DE 2.0 elements like DistributionType or DistributionStatus, since they are required to be inserted, i.e. we don't allow null or blank values with the assumption that the “default” value will be inserted? (Answer: We will consider this as we move forward with our next working draft.)

3. Would someone like to sign up for revising the TargetArea section of our DE 2.0 Working Draft? (Answer: Lew graciously offered to spearhead the revision of the TargetArea portion of the DE 2.0, including issues such as whether “circle” documentation should go into the OASIS SimpleFeatures Profile.)