CSS Template Level 3

Abstract

[Establish the context (style sheets -> CSS -> CSS3 -> modules...) and summarize the module here.]

Status of this document

This is a member-only draft. It may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

The (archived) mailing list w3c-css-wg@w3.org is preferred for discussion of this specification.

This document was produced by the CSS Working Group (part of the Style Activity).

[Change or remove the following CR exit criteria if the spec is not a module, but, e.g., a Note or a profile. This text was decided on 2008-06-04.] For this specification to be advanced to Proposed Recommendation, there must be at least two independent, interoperable implementations of each feature. Each feature may be implemented by a different set of products, there is no requirement that all features be implemented by a single product. For the purposes of this criterion, we define the following terms:

independent

each implementation must be developed by a different party and cannot share, reuse, or derive from code used by another qualifying implementation. Sections of code that have no bearing on the implementation of this specification are exempt from this requirement.

interoperable

passing the respective test case(s) in the official CSS test suite, or, if the implementation is not a Web browser, an equivalent test. Every relevant test in the test suite should have an equivalent test created if such a user agent (UA) is to be used to claim interoperability. In addition if such a UA is to be used to claim interoperability, then there must one or more additional UAs which can also pass those equivalent tests in the same way for the purpose of interoperability. The equivalent tests must be made publicly available for the purposes of peer review.

implementation

a user agent which:

1. implements the specification.
2. is available to the general public. The implementation may be a shipping product or other publicly available version (i.e., beta version, preview release, or “nightly build”). Non-shipping product releases must have implemented the feature(s) for a period of at least one month in order to demonstrate stability.
3. is not experimental (i.e., a version specifically designed to pass the test suite and is not intended for normal usage going forward).

The specification will remain Candidate Recommendation for at least six months.

The following features are at risk:…

Table of contents

• 1. Dependencies on other modules
• 2. Introduction
• 3. Sample section
  • 3.1 Test suite
• 4. Profiles & conformance
• 5. Conformance
• Acknowledgments
• References
  • Normative references
  • Other references
• Index
• Property index

1. Dependencies on other modules

This CSS3 module depends on the following other CSS3 modules:

• CSS3 module: syntax [CSS3SYN]
• CSS3 module: values and units [CSS3VAL]
• [etc]

It has non-normative (informative) references to the following other CSS3 modules:

• [module]
• [module]

2. Introduction

[document here]

3. Sample section

Look at the mark-up in this section for examples. See the documentation for more precise instructions. The companion of this template shows the processed result. (The icon of Woolly is just for fun. It will not appear on public WDs.)

To refer to HTML, use [HTML40] (note the double square brackets). To make a normative reference, insert a “!”, like this: [CSS3SYN] The currently available list of bibliographic data can of course be extended.

We write about a property such as ‘display-model’ like this and about a piece of CSS code like this: ‘foo: bar’. Inline HTML and XML are similar, but use the CODE element: <blockquote>...</blockquote> and <r:xyz>...</r:xyz>.

Note that the property will automatically be linked to its definition.

To put terms into the index, there are many variants, but hopefully the simplest will be the most common. But a little more work now will help many people for a long time.

Note that you can add non-normative notes like this.

Of course, multi-paragraph notes are also possible: just enclose them in a DIV:

Displayed examples come in eight different types: CSS examples that need no separate paragraph of explanation are put in a simple PRE:

EM { font-style: italic }

CSS examples that need extra text need a DIV.

EM { font-style: italic }

Illegal CSS examples (examples of errors) are the same, but with class "illegal-example". Examples of HTML and XML code have class "html" and "xml" respectively, but are otherwise ditto.

A formal definition of a property looks like this:

Cross-references are created by enclosing a term or phrase in <dfn> (like the word cross-references earlier in this sentence). Then any element with the same content will automatically be linked. For example: cross-references.

And a figure with a caption is done like this:

Don't forget to write the longdesc.

An open issue or editorial remark is OK in a WD, but they should be resolved/removed before the document goes to “CR” (Candidate Recommendation). Use class=“issue”.

3.1 Test suite

There should be tests for every property and every section. See [somewhere] for a description of the format of tests.

There should also be a test for every property that tests whether implementations correctly skip illegal values. For example, like this:

<style type="text/css">
p.c1 { display: list-item; display: illegal-value }
</style>
<p class=c1>This paragraph should look like a list item, i.e., with a bullet
before it.

4. Profiles & conformance

[We need some boilerplate text for all modules that explains what we mean by “implement CSS,” because new developers may well be confused by the number of modules and profiles. If somebody wants to implement CSS, what would we like him to do exactly, other than implement everything...]

[This section explains what parts of this module belong in which profiles.]

We have at least 4 profiles: level 1, level 2, level 3 and full

5. Conformance

[...]

Acknowledgments

[acknowledgments]

References

Normative references

[CSS3SYN]

L. David Baron. CSS3 module: Syntax. 13 August 2003. W3C Working Draft. (Work in progress.) URL: http://www.w3.org/TR/2003/WD-css3-syntax-20030813

[CSS3VAL]

Håkon Wium Lie; Chris Lilley. CSS3 module: Values and Units. 19 September 2006. W3C Working Draft. (Work in progress.) URL: http://www.w3.org/TR/2006/WD-css3-values-20060919

Other references

[HTML40]

Dave Raggett; Arnaud Le Hors; Ian Jacobs. HTML 4.0 Specification. 18 December 1997. W3C Recommendation. Revised on 24 April 1998 URL: http://www.w3.org/TR/1998/REC-html40-19980424

Index

• Cross-references, #
• display-model, #
• frequency
  • common, #
• index, #
• resource
  • time spent, #
• simple, #
• simpler, #
• simplest, #
• terms, #
• variant, #
• work, #

Property index