hcard-feedback

hCard feedback

General feedback about hCard may be provided here, and the editor(s) will do their best to try to accomodate such feedback. The more specific the feedback the better chance it will be handled. For specific issues with the spec (as opposed to general problems and feedback), please use the hCard issues page.

Feedback may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Use the provided template and add your feedback to the end of the Feedback section. Write your feedback well. — Tantek

Feedback

• 2006-11-15 raised by Lachy in #whatwg.
  1. I think the whole hCard specification needs to be restructured.
  2. It's incredibly difficult to work out what each class name means and how to use them properly.

• 2006-11-15 raised by hsivonen in #whatwg.
  1. Without knowing iCalendar or vCard, it is totally non-obvious to see what hCards or hCalendars would be conforming. The normative part is extremely short and doesn't seem to establish clear enough a mapping between the microformats and the RFCs.
     • This (and Lachy's 2nd feedback point above) should be addressed by clarifying the mapping with better use of the hCard profile which does clearly map the class names to vCard properties and the sections of the vCard specification that defines them. - Tantek

• 2006-11-15 raised by Hixie in #whatwg (and agreed by Lachy and hsivonen).
  1. The hCard spec basically reads as a brainstorm, not a normative spec.

Meta

(feel free to remove once dealt with)

• A definition of, or link to, "#whatwg" would be useful. Andy Mabbett 06:37, 16 Nov 2006 (PST)

Template

Please use this format (copy and paste this to the end of the list to add your feedback):

• YYYY-MM-DD raised by YOURNAME.
  1. Here is the first general feedback I have.
  2. Here is the second general feedback I have.