Read the status and version of a web specification
Distinguish drafts, notes and recommendations before citing a specification or making it a project requirement.
Follow the method ↓
The answer in 30 seconds
A w3.org address may host work in progress, information or a standard. The organisation’s name does not establish the document type. Use this checklist to prepare precise references and implementation questions.
Read status, date and links to published and previous versions. Working Draft and Candidate Recommendation are process stages; a Group Note is not a Recommendation. Cite the real status and independently verify software behaviour.
Examples to adapt
Fictional example: an article links to an Editor’s Draft. Describe it as work in progress and look for a published version.
Fictional example: team and supplier use different editions. Compare relevant passages before discussing interpretation.
Follow the method
- 1Identify the document
Record title, authoring group, date and exact type. Use Status of This Document where present. Do not infer status from a search excerpt.
- 2Choose a version
Keep a dated address to explain the text consulted. Also record the latest-version address to follow changes. These serve different purposes.
- 3Define the scope
Separate standards-track material, informational notes and proposals. In a project specification, name the version and how a requirement will be checked. A document title alone is not an acceptance criterion.
- 4Check practical use
Prepare a small test in target software, record versions and document outcomes. Document maturity and software compatibility are separate observations.
A checklist to keep
Use these checks to record your observations. They are a reading aid, not an automatic assessment.
| Check | What to examine | Action |
|---|---|---|
| Status | Type and authoring group | Qualify the reference |
| Version | Date and dated address | Preserve the text read |
| Scope | Requirement and passage | Avoid vague claims |
| Use | Software and tests | Record limits |
Free, no sign-up. UTF-8 text with semicolon-separated columns.
What to check
Do not call a Group Note a Recommendation.
Identify a translation’s version and provenance.
A local software test does not establish universal compatibility.
Common questions
Is the newest version always a standard?
No. It may be a draft. Read its status.
Why keep a dated address?
It locates the text you read even when the latest version changes.
Does status replace testing?
No. Define the software and situations your project must support.
Sources and documentation
Documentation consulted on . Examples are illustrative; interfaces and results may change.
Continue with a specialist resource
These websites belong to our network. Each has its own editorial scope; check its current information before relying on it.
Reference record for this resource
Identify the publisher, official destination and practical checks before using the service.
Read the W3C record →