[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [oslc-promcode] OASIS Specification Writing Guide
Hi Chet:
Thank you for the right information on the SoU.
At this moment, this would be enough to sketch out
the process of drafting the specfications.
Best Regards,
Mikio
From: Chet Ensign
Sent: Thursday, March 5, 2015 12:59 AM
To: Mikio Aoyama
Cc: Steve K Speicher ; Tsutomu Kamimura ;
薮田和夫 ;
oslc-promcode@lists.oasis-open.org
; Robin
Cover ; Paul Knight
Subject: Re: [oslc-promcode] OASIS Specification Writing
Guide Ah, yes.
I believe you are talking about what we call the Statements of Use (SoU).
You need 3 or more SoUs when you are ready to submit your Committee
Specification to the membership as a Candidate OASIS Standard.
You won't be ready to request those until you have an approved Committee
Specification, although of course people can be working on implementations
throughout your drafting of the spec.
The requirements for the SoUs are simple:
- At least one must come from an OASIS member. The others may come from
implementers who are not OASIS members. You can have as many as you want - 3 is
the minimum.
- The SoU must include the title, version number and approval date of the
Committee Specification it has implemented.
- It must state that it has implemented either all the Conformance Clauses
listed in the spec or else list the Conformance Clauses it implemented.
- It must state whether or not its implementation included or worked with
other interoperable implementations.
The implementations themselves need not be in the OASIS repository although
they certainly can be there. And the SoUs do not have to include links to the
implementations themselves although again you are free to include that.
As I said, you won't need these for some time. I can send you examples
whenever you want to explore further.
Best,
/chet
On Wed, Mar 4, 2015 at 10:39 AM, Mikio Aoyama <mikio.aoyama@nifty.com> wrote:
/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]