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:

Hi Chet:

One specific question:

what is the guideline of implementation.

I remember we need three (prototype) implementations.

Is there any specific requirements what we need to do

by the implementations?

Best,

Mikio

From: Chet Ensign

Sent: Thursday, March 5, 2015 12:25 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

You're very welcome. I see the ticket and we'll respond quickly.

/chet

On Wed, Mar 4, 2015 at 10:23 AM, Mikio Aoyama <mikio.aoyama@nifty.com> wrote:

Hi Chet:

Thank you for your immediate response.

I just submitted a request through the following link

for creating a WD(Working Draft) of PROMCODE Interface specifications.

I very much appreciate your advice.

Best Regards,

Mikio

From: Chet Ensign

Sent: Wednesday, March 4, 2015 11:35 PM

To: Steve K Speicher

Cc: Mikio Aoyama ; Tsutomu Kamimura ; 薮田和夫 ; oslc-promcode@lists.oasis-open.org ; Robin Cover ; Paul Knight

Subject: Re: [oslc-promcode] OASIS Specification Writing Guide

Hi Mikio,

This is great news. I am happy that the TC has made so much progress so quickly.

To start writing the specification, please request a starter document and template using the support request template at https://www.oasis-open.org/resources/tc-admin-requests/work-product-registration-template-request

Even if you will be writing the spec itself using ReSpec, requesting the template will allow me to work out details about filenames, titles, and other mechanical parts of the OASIS process with you in advance. We will prepare and send you a starter document that you can use for writing the draft specification. If you want to write it using ReSpec, we will prepare a version showing the cover page the way it should appear when published.

We don't have a style guide or writing guide but we can offer advice as you work on the draft.

For the sample implementation, we don't really have guidelines on that. You can use the TC's SVN repository as a location for implementation code (https://tools.oasis-open.org/version-control/browse/wsvn/oslc-promcode/?sc=0). If you have some more specific questions on that topic, I will get answers for you.

Again, great work! I look forward to helping you all as you develop your specification.

Best,

/chet

On Wed, Mar 4, 2015 at 9:03 AM, Steve K Speicher <sspeiche@us.ibm.com> wrote:

Specific references on that page:

Specification Writer's Handbook: https://wiki.oasis-open.org/oslc-core/SpecWriterHandbook
Which has references to other OASIS process docs
There is a reference to template you can use at: http://sspeiche.github.io/respec/examples/oslc/template-spec.html
Here's an example of it being used for OSLC Core Resource Preview spec: http://tools.oasis-open.org/version-control/browse/wsvn/oslc-core/specs/resource-preview.html

Thanks,
Steve Speicher
IBM Rational Software
OSLC - Lifecycle integration inspired by the web -> http://open-services.net

From:        "Mikio Aoyama" <mikio.aoyama@nifty.com>
To:        <oslc-promcode@lists.oasis-open.org>
Cc:        <kazuo.yabuta@gmail.com>, "Tsutomu Kamimura" <EBB0CMB@jp.ibm.com>
Date:        03/03/2015 07:43 PM
Subject:        Re: [oslc-promcode] OASIS Specification Writing Guide
Sent by:        <oslc-promcode@lists.oasis-open.org>

Hi All:

Here is the URL:
https://wiki.oasis-open.org/oslc-core/

Mikio
From: Mikio Aoyama
Sent: Wednesday, March 4, 2015 9:25 AM
To: Chet Ensign
Cc: Robin Cover ; Steve K Speicher ; oslc-promcode@lists.oasis-open.org ; kazuo.yabuta@gmail.com ; Tsutomu Kamimura ; arthur.ryman@gmail.com
Subject: [oslc-promcode] OASIS Specification Writing Guide

Dear Chet, Steve and PROMCODE TC Members:

The PROMCODE TC is about starting to write the specifications.
Could you guide us the following points?
Chet:
1. Writing guide of OASIS specifications?
2. Guide of sample implementation?

Steve:
3. Guide of OSLC Member Section, and any review?
Thank you for this procedure.
Best Regards,

Mikio

--

/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

--

/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

/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

oslc-promcode message