Editor: Anne Anderson
Version: 1.4 Updated: 06/10/03 (yy/mm/dd)
This is a profile of the current OASIS document and naming guidelines for applicability to XACML specifications, schemas, and names. It is based on the following references:
According to e-mail from Robin Cover, 3 Oct 2006, Document  is the base document. Document  supplements and clarifies , and is in the process of being merged with .  should be used for document format templates, and  explains fonts, styles, document sections, etc., but  and  are the only normative naming guidelines, and override  and .
The OASIS guidelines apply only to documents to be stored under http://docs.oasis-open.org/xacml/3.0/..., etc., but we will use them for Working Drafts also in order to make conversion to the standard format easier as specifications are approved.
No names of schema elements or attributes are affected.
See  and  for more details.
OASIS provides specification templates at , with instructions for their use in , which are not necessarily up-to-date.  and  override  and .
Changes from older versions:
Be sure to copy new versions of the changed pages from 
[Specification Title] Version[X.X]
Note that all major words in the title are capitalized, and there is no comma before "Version", which is also capitalized.
There is no normative syntax for [Specification Title]. For XACML, we will construct names as in the following examples, but you should get your title approved by the OASIS administration (Robin Cover <firstname.lastname@example.org>, Mary McRae <mary.mcrae&oasis-open.org>) before casting it in concrete:
There is no normative syntax for file names, except that normative specification files must be available in PDF and XHTML formats, and an editable version (.odt, .doc) must be available in the TC repository. When a file becomes a Committee Draft or OASIS Standard, it will be stored under http://docs.oasis-open.org/xacml/<XACML version>/ by the OASIS Administration.
For XACML, we will construct file names as follows:
xacml-<xacml version>[-profile]-<topic>-v<topic version>-<doctype>-<stage>-<draft version>-<language>.<format>
Hyphens will be used to separate name components, and camel case will be used to separate elements within a name component, since underscores are hard to see when a URL is underlined.
The Document Identifier that goes on the title page of a specification is everything up through <draft version>.
Core spec: xacml-3.0-core-spec-v1.0-wd-1-en.pdf Core schema1: xacml-3.0-core-schema-policy-v1.0-wd-1.xml Core schema2: xacml-3.0-core-schema-context-v1.0-wd-1.xml Supplement spec: xacml-3.0-administration-v1.0-wd-13.pdf
Profiles should identify the version of what is being profiled if relevant:
Profile: xacml-3.0-profile-webservices-spec-v1.0-wd-1-en.pdf Profile schema: xacml-3.0-profile-webservices-schema-v1.0-wd-1.xml Profile: xacml-2.0-profile-saml2.0-spec-v2.0-wd-1-en.pdf Profile schema: xacml-2.0-profile-saml2.0-schema-assertion-v2.0-wd-1.xml
If we update a profile, give it a new version (v1.1, v2.0, etc.)
Profile: xacml-2.0-profile-saml2.0-v2.1-spec-wd-1-en.odt Profile schema: xacml-2.0-profile-saml2.0-v2.1-schema-assertion-wd-1.xml
OASIS administration will put Committee Draft and OASIS Standard documents under:
We can continue to use:
OASIS administration recommends URIs of the following form, but this is not a requirement: