[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emergency] Statement of Use - CAP 1.2 - Need one more! - Answer found.
|
Elysa, I googled “mandatory conformance clauses stated in the
specification in Section 2.18” and found the OASIS Technical
Committee Process web page: http://www.oasis-open.org/committees/process.php Under section 2.18 it states: 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 be written using the OASIS document authoring templates, which shall be
published and maintained by the TC Administrator. The name of any specification
may not include any trademarks or service marks not owned by OASIS. A specification that is approved by the TC at
the Public Review Draft, Committee Specification or OASIS Standard level must
include a separate section, listing a set of numbered conformance clauses, to
which any implementation of the specification must adhere in order to claim
conformance to the specification (or any optional portion thereof). A specification that is approved by the TC at any level
must include a list of people who participated in the development of the
specification. This 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. A specification that is approved by the TC at any level
must clearly indicate whether each reference in the specification to a document
or artifact is a Normative Reference. Editable formats of all versions of TC documents must be
delivered 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 delivered to the TC’s document repository in the
(1) editable source, (2) HTML or XHTML, and (3) PDF formats; and the TC must
explicitly designate one of those delivered formats as the authoritative
document. Any links published by the TC shall be to the HTML, XHTML and/or PDF
formats stored using repositories and domain names owned by OASIS and as
approved by the TC Administrator. All normative computer language definitions that are
part of the specification, such as XML instances, schemas and Java(TM) code,
including fragments of such, must be well-formed and valid, and must be
provided in separate plain text files. Each text file must be referenced from
the specification. Where any definition in these separate files disagrees with
the definition found in the specification, the definition in the separate file
prevails. 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 (a) the approval status, (b) the
date, (c) the URIs of the specification as appropriate, (d) the running
header/footer, and (e) any approved Designated Cross-Reference Changes, all of
which must be made after the approval of the specification as a Committee
Draft, Committee Specification, or OASIS Standard. This was a bit confusing as the statement
of use reads that 2.18 is from the specification but yet it is actually from
the OASIS Technical Committee Process and not clearly identified in the statement of use. Answer is found but just could have been
more clear. Thank you. Timothy
D. Gilmore | SAIC Senior Test Engineer | ILPSG | NIMS SC |
NIMS STEP phone: 606.274.2063 | fax: 606.274.2012 mobile: 606.219.7882 |
email: P Please consider the
environment before printing this email. From: Gilmore, Timothy
Elysa, Can anyone tell me where is Section 2.18 in the specification
– as called out below? I don’t see it in the public review draft 02
version of CAP v1.2. Section 4 is the Conformance section and
section 2 is Design Principles and Concepts (non-normative). Confusing
that’s all.
Timothy
D. Gilmore | SAIC Senior Test Engineer | ILPSG | NIMS SC |
NIMS STEP phone: 606.274.2063 | fax: 606.274.2012 mobile: 606.219.7882 |
email: gilmoret@us.saic.com P Please consider the
environment before printing this email. From:
emergency-return-1881-timothy.d.gilmore=saic.com@lists.oasis-open.org [mailto:emergency-return-1881-timothy.d.gilmore=saic.com@lists.oasis-open.org]
On Behalf Of Elysa Jones Friends, |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]