OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebsoa message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: TC processes


Sally,
Here is the link to the process for approving a committee draft:
http://www.oasis-open.org/committees/process.php#stand_approv_process

Here is info regarding spec quality (section above the approval
process): 
2.18 Specification Quality

	All documents and other files produced by the TC, including
specifications at any level of approval, must use the OASIS file naming
scheme, and must include the OASIS copyright notice. All document files
must also use the OASIS document templates. The name of any
specification may not include any trademarks or service marks not owned
by OASIS.
	The specification must include a list of people who participated
in the development of the specification. T his list shall be initially
compiled by the Chair, and any Member of the TC may add or remove their
names from the list by request. 
	Editable formats of all versions of TC documents must be
submitted to the TC's document repository. TC Working Drafts may be in
any format (i.e. produced by any application). All TC-approved versions
of documents (i.e. Committee Drafts, Public Review Drafts, and Committee
Specifications) must be submitted to the TC's document repository in the
editable source, HTML, and PDF formats. Any links published by the TC
shall be to the HTML and/or PDF formats stored in the TC's document
repository. 
	All schema and XML instances, whether by inclusion or by
reference, including fragments of such, must be well formed. All
expressions must be valid. All machine-processable schemas, XML
instances etc. that are part of the specification must be available
separately in their own plain text file with their own file name. 
	A specification may be composed of any number of files of
different types, though any such multi-part specification must have a
single specification name and version number. Irrespective of the number
and status of the constituent parts, the specification as a whole must
be approved by a single TC ballot. Any change made to a specification
requires a new version or revision number, except for changes made to
the title page and in the running footer noting the approval status and
date, which must be made after the approval of the specification. 
Here is the link to the templates:
http://docs.oasis-open.org/templates/

Jamie or Mary can also help with questions - you may want to invite one
of them to join a meeting if there are questions still unanswered after
reviewing the materials above.


Kathryn Breininger
CENTRAL Project Manager
Emerging Technologies
Boeing Library Services

425-965-0182 phone
425-237-3491 fax
kathryn.r.breininger@boeing.com

> How was your service? Please click link below.......
> http://socal.web.boeing.com/ssglibsurvey/
> 
> 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]