hcard-issues: Difference between revisions
Jump to navigation
Jump to search
(→Issues) |
|||
| Line 6: | Line 6: | ||
== Issues == | == Issues == | ||
* 2005-06-21 raised by Hixie | |||
*# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how hCards must be parsed, how to handle errors, and so forth. Is it defined in terms of the DOM? Is it defined in terms of a serialisation? How do you handle unexpected content or missing content? | |||
== Template == | |||
Please use this format: | Please use this format: | ||
Revision as of 13:13, 21 June 2005
hCard issues
These are externally raised issues about hCard with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec. Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — Tantek
See related hcalendar-issues.
Issues
- 2005-06-21 raised by Hixie
- Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how hCards must be parsed, how to handle errors, and so forth. Is it defined in terms of the DOM? Is it defined in terms of a serialisation? How do you handle unexpected content or missing content?
Template
Please use this format:
- YYYY-MM-DD raised by AUTHORNAME
- Issue 1: Here is the first issue I have.
- Issue 2: Here is the second issue I have.