W3C technical reports

Turn an approved technical design into a precise specification. Improve expression and structure without creating policy, consensus, conformance criteria, or requirements.

Establish authority and scope

• Identify the source of approved requirements and the decision body that owns them.
• Preserve requirement strength, actors, conditions, exceptions, algorithms, data types, error behavior, and compatibility constraints.
• Do not infer a normative requirement from an example, implementation, issue discussion, preference, or common practice.
• Mark unresolved decisions and contradictions as issues. Do not silently choose a behavior.
• State the document's scope, out-of-scope concerns, maturity, and intended implementations.

Build the conceptual model