More information about statements of use

At least one of the three SoUs must come from an OASIS member. You can accept SoUs from non-OASIS members.

The definition of OASIS member is: "a person, organization or entity who is a voting or non-voting member of the corporation, as defined by the OASIS Bylaws." (In the bylaws, if you look, the description is down in Article 12.) So by my reading, an individual member can submit a Statement of Use.

The minimal format for a SoU is:

"<member name> has successfully implemented <committee specification title> Version #.# Committee Specification ## (<link to the spec>) approved <approval date> in accordance with the conformance clauses defined in <section where conformance clauses are defined> <<note here that the wording should either specify "all conformance clauses" or else list/describe the conformance clauses that the implementation satisfies.>> The use of the specification <includes | does not include> interoperation of multiple independent implementations.”

The provider can give more information, but that is the minimal statement. Also, for non-member submissions, the TC can require more supporting information such as links to files, demonstration transcripts, etc.

For OASIS members, the SoU should go to the main TC mailing list. For an Organizational Member, the primary rep must endorse the SoU. If the primary is not a member of the TC, then she/he can just send their statement to whoever is a TC member to forward on.

For non-OASIS members, the SoU must go to the comment mailing list.

The TC must approve a resolution to accept the SoUs.

I think that about covers it.

/chet

On Tue, Oct 21, 2014 at 9:27 AM, Kristen James Eberlein <kris@eberleinconsulting.com> wrote:

Thanks!
On a different note -- Can you provide me with more information about what is required for statements of use? And I assume that an organizational member is an OASIS member that is NOT an individual member; let me know if I am making an incorrect assumption.

Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)

On 10/21/2014 9:14 AM, Chet Ensign wrote:

Let me look into this Kris. I'll get back to you with an answer - this one is old and I need to do some digging...

/chet

On Mon, Oct 20, 2014 at 7:35 PM, Kristen James Eberlein <kris@eberleinconsulting.com> wrote:

Can you provide me with a citation? I could not find an on-line version of the specification.
--
Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 682-2290; kriseberlein (skype)

--

/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

dita message