[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [emergency-rim] Groups - DRAFT-EDXL-RIM-SC-MtgNotes-12-16-2010.doc (DRAFT-EDXL-RIM-SC-MtgNotes-12-16-2010.doc) uploaded
Thanks Jeff, This captures the meeting very well as usual. One small nit: I think 3 should be amended to complete the question: Where should the repository for the common types reside? Cheers, Rex On 12/16/10 12:13 PM, jeff.waters@navy.mil wrote: 20101216201308.29646.qmail@eos.oasis-open.org" type="cite">Please review these minutes of the Reference Information Model (RIM) Subcommittee from today, December 16, 2010, for approval at our next meeting, subject to any specified changes. Thanks. -- Jeff Waters The document named DRAFT-EDXL-RIM-SC-MtgNotes-12-16-2010.doc (DRAFT-EDXL-RIM-SC-MtgNotes-12-16-2010.doc) has been submitted by Jeff Waters to the EM Reference Information Model SC document repository. Document 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 Werners proposed mission statement? (Answer: Only to streamline Werners vision statement with Jeffs previously submitted suggestions, which are more about process, and to incorporate some aspects of the issues (process, repository, responsibility of RIM, etc.) that weve 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.) View Document Details: http://www.oasis-open.org/committees/document.php?document_id=40605 Download Document: http://www.oasis-open.org/committees/download.php/40605/DRAFT-EDXL-RIM-SC-MtgNotes-12-16-2010.doc PLEASE NOTE: If the above links do not work for you, your email application may be breaking the link into two pieces. You may be able to copy and paste the entire link address into the address field of your web browser. -OASIS Open Administration |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]