http://microformats.org/wiki/api.php?action=feedcontributions&user=Kornel&feedformat=atomMicroformats Wiki - User contributions [en]2024-03-29T05:15:37ZUser contributionsMediaWiki 1.38.4http://microformats.org/wiki/index.php?title=User:Kornel&diff=43244User:Kornel2010-11-06T20:43:02Z<p>Kornel: contact</p>
<hr />
<div>== Kornel Lesiński ==<br />
<br />
You can contact me via email: <my first name>@geekhood.net.</div>Kornelhttp://microformats.org/wiki/index.php?title=validators&diff=43243validators2010-11-06T20:41:02Z<p>Kornel: /* validator project */ Suggesting hCard Validator as official one</p>
<hr />
<div><entry-title>microformats validators</entry-title><br />
== general purpose validators ==<br />
The following validators will validate multiple microformats on a page:<br />
<br />
===Optimus===<br />
{{main|Optimus}}<br />
<br />
[[Optimus]] is a microformats transformer and validator that supports numerous microformats including [[hCard]], [[hCalendar]], [[hReview]], [[hAtom]] (note: [[optimus-issues#hAtom_validation|hAtom validation issues]]).<br />
<br />
Get the [http://tantek.com/favelets/#optimus-validator Optimus microformats validator favelet]. Blog post: [http://microformats.org/blog/2009/05/27/placemaker-optimus-validator/#optimus-favelet validator browser button].<br />
<br />
Please add issues to the [[optimus-issues]] page.<br />
<br />
== specific microformats validators ==<br />
<br />
=== hCard Validator ===<br />
<ul><li>'''[http://hcard.geekhood.net/ The unofficial hCard Validator]'''<br />
<div class="discussion"><br />
*It's [http://github.com/pornel/hCardValidator open-source] and contributions are welcome! Please join the project and extend it to support more microformats.<br />
</div><br />
</li></ul><br />
<br />
===Operator Debugger===<br />
{{main|Operator}}<br />
* [https://addons.mozilla.org/firefox/4106/ https://addons.mozilla.org/firefox/4106/]<br />
<br />
microformats: hCard, hCalendar<br />
<br />
Operator does a good job of compliant parsing for microformats in general, and includes a debug mode that can help identify errors in the structure.<br />
<br />
=== rel-lint ===<br />
* [http://tools.microformatic.com/help/xhtml/rel-lint/ http://tools.microformatic.com/help/xhtml/rel-lint/]<br />
<br />
Rel-Lint provides linting and inspection of [[rel-tag|rel-tag]] and [[xfn|XFN]] (by [[implementors#Drew_McLellan|Drew McLellan]])<br />
<br />
== validator project ==<br />
There has been a suggestion to host an "official" microformats validator at microformats.org.<br />
<br />
Ideas:<br />
* [https://github.com/pornel/hCardValidator hCard validator is open-source] (BSD-licensed) and extensible enough to support other microformats (it's mostly a matter of hooking up XSLT templates that extract microformat data and find errors). The codebase is pretty clean, UI is internationalized.<br />
* …<br />
<br />
Who wants to help make this happen, and what do you need?<br />
* …<br />
<br />
== related ==<br />
* [[debugging-tools]]<br />
* [[implementations]]<br />
* [[tests]]<br />
* [[test-suite]]</div>Kornelhttp://microformats.org/wiki/index.php?title=validators&diff=43242validators2010-11-06T20:15:11Z<p>Kornel: /* hCard Validator */ fancy formatting</p>
<hr />
<div><entry-title>microformats validators</entry-title><br />
== general purpose validators ==<br />
The following validators will validate multiple microformats on a page:<br />
<br />
===Optimus===<br />
{{main|Optimus}}<br />
<br />
[[Optimus]] is a microformats transformer and validator that supports numerous microformats including [[hCard]], [[hCalendar]], [[hReview]], [[hAtom]] (note: [[optimus-issues#hAtom_validation|hAtom validation issues]]).<br />
<br />
Get the [http://tantek.com/favelets/#optimus-validator Optimus microformats validator favelet]. Blog post: [http://microformats.org/blog/2009/05/27/placemaker-optimus-validator/#optimus-favelet validator browser button].<br />
<br />
Please add issues to the [[optimus-issues]] page.<br />
<br />
== specific microformats validators ==<br />
<br />
=== hCard Validator ===<br />
<ul><li>'''[http://hcard.geekhood.net/ The unofficial hCard Validator]'''<br />
<div class="discussion"><br />
*It's [http://github.com/pornel/hCardValidator open-source] and contributions are welcome! Please join the project and extend it to support more microformats.<br />
</div><br />
</li></ul><br />
<br />
===Operator Debugger===<br />
{{main|Operator}}<br />
* [https://addons.mozilla.org/firefox/4106/ https://addons.mozilla.org/firefox/4106/]<br />
<br />
microformats: hCard, hCalendar<br />
<br />
Operator does a good job of compliant parsing for microformats in general, and includes a debug mode that can help identify errors in the structure.<br />
<br />
=== rel-lint ===<br />
* [http://tools.microformatic.com/help/xhtml/rel-lint/ http://tools.microformatic.com/help/xhtml/rel-lint/]<br />
<br />
Rel-Lint provides linting and inspection of [[rel-tag|rel-tag]] and [[xfn|XFN]] (by [[implementors#Drew_McLellan|Drew McLellan]])<br />
<br />
== validator project ==<br />
There has been a suggestion to host an "official" microformats validator at microformats.org.<br />
<br />
Ideas:<br />
* ...<br />
<br />
Who wants to help make this happen, and what do you need?<br />
* ...<br />
<br />
== related ==<br />
* [[debugging-tools]]<br />
* [[implementations]]<br />
* [[tests]]<br />
* [[test-suite]]</div>Kornelhttp://microformats.org/wiki/index.php?title=validators&diff=43241validators2010-11-06T20:13:46Z<p>Kornel: /* hCard Validator */ syntax</p>
<hr />
<div><entry-title>microformats validators</entry-title><br />
== general purpose validators ==<br />
The following validators will validate multiple microformats on a page:<br />
<br />
===Optimus===<br />
{{main|Optimus}}<br />
<br />
[[Optimus]] is a microformats transformer and validator that supports numerous microformats including [[hCard]], [[hCalendar]], [[hReview]], [[hAtom]] (note: [[optimus-issues#hAtom_validation|hAtom validation issues]]).<br />
<br />
Get the [http://tantek.com/favelets/#optimus-validator Optimus microformats validator favelet]. Blog post: [http://microformats.org/blog/2009/05/27/placemaker-optimus-validator/#optimus-favelet validator browser button].<br />
<br />
Please add issues to the [[optimus-issues]] page.<br />
<br />
== specific microformats validators ==<br />
<br />
=== hCard Validator ===<br />
<ul><li>'''[http://hcard.geekhood.net/ The unofficial hCard Validator]'''<br />
<p><br />
It's [http://github.com/pornel/hCardValidator open-source] and contributions are welcome! Please join the project and extend it to support more microformats.<br />
</p><br />
</li></ul><br />
<br />
===Operator Debugger===<br />
{{main|Operator}}<br />
* [https://addons.mozilla.org/firefox/4106/ https://addons.mozilla.org/firefox/4106/]<br />
<br />
microformats: hCard, hCalendar<br />
<br />
Operator does a good job of compliant parsing for microformats in general, and includes a debug mode that can help identify errors in the structure.<br />
<br />
=== rel-lint ===<br />
* [http://tools.microformatic.com/help/xhtml/rel-lint/ http://tools.microformatic.com/help/xhtml/rel-lint/]<br />
<br />
Rel-Lint provides linting and inspection of [[rel-tag|rel-tag]] and [[xfn|XFN]] (by [[implementors#Drew_McLellan|Drew McLellan]])<br />
<br />
== validator project ==<br />
There has been a suggestion to host an "official" microformats validator at microformats.org.<br />
<br />
Ideas:<br />
* ...<br />
<br />
Who wants to help make this happen, and what do you need?<br />
* ...<br />
<br />
== related ==<br />
* [[debugging-tools]]<br />
* [[implementations]]<br />
* [[tests]]<br />
* [[test-suite]]</div>Kornelhttp://microformats.org/wiki/index.php?title=validators&diff=43240validators2010-11-06T20:12:44Z<p>Kornel: /* hCard Validator */ Linked to validator's github repo</p>
<hr />
<div><entry-title>microformats validators</entry-title><br />
== general purpose validators ==<br />
The following validators will validate multiple microformats on a page:<br />
<br />
===Optimus===<br />
{{main|Optimus}}<br />
<br />
[[Optimus]] is a microformats transformer and validator that supports numerous microformats including [[hCard]], [[hCalendar]], [[hReview]], [[hAtom]] (note: [[optimus-issues#hAtom_validation|hAtom validation issues]]).<br />
<br />
Get the [http://tantek.com/favelets/#optimus-validator Optimus microformats validator favelet]. Blog post: [http://microformats.org/blog/2009/05/27/placemaker-optimus-validator/#optimus-favelet validator browser button].<br />
<br />
Please add issues to the [[optimus-issues]] page.<br />
<br />
== specific microformats validators ==<br />
<br />
=== hCard Validator ===<br />
<ul><li>'''[http://hcard.geekhood.net/ The unofficial hCard Validator]'''<br />
<p><br />
It's [http://github.com/pornel/hCardValidator open-source] and contributions are welcome! Please join the project and extend it to support more microformats.<br />
<br />
===Operator Debugger===<br />
{{main|Operator}}<br />
* [https://addons.mozilla.org/firefox/4106/ https://addons.mozilla.org/firefox/4106/]<br />
<br />
microformats: hCard, hCalendar<br />
<br />
Operator does a good job of compliant parsing for microformats in general, and includes a debug mode that can help identify errors in the structure.<br />
<br />
=== rel-lint ===<br />
* [http://tools.microformatic.com/help/xhtml/rel-lint/ http://tools.microformatic.com/help/xhtml/rel-lint/]<br />
<br />
Rel-Lint provides linting and inspection of [[rel-tag|rel-tag]] and [[xfn|XFN]] (by [[implementors#Drew_McLellan|Drew McLellan]])<br />
<br />
== validator project ==<br />
There has been a suggestion to host an "official" microformats validator at microformats.org.<br />
<br />
Ideas:<br />
* ...<br />
<br />
Who wants to help make this happen, and what do you need?<br />
* ...<br />
<br />
== related ==<br />
* [[debugging-tools]]<br />
* [[implementations]]<br />
* [[tests]]<br />
* [[test-suite]]</div>Kornelhttp://microformats.org/wiki/index.php?title=hcard-implementations&diff=27515hcard-implementations2008-06-16T01:16:07Z<p>Kornel: /* New Implementations */</p>
<hr />
<div><h1>hCard Implementations</h1><br />
{{TOC-right}}<br />
<br />
This page is an '''informative''' section of the [[hcard|hCard specification]].<br />
<br />
The following implementations have been developed which either generate or parse [[hcard|hCards]]. If you have such an hCard implementation, feel free to add it to '''the top''' of the New Implementations section. If you have a page or site which just ''publishes'' hCards, please use [[hcard-examples-in-wild]] instead.<br />
<br />
== New Implementations ==<br />
Add new implementations here for evaluation and classification into the below taxonomy of implementations.<br />
<br />
* [http://hcard.geekhood.net/ hCard Validator] - finally!<br />
* [http://www.cogmap.com/ Cogmap] - Cogmap has a bunch of org charts marked up with hcard. Desperately needs [[XPN]]!<br />
* [http://www.tripit.com/ TripIt] - The TripIt contact list of your connections is marked up with hCard<br />
* [[hAvatar]] - Wordpress plugin displaying avatars for commenters based on their hCard<br />
* [[org.microformats.hCard]] - java hCard parser and creator.<br />
* [http://mobileonlinebusiness.com.au/uf/vCard_to_hCard_converter.html Mobile Online Business' vCard to hCard converter]<br />
*[http://www.jamplanet.com Jam] is an active address book extension for Firefox/Flock. Jam imports Vcard and various CSV formats, and can output contacts in Vcard and hCard format.<br />
*The "[http://typo3.org/extensions/repository/view/tt_address/2.0.1/ tt_address]" extension for [http://www.typo3.com TYPO3] supports hCard since the latest release, v2.0.0 <br />
*[https://addons.mozilla.org/firefox/4106/ Operator] lets you combine pieces of information on Web sites with applications in ways that are useful. (Firefox-plugin)<br />
*[http://rafaeloliveira.net/labs/hcard_creator.zip Wordpress hCard Creator] - I've made this simple plugin for wordpress. It adds the hCard Options submenu at Options menu, where you can create a simple hCard and put it on your blog using < ?php hcard_creator() ?> to show it. Also, it is possible to show an "export to vCard" link, which uses Brian Suda X2V. (Got send an e-mail to him regarding this)<br />
*[http://leftlogic.com/lounge/articles/microformats_bookmarklet/ Microformats Bookmarklet] is a bookmarklet designed for IE6 and IE7, Firefox, Safari, Opera and Camino, that overlays on the current page to allow users to import individual hCards or hCalendars. Written by Remy Sharp.<br />
*[http://domanske.de/2006/09/vcardexplorer-04/ vCardExplorer] is a Mac OS X Application, that displays VCF-Files and extracts hCards from Websites written by [http://vcardexplorer.corefault.de Daniel Kagemann].<br />
* [http://placenamehere.com/mf/nnwextract/ Extract Microformats] is a script for NetNewsWire that supports extracting hCard and hCalendar data in blog posts (via technorati service). Written by [[User:ChrisCasciano|Chris Casciano]]<br />
* [http://allinthehead.com/hkit/ hKit] is an open source PHP 5 parsing library with support for hCard.<br />
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek].<br />
** list of pages with indexing Issues so they can be looked into as to why data is not being extracted<br />
** suda.co.uk/contact<br />
** multipack.co.uk<br />
* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of hCards from within Dreamweaver 8.<br />
* [http://scooch.gr0w.com/ Scooch] is a slide show and presentation creator that generates a [[hCard]] for individual slide show authors and comment authors with a CSS button to parse and download via [http://suda.co.uk/projects/X2V/ X2V]. Also uses [[hReview]] for slide ratings and [[rel-tag]] for categories.<br />
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar<br />
*[http://opensource.reevoo.com/2006/03/08/release-uformats-12/ uformats] is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]<br />
* [http://blog.codeeg.com/tails-firefox-extension-03/ Tails] is a Firefox Extension that will display the presence and details of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage. [https://addons.mozilla.org/firefox/2240/ Tails Export] is an extended version.<br />
* [http://www.stripytshirt.co.uk/features/firefox/smartzilla Smartzilla is a Firefox Extension] that finds hCards on web pages and lets you add them to your addressbook.<br />
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCard and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].<br />
* There is [http://flickr.com/photos/factoryjoe/68755089/ evidence of built-in hCard support in the Konqueror browser]. Specifically, Konqueror 3.5, in KDE 3.5 (kubuntu Breezy w/ update).<br />
* There is [http://tagcamp.org/index.cgi?ContactList evidence of a kwiki plugin for hCards]. Update: the [http://svn.kwiki.org/cwest/Kwiki-hCard/ hCard kwiki plugin svn repository]. See the [http://microwiki.caseywest.com/index.cgi?hCard documentation of the hCard kwiki plugin].<br />
* [http://suda.co.uk/projects/X2V/ X2V] is a bookmarklet that parses hCard and produces a .vcf (vCard) stream. Note: needs to be updated as the spec is refined.<br />
* [http://www.stripytshirt.co.uk Duncan Walker] has built [http://www.stripytshirt.co.uk/features/firefox/smartzilla a Firefox extension] that gets hCard data from a webpage, uses Brian Suda's XSL (locally) to transform it to vcard format and opens the resulting .vcf file.<br />
* [http://george.hotelling.net/90percent/ George] has written a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script] that detects hCards and allows users to easily add them to their address book application. Relies on the X2V web service to do the conversion.<br />
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including hCards, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCard to vCard conversion is done internally within the script. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''<br />
* [http://diveintomark.org/ Mark Pilgrim] has also written an [http://diveintomark.org/projects/greasemonkey/hcard/ hCard parser Greasemonkey user script]. It is self-contained and does not rely on the X2V web service.<br />
* [http://www.oliverbrown.me.uk/2005/09/03/a-working-microformats-extension-to-simplexml/ Oliver Brown] has written an "extension" to [http://www.php.net/simplexml SimpleXML] that gives simple access to hCard information in PHP 5.<br />
* [http://thedredge.org/ Andrew D. Hume] has built a system (Wordpress plugin?) for [http://thedredge.org/2005/06/using-hcards-in-your-blog/ using hCards in your blog] to represent people leaving comments on blog posts.<br />
* [http://greenbytes.de/tech/webdav/rfc2629.xslt rfc2629.xslt] now attempts to generate hCard information ([http://ietf.org/rfc/rfc2629 RFC2629] is an XML format for authoring RFCs and Internet Drafts, see [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html example document])<br />
* [http://tantek.com/microformats/buddylist2hcards.html iChat buddy list to hCards] - Open source AppleScript to automatically convert one's buddy list in the MacOSX iChat AIM client into a valid XHTML 1.0 Strict list of hCards. <br />
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] is a collection of palmpilot and sidekick tools. It includes X2V derivatives xhtml2hcard.xsl and toICal.xsl plus some [http://dev.w3.org/cvsweb/2001/palmagent/hcardTest.html hcardTest] materials<br />
* [http://www.openpsa.org/ OpenPsa 2.x] CRM application uses hCard for all person listings. The widget is [http://www.midgard-project.org/midcom-permalink-922834501b71daad856f35ec593c7a6d reusable across Midgard CMS]<br />
* [http://www.metonymie.com Emiliano Martínez Luque] has written an experimental [http://www.metonymie.com/hCard_extract/app.html hCard finder and structured search application] that finds hCards within a given set of URLs and returns the ones that match the specified search criteria.<br />
<!-- * [http://randomchaos.com/microformats/base/ Microformat Base] is an open-source PHP microformat aggregation crawler, currently recognizing hReview, hCalendar, and hCard. down! --><br />
<br />
==Authoring==<br />
Implementations you can use to author, create, and publish hCards.<br />
<br />
===Web-based Creators===<br />
;[http://microformats.org/code/hcard/creator hCard creator]:Create your own hCards; also has a [http://www.wnas.nl/microformats/hcard/hcardCreator.html Dutch interface]. [[hcard-creator-feedback|hCard Give feedback.]]<br />
<br />
===Blogging and CMS tools===<br />
;[http://euphemize.net/blog/plugins/textpattern/jmc_event_manager/ Textpattern plug-in]:jmc_event_manager is a plugin for [http://textpattern.com/ Textpattern] that outputs locations and events in hCard (and hCalendar) formats. Written by [http://euphemize.net/ Joel Courtney].<br />
;[http://wordpress.org/extend/plugins/addressbook/ Wordpress Addressbook plugin]:Display list of addresses from the blog owner's address book, each marked up as an hCard. Maintained by [http://samwilson.id.au Sam Wilson].<br />
<br />
===Browser scripts and plug-ins===<br />
Browser plugins that work with existing authoring tools:<br />
; Any browser with javascript and a little bit of CSS : [http://microformats.org/code/hcard/creator microformats.org hCard creator] (see also [http://tantek.com/ Tantek]'s original [http://tantek.com/microformats/hcard-creator.html hCard creator on tantek.com].<br />
<br />
===Desktop Authoring Tools===<br />
* ...<br />
<br />
==Search and Discovery==<br />
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek]. <br />
* [http://leftlogic.com/info/articles/microformats_bookmarklet Microformats Bookmarklet] is a bookmarklet designed for Safari (works in Firefox and Camino) that overlays on the current page to allow users to import individual [[hcard|hCards]] or [[hcalendar|hCalendars]]. Written by [http://leftlogic.com Remy Sharp].<br />
<br />
<!-- need to continue copy/rename some parallel implementations from [[hcalendar-implementations]] from here down --><br />
<br />
==Conversion and Import==<br />
Implementations you can use to importing into an address book application, typically by converting hCard to vCard.<br />
<br />
===Web Services===<br />
These return vCard (.vcf) and other contact formats for easy importing into typical address book programs or other processing.<br />
* [http://www.tomota.de www.tomota.de] Online address book that allows to import, export and convert hCard into vCard, ldif, csv and plain text. <br />
<br />
* ...<br />
<br />
===Firefox Greasemonkey Plugins===<br />
* ...<br />
<br />
===Aggregators===<br />
* ...<br />
<br />
===Forms===<br />
* [http://lib.omnia-computing.de/hcardmapper hCard Mapper] maps hCards onto form fields (Javascript based)<br />
<br />
==Browsing==<br />
Implementations that detect, display and otherwise highlight hCards in pages.<br />
* ...<br />
<br />
===Firefox extension===<br />
<br />
[http://www.kaply.com/weblog/operator Operator] - This extension is casual-user, advanced-user and developer friendly. Very customizable and unobstrusive.<br />
<br />
===Flock extension===<br />
* ...<br />
<br />
==Open Source==<br />
Open source libraries of hCard parsers and other related code for building hCard implementations. Note: it is very likely that above implementations may be duplicated in this section. That's ok.<br />
* ...<br />
;Javascript <br />
: The [http://microformats.org/code/hcard/creator hCard creator] ([[hcard-creator-feedback|hCard creator feedback]]) is a very simple, yet illustrative, open source user interface / form / script which creates an hCard in real-time as you type in a set of contact information.<br />
<br />
; PHP : <br />
* [[hKit]]<br />
; Python : <br />
* [http://tommorris.org/files/gmail2hcard-py.txt gmail2hcard-py.txt] - for converting Gmail CSV address book export to hCards<br />
; Java :<br />
* [[org.microformats.hCard]]<br />
; Ruby :<br />
: ...<br />
; XSLT :<br />
* ...<br />
<br />
== Additional Applications ==<br />
This section should probably be incorporated into [[hcard-brainstorming]].<br />
<br />
There are numerous potential additional uses and applications for hCards on the Web. The following are merely a few thoughts and possibilities that folks have come up with:<br />
<br />
* As an open standard/format for [http://www.gravatar.com/ Gravatars].<br />
** Like [http://alper.nl/cgi-bin/OpenAvatar.py?url=http://tantek.com this].<br />
** Wordpress plugin with hCard based replacement for gravatar is in the make. [[User:Alper|Alper]] 12:59, 8 Aug 2007 (PDT)<br />
* Marking up individual authors of blog posts on a group blog<br />
* Marking up people's names and URLs in a blogroll<br />
* Any reference to people in blog posts (e.g. when citing them, or referencing them, or describing them, by name).<br />
* ...<br />
<br />
== Related Pages ==<br />
{{hcard-related-pages}}</div>Kornelhttp://microformats.org/wiki/index.php?title=hcard-feedback&diff=32441hcard-feedback2008-06-15T23:37:42Z<p>Kornel: /* 2008 */</p>
<hr />
<div><h1> hCard feedback </h1><br />
{{TOC-right}}<br />
General feedback about [[hcard|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|hCard issues]] page.<br />
<br />
'''IMPORTANT''': Please read the [[hcard-faq|hCard FAQ]] and the [[hcard-issues#resolved_issues|hCard resolved issues]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
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. — [[User:Tantek|Tantek]]<br />
<br />
== Feedback ==<br />
Please add feedback here, in datetime sequential order:<br />
<br />
=== 2007 ===<br />
* All hCard feedback as of 2007-04-27 has been resolved, and resolved issues have been moved to the [[hcard-issues#resolved_issues|hCard resolved issues]] section. Note there are still a few [[hcard-issues#issues|outstanding issues]]. [[User:Tantek|Tantek]] 08:46, 14 Dec 2007 (PST)<br />
<br />
=== 2008 ===<br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-01-13</span> raised by <span class="fn">Christopher Allen</span> at OpenIDDevCamp (collected by [[User:Tantek|Tantek]]).</span><br />
<div class="description"><br />
*# What is the best practice for publishing your TZ in your hCard? As publishing just a fixed offset will likely result in 1 hour off error half the year for more people, given that the rest of the hCard is likely to be static.<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-06-16</span> raised by <span class="fn">[[User:Kornel|Kornel]]</span></span><br />
<div class="description"><br />
*# In the rfc2426 the KEY property defaults to binary. hCard profile suggests to use &lt;abbr> for the key. Shouldn't it recommend data: URI with application/pgp-keys type or HTTP URL to a PGP/GPG key file? Key in &lt;abbr> can't be copied/saved without dedicated hCard parser. And I'm not sure if line-breaks (removed by attribute whitespace normalisation) aren't neccessary for parsing key file.<br />
</div><br />
</div><br />
<br />
== Template ==<br />
{{issues-format}}<br />
<br />
== Related Pages ==<br />
{{hcard-related-pages}}</div>Kornelhttp://microformats.org/wiki/index.php?title=hcard-issues&diff=27343hcard-issues2008-06-15T19:31:28Z<p>Kornel: /* 2008 */ label type</p>
<hr />
<div><h1> hCard issues </h1><br />
{{TOC-right}}<br />
These are externally raised issues about [[hcard|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. <br />
<br />
'''IMPORTANT''': Please read the [[hcard-faq|hCard FAQ]] and the [[hcard-issues-resolved|hCard resolved issues]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
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. — [http://tantek.com/ Tantek]<br />
<br />
For matters relating to the vCard specification itself, see [[vcard-errata]] and [[vcard-suggestions]].<br />
<br />
See other [[issues]] also.<br />
<br />
== closed issues ==<br />
See: [[hcard-issues-resolved]]<br />
<br />
== resolved issues ==<br />
See: [[hcard-issues-resolved]]<br />
<br />
== issues ==<br />
<span id="Issues">Please add new issues</span> to the '''bottom''' of the list by copy and pasting the [[hcard-issues#Template|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.<br />
<br />
=== 2006 ===<br />
<br />
* {{OpenIssue}} 2006-10-21 raised by [[User:AndyMabbett|Andy Mabbett]]<br />
*# ''There should be some way to say that the URL of an hCard or hCalendar event is the URL of the page itself, without having to include a redundant, and accessibility-damaging link to that page, on the page itself.''<br />
*#* Quite often I see "a" webpage accessible with several different URLs. Typically 1 URL is the "preferred" URL, expected to have a long lifetime. Sometimes other URLs are "convenience" URLs that may have been linked to in the past, but are expected to go away soon, which resolve to the same file (the "latest version"). Then there are "archive" URLs that show an exact copy of that webpage as it appeared some time in the past. I think we want to always use the "preferred" URL, no matter which of those URLs we happen to stumble upon first -- so the URL is not actually redundant. (How exactly is it "accessibility-damaging" for a page to link to itself? Could you explain or add a link to an explanation?) --[[User:DavidCary|DavidCary]] 17:44, 5 Apr 2007 (PDT)<br />
*#**"''How exactly is it "accessibility-damaging" for a page to link to itself?''" - Novice user clicks on link; nothing (it appears) happens. Repeat ad infinitum, until user leaves site to do something else. [[User:AndyMabbett|Andy Mabbett]] 02:43, 6 Apr 2007 (PDT)<br />
*#*A: ACCEPTED THEORETICAL. While I tend to agree with the accessibility guidelines/issues noted herein in theory, to make this a real world issue worthy of higher priority, we need documentation of examples in the wild where the URL of an hCard or hCalendar event is the URL of the page itself, so that we can use those examples to inform brainstorming towards a solution. [[User:Tantek|Tantek]] 15:11, 10 Apr 2007 (PDT)<br />
*#** Examples in the wild where the URL of an hCard is the URL of the page itself:<br />
*#*** [http://2007.sxsw.com/music/showcases/band/999918.html The Pipettes] page at SXSW 2007 (1 of 1000+ bands). There are no links to the page itself on the page to markup with class="url". Thus it would be nice to have a way for the hCard for The Pipettes to indicate that the page itself is the URL for the hCard.<br />
*#*** See also the proposal to use this pattern in [[representative-hcard]]<br />
*#** Examples in the wild where the URL of an hCalendar event is the URL of the page itself:<br />
*#*** [http://2007.sxsw.com/music/showcases/band/999918.html The Pipettes at La Zona Rosa] page at SXSW 2007 (1 of 1000+ concerts, yes, same page as the page for The Pipettes the org). There are no links to the page itself on the page to markup with class="url". Thus it would be nice to have a way for the hCalendar event for The Pipettes at La Zona Rosa to indicate that the page itself is the URL for the hCalendar event.<br />
*#** This is also an [[hreview-issues|hReview issue]] and any other microformat which has a "url" property. Examples where the URL of an (potential) hReview *item* is the URL of the page itself: <br />
*#*** [http://www.amazon.com/exec/obidos/ASIN/0553380958 Snow Crash (Bantam Spectra Book) (Paperback) on Amazon] (millions of potential hReview items/products with reviews on their item pages).<br />
<br />
=== 2007 ===<br />
* {{OpenIssue}} 2007-01-26 raised by [[User::JamesCraig|JamesCraig]].<br />
*# RFC2426 'type' values cannot be localized/internationalized in hCard. In the example below, there is no solution to mark the Spanish version with a type of 'home' since the RFC2426 values are defined in English. <strong>abbr-design-pattern</strong> would suggest using abbr, but 'Casa' is not an abbreviated form of 'home', therefore the currently recommended version (below) is not valid.<pre><nowiki><br />
<span class="tel" xml:lang="es"><br />
<abbr class="type" title="home">Casa</abbr> (<span class="type">pref</span>erido):<br />
<span class="value">+1.415.555.1212</span><br />
</span><br />
</nowiki></pre> <br />
*#* REJECTED. TOO LITTLE INFORMATION. Please provide the precise URL to the specific statement on the accessify forum discussion that asserts that using abbr is not valid. Please also provide a precise URL to a *real world* (as opposed to an artificially constructed test case) example in the wild of an non-English hCard which attempts to specify RFC2426 type information on a "tel" property and fails to do so.<br />
*#* REOPENED and clarified (Also removed Accessify reference pulled from [[http://microformats.org/wiki?title=accessibility&oldid=12943 original raising]]).<br />
*#*# Though erroneously first raised on the accessibility page, this is not an accessibility issue. It is an HTML semantics issue for internationalization. <code>abbr[title]</code> should be an expanded form of <code>abbr</code> contents, in the same language.<br />
*#*# There are real-world non-English examples in the current Mac OS 10.5 (Leopard) developer seed. This code example illustrates the point sufficiently.<br />
*#*# Please leave the clarification as-is even if you feel you must RE-REJECT (add-on, don't revert). My original points were lost when they were taken out of context and moved here. -[[User::JamesCraig|JamesCraig]]<br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2007-03-19</span> raised by <span class="fn">[[User::ChristinaHope|Christina Hope]]</span></span><br />
<div class="description"><br />
*# ''Does Microsoft Outlook 2003 allow the use of the "role" property? I have added it to all of my hCards and it is not appearing. Am I doing something wrong?''<br />
*#** URL? (if no URL to a demonstrative example is provided within a year of this issue being raised, it will be closed as REJECTED INSUFFICIENT INFORMATION.)<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2007-03-31</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span></span><br />
<div class="description"><br />
*# The [http://en.wikipedia.org/wiki/World_Geodetic_System WGS84 scehma] used as a default by <code>geo</code> will not remain valid forever. Fortunately, the proposed [[geo-extension-strawman|geo extension]], originally intended for lunar/ Martian coordinates, also provides a facility for the specification of other, Earth-bound schema, which will alleviate this problem. [[User:AndyMabbett|Andy Mabbett]] 13:00, 31 Mar 2007 (PDT)<br />
*#* Note also the forthcoming [http://www.euref-iag.net/ European Terrestrial Reference System 89 schema] (See also [http://en.wikipedia.org/wiki/European_Terrestrial_Reference_System_1989 Etrs89 on Wikipedia]. [[User:AndyMabbett|Andy Mabbett]] 03:11, 5 Apr 2007 (PDT)<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2007-04-19</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span></span><br />
<div class="description"><br />
*#How should we handle [http://en.wikipedia.org/wiki/Old_Style_and_New_Style_dates Old Style and New Style dates] (i.e. Julian calendar vs. Gregorian), in DoB? For instance, [http://en.wikipedia.org/wiki/Boris_Pasternak Boris Pasternak], born "10 February [O.S. January 29] 1890". Should the hCard spec. specify New Style, using the [[abbr-design-pattern]] (or its successor) if necessary: <nowiki><abbr title="1890-02-10">29 January 1890</abbr></nowiki>?<br />
</div><br />
</div><br />
<br />
===2008===<br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-01-01</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011182.html microformats-discuss/2008-January/011182.html]</span><br />
<div class="description"><br />
*# The "n" optimisation rules (nickname, fn) should not apply where the fn is on part of adr or label: e.g <code><nowiki><br />
<span class="fn locality">New York</span></nowiki></code>; <code><nowiki><span class="fn label">Asia</span></nowiki></code>, since, in these examples, "Asia" is not a nickname, "New" is not a given-name and "York" is not a family-name. (see also [[hcard-brainstorming#Named_locations]])<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary"><span class="dtstart">2008-01-09</span> <span id="tel-type-lang">2008- moved from vcard-suggestions</span></span><br />
<div class="description"><br />
*#We can't have a generic type name cause we have to localize in French. so, for us, hCard work phone number is: <nowiki><div class="tel"><span class="type">Travail</span> : <span class="value">0321596224</span></div></nowiki>. How will a bot recognize that type ? We cannot specify every types in every languages in the specification. That's why i think something like this would be better: <nowiki>Travail : <span class="telwork">0321596224</span></nowiki> Please, use class and id attributes ONLY for micro formats specifications ! XML #cdata and #data are localized ! Thanks !<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-02-02</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span></span><br />
<div class="description"><br />
*# The "<code>n</code>" optimisation rules (<code>nickname</code>, <code>fn</code>) should not apply where the <code>fn</code> is also the <code>role</code> or <code>title</code>: e.g <code><nowiki><br />
<span class="fn role">Webmaster</span></nowiki></code>; <code><nowiki><span class="fn title">Duty Manager</span></nowiki></code>, since, in these examples, "Webmaster" is not a nickname, "Duty" is not a given-name and "Manager" is not a family-name.<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-02-06</span> raised by <span class="fn">[[User:Guillaume Lebleu| Guillaume Lebleu]]</span></span><br />
<div class="description"><br />
*# It seems to me that FN has been reused beyond its original vCard scope of person names, to cover any name. This led to the fn/title debate, but it seems some implementors are confused between following the vCard semantics (FN only for person names) or the hCard ones (FN for any name). See. http://cinematreasures.org/theater/365/, which uses an empty FN, resulting in their vCard not being detected by Operator, only the address.<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-02-07</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span></span><br />
<div class="description"><br />
*# The "<code>fn</code>" optimisation rule should not apply where the full <code>fn</code> is also the <code>nickname</code>: e.g <code><nowiki><span class="fn nickname">Plastic Bertram</span></nowiki></code>, since a given-name+family-name pair is not usually a nickname. (But how to deal with pseudonyms such as "Maurice Micklewhite (known professionally as Michael Caine)"?)<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-02-07</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-February/011552.html microformats-discuss/2008-February/011552.html]</span><br />
<div class="description"><br />
*# Is "n" optional or mandatory? The spec says yes (with exceptions) the cheat-sheet says no. Parsers and common practice seem to indicate not.<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-02-07</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-February/011552.html microformats-discuss/2008-February/011552.html]</span><br />
<div class="description"><br />
*# "<code>nickname</code>" and "<code>fn</code>" optimisation does not work for some or all names in Asian languages. See [http://zh.wikipedia.org/wiki/%E6%B9%AF%E5%A7%86%C2%B7%E5%85%8B%E9%AD%AF%E6%96%AF Tom Cruise on Chinese Wikipedia], where the <code>fn</code> and nickname are the same. This could be partly remedied by not applying such optimisation when the page's (or element's) language is set to one of a set of affected languages (may also apply to other languages, such as Greek). '''Cpmment from people fluent in such languages would be welcome.'''<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-02-08</span> raised by <span class="fn">[[User:Guillaume Lebleu| Guillaume Lebleu]]</span></span><br />
<div class="description"><br />
*# The required FN makes it difficult to use hCard in HTML Tables without resorting to hiding information (as in http://www.bo.ingv.it/contents/INGV-Bologna/Staff.html) or using the [[include-pattern]]. Perhaps FN should not be required if some N are present. Originally raised in [http://rbach.priv.at/Microformats/IRC/2008-02-08#T181749]<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-06-01</span> raised by <span class="fn">[[User:Kornel|Kornel]]</span></span><br />
<div class="description"><br />
*# I need clarification how should "more semantic equivalents" be interpreted inside values (when they don't have relevant class name, but are inside another parsed element)<br />
*#* <code><nowiki>&lt;span class=&quot;email&quot;&gt;&lt;a href=&quot;mailto:href&quot;&gt;nodetext&lt;/a&gt;&lt;/span&gt;</nowiki></code> &ndash; is it "href", "nodetext" or an error? What if there are multiple links inside?<br />
*#** Parsed as "nodetext" [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)<br />
*#* <code><nowiki>&lt;span class=&quot;fn&quot;&gt;&lt;abbr title=&quot;title&quot;&gt;nodetext&lt;/abbr&gt;&lt;/span&gt;</nowiki></code> &ndash; is it "title" or "nodetext"?<br />
*#** Parsed as "nodetext" [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)<br />
*#* <code><nowiki>&lt;span class=&quot;fn&quot;&gt;&lt;img alt=&quot;alt&quot;&gt;nodetext&lt;/span&gt;</nowiki></code> &ndash; is it "alt", "nodetext" or both?<br />
*#** A matter of debate recently. Some parsers as "nodetext", others as "altnodetext". [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)<br />
*#* <code><nowiki>&lt;span class=&quot;fn&quot;&gt;&lt;abbr title=&quot;title&quot;&gt;&lt;span class=&quot;value&quot;&gt;nodetext&lt;/span&gt;&lt;/abbr&gt;&lt;/span&gt;</nowiki></code> &ndash;&nbsp;"title", "nodetext" or both?<br />
*#** Parsed as "nodetext" [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)<br />
*#* <code><nowiki>&lt;span class=&quot;url&quot;&gt;&lt;img src=&quot;src&quot; alt=&quot;alt&quot;&gt;nodetext&lt;/span&gt;</nowiki></code> &ndash; "src", "alt", "nodetext" or "altnodetext"?<br />
*#** A matter of debate recently. Some parsers as "nodetext", others as "altnodetext". [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)<br />
*#* <code>&lt;div class=&quot;category&quot;&gt;&lt;a rel=&quot;tag bookmark&quot; href=&quot;href&quot;&gt;nodetext&lt;/a&gt;&lt;/div&gt;</code> – is it a tag? What if there are multiple links inside?<br />
*#** Not sure how other parsers treat this, but Cognition will create two categories based on this. One because of the [rel-tag], based on the final component of the URL; and the second category because of class=category, based on the node text. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)<br />
*# Does <code>agent</code> property has to be a hCard?<br />
*#* Is <code>&lt;span class=&quot;agent&quot;&gt;Joe Sixpack&lt;/span&gt;</code> allowed?<br />
*#** Yes. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)<br />
*#* Is <code>&lt;span class=&quot;agent&quot;&gt;&lt;div class=&quot;vcard&quot;&gt;&hellip;&lt;/div&gt;&lt;/span&gt;</code> ok?<br />
*#** [http://buzzword.org.uk/cognition/ Cognition] doesn't specifically support this format - they'll be parsed as two separate hCards. The "outer" hCard will have an "agent" property containing the unparsed node text for the inner hCard, as if you'd used a plain string for the agent as per the previous example. If you want to provide an hCard for the agent, and have it parsed as such, Cognition requires that you use: <code>&lt;div class=&quot;agent vcard&quot;&gt;&hellip;&lt;/div&gt;</code>. (There is also the separate issue that it is illegal in HTML to nest a DIV within a SPAN.) [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)<br />
*#* What about <code>&lt;a class=&quot;agent&quot; href=&quot;card.vcf&quot;&gt;&hellip;&lt;/a&gt;</code>?<br />
*#** I don't think many hCard parsers also parse vCard. If they support vCard it's probably as an output format rather than input. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)<br />
*# Is value of <code>&lt;abbr&gt;</code> without <code>title</code> empty or should it be interpreted like <code>&lt;span&gt;</code>?<br />
*#* I think consensus is that the node text should be used. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)<br />
*# Does <code>&lt;acronym&gt;</code> work like <code>&lt;abbr&gt;</code>?<br />
*#* Not as per spec, but some parsers do treat it like <code>&lt;abbr&gt;</code>. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)<br />
*# Is this allowed: <code><nowiki>&lt;div class=&quot;photo&quot;&gt;http://example.com/photo.jpg&lt;/div&gt;</nowiki></code>?<br />
*#* Yes, though it ''may'' cause problems for some naive parsers, and is probably less useful for humans viewing the page. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)<br />
*# Is it allowed to use <code><nowiki>http://</nowiki></code> URLs in <code>email</code>? or <code><nowiki>mailto:</nowiki></code> in <code>url</code>?<br />
*#* Non-SMTP e-mail addresses can be used - the presence of a e-mail "type" of "x400" confirms this - so e-mail addresses which don't start with "mailto:" and do not contain an @-sign are theoretically possible. But given the prevalence of SMTP for mail delivery on the modern Internet, I don't see why this would be useful. For "url" it is often useful to encode non-HTTP URIs, such as FTP addresses or URIs for use with various instant messaging protocols, but given the existence of the "email" property, I don't see that it makes sense to encode "mailto" URIs. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)<br />
*# Is it allowed/required to use <code>mailto:</code> when e-mail is in non-<code>&lt;a&gt;</code>, e.g. <code><nowiki>&lt;span class=&quot;email&quot;&gt;mailto:joe@example.com&lt;/span&gt;</nowiki></code><br />
*#* Yes, but for copy-and-pastability I'd recommend leaving out the "mailto:" prefix. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)<br />
*# If value of a property is empty (<code><nowiki>&lt;span class=&quot;email&quot;&gt;&lt;/span&gt;</nowiki></code>) should it be interpreted as unknown value? ignored completely like it didn't exist? an error?<br />
*# Can hCard contain nested hCard <i>anywhere</i>? or only outside any property or only inside <code>agent</code>?<br />
*#* Yes, though naive parsers may have problems. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)<br />
*# Can <code>organi'''s'''ation-name</code> (note spelling) be interpreted by parsers?<br />
*#* It should not. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)<br />
*# Is <code>type</code> class ignored in values anywhere? It is ignored in <code>&lt;div class=&quot;tel&quot;&gt;&lt;span class=&quot;type&quot;&gt;Work&lt;/span&gt; 555&lt;/div&gt;</code>, but is it in <code>&lt;div class=&quot;fn&quot;&gt;&lt;span class=&quot;type&quot;&gt;Work&lt;/span&gt; Joe&lt;/div&gt;</code>?<br />
*#* It doesn't have any special meaning within "fn", so should not be ignored. That is, the person's name would be parsed as "Work Joe". [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-06-15</span> raised by <span class="fn">[[User:Kornel|Kornel]]</span></span><br />
<div class="description"><br />
*# RFC 2426 allows TYPE for LABEL, however [[hcard-cheatsheet|hCard cheatsheet]] does not list any subproperties for <code>label</code>. Is this intentional? Is <code>label</code>'s <code>type</code> allowed in hCard?<br />
</div><br />
</div><br />
<br />
== template ==<br />
<br />
{{issues-format}}<br />
<br />
== related pages ==<br />
{{hcard-related-pages}}</nowiki></div>Kornelhttp://microformats.org/wiki/index.php?title=hcard-issues&diff=27240hcard-issues2008-06-01T14:45:27Z<p>Kornel: /* 2008 */ multiple questions about conformance criteria</p>
<hr />
<div><h1> hCard issues </h1><br />
{{TOC-right}}<br />
These are externally raised issues about [[hcard|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. <br />
<br />
'''IMPORTANT''': Please read the [[hcard-faq|hCard FAQ]] and the [[hcard-issues-resolved|hCard resolved issues]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.<br />
<br />
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. — [http://tantek.com/ Tantek]<br />
<br />
For matters relating to the vCard specification itself, see [[vcard-errata]] and [[vcard-suggestions]].<br />
<br />
See other [[issues]] also.<br />
<br />
== closed issues ==<br />
See: [[hcard-issues-resolved]]<br />
<br />
== resolved issues ==<br />
See: [[hcard-issues-resolved]]<br />
<br />
== issues ==<br />
<span id="Issues">Please add new issues</span> to the '''bottom''' of the list by copy and pasting the [[hcard-issues#Template|Template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.<br />
<br />
=== 2006 ===<br />
<br />
* {{OpenIssue}} 2006-10-21 raised by [[User:AndyMabbett|Andy Mabbett]]<br />
*# ''There should be some way to say that the URL of an hCard or hCalendar event is the URL of the page itself, without having to include a redundant, and accessibility-damaging link to that page, on the page itself.''<br />
*#* Quite often I see "a" webpage accessible with several different URLs. Typically 1 URL is the "preferred" URL, expected to have a long lifetime. Sometimes other URLs are "convenience" URLs that may have been linked to in the past, but are expected to go away soon, which resolve to the same file (the "latest version"). Then there are "archive" URLs that show an exact copy of that webpage as it appeared some time in the past. I think we want to always use the "preferred" URL, no matter which of those URLs we happen to stumble upon first -- so the URL is not actually redundant. (How exactly is it "accessibility-damaging" for a page to link to itself? Could you explain or add a link to an explanation?) --[[User:DavidCary|DavidCary]] 17:44, 5 Apr 2007 (PDT)<br />
*#**"''How exactly is it "accessibility-damaging" for a page to link to itself?''" - Novice user clicks on link; nothing (it appears) happens. Repeat ad infinitum, until user leaves site to do something else. [[User:AndyMabbett|Andy Mabbett]] 02:43, 6 Apr 2007 (PDT)<br />
*#*A: ACCEPTED THEORETICAL. While I tend to agree with the accessibility guidelines/issues noted herein in theory, to make this a real world issue worthy of higher priority, we need documentation of examples in the wild where the URL of an hCard or hCalendar event is the URL of the page itself, so that we can use those examples to inform brainstorming towards a solution. [[User:Tantek|Tantek]] 15:11, 10 Apr 2007 (PDT)<br />
*#** Examples in the wild where the URL of an hCard is the URL of the page itself:<br />
*#*** [http://2007.sxsw.com/music/showcases/band/999918.html The Pipettes] page at SXSW 2007 (1 of 1000+ bands). There are no links to the page itself on the page to markup with class="url". Thus it would be nice to have a way for the hCard for The Pipettes to indicate that the page itself is the URL for the hCard.<br />
*#*** See also the proposal to use this pattern in [[representative-hcard]]<br />
*#** Examples in the wild where the URL of an hCalendar event is the URL of the page itself:<br />
*#*** [http://2007.sxsw.com/music/showcases/band/999918.html The Pipettes at La Zona Rosa] page at SXSW 2007 (1 of 1000+ concerts, yes, same page as the page for The Pipettes the org). There are no links to the page itself on the page to markup with class="url". Thus it would be nice to have a way for the hCalendar event for The Pipettes at La Zona Rosa to indicate that the page itself is the URL for the hCalendar event.<br />
*#** This is also an [[hreview-issues|hReview issue]] and any other microformat which has a "url" property. Examples where the URL of an (potential) hReview *item* is the URL of the page itself: <br />
*#*** [http://www.amazon.com/exec/obidos/ASIN/0553380958 Snow Crash (Bantam Spectra Book) (Paperback) on Amazon] (millions of potential hReview items/products with reviews on their item pages).<br />
<br />
=== 2007 ===<br />
* {{OpenIssue}} 2007-01-26 raised by [[User::JamesCraig|JamesCraig]].<br />
*# RFC2426 'type' values cannot be localized/internationalized in hCard. In the example below, there is no solution to mark the Spanish version with a type of 'home' since the RFC2426 values are defined in English. <strong>abbr-design-pattern</strong> would suggest using abbr, but 'Casa' is not an abbreviated form of 'home', therefore the currently recommended version (below) is not valid.<pre><nowiki><br />
<span class="tel" xml:lang="es"><br />
<abbr class="type" title="home">Casa</abbr> (<span class="type">pref</span>erido):<br />
<span class="value">+1.415.555.1212</span><br />
</span><br />
</nowiki></pre> <br />
*#* REJECTED. TOO LITTLE INFORMATION. Please provide the precise URL to the specific statement on the accessify forum discussion that asserts that using abbr is not valid. Please also provide a precise URL to a *real world* (as opposed to an artificially constructed test case) example in the wild of an non-English hCard which attempts to specify RFC2426 type information on a "tel" property and fails to do so.<br />
*#* REOPENED and clarified (Also removed Accessify reference pulled from [[http://microformats.org/wiki?title=accessibility&oldid=12943 original raising]]).<br />
*#*# Though erroneously first raised on the accessibility page, this is not an accessibility issue. It is an HTML semantics issue for internationalization. <code>abbr[title]</code> should be an expanded form of <code>abbr</code> contents, in the same language.<br />
*#*# There are real-world non-English examples in the current Mac OS 10.5 (Leopard) developer seed. This code example illustrates the point sufficiently.<br />
*#*# Please leave the clarification as-is even if you feel you must RE-REJECT (add-on, don't revert). My original points were lost when they were taken out of context and moved here. -[[User::JamesCraig|JamesCraig]]<br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2007-03-19</span> raised by <span class="fn">[[User::ChristinaHope|Christina Hope]]</span></span><br />
<div class="description"><br />
*# ''Does Microsoft Outlook 2003 allow the use of the "role" property? I have added it to all of my hCards and it is not appearing. Am I doing something wrong?''<br />
*#** URL? (if no URL to a demonstrative example is provided within a year of this issue being raised, it will be closed as REJECTED INSUFFICIENT INFORMATION.)<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2007-03-31</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span></span><br />
<div class="description"><br />
*# The [http://en.wikipedia.org/wiki/World_Geodetic_System WGS84 scehma] used as a default by <code>geo</code> will not remain valid forever. Fortunately, the proposed [[geo-extension-strawman|geo extension]], originally intended for lunar/ Martian coordinates, also provides a facility for the specification of other, Earth-bound schema, which will alleviate this problem. [[User:AndyMabbett|Andy Mabbett]] 13:00, 31 Mar 2007 (PDT)<br />
*#* Note also the forthcoming [http://www.euref-iag.net/ European Terrestrial Reference System 89 schema] (See also [http://en.wikipedia.org/wiki/European_Terrestrial_Reference_System_1989 Etrs89 on Wikipedia]. [[User:AndyMabbett|Andy Mabbett]] 03:11, 5 Apr 2007 (PDT)<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2007-04-19</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span></span><br />
<div class="description"><br />
*#How should we handle [http://en.wikipedia.org/wiki/Old_Style_and_New_Style_dates Old Style and New Style dates] (i.e. Julian calendar vs. Gregorian), in DoB? For instance, [http://en.wikipedia.org/wiki/Boris_Pasternak Boris Pasternak], born "10 February [O.S. January 29] 1890". Should the hCard spec. specify New Style, using the [[abbr-design-pattern]] (or its successor) if necessary: <nowiki><abbr title="1890-02-10">29 January 1890</abbr></nowiki>?<br />
</div><br />
</div><br />
<br />
===2008===<br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-01-01</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011182.html microformats-discuss/2008-January/011182.html]</span><br />
<div class="description"><br />
*# The "n" optimisation rules (nickname, fn) should not apply where the fn is on part of adr or label: e.g <code><nowiki><br />
<span class="fn locality">New York</span></nowiki></code>; <code><nowiki><span class="fn label">Asia</span></nowiki></code>, since, in these examples, "Asia" is not a nickname, "New" is not a given-name and "York" is not a family-name. (see also [[hcard-brainstorming#Named_locations]])<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary"><span class="dtstart">2008-01-09</span> <span id="tel-type-lang">2008- moved from vcard-suggestions</span></span><br />
<div class="description"><br />
*#We can't have a generic type name cause we have to localize in French. so, for us, hCard work phone number is: <nowiki><div class="tel"><span class="type">Travail</span> : <span class="value">0321596224</span></div></nowiki>. How will a bot recognize that type ? We cannot specify every types in every languages in the specification. That's why i think something like this would be better: <nowiki>Travail : <span class="telwork">0321596224</span></nowiki> Please, use class and id attributes ONLY for micro formats specifications ! XML #cdata and #data are localized ! Thanks !<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-02-02</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span></span><br />
<div class="description"><br />
*# The "<code>n</code>" optimisation rules (<code>nickname</code>, <code>fn</code>) should not apply where the <code>fn</code> is also the <code>role</code> or <code>title</code>: e.g <code><nowiki><br />
<span class="fn role">Webmaster</span></nowiki></code>; <code><nowiki><span class="fn title">Duty Manager</span></nowiki></code>, since, in these examples, "Webmaster" is not a nickname, "Duty" is not a given-name and "Manager" is not a family-name.<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-02-06</span> raised by <span class="fn">[[User:Guillaume Lebleu| Guillaume Lebleu]]</span></span><br />
<div class="description"><br />
*# It seems to me that FN has been reused beyond its original vCard scope of person names, to cover any name. This led to the fn/title debate, but it seems some implementors are confused between following the vCard semantics (FN only for person names) or the hCard ones (FN for any name). See. http://cinematreasures.org/theater/365/, which uses an empty FN, resulting in their vCard not being detected by Operator, only the address.<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-02-07</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span></span><br />
<div class="description"><br />
*# The "<code>fn</code>" optimisation rule should not apply where the full <code>fn</code> is also the <code>nickname</code>: e.g <code><nowiki><span class="fn nickname">Plastic Bertram</span></nowiki></code>, since a given-name+family-name pair is not usually a nickname. (But how to deal with pseudonyms such as "Maurice Micklewhite (known professionally as Michael Caine)"?)<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-02-07</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-February/011552.html microformats-discuss/2008-February/011552.html]</span><br />
<div class="description"><br />
*# Is "n" optional or mandatory? The spec says yes (with exceptions) the cheat-sheet says no. Parsers and common practice seem to indicate not.<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-02-07</span> raised by <span class="fn">[[User:AndyMabbett|Andy Mabbett]]</span> in [http://microformats.org/discuss/mail/microformats-discuss/2008-February/011552.html microformats-discuss/2008-February/011552.html]</span><br />
<div class="description"><br />
*# "<code>nickname</code>" and "<code>fn</code>" optimisation does not work for some or all names in Asian languages. See [http://zh.wikipedia.org/wiki/%E6%B9%AF%E5%A7%86%C2%B7%E5%85%8B%E9%AD%AF%E6%96%AF Tom Cruise on Chinese Wikipedia], where the <code>fn</code> and nickname are the same. This could be partly remedied by not applying such optimisation when the page's (or element's) language is set to one of a set of affected languages (may also apply to other languages, such as Greek). '''Cpmment from people fluent in such languages would be welcome.'''<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-02-08</span> raised by <span class="fn">[[User:Guillaume Lebleu| Guillaume Lebleu]]</span></span><br />
<div class="description"><br />
*# The required FN makes it difficult to use hCard in HTML Tables without resorting to hiding information (as in http://www.bo.ingv.it/contents/INGV-Bologna/Staff.html) or using the [[include-pattern]]. Perhaps FN should not be required if some N are present. Originally raised in [http://rbach.priv.at/Microformats/IRC/2008-02-08#T181749]<br />
</div><br />
</div><br />
<br />
<div class="vevent"><br />
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">2008-06-01</span> raised by <span class="fn">[[User:Kornel|Kornel]]</span></span><br />
<div class="description"><br />
*# I need clarification how should "more semantic equivalents" be interpreted inside values (when they don't have relevant class name, but are inside another parsed element)<br />
*#* <code><nowiki>&lt;span class=&quot;email&quot;&gt;&lt;a href=&quot;mailto:href&quot;&gt;nodetext&lt;/a&gt;&lt;/span&gt;</nowiki></code> &ndash; is it "href", "nodetext" or an error? What if there are multiple links inside?<br />
*#* <code><nowiki>&lt;span class=&quot;fn&quot;&gt;&lt;abbr title=&quot;title&quot;&gt;nodetext&lt;/abbr&gt;&lt;/span&gt;</nowiki></code> &ndash; is it "title" or "nodetext"?<br />
*#* <code><nowiki>&lt;span class=&quot;fn&quot;&gt;&lt;img alt=&quot;alt&quot;&gt;nodetext&lt;/span&gt;</nowiki></code> &ndash; is it "alt", "nodetext" or both?<br />
*#* <code><nowiki>&lt;span class=&quot;fn&quot;&gt;&lt;abbr title=&quot;title&quot;&gt;&lt;span class=&quot;value&quot;&gt;nodetext&lt;/span&gt;&lt;/abbr&gt;&lt;/span&gt;</nowiki></code> &ndash;&nbsp;"title", "nodetext" or both?<br />
*#* <code><nowiki>&lt;span class=&quot;url&quot;&gt;&lt;img src=&quot;src&quot; alt=&quot;alt&quot;&gt;nodetext&lt;/span&gt;</nowiki></code> &ndash; "src", "alt", "nodetext" or "altnodetext"?<br />
*#* <code>&lt;div class=&quot;category&quot;&gt;&lt;a rel=&quot;tag bookmark&quot; href=&quot;href&quot;&gt;nodetext&lt;/a&gt;&lt;/div&gt;</code> – is it a tag? What if there are multiple links inside?<br />
*# Does <code>agent</code> property has to be a hCard?<br />
*#* Is <code>&lt;span class=&quot;agent&quot;&gt;Joe Sixpack&lt;/span&gt;</code> allowed?<br />
*#* Is <code>&lt;span class=&quot;agent&quot;&gt;&lt;div class=&quot;vcard&quot;&gt;&hellip;&lt;/div&gt;&lt;/span&gt;</code> ok?<br />
*#* What about <code>&lt;a class=&quot;agent&quot; href=&quot;card.vcf&quot;&gt;&hellip;&lt;/a&gt;</code>?<br />
*# Is value of <code>&lt;abbr&gt;</code> without <code>title</code> empty or should it be interpreted like <code>&lt;span&gt;</code>?<br />
*# Does <code>&lt;acronym&gt;</code> work like <code>&lt;abbr&gt;</code>?<br />
*# Is this allowed: <code><nowiki>&lt;div class=&quot;photo&quot;&gt;http://example.com/photo.jpg&lt;/div&gt;</nowiki></code>?<br />
*# Is it allowed to use <code><nowiki>http://</nowiki></code> URLs in <code>email</code>? or <code><nowiki>mailto:</nowiki></code> in <code>url</code>?<br />
*# Is it allowed/required to use <code>mailto:</code> when e-mail is in non-<code>&lt;a&gt;</code>, e.g. <code><nowiki>&lt;span class=&quot;email&quot;&gt;mailto:joe@example.com&lt;/span&gt;</nowiki></code><br />
*# If value of a property is empty (<code><nowiki>&lt;span class=&quot;email&quot;&gt;&lt;/span&gt;</nowiki></code>) should it be interpreted as unknown value? ignored completely like it didn't exist? an error?<br />
*# Can hCard contain nested hCard <i>anywhere</i>? or only outside any property or only inside <code>agent</code>?<br />
*# Can <code>organi'''s'''ation-name</code> (note spelling) be interpreted by parsers?<br />
*# Is <code>type</code> class ignored in values anywhere? It is ignored in <code>&lt;div class=&quot;tel&quot;&gt;&lt;span class=&quot;type&quot;&gt;Work&lt;/span&gt; 555&lt;/div&gt;</code>, but is it in <code>&lt;div class=&quot;fn&quot;&gt;&lt;span class=&quot;type&quot;&gt;Work&lt;/span&gt; Joe&lt;/div&gt;</code>?<br />
</div><br />
</div><br />
<br />
== template ==<br />
<br />
{{issues-format}}<br />
<br />
== related pages ==<br />
{{hcard-related-pages}}</nowiki></div>Kornel