hcard-issues

(Difference between revisions)

Jump to: navigation, search
(justification or reference to previous discussion of issue please!)
(closed theoretical issue that was getting a bit ridiculous)
Line 18: Line 18:
*# (Paraphrased) By including organisations and places, as well as people, hCards have lost semantic specificity (see cited mailing list post for details).
*# (Paraphrased) By including organisations and places, as well as people, hCards have lost semantic specificity (see cited mailing list post for details).
-
* {{OpenIssue}} 2006-12-15 raised by [[User:WizardIsHungry|WizardIsHungry]]
+
* 2006-12-15 raised by [[User:WizardIsHungry|WizardIsHungry]]
-
*# [Moved from a user talk page] Hey, why is hiding semi-useful information using CSS bad? The Geo and Address stuff wouldn't be enough to contact me, but I would like there so bookmarklets, crawlers, greasemonkey etc can manipulate it. Is there a policy on using CSS hiding of fields? Thanks :)
+
*# ''[Moved from a user talk page] Hey, why is hiding semi-useful information using CSS bad? The Geo and Address stuff wouldn't be enough to contact me, but I would like there so bookmarklets, crawlers, greasemonkey etc can manipulate it. Is there a policy on using CSS hiding of fields? Thanks :)''
*#* I guess we can't rely that anything that consumes hCards is normalizing it to a particular format instead of just taking all the xml inside the hcard classed block and sticking it somewhere. If it does just store it as a string, then generating html from it will yield the same hidden fields. Perhaps hiding fields by applying a stylesheet to the relevant hcard styles is ok, but not hiding them using inline css styling. Feedback? --[[User:WizardIsHungry|Jon Williams]] 10:28, 22 Dec 2006 (PST)
*#* I guess we can't rely that anything that consumes hCards is normalizing it to a particular format instead of just taking all the xml inside the hcard classed block and sticking it somewhere. If it does just store it as a string, then generating html from it will yield the same hidden fields. Perhaps hiding fields by applying a stylesheet to the relevant hcard styles is ok, but not hiding them using inline css styling. Feedback? --[[User:WizardIsHungry|Jon Williams]] 10:28, 22 Dec 2006 (PST)
*#* Furthermore, [[hcard-example1-steps]] shows using inline CSS to hide fields. What gives? I still think this is an open issue; particularly the distinction between external stylesheet hiding and inline rules though. --[[User:WizardIsHungry|Jon Williams]] 13:33, 5 Jan 2007 (PST)
*#* Furthermore, [[hcard-example1-steps]] shows using inline CSS to hide fields. What gives? I still think this is an open issue; particularly the distinction between external stylesheet hiding and inline rules though. --[[User:WizardIsHungry|Jon Williams]] 13:33, 5 Jan 2007 (PST)
Line 25: Line 25:
*#** The example you cite is the first of several steps, which refine and improve the first step's suboptimal hCard.
*#** The example you cite is the first of several steps, which refine and improve the first step's suboptimal hCard.
*#*** The question is: ''why is this considered suboptimal if it is ok to hide the entire card?'''
*#*** The question is: ''why is this considered suboptimal if it is ok to hide the entire card?'''
-
 
+
*#**** REJECTED CLOSED TOO THEORETICAL. It is not ok to hide the entire card. Without further concrete examples with real world URLs on the web, this issue is closed.
-
http://microformats.org/wiki/hcard#Organization_Contact_Info
+
* {{OpenIssue}} 2006-12-07 raised by RyanKing.
* {{OpenIssue}} 2006-12-07 raised by RyanKing.

Revision as of 22:56, 8 January 2007

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.

IMPORTANT: Please read the hCard FAQ before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

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

For matters relating to the vCard specification itself, see vcard-errata and vcard-suggestions.

See also related hcalendar-issues.

Contents


Issues

<span class="adr">
<span class="type">work</span>:
...
</span>
<span class="tel">
<span class="type">work</span>:
<span class="value">123.456.7890</span>
</span>

the TYPE needs to be a sub-element of the property (adr, tel, etc) NOTE: EMAIL does NOT have many TYPE attributes, only INTERNET and X400

Template

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

Note: large blocks of italic text are inaccessible to many readers, including people with types of visual impairment, dyslexia, etc. [1], [2]. [3], [4], [5]

Related Pages

The hCard specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.

hcard-issues was last modified: Wednesday, December 31st, 1969

Views