Description
At the January 18, 2011 meeting of the Infrastructure Framework subcommitteee, ince the group has completed its review of edits for the DE 2.0 issues list, and has a draft schema (including Jacob-inspired reorganization to make components independently reusable, gml-compliant targetArea, xlink for linking content objects, more ValueListURI) , we are in the process of reviewing/testing the schema and beginning the formal specification template editing. We discussed today the process for editing and we discussed the need for more participants' testing of the proposed schema to satisfy the use cases submitted at the face-2-face and otherwise. The next step is that I will try to produce and post the 1st version of our “gold” copy draft DE 2.0 spec in the OASIS template to Kavi. Also in regard to testing, we discussed the significance of having those who submitted use cases (DNDO, weather service, others) to have a chance and perhaps a strong recommendation to try the proposed DE 2.0 schema and see if it meets their needs. We can then take this to the larger EM TC audience, and then folks outside can do some testing during the public review.
1. TOPIC: What is the update on DE 2.0 progress? (Answer: (1) We've received template from OASIS, now time to pour in content and start revision process; (2) we're testing/reviewing the proposed schema and awaiting SimpleFeatures (3) we submitted CommonTypes schema to the RIM as a proposed reusable component; (4) We've identified certain issues for some additional thought, including CIQ or VCard, Xlink usability, TargetArea flexibility with ValueListURI. )
2. TOPIC: What is a good process for managing the revisions to the formal specification document? (Answer: (1) Keep a "gold" copy maintained by one chief editor (2) hand out sections for editing by specific subcommittee members; (3) when people edit, they turn on track changes and they append their initials to the working draft title so multiple people can work simultaneously; (4) maintain control; (5) Only post to Kavi when you change the working draft number, maybe once per week; )
3. TOPIC: How are we doing on testing our proposed DE 2.0 schema? (Answer: (1) Jeff began a simple Java parser with the additional goal of showing relevant xlink parsing; (2) now is our time to get the schema right so good time to help test with your particular use case; (3) we should get feedback from those producing use cases at the face-2-face, including DNDO, IPAWS, and weather service; (4) there is a difficulty getting people's time and attention for testing, but it's needed. We may need to do more to encourage participation. )
