ISSUE-81: Make declarative definition normative, procedural definition informative. Triage of Issue 75 - Part 3
Make declarative definition normative, procedural definition informative. Triage of Issue 75 - Part 3
- State:
- CLOSED
- Product:
- LC Comment - RDFa Core 1.1
- Raised by:
- Steven Pemberton
- Opened on:
- 2011-01-21
- Description:
- Normative
Jeni Tennison:
Information about how to process RDFa documents is defined in both:
* Section 7.5 Sequence
* Section 8 RDFa Processing in Detail
When I was implementing RDFa 1.0, I found this particularly problematic. I ended up trusting Section 7.5 (or whatever it was then) and ignoring Section 8. What I would like to see is one of these sections becoming non-normative, so that there is a single authoritative place within the spec that defines how to process RDFa.
FWIW, I generally prefer a declarative definition to a procedural one, but Section 8 is written more as a sequence of examples than a detailed definition of RDFa processing, so of the two I think that it should be the one made non-normative. - Related Actions Items:
- No related actions
- Related emails:
- RDFa WG telecon minutes for 2011-03-24 (from msporny@digitalbazaar.com on 2011-03-24)
- RDFa Last Call responses (from msporny@digitalbazaar.com on 2011-03-08)
- ISSUE-81: Specification Structure, Part 3. (from Steven.Pemberton@cwi.nl on 2011-02-24)
- Preparing Official LC Responses (from msporny@digitalbazaar.com on 2011-02-06)
- RDFa WG telecon minutes for 2011-01-27 (from msporny@digitalbazaar.com on 2011-01-27)
- Telecon Agenda - January 28th 2011, 1400 UTC (from msporny@digitalbazaar.com on 2011-01-24)
- ISSUE-81: Make declarative definition normative, procedural definition informative. Triage of Issue 75 - Part 3 [LC Comment - RDFa Core 1.1] (from sysbot+tracker@w3.org on 2011-01-21)
Related notes:
Steven is responsible for this issue.
This change is implemented.
Display change log
