ISSUE-73
predefined-voc
Overlap of "predefined vocabularies" with other specifications
- State:
- OPEN
- Product:
- HTML 5 spec
- Raised by:
- Julian Reschke
- Opened on:
- 2009-06-03
- Description:
Recently, new sections have been added to the spec, defining embedding/extraction of data in various formats, such as vCard, iCalendar, Atom, and BibTex. The issues mentioned below a primarily about the vCard related stuff, but similar concerns apply to iCalendar and Atom as well (which both are IETF specs as well). Procedural - the WG is working on trying to find consensus on all sections of the spec; sections without consensus are to be removed (at least that's my understanding of the process). Also, the editor himself announced a "feature freeze" quite some time ago. So, why are we seeing these new sections without *any* prior discussion? Spec Size - the spec already is big, and there is no evidence that this needs to be specified *inside* the HTML5 spec. Extensibility - the current chapter copies terminology from RFC2426, but misses it's extensibility hooks, and thus fails to mention things that have been defined later, such as the IMPP type name. Parsing - for some types, parsing rules are being rephrased from RFC2426. There is a risk that they diverge. Versioning - the IETF is revising vCard, see <http://tools.ietf.org/html/draft-ietf-vcarddav-vcardrev-07>. Is HTML5 going to freeze the vocabulary at a version that the IETF is currently obsoleting? HTML5-SPEC-SECTIONS [predefined-vocabularies predefined-vocabularies-0] ------------------------------------------------------------- PROPOSED RESOLUTION: Resolved by a spec change that has moved the predefined vocabularies out of HTML5 and into separate drafts, none of which the HTML5 draft references or has any dependency on. -------------------------------------------------------------
- Related Actions Items:
ACTION-123 on Sam Ruby to Discuss choice of embedding vcard microdata instead of referencing IETF spec and defining conformance reqs for HTML5 - due 2009-10-31, closed- Related emails:
- minutes Re: {agenda} HTML WG telcon 2009-10-29: issues, action items, calls for consensus/proposals, task forces, F2F... (from cooper@w3.org on 2009-10-29)
- Re: {agenda} HTML WG telcon 2009-10-29: issues, action items, calls for consensus/proposals, task forces, F2F... (from singer@apple.com on 2009-10-29)
- {agenda} HTML WG telcon 2009-10-29: issues, action items, calls for consensus/proposals, task forces, F2F... (from rubys@intertwingly.net on 2009-10-28)
- Re: Microdata vocabulary specifications (from mjs@apple.com on 2009-10-05)
- Re: Microdata vocabulary specifications (from mike@w3.org on 2009-10-05)
- ISSUE-73, was: Microdata vocabulary specifications (from julian.reschke@gmx.de on 2009-10-05)
- Re: Microdata vocabulary specifications (from mike@w3.org on 2009-10-05)
- Producing Atom (was: Microdata vocabulary specifications) (from rubys@intertwingly.net on 2009-10-04)
- Re: Microdata vocabulary specifications (from ian@hixie.ch on 2009-10-04)
- Re: Microdata vocabulary specifications (from ian@hixie.ch on 2009-10-04)
- Re: Microdata vocabulary specifications (from julian.reschke@gmx.de on 2009-10-04)
- Re: Microdata vocabulary specifications (from jonas@sicking.cc on 2009-10-04)
- Re: Microdata vocabulary specifications (from mjs@apple.com on 2009-10-03)
- Re: ISSUE-73 (from julian.reschke@gmx.de on 2009-09-10)
- Agenda for HTML WG telcon 2009-09-10 - Accessibility TF, Testing TF, etc (from Paul.Cotton@microsoft.com on 2009-09-09)
- FW: Agenda for HTML WG telcon 2009-09-10 - Accessibility TF, Testing TF, etc (from Paul.Cotton@microsoft.com on 2009-09-09)
- ISSUE-73 (was: Agenda for HTML WG telcon 2009-09-10) (from rubys@intertwingly.net on 2009-09-09)
- Re: ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from julian.reschke@gmx.de on 2009-07-24)
- Re: ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from ian@hixie.ch on 2009-07-24)
- RE: ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from masinter@adobe.com on 2009-07-23)
- Re: ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from julian.reschke@gmx.de on 2009-07-23)
- Re: ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from ian@hixie.ch on 2009-07-23)
- Re: ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from julian.reschke@gmx.de on 2009-07-21)
- Re: ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from ian@hixie.ch on 2009-07-21)
- Re: ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from julian.reschke@gmx.de on 2009-07-21)
- Re: ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from ian@hixie.ch on 2009-07-21)
- Re: ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from jonas@sicking.cc on 2009-07-16)
- Re: ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from mjs@apple.com on 2009-07-16)
- Re: ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from ian@hixie.ch on 2009-07-16)
- Re: ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from jgraham@opera.com on 2009-07-16)
- Re: ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from julian.reschke@gmx.de on 2009-07-16)
- Re: ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from ian@hixie.ch on 2009-07-16)
- Re: ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from jgraham@opera.com on 2009-07-15)
- Re: ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from julian.reschke@gmx.de on 2009-07-08)
- Re: ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from ian@hixie.ch on 2009-07-08)
- ISSUE-73 (Overlap of 'predefined vocabularies' with other specifications), was: Concerns about new section 'predefined vocabularies' (from julian.reschke@gmx.de on 2009-06-10)
- ISSUE-73 (predefined-voc): Overlap of 'predefined vocabularies' with other specifications [HTML 5 spec] (from sysbot+tracker@w3.org on 2009-06-03)
Related notes:
2009-06-03 11:48:14: Related mail thread starts here: http://lists.w3.org/Archives/Public/public-html/2009May/0113.html [Julian Reschke]
2009-08-10 12:58:38: Sent summary and pointer to IETF Apps Area, plus vcarddav and calsify mailing lists:
http://lists.osafoundation.org/pipermail/ietf-calsify/2009-August/002199.html
[Julian Reschke]
2009-10-05 05:45:09: [MikeSmith]: predefined vocabs have now been moved out of HTML5 and into separate drafts; see http://lists.w3.org/Archives/Public/public-html/2009Oct/0087.html & http://dev.w3.org/html5/mdvcard/ & http://dev.w3.org/html5/mdvevent/ & http://dev.w3.org/html5/mdwork/ and note that HTML5 does not reference those drafts nor have any dependency on them.
Display change log.