Definitions and Goals

(Rough) Definitions of a Registry:

1. Contains essentially independent registered entries (‘rows’)
2. Has a management policy and process for updates
3. Often provides choices for something (field, attribute) in a specification

Goals

1. Easy to manage incrementally once set up
2. Separate from heavier-weight, slower, processes (like patent exclusions)

Elements

1. Referencing specification(s)
   • e.g. the Recommendation(s) using the registry
2. Registry definition and rules
3. Published registry values (the body, contents, table)
   • something new for W3C to publish
4. Registry development and tracking

Registry definition

• The “columns” and rules for their values
• How to get a new registered value, application and approval process
• The update policy: changes, retirements, re-use, etc.
• Any restrictions on referenced specifications (e.g. publicly available, must be W3C)
• Any evidence requirements (e.g. intent to use, evidence of implementability/implementation)

Examples

• W3C Timing Entry Names
• The MP4 Registration Authority
• HTTP Cache Directive

Publishing together (Debate)

Which elements can be, must be, or must not be, combined in one publication?

Referencing Recommendation, Registry Definition, Published Registry

• Registry definitions + Published Registry values
• IETF style: Referencing document + Registry Rules, separate Published Registry (with back-pointer)
• All 3 together (good for simple cases)
• ISO style (bad idea): publication and management are off the ISO site (bad idea)

We may need a new type of specification (Registry Table, Registry Definitions)

Registry Definitions don't need Exclusion (we think)

Publication development rules (under discussion)

Probably apply to all publications; but Recs and Registries have different practice today

Example development rules for W3C publications (under debate)

• Must keep history
• Must have some request/issue/bug tracking
• Must permit notifications of changes, issues etc.
• Must be backed up by the W3C, should be referencable by a w3.org URL
• Should be accessible, viewable/usable by the entire (worldwide) W3C community
• …

More information

More extensive discussion and process requirements on a Wiki

Early draft of a process section, assuming one publication model, on Github