Description
At today's meeting, the RIM members discussed the following topics and developed the proposed answers:
1. Do we need to do any modifications to Werner’s proposed mission statement? (Answer: Only to streamline Werner’s vision statement with Jeff’s previously submitted suggestions, which are more about process, and to incorporate some aspects of the issues (process, repository, responsibility of RIM, etc.) that we’ve been discussing over the last two meetings. Action Item: Werner will take a stab at drafting a merged document after minutes are posted.)
2. How and where should we capture lessons learned such as best practices or guidance? (Answer: We should utilize the adoption wiki, perhaps in the form of frequently asked questions, and the process to gather the lessons learned is a responsibility of the Adoption TC. In order to satisfy this responsibility, the EM Adoption TC will ask for volunteers one each to serve on each subcommittee of the EM TC.)
3. Where should the repository be for the common types? (Answer: The RIM will create two new folders in Kavi, one called “Candidate Common Types” wherein will reside the schema representing the proposed common components submitted by any one of the subcommittees and the other folder called “Common Types” wherein will reside expository material, including material about the RIM process, and zip files of schema with examples, included subschema, etc. needed for testing. These folders support an envisioned 3-level OASIS process: (1) Draft common types schema: Candidate common types are fashioned as they occur in subcommittees and posted to the RIM “Candidate Common Types” folder. (2) Testing of common types schema: The zip files (which include examples, subschema and everything needed to validate the examples and support easy testing by all EM TC members) are posted to the “Common Types” folder; (3) Formal common types spec work: If the consensus among EM TC members is that the testing was successful, then the formal specification for common types (either one that gets revised regularly or multiple small ones, unsure which is best) is put through the formal process and the resulting schema are posted to the normal OASIS spec document repository. Action Items: Rex will request creation of the folders, after which, Jeff will post the common types schema from the DE 2.0 as a sample submission.)
