Document:
DRAFT-05-24-11-Minutes-IF-Subcommittee-1-1.doc

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

Details

Submitted By Jeff Waters on 2011-06-07 10:58 am 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

213

Download Agreement

None at this time.

Description

This document contains the minutes of the May 24th, 2011 meeting of the Infrastructure Framework Subcommittee. At this meeting, following topics were discussed:


1. TOPIC: Do we have a diagram for our new DE 2.0? (Answer: Yes, a diagram has been generated and uploaded. Also a cheatsheet has been uploaded describing the elements, simple types, cardinality, and default values. A few issues were raised in regard to these.)

2. TOPIC: What is the current approach for appropriately constraining SimpleFeatures for our profile purposes? (Answer: The latest concept is to leverage work already accomplished which has a constrained schema and schematron rules of GML. This will be discussed at the TC call. Although this adds some complexity to learn the schematron, it is a well-used technology among developers, it is consistent with the GML/ISO approach to new profile development, and the existing work allows the schematron rules to be applied to a shorter, simpler version of GML than the SimpleFeatures which reduces the complexity.)

3. TOPIC: Should we use ValueLists for describing areas, rather than just target and source areas? (Answer: We’ll decide next time. Werner suggested treating areas as being a choice between either using own values from own ValueListURI or using your default values. This would treat areas the same way we are treating DistributionStatus and DistributionType. But Rex had concerns about whether this detail was appropriate for the routing uses and whether this adds unneeded complexity.)

4. TOPIC: Should we rename the “DistributionType” element to avoid awkwardness of naming an element the way we name types? (Answer: Yes. Proposed name is “DistributionKind”. Other option is “DistributionCategory”. We’ll decide for sure next time.)