Examples of different ways of organizing OASIS specifications

Hi folks,

As promised, here are some examples of different ways different TCs organize their standards. Note that all these documents have a consistent look and feel - when you submit approved work to us to publish, I put on the OASIS cover pages and produce editable source, PDF and HTML versions that go online. Please note - I don't mess with your content! That is yours. I simply put it into our standard cover page layout.

You can find all the approved work at docs.oasis-open.org

Here is a simple Committee Specification - a single narrative spec and no associated documents: http://docs.oasis-open.org/kmip/spec/v1.1/cs01/

Here is a more typical one with a single narrative specification but several associated schemas: http://docs.oasis-open.org/emix/emix/v1.0/cs01/

And here is a multi-part spec (OData version 4.0) with the document itself in several parts and a number of associated artifact types: http://docs.oasis-open.org/odata/odata/v4.0/csprd02/

As I said on the call, I'm happy to consult with you any time on alternatives for structuring your documentation. Just let me know.

Best regards,

/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

xmile message