ISSUE-73

2009-06-03 11:47:29: Created issue 'Overlap of "predefined vocabularies" with other specifications' nickname predefined-voc owned by Julian Reschke on product HTML 5 spec, 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? ' non-public [Julian Reschke]

2009-07-30 16:29:02: Status changed to 'open' [Dan Connolly]

2009-08-21 11:37:28: Description changed to '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] ' [James Graham]

2009-08-25 11:47:39: Description changed to '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] ' [Julian Reschke]

2009-10-05 08:09:28: Description changed to '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: No change to the specification is now needed, because the predefined vocabularies have been moved out of HTML5 and into separate drafts, and the HTML5 draft does not reference those drafts nor have any dependency on them. -------------------------------------------------------------' [Michael(tm) Smith]

2009-10-05 08:10:58: Description changed to '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. -------------------------------------------------------------' [Michael(tm) Smith]