Description
Since the group has completed its review of edits for the DE 2.0 issues list, and has a draft schema (including reorganization to make components independently reusable, gml-compliant targetArea, xlink for linking content objects, more ValueListURI usage for flexibility) , it's time to review our remaining tasking and get a sense of level of effort and schedule.
1. TOPIC: What are the next steps in our DE 2.0 process? (Answer: (1) Pour the current content into the official template and finish editing; (2) test the proposed schema for practicability with common parsers and for addressing individual use cases and provide feedback, and (3) revisit especially meaningful use cases. The challenge is that members of the committee are busy and it's hard to find the time and support for the testing; yet, the individual member feedback is important. )
2. TOPIC: What is the status of the SimpleFeatures specification supporting TargetArea? (Answer: A SimpleFeatures specification may be available, but it is being modified to support “circle” and a few other items. )
3. TOPIC: What are some of the most compelling use cases demonstrating the significance of using the DE 2.0? (Answer: Everyone should consider this question as we move forward to adoption. One use case of significance is the use of the DE ValueListURI to link to externally managed ontologies to enable “smart” routing. Doing the collection and documentation of the terms used in the field is an important initiative, perhaps one that university graduate students might be best equipped to handle. Automatic generation of ontologies from text documentation is also a potential starting point.)
