[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Public Review/Comment of Requirements?
Chet,
I had to look up “Committee Note”. Here are the relevant definitions from the TC Process.------
- "Committee Note" is a Non-Standards Track Work Product that has been approved by a Technical Committee as specified in Section 3.3.
- "Committee Note Draft" is a Non-Standards Track Work Product approved by a Technical Committee as specified in Section 3.1.
- "Committee Note Public Review Draft" is a Committee Note Draft that has been approved by the TC to go to public review as specified in Section 3.2 of this Process.
- "Non-Standards Track Work Product" is a Work Product produced and approved by a TC in accordance with the TC Process which may be progressed to Committee Note as described in Section 3. Non-Standards Track Work Products are intended to be informative and explanatory in nature. They are not subject to the patent licensing and non-assertion obligations requirements of the OASIS IPR Policy.
Non-Standards Track Work Products may directly be approved as Committee Notes by the Technical Committees via a Full Majority vote.Public reviews are optional for Committee Notes. If a TC wishes to conduct public reviews before approving a Committee Note, the same procedures for approving a Committee Specification (as outlined in section 3.1, section 3.2 and section 3.3) and a similar terminology used for the intermediate drafts of the Committee Specifications (i.e. Committee Note Draft and Committee Note Public Review Draft) must be followed.
Note that a Committee Note is never progressed as an OASIS standard.
After approving a Committee Note, a Technical Committee may notify the TC Administrator for publishing the Committee Note to the OASIS Library and announcing its publication to the OASIS membership.
--------
So, assuming we want to follow your recommended process, the document need not follow a prescribed format. We jus need to:
1. Approve the requirements document (by full majority vote) as a “Committee Note Public Review Draft” ,2. Submit a 30 day public review request including a list of external stakeholders who should be notified,3. Collect all public feedback through the comments list, and4. Track and respond to all comments received.
Is that right?
From: Chet Ensign
Sent: Tuesday, February 10, 2015 3:42 PM
To: James E Cabral
Cc: legalxml-courtfiling@lists.oasis-open.org
The most straightforward way is to make it a Committee Note Draft and send it out for public review. I will always bcc any contacts you list on public review announcements (bcc so that they don't get spammed by a reply all somewhere along the food chain).
If you think that this is too early for that, you could informally share a link to a draft document in the TC's Kavi archive. The key thing there would be to get people to submit any thoughts they have for the TC through the -comment@ mailing list. That is what keeps their comments and feedback covered by the OASIS IPR agreements.
If you want to approach professional organizations or people in their professional capacity as opposed to a personal relationship, then I recommend the CN. That presents it as a formal work of the TC and makes an overall good impression.
Best,
/chet
On Tue, Feb 10, 2015 at 3:15 PM, James E Cabral <jec@mtgmc.com> wrote:
Chet,
One of the features that we are planning for ECF 5.0 would involve some segments of the legal services industry (specifically, process servers) that are not well represented in LegalXML today. We have developed some draft requirements and would really like to get feedback from some of the professional associations in this area but we understand we need to stay within OASIS IPR guidelines.
Is there an OASIS process for sharing a requirements document for public comment? If it is not a specification, does it need to follow a prescribed format?
--
/chet [§]
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html
TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin
Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]