Specification Template 1.0

Unofficial Draft Proposal

This version:
URL of this version
Latest version:
URL of previous version
Previous version:
URL of previous version
Editors:
First Editor Name, Organization Name <editor@example.com>
Second Editor Name, Organization Name <editor@example.com>
Authors:
list of names.

This document is licensed under a Creative Commons Attribution 3.0 License. Insert appropriate license terms.

Abstract

Insert a short description of the specification here. Please explain the use cases and needs that this module meets.

Status of This Document

This section describes the status of this document at the time of its publication. Other documents may supersede this document.

This document is not affiliated with W3C in any way, and is not endorsed or approved by W3C. This document may or may not be reviewed by people or groups operating under W3C.

This document is a working draft of this specification. It has been produced by an independent party as a proposal to the Insert Group Name Here Working Group.

It is inappropriate to cite this specification as as a publication of the World Wide Web Consortium (W3C), or anything other than a work in progress by an independent entity.

How to read this document and give feedback

Please send comments on this specification to person-or-list@example.org

Contents

  1. 1. Introduction
  2. 2. Conformance
  3. 3. Use Cases and Requirements
  4. 4. Features
  5. 5. Examples
  6. 6. Security Considerations
  7. 7. RelaxNG Schema
  8. 8. References
  9. 9. Acknowledgments

1. Introduction

This section is informative.

Describe the technology and specification here.

2. Conformance

This section is normative.

Describe different conformance classes here.

This document contains explicit conformance criteria that overlap with some RNG definitions in requirements. If there is any conflict between the two, the explicit conformance criteria are the definitive reference.

Within this specification, the key words "MUST, "MUST NOT", "REQUIRED, "SHALL, "SHALL NOT, "SHOULD, "SHOULD NOT", "RECOMMENDED, "MAY", and "OPTIONAL" are to be interpreted as described in RFC 2119 [RFC2119]. However, for readability, these words do not necessarily appear in uppercase in this specification.

3. Use Cases and Requirements

This section is informative.

3.1. Use Cases

The following usage scenarios illustrate some of the ways in which Specification Template might be used for various applications:

Insert Use Case 1: Explain use case 1.

Insert Use Case 2: Explain use case 2.

3.2. Requirements

Memory and processor requirements: What are the requirements on memory or processing resources?

Implementation commitments: How difficult, or what details are needed, for implementation?

Ease of authoring: What considerations need to be borne in mind for authors?

4. Features

This section is normative.

Please define the features of the specification here, including the necessary elements, attributes, attribute values, interfaces, methods, and other features.

Authors are encouraged to also describe features in terms of the IDL using Web IDL [WebIDL] blocks inline.

Note: Specification authors are encouraged to use the W3C Typographic Conventions for marking up and styling their documents.

5. Examples

This section is informative.

Provide examples of the usage of the technology here.

6. Security Considerations

This section is informative.

Provide security considerations for the implementation and authoring of this technology here.

7. RelaxNG Schema

The schema for Specification Template 1.0 is written in RelaxNG [RelaxNG], a namespace-aware schema language that uses the datatypes from XML Schema Part 2 [Schema2]. This allows namespaces and modularity to be much more naturally expressed than using DTD syntax. The RelaxNG schema for Specification Template 1.0 may be imported by other RelaxNG schemas, or combined with other schemas in other languages into a multi-namespace, multi-grammar schema using Namespace-based Validation Dispatching Language [NVDL].

Unlike a DTD, the schema used for validation is not hardcoded into the document instance. There is no equivalent to the DOCTYPE declaration. Simply point your editor or other validation tool to the IRI of the schema (or your local cached copy, as you prefer).

Please add a schema here, and link to external schema files, if made available.

8. References

8.1. Normative References

[RFC2119]
Key words for use in RFCs to Indicate Requirement Levels, S. Bradner, March 1997.
Available at http://tools.ietf.org/html/rfc2119.
[RELAXNG]
Document Schema Definition Languages (DSDL) — Part 2: Regular grammar-based validation — RELAX NG, ISO/IEC FDIS 19757-2:2002(E), J. Clark, 村田 真 (Murata M.), eds. International Organization for Standardization, 12 December 2002.
Available at http://www.y12.doe.gov/sgml/sc34/document/0362_files/relaxng-is.pdf.

8.2. Informative References

[SCHEMA2]
XML Schema Part 2: Datatypes Second Edition. P. Biron, A. Malhotra, eds. World Wide Web Consortium, 28 October 2004. (See also Processing XML 1.1 documents with XML Schema 1.0 processors [XML11-SCHEMA].)
This edition of XML Schema Part 2 is http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/.
The latest edition of XML Schema Part 2 is available at http://www.w3.org/TR/xmlschema-2/.
[WebIDL]
WebIDL, C. McCormack, ed. World Wide Web Consortium, work in progress, 19 December 2008.
This edition of WebIDL is http://www.w3.org/TR/2008/WD-WebIDL-20081219/.
The latest edition of WebIDL is available at http://dev.w3.org/2006/webapi/WebIDL/.

9. Acknowledgments

The editors would like to acknowledge and thank the following people for substantive aid with this specification: list of names.