Changes in OASIS requirements since 1.0 was published

Aside from the conformance issues mentioned in my previous
note, the following editorial changes should be incorporated going forward.

 

1)     
The key words “MUST”, “MUST
NOT”, “REQUIRED”, “SHALL”, “SHALL
NOT”, “SHOULD”, “SHOULD NOT”,
“RECOMMENDED”, “MAY”, and “OPTIONAL” in this
document are to be interpreted as described in [RFC2119].

http://www.ietf.org/rfc/rfc2119.txt

2)     
Reference WSDL, XML, etc should be in an external
document which can be machine readable. The standards document itself can still
contain sample code. If any inconsistencies are found between the XML in the
artifacts in the standards document and that in the external WSDL and XML, the
external document is considered normative.

3)     
We have been a little loose in using the OASIS artifact
naming standards. We need to distinguish properly between working documents and
committee drafts. Committee drafts are in turn distinguished from committee
documents. Authors should see 

http://docs.oasis-open.org/specGuidelines/namingGuidelines/OASIS-TAB-ArtifactNamingWD06.pdf

4)     
In general, we should use the current templates for documents
as defined in http://docs.oasis-open.org/templates/

 

Meeting these requirements will be critical to meeting our
goals of OASIS Standard rather than Specification

 

Thanks

 

 

tc

"When one door closes, another opens; but we often look
so long and so regretfully upon the closed door that we do not see the one
which has opened for us." -- Alexander Graham Bell

 

  
  
Toby Considine

  
Chair, OASIS oBIX Technical Committee

  OASIS Technical Advisory Board

  OASIS Energy Interoperation TC

  Facilities Technology Office

  University of North Carolina

  Chapel Hill, NC

  
  
  
  

  
  
  
Email: Toby.Considine@
  unc.edu

  Phone: (919)962-9073 

  
http://www.oasis-open.org 

  
blog: www.NewDaedalus.com