Microformats Wiki - User contributions [en]

hcard-issues-resolved

2010-07-20T03:35:52Z

Oli: /* resolved 2010 */ fixing formatting

<entry-title>hCard resolved issues</entry-title>
== resolved issues ==
[[hCard]] issues that are resolved but may have outstanding [[to-do]] items.

As issues are resolved, they will be moved from the [[hcard-issues|Issues list]] to this section.

As actions are taken according to the resolutions noted in the issues, they are moved to [[hcard-issues-closed]].

=== resolved 2005 ===
'''Note: As the resolutions are enacted and the issues are closed, it may be worth moving this year of issues to its own page.'''

* 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?
*#*A: ACCEPTED.
*#** [[to-do]]: add "user agent conformance section" similar to or better than conformance criteria documented in [http://dev.w3.org/html5/mdvcard/ microdata vCard vocabulary].
*#** See [[hcard-parsing]] for how hCards must be parsed.
*#** [[to-do]]: add more deatils to [[hcard-parsing]] on how to handle errors in invalid hCards, unexpected content, or missing content.
*#** [[to-do]]: clarify in [[hcard-parsing]] that is based upon the parse tree (e.g. DOM) of the source document. Provide general parsing details but defer to specific parsing rules of document source (e.g. defer to HTML5 for how to parse an HTML5 document (HTML serialization or XHTML serialization) and produce a DOM tree, which hcard-parsing then uses to extract hCards).
*#** [[to-do]]: add a section to [[hCard]] or a separate normative page (subsection page) that provides additional vCard-format-specific details for converting hCards to vCards (.vcf).

=== resolved 2006 ===
'''Note: As the resolutions are enacted and the issues are closed, it may be worth moving this year of issues to its own page.'''

* 2006-11-15 raised by [http://lachy.id.au/ Lachy] in [irc://freenode/whatwg #whatwg] (an IRC channel on [http://freenode.net/ freenode] about [http://whatwg.org/ The WHATWG]).
*# ''I think the whole [[hcard|hCard]] specification needs to be restructured.''
*#* ACCEPTED. I (the editor, Tantek) have been rewriting the spec accordingly since 2007 June.
*# ''It's incredibly difficult to work out what each class name means and how to use them properly.''
*#* ACCEPTED. Thorough itemized list of class names have been added. Definitions are in the [[hcard-profile]] and how to use (some of) them properly are in [[hcard-authoring]], but should also briefly be in the spec. - Tantek

* 2006-11-15 raised by hsivonen in #whatwg.
*# ''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.''
*#* ACCEPTED. This (and Lachy's 2nd feedback point above) should be addressed by clarifying the mapping with better use of the [[hcard-profile|hCard profile]] which does clearly map the class names to vCard properties and the sections of the vCard specification that defines them, as well as by adding to the itemized list of properties in the spec at least brief definitions that then link to the expanded definitions in the profile. - Tantek

* 2006-11-15 raised by Hixie in #whatwg (and agreed by [http://lachy.id.au/ Lachy] and hsivonen).
*# ''The [[hcard|hCard]] spec basically reads as a brainstorm, not a normative spec.''
*#* ACCEPTED. As editor I will seek to make the hCard spec as normatively written as at least common W3C recommendations, and hopefully to the level of the HTML5 specification. -Tantek

* 2006-11-17 raised by [http://lachy.id.au/ Lachlan Hunt] (I second all of these feedback items. [[User:AndyMabbett|Andy Mabbett]] 07:15, 17 Nov 2006 (PST))
*# Semantic XHTML Design Princples: This section should go. Guidelines for how to write a microformats specification do not belong in the spec itself.
*#* ACCEPTED. I've expanded on the specifics of this section AND moved it to a separate page accordingly [[hcard-design-methodology]].
*# Format - More Semantic Equivalents: Explanations of how to use each property correctly should be given with each and every property, not just list a few at the top before the properties have even been defined.
*#* ACCEPTED. Each property has now been listed explicitly. Brief explanations of each property will be added. -Tantek
*# Singlular vs. Plural: It is unclear what is meant by singular vs. plural properties. Ordinarily, a plural is word that refers to multiple objects, but in this spec, it's being used to designate a property that can be used more than once. It doesn't make sense because the property itself isn't a plural. Besides, this section should go. The number of times a property can be used should be listed with each individual property description.
*#* ACCEPTED PARTIAL. The definition of singular and plural in this context will be expanded to clarify. Listing the number of times a property can be used with the individual property description will be considered, but may be rejected per editor discretion of keeping the spec shorter and simpler. -Tantek
*# Plural Properties Singularized: What the...? After attempting to read that paragraph several times, I still can't comprehend what on earth it's trying to say.
*#* ACCEPTED. This section has been moved to [[hcard#Notes_on_derivation_from_vCard|an informative notes on derivation section]]. -Tantek
*# Human vs. Machine Readable: This title only makes some sense for the use of the abbr element. Everything in this section should be moved to a Conformance Requirements section, which explains how to extract values from the markup. It should also use RFC2119 terminology that describes exactly what a UA has to do. Presently, it's written too informatively, rather than normatively (particularly for the abbr element).
*#* ACCEPTED PARTIAL. Note that the title also makes sense for the use of URL properties in attributes like href and src. A conformance requirements section is a reasonable request, but it may reference the Human vs. Machine Readable section rather than included it for better document flow. Agreed on use of [[RFC2119]] terminology. -Tantek
*# Property List: This section is almost useless, it's effectively written like an index of properties but doesn't link to or help define, in any way whatsoever, what the actual meaning of a property is, nor how to use it. For every single property, all of the following information should be listed
*#* Property name
*#* Expansion (e.g. it's not clear from this section what fn stands for. First Name? Family Name? Full Name? Flight Number?)
*#* Definition. (e.g. either copy the definition directly from vCard or provide a short summary, and also a link to the relevant vCard section. Saying just "See section #.#.# of RFC 2426.", as done in the profile, is not so easy to do.)
*#* Usage
*#** Contexts in which this property may be used
*#** Content model (e.g. list of sub properties, expected elements, text, or whatever)
*#** Syntax of the value (i.e. plain text, number, URI, etc.)
*#** Elements this property may be used on
*#* How to interpret the value (may link to relevant section in Conformance Requirements)
*#* ACCEPTED PARTIAL. Much of this is good feedback on how to improve the property listing. Per some of the above resolutions, editor's discretion will be used to keep the property listing as short and simple as possible for better readability/accessibility. - Tantek

* 2006-11-23 raised by [[User:AndyMabbett|Andy Mabbett]]
*# The specification should be "stand alone", and not normally require reference to the vCard specification.
*#*A: ACCEPTED PARTIAL. Agreed that [[hcard|hCard]] should be usable by typical web authors without having to dig through the vCard specification. Precise implementation of parsing etc. hCard properties however will likely require programmers to reference the specifics/grammars in the vCard specification which we will NOT replicate in the hCard specification in order to avoid inevitable introduction of errors due to duplication. And that being said, ''informative'' explanations may be a good idea, while the vCard property/value definitions are kept as ''normative''.
*#** Yes; my meaning was with reference to hCard publishing, not parsing-into-vCards. [[User:AndyMabbett|Andy Mabbett]]
*# ''The specification should state that "telephone numbers SHOULD adhere to [http://en.wikipedia.org/wiki/E.123 ITU-T Recommendation E.123]" (or perhaps "MUST").''
*#* ACCEPTED PARTIAL. This makes sense as an informative reference and a MAY, but since vCard makes no such SHOULD statement for TEL values, neither should/will hCard. In addition, as a Wikipedia URL that is subject to drastic change, we cannot make that a normative reference.
*#** I take your point about Wikipedia - here's [http://www.itu.int/rec/T-REC-E.123-200102-I/en a more definitive ITU-E.123 URL]; but it's for a chargeable document. Using "SHOULD" or "MUST" in hCard will not affect compatibility with or conversion to vCard. [[User:AndyMabbett|Andy Mabbett]]
*#* ACCEPTED DOCUMENTATION. [[to-do]]. -Tantek

* 2006-11-24 raised by [[User:AndyMabbett|Andy Mabbett]]
*# A suggested work-around for the lack of a gender property is to represent gender implicitly in the honorific-prefix field, e.g. Mr. for male, and Ms. for female. This approach does has the limitation that "Mr." and "Ms." (or "Miss"/ "Mrs.") conflicts with a higher-ranking, gender-neutral honorific, such as "Dr." or "Rev." for the person, as it is unusual (and sometimes, outside the USA, invalid) to refer to someone as "Mr. Dr." or "Mrs. Rev." for example. Note also that some cultures or religions regard such titles as offensive, or at least disdain them.
*#* ACCEPTED FAQ, PROPOSAL. This technique for communicating gender should be documented in the FAQ, along with the limitations noted in this issue, as well as a pointer to the gender proposal in progress. The gender proposal should also point to this existing technique, and note its limitations as additional justification for the proposal. -Tantek

* 2006-12-07 raised by RyanKing.
*# ''hCard org-fn matching should use organization-name, if given.''
*# originally [http://microformats.org/discuss/mail/microformats-discuss/2006-November/007337.html raised on uf-discuss] by David Janes.
*#* ACCEPTED. This is a good suggested clarification. Tantek [[to-do]]: update [[hcard|hCard]] accordingly.

* 2006-12-15 raised ([http://microformats.org/discuss/mail/microformats-discuss/2006-December/007730.html on 2006-12-14, on the mailing list]) by Joe Andrieu.
*# (Paraphrased) By including organisations and places, as well as people, hCards have lost semantic specificity (see cited mailing list post for details).
*#* [http://microformats.org/discuss/mail/microformats-discuss/2007-March/009102.html Apparently intentional], but possibly requiring further extension. [[User:AndyMabbett|Andy Mabbett]]
*#* REJECTED. As there are precise parsing rules for determining [[hcard#Organization_Contact_Info|whether an hCard is an organization]], or [[hcard-brainstorming#Named_locations|whether an hCard is a location]], semantic precision is preserved from the publisher who decides to publish a person, organization, or location, thru to the parser, which determines the semantic specificness of whether the hCard is a person, organization, or place. -Tantek
*#* REOPENED - the latter is a recent proposal, on a brainstorming page, and no more. There is insufficient evidence of use in the wild to be sure whether or not it meets all common publishing bahaviour. [[User:AndyMabbett|Andy Mabbett]] 05:32, 15 Dec 2007 (PST)
*#* ACCEPTED PARTIAL. The organizations vs. people portion remains REJECTED. However, as indicated, the named location proposal needs to be tested with more examples. -Tantek
*#* Consider also an hCard for a City, "Birmingham, England": Birmingham may be the "fn" and the "locality", but it's not an "extended-address". Perhaps the rule should be that the hCard is for a place if the "fn" is on any address component (e.g "fn locality" or "fn street-address")? See discussion at [http://microformats.org/discuss/mail/microformats-discuss/2007-December/011169.html] et seq. [[User:AndyMabbett|Andy Mabbett]] 16:15, 30 Dec 2007 (PST)
*#** If so, the "implied-n-optimisation" rule will need to be modified, to exclude cases where the fn is on the same attribute as an adr-child (which should probably not happen anyway). [[User:AndyMabbett|Andy Mabbett]] 13:59, 2 Jan 2008 (PST)

=== resolved 2007 ===
'''Note: As the resolutions are enacted and the issues are closed, it may be worth moving this year of issues to its own page.'''

* 2007-01-22 raised by [[User:Christina Hope|Christina Hope]].
*# ''What is the easiest way to display an hCard all on one line with spacing. Currently I am using this - but I know that there has to be an easier/ simpler way to do it. Example:''
<pre><nowiki>

Christina Hope& nbsp;& nbsp;& nbsp;
Information Technology& nbsp;& nbsp;& nbsp;
Website Coordinator& nbsp;& nbsp;& nbsp;

 x3408 & nbsp;& nbsp;& nbsp;
<a href="mailto:chope@example.com">chope@example.com</a>
</nowiki></pre>
*#* ACCEPTED FAQ.

:: Try
<pre><nowiki>
Christina Hope
Information Technology
Website Coordinator
<abbr class="tel" title="+44123 456 7890 x 3408"> x3408</abbr>
<a class="email" href="mailto:chope@example.com">chope@example.com</a>
</nowiki></pre>

::Note: apply classes to existing elements; use abbr to give the phone number in full, in international format. Also, use CSS, not non- breaking spaces, for spacing.

::[[User:AndyMabbett|Andy Mabbett]] 08:34, 22 Jan 2007 (PST)

* 2007-01-26 raised by [[User:JamesCraig|JamesCraig]].
*# 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. abbr-design-pattern would suggest using abbr, but 'Casa' is not an abbreviated form of 'home', therefore the currently recommended version (below) is not valid.

<pre><nowiki>

<abbr class="type" title="home">Casa</abbr> (preferido):
+1.415.555.1212

</nowiki></pre>

*#* 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.
*#* REOPENED and clarified (Also removed Accessify reference pulled from [[http://microformats.org/wiki?title=accessibility&oldid=12943 original raising]]).
*#*# 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.
*#*# There are real-world non-English examples in the current Mac OS 10.5 (Leopard) developer seed. This code example illustrates the point sufficiently.
*#*# 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]]
*# To avoid [[i18n]] issues, microformats should keep its hands off content (this also affects [[hReview]]). [[abbr-design-pattern]] doesn't seem the right solution here. Someone from France suggested elsewhere to use the class value '''telwork''', etc. but again it's a dubious solution (remember that a ''tel'' can have a type of ''voice'' and ''work'' '''at the same time'''). I suggest considering:

<pre><nowiki>

Casa (preferido):
+1.415.555.1212

</nowiki></pre>

It could be argued that somehow this solution violates the microformats [[principles|principle of visible data]]. Maybe it does, but [[i18n]] should come first because otherwise microformats violates the first rule: '''solve a specific problem''' (and the last: "enable and encourage decentralized and distributed development, content, services: explicitly encourage the original 'spirit of the Web'"). -[[User:XavierBadosa|Xavier Badosa]]
*#* ACCEPTED SOLVED. The use of <code>abbr</code> and <code>title</code> attribute to provide an alternate language representation rather than an abbreviation expansion falls outside the semantics of <code>abbr</code>. The [[value-class-pattern]] has been devised as a solution to this problem, to avoid the semantic mis-use of abbr for this instance.

* 2007-01-30 raised by [[User:AndyMabbett|Andy Mabbett]]
*# Many sites, not least Wikipedia, publish co-ordinates as degrees-minutes-seconds (e.g. [http://en.wikipedia.org/wiki/Birmingham]). Should [[geo]] be extended to allow for this, with parsers making the conversion to digital values?
*#* ACCEPTED BRAINSTORMING. My first instinct is that if a precise grammar can be defined for the human friendlier d-m-s syntax, and if that precise grammar reflects the 80% of existing real world cases (e.g. Wikipedia as cited), then it should be considered for addition to the [[geo]] property and thus hCard. This may help reduce the number of instances of needing to duplicate the d-m-s value as a decimal value for machines. -Tantek

* 2007-02-02 raised by [[User:DerrickPallas|Derrick Pallas]]
*# [[adr]] says that all of it's properties are singular; however, "street-address" is listed as zero-or-more.
*#* ACCEPTED. This appears to have been fixed in the [[adr]] specification. "street-address" is no longer listed as zero-or-more.

* 2007-02-25 [http://microformats.org/wiki?title=adr&diff=next&oldid=13732 raised elsewhere] by [[User:JamesCraig]]
*#internationalization Note: <code>country-code</code> may be missing. Usually a postal-code prefix such as "FIN-00630 Helsinki" or "L-4750 Petange" (Luxembourg).
*#* ACCEPTED FAQ. This seems like just an FYI/FAQ rather than any real issue. Often country names can be inferred from postal-codes. Also perhaps the country-name can be marked up as an abbr subset of the postal-code in cases like the "FIN" example given. -Tantek

* 2007-03-19 raised by [[User:ChristinaHope|Christina Hope]]
*# ''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?''
*#** 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.)
*#** REJECTED INSUFFICIENT INFORMATION. Perhaps a note can be added to [[vcard-implementations]] with mention of this issue, in case others come across it and can then document it more thoroughly.

* 2007-03-26 raised by [[User:AndyMabbett|Andy Mabbett]]
*#Parsers (Operator, Tails) currently expect <code>adr</code> to have one or more children. It is not clear from the spec that that's mandatory; nor is it always possible for an address field in a templated (or CMS) web site to be defined with such granularity. See [[hcard-brainstorming#ADR with no children]] for discussion.
*#* ACCEPTED. Tantek [[to-do]]: Add more precision to how to handle adr sub-properties (or lack thereof) to [[adr]] and [[hcard]]. In particular, an "adr" without any sub-properties simply provides no information.

* 2007-03-28 raised by [[User:JamesCraig|James Craig]]
*#[[internationalization|Internationalization]] (i18n) issue for implied optimization of FN. Many languages (for example, Japanese) often list FN as "family-name given-name" instead of the assumed "given-name family-name" in English and other Western languages. There should be a affordance to indicate the order ''or'' a note in the spec indicating that the two-word FN is a shorthand for Western languages and any languages not fitting this format should explicitly define "family-name" and "given-name" every time.
*#* ACCEPTED. Tantek [[to-do]]: add internationalization section in [[hcard|hCard]] spec, and note in the spec indicating that the two-word FN is a shorthand for Western languages and any languages not fitting this format should explicitly define "family-name" and "given-name" every time. In particular, the fn implied n optimization should be limited to fn properties which themselves are on elements that are on a whitelist of Western languages that typically publish with "given-name family-name" order, such as "en" (add others as confirmed by i18n experts). fn elements of other languages should not imply this optimization. When the optimization is not implied, then the n property is left as is - if it were otherwise empty, it is left empty.
* 2007-03-31 raised by [[User:AndyMabbett|Andy Mabbett]]
*# 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)
*#* 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)
*#* ACCEPTED BRAINSTORMING. The [[geo-extension-strawman]] should be listed in [[geo-brainstorming]] for consideration in a revision of [[geo]] and the microformats that use it ([[hCard]] and [[hCalendar]]).

* 2007-04-09 raised by [[User:AndyMabbett|Andy Mabbett]]
*#Why is [[geo]] still a draft, when it's included in the already-published [[hcard|hCard]] spec?
*#* ACCEPTED. [[geo]] has been vetted long enough by the community to be raised to the same level as hCard. Tantek [[to-do]]: send an email to microformats-new proposing this.

* 2007-04-19 raised by [[User:AndyMabbett|Andy Mabbett]]
*#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: <code><nowiki><abbr title="1890-02-10">29 January 1890</abbr></nowiki></code>?
*#* ACCEPTED FAQ. The author of the content should specify *at least* an ISO compatible Gregorian date (i.e. using the [http://en.wikipedia.org/wiki/Proleptic_Gregorian_calendar Proleptic Gregorian Calendar] as necessary), e.g. as the Boris Pasternak example does, and mark *that* date up with the <code>bday</code> property: <code><nowiki>"<abbr title="1890-02-10">10 February</abbr> [O.S. January 29] 1890"</nowiki></code> Since the likelihood of error/drift/misunderstanding is greatly increased by two different representations of date with different numbers with one of them being less visible (e.g. in the <code>title</code> attribute), pattern like the suggested <code><nowiki><abbr title="1890-02-10">29 January 1890</abbr></nowiki></code> MUST be '''avoided''' by authors.

* 2007-04-21 raised by [http://www.mnot.net/ Mark Nottingham].
*# Pages often list many addresses in the same locality, but hCard (and adr) are currently structured so that you have to repeat the entire global context for each address. For example, <pre><nowiki>
<h2>Pizza Shops in Burlingame, California</h2>
<ul>
<li>Round Table - 231 Burlingame Avenue</li>
<li>Village Host - 303 Broadway</li>
<li>Pizza Hut - 43423 El Camino Real</li>
</ul>
</nowiki></pre>As specified, there'd be a lot of repeated information here.However, if adr allowed use of locality, region, postcode and country as ancestors of the more specific address tags, it would save a lot of bits -- and help adoption of these microformats in this kind of case (which is quite common).
*#* ACCEPTED FAQ. Use the [[include-pattern]]. [[User:AndyMabbett|Andy Mabbett]] 03:51, 21 Apr 2007 (PDT)

* 2007-04-24 raised by [[User:Singpolyma|singpolyma]]
*# ''What is the 'Label' property for''
*#* ACCEPTED FAQ. Per earlier resolutions, more explanation will be added to the hCard specification, and this question should be added to the [[hcard-faq]].

* 2007-04-27 raised by Sjoerd Mullender
*# There is a proposal for a geo URI scheme [http://www.ietf.org/internet-drafts/draft-mayrhofer-geo-uri-00.txt]. It would be nice if that scheme and the geo hCard type could somehow be combined. It seems to me that if you want to use both and also have a human-readable version, you need three copies of the latitude/longitude: <pre><nowiki>Location: <a href="geo:52.356389,4.952222"><abbr class="latitude" title="52.356389">52°21'23.00" N</abbr> <abbr class="longitude" title="4.952222">4°57'08.00" E</abbr></a></nowiki></pre>
*#* ACCEPTED BRAINSTORMING. This is a very interesting proposal, and clearly it is desirable to minimize the number of copies of the latitude/longitude. Thus this should be added to the [[geo-brainstorming#geo_links|geo brainstorming geo links section]]. -Tantek

* 2007-08-03 raised by [http://www.kaply.com/weblog/ MikeKaply].
*# ''Issue 1: When using the value design pattern, should the data be extracted completely (including HTML tags) or just text content? In general, the value pattern seems to imply taking the data exactly.''
*#* ACCEPTED FAQ. For [[hcard#Value_excerpting|value excerpting]], the parsing is handled as it would be for the property, but just on the element with class name "value" rather than the element with the class name of the property itself. Thus in general just the text content but see [[hcard-parsing]] specific combinations of property and/or element for special cases. It is only the [[include-pattern]] which incorporates the HTML subtree (including tags) in its entirety.

* 2007-11-04 raised by [http://www.tomota.de/ RalfEngels].
*# ''Issue 1: The section Organization Contact Info is exeedingly vague. It says "I must not set the N property" and later on it says that I could set it to an empty value. Which of both is true? Must not or empty?''
*#* ACCEPTED. Tantek [[to-do]]: clarify the spec on this point. Not setting it and setting it to empty have the same effect. Improve the wording.
*# ''Issue 2: Same section. It does not cover e.g. Mr Fischer (N=Fischer) from the Fischer AG (ORG=Fischer). Could you re-formulate it stating that if the N attribute is missing the hcard is regarded as the card of a company.''
*#* REJECTED. If the "n" property is missing, then remaining fn+org or implied fn rules still apply.
*# ''Issue 3: Grouping as specified by rfc2425 and supported by vcard cannot be expressed. Grouping allows you to express the relation between different values.''
*#* REJECTED. hCard only maps the properties and values from vCard, not all features. Grouping in particular is excluded.
*# ''Issue 4: Implied n optimization: the typical case list specifies a (space) in the first and last line. In the middle lines it specifies a (comma). I guess this should mean (comma)(space) instead. In addition it contradicts with the previous text where you state that the separating character is a (whitespace)''
*#* ACCEPTED. Tantek [[to-do]]: clarify the spec on this point. space and whitespace are the same in this context.
*# ''Issue 5: Concatenation of texts is not consistent in the examples. Example file 21 contatinates telephone fields with spaces. Example 16 concatenates multiple name sub-properties by a comma. Example 34 even concatinates multiple note fields.''
*#* ACCEPTED. Tantek [[to-do]]: clarify concatenation handling in [[hcard-parsing]]. [[to-do]]: correct [[hcard-examples]] accordingly.

=== resolved 2008 ===
'''Note: As the resolutions are enacted and the issues are closed, it may be worth moving this year of issues to its own page.'''

* 2008-01-01 raised by [[User:AndyMabbett|Andy Mabbett]] in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011182.html microformats-discuss/2008-January/011182.html]
*# The "n" optimization rules (nickname, fn) should not apply where the fn is on part of adr or label: e.g <code><nowiki>
New York</nowiki></code>; <code><nowiki>Asia</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]])
*#* ACCEPTED BRAINSTORMING. This both makes sense from the point of view of avoiding a shorthand optimization to represent a person in a case where clearly the markup represents a place, and for allowing one possible way to use hCard for named locations.

* 2008-01-09 2008- moved from [[vcard-suggestions]]
*#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">Travail : 0321596224</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 : 0321596224</nowiki> Please, use class and id attributes ONLY for microformats specifications ! XML #cdata and #data are localized ! Thanks !
*#* ACCEPTED ISSUE, REJECTED PROPOSAL. The localization issue is recognized and now addressed by the [[value-class-pattern]]. The proposal for "telwork" is unnecessary, will contribute to vocabulary expansion for every other property that has a work subtype for example, illustrates a vocabulary anti-pattern, and is thus undesirable.

* 2008-01-13 raised by Christopher Allen at OpenIDDevCamp (collected by [[User:Tantek|Tantek]]).
*# 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.
*#* ACCEPTED FAQ EXAMPLES. This is an excellent question, and a good subject to address as an example in [[hcard-authoring]] as well as on a page on [[date-time-authoring]] with perhaps a Q&A pointer from [[hcard-faq]]. For now, see [[value-class-pattern]] and Jakob Nielsen's post on [http://www.useit.com/alertbox/9608.html International Usability] which mentions time zone.

* 2008-02-02 raised by [[User:AndyMabbett|Andy Mabbett]]
*# The "<code>n</code>" optimization 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>
Webmaster</nowiki></code>; <code><nowiki>Duty Manager</nowiki></code>, since, in these examples, "Webmaster" is not a nickname, "Duty" is not a given-name and "Manager" is not a family-name.
*#* ACCEPTED BRAINSTORMING. This makes sense from the point of view of avoiding a shorthand optimization to represent a specific person's nickname or given/family names in a case where clearly the markup represents a generic person. In both examples given, it may be better to define the n property as having an implied empty value, while the fn has the explicitly marked up value.

* 2008-02-06 raised by [[User:Guillaume Lebleu| Guillaume Lebleu]]
*# 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.
*#* REJECTED MISCONCEPTION, MARKUP ERROR. ACCEPTED FAQs. 1. The scope that vCard provides is that of "person" or "organization", combined with that with the FN meaning of "formatted name" results in the meaning of "formatted name of a person or organization" (e.g. "person name" as stated). FN by itself does not have the scope of person or organization. The page given, http://cinematreasures.org/theater/365/, erroneously uses an empty fn, when they should be marking up the following markup: <code><nowiki><a href="/theater/365/">Hornbeck & Penthouse Theatre</a></nowiki></code> with fn org url uid for property hCard semantics: <code><nowiki><a class="fn org url uid" href="/theater/365/">Hornbeck & Penthouse Theatre</a></nowiki></code>. This example should be added to [[hcard-examples-in-wild]], along with this noted correction in markup.

* 2008-02-07[[User:AndyMabbett|Andy Mabbett]]
*# The "<code>fn</code>" optimization rule should not apply where the full <code>fn</code> is also the <code>nickname</code>: e.g <code><nowiki>Plastic Bertram</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)"?)
*#* ACCEPTED BRAINSTORMING AND FAQ. This makes sense from the point of view of avoiding a shorthand optimization to represent a person's given/family names in a case where clearly the markup represents their nickname. The given pseudonym could perhaps be marked up as: <code><nowiki>Maurice Micklewhite (known professionally as Michael Caine)"?)</nowiki></code>, however, without additional context of where that example is used, it's not clear that that's the best markup possible for the text.

* 2008-02-07 raised by [[User:AndyMabbett|Andy Mabbett]] in [http://microformats.org/discuss/mail/microformats-discuss/2008-February/011552.html microformats-discuss/2008-February/011552.html]
*# Is "n" optional or mandatory? The spec says yes (with exceptions) the cheat-sheet says no. Parsers and common practice seem to indicate not.
*#* ACCEPTED FAQ. The "n" property is required, but that requirement may be met by satisfying one of the n property optimizations/shorthands. Thus parsers and common practice, by implementing those optimization/shorthands are still indicating the "n" property requirement.

* 2008-02-08 raised by [[User:Guillaume Lebleu| Guillaume Lebleu]]
*# 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]
*#* ACCEPTED BRAINSTORMING. Because of this and other mentions of challenges of using hCard (and other microformats) in semantic HTML Tables, as well as the observation that fewer levels of hierarchy makes microformats easier to understand, a proposal is being considered to promote subproperties of a singular property to being properties themselves, e.g. the <code>n</code> subproperties (<code>given-name</code>, </code>family-name</code>, etc.), and in the case of non-singular properties with subproperties (e.g. <code>adr</code>), allowing the use of such subproperties (e.g. <code>street-address</code>, <code>locality</code>, <code>region</code>, etc.) with a single default/implied <code>adr</code> property container instance for the hCard.

* 2008-06-01 raised by [[User:Kornel|Kornel]]
*# 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)
*#* <code><nowiki><a href="mailto:href">nodetext</a></nowiki></code> – is it "href", "nodetext" or an error? What if there are multiple links inside?
*#** Parsed as "nodetext" [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#* <code><nowiki><abbr title="title">nodetext</abbr></nowiki></code> – is it "title" or "nodetext"?
*#** Parsed as "nodetext" [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#* <code><nowiki><img alt="alt">nodetext</nowiki></code> – is it "alt", "nodetext" or both?
*#** Per [[hcard-parsing]], since the "fn" property is a text/string property, in this example it should be parsed as "nodetext" [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC).
*#** A matter of debate recently. Some parsers as "nodetext", others as "altnodetext". [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#*** What parsers produce "altnodetext"? Please add them to [[hcard-implementations]] and per [[hcard-parsing]] note that those parsers are buggy since the fn property should be parsed as "nodetext" in this example. [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC)
*#* <code><nowiki><abbr title="title">nodetext</abbr></nowiki></code> – "title", "nodetext" or both?
*#** Parsed as "nodetext" [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#* <code><nowiki><img src="src" alt="alt">nodetext</nowiki></code> – "src", "alt", "nodetext" or "altnodetext"?
*#** Per [[hcard-parsing]] in this example it should be parsed as "nodetext" [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC).
*#** A matter of debate recently. Some parsers as "nodetext", others as "altnodetext". [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#*** What parsers produce "altnodetext"? Please add them to [[hcard-implementations]] and per [[hcard-parsing]] note that those parsers are buggy it should be parsed as "nodetext" in this example. [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC)
*#* <code><div class="category"><a rel="tag bookmark" href="href">nodetext</a></div></code> – is it a tag? What if there are multiple links inside?
*#** 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)
*#** As Toby indicates, that example would likely generate two "category" values for the hCard, "href" (or the last segment of the href, if "href" was not intended as a literal), and "nodetext". I say "likely" because if those two happened to be the same, only one <code>category</code> value would be generated.
*#* '''ACCEPTED FAQ.''' Lots of questions here that are answered by [[hcard-parsing]] but could also be listed in [[hcard-parsing-faq]] for hopefully easier discovery. In addition, each example presented would make a good test case.
*# Does <code>agent</code> property have to be an hCard?
*#* Is <code>Joe Sixpack</code> allowed?
*#** Yes. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#* Is <code>…</code> ok?
*#** [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><div class="agent vcard">…</div></code>. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#** As Toby says, it is "ok" in that it is valid, but the agent relationship is not established by that example. Toby's change to the example to use <code>class="agent vcard"</code> fixes it to have the intended effect. [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC)
*#* What about <code><a class="agent" href="card.vcf">…</a></code>?
*#** 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)
*#** No. The example given will be parsed as "…" for the <code>agent</code>. [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC)
*# Is value of <code><abbr></code> without <code>title</code> empty or should it be interpreted like <code></code>?
*#* I think consensus is that the node text should be used. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#* More than consensus, per the [[hcard-parsing#all_properties|hCard parsing spec]]: "<code><abbr title></code>: use the value of the 'title' attribute. If there is no 'title' attribute then use the contents of the element." [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC)
*#* '''ACCEPTED FAQ.''' Lots of questions here that are answered by [[hcard-parsing]] but could also be listed in [[hcard-parsing-faq]] for hopefully easier discovery. In addition, each example presented would make a good test case.
*# Does <code><acronym></code> work like <code><abbr></code>?
*#* Not as per spec, but some parsers do treat it like <code><abbr></code>. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#** Which parsers? Please list them and note their extra support of <code><acronym></code> on the [[hcard-implementations]] page.
*#* '''ACCEPTED FAQ and BRAINSTORMING.''' <code><acronym></code> is not currently handled in any special way per [[hcard-parsing]]. If you (or anyone) thinks that <code><acronym></code> should be handled like <code><abbr></code>, please add it as a proposal to [[hcard-brainstorming]]. [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC)
*# Is this allowed: <code><nowiki><div class="photo">http://example.com/photo.jpg</div></nowiki></code>?
*#* It is allowed and will parse the URL as the photo property per step 3 of [[hcard-parsing#parsing_hCard_properties_and_values|hCard parsing properties and values]]. [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC)
*#* 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)
*#** Which "naive" parsers? Please list them on [[hcard-implementations]] and note what problems they supposedly have with this example.
*#* '''ACCEPTED FAQ.''' Lots of questions here that are answered by [[hcard-parsing]] but could also be listed in [[hcard-parsing-faq]] for hopefully easier discovery. In addition, each example presented would make a good test case.
*# 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>?
*#* 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)
*#* Yes both are allowed but there is insufficient detail in the example(s) given to understand what utility they would have. [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC)
*#* '''ACCEPTED FAQ.''' Lots of questions here that are answered by [[hcard-parsing]] but could also be listed in [[hcard-parsing-faq]] for hopefully easier discovery. In addition, each example presented would make a good test case.
*# Is it allowed/required to use <code>mailto:</code> when e-mail is in non-<code><a></code>, e.g. <code><nowiki>mailto:joe@example.com</nowiki></code>
*#* Yes, but for copy-and-pasteability I'd recommend leaving out the "mailto:" prefix. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#* '''ACCEPTED FAQ and BRAINSTORMING.''' Yes it is allowed per step 3 of [[hcard-parsing#parsing_hCard_properties_and_values|hCard parsing properties and values]]. However the "mailto:" prefix is currently only removed when specifying the <code>email</code> property on <code>a</code> or <code>area</code> elements per [[hcard-parsing#email_property|hCard parsing - email property]]. Thus this should both be clarified in [[hcard-authoring]], that is, Toby's suggestion to leave otu the "mailto:" prefix in user visible text of the email property, and be clarified in [[hcard-parsing]], that is, that a "mailto:" prefix should be removed from the <code>email</code> property regardless of what HTML element is used for the <code>email</code> property.
*# If value of a property is empty (<code><nowiki></nowiki></code>) should it be interpreted as unknown value? ignored completely like it didn't exist? an error?
*#* '''ACCEPTED FAQ.''' Yes it is allowed and per step 3 of [[hcard-parsing#parsing_hCard_properties_and_values|hCard parsing properties and values]] will result in an empty value.
*# Can hCard contain nested hCard anywhere? or only outside any property or only inside <code>agent</code>?
*#* Yes, though naive parsers may have problems. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#* '''ACCEPTED FAQ.''' Yes a nested hCard is allowed anywhere inside an hCard, however, note that any property inside the nested hCard will not be seen as part of the container hCard per [[hcard-parsing#nested_hCards|hCard parsing - nested hCards]]. A nested hCard on the <code>agent</code> property provides structured details on an agent of the containing hCard, and a nested hCard on the <code>org</code> property provides structured details on an org of the containing hCard.
*# Can <code>organi'''s'''ation-name</code> (note spelling) be interpreted by parsers?
*#* It should not. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#* '''ACCEPTED FAQ.''' No. See [[en-us-faq#why_not_create_multiple_aliases_for_properties_in_other_spellings_and_languages|en-US FAQ: why not create aliases for properties in other spellings and languages.]].
*# Is <code>type</code> class ignored in values anywhere? It is ignored in <code><div class="tel">Work 555</div></code>, but is it in <code><div class="fn">Work Joe</div></code>?
*#* 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)
*#* '''ACCEPTED FAQ.''' Indeed, any markup that is not specified to do anything should be ignored by parsers - this is a "MUST IGNORE" aspect of the forwards/backwards compatibility design of microformats. Lots of questions here that are answered by [[hcard-parsing]] but could also be listed in [[hcard-parsing-faq]] for hopefully easier discovery. In addition, each example presented would make a good test case.

* 2008-06-15 raised by [[User:Kornel|Kornel]]
*# [[RFC2426]] 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?
*#* I raised this very issue on the mailing list about a month ago, but received no responses. Given that hCard claims to be a "a 1:1 representation of vCard (RFC2426) properties and values in semantic HTML or XHTML" (direct quote from [[hcard|spec]]), I think it's reasonable to infer that these types *are* allowed, but simply undocumented so far. I'll be including support for them in the next alpha of Cognition. [[User:TobyInk|TobyInk]] 23:59, 15 Jun 2008 (PDT)
*#* '''ACCEPTED.''' Indeed this is an unintentional omission from the [[hCard]] specification. In the [[hcard#Property_List|hCard list of properties]], the entry for "label" should be changed to "label (type, value)" and the section on [[hcard#adr_tel_email_types|adr tel email types]] should be renamed to "adr email label tel types" and a list item should be added as follows: "* label type: INTL, POSTAL, PARCEL, WORK, dom, home, pref".

* 2008-06-16 raised by [[User:Kornel|Kornel]]
*# In the rfc2426 the KEY property defaults to binary. hCard profile suggests to use <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 <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.
*#* ACCEPTED FAQ EXAMPLES. How to author a "key" property value should be better addressed as indicated, in both [[hcard-examples]] and [[hcard-authoring]] with perhaps a Q&A pointer from [[hcard-faq]].

* 2008-12-11 raised by [[User:mephtu|mephtu]]
* I am concerned that hCard usage will foster widespread abuse of personal datamining by scrapers/spammers, as a standard markup of personal information formalizes the structure of such information which until now has been loosely encoded as formatting markup (e.g. HTML).
** The nice thing about microformats is that you are not required to publish everything. If you are not comfortable publishing your email, address, phone or other information, then you don't have to. If you are already publishing it on the web, then by adding microformats you are disambiguating a plain string of text and a string as meaning your name. [[User:Brian|Brian]] 08:56, 12 Dec 2008 (UTC)
*** That is true, but it does more tightly associate e-mail addresses with other information. Spammers could use this to tie an e-mail address to other personal/contact details and make their messages less spammy in an attempt to fool filters. For example, some filters will raise the spam score of a message if the "To" field contains just an e-mail address, and not the recipient's name - hCard provides spammers with a fairly reliable way of finding out that name. I don't think this is a ''huge'' concern, but it is a slight concern which shouldn't be entirely dismissed. [[User:TobyInk|TobyInk]] 16:37, 12 December 2008 (UTC)
*** ACCEPTED FAQ. There is already [[faq#Microformats_and_Spam|a general microformats FAQ on SPAM]] and this should be either added to that or perhaps specifically to [[hcard-faq]].

* 2008-12-16 raised by [[User:TobyInk|TobyInk]]
*# '''n''' is listed as a required property. Sometimes this is implicit from the '''fn''', and that's fine. However, when <code><nowiki>Foo</nowiki></code> is found, "Foo" is implicitly a nickname, so the hCard still has no '''n''' property — does such an hCard still need an explicit '''n''' added?
*#* ACCEPTED FAQ. The conclusion that "the hCard still has no '''n''' property" is incorrect. The hCard has an "n" property, it is just empty. This should be noted explicitly in [[hcard-parsing]] or perhaps [[hcard-parsing-faq]].

=== resolved 2009 ===
<div class="hentry">
{{ResolvedIssue}} 2009-218 raised by [[User:Singpolyma|Singpolyma]]
<div class="entry-content discussion issues">
* Format for key. What format should be used for key? I suggest the following:<pre><nowiki><a class="key" type="application/pgp-keys" href="https://path.to/key">My PGP Key</a></nowiki></pre>With MIME type obviously changed based on type of key.
** RESOLVED ACCEPTED FAQ EXAMPLES. This seems reasonable to me, and we should update [[hcard-examples]] and [[hcard-faq]] accordingly. Thanks for the suggestion. [[User:Tantek|Tantek]] 02:57, 26 August 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ResolvedIssue}} 2009-09-10 raised by [[User:TomMorris|TomMorris]]
<div class="entry-content discussion issues">
* Parsing UTF-8 'special' space characters in telephone fields. I recently designed a page that used an hCard with a <code>span</code> containing the <samp>tel</samp> value. To space the phone number appropriately, I used the U+8201 (THIN SPACE) character <code>&#8201;</code>. [[operator|Operator's]] hCard parser coughed up on this and refused to read both the contents of the <samp>tel</samp> <code>span</code> but also an <code>a</code> element containing the <samp>email</samp> property that was contained in the parent <code>p</code> element. I cannot find a clear definition of what is acceptable content for the <samp>tel</samp> property. There seems to be two ways of resolving this: (1) instruct authors of microformat parsing libraries to normalise the Unicode characters U+8194 (EN SPACE), U+8195 (EM SPACE), U+8196 (THREE-PER-EM SPACE), U+8197 (FOUR-PER-EM SPACE), U+8198 (SIX-PER-EM SPACE), U+8199 (FIGURE SPACE), U+8200 (PUNCTUATION SPACE), U+8201 (THIN SPACE), U+8202 (HAIR SPACE), U+8203 (ZERO WIDTH SPACE) and other similar characters (including the HTML entities <code>&ensp;</code>, <code>&emsp;</code>, <code>&thinsp;</code> and <code>&nbsp;</code>) so that, for the purpose of parsing the microformat they are treated as a standard space (U+0020) or (2) instructing microformat authors to not use any other space character than U+0020 (and to use the [http://www.w3.org/TR/CSS21/text.html#spacing-props CSS <code>word-spacing</code> property] for manipulating <samp>tel</samp> properties). Which of these is best? Anyone want to survey the current implementations to see how they currently parse telephone numbers with unexpected characters in them? Part of the problem may be that there doesn't seem to be any clear specification of what a valid telephone number is, so far as I can see—which is just from reading [http://www.ietf.org/rfc/rfc2426.txt RFC 2426] §3.3, which says that it should simply be the telephone format defined in X.500 ([http://www.ietf.org/rfc/rfc1274.txt RFC 1274]), but there is no explicit definition in X.500 except to say it is "telephoneNumberSyntax", which is defined in [http://www.ietf.org/rfc/rfc1778.txt RFC 1778] §2.16 as simply being a printable string. Perhaps I've gone off down a blind alley! (Do we need a page for character encoding/Unicode issues?)
** ACCEPTED FAQ, parsing. [[microformats]] depend on the character parsing of the language they are in. In this case, let's for example see what HTML4 and HTML5 say, and advise accordingly in [[hcard-faq]] and [[hcard-parsing]]. [[User:Tantek|Tantek]] 08:56, 9 October 2009 (UTC)
</div>
</div>

=== resolved 2010 ===

<div class="hentry">
{{ResolvedIssue}} 2010-02-03 raised by [http://foolip.org/ Philip Jägenstedt]
<div class="entry-content discussion issues">
* Implied "n" Optimization. The [[hcard#Implied_.22n.22_Optimization|hCard spec]] and the derived [http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html#conversion-to-vcard microdata vCard spec] has some magic intended to derive N from FN when it is not given explicitly, as N is required by the vCard spec. The guessing employed will fail for at least Vietnamese names (e.g. Phương Thanh => N:Thanh;Phương;;;), Chinese names (e.g. 冯小刚 => N:;冯小刚;; and Feng Xiaogang => N:Xiaogang;Feng;;;) and Japanese/Korean names for the same reasons. The problem is both that family-name and given-name are reversed and that Chinese is written without space, so the whole name is interpreted as family name. If the only issue is that N is mandatory, simply outputting N:;;;; seems the safest. Although it's technically possible to add markup to avoid the guessing, that's not going to be an option when microdata/microformats are used in a template and the user isn't asked for both the full name and all of its components. This issue was previously raised on [http://microformats.org/discuss/mail/microformats-discuss/2010-February/013187.html microformats-discuss].
** RESOLVED PARTIAL DUPLICATE. This is mostly a duplicate of [[hcard-issues-resolved#fn-opt-i18n|previous issue raised by James Craig 2007-03-28]], however, the additional information is appreciated. This documentation of the issue contains several points useful to a refined resolution. [[User:Tantek|Tantek]] 00:22, 16 April 2010 (UTC)
*** MUST NOT apply FN to implied N optimization when lang is Vietnamese (need lang code), Chinese (need lang code(s)), Japanese ("ja"), or Korean (need lang code).
*** For hCard to vCard converters: If an hCard lacks an 'n' property (either explicit or implied), when producing the equivalent vCard, output an empty N "N:;;;;" property in order to satisfy vCard's requirement that an N property be specified.
** '''Further information''' Hey Tantek, this assumes that the page has lang declared. That just isn’t common in Japan, and I guess in the other countries mentioned, given the monolingualism. I did some quick research for you, using the first 10 search results for Nakamura (a common Japanese family name) in kanji:
*** http://search.yahoo.co.jp/search?p=%中村&ei=UTF-8&fr=top_ga1_sa&x=wrt
**** 303,000,000 results
**** http://ja.wikipedia.org/wiki/中村 yes
**** http://www.nakamura.ed.jp/ no
**** http://shunsuke.com/ yes
**** http://ja.wikipedia.org/wiki/中村紀洋 yes
**** http://www.mypixel.co.jp/kabuki/nakamura/ no
**** http://www.nakamuraya.co.jp/index.html no
**** http://www.nakamura-net21.co.jp/ no
**** http://www.eriko-nakamura.com/index.html no
**** http://ataru-atariya.com/ yes
**** http://baseball.yahoo.co.jp/npb/player?id=12101 yes
**** 5 out of 10
*** http://www.google.co.jp/search?hl=en&source=hp&q=中村
**** 28,700,000 results
**** http://www.nakamura.ed.jp/ no
**** http://ja.wikipedia.org/wiki/中村 yes
**** http://ja.wikipedia.org/wiki/中村俊輔 yes
**** http://nakamura-japan.net/ no
**** http://shunsuke.com/ yes
**** http://www.nakamura-udon.jp/ no (not even encoding!)
**** http://www.city.nakamura.kochi.jp/topj.html yes
**** http://www.nakamura-u.ac.jp/ yes
**** http://dailynews.yahoo.co.jp/fc/sports/shunsuke/ no (!)
**** http://nakamurajapan.blog17.fc2.com/ yes
**** 6 out of 10
*** I’d like to note these are the highest ranked pages for a very popular search term, and include universities, schools and soccer star (well in Japan ;-) Shunsuke Nakamura’s homepage. There’s even a yahoo.co.jp site without lang="ja". I guess you can imagine the long tail :/ If you need Japanese examples or further info, please let me know. Also, check the hCards for http://twitter.com/boblet/following for examples of Philip’s comment about template/social media sites. Ignoring the current invalid stuff, you can see my friend Channy’s vcard is wrong.
</div>
</div>

== see also ==
* [[hcard-issues]]
* [[hcard-issues-closed]]

hcard-issues-resolved

2010-07-20T03:32:43Z

Oli: /* resolved 2010 */ adding extra information re: the 18n problem with implied n optimisation (hope this is the right place for it)

<entry-title>hCard resolved issues</entry-title>
== resolved issues ==
[[hCard]] issues that are resolved but may have outstanding [[to-do]] items.

As issues are resolved, they will be moved from the [[hcard-issues|Issues list]] to this section.

As actions are taken according to the resolutions noted in the issues, they are moved to [[hcard-issues-closed]].

=== resolved 2005 ===
'''Note: As the resolutions are enacted and the issues are closed, it may be worth moving this year of issues to its own page.'''

* 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?
*#*A: ACCEPTED.
*#** [[to-do]]: add "user agent conformance section" similar to or better than conformance criteria documented in [http://dev.w3.org/html5/mdvcard/ microdata vCard vocabulary].
*#** See [[hcard-parsing]] for how hCards must be parsed.
*#** [[to-do]]: add more deatils to [[hcard-parsing]] on how to handle errors in invalid hCards, unexpected content, or missing content.
*#** [[to-do]]: clarify in [[hcard-parsing]] that is based upon the parse tree (e.g. DOM) of the source document. Provide general parsing details but defer to specific parsing rules of document source (e.g. defer to HTML5 for how to parse an HTML5 document (HTML serialization or XHTML serialization) and produce a DOM tree, which hcard-parsing then uses to extract hCards).
*#** [[to-do]]: add a section to [[hCard]] or a separate normative page (subsection page) that provides additional vCard-format-specific details for converting hCards to vCards (.vcf).

=== resolved 2006 ===
'''Note: As the resolutions are enacted and the issues are closed, it may be worth moving this year of issues to its own page.'''

* 2006-11-15 raised by [http://lachy.id.au/ Lachy] in [irc://freenode/whatwg #whatwg] (an IRC channel on [http://freenode.net/ freenode] about [http://whatwg.org/ The WHATWG]).
*# ''I think the whole [[hcard|hCard]] specification needs to be restructured.''
*#* ACCEPTED. I (the editor, Tantek) have been rewriting the spec accordingly since 2007 June.
*# ''It's incredibly difficult to work out what each class name means and how to use them properly.''
*#* ACCEPTED. Thorough itemized list of class names have been added. Definitions are in the [[hcard-profile]] and how to use (some of) them properly are in [[hcard-authoring]], but should also briefly be in the spec. - Tantek

* 2006-11-15 raised by hsivonen in #whatwg.
*# ''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.''
*#* ACCEPTED. This (and Lachy's 2nd feedback point above) should be addressed by clarifying the mapping with better use of the [[hcard-profile|hCard profile]] which does clearly map the class names to vCard properties and the sections of the vCard specification that defines them, as well as by adding to the itemized list of properties in the spec at least brief definitions that then link to the expanded definitions in the profile. - Tantek

* 2006-11-15 raised by Hixie in #whatwg (and agreed by [http://lachy.id.au/ Lachy] and hsivonen).
*# ''The [[hcard|hCard]] spec basically reads as a brainstorm, not a normative spec.''
*#* ACCEPTED. As editor I will seek to make the hCard spec as normatively written as at least common W3C recommendations, and hopefully to the level of the HTML5 specification. -Tantek

* 2006-11-17 raised by [http://lachy.id.au/ Lachlan Hunt] (I second all of these feedback items. [[User:AndyMabbett|Andy Mabbett]] 07:15, 17 Nov 2006 (PST))
*# Semantic XHTML Design Princples: This section should go. Guidelines for how to write a microformats specification do not belong in the spec itself.
*#* ACCEPTED. I've expanded on the specifics of this section AND moved it to a separate page accordingly [[hcard-design-methodology]].
*# Format - More Semantic Equivalents: Explanations of how to use each property correctly should be given with each and every property, not just list a few at the top before the properties have even been defined.
*#* ACCEPTED. Each property has now been listed explicitly. Brief explanations of each property will be added. -Tantek
*# Singlular vs. Plural: It is unclear what is meant by singular vs. plural properties. Ordinarily, a plural is word that refers to multiple objects, but in this spec, it's being used to designate a property that can be used more than once. It doesn't make sense because the property itself isn't a plural. Besides, this section should go. The number of times a property can be used should be listed with each individual property description.
*#* ACCEPTED PARTIAL. The definition of singular and plural in this context will be expanded to clarify. Listing the number of times a property can be used with the individual property description will be considered, but may be rejected per editor discretion of keeping the spec shorter and simpler. -Tantek
*# Plural Properties Singularized: What the...? After attempting to read that paragraph several times, I still can't comprehend what on earth it's trying to say.
*#* ACCEPTED. This section has been moved to [[hcard#Notes_on_derivation_from_vCard|an informative notes on derivation section]]. -Tantek
*# Human vs. Machine Readable: This title only makes some sense for the use of the abbr element. Everything in this section should be moved to a Conformance Requirements section, which explains how to extract values from the markup. It should also use RFC2119 terminology that describes exactly what a UA has to do. Presently, it's written too informatively, rather than normatively (particularly for the abbr element).
*#* ACCEPTED PARTIAL. Note that the title also makes sense for the use of URL properties in attributes like href and src. A conformance requirements section is a reasonable request, but it may reference the Human vs. Machine Readable section rather than included it for better document flow. Agreed on use of [[RFC2119]] terminology. -Tantek
*# Property List: This section is almost useless, it's effectively written like an index of properties but doesn't link to or help define, in any way whatsoever, what the actual meaning of a property is, nor how to use it. For every single property, all of the following information should be listed
*#* Property name
*#* Expansion (e.g. it's not clear from this section what fn stands for. First Name? Family Name? Full Name? Flight Number?)
*#* Definition. (e.g. either copy the definition directly from vCard or provide a short summary, and also a link to the relevant vCard section. Saying just "See section #.#.# of RFC 2426.", as done in the profile, is not so easy to do.)
*#* Usage
*#** Contexts in which this property may be used
*#** Content model (e.g. list of sub properties, expected elements, text, or whatever)
*#** Syntax of the value (i.e. plain text, number, URI, etc.)
*#** Elements this property may be used on
*#* How to interpret the value (may link to relevant section in Conformance Requirements)
*#* ACCEPTED PARTIAL. Much of this is good feedback on how to improve the property listing. Per some of the above resolutions, editor's discretion will be used to keep the property listing as short and simple as possible for better readability/accessibility. - Tantek

* 2006-11-23 raised by [[User:AndyMabbett|Andy Mabbett]]
*# The specification should be "stand alone", and not normally require reference to the vCard specification.
*#*A: ACCEPTED PARTIAL. Agreed that [[hcard|hCard]] should be usable by typical web authors without having to dig through the vCard specification. Precise implementation of parsing etc. hCard properties however will likely require programmers to reference the specifics/grammars in the vCard specification which we will NOT replicate in the hCard specification in order to avoid inevitable introduction of errors due to duplication. And that being said, ''informative'' explanations may be a good idea, while the vCard property/value definitions are kept as ''normative''.
*#** Yes; my meaning was with reference to hCard publishing, not parsing-into-vCards. [[User:AndyMabbett|Andy Mabbett]]
*# ''The specification should state that "telephone numbers SHOULD adhere to [http://en.wikipedia.org/wiki/E.123 ITU-T Recommendation E.123]" (or perhaps "MUST").''
*#* ACCEPTED PARTIAL. This makes sense as an informative reference and a MAY, but since vCard makes no such SHOULD statement for TEL values, neither should/will hCard. In addition, as a Wikipedia URL that is subject to drastic change, we cannot make that a normative reference.
*#** I take your point about Wikipedia - here's [http://www.itu.int/rec/T-REC-E.123-200102-I/en a more definitive ITU-E.123 URL]; but it's for a chargeable document. Using "SHOULD" or "MUST" in hCard will not affect compatibility with or conversion to vCard. [[User:AndyMabbett|Andy Mabbett]]
*#* ACCEPTED DOCUMENTATION. [[to-do]]. -Tantek

* 2006-11-24 raised by [[User:AndyMabbett|Andy Mabbett]]
*# A suggested work-around for the lack of a gender property is to represent gender implicitly in the honorific-prefix field, e.g. Mr. for male, and Ms. for female. This approach does has the limitation that "Mr." and "Ms." (or "Miss"/ "Mrs.") conflicts with a higher-ranking, gender-neutral honorific, such as "Dr." or "Rev." for the person, as it is unusual (and sometimes, outside the USA, invalid) to refer to someone as "Mr. Dr." or "Mrs. Rev." for example. Note also that some cultures or religions regard such titles as offensive, or at least disdain them.
*#* ACCEPTED FAQ, PROPOSAL. This technique for communicating gender should be documented in the FAQ, along with the limitations noted in this issue, as well as a pointer to the gender proposal in progress. The gender proposal should also point to this existing technique, and note its limitations as additional justification for the proposal. -Tantek

* 2006-12-07 raised by RyanKing.
*# ''hCard org-fn matching should use organization-name, if given.''
*# originally [http://microformats.org/discuss/mail/microformats-discuss/2006-November/007337.html raised on uf-discuss] by David Janes.
*#* ACCEPTED. This is a good suggested clarification. Tantek [[to-do]]: update [[hcard|hCard]] accordingly.

* 2006-12-15 raised ([http://microformats.org/discuss/mail/microformats-discuss/2006-December/007730.html on 2006-12-14, on the mailing list]) by Joe Andrieu.
*# (Paraphrased) By including organisations and places, as well as people, hCards have lost semantic specificity (see cited mailing list post for details).
*#* [http://microformats.org/discuss/mail/microformats-discuss/2007-March/009102.html Apparently intentional], but possibly requiring further extension. [[User:AndyMabbett|Andy Mabbett]]
*#* REJECTED. As there are precise parsing rules for determining [[hcard#Organization_Contact_Info|whether an hCard is an organization]], or [[hcard-brainstorming#Named_locations|whether an hCard is a location]], semantic precision is preserved from the publisher who decides to publish a person, organization, or location, thru to the parser, which determines the semantic specificness of whether the hCard is a person, organization, or place. -Tantek
*#* REOPENED - the latter is a recent proposal, on a brainstorming page, and no more. There is insufficient evidence of use in the wild to be sure whether or not it meets all common publishing bahaviour. [[User:AndyMabbett|Andy Mabbett]] 05:32, 15 Dec 2007 (PST)
*#* ACCEPTED PARTIAL. The organizations vs. people portion remains REJECTED. However, as indicated, the named location proposal needs to be tested with more examples. -Tantek
*#* Consider also an hCard for a City, "Birmingham, England": Birmingham may be the "fn" and the "locality", but it's not an "extended-address". Perhaps the rule should be that the hCard is for a place if the "fn" is on any address component (e.g "fn locality" or "fn street-address")? See discussion at [http://microformats.org/discuss/mail/microformats-discuss/2007-December/011169.html] et seq. [[User:AndyMabbett|Andy Mabbett]] 16:15, 30 Dec 2007 (PST)
*#** If so, the "implied-n-optimisation" rule will need to be modified, to exclude cases where the fn is on the same attribute as an adr-child (which should probably not happen anyway). [[User:AndyMabbett|Andy Mabbett]] 13:59, 2 Jan 2008 (PST)

=== resolved 2007 ===
'''Note: As the resolutions are enacted and the issues are closed, it may be worth moving this year of issues to its own page.'''

* 2007-01-22 raised by [[User:Christina Hope|Christina Hope]].
*# ''What is the easiest way to display an hCard all on one line with spacing. Currently I am using this - but I know that there has to be an easier/ simpler way to do it. Example:''
<pre><nowiki>

Christina Hope& nbsp;& nbsp;& nbsp;
Information Technology& nbsp;& nbsp;& nbsp;
Website Coordinator& nbsp;& nbsp;& nbsp;

 x3408 & nbsp;& nbsp;& nbsp;
<a href="mailto:chope@example.com">chope@example.com</a>
</nowiki></pre>
*#* ACCEPTED FAQ.

:: Try
<pre><nowiki>
Christina Hope
Information Technology
Website Coordinator
<abbr class="tel" title="+44123 456 7890 x 3408"> x3408</abbr>
<a class="email" href="mailto:chope@example.com">chope@example.com</a>
</nowiki></pre>

::Note: apply classes to existing elements; use abbr to give the phone number in full, in international format. Also, use CSS, not non- breaking spaces, for spacing.

::[[User:AndyMabbett|Andy Mabbett]] 08:34, 22 Jan 2007 (PST)

* 2007-01-26 raised by [[User:JamesCraig|JamesCraig]].
*# 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. abbr-design-pattern would suggest using abbr, but 'Casa' is not an abbreviated form of 'home', therefore the currently recommended version (below) is not valid.

<pre><nowiki>

<abbr class="type" title="home">Casa</abbr> (preferido):
+1.415.555.1212

</nowiki></pre>

*#* 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.
*#* REOPENED and clarified (Also removed Accessify reference pulled from [[http://microformats.org/wiki?title=accessibility&oldid=12943 original raising]]).
*#*# 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.
*#*# There are real-world non-English examples in the current Mac OS 10.5 (Leopard) developer seed. This code example illustrates the point sufficiently.
*#*# 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]]
*# To avoid [[i18n]] issues, microformats should keep its hands off content (this also affects [[hReview]]). [[abbr-design-pattern]] doesn't seem the right solution here. Someone from France suggested elsewhere to use the class value '''telwork''', etc. but again it's a dubious solution (remember that a ''tel'' can have a type of ''voice'' and ''work'' '''at the same time'''). I suggest considering:

<pre><nowiki>

Casa (preferido):
+1.415.555.1212

</nowiki></pre>

It could be argued that somehow this solution violates the microformats [[principles|principle of visible data]]. Maybe it does, but [[i18n]] should come first because otherwise microformats violates the first rule: '''solve a specific problem''' (and the last: "enable and encourage decentralized and distributed development, content, services: explicitly encourage the original 'spirit of the Web'"). -[[User:XavierBadosa|Xavier Badosa]]
*#* ACCEPTED SOLVED. The use of <code>abbr</code> and <code>title</code> attribute to provide an alternate language representation rather than an abbreviation expansion falls outside the semantics of <code>abbr</code>. The [[value-class-pattern]] has been devised as a solution to this problem, to avoid the semantic mis-use of abbr for this instance.

* 2007-01-30 raised by [[User:AndyMabbett|Andy Mabbett]]
*# Many sites, not least Wikipedia, publish co-ordinates as degrees-minutes-seconds (e.g. [http://en.wikipedia.org/wiki/Birmingham]). Should [[geo]] be extended to allow for this, with parsers making the conversion to digital values?
*#* ACCEPTED BRAINSTORMING. My first instinct is that if a precise grammar can be defined for the human friendlier d-m-s syntax, and if that precise grammar reflects the 80% of existing real world cases (e.g. Wikipedia as cited), then it should be considered for addition to the [[geo]] property and thus hCard. This may help reduce the number of instances of needing to duplicate the d-m-s value as a decimal value for machines. -Tantek

* 2007-02-02 raised by [[User:DerrickPallas|Derrick Pallas]]
*# [[adr]] says that all of it's properties are singular; however, "street-address" is listed as zero-or-more.
*#* ACCEPTED. This appears to have been fixed in the [[adr]] specification. "street-address" is no longer listed as zero-or-more.

* 2007-02-25 [http://microformats.org/wiki?title=adr&diff=next&oldid=13732 raised elsewhere] by [[User:JamesCraig]]
*#internationalization Note: <code>country-code</code> may be missing. Usually a postal-code prefix such as "FIN-00630 Helsinki" or "L-4750 Petange" (Luxembourg).
*#* ACCEPTED FAQ. This seems like just an FYI/FAQ rather than any real issue. Often country names can be inferred from postal-codes. Also perhaps the country-name can be marked up as an abbr subset of the postal-code in cases like the "FIN" example given. -Tantek

* 2007-03-19 raised by [[User:ChristinaHope|Christina Hope]]
*# ''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?''
*#** 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.)
*#** REJECTED INSUFFICIENT INFORMATION. Perhaps a note can be added to [[vcard-implementations]] with mention of this issue, in case others come across it and can then document it more thoroughly.

* 2007-03-26 raised by [[User:AndyMabbett|Andy Mabbett]]
*#Parsers (Operator, Tails) currently expect <code>adr</code> to have one or more children. It is not clear from the spec that that's mandatory; nor is it always possible for an address field in a templated (or CMS) web site to be defined with such granularity. See [[hcard-brainstorming#ADR with no children]] for discussion.
*#* ACCEPTED. Tantek [[to-do]]: Add more precision to how to handle adr sub-properties (or lack thereof) to [[adr]] and [[hcard]]. In particular, an "adr" without any sub-properties simply provides no information.

* 2007-03-28 raised by [[User:JamesCraig|James Craig]]
*#[[internationalization|Internationalization]] (i18n) issue for implied optimization of FN. Many languages (for example, Japanese) often list FN as "family-name given-name" instead of the assumed "given-name family-name" in English and other Western languages. There should be a affordance to indicate the order ''or'' a note in the spec indicating that the two-word FN is a shorthand for Western languages and any languages not fitting this format should explicitly define "family-name" and "given-name" every time.
*#* ACCEPTED. Tantek [[to-do]]: add internationalization section in [[hcard|hCard]] spec, and note in the spec indicating that the two-word FN is a shorthand for Western languages and any languages not fitting this format should explicitly define "family-name" and "given-name" every time. In particular, the fn implied n optimization should be limited to fn properties which themselves are on elements that are on a whitelist of Western languages that typically publish with "given-name family-name" order, such as "en" (add others as confirmed by i18n experts). fn elements of other languages should not imply this optimization. When the optimization is not implied, then the n property is left as is - if it were otherwise empty, it is left empty.
* 2007-03-31 raised by [[User:AndyMabbett|Andy Mabbett]]
*# 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)
*#* 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)
*#* ACCEPTED BRAINSTORMING. The [[geo-extension-strawman]] should be listed in [[geo-brainstorming]] for consideration in a revision of [[geo]] and the microformats that use it ([[hCard]] and [[hCalendar]]).

* 2007-04-09 raised by [[User:AndyMabbett|Andy Mabbett]]
*#Why is [[geo]] still a draft, when it's included in the already-published [[hcard|hCard]] spec?
*#* ACCEPTED. [[geo]] has been vetted long enough by the community to be raised to the same level as hCard. Tantek [[to-do]]: send an email to microformats-new proposing this.

* 2007-04-19 raised by [[User:AndyMabbett|Andy Mabbett]]
*#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: <code><nowiki><abbr title="1890-02-10">29 January 1890</abbr></nowiki></code>?
*#* ACCEPTED FAQ. The author of the content should specify *at least* an ISO compatible Gregorian date (i.e. using the [http://en.wikipedia.org/wiki/Proleptic_Gregorian_calendar Proleptic Gregorian Calendar] as necessary), e.g. as the Boris Pasternak example does, and mark *that* date up with the <code>bday</code> property: <code><nowiki>"<abbr title="1890-02-10">10 February</abbr> [O.S. January 29] 1890"</nowiki></code> Since the likelihood of error/drift/misunderstanding is greatly increased by two different representations of date with different numbers with one of them being less visible (e.g. in the <code>title</code> attribute), pattern like the suggested <code><nowiki><abbr title="1890-02-10">29 January 1890</abbr></nowiki></code> MUST be '''avoided''' by authors.

* 2007-04-21 raised by [http://www.mnot.net/ Mark Nottingham].
*# Pages often list many addresses in the same locality, but hCard (and adr) are currently structured so that you have to repeat the entire global context for each address. For example, <pre><nowiki>
<h2>Pizza Shops in Burlingame, California</h2>
<ul>
<li>Round Table - 231 Burlingame Avenue</li>
<li>Village Host - 303 Broadway</li>
<li>Pizza Hut - 43423 El Camino Real</li>
</ul>
</nowiki></pre>As specified, there'd be a lot of repeated information here.However, if adr allowed use of locality, region, postcode and country as ancestors of the more specific address tags, it would save a lot of bits -- and help adoption of these microformats in this kind of case (which is quite common).
*#* ACCEPTED FAQ. Use the [[include-pattern]]. [[User:AndyMabbett|Andy Mabbett]] 03:51, 21 Apr 2007 (PDT)

* 2007-04-24 raised by [[User:Singpolyma|singpolyma]]
*# ''What is the 'Label' property for''
*#* ACCEPTED FAQ. Per earlier resolutions, more explanation will be added to the hCard specification, and this question should be added to the [[hcard-faq]].

* 2007-04-27 raised by Sjoerd Mullender
*# There is a proposal for a geo URI scheme [http://www.ietf.org/internet-drafts/draft-mayrhofer-geo-uri-00.txt]. It would be nice if that scheme and the geo hCard type could somehow be combined. It seems to me that if you want to use both and also have a human-readable version, you need three copies of the latitude/longitude: <pre><nowiki>Location: <a href="geo:52.356389,4.952222"><abbr class="latitude" title="52.356389">52°21'23.00" N</abbr> <abbr class="longitude" title="4.952222">4°57'08.00" E</abbr></a></nowiki></pre>
*#* ACCEPTED BRAINSTORMING. This is a very interesting proposal, and clearly it is desirable to minimize the number of copies of the latitude/longitude. Thus this should be added to the [[geo-brainstorming#geo_links|geo brainstorming geo links section]]. -Tantek

* 2007-08-03 raised by [http://www.kaply.com/weblog/ MikeKaply].
*# ''Issue 1: When using the value design pattern, should the data be extracted completely (including HTML tags) or just text content? In general, the value pattern seems to imply taking the data exactly.''
*#* ACCEPTED FAQ. For [[hcard#Value_excerpting|value excerpting]], the parsing is handled as it would be for the property, but just on the element with class name "value" rather than the element with the class name of the property itself. Thus in general just the text content but see [[hcard-parsing]] specific combinations of property and/or element for special cases. It is only the [[include-pattern]] which incorporates the HTML subtree (including tags) in its entirety.

* 2007-11-04 raised by [http://www.tomota.de/ RalfEngels].
*# ''Issue 1: The section Organization Contact Info is exeedingly vague. It says "I must not set the N property" and later on it says that I could set it to an empty value. Which of both is true? Must not or empty?''
*#* ACCEPTED. Tantek [[to-do]]: clarify the spec on this point. Not setting it and setting it to empty have the same effect. Improve the wording.
*# ''Issue 2: Same section. It does not cover e.g. Mr Fischer (N=Fischer) from the Fischer AG (ORG=Fischer). Could you re-formulate it stating that if the N attribute is missing the hcard is regarded as the card of a company.''
*#* REJECTED. If the "n" property is missing, then remaining fn+org or implied fn rules still apply.
*# ''Issue 3: Grouping as specified by rfc2425 and supported by vcard cannot be expressed. Grouping allows you to express the relation between different values.''
*#* REJECTED. hCard only maps the properties and values from vCard, not all features. Grouping in particular is excluded.
*# ''Issue 4: Implied n optimization: the typical case list specifies a (space) in the first and last line. In the middle lines it specifies a (comma). I guess this should mean (comma)(space) instead. In addition it contradicts with the previous text where you state that the separating character is a (whitespace)''
*#* ACCEPTED. Tantek [[to-do]]: clarify the spec on this point. space and whitespace are the same in this context.
*# ''Issue 5: Concatenation of texts is not consistent in the examples. Example file 21 contatinates telephone fields with spaces. Example 16 concatenates multiple name sub-properties by a comma. Example 34 even concatinates multiple note fields.''
*#* ACCEPTED. Tantek [[to-do]]: clarify concatenation handling in [[hcard-parsing]]. [[to-do]]: correct [[hcard-examples]] accordingly.

=== resolved 2008 ===
'''Note: As the resolutions are enacted and the issues are closed, it may be worth moving this year of issues to its own page.'''

* 2008-01-01 raised by [[User:AndyMabbett|Andy Mabbett]] in [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011182.html microformats-discuss/2008-January/011182.html]
*# The "n" optimization rules (nickname, fn) should not apply where the fn is on part of adr or label: e.g <code><nowiki>
New York</nowiki></code>; <code><nowiki>Asia</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]])
*#* ACCEPTED BRAINSTORMING. This both makes sense from the point of view of avoiding a shorthand optimization to represent a person in a case where clearly the markup represents a place, and for allowing one possible way to use hCard for named locations.

* 2008-01-09 2008- moved from [[vcard-suggestions]]
*#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">Travail : 0321596224</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 : 0321596224</nowiki> Please, use class and id attributes ONLY for microformats specifications ! XML #cdata and #data are localized ! Thanks !
*#* ACCEPTED ISSUE, REJECTED PROPOSAL. The localization issue is recognized and now addressed by the [[value-class-pattern]]. The proposal for "telwork" is unnecessary, will contribute to vocabulary expansion for every other property that has a work subtype for example, illustrates a vocabulary anti-pattern, and is thus undesirable.

* 2008-01-13 raised by Christopher Allen at OpenIDDevCamp (collected by [[User:Tantek|Tantek]]).
*# 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.
*#* ACCEPTED FAQ EXAMPLES. This is an excellent question, and a good subject to address as an example in [[hcard-authoring]] as well as on a page on [[date-time-authoring]] with perhaps a Q&A pointer from [[hcard-faq]]. For now, see [[value-class-pattern]] and Jakob Nielsen's post on [http://www.useit.com/alertbox/9608.html International Usability] which mentions time zone.

* 2008-02-02 raised by [[User:AndyMabbett|Andy Mabbett]]
*# The "<code>n</code>" optimization 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>
Webmaster</nowiki></code>; <code><nowiki>Duty Manager</nowiki></code>, since, in these examples, "Webmaster" is not a nickname, "Duty" is not a given-name and "Manager" is not a family-name.
*#* ACCEPTED BRAINSTORMING. This makes sense from the point of view of avoiding a shorthand optimization to represent a specific person's nickname or given/family names in a case where clearly the markup represents a generic person. In both examples given, it may be better to define the n property as having an implied empty value, while the fn has the explicitly marked up value.

* 2008-02-06 raised by [[User:Guillaume Lebleu| Guillaume Lebleu]]
*# 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.
*#* REJECTED MISCONCEPTION, MARKUP ERROR. ACCEPTED FAQs. 1. The scope that vCard provides is that of "person" or "organization", combined with that with the FN meaning of "formatted name" results in the meaning of "formatted name of a person or organization" (e.g. "person name" as stated). FN by itself does not have the scope of person or organization. The page given, http://cinematreasures.org/theater/365/, erroneously uses an empty fn, when they should be marking up the following markup: <code><nowiki><a href="/theater/365/">Hornbeck & Penthouse Theatre</a></nowiki></code> with fn org url uid for property hCard semantics: <code><nowiki><a class="fn org url uid" href="/theater/365/">Hornbeck & Penthouse Theatre</a></nowiki></code>. This example should be added to [[hcard-examples-in-wild]], along with this noted correction in markup.

* 2008-02-07[[User:AndyMabbett|Andy Mabbett]]
*# The "<code>fn</code>" optimization rule should not apply where the full <code>fn</code> is also the <code>nickname</code>: e.g <code><nowiki>Plastic Bertram</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)"?)
*#* ACCEPTED BRAINSTORMING AND FAQ. This makes sense from the point of view of avoiding a shorthand optimization to represent a person's given/family names in a case where clearly the markup represents their nickname. The given pseudonym could perhaps be marked up as: <code><nowiki>Maurice Micklewhite (known professionally as Michael Caine)"?)</nowiki></code>, however, without additional context of where that example is used, it's not clear that that's the best markup possible for the text.

* 2008-02-07 raised by [[User:AndyMabbett|Andy Mabbett]] in [http://microformats.org/discuss/mail/microformats-discuss/2008-February/011552.html microformats-discuss/2008-February/011552.html]
*# Is "n" optional or mandatory? The spec says yes (with exceptions) the cheat-sheet says no. Parsers and common practice seem to indicate not.
*#* ACCEPTED FAQ. The "n" property is required, but that requirement may be met by satisfying one of the n property optimizations/shorthands. Thus parsers and common practice, by implementing those optimization/shorthands are still indicating the "n" property requirement.

* 2008-02-08 raised by [[User:Guillaume Lebleu| Guillaume Lebleu]]
*# 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]
*#* ACCEPTED BRAINSTORMING. Because of this and other mentions of challenges of using hCard (and other microformats) in semantic HTML Tables, as well as the observation that fewer levels of hierarchy makes microformats easier to understand, a proposal is being considered to promote subproperties of a singular property to being properties themselves, e.g. the <code>n</code> subproperties (<code>given-name</code>, </code>family-name</code>, etc.), and in the case of non-singular properties with subproperties (e.g. <code>adr</code>), allowing the use of such subproperties (e.g. <code>street-address</code>, <code>locality</code>, <code>region</code>, etc.) with a single default/implied <code>adr</code> property container instance for the hCard.

* 2008-06-01 raised by [[User:Kornel|Kornel]]
*# 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)
*#* <code><nowiki><a href="mailto:href">nodetext</a></nowiki></code> – is it "href", "nodetext" or an error? What if there are multiple links inside?
*#** Parsed as "nodetext" [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#* <code><nowiki><abbr title="title">nodetext</abbr></nowiki></code> – is it "title" or "nodetext"?
*#** Parsed as "nodetext" [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#* <code><nowiki><img alt="alt">nodetext</nowiki></code> – is it "alt", "nodetext" or both?
*#** Per [[hcard-parsing]], since the "fn" property is a text/string property, in this example it should be parsed as "nodetext" [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC).
*#** A matter of debate recently. Some parsers as "nodetext", others as "altnodetext". [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#*** What parsers produce "altnodetext"? Please add them to [[hcard-implementations]] and per [[hcard-parsing]] note that those parsers are buggy since the fn property should be parsed as "nodetext" in this example. [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC)
*#* <code><nowiki><abbr title="title">nodetext</abbr></nowiki></code> – "title", "nodetext" or both?
*#** Parsed as "nodetext" [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#* <code><nowiki><img src="src" alt="alt">nodetext</nowiki></code> – "src", "alt", "nodetext" or "altnodetext"?
*#** Per [[hcard-parsing]] in this example it should be parsed as "nodetext" [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC).
*#** A matter of debate recently. Some parsers as "nodetext", others as "altnodetext". [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#*** What parsers produce "altnodetext"? Please add them to [[hcard-implementations]] and per [[hcard-parsing]] note that those parsers are buggy it should be parsed as "nodetext" in this example. [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC)
*#* <code><div class="category"><a rel="tag bookmark" href="href">nodetext</a></div></code> – is it a tag? What if there are multiple links inside?
*#** 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)
*#** As Toby indicates, that example would likely generate two "category" values for the hCard, "href" (or the last segment of the href, if "href" was not intended as a literal), and "nodetext". I say "likely" because if those two happened to be the same, only one <code>category</code> value would be generated.
*#* '''ACCEPTED FAQ.''' Lots of questions here that are answered by [[hcard-parsing]] but could also be listed in [[hcard-parsing-faq]] for hopefully easier discovery. In addition, each example presented would make a good test case.
*# Does <code>agent</code> property have to be an hCard?
*#* Is <code>Joe Sixpack</code> allowed?
*#** Yes. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#* Is <code>…</code> ok?
*#** [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><div class="agent vcard">…</div></code>. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#** As Toby says, it is "ok" in that it is valid, but the agent relationship is not established by that example. Toby's change to the example to use <code>class="agent vcard"</code> fixes it to have the intended effect. [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC)
*#* What about <code><a class="agent" href="card.vcf">…</a></code>?
*#** 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)
*#** No. The example given will be parsed as "…" for the <code>agent</code>. [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC)
*# Is value of <code><abbr></code> without <code>title</code> empty or should it be interpreted like <code></code>?
*#* I think consensus is that the node text should be used. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#* More than consensus, per the [[hcard-parsing#all_properties|hCard parsing spec]]: "<code><abbr title></code>: use the value of the 'title' attribute. If there is no 'title' attribute then use the contents of the element." [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC)
*#* '''ACCEPTED FAQ.''' Lots of questions here that are answered by [[hcard-parsing]] but could also be listed in [[hcard-parsing-faq]] for hopefully easier discovery. In addition, each example presented would make a good test case.
*# Does <code><acronym></code> work like <code><abbr></code>?
*#* Not as per spec, but some parsers do treat it like <code><abbr></code>. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#** Which parsers? Please list them and note their extra support of <code><acronym></code> on the [[hcard-implementations]] page.
*#* '''ACCEPTED FAQ and BRAINSTORMING.''' <code><acronym></code> is not currently handled in any special way per [[hcard-parsing]]. If you (or anyone) thinks that <code><acronym></code> should be handled like <code><abbr></code>, please add it as a proposal to [[hcard-brainstorming]]. [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC)
*# Is this allowed: <code><nowiki><div class="photo">http://example.com/photo.jpg</div></nowiki></code>?
*#* It is allowed and will parse the URL as the photo property per step 3 of [[hcard-parsing#parsing_hCard_properties_and_values|hCard parsing properties and values]]. [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC)
*#* 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)
*#** Which "naive" parsers? Please list them on [[hcard-implementations]] and note what problems they supposedly have with this example.
*#* '''ACCEPTED FAQ.''' Lots of questions here that are answered by [[hcard-parsing]] but could also be listed in [[hcard-parsing-faq]] for hopefully easier discovery. In addition, each example presented would make a good test case.
*# 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>?
*#* 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)
*#* Yes both are allowed but there is insufficient detail in the example(s) given to understand what utility they would have. [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC)
*#* '''ACCEPTED FAQ.''' Lots of questions here that are answered by [[hcard-parsing]] but could also be listed in [[hcard-parsing-faq]] for hopefully easier discovery. In addition, each example presented would make a good test case.
*# Is it allowed/required to use <code>mailto:</code> when e-mail is in non-<code><a></code>, e.g. <code><nowiki>mailto:joe@example.com</nowiki></code>
*#* Yes, but for copy-and-pasteability I'd recommend leaving out the "mailto:" prefix. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#* '''ACCEPTED FAQ and BRAINSTORMING.''' Yes it is allowed per step 3 of [[hcard-parsing#parsing_hCard_properties_and_values|hCard parsing properties and values]]. However the "mailto:" prefix is currently only removed when specifying the <code>email</code> property on <code>a</code> or <code>area</code> elements per [[hcard-parsing#email_property|hCard parsing - email property]]. Thus this should both be clarified in [[hcard-authoring]], that is, Toby's suggestion to leave otu the "mailto:" prefix in user visible text of the email property, and be clarified in [[hcard-parsing]], that is, that a "mailto:" prefix should be removed from the <code>email</code> property regardless of what HTML element is used for the <code>email</code> property.
*# If value of a property is empty (<code><nowiki></nowiki></code>) should it be interpreted as unknown value? ignored completely like it didn't exist? an error?
*#* '''ACCEPTED FAQ.''' Yes it is allowed and per step 3 of [[hcard-parsing#parsing_hCard_properties_and_values|hCard parsing properties and values]] will result in an empty value.
*# Can hCard contain nested hCard anywhere? or only outside any property or only inside <code>agent</code>?
*#* Yes, though naive parsers may have problems. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#* '''ACCEPTED FAQ.''' Yes a nested hCard is allowed anywhere inside an hCard, however, note that any property inside the nested hCard will not be seen as part of the container hCard per [[hcard-parsing#nested_hCards|hCard parsing - nested hCards]]. A nested hCard on the <code>agent</code> property provides structured details on an agent of the containing hCard, and a nested hCard on the <code>org</code> property provides structured details on an org of the containing hCard.
*# Can <code>organi'''s'''ation-name</code> (note spelling) be interpreted by parsers?
*#* It should not. [[User:TobyInk|TobyInk]] 08:30, 1 Jun 2008 (PDT)
*#* '''ACCEPTED FAQ.''' No. See [[en-us-faq#why_not_create_multiple_aliases_for_properties_in_other_spellings_and_languages|en-US FAQ: why not create aliases for properties in other spellings and languages.]].
*# Is <code>type</code> class ignored in values anywhere? It is ignored in <code><div class="tel">Work 555</div></code>, but is it in <code><div class="fn">Work Joe</div></code>?
*#* 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)
*#* '''ACCEPTED FAQ.''' Indeed, any markup that is not specified to do anything should be ignored by parsers - this is a "MUST IGNORE" aspect of the forwards/backwards compatibility design of microformats. Lots of questions here that are answered by [[hcard-parsing]] but could also be listed in [[hcard-parsing-faq]] for hopefully easier discovery. In addition, each example presented would make a good test case.

* 2008-06-15 raised by [[User:Kornel|Kornel]]
*# [[RFC2426]] 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?
*#* I raised this very issue on the mailing list about a month ago, but received no responses. Given that hCard claims to be a "a 1:1 representation of vCard (RFC2426) properties and values in semantic HTML or XHTML" (direct quote from [[hcard|spec]]), I think it's reasonable to infer that these types *are* allowed, but simply undocumented so far. I'll be including support for them in the next alpha of Cognition. [[User:TobyInk|TobyInk]] 23:59, 15 Jun 2008 (PDT)
*#* '''ACCEPTED.''' Indeed this is an unintentional omission from the [[hCard]] specification. In the [[hcard#Property_List|hCard list of properties]], the entry for "label" should be changed to "label (type, value)" and the section on [[hcard#adr_tel_email_types|adr tel email types]] should be renamed to "adr email label tel types" and a list item should be added as follows: "* label type: INTL, POSTAL, PARCEL, WORK, dom, home, pref".

* 2008-06-16 raised by [[User:Kornel|Kornel]]
*# In the rfc2426 the KEY property defaults to binary. hCard profile suggests to use <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 <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.
*#* ACCEPTED FAQ EXAMPLES. How to author a "key" property value should be better addressed as indicated, in both [[hcard-examples]] and [[hcard-authoring]] with perhaps a Q&A pointer from [[hcard-faq]].

* 2008-12-11 raised by [[User:mephtu|mephtu]]
* I am concerned that hCard usage will foster widespread abuse of personal datamining by scrapers/spammers, as a standard markup of personal information formalizes the structure of such information which until now has been loosely encoded as formatting markup (e.g. HTML).
** The nice thing about microformats is that you are not required to publish everything. If you are not comfortable publishing your email, address, phone or other information, then you don't have to. If you are already publishing it on the web, then by adding microformats you are disambiguating a plain string of text and a string as meaning your name. [[User:Brian|Brian]] 08:56, 12 Dec 2008 (UTC)
*** That is true, but it does more tightly associate e-mail addresses with other information. Spammers could use this to tie an e-mail address to other personal/contact details and make their messages less spammy in an attempt to fool filters. For example, some filters will raise the spam score of a message if the "To" field contains just an e-mail address, and not the recipient's name - hCard provides spammers with a fairly reliable way of finding out that name. I don't think this is a ''huge'' concern, but it is a slight concern which shouldn't be entirely dismissed. [[User:TobyInk|TobyInk]] 16:37, 12 December 2008 (UTC)
*** ACCEPTED FAQ. There is already [[faq#Microformats_and_Spam|a general microformats FAQ on SPAM]] and this should be either added to that or perhaps specifically to [[hcard-faq]].

* 2008-12-16 raised by [[User:TobyInk|TobyInk]]
*# '''n''' is listed as a required property. Sometimes this is implicit from the '''fn''', and that's fine. However, when <code><nowiki>Foo</nowiki></code> is found, "Foo" is implicitly a nickname, so the hCard still has no '''n''' property — does such an hCard still need an explicit '''n''' added?
*#* ACCEPTED FAQ. The conclusion that "the hCard still has no '''n''' property" is incorrect. The hCard has an "n" property, it is just empty. This should be noted explicitly in [[hcard-parsing]] or perhaps [[hcard-parsing-faq]].

=== resolved 2009 ===
<div class="hentry">
{{ResolvedIssue}} 2009-218 raised by [[User:Singpolyma|Singpolyma]]
<div class="entry-content discussion issues">
* Format for key. What format should be used for key? I suggest the following:<pre><nowiki><a class="key" type="application/pgp-keys" href="https://path.to/key">My PGP Key</a></nowiki></pre>With MIME type obviously changed based on type of key.
** RESOLVED ACCEPTED FAQ EXAMPLES. This seems reasonable to me, and we should update [[hcard-examples]] and [[hcard-faq]] accordingly. Thanks for the suggestion. [[User:Tantek|Tantek]] 02:57, 26 August 2009 (UTC)
</div>
</div>

<div class="hentry">
{{ResolvedIssue}} 2009-09-10 raised by [[User:TomMorris|TomMorris]]
<div class="entry-content discussion issues">
* Parsing UTF-8 'special' space characters in telephone fields. I recently designed a page that used an hCard with a <code>span</code> containing the <samp>tel</samp> value. To space the phone number appropriately, I used the U+8201 (THIN SPACE) character <code>&#8201;</code>. [[operator|Operator's]] hCard parser coughed up on this and refused to read both the contents of the <samp>tel</samp> <code>span</code> but also an <code>a</code> element containing the <samp>email</samp> property that was contained in the parent <code>p</code> element. I cannot find a clear definition of what is acceptable content for the <samp>tel</samp> property. There seems to be two ways of resolving this: (1) instruct authors of microformat parsing libraries to normalise the Unicode characters U+8194 (EN SPACE), U+8195 (EM SPACE), U+8196 (THREE-PER-EM SPACE), U+8197 (FOUR-PER-EM SPACE), U+8198 (SIX-PER-EM SPACE), U+8199 (FIGURE SPACE), U+8200 (PUNCTUATION SPACE), U+8201 (THIN SPACE), U+8202 (HAIR SPACE), U+8203 (ZERO WIDTH SPACE) and other similar characters (including the HTML entities <code>&ensp;</code>, <code>&emsp;</code>, <code>&thinsp;</code> and <code>&nbsp;</code>) so that, for the purpose of parsing the microformat they are treated as a standard space (U+0020) or (2) instructing microformat authors to not use any other space character than U+0020 (and to use the [http://www.w3.org/TR/CSS21/text.html#spacing-props CSS <code>word-spacing</code> property] for manipulating <samp>tel</samp> properties). Which of these is best? Anyone want to survey the current implementations to see how they currently parse telephone numbers with unexpected characters in them? Part of the problem may be that there doesn't seem to be any clear specification of what a valid telephone number is, so far as I can see—which is just from reading [http://www.ietf.org/rfc/rfc2426.txt RFC 2426] §3.3, which says that it should simply be the telephone format defined in X.500 ([http://www.ietf.org/rfc/rfc1274.txt RFC 1274]), but there is no explicit definition in X.500 except to say it is "telephoneNumberSyntax", which is defined in [http://www.ietf.org/rfc/rfc1778.txt RFC 1778] §2.16 as simply being a printable string. Perhaps I've gone off down a blind alley! (Do we need a page for character encoding/Unicode issues?)
** ACCEPTED FAQ, parsing. [[microformats]] depend on the character parsing of the language they are in. In this case, let's for example see what HTML4 and HTML5 say, and advise accordingly in [[hcard-faq]] and [[hcard-parsing]]. [[User:Tantek|Tantek]] 08:56, 9 October 2009 (UTC)
</div>
</div>

=== resolved 2010 ===

<div class="hentry">
{{ResolvedIssue}} 2010-02-03 raised by [http://foolip.org/ Philip Jägenstedt]
<div class="entry-content discussion issues">
* Implied "n" Optimization. The [[hcard#Implied_.22n.22_Optimization|hCard spec]] and the derived [http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html#conversion-to-vcard microdata vCard spec] has some magic intended to derive N from FN when it is not given explicitly, as N is required by the vCard spec. The guessing employed will fail for at least Vietnamese names (e.g. Phương Thanh => N:Thanh;Phương;;;), Chinese names (e.g. 冯小刚 => N:;冯小刚;; and Feng Xiaogang => N:Xiaogang;Feng;;;) and Japanese/Korean names for the same reasons. The problem is both that family-name and given-name are reversed and that Chinese is written without space, so the whole name is interpreted as family name. If the only issue is that N is mandatory, simply outputting N:;;;; seems the safest. Although it's technically possible to add markup to avoid the guessing, that's not going to be an option when microdata/microformats are used in a template and the user isn't asked for both the full name and all of its components. This issue was previously raised on [http://microformats.org/discuss/mail/microformats-discuss/2010-February/013187.html microformats-discuss].
** RESOLVED PARTIAL DUPLICATE. This is mostly a duplicate of [[hcard-issues-resolved#fn-opt-i18n|previous issue raised by James Craig 2007-03-28]], however, the additional information is appreciated. This documentation of the issue contains several points useful to a refined resolution. [[User:Tantek|Tantek]] 00:22, 16 April 2010 (UTC)
*** MUST NOT apply FN to implied N optimization when lang is Vietnamese (need lang code), Chinese (need lang code(s)), Japanese ("ja"), or Korean (need lang code).
*** For hCard to vCard converters: If an hCard lacks an 'n' property (either explicit or implied), when producing the equivalent vCard, output an empty N "N:;;;;" property in order to satisfy vCard's requirement that an N property be specified.
** '''Further information''' Hey Tantek, this assumes that the page has lang declared. That just isn’t common in Japan, and I guess in the other countries mentioned, given the monolingualism. I did some quick research for you, using the first 10 search results for Nakamura (a common Japanese family name) in kanji:

http://search.yahoo.co.jp/search?p=%中村&ei=UTF-8&fr=top_ga1_sa&x=wrt
303,000,000 results
http://ja.wikipedia.org/wiki/中村 yes
http://www.nakamura.ed.jp/ no
http://shunsuke.com/ yes
http://ja.wikipedia.org/wiki/中村紀洋 yes
http://www.mypixel.co.jp/kabuki/nakamura/ no
http://www.nakamuraya.co.jp/index.html no
http://www.nakamura-net21.co.jp/ no
http://www.eriko-nakamura.com/index.html no
http://ataru-atariya.com/ yes
http://baseball.yahoo.co.jp/npb/player?id=12101 yes
5 out of 10

http://www.google.co.jp/search?hl=en&source=hp&q=中村
28,700,000 results
http://www.nakamura.ed.jp/ no
http://ja.wikipedia.org/wiki/中村 yes
http://ja.wikipedia.org/wiki/中村俊輔 yes
http://nakamura-japan.net/ no
http://shunsuke.com/ yes
http://www.nakamura-udon.jp/ no (not even encoding!)
http://www.city.nakamura.kochi.jp/topj.html yes
http://www.nakamura-u.ac.jp/ yes
http://dailynews.yahoo.co.jp/fc/sports/shunsuke/ no (!)
http://nakamurajapan.blog17.fc2.com/ yes
6 out of 10

I’d like to note these are the highest ranked pages for a very popular search term, and include universities, schools and soccer star (well in Japan ;-) Shunsuke Nakamura’s homepage. There’s even a yahoo.co.jp site without lang="ja". I guess you can imagine the long tail :/

If you need Japanese examples or further info, please let me know.

Also, check the hCards for http://twitter.com/boblet/following for examples of Philip’s comment about template/social media sites. Ignoring the current invalid stuff, you can see my friend Channy’s vcard is wrong.
</div>
</div>

== see also ==
* [[hcard-issues]]
* [[hcard-issues-closed]]

hcard-issues-closed

2010-07-20T02:50:03Z

Oli: /* closed 2008 */ adding link to #fn-opt-i18n

<entry-title>hCard closed issues</entry-title>

== closed issues ==
[[hCard]] closed issues that have no further actions to take..

=== closed 2005 ===
Closed issues that were raised in 2005.

* 2005-06-30 raised by Jack L. Wolfgang II. Please feel free to move these to the FAQs if they are better suited there.
*# ''Handling middle names and suffixes: How does one handle middle initials/names in the hCard format and suffixes that are not honorific suffixes (e.g. Jr., Sr., II, III, etc. as opposed to Ph.D., Esq., M.D., etc.)?''
*#*A: ACCEPTED FAQ. hCard is based of the RFC2426 spec. I you want to use a middle initial it can be expanded using the abbr element. <code><abbr title="[MiddleName]" class="additional-name">M</abbr></code>. Honorific Suffixes in the RFC include Jr., Esq. and other inherited suffixes, so I would just use <code><abbr class="honorific-suffix" title="Junior">Jr.</abbr></code> etc. See [[hcard-faq#How_do_you_mark_up_suffixes|hCard FAQ: marking up suffixes]] for more details.
*# ''Handling different types of addresses: How does one handle the TYPE (e.g. postal, work, etc.) specification for addresses as specified in RFC 2426 Section 3.2.1?''
*#*A: ACCEPTED FAQ. If you want to add a type to certain elements, including address and telephone it may be done in the following manner:
<source lang=html4strict>

work
...

</source>
See [[hcard-faq#How_do_I_markup_multiple_addresses|hCard FAQ: multiple addresses]] for detailed examples.

<source lang=html4strict>

work
123.555.1212

</source>
See [[hcard-authoring#Phone_Numbers|hCard authoring: phone numbers]] for more detailed examples.

Note: 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

* 2005-07-22 raised by DanConnolly
*# ''...in my cellphone/sidekick address book, I have a number of entries for companies. I wrote [http://dev.w3.org/cvsweb/2001/palmagent/asHCard.xsl asHCard.xsl] to convert the data from RDF to hCard, but I don't know what to do with entries for companies, since FN is mandatory in hCard.''
*#*A: ACCEPTED. This should at least be an FAQ. "How do I write an hCard for a company?" The vCard specification is silent on this point (entries for companies). Thus there are two options as far as the hCard standard is concerned:
*#*# Set "fn" and "org" to the same value. E.g. <code>W3C</code> (recommended)
*#*# Set "org" as usual, and set "fn" explicitly to empty. E.g. <code>W3C</code> or
*#*#* Simply have no "fn", and on the parsing side, if there is no "fn" present, but there is an "org" property, then duplicate the "org" value as "fn"
*#*The last two options are effectively the same and are both not explicit and easily confusable with a "missing data" condition. Thus option 1 is preferred. For converting applications (hCard to vCard), they ''may'' consider using proprietary extensions to make the distinction explicit in generated vCards, based on either case 1 or 2 above. E.g. Apple's Address Book application supports the property: <code>X-ABShowAs:COMPANY</code>
*#*We are looking for descriptions of how other vCard supporting applications treat "company" vCards differently from "person" vCards. Please provide descriptions here:
*#** Address Book / MacOSX.3:
*#*** Export (e.g. drag & drop to desktop, view in text editor)
*#**** Sets "FN" and "ORG" to the name of the company
*#**** Sets proprietary <code>X-ABShowAs:COMPANY</code>
*#*** Import (e.g. edit in text editor, drag & drop from desktop)
*#**** By setting "FN" and "ORG' to the same name (e.g. Banana Computers Inc.)
*#**** And removing any proprietary properties (e.g. X-ABShowAs)
*#**** Address Book user interface showed new vCard as a "company" contact rather an a person
*#** Address Book MacOSX.4:
*#*** same results as above -RyanKing
*#** The Danger Hiptop (aka T-Mobile Sidekick) address book:
*#*** Export (e.g. [http://lists.w3.org/Archives/Public/www-archive/2005Sep/0007.html email to a mailing list])
*#**** Sets "FN" to the empty string and puts the company name in "ORG".
*#*** Import - could not find a way to import a .vcf, by email, IM, or other means into the Sidekick.
*#** Contacts / Outlook 2003 Windows
*#*** Export (e.g. Highlight contact, File, Save As, vcard)
*#**** Sets "N" and "ORG to the name of the company
*#**** Sets "FN" to value in "File as:"
*#** Add another vCard app here.
*#* RESOLVED. hCard now specifically describes [[hcard#Organization_Contact_Info|organization contact info]], and there is also now an FAQ regarding this: [[hcard-faq#How_do_you_mark_up_an_organization|hCard FAQ: How do you mark up an organization]].

* 2005-07-23 raised by DanConnolly
*# ''Are class names case sensitive or not? [[hcard]] says "If names in the source schema are case-insensitive, then use an all lowercase equivalent."''
*#* A: ACCEPTED FAQ. Class names are case sensitive per the HTML4 specification. Hence hCard explicitly specifies the case of class name to use for source schema names that are case-insensitive. FAQ added: [[faq#Q._Are_class_names_case_sensitive.3F|FAQ: Are class names case sensitive]].
*# ''...but I find example data with class="Given-Name"''
*#* A: ACCEPTED RESOLVED. That is from an older preliminary version of the hCard spec which used mixed case class names. Such class names are no longer valid hCard. Please note which examples (URLs) are using the older class names and hopefully we can get them fixed. FAQ also added: [[hcard-faq#Can_hCards_use_variants_of_properties_like_Given-Name_or_country|hCard FAQ: Can hCards use variants of properties like Given Name]]
*#** A: By [http://suda.co.uk Brian Suda] I have fixed all the references in the [[hcard-brainstorming]] page to reflect the lower-case style, this is a hold-over from the original design, X2V has been updated.
*# ''..and code that supports it [data with class="Given-Name"].''
*#* A: ACCEPTED RESOLVED. Any code supporting the older class name(s) is for backward compatibility only, and should be phased out. Any new hCard code SHOULD NOT support such mixed case class names.
*#** [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html rfc2629xslt.html] uses Street-Address, Family-Name, etc.
*#*** A: By [http://greenbytes.de/tech/webdav/ Julian Reschke] Fixed rfc2629.xslt (2005-10-29)
*#** [http://suda.co.uk/projects/X2V/ X2V] Version 0.5.1 2005-07-08 supports Family-Name etc.
*#*** A: By [http://suda.co.uk Brian Suda] I agree that the upper-case class names can be removed from the code, this was a hold-over and will be trimmed.
*# ''The ul/ol stuff for multiple values of a property seems to be in the X2V code and in [[hcard-brainstorming]] but not in the [[hcard]] spec.''
*#* A. ACCEPTED RESOLVED. This needs to be added to the spec. 2005-11-08 Update: the way multiple values has been updated to work much better and not require ul/ol.
*# ''the [[hcard-profile]] says country-name but X2V and lots of the data I've seen says country''
*#* A. ACCEPTED RESOLVED. RFC 2426 clearly says "country name" in both the prose and the grammar, thus "country-name" is the correct class name to use. If X2V uses just "country", it needs to be fixed to use "country-name", and any such examples as well. Please note which examples (URLs) are using the class name "country" and hopefully we can get them fixed. FAQ also added: [[hcard-faq#Can_hCards_use_variants_of_properties_like_Given-Name_or_country|hCard FAQ: Can hCards use variants of properties like Given Name]]
*#** A: By [http://suda.co.uk Brian Suda] I have fixed all the references in the [[hcard-brainstorming]] page to reflect the proper country-name, X2V will support this in the next iteration when i fix several bugs at once.

* 2005-08-12 raised by [http://home.alltel.net/jackwolfgang/contact/ Jack L. Wolfgang II]. Use of mailto transport functionality for the E-Mail address field.
*# ''As stated in the [[hcard-brainstorming]] document, mailto is abused by spammers. As a result, many organizations have moved to form-based contacts as opposed to mailtos. According to [http://www.ietf.org/rfc/rfc2426.txt RFC 2426], Section 3.3.2, "A non-standard value can also be specified." Does this refer to a non-standard e-mail address value or type value?''
*#* A: ACCEPTED FAQ. Type value. Note that non-standard property values and properties are allowed in vCard, but that mechanism is not adopted by hCard. See [[hcard-faq#What_types_of_email_can_you_specify|hCard FAQ: what types of email can you specify]].

* 2005-10-30 raised by [http://greenbytes.de/tech/webdav/ Julian Reschke].
*# ''Several implementations'' '''(Which ones? Please provide links.)''' ''seem to assume that any class attribute that contains the substring "vcard" indeed signals the presence of vcard information. Not so: there are examples'' '''(What examples? Please provide links.)''' ''of where a token in the class attribute indeed only ''starts with'' "vcard", in which it should be ignored. Implementations using XPath (such as XSLT or Greasemonkey scripts) should be advised to do a <code>contains(concat(@class,' '),'vcard ')</code>.
*#* REJECTED VAGUE. Which implementations? And which examples?
*#*''(Note: the code <code>contains(concat(@class,' '),'vcard ')</code> above is broken see [[parsing-microformats#Parsing_class_values]] for a correct example --[[User:RobertBachmann|Robert Bachmann]])''
*#* CLOSING DUE TO INSUFFICIENT INFORMATION. No specific implementation examples have been provided that show any problems with substring matches of "vcard". [[User:Tantek|Tantek]] 07:00, 16 October 2009 (UTC)

* 2005-12-08 raised by [http://www.heatonarts.com Kenny Heaton].
*# ''The specification gives no way to to declare a telephone extension, as in (800) 234-5678 ext. 101''
*#* ACCEPTED FAQ. What is the best way to declare a telephone extension in a "tel" property? (also seems like it would be a vCard FAQ). See [[hcard-faq#How_do_you_mark_up_a_phone_extension|hCard FAQ: How do you mark up a phone extension]].

=== closed 2006 ===
Closed issues that were raised in 2006.

* 2006-01-21 raised by [http://inspire.server101.com/ben/resume/ Ben Boyle].
*# ''Have run into issues trying to use definition lists with hCard, specifically around nesting requirements for tel where the DT element takes a class "type" (e.g. Telephone, Facsimile) and the DD element marks the value. It is invalid to place any other elements within a DL that wrap around the DT/DD pairs so there is no available element to assign the class "tel" to. XHTML2 proposes a DI element that will resolve this issue. I am hoping for an interim solution for those that wish to use definition lists, perhaps that "any class that would be placed on the DI parent (in XHTML2) must instead be placed on the first DT element". I realise this will cause headaches for those implementing hCard parsers. I'd also like to note this may affect other (current or future) microformats and relates to the general hassle of definition lists in current (X)HTML recommendations. For your consideration - thanks!''
*#* ACCEPTED PARTIAL FAQ. An example has been added for how to use a semantic DL to markup a microformat such as hCard to the [[faq#Q._Why_do_the_examples_on_the_wiki_use_.3Cspan.3E_and_.3Cdiv.3E_for_nearly_everything.3F|faq:Why do the examples use span and div]].
*#* REJECTED LACK OF REAL WORLD EXAMPLES. No URLs have been provided that publish the specific "Telephone"/"Facsimile" in DT mark up pattern mentioned in the issue.
*#* REJECTED WORKAROUND AVAILABLE.
*#*# Consider using the [[value-class-pattern]] inside the <code><dd class="tel"></code>, e.g. <code> </code>
*#*# Don't use definition lists in this manner. The description of a definition should go completely in the DD element, and thus you should be able to put the class on that.
*#*# Use separate DLs in the cases where you would otherwise have needed a DI element.
*#* REJECTED XHTML2 ABANDONED. The W3C is abandoning XHTML2 as of 2009-12, thus there is no need to plan for a DI element.

* 2006-01-23 raised by David Janes (?).
*# ''Issue 1: Specifying Authoritative or Canonical or Official hCard''
*#* Use of rel="me"?
*#** Only specifies an alternate version, not necessarily the canonical version
*#** rel="me" must be symmetrical, per the XFN spec. What exactly does this mean for this use?
*#** "me" (and, depending on usage, "self") are not appropriate for content referring to third- parties. [[User:AndyMabbett|Andy Mabbett]]
*#** +1 REJECTED bad overloading of [[rel-me]] to attempt to make it explicity imply some logic for authoritative/canonical/official. [[User:Tantek|Tantek]] 00:28, 30 October 2009 (UTC)
*#* Suggestion: use rel="me self". Adopt "self" semantics from Atom which means "the", or controversially "alternate, equivalent" version
*#** The combined use of rel="me" and rel="self" may conflict with their definitions in the [http://www.gmpg.org/xfn/11#me XFN Profile] and RFC 4287 respectively. See [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008443.html the mailing list discussion on rel="me self"] for more information. From [[User:RCanine|Ryan Cannon]].
*#** +1 REJECTED rel="me self" per conflict pointed out by Ryan Cannon. [[User:Tantek|Tantek]] 00:28, 30 October 2009 (UTC)
*#* Suggestion: use rel="via". Per RFC 4287, via "signifies that the IRI in the value of the href attribute identifies a resource that is the source of the information provided in the containing element." from [[User:RCanine|Ryan Cannon]].
*#** REJECTED different problem. The notion of where the data came from (i.e. "via") is different from content asserting that it is authoritative/canonical/official. [[User:Tantek|Tantek]] 00:28, 30 October 2009 (UTC)
*#* Other suggestions? "authoritative", "canonical"?
*#** REJECTED inadequate description of what those terms would mean (thus they would inevitably be incompatibly used). [[User:Tantek|Tantek]] 00:28, 30 October 2009 (UTC)
*#* How does this relate to authentication/trust issues? Is this a different problem with a different scope?
*#** (microformats-discuss list) Joe Andrieu: The concept behind an "authoritative" hCard rather than "definitive" or "canonical" one was that "authoritative" would explicitly be a ''claim'' by the author of the hCard regarding its authority in describing the subject of the hCard, i.e., use ''this'' hCard as the one true source of this individual's contact information.
*#** REJECTED different problem. To summarize: authentication/trust is a separate topic. See [[OAuth]] for starters. [[User:Tantek|Tantek]] 00:28, 30 October 2009 (UTC)
*#* What exactly is the scope of the problem to solve here?
*#** (IRC) (10:47:44) sreynen: for example, all of the examples I've seen involve a single person publishing multiple hCards of himself
*#** (IRC) (10:48:13) sreynen: yet many people are talking about 3rd parties publishing hCards and pointing back to the subject's own hCard
*#** +1 REJECTED insufficient (as in, none provided) real world examples of the issue. [[User:Tantek|Tantek]] 00:28, 30 October 2009 (UTC)
*#* ACCEPTED PARTIAL. MULTIPLE ISSUES AND BRAINSTORMING. The questions of authoritative, and canonical, and representative are likely different questions and must be deconstructed into separate issues. - [[User:Tantek|Tantek]] 00:28, 30 October 2009 (UTC)
*#** See [[representative-hcard]] for the resolution of the the representative hCard question.
*#** "authoritative" hCard needs a better definition of the specific question, and documented real world examples where it would be useful. Closing due to lack of provided real world examples.
*#** "canonical" hCard needs a better definition of the specific question, and documented real world examples where it would be useful. Closing due to lack of provided real world examples.
*#** Use "url uid" when linking to a canonical version of the hCard for a specific site - as now documented in [[hcard-authoring#Canonical_hCard_within_a_site|hCard Authoring: canonical hCard within a site]].

* 2006-01-28 raised by [http://rbach.priv.at/Microformats-IRC/2006-01-28#T075222 Tantek on #microformats]
*# ''Is hCard is really appropriate for a named phone bridge, or do we need something else for a named phone numbers that are neither people nor organizations. For example see the "Zakim" hCard on http://www.w3.org/2005/12/allgroupoverview.html''
*#* ACCEPTED BRAINSTORMING. Though hCard has been expanded to allow named locations, those are *physical* locations, and hCard is not really appropriate for named virtual locations (aka virtual addresses) such as a phone number or URL. However, given the use case of having a contact in one's address book for "Zakim" in order to "dial Zakim" as may be recommended in a working group IRC discussion, perhaps Zakim is a virtual entity like an organization. Update (2009-312): I've captured this scenario in [[hcard-brainstorming#named_phone_numbers|hCard brainstorming: named phone numbers]]. The 2005 W3C All Group overview no longer mentions Zakim so this is a past or theoretical example at this point. In addition this question has not come up again, and thus the resolution has been changed from FAQ to BRAINSTORMING, and as captured as such, this issue is closed. [[User:Tantek|Tantek]] 05:05, 9 November 2009 (UTC)

*2006-02-03 raised by Brian
*# We can use the [[geo]] microformat in [[hatom]] to represent GeoRSS element
*#* ACCEPTED DOCUMENTATION. Yes, this should be documented in [[hatom-examples]], and has been moved to [[hatom-brainstorming]] as a suggestion to be explored and written up there accordingly. -Tantek

* 2006-02-13 raised by [http://microformats.org/wiki/User:Eron_Wright Eron Wright]
*# ''Few systems contemplate the altitude component of a coordinate, yet it exists. Altitude becomes important when working with 3D mapping software such as Google Earth. Indeed, the geocoding service that Google Earth uses returns a three-dimensional coordinate. I suggest that hCard provide explicit support for altitude.''
*#* REJECTED POSTPONED. Not in vCard. There is no "altitude" component in vCard (RFC 2426), and thus (certainly for now) there won't be any in hCard. If a new version of vCard were to come out with altitude, then we would add it to hCard. At some point we may also consider adding explicit extensions beyond vCard, but if we were to do so, we would capture them first on the [[hcard-brainstorming]] page. See [[vcard-suggestions#Elevation|vCard suggestions: elevation]], and [[geo-extension-elevation]].

* 2006-02-19 raised by Miika Mäkinen.
*# ''Couldn't the types for tel numbers be specified in a class? Now, for a phone number one needs to add the type as "visible" text, which is not always preferred. For example, type "Work", many times more suitable label could be "Office" or similar and sometimes you might not want to display any type information at all.''
*#* REJECTED TRIED ALREADY. Using class names for the "type" of a tel or adr [http://microformats.org/wiki/hcard-parsing#ISSUE_2 was attempted], and failed in many situations. In addition, the "type" information is actual data, not just a property name, and thus deserves to be in the ''visible'' markup. Note that you can use abbreviations, e.g. <code><nowiki><abbr class="type" title="work">W:</abbr></nowiki></code> in order to present the type in a way that may better fit in with the rest of your presentation. Update (2009-312) see also the [[value-class-pattern]] for how to provide tel 'type' information with other labels. - [[User:Tantek|Tantek]] 05:11, 9 November 2009 (UTC)

* 2006-02-23 raised by [http://www.thefutureoftheweb.com/ Jesse Skinner] and [http://www.thefutureoftheweb.com/blog/2006/1/hcard#comment1 Ben Buchanan].
*# ''Are multiple URLs allowed? The [http://microformats.org/wiki/hcard#Property_List Property List] suggests not, whereas email and tel have multiple type/value pairs. However, the [http://microformats.org/wiki/hcard-parsing#finding_hCard_properties parsing page] suggests multiple URLs are OK. Either way, it seems clear that a type cannot be associated with a URL. So how exactly does hCard deal with multiple URLs?''
*#* RESOLVED FAQ: Multiple URLs are allowed. Some consuming agents (Apple's AddressBook.app among them) don't have an interface for producing multiple URLs, but they are still valid in vCard and therefore hCard. --[[User:RyanKing|RyanKing]] 17:58, 12 Jun 2006 (PDT)
*#* FAQ documented: [[hcard-faq#Can_an_hCard_have_multiple_URLs|hCard FAQ: can an hCard have multiple URLs]]

* 2006-03-07 raised by [http://tantek.com Tantek].
*# ''Issue 1: In 99% of the cases I am finding the need to explicitly do "n" markup, the person has a three word fn which is in the form "given-name additional-name(or initial) family-name". Should we make three word fn's into another shorthand notation to make this easier for authors?''
*#* REJECTED. I have seen sufficient additional cases in systems that have full names but not structured names that have multi-word family names that I think such an algorithm may cause minor data corruption where part of a family-name is interpreted as an additional-name. -Tantek. Update (2009-312). keywords: n shorthand, three word fn shorthand. some examples:
*#** [http://www.vanderwal.net/ Thomas Vander Wal]
*#** [http://hajollyha.net/ Amy van der Hiel]

* 2006-04-06 raised by [[User:Evan|Evan]].
*# ''What is the relationship between the CATEGORY property and [[rel-tag]]? Can you add a tag to an hCard? How can you add a tag to a particular hcard on a page without tagging the other cards on a page?''
*#* ACCEPTED. Categories can optionally be represented as tags. The classname 'category' should always be used, but rel="tag" can optionally be used (in addition to the category classname). In the case that a rel-tag tag is used, the tag (as defined by [[rel-tag]]) is used for the category. Examples: (1) <code><nowiki>food</nowiki></code> and (2) <code><nowiki><a class="category" rel="tag" href="http://example.com/food">Food!</a></nowiki></code>. --[[User:RyanKing|RyanKing]] 15:16, 13 Jun 2006 (PDT)
*#* FAQ: [[hcard-faq#How_are_category_and_rel-tag_related|hCard FAQ: How are category and rel-tag related]]

* 2006-04-10 raised by [[User:ScottReynen|Scott Reynen]].
*# ''When someone looks at the [[hcard|hCard]] pages, one sees no collection of real-world publishing of contact data nor discussion of the properties implied by such examples, I think it's far too easy to infer that microformats come from other formats more than actual behavior. There's nothing on the [[process]] nor the hCard pages explaining this discrepancy. I would argue that there should be an explanation, probably in both places.''
*#* ACCEPTED. Agreed. Part of this is now documented in [[hcard-design-methodology]], but to do: document additional specifics in the [[process]] and [[process-faq]] accordingly. - Tantek. 2009-313 Update by [[User:Tantek|Tantek]] 03:21, 10 November 2009 (UTC) - wrote up additional specifics in:
*#** [[process#Document_Current_Behavior|process: Document Current Behavior]]
*#** [[process-faq#Where_are_the_real-world_publishing_examples_and_analysis_of_properties_implied_in_hCard_and_hCalendar|process FAQ: on hCard on hCalendar]]

* 2006-10-21 raised by [[User:AndyMabbett|Andy Mabbett]]
*# ''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.''
*#* 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)
*#**"''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)
*#*** That scenario demonstrates more of a ''usability'' issue than an ''accessibility'' issue. Also, given that numerous (nearly all?) social network sites (e.g. sites with [[hcard-supporting-user-profiles]]) provide profile pages that link to themselves, this issue (and the above hypothesized user behavior) may be a theoretical misconception, and require data/studies to back it up, since modern accepted practice contradicts this hypothetical issue as currently described.
*#*A: REJECTED THEORETICAL AND MISCONCEPTION. As noted, given that numerous (nearly all?) social network sites (e.g. sites with [[hcard-supporting-user-profiles]]) provide profile pages that link to themselves, the ''usability'' aspect of this issue may be a theoretical misconception, and require data/studies to back it up and thus for now is rejected. As far as any ''accessibility'' issue - if this were truly an accessibility issue, then accessibility tools such as screen readers would unlink/delink or otherwise not make clickable any links from a page to itself, thus solving any such supposed problem at the tool level. If accessibility tools are NOT doing so, that is, leaving pages links to themselves active, then they have likely decided that such links are not an accessibility problem.
*#* A: 2009-313 UPDATE: ACCEPT AUTHORING GUIDELINE. There are three cases to this issue which would help as an [[hcard-authoring]] example to illustrate this issue and provide authoring guidance. Described below, and now added to [[hcard-authoring#URL_of_an_hCard_being_the_page_itself|hCard authoring: URL of an hCard being the page itself]]. Obviously similar techniques can be used for events, reviews etc.
*#** First, as stated above, numerous social network sites' profile pages link to themselves, usually on thumbnail icons, for whatever design reasons they have - whether or not this behavior is (un)desirable is irrelevant to the practicality of marking them up - if a site chooses to do so, it can markup such links with class="url" or perhaps class="url uid".
*#** Second, as of 2009 many (most?) profile pages have some form of live or updating content, and thus it makes functional sense to include a link to the page itself labeled something like "reload" or "refresh". When the user clicks the link, it's not that "nothing happens" as claimed above, but rather, the user is shown new content. If the site provides updates dynamically (e.g. via XHR), then when doing so they can also use javascript+CSS that hides any such manual reload/refresh link.
*#** Third, for profile pages which neither link to themselves as part of their design, nor have any live/updating content, the author can include an empty hyperlink with an empty href attribute (which is resolved as a relative URL to the page itself) to provide an invisible hyperlink to the page itself which is thus both not typically clickable (since it takes up no space), nor has any content which could be erroneously read by a screen reader. E.g. <code><a class="url" href=""></a></code>. This authoring suggestion is probably good enough to handle this third, now perhaps rarest case, though it would be useful to to have some test cases that can be run in various browsers / assistive technologies to see what they do. Another (lengthier) suggestion would be to use [[value-class-pattern]] value-title technique, e.g.: <code><nowiki> </nowiki></code>.

* 2006-11-16 raised by [[User:AndyMabbett|Andy Mabbett]]
*# ''The "type" for "tel" lacks a "textphone" option (for the devices used by, e.g., people who are deaf or have speech difficulties. Example: [http://www.birmingham.gov.uk/contact Birmingham City Council (303 1119)].''
*#*A: REJECTED. This is a vCard issue, as the "type" taxonomy for "tel" is determined by vCard. We are not presently extending hCard beyond the properties and values in vCard.
*#** ''I'm not clear how you can "reject" a provably factual statement. What's the process of suggesting an update to vCard? [[User:AndyMabbett|Andy Mabbett]]''
*#***A: ACCEPTED PARTIAL RESOLVED. Unfortunately it is not clear what the process is for updating vCard. However, we can at least capture suggestions for improvement to vCard from this community which may be helpful once the process for updating vCard is understood. I've created [[vcard-suggestions]] for this purpose and added this suggestion. - Tantek
*#**** The vCard spec is updated by RFC, for example [http://www.rfc-editor.org/rfc/rfc4770.txt RFC 4770]. [[User:AndyMabbett|Andy Mabbett]] 06:22, 12 Jan 2007 (PST)
*#***** A: COLLECTED AND CLOSED. The suggestion has been documented in [[vcard-suggestions]] and it's now up to vCard 4 to see it is adopted or not. If it is, then hCard 1.1 can consider adding it.

* 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 :)''
*#* 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 in-line 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)
*#* Should this be on [[microformats-issues]]? --[[User:WizardIsHungry|Jon Williams]] 13:37, 5 Jan 2007 (PST)
*#** REJECTED. The example you cite is the first of several steps, which refine and improve the first step's suboptimal hCard, not intended as examples for publication.
*#*** The question is: ''why is this considered suboptimal if it is ok to hide the entire card?'''
*#**** REJECTED. It is not OK to hide the entire card.
*#***** Here are a number of examples of hiding the entire card, taken from [[hcard-examples-in-wild]]: [http://www.meryl.net/] [http://www.fberriman.com/] [http://www.fberriman.com/] [http://www.last.fm/user/Crok/?scrobbling=t1] -- Could someone link to where this was discussed and decided in the past, as it seems like this is being governed by fiat. Even if you don't care to have consensus, but could you at least justify this? This stonewalling is rather rude. --[[User:WizardIsHungry|Jon Williams]] 13:24, 9 Jan 2007 (PST)
*#****** ACCEPTED FAQ. This based on the microformats [[principle]] of visibility data is better than invisible data. More documentation is on the microformats [[principles]] page. The [[faq#Q._Given_that_Google_now_looks_at_hidden_content_as_potential_spam.2C_will_invisible_microformats_be_considered_spam.3F|faq also has a related question and answer]].
*#* [[hcard-brainstorming#CSS_Styles]] explicitly permits this. I'm going with what they say.
*#** REJECTED. Note [[hcard-brainstorming#CSS_Styles|that section]] explicitly says: "WARNING: This is very much recommended AGAINST". -Tantek

=== closed 2007 ===
Closed issues that were raised in 2007.

* 2007-01-26 raised by [[User:JamesCraig|JamesCraig]].
*# ''Proposal to use the class attribute for qname prefixed type values (and others such as dtstart values), AKA meta classes.''
<pre><nowiki>
Home (preferred): +1.415.555.1212
Casa (preferido): +1.415.555.1212
</nowiki></pre>
*#* REJECTED DUPLICATE ETC. Class attributes for type values [http://microformats.org/wiki/hcard-parsing#ISSUE_2 was tried and rejected] and in addition, [[qnames-considered-harmful]].
*#* Clarified proposal, leaving REJECTED.

*2007-05-08 raised by Tantek as a result of a message from [[User:AndyMabbett|Andy Mabbett]] on microformats-new
*#''How do you distinguish a '''place''' vs. an '''organization''' hCard, both from the perspective of a publisher (author) wishing to express the particular semantic, and from the perspective of a parser (developer) wishing to discern the difference? This is different from the 2006-12-15 issue on semantic specificity because this issue is *specifically* about place vs. org, rather than conflating that with person.''
*#Note: mailing list post cited in 2006-12-15 issue is quite clear; it says "''when a spider finds an hCard, it can't tell if it is a person, company, organization, or place.''".
*#* DUPLICATE. See 2006-12-15 issue.

=== closed 2008 ===
Closed issues that were raised in 2008.

* 2008-02-07 raised by [[User:AndyMabbett|Andy Mabbett]] in [http://microformats.org/discuss/mail/microformats-discuss/2008-February/011552.html microformats-discuss/2008-February/011552.html]
*# "<code>nickname</code>" and "<code>fn</code>" optimization 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 optimization 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). '''Comment from people fluent in such languages would be welcome.'''
*#* REJECTED DUPLICATE. This is a duplicate of [[hcard-issues-resolved#fn-opt-i18n|previous issue raised by James Craig 2007-03-28]].

* 2008-12-16 raised by [[User:Tantek|Tantek Çelik]]
*# The "n" optimization rule for turning an fn of "WORD C." into an n given-name initial of "C" and family-name of "WORD" should be dropped, as it was not based on sufficient usage in practice (based on why I put it in there in the first place), and (a) it actually interferes with some broad usage in historical practice, e.g. on Pownce user's names were abbrevated as "GIVEN F." where GIVEN was their given-name and F was there family-name initial and (b) may have problems with non-Western name abbreviations also.
*#* suggested resolution: drop respective "n" optimization rule, and suggest markup for any use of abbreviated name components with abbr tag, e.g. <code><nowiki>Tantek <abbr>Ç.</abbr></nowiki></code>
*#** Could retain the rule when a comma or semicolon is found between the two parts though. [[User:TobyInk|TobyInk]] 22:39, 16 December 2008 (UTC)
*#*** At this point, unless sufficient real world sites are documented which use that practice of "a comma or semicolon is between the two parts", it is preferable to drop it, for simplicity. [[User:Tantek|Tantek]] 23:17, 3 June 2009 (UTC)
*#* ACCEPTED. Resolution: Drop "WORD C." "n" optimization rule, noting the past examples of Pownce (formerly at <nowiki>http://pownce.com</nowiki>) and Dodgeball (formerly at <nowiki>http://dodgeball.com/</nowiki>), and the more recent example of [http://foursquare.com/ Foursquare] (originally at http://playfoursquare.com).
*#* CLOSED. Resolution implemented in [[hCard]]. [[User:Tantek|Tantek]] 02:22, 16 April 2010 (UTC)

=== closed 2009 ===
Closed issues that were raised in 2009.
* ...

== see also ==
* [[hcard-issues]]
* [[hcard-issues-resolved]]

microdata

2010-07-19T13:30:33Z

Oli: /* summary */ fixed typo

<entry-title>microdata</entry-title>

<dfn style="font-style:italic;font-weight:bold">microdata</dfn> is an extension to [[HTML5]] that provides another way to embed [[microformats]] and [[poshformats]] vocabularies.

Specification: http://www.w3.org/TR/microdata/

== summary ==
microdata consists of a set of attribute extensions to [[HTML5]]:

* <code>itemprop</code> attribute is a more specific version of <code>class</code>, for field names
* <del><code>subject</code> attribute allows semantically linking within the page. Conceptually similar to the [[include-pattern]].</del>
* <code>itemref</code> attribute allows including properties elsewhere on the page that are not descendants of <code>itemscope</code>. Takes space-separated ids (for example <code>itemref="address phone"</code> would include the elements with <code>id="address"</code> and <code>id="phone"</code>). Conceptually similar to the [[include-pattern]].
* <code>content</code> attribute on the <code>meta</code> element can be used to include invisible data that is not part of the content. As current browsers move <code>meta</code> inside <code><head></code>, make sure to include via <code>itemref</code>. Conceptually similar to the 'value-title' feature of the [[value-class-pattern]].
* <code>itemscope</code> attribute identifies blocks to be marked as structured data. Conceptually similar to the [[mfo]] brainstorming.
* <code>itemtype</code> attribute to specify the type for an item (for example: <code><nowiki>itemtype="http://microformats.org/profile/hcard"</nowiki></code>)

For common semantics on the web (e.g. [[hcard|people+organizations]], [[hcalendar|events]], [[hreview|reviews]], [[hatom|syndicated content]]), [[microformats]] are still simpler and easier than [[microdata]], and are already well implemented across numerous tools and services.

For uncommon, rare, experimental, or one-off semantics, [[microdata]] offers a simpler and easier to understand solution than alternatives that use [[namespaces]] like XML/RDF/RDFa. Developers should consider [[microdata]] as another way of expressing semantics that they may otherwise use [[poshformats]] for.

== history ==
microdata didn't happen overnight. Much of the design and simplicity of microdata is based on years of work on microformats [[principles]] deliberately designed to help guide and create simpler, more usable and accessible solutions. It happened so quickly because Ian Hickson designed microdata based upon years of work by both the microformats community, and the concept of using reverse-domain-names as unique qualifiers (popularized perhaps by Java programming language naming conventions).

== potential ==
I think there are some very clever ideas in general purpose microdata, it has a lot of potential, and despite being a bit more abstract than microformats, still much simpler/easier to explain to web designers/developers/programmers than any form of RDF.

General microdata may be the right solution to the general purpose data representation problem that microformats specifically chose not to work on.

- [[User:Tantek|Tantek]] 17:42, 22 August 2009 (UTC)

== microdata vocabularies ==
Separate from the [[microdata]] specification, there are a number of microdata vocabularies, based on microformats and previous formats like vCard and iCalendar.

=== microdata vCard vocabulary ===
Formerly documented as a separate specification at <nowiki>http://dev.w3.org/html5/mdvcard/</nowiki>, the microdata vCard vocabulary is currently available as [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#vcard part of WHATWG additions to HTML5].

* Recommendation: use [[hCard]] directly instead, taking into account:
** the [[hcard-faq|hCard FAQ]] and
** [[hcard-issues-resolved|resolved]]+[[hcard-issues-closed|closed issues]].

hCard 1.0.1 (under development) is incorporating these errata.

Using hCard will produce Google Rich Snippets, as well as work with [[yahoo-search]], and [[Firefox]] [[Operator]] and other tools.

Note:
* Avoid the "microdata vCard vocabulary" as in many ways it is an out-of-date fork/snapshot of hCard, even though portions of it appear to based directly on the vCard RFC. as well.
* Avoid Google’s Rich Snippets vocabularies ([http://www.data-vocabulary.org/Person/ Person] and [http://www.data-vocabulary.org/Organization/ Organization]), which are also forks of hCard/vCard, and are only implemented by Google currently.

=== microdata vEvent vocabulary ===
Formerly documented as a separate specification at <nowiki>http://dev.w3.org/html5/mdvevent/</nowiki>, the microdata vEvent vocabulary is currently available as [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#vevent part of WHATWG additions to HTML5].

* Recommendation: use [[hCalendar]] directly instead, taking into account:
** the [[hcalendar-faq|hCalendar FAQ]] and
** [[hcalendar-issues-resolved|resolved]]+[[hcalendar-issues-closed|closed issues]].

hCalendar 1.0.1 (under development) is incorporating these errata.

Using hCalendar will produce Google Rich Snippets, as well as work with [[yahoo-search]], and [[Firefox]] [[Operator]] and other tools.

Note:
* Avoid the "microdata vEvent vocabulary" as in many ways it is an out-of-date fork/snapshot of hCalendar's vevent root class name and applicable properties, even though portions of it appear to based directly on the iCalendar RFC.
* Avoid Google’s Rich Snippets vocabulary ([http://www.data-vocabulary.org/Event/ Event]), which is also a fork of hCalendar/iCalendar, and are only implemented by Google currently.

=== microdata Licensing Works vocabulary ===
Formerly documented as a separate specification at <nowiki>http://dev.w3.org/html5/mdwork/</nowiki>, the microdata Licensing Works vocabulary is currently available as [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#licensing-works part of WHATWG additions to HTML5].

The [[licensing]] microformat work provides a potential microformat alternative to the microdata Licensing Works vocabulary.

Please see: [[licensing-brainstorming]] and provide feedback.

== microformats in microdata ==
For those that are ok with going with an [[HTML5]] only solution, it may be interesting to consider and document a consistent way to use microformats and microformats vocabulary in microdata.

(needs expansion with examples)
...

== alternatives ==
Since the introduction of [[XMDP]], web authors have been able to define their specific uses of rel attribute values and class names.

(needs expansion with examples)
...

== see also ==
* [[HTML5]]
* [[poshformats]]
* [[principles]]
* [[XMDP]]

microdata

2010-07-13T16:54:08Z

Oli: /* microdata vEvent vocabulary */ remove typo

<entry-title>microdata</entry-title>

<dfn style="font-style:italic;font-weight:bold">microdata</dfn> is an extension to [[HTML5]] that provides another way to embed [[microformats]] and [[poshformats]] vocabularies.

Specification: http://www.w3.org/TR/microdata/

== summary ==
microdata consists of a set of attribute extensions to [[HTML5]]:

* <code>itemprop</code> attribute is a more specific version of <code>class</code>, for field names
* <del><code>subject</code> attribute allows semantically linking within the page. Conceptually similar to the [[include-pattern]].</del>
* <code>itemref</code> attribute allows including properties elsewhere on the page that are not descendants of <code>itemscope</code>. Takes space-separated ids (for example <code>itemref="address phone"</code> would include the elements with <code>id="address"</code> and <code>id="phone"</code>). Conceptually similar to the [[include-pattern]].
* <code>content</code> attribute on the <code>meta</code> element can be used to include invisible data that is not part of the content. As current browsers move <code>meta</code> inside <code><head></code>, make sure to include via <code>itemref</code>. Conceptually similar to the 'value-title' feature of the [[value-class-pattern]].
* <code>itemscope</code> attribute identifies blocks to be marked as structured data. Conceptually similar to the [[mfo]] brainstorming.
* <code>itemtype</code> attribute to specify the type for an item (for example: <code><nowiki>itemtype="http://microformats.org/profile/hcard"</nowiki></code>)

For common semantics on the web (e.g. [[hcard|people+organizations]], [[hcalendar|events]], [[hreview|reviews]], [[hatom|syndicated content]]), [[microformats]] are still simpler and easier than [[microdata]], as well already well implemented across numerous tools and services.

For uncommon, rare, experimental, or one-off semantics, [[microdata]] offers a simpler and easier to understand solution than alternatives that use [[namespaces]] like XML/RDF/RDFa. Developers should consider [[microdata]] as another way of expressing semantics that they may otherwise use [[poshformats]] for.

== history ==
microdata didn't happen overnight. Much of the design and simplicity of microdata is based on years of work on microformats [[principles]] deliberately designed to help guide and create simpler, more usable and accessible solutions. It happened so quickly because Ian Hickson designed microdata based upon years of work by both the microformats community, and the concept of using reverse-domain-names as unique qualifiers (popularized perhaps by Java programming language naming conventions).

== potential ==
I think there are some very clever ideas in general purpose microdata, it has a lot of potential, and despite being a bit more abstract than microformats, still much simpler/easier to explain to web designers/developers/programmers than any form of RDF.

General microdata may be the right solution to the general purpose data representation problem that microformats specifically chose not to work on.

- [[User:Tantek|Tantek]] 17:42, 22 August 2009 (UTC)

== microdata vocabularies ==
Separate from the [[microdata]] specification, there are a number of microdata vocabularies, based on microformats and previous formats like vCard and iCalendar.

=== microdata vCard vocabulary ===
Formerly documented as a separate specification at <nowiki>http://dev.w3.org/html5/mdvcard/</nowiki>, the microdata vCard vocabulary is currently available as [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#vcard part of WHATWG additions to HTML5].

* Recommendation: use [[hCard]] directly instead, taking into account:
** the [[hcard-faq|hCard FAQ]] and
** [[hcard-issues-resolved|resolved]]+[[hcard-issues-closed|closed issues]].

hCard 1.0.1 (under development) is incorporating these errata.

Using hCard will produce Google Rich Snippets, as well as work with [[yahoo-search]], and [[Firefox]] [[Operator]] and other tools.

Note:
* Avoid the "microdata vCard vocabulary" as in many ways it is an out-of-date fork/snapshot of hCard, even though portions of it appear to based directly on the vCard RFC. as well.
* Avoid Google’s Rich Snippets vocabularies ([http://www.data-vocabulary.org/Person/ Person] and [http://www.data-vocabulary.org/Organization/ Organization]), which are also forks of hCard/vCard, and are only implemented by Google currently.

=== microdata vEvent vocabulary ===
Formerly documented as a separate specification at <nowiki>http://dev.w3.org/html5/mdvevent/</nowiki>, the microdata vEvent vocabulary is currently available as [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#vevent part of WHATWG additions to HTML5].

* Recommendation: use [[hCalendar]] directly instead, taking into account:
** the [[hcalendar-faq|hCalendar FAQ]] and
** [[hcalendar-issues-resolved|resolved]]+[[hcalendar-issues-closed|closed issues]].

hCalendar 1.0.1 (under development) is incorporating these errata.

Using hCalendar will produce Google Rich Snippets, as well as work with [[yahoo-search]], and [[Firefox]] [[Operator]] and other tools.

Note:
* Avoid the "microdata vEvent vocabulary" as in many ways it is an out-of-date fork/snapshot of hCalendar's vevent root class name and applicable properties, even though portions of it appear to based directly on the iCalendar RFC.
* Avoid Google’s Rich Snippets vocabulary ([http://www.data-vocabulary.org/Event/ Event]), which is also a fork of hCalendar/iCalendar, and are only implemented by Google currently.

=== microdata Licensing Works vocabulary ===
Formerly documented as a separate specification at <nowiki>http://dev.w3.org/html5/mdwork/</nowiki>, the microdata Licensing Works vocabulary is currently available as [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#licensing-works part of WHATWG additions to HTML5].

The [[licensing]] microformat work provides a potential microformat alternative to the microdata Licensing Works vocabulary.

Please see: [[licensing-brainstorming]] and provide feedback.

== microformats in microdata ==
For those that are ok with going with an [[HTML5]] only solution, it may be interesting to consider and document a consistent way to use microformats and microformats vocabulary in microdata.

(needs expansion with examples)
...

== alternatives ==
Since the introduction of [[XMDP]], web authors have been able to define their specific uses of rel attribute values and class names.

(needs expansion with examples)
...

== see also ==
* [[HTML5]]
* [[poshformats]]
* [[principles]]
* [[XMDP]]

html5

2010-07-12T14:51:53Z

Oli: /* microdata */ fixed itemref presentation, added example

<entry-title>Microformats in HTML 5</entry-title>

''This page is to document '''future''' use of microformats in [http://www.w3.org/html/wg/html5 HTML 5]. None of the items documented are supported now, and may change upon proper development within the microformats community, or changes in the HTML 5 specification. This page is to track HTML5 enabled enhancements to microformats, and issues that HTML5 raises. It may be used to track issues which we need to push back into the HTML 5 development process.''

If there are things that Microformats would like to mark up that aren't handled by HTML5 explicitly, please let the WHATWG know, so we can improve HTML5. This is how <code>time</code> came to be, for instance.

==New features in HTML5==

=== time element ===
'''<code>time</code> element for representing date times'''. In HTML5, the machine form of datetimes can be represented natively. It should be possible to replace the date-time design pattern with native HTML.
* <code>time</code> takes an optional <code>pubdate</code> attribute, to indicate the publication date of an <code>article</code>. Synonymous with [[hAtom]] <code>published</code>, may imply [[hAtom]] <code>updated</code>, may imply [[hReview]] <code>dtreviewed</code>, may imply [[hListing]] <code>dtlisted</code>

=== article element ===
'''<code>article</code>''' element for major, independent compositions of content within a page. Perhaps synonymous with [[hAtom]] <code>hentry</code>. Could be parsed as <code>hentry</code> within explicit <code>hfeed</code> blocks?

=== microdata ===
'''[[microdata]]'''. HTML5 provides a set of attributes and associated DOM APIs for extracting data from web pages.
* <code>itemprop</code> attribute is a more specific version of <code>class</code>, for field names
* <del><code>subject</code> attribute allows semantically linking within the page. Conceptually similar to the [[include-pattern]].</del>
* <code>itemref</code> attribute allows including properties elsewhere on the page that are not descendants of <code>itemscope</code>. Takes space-separated ids (for example <code>itemref="address phone"</code> would include the elements with <code>id="address"</code> and <code>id="phone"</code>). Conceptually similar to the [[include-pattern]].
* <code>content</code> attribute on the <code>meta</code> element can be used to include data that is not part of the content. As current browsers move <code>meta</code> inside <code><head></code>, make sure to include via <code>itemref</code>. Conceptually similar to the [[value-class-pattern]].
* <code>itemscope</code> attribute identifies blocks to be marked as structured data. Conceptually similar to the [[mfo]] brainstorming?
* <code>itemtype</code> attribute to specify the type for an item (for example: <code><nowiki>itemtype="http://microformats.org/profile/hcard"</nowiki></code>)

==== microdata vocabularies ====
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#vcard microdata vCard] - this is based directly on vCard. Alternatively use Google’s Rich Snippets vocabularies ([http://www.data-vocabulary.org/Person/ Person] and [http://www.data-vocabulary.org/Organization/ Organization]), which are simplified versions also based on vCard
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#vevent microdata vEvent] - this is based directly on iCalendar. Alternatively use Google’s Rich Snippets vocabulary ([http://www.data-vocabulary.org/Event/ Event]), which is a simplified version also based on iCalendar
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#licensing-works microdata Licensing Works] - see also [[licensing-brainstorming]]

=== data attributes ===
'''<code>data-</code> naming convention for tag attributes'''. the draft specification states that any attribute that starts with "data-" will be treated as a storage area for private data.
* Note that the data-* stuff is explicitly not for microformats. Those attributes are defined in such a way that browsers will never do anything special with them, ever. They are intended for script authors to have a space in which they can play without ever clashing with anything the browser does. There may be some cases of private [[poshformats]] that are never intended for interchange that may be used in data-* attributes.

== Current microformat compatibility ==
There seems to be no issue with current implementation of the following microformats in HTML 5:
* [[hcard]]
* [[xfn]]

== Requests ==
* "how to use with HTML5" sections that include (a) microformats examples that use [[HTML5]], and (b) microformats parsing details that specify what to do (if anything special is required) with HTML5 elements (e.g. how to parse the <code>time</code> element for dates and times for microformats). See (and add to if necessary) :
** [[hcard-brainstorming#how_to_use_with_HTML5|hCard brainstorming - how to use with HTML5]]
** [[hcalendar-brainstorming#how_to_use_with_HTML5|hCalendar brainstorming - how to use with HTML5]] e.g. hCalendar with the <code>time</code> element
** [[citation-brainstorming#how_to_use_with_HTML5|citation brainstorming - how to use with HTML5]]
** if nothing special is required for HTML5, then after performing the analysis, that should be noted as well, for the purpose of clarity.

==Issues==
<div class='discussion issues'>
* '''The <code>rev</code> attribute has been removed'''. In HTML5, <code>rel</code> and <code>rev</code> are no-longer paired, and the <code>rel</code> attribute nolonger describes the direction of a relationship. Microformats which use <code>rev</code> will need to use <code>rel</code> instead.
** Or something like data-rev="vote-for"
*** As above, <code>data-</code> attributes are for application-context functionality, ''not'' shared vocabularies. Further, the HTML5 specification makes <code>rel</code> the correct attribute to use, regardless of direction, through the changed specification. --[[User:BenWard|BenWard]] 17:53, 12 May 2009 (UTC)
* '''The <code>profile</code> attribute has been removed'''. In HTML, the <code>profile</code> attribute from the <code>head</code> has been removed, with no direct replacement. This causes issues for GRDDL support. It's been suggested that profile URLs be represented in <code>link</code> elements instead, or even as a custom HTTP header. See [[grddl]] and [[profile-uris]]
** See [[rel-profile]] which is the replacement for the profile attribute. [[User:Tantek|Tantek]] 23:24, 5 November 2009 (UTC)
* '''Microdata <code>itemprop</code> duplicates <code>class</code> data'''. the new attribute itemprop is designed to hold some meaningful data about an element, but class already exists to hold this data. Unsure of reasons why itemprop required?
** This is because microdata is designed to be generically parsable, even when the parser does not understand the vocabulary. As such, property names have to be on an explicit attribute, not shared with other, non-data classnames. --[[User:BenWard|BenWard]] 21:12, 4 September 2009 (UTC)
* '''The [http://microformats.org/wiki/value-class-pattern#Date_and_time_parsing recommended removal of the colon in timezone] doesn’t validate''' The relevant uF wiki text is “However the colons ":" separating the hours and minutes of any timezone offset are optional and discouraged in order to make it less likely that a timezone offset will be confused for a time.” ref: [http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#global-dates-and-times HTML5 time microsyntax for <time>] --[[User:Oli|Oli]] 14:40, 14 February 2010 (+9)
</div>

== see also ==
* [[HTML3]]

html5

2010-07-12T14:48:23Z

Oli: /* microdata */ updated attribute definitions and uses, changed microdata vocabulary links to working versions, removed out-of-date warnings about using microdata vocabularies

<entry-title>Microformats in HTML 5</entry-title>

''This page is to document '''future''' use of microformats in [http://www.w3.org/html/wg/html5 HTML 5]. None of the items documented are supported now, and may change upon proper development within the microformats community, or changes in the HTML 5 specification. This page is to track HTML5 enabled enhancements to microformats, and issues that HTML5 raises. It may be used to track issues which we need to push back into the HTML 5 development process.''

If there are things that Microformats would like to mark up that aren't handled by HTML5 explicitly, please let the WHATWG know, so we can improve HTML5. This is how <code>time</code> came to be, for instance.

==New features in HTML5==

=== time element ===
'''<code>time</code> element for representing date times'''. In HTML5, the machine form of datetimes can be represented natively. It should be possible to replace the date-time design pattern with native HTML.
* <code>time</code> takes an optional <code>pubdate</code> attribute, to indicate the publication date of an <code>article</code>. Synonymous with [[hAtom]] <code>published</code>, may imply [[hAtom]] <code>updated</code>, may imply [[hReview]] <code>dtreviewed</code>, may imply [[hListing]] <code>dtlisted</code>

=== article element ===
'''<code>article</code>''' element for major, independent compositions of content within a page. Perhaps synonymous with [[hAtom]] <code>hentry</code>. Could be parsed as <code>hentry</code> within explicit <code>hfeed</code> blocks?

=== microdata ===
'''[[microdata]]'''. HTML5 provides a set of attributes and associated DOM APIs for extracting data from web pages.
* <code>itemprop</code> attribute is a more specific version of <code>class</code>, for field names
* <del><code>subject</code> attribute allows semantically linking within the page. Conceptually similar to the [[include-pattern]].</del>
* <code><itemref="" /></code> allows including properties elsewhere on the page that are not descendants of <code>itemscope</code>. Takes space-separated ids. Conceptually similar to the [[include-pattern]].
* <code>content</code> attribute on the <code>meta</code> element can be used to include data that is not part of the content. As current browsers move <code>meta</code> inside <code><head></code>, make sure to include via <code>itemref</code>. Conceptually similar to the [[value-class-pattern]].
* <code>itemscope</code> attribute identifies blocks to be marked as structured data. Conceptually similar to the [[mfo]] brainstorming?
* <code>itemtype</code> attribute to specify the type for an item (for example: <code><nowiki>itemtype="http://microformats.org/profile/hcard"</nowiki></code>)

==== microdata vocabularies ====
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#vcard microdata vCard] - this is based directly on vCard. Alternatively use Google’s Rich Snippets vocabularies ([http://www.data-vocabulary.org/Person/ Person] and [http://www.data-vocabulary.org/Organization/ Organization]), which are simplified versions also based on vCard
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#vevent microdata vEvent] - this is based directly on iCalendar. Alternatively use Google’s Rich Snippets vocabulary ([http://www.data-vocabulary.org/Event/ Event]), which is a simplified version also based on iCalendar
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#licensing-works microdata Licensing Works] - see also [[licensing-brainstorming]]

=== data attributes ===
'''<code>data-</code> naming convention for tag attributes'''. the draft specification states that any attribute that starts with "data-" will be treated as a storage area for private data.
* Note that the data-* stuff is explicitly not for microformats. Those attributes are defined in such a way that browsers will never do anything special with them, ever. They are intended for script authors to have a space in which they can play without ever clashing with anything the browser does. There may be some cases of private [[poshformats]] that are never intended for interchange that may be used in data-* attributes.

== Current microformat compatibility ==
There seems to be no issue with current implementation of the following microformats in HTML 5:
* [[hcard]]
* [[xfn]]

== Requests ==
* "how to use with HTML5" sections that include (a) microformats examples that use [[HTML5]], and (b) microformats parsing details that specify what to do (if anything special is required) with HTML5 elements (e.g. how to parse the <code>time</code> element for dates and times for microformats). See (and add to if necessary) :
** [[hcard-brainstorming#how_to_use_with_HTML5|hCard brainstorming - how to use with HTML5]]
** [[hcalendar-brainstorming#how_to_use_with_HTML5|hCalendar brainstorming - how to use with HTML5]] e.g. hCalendar with the <code>time</code> element
** [[citation-brainstorming#how_to_use_with_HTML5|citation brainstorming - how to use with HTML5]]
** if nothing special is required for HTML5, then after performing the analysis, that should be noted as well, for the purpose of clarity.

==Issues==
<div class='discussion issues'>
* '''The <code>rev</code> attribute has been removed'''. In HTML5, <code>rel</code> and <code>rev</code> are no-longer paired, and the <code>rel</code> attribute nolonger describes the direction of a relationship. Microformats which use <code>rev</code> will need to use <code>rel</code> instead.
** Or something like data-rev="vote-for"
*** As above, <code>data-</code> attributes are for application-context functionality, ''not'' shared vocabularies. Further, the HTML5 specification makes <code>rel</code> the correct attribute to use, regardless of direction, through the changed specification. --[[User:BenWard|BenWard]] 17:53, 12 May 2009 (UTC)
* '''The <code>profile</code> attribute has been removed'''. In HTML, the <code>profile</code> attribute from the <code>head</code> has been removed, with no direct replacement. This causes issues for GRDDL support. It's been suggested that profile URLs be represented in <code>link</code> elements instead, or even as a custom HTTP header. See [[grddl]] and [[profile-uris]]
** See [[rel-profile]] which is the replacement for the profile attribute. [[User:Tantek|Tantek]] 23:24, 5 November 2009 (UTC)
* '''Microdata <code>itemprop</code> duplicates <code>class</code> data'''. the new attribute itemprop is designed to hold some meaningful data about an element, but class already exists to hold this data. Unsure of reasons why itemprop required?
** This is because microdata is designed to be generically parsable, even when the parser does not understand the vocabulary. As such, property names have to be on an explicit attribute, not shared with other, non-data classnames. --[[User:BenWard|BenWard]] 21:12, 4 September 2009 (UTC)
* '''The [http://microformats.org/wiki/value-class-pattern#Date_and_time_parsing recommended removal of the colon in timezone] doesn’t validate''' The relevant uF wiki text is “However the colons ":" separating the hours and minutes of any timezone offset are optional and discouraged in order to make it less likely that a timezone offset will be confused for a time.” ref: [http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#global-dates-and-times HTML5 time microsyntax for <time>] --[[User:Oli|Oli]] 14:40, 14 February 2010 (+9)
</div>

== see also ==
* [[HTML3]]

User:Oli

2010-07-12T14:28:11Z

Oli: adding twitter handle

Oli Studholme I’m interested in HTML5, and live in Japan. I blog at [http://oli.jp/ Oli.jp] and am @[http://twitter.com/boblet boblet] on Twitter.

assistive-technology

2010-05-30T22:52:07Z

Oli: Adding more recent accessibility UA statistics

<h1>assistive technology</h1>

This page is for documenting currently known [[accessibility]] assistive technologies (implementations) that are being used in the wild for the purpose of testing any particular microformats and microformats techniques to determine their impact on assistive technologies.

__TOC__

== What to add ==

=== Only accessible assistive technologies ===
Rather than duplicating lists elsewhere on the Web (e.g. [http://en.wikipedia.org/wiki/Comparison_of_screen_readers Wikipedia's Comparison of screen readers]), please only add assistive technologies that you, or someone you know (such as a user of an assistive technology that you are in touch with) has access to for testing purposes. This will help keep the testing "real world" on an ongoing basis, because if no one has access to an assistive technology, then testing it is an unreasonable (purely theoretical) expectation.

=== Please provide ===
When adding an assistive technology to the list(s) below, please provide:
* Your name / name of person who has access to the assistive technology for testing purposes
* Name of assistive technology
* URL to home page for the technology, and URL(s) to purchase if available
* version number
* when published/released
* estimated number of users if known (even rough estimates are ok), along with date of estimate (ideally with a citation).

=== Note their bugs too ===
In addition, by keep tracking of various different assistive technologies, their versions, their bugs/shortcomings, and any non-standards-compliant behavior, especially when such behavior interferes with microformats on the page, we can focus our efforts on suggesting improvements for them accordingly.

== Screen Readers ==
General marketshare numbers for screen readers:
* 2003 USA: JAWS 65%, GW-Micro Window-Eyes 35%. According to [http://www.redish.net/content/papers/interactions.html a study of screen reader use published in December 2003], a spokesperson for the US National Federation of the Blind estimated that in the USA, JAWS had 65% of the screen reader market and GW-Micro Window-Eyes had 35%; also JAWS was the software most commonly used by U.S. federal workers.
* [http://webaim.org/projects/screenreadersurvey2/ 2009 WebAIM survey]: Primary screen reader; JAWS 66%, Window-Eyes 10%. Commonly used screen readers; JAWS 75%, NVDA 26%, Window-Eyes 24%, SA or SAToGo 23% (note that NVDA may have inflated usage here due to some recipients being sighted developers using it to test content)

=== JAWS ===
Publisher: Freedom Scientific
Total users as of 2002: [http://web.archive.org/web/20021015235548/http://www.microsoft.com/presspass/trial/mswitness/2002/hofstader.asp "There are approximately 80,000 registered users of JAWS"] - Chris Hofstader of Freedom Scientific. Presumably world-wide users of any version of JAWS.

It might be a good idea to consult [http://www.freedomscientific.com/fs_products/JAWS_UserGroups.asp JAWS user groups].

==== Testing possibilities ====
You can download demo versions of JAWS that are limited to run for about half an hour per Windows session. Unfortunately, Freedom Scientific considers testing web standards support in JAWS demos to be a breach of its EULA. Alternative, you could submit a test-case to end users at one of the [http://www.freedomscientific.com/fs_support/User_Groups.asp JAWS mailing lists].

==== Documentation ====
*[http://www.freedomscientific.com/fs_support/doc_screenreaders.asp Official manuals].
*[http://www.freedomscientific.com/fs_products/Surfs_Up/_Surfs_Up_Start_Here.htm Official tutorial about surfing the web with JAWS].

==== Extensibility ====
JAWS is scriptable, and some scripts attempt to improve web access, such as Jamal Mazrui's [http://www.freelists.org/archives/guispeak/04-2007/msg00010.html HomerKit].

==== Release notes ====
* [http://www.freedomscientific.com/fs_products/software_jaws80fea.asp JAWS 8] (November 2006).
* [http://www.freedomscientific.com/fs_products/software_jaws710fea.asp JAWS 7.10] (June 2006).
* [http://www.freedomscientific.com/fs_products/software_jaws70fea.asp JAWS 7] (October 2005). Perhaps the most commonly used version of JAWS).
* [http://www.freedomscientific.com/fs_products/software_jaws620fea.asp JAWS 6.2]. Seemingly the [http://www.kanhan.com/jaws/ last version of JAWS adapted for use in China] (see also [http://www.kanhan.com/webpage/eng/E_news.php?news=51 English summary]).
* [http://www.freedomscientific.com/fs_products/software_jaws610fea.asp JAWS 6.1].
* [http://www.freedomscientific.com/fs_products/software_jaws60intro.asp JAWS 6] (2005). Many JAWS-related mailing list correspondents use a version of 6.
* [http://www.freedomscientific.com/fs_products/software_jaws510intro.asp JAWS 5.1] (2004).
* [http://www.freedomscientific.com/fs_products/software_jaws5intro.asp JAWS 5] (2004). A few correspondents use 5 or earlier.
* [http://www.freedomscientific.com/fs_downloads/DL_JAWS451.asp JAWS 4.51] This is the earliest version recently spotted on JAWS-related mailing lists.

=== GW Micro Window-Eyes ===

==== Test possibilities ====
Volunteer testers: Benjamin Hawkes-Lewis (webdev not user).

Like Freedom Scientific, [http://www.gwmicro.com/Window-Eyes/Demo/ GW-Micro offer an otherwise fully-functional demo] of their latest release which can only be run for about half an hour per Windows session. Unlike Freedom Scientific, [http://www.gwmicro.com/Developers/ GW-Micro encourage developers to test with the demo]. You can also download the demo for an earlier version, 5.5, from [http://www.beyondsight.com/demo.htm Beyond Sight].

Alternatively, you could submit a test-case to one of the [http://www.gwmicro.com/Support/Email_Lists/ Window-Eyes users' mailing lists], as [http://www.gwmicro.com/Developers/Web/ suggested by GW-Micro themselves].

==== Extensibility ====
Window-Eyes "set files" map functionality to applications.

==== Documentation ====
*[http://www.gwmicro.com/Window-Eyes/Manual/HTML/ Official manual].
*[http://www.gwmicro.com/Support/Knowledge_Base/?kbnumber=GWKB1040 Window-Eyes and Firefox Extensions].
*[http://www.gwmicro.com/Support/Knowledge_Base/?kbnumber=GWKB1044 Window-Eyes and ActiveX].
*[http://www.gwmicro.com/Audio_Video_Archive/Window-Eyes_Tutorials/ MP3 tutorials].
*[http://www.gwmicro.com/Developers/Web/ Information for web developers].

==== Release Notes ====

* [http://www.gwmicro.com/Window-Eyes/Version_History/ Release notes for most versions].

=== MicroPower Virtual Vision ===
Brazilian screen reader.

==== Userbase ====
The [http://br.groups.yahoo.com/group/vv-l/ Yahoo! Group devoted to Virtual Vision] has 226 members (as of 2007-05-01).

==== Testing possibilites ====
Submit a testcase to the [http://www.micropower.com.br/v3/pt/acessibilidade/lista.asp Virtual Vision mailing list].

==== Release notes ====
*[http://www.micropower.com.br/v3/pt/acessibilidade/vv5/index.asp Virtual Vision 5.5]

=== PC-Talker ===
Japanese screen reader.

==== Userbase ====
Along with 95 Reader, PC-Talker is more commonly used than the Japanese edition of JAWS, according to [http://www.w4a.info/2006/prog/6-watanabe.pdf Takayuki Watanabe and Masahiro Umegaki, Capability Survey of Japanese User Agents and Its Impact on Web Accessibility (2006) (PDF)].

==== Test possibilities ====
Probably the best bet would be to contact Watanabe.

==== Documentation ====
*[http://www.aok-net.com/products/pctalker.htm Kochi System Development PC-Talker]

=== 95 Reader ===
Japanese screen reader.

==== Userbase ====
Along with PC-Talker, 95 Reader is more commonly used than the Japanese edition of JAWS, according to [http://www.w4a.info/2006/prog/6-watanabe.pdf Takayuki Watanabe and Masahiro Umegaki, Capability Survey of Japanese User Agents and Its Impact on Web Accessibility (2006) (PDF)].

==== Test possibilities ====
Probably the best bet would be to contact Watanabe.

==== Documentation ====
* [http://www.ssct.co.jp/barrierfree/95reader/ 95 Reader]

== See Also ==
* [[accessibility]]
* [[assistive-technology-abbr-results]]
* [[include-pattern-feedback#Test_Results_from_Yahoo.21_Accessibility|Test Results from Yahoo! Accessibility]]

presentations

2010-02-21T14:01:57Z

Oli: adding link to "Microformats & Microdata" presentation slides

{{TOC-right}}
This page lists various presentations, sessions, papers and posters which have provided explanations and discusions of both [[microformats]] in general, and specific microformats. Check out microformats [[events]] for upcoming presentations. See also microformats [[podcasts]] and [[screencasts]] for audio/video presentations and discussions.

'''Note: This page is missing a lot of presentation links.''' More presentation links can be found by going through specific [[events]] pages.

Most recent presentations/sessions listed first.

== 2010 ==
* 2010-02-17 <cite>[http://oli.jp/slides/microformats-microdata Microformats & Microdata]</cite> presentation by [http://oli.jp/ Oli Studholme] ([http://twitter.com/boblet @boblet]) for [http://atnd.org/events/3058 第３回 Webkit/HTML5 勉強会] in Tokyo, Japan ([[events/2010-02-17-webkit-html5-benkyokai|more info]]) (the presentation was in Japanese, the slides are mainly English)

== 2009 ==
* 2009-12-04 <cite>[http://codebits.eu/intra/s/session/79 Re-using social media data]</cite> presentation by Glenn Jones at SAPO Codebits Lisbon, Portugal

* 2009-06-03 <cite lang="pt">[http://e.yq.sl.pt/ Microformatos - 2009 - Juntando as Peças do Puzzle]</cite> by [http://twitter.com/andr3 André Luís] at SAPO Sessions ([http://twitter.com/andr3/status/2017551933 as tweeted by @andr3])

* 2009-03-12 [http://csarven.ca/presentations/microformats-06/ microformats: #towerofbabel #pareto #dataportability] presentation by [[User:Csarven|Sarven Capadisli]] at [http://mcgill.ca GLIS 663 Knowledge Taxonomies, McGill], Montréal, Canada

* 2009-03-05 [http://csarven.ca/presentations/microformats-05/ Website data through the looking-glass] presentation by [[User:Csarven|Sarven Capadisli]] at [http://conf.phpquebec.com PHP Québec Conference 2009], Montréal, Canada

* 2009-01-08 [http://csarven.ca/presentations/microformats-04/ Interacting with microformats] presentation by [[User:Csarven|Sarven Capadisli]] at [http://phpquebec.org PHP Québec Monthly Meetup], Montréal, Canada

== 2008 ==
* 2008-11-18 [http://cdharrison.com/presentations/microformats/ microformats: What are they and why should you use them?] during [http://refreshaugusta.com/ RefreshAugusta] at PowerServe, Augusta, Georgia.
* 2008-09-05 [http://tantek.com/presentations/2008/09/social-network-portability Social Network Portability] during [[events/2008-09-05-dconstruct-social-network-portability|dConstruct 2008]].
* 2008-08-19 [http://tantek.com/presentations/2008/08/microformats Better User Experience Through Microformats] during day 2 of [[events/2008-08-19-better-user-experience|An Event Apart San Francisco]].
* 2008-08-16 [http://tantek.com/presentations/2008/08/wordpress-microformats/ WordPress and Microformats: Past, Present, Future] during [[events/2008-08-16-wordcamp|WordCamp 2008]]
* 2008-07-02 [http://www.slideshare.net/andr3/microformatos-pequenas-peas-do-puzzle Microformatos - pequenças peças do puzzle] presentation in Portuguese, by André Luís for a training session at SAPO.pt (Lisbon, Portugal)
* 2008-05-15 [http://csarven.ca/presentations/microformats-03/ Creating next generation Web sites] presentation by [[User:Csarven|Sarven Capadisli]] at [http://www.nstein.com/summit2008/ Nstein Innovation Leaders Summit 2008], Montreal, Canada
* 2008-04-16 [http://slideshow.rubyforge.org/microformats.html Microformats - Adding Semantics to Your Web Site - Web 3.0 in Action] presentation by Gerald Bauer (Vancouver Software Developers Network/VanDev at University of British Columbia)
* 2008-03-17 [http://csarven.ca/presentations/microformats-02/ Microformats overview: how to help machines recognise common data formats in Web documents] presentation by [[User:Csarven|Sarven Capadisli]] at [http://station-c.com/ Coder's Saturday], Montreal, Canada
* 2008-02-19 [http://www.glennjones.net/Post/835/SemanticCampLondon.htm Can your website be your API and real life] presentation by Glenn Jones (Semantic Camp London) covers social network portability and date portability
* 2008-02-19 [http://www.slideshare.net/garethr/parsing-microformats Parsing Microformats] presentation by Gareth Rushgrove (Semantic Camp London) includes an overview of available parsers

== 2007 ==
* 2007-11-17 [http://www.slideshare.net/56k/mromanello-ecal-presentation Linking Text References to Relevant Digital Resources Over The Web (Proposal of a Microformat for Canonical Texts References)] presentation by Matteo Romanello at [http://enlil.ff.cuni.cz/ecal Electronic Corpora of Ancient Languages] conference held in Prague on November 2007.
* 2007-11-06 [http://www.slideshare.net/guest897d73/microformats-a-web-of-data Microformats: A Web of Data] presentation by Brian Suda at [[events/2007-11-06-microfomats-a-web-of-data|Web 2.0 Expo Berlin]].
* 2007-10-31 [http://video.google.com/videoplay?docid=4912491017216716477 Microformats - The What, Where, Why and How] This is a recording of a presentation given by Mark Meeker on Microformats. Mark is an Architect on the UI Engineering team at Orbitz Worldwide. OrbitzTech talk Chicago Il.
* 2007-10-04 [http://tantek.com/presentations/2007/10/social-network-portability/ Social Network Portability] presentation by Tantek Çelik at [[events/2007-10-04-fundamentos-web-social-network-portability|Fundamentos Web 2007]].
* 2007-10-04 [http://www.slideshare.net/mattb/coding-on-the-shoulders-of-giants Coding on the Shoulders of Giants] presentation by Matt Biddulph at [[events/2007-10-04-future-of-web-apps|Future of Web Apps London 2007]] - mentions their implementation of hCard, hCalendar and how their support gives them more features.
* 2007-10-02 [http://www.slideshare.net/cgriego/microformats-building-blocks-of-the-semantic-web/ Microformats, building blocks of the semantic web] presentation by Chris Griego at [[events/2007-10-02-dallas-ruby-brigade|Dallas Ruby Brigade October 2007]]
* 2007-08-30 GeekUp presentation by [http://www.ts0.com Thom Shannon] - [http://www.ts0.com/2007/09/microformats-whats-point.asp Microformats: What's the point?]
* 2007-06-.. http://tantek.com/presentations/2007/06/microformats-bb-you/
* 2007-05-.. http://tantek.com/presentations/2007/05/microformats-bb-you/
* 2007-06-02 BarCamp San Diego presentation by Joshua Brewer: [http://www.slideshare.net/jbrewer/barcamp-sd-microformats Microformats: Building a Better Web].
* 2007-05-16 [[events/2007-05-16-XTech|XTech 2007]] presentation by Jeremy Keith: [http://adactio.com/extras/slides/nanotech.pdf Microformats: the nanotechnology of the semantic web].
* 2007-04-30 [[events/2007-04-30-mix07|Microformats: Data Formats That Put Humans First]] [http://tantek.com/presentations/2007/04/microformats/ presentation by Tantek Çelik]
* 2007-03-23 [[events/2007-03-23-stanford|Microformats at Stanford]] [http://tantek.com/presentations/2007/03/microformats/ presentation by Tantek Çelik]
* 2007-03-22 [http://www.webdu.com.au/go/session/microformats--hidden-treasures Microformats—the hidden treasure] by Dmitry Baranovskiy at the [http://www.webdu.com.au/ webDU 2007] conference in Sydney, Australia, 3:00pm–4:00pm
* 2007-03-16 [http://www.afroginthevalley.com/fr/2007/03/16/presentation-microformats-a-php-quebec/ Métadonnées pour Humains & Machines] (dead link ?) presentation in French by Sylvain Carle at the [http://conf.phpquebec.com/fr/archive/conf2007/ PHP Québec 2007] conference in Montréal, Canada.
* 2007-02-23 [http://bluesmoon.info/talks/microformats/ Microformats at the CSI Web 2.0 Conference in Bangalore] presentation by Philip Tellis
* 2007-02-19, [http://www.glennjones.net/Post/825/DestroyingWalledGardens-MicroformatssyndicationandAPI%e2%80%99s.htm Destroying Walled Gardens - Microformats syndication and API’s] at [http://barcamp.org/BarCampLondon2 BarCamp London 2], UK by Glenn Jones
* 2007-02-13, [http://groups.google.com/group/bristolskillswap/web/february-skillswap-microformats Microformats: The Semantic Web for the Rest of Us] Bristol Skillswap [rtsp://stream.watershed.co.uk/skillswap/2007.02.13.microformats.mov Streaming Video]
* 2007-02-07, [http://north.webdirections.org Web Directions North 2007], [http://north.webdirections.org/detail/venue/ Renaissance Vancouver Hotel Harbourside], 1133 West Hastings Street, Vancouver, British Columbia, V6E3T3, Canada
** [[events/2007-02-07-web-directions-north|Microformats at Web Directions North 2007]], 11:45am-12:45pm, 1:45pm-3:45pm
*** Tantek Çelik (Technorati) - "[http://tantek.com/presentations/2007/02/microformats/ Microformats — The Big Picture]"
*** John Allsopp (Westciv) - "[http://north07.webdirections.org/presentations/MicroformatsForDevelopers.pdf Microformats For Developers]"
*** Dan Cederholm (Simplebits) - "[http://north07.webdirections.org/presentations/MicroformatsForDesigners.pdf Microformats For Designers]"
* 2007-02-03 [http://www.glennjones.net/Post/823/Microformats%2ctheAK-47oftheweb-WebDD.htm Microformats HTML to API] at [http://www.webdd.org.uk/ WebDD], Reading UK by Glenn Jones

== 2006 ==
* 2006-11-24, Taichi Kaminogoya presented to [http://2xup.org/log/2006/11/27-2219 microformats に触れてみよう] at [http://www.asahi-net.or.jp/~eb2m-mrt/kaihatsu9.html XML Developers' Day #9], Tokyo, JAPAN.
* October 28th, [http://www.keepthebyte.ch/2006/10/microformats-speech-at-barcamp-zurich.html Microformats Speech at Barcamp Zurich]
* October 10th, Taichi Kaminogoya presented to [http://2xup.org/log/2006/10/10-1800 microformatsがもたらすドキドキする未来] at [http://lp1.cssnite.jp/ CSS Nite LP Disk 1], Tokyo, JAPAN.
* September 28th, [http://www.webdirections.org/microformats/ Microformats] at Web Directions South, Sydney Australia by John Allsopp. [http://www.webdirections.org/microformats/ slides, podcast, live blogging transcript all online now]
* September 27th, [http://tantek.com/presentations/2006/09/microformats-intro/ Microformats Intro] at New Context 2006, Radisson Miyako Hotel, Minato-ku, Tokyo, JAPAN. See also [http://flickr.com/photos/tags/microformatsnewcontext2006 photos].
* September 16th, [http://fredericdevillamil.com/presentations/2006/que-sont-les-microformats/index.html Introducing Microformats for resume publishing] in French by Frederic de Villamil at Barcamp Paris 4. Location: 43 rue d'Aboukir, 75002 Paris France
* September 13th, [http://tantek.com/presentations/2006/09/microformats-practices/ Microformats Practices] at [[events/2006-09-13-future-of-web-apps-microformats|Future of Web Apps]] in San Francisco. Location: Palace of Fine Arts Theatre, Lyon Street, San Francisco CA 94123.
* September 3th, Backnetwork and Microformats by Glenn Jones at Barcamp London. demo of hCard subscription idea for social networks.
* August 26th, Tantek Çelik led the [http://barcamp.org/BarCampStanfordMicroformats BarCampStanfordMicroformats] discussion at room 426, Margaret Jacks Hall, Stanford, CA 94305. There is an [http://barcamp.org/f/MF-barcamp_08_26_2006.ogg Ogg recording of the session].
* July 11th, [http://tantek.com/presentations/2006/07/what-are-microformats/ What are microformats?] at [[events/2006-07-11-an-event-apart-microformats|An Event Apart in New York City]]
* July 6th, [http://yatil.de/webmontag/ka0706/ Mikroformate Erweiterte Semantik von HTML-Dokumenten] (Präsentation von Eric Eggert) Web mondays presentation in german - translation is available here
* June 15th, Phil Wilson presented to the [http://www.ukoln.ac.uk/web-focus/events/workshops/webmaster-2006/ Institutional Web Management Workshop]
* June 8, Pete Prodoehl presented [http://rasterweb.net/raster/presentations/microformats-20060608/ Microformats] to the Milwaukee Web Design Meetup Group
* May 30, [http://netsquared.org NetSquared] [http://netsquared.org/conference/ Conference], 4:15pm-5:10pm: : [http://netsquared.org/conference/conference-sessions/Mashups A web more woven - the alchemy and practicalities of Mashups]. Tantek Çelik, Taylor McKnight and Chris Messina will discuss the core utility of microformats to publish and share data for/with mashups and other applications. Location: Jordan room, Cisco Systems' Vineyard Conference Center, 260 E. Tasman Drive, San Jose, CA.
* May 25, Brian Suda and Ryan King presented [http://theryanking.com/presentations/2006/www/ Practical Microformats] at WWW 2006 ([http://www.molly.com Molly Holzschlag] was orginally scheduled to give this talk, we filled in at the last minute with our slides from XTech)
* May 24, Kevin Lawver presented [http://presentations.lawver.net/standards/a_microformat_and_proposal_for/ A Microformat and Proposal For Interoperable Widgets]
* May 18, [http://xtech06.usefulinc.com/schedule/paper/148 The Intelligent Design of Microformats] by Ryan King at XTech 2006. ([http://theryanking.com/presentations/2006/xtech/talk/ slides]).
* May 16, [http://thebigjc.org/articles/2006/05/16/is-web-2-0-changing-the-software-industry Is Web 2.0 Changing the Software Industry?] by Chris Messina at [http://meshconference.com Mesh Conference]
* May 16, [http://theryanking.com/presentations/2006/xtech/tutorial/ Microformats from the Ground Up] by Brian Suda and Ryan King @ XTech 2006
* April 25, At [http://barcamp.org/TorCampDemoCamp5 DemoCamp #5 in Toronto], [http://blog.davidjanes.com David Janes] demonstrated [http://www.blogmatrix.com/ BlogMatrix] his platform for publish which supports microformats. (see [http://accordionguy.blogware.com/blog/_archives/2006/4/26/1913279.html Accordionguy blogpost]).
* April 23, [http://jazkarta.com/presentations/microformats.pdf/view Microformats and the Future of Syndication] by Nate Aune, AdaptiveWave (CM Pros Summit, San Francisco, CA)
* April 22, Intro to Microformats, [http://barcamp.pbwiki.com/BarCampBangalore Barcamp Bangalore], Bangalore, India, (photos [http://flickr.com/photos/abgpt/133393564/ 1], [http://flickr.com/photos/abgpt/133393545/ 2], [http://flickr.com/photos/abgpt/133393626/ 3])
* March 16, [http://ono.cdlib.org/archives/shimenawa/000219.html Reading 2.0] (see [http://radar.oreilly.com/archives/2006/03/link_list_reading_20_1.html Tim O'Reilly's notes]), San Francisco, CA
** Building with MicroFormats, [http://www.chaddickerson.com/blog/2006/03/17/reading-20-and-microformats/ Chad Dickerson], Yahoo
* March 13, SXSW Interactive, Room 17AB, Austin Convention Center, Austin, TX
** [[events/2006-03-13-sxsw-microformats|Microformats: Evolving the Web]], 11:30am-12:30pm
* March 11, SXSW Interactive, Room 17AB, Austin Convention Center, Austin, TX
** [http://tantek.com/presentations/2006/03/building-blocks Creating Building Blocks For Independents], 5pm-6pm
** [http://flickr.com/photos/tags/microformatssxsw photos]
* March 7, O'Reilly Emerging Technologies (ETech) Conference, Manchester Grand Hyatt, Ballroom, San Diego, CA
** [[events/2006-03-07-etech-microformats|Microformats intro and lightning demos at O'Reilly ETech conf.]], 5:30pm-6:15pm
** [http://flickr.com/photos/tags/microformatsetech photos]
* March 1, W3C Technical Plenary Day, Hotel Sofitel Cannes Mandelieu Royal Casino, main auditorium, 605 avenuedu Général de Gaulle, BP 49, MANDELIEU LA NAPOULE CEDEX, 06212 MANDELIEU LA NAPOULE, FRANCE
** [[events/2006-03-01-w3c-plenary-microformats|Microformats panel at W3C Technical Plenary Day]], 10:30am-11:30am
*** Ian Hickson (Google) - "A billion documents and no semantics anywhere" (NEED LINK TO SLIDES OR STUDY)
*** Tantek Çelik (Technorati) - "[http://tantek.com/presentations/2006/03/what-are-microformats/ What are microformats?]"
*** Håkon Wium Lie (Opera) - "Cascading Markup Languages — boom!" (NEED LINK TO SLIDES)
*** Rohit Khare (CommerceNet) - "[http://labs.commerce.net/~rohit/Angstro-W3C-TP/ Where Angle Brackets Fear to Tread]"
*** Dan Connolly (W3C) - "[http://www.w3.org/2003/g/talk62/slides Microformats for practical Semantic Web deployment]"
*** Q&A
**** "I'm very excited about '''microformats'''. What I really want is to get all the data out of databases and expressed as part of the Semantic Web." - Tim Berners-Lee. ('''emphasis''' added)
** "Services and the Web" by Mark Nottingham (Yahoo), 12:05pm-12:10pm.
*** Request to W3T/W3M: Go After The "Real" Web: Apache, PHP, Mozilla, Intermediaries and Caches, '''Microformats''', JSON... ('''emphasis''' added)
** Attendees voted the "Microformats" session the best session of the Plenary Day. 6:17pm.
* February 24, Yahoo Speakers Series, Yahoo Mission College Campus, 2nd floor conference room, 2821 Mission College Blvd., Santa Clara, CA 95054
** [http://tantek.com/presentations/2006/02/microformats-evolution/ Microformats: Evolving the Web]
* January 18, Apple Web Publishers internal meeting, Apple Computer, Star Trek conference room, 1 Infinite Loop, Cupertino, CA 95014, 12-1:40pm
** [http://tantek.com/presentations/2006/01/microformats-evolution/ Microformats: Evolving the Web]
* January 10, SD Forum Emerging Technologies SIG, Room H1, Cubberley Community Center, Palo Alto, CA, 7-9pm
** Ryan King's presentation, Ernie Prabhakar's presentation, Rohit Khare's presentation
** Microformats panel: Ryan King, Ernie Prabhakar, Rohit Khare, Tantek Çelik, Kevin Marks

== 2005 ==
* December 15, Syndicate Conference, San Francisco, CA
** [http://tantek.com/presentations/2005/12/syndicate-microformats/ Microformats - Emerging syndication types]
* November 26, [http://barcamp.org/index.cgi?TorCamp TorCamp], Teehan+Lax, 460 Richmond St. W, Toronto, ON, CA
** [http://www.davidjanes.com/docs/2005.11.25%20Microformats%20Presentation.ppt powerpoints] (sorry)
** [http://blog.davidjanes.com/mtarchives/2005_12.html#003467 photo]
* November 12, THINK Conference, Santa Cruz room, Chaminade hotel, Santa Cruz, CA, USA
** [[presentation-think-2005-11-12]]
* November 10, (location unknown), by Kevin Yank of SitePoint Pty. Ltd.
** [http://www.sitepoint.com/examples/innovation-on-standards/ Innovating on top of standards - Not around them]
* October 5, [http://web2con.com Web 2.0 Conference], Olympic Room, Argent Hotel, San Francisco, CA, USA
** [http://tantek.com/presentations/2005/10/microformats-examples/ Microformats Examples]
* October 4, [http://osafoundation.org/ OSAF], San Francisco, CA, USA
** [http://tantek.com/presentations/2005/10/microformats-evolution/ Microformats: Evolving the Web]
* September 30, [http://web.archive.org/web/20051102094339/we05.com/ Web Essentials 05] <nowiki>http://we05.com/</nowiki> (link broke 2007-12-18 or earlier), Guthrie auditorium, University of Technology, Sydney, Australia
** [http://tantek.com/presentations/2005/09/microformats-evolution/ Microformats: Evolving the Web] (<nowiki>http://we05.com/podcast/mp3/we05-14-tantek-celik2.mp3</nowiki> (link broke 2007-12-18 or earlier) MP3 - incomplete, mirror: http://microformats.org/media/2005/09/we05-14-tantek-celik2.mp3)
* September 29, [http://web.archive.org/web/20051102094339/we05.com/ Web Essentials 05] <nowiki>http://we05.com/</nowiki> (link broke 2007-12-18 or earlier), Guthrie auditorium, University of Technology, Sydney, Australia
** [http://tantek.com/presentations/2005/09/elements-of-xhtml/ The Elements of Meaningful XHTML] (<nowiki>http://we05.com/podcast/mp3/we05-2-tantek-celik.mp3</nowiki> (link broke 2007-12-18 or earlier) MP3 mirror: http://microformats.org/media/2005/09/we05-2-tantek-celik.mp3 )
* September 25, [http://webzine2005.com/ Webzine 2005], Valhalla Room, Swedish American Hall, San Francisco, CA, USA
** [http://theryanking.com/presentations/2005/webzine/ Microformats @ Webzine 2005]
* September 21, Web Intelligence Conference, Compiegne, France
** [http://moloko.itc.it/paoloblog/presentations/presentation_wi05/presentation_wi05.html Page-reRank: using trusted links to re-rank authority] ([http://sra.itc.it/people/massa/publications/wi05_page_rerank_massa_hayes.pdf paper]) - A discussion of using [[vote-links]] to improve [http://www-db.stanford.edu/~backrub/google.html PageRank]
* June 20: Supernova 2005 ([http://supernova2005.com/ Supernova2005 site]), Microformats [http://supernova2005.com/workshops.htm Workshop], Wharton West, Suite 500, San Francisco, CA, USA
** "[http://tantek.com/presentations/2005/06/what-are-microformats/ What are Microformats?]"
** "[http://homepage.mac.com/kevinmarks/supernovatags.html A microformat for tags]"
** [http://wiki.commerce.net/wiki/ZCommerceWS#Microformats commercenet wiki page on the workshop] ([http://labs.commerce.net/wiki/index.php/ZCommerceWS#Microformats 2])
* May 14: Fourteenth International World Wide Web Conference ([http://www2005.org/ WWW2005]), 2005, Microformats Dev-Day Track, Makuhari Messe Room 303, Chiba, JAPAN
** "[http://tantek.com/presentations/2005/05/what-are-microformats/ What are Microformats?]" - Tantek Çelik
** "[http://westciv.com/WWW2005/linkmf.html Link Microformats]" - John Allsopp
** "[http://complexspiral.com/events/archive/2005/www2005/potential.html The Potential of Microformats]" - Eric Meyer
** "Distributed Social Networks (XFN Implementations)"
*** Demonstrations of [http://wordpress.org WordPress] & [http://metafilter.com Metafilter]'s builtin XFN support, and XFN search engines [http://rubhub.com/ RubHub] & [http://xhtmlfriends.net/ xhtmlfriends.net].
** "[http://tantek.com/presentations/2005/05/hcard-hcalendar/ People and Events (hCard & hCalendar)]" - Tantek Çelik
** "[http://cnlabs.commerce.net/~rohit/hReview-in-Review/ hReview in Review]" - Rohit Khare
** "Bibliographies (hBib)" - notes captured: [[hbib-discussion-2005-05-14|hBib Discussion 2005-05-14]]
** "[http://westciv.com/WWW2005/xml2mf.html a more meaningful web with microformats]"
** "Semantic Web and Microformats" panel, Room 201

* March 15: "[http://tantek.com/presentations/2005/03/decentralizednetworks/ Decentralized Social Networks]", South by South West Conference (SXSW) 2005, Austin Convention Center Room 17AB, Austin TX

* March 14: "[http://2005.sxsw.com/interactive/conference/panels/?action=show&id=IAP0060 How to Trick-Out Your Blog]", South by South West Conference (SXSW) 2005, Austin Convention Center Room 16B, Austin TX

* March 13
** "[http://complexspiral.com/events/archive/2005/sxsw/ Emergent Semantics]", South by South West Conference (SXSW) 2005, Austin Convention Center Room 15, Austin TX
** "[http://tantek.com/presentations/2005/03/leveragingtags.html Leveraging Tags]", as part of the "How to Leverage Solipsism" panel, South by South West Conference (SXSW) 2005, Austin Convention Center Room 18A, Austin TX
** "[http://tantek.com/presentations/2005/03/elementsofxhtml/ The Elements of Meaningful XHTML]", South by South West Conference (SXSW) 2005, Austin Convention Center Room 16B, Austin TX

* January 21: [http://tantek.com/presentations/2005/01/attentionxml.html Attention.xml Technology Overview], private presentation, Yahoo! campus, Santa Clara, CA

== 2004 ==

* September 28: "[http://tantek.com/presentations/20040928sdforumws/semantic-xhtml.html Semantic XHTML: Can your website be your API? - Using semantic XHTML to show what you mean]", SD Forum Web Services SIG, eBay's Silicon Valley Conference Center 2161 North First Street San Jose, CA 95131

* September 12: "[http://wiki.oreillynet.com/foocamp04/index.cgi?MVCeqXHTMLCSSJS Model+View+Controller = XHTML+CSS+JS]", O'Reilly Media Foo Camp 2004, O'Reilly Campus, Wallcreeper room, Sebastopol CA

* September 11: "[http://wiki.oreillynet.com/foocamp04/index.cgi?AttentionXML Attention.XML]", O'Reilly Media Foo Camp 2004, O'Reilly Campus, Appaloosa room, Sebastopol CA

* September 10: "[http://wiki.oreillynet.com/foocamp04/index.cgi?SimpleSemanticFormats Simple Semantic Formats]", O'Reilly Media Foo Camp 2004, O'Reilly Campus, Camel room, Sebastopol CA

* March 15: "[http://tantek.com/presentations/2004sxsw/xfn.html Ridiculously Easy Social Software]", South by South West Conference (SXSW) 2004, Austin Convention Center Room 17B, Austin TX

* February 11th: "[http://www.tantek.com/presentations/2004etech/realworldsemanticspres.html real world semantics]", O'Reilly Emerging Technology Conference (ETech) 2004 Westin Horton Plaza, San Diego, CA. This presentation was the first public discussion and introduction of the terms "microformat" and "lowercase semantic web". Reprised as a five-minute lightning talk at [http://wiki.oreillynet.com/etech/index.cgi?ConCon ConCon], Rx Gallery, San Francisco CA (16 February 2004).

This page was contributed from [http://developers.technorati.com/wiki/MicroFormatsPresentations the Technorati developers wiki].

events/2010-02-17-webkit-html5-benkyokai

2010-02-21T13:49:29Z

Oli: adding note about language

<entry-title>3rd Webkit/HTML5 Benkyokai (第3回Webkit/HTML5勉強会)</entry-title>
__TOC__
One of several microformats [[events]].

<div class="event-page vevent">
== details ==
;When
:2010-02-17 from 19:00–20:00
;Where
:グリー株式会社, 東京都港区六本木4-1-4 黒崎ビル5F (Tokyo, Japan)
;What
:3rd Webkit/HTML5 Benkyokai (第3回Webkit/HTML5勉強会)
;Presenter
:[http://oli.jp/ Oli Studholme]
;Web
:http://atnd.org/events/3058
;Slides
:[http://oli.jp/slides/microformats-microdata Microformats & Microdata] (slides mainly in English, code examples use Japanese text)

'''[http://feeds.technorati.com/events/microformats.org/wiki/events/2010-02-17-webkit-html5-benkyokai Add this event to your diary or calendar program]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== microformats & microdata ==

Oli Studholme will give an overview of Microformats & Microdata, and discuss using them in HTML5 for contact and event data (in Japanese)

== tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):

<kbd class="tags" style="display:block">
'''#html5j'''
microformats
tokyo
</kbd>

If you use Twitter, mention ''@microformats''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats Twitter Search].

== notes ==
Topics discussed:

* Microformats
* Microdata

== articles and blog posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below. Newest first.

* ...

</div> 

== related pages==
{{events-related-pages}}

events/2010-02-17-webkit-html5-benkyokai

2010-02-21T13:48:11Z

Oli: adding link to slides

<entry-title>3rd Webkit/HTML5 Benkyokai (第3回Webkit/HTML5勉強会)</entry-title>
__TOC__
One of several microformats [[events]].

<div class="event-page vevent">
== details ==
;When
:2010-02-17 from 19:00–20:00
;Where
:グリー株式会社, 東京都港区六本木4-1-4 黒崎ビル5F (Tokyo, Japan)
;What
:3rd Webkit/HTML5 Benkyokai (第3回Webkit/HTML5勉強会)
;Presenter
:[http://oli.jp/ Oli Studholme]
;Web
:http://atnd.org/events/3058
;Slides
:[http://oli.jp/slides/microformats-microdata Microformats & Microdata]

'''[http://feeds.technorati.com/events/microformats.org/wiki/events/2010-02-17-webkit-html5-benkyokai Add this event to your diary or calendar program]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== microformats & microdata ==

Oli Studholme will give an overview of Microformats & Microdata, and discuss using them in HTML5 for contact and event data (in Japanese)

== tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):

<kbd class="tags" style="display:block">
'''#html5j'''
microformats
tokyo
</kbd>

If you use Twitter, mention ''@microformats''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats Twitter Search].

== notes ==
Topics discussed:

* Microformats
* Microdata

== articles and blog posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below. Newest first.

* ...

</div> 

== related pages==
{{events-related-pages}}

spam-removal

2010-02-21T13:44:25Z

Oli: adding info for non-sysop users

<h1>Spam Removal</h1>

Unfortunately not everyone plays nice on the microformats wiki, and from time to time a misguided individual (or bot) may edit pages and add unrelated content, typically advertisements with links, sometimes hidden, and sometimes they may even delete or otherwise damage the existing content.

Whether or not you have admin privileges, you can help fight this spam.

The fastest / best way to remove spam is to get in the [[irc]] channel, and see if you can alert an admin by mentioning "adminhelp", or even ask one of the admins you see in the channel by name. Admins can block the spammer immediately to prevent further damage from that login, as well as one-click rollback their changes.

If there are no admins about, please remove the links and mention “spam” in summary.

== Block (admins only) ==

# Start with http://microformats.org/wiki/Special:Recentchanges
# click the "block" link next to one of the changes from a spammer
# enter "infinite" for the Expiry
# and something like "spammer" for the Reason
# Click "Block this user"
# Go back to http://microformats.org/wiki/Special:Recentchanges to verify that your block took effect, and look for any other spammers to block

== Rollback (admins only) ==

# Start with http://microformats.org/wiki/Special:Recentchanges
# Apple/command/control-click the (diff) link next to each change that a spammer has done to open new tabs for each problem. Only once per page though - you don't need to click diff for each change for a single page.
# Now on that diff page there are three possibilities:
## There is a [rollback] link in the top right - if so, click it, you're done.
## There is no [rollback] link, typically because someone else has changed the page after the spammer. In that case, click the history link near the top left and then click the radio button in the left column of radio buttons that corresponds to the last version before the spammer started editing and click "Compare selected versions". You should see no changes (i.e. some other microformats community member successfully removed the spam). If you see any other changes, (like accidental removal of content), the easiest thing to do is to go back to the history page, then click on the dated link of the last stable version, then edit, note the warning about editing an older version, then save.
## Something goes wrong when you click the (diff) link and you don't get the typical diff page. You get some other plain typically unstyled HTML. i've only seen this a few times and it usually means the wiki page was really messed up in some odd way. In this scenario you also have to go back to [http://microformats.org/wiki/Special:Recentchanges recent changes], click the (hist) link instead of the (diff) link next to the errant change, and then just like the second part of the previous tip, click on the dated link of the last stable version, then edit, note the warning, then save.
## There is a 4th possibility, when a spammer creates a new page, in that case you simply Delete it, with the reason given as spam.
# In any case, when you're done repairing that page, close the tab, and repair the next one. In the typical case where you catch the spam nearly immediately and no-one has changed the page, you can click the [rollback] link, then close the tab, in quite rapid succession, often undoing a recent spam attack on a number of pages in under a minute.
# Finally you may want to go back to http://microformats.org/wiki/Special:Recentchanges and verify that you repaired the damage.

h2vx

2010-02-14T15:53:51Z

Oli: /* issues */ adding timezone issue

<entry-title>H2VX</entry-title>
__TOC__
<dfn>[http://h2vx.com H2VX]</dfn> is a production deployment of the [[X2V]] hCard and hCalendar conversion transforms.

It converts [[hCard]] contacts and [[hCalendar]] events on web pages to .vcf and .ics respectively for use in desktop and other client software applications.

== documentation ==
To convert hCards to vCards, go http://h2vx.com/vcf/ and enter the URL to the hCards.

To convert hCalendar to iCalendar, go http://h2vx.com/ics/ and enter the URL to the hCalendar events.

=== URLs ===
Links to H2VX.com to convert a URL (like <nowiki>http://microformats.org/wiki/events</nowiki> ) can be constructed as follows:

You may omit the leading "http://" from the URL to be converted for a briefer more readable URL:

;download vCards from hCards
:<kbd><nowiki>http://h2vx.com/vcf/URL</nowiki></kbd>
:e.g. <kbd><nowiki>http://h2vx.com/vcf/microformats.org/wiki/events</nowiki></kbd>
;download iCalendar from hCalendar
:<kbd><nowiki>http://h2vx.com/ics/URL</nowiki></kbd>
:e.g. <kbd><nowiki>http://h2vx.com/ics/microformats.org/wiki/events</nowiki></kbd>
;subscribe to hCalendar from hCalendar
:<kbd><nowiki>webcal://h2vx.com/ics/URL</nowiki></kbd>
:e.g. <kbd><nowiki>webcal://h2vx.com/ics/microformats.org/wiki/events</nowiki></kbd>
:<kbd><nowiki>http://h2vx.com/ics/sub/URL</nowiki></kbd> for systems which don't support auto-linking of webcal: URLs, e.g. MediaWiki, Twitter.
:e.g. <kbd><nowiki>http://h2vx.com/ics/sub/microformats.org/wiki/events</nowiki></kbd>

=== user agent strings ===
H2VX uses two user agent strings, when retrieving hCards and hCalendars respectively:
* <samp><nowiki>H2VX contacts proxy (http://h2vx.com/vcf/)</nowiki></samp>
* <samp><nowiki>H2VX events proxy (http://h2vx.com/ics/)</nowiki></samp>
You may see occurrences of these in your web server logs when users of H2VX convert hCards and hCalendar events on your pages.

=== built ===
H2VX is built and maintained by [[User:Tantek|Tantek]] with:
* [[X2V]] XSLTs by [[User:Brian|Brian Suda]]
* PHP get-contact.php get-cal.php originally written by Brian, updated/factored by Tantek with various improvements. [[to-do]]: open source these.
* PHP common.php (and Javascript common.js) by Tantek which incorporate CASSISv0 open source from http://cassisproject.com/
* XHTML1+CSS+JS front-end design/interface by Tantek (view source of h2vx.com in your browser for more).

== feedback ==
Have feedback on H2VX? Feel free to add to the top of this list and use <nowiki>~~~~</nowiki> to sign your name and date your comment. If this grows too big we can move it to [[h2vx-feedback]]

* As a Web page author I find the H2XV site a bit awkward to use -- it's difficult to find the URLs to use in my Web page. As an end-user it fine to have the H2VX bookmarklets in my toolbar, but as a page author I can't be sure everyone has the bookmarklets or Operator installed. [[User:Bob Jonkman|Bob Jonkman]] 00:56, 10 November 2009 (UTC)
* "Also, a short 'about' page would be worthwhile IMO, especially for adding to the homepage." - Norm on microformats-discuss.
* ...

== issues ==
Found a problem with H2VX? Please note it here at the top of this list (consider grouping it under an existing subhead or introduce a new subhead if necessary) and use <nowiki>~~~~</nowiki> to sign your name and date your comment. If this grows too big we can move it to [[h2vx-issues]]

=== HTML5 support ===
* <code><meta charset=utf-8></code> isn't recognized so the output is double encoded. [[User:Greut|Greut]] 11:12, 4 January 2010 (UTC)
* new HTML5 elements (such as header, footer, section) are not supported (this is because they are stripped out by PHP Tidy and thus ignored). [[User:Tantek|Tantek]] 16:13, 19 January 2010 (UTC) possible solutions:
** 1. Wait for a PHP html5lib (being coded by the HTML5 community, but not available/functional yet AFAIK)
** 2. Add a flag to the H2VX processing URL which says "I'm a crazy XML person and my markup is 100% well formed XML, please don't tidy, please break and fail to process if it's not well formed".
** in either case, new special HTML5 elements (like time) will require an update to [[X2V]] to know to properly handle/parse new semantic attributes (like datetime).

=== mouse events ===
* The "what are microformats?" style descriptions only appear on mouse-over of the trigger terms (those with class="term"). It does not appear at all when keyboard navigation is used, making it somewhat inaccessible. The problem here is that the trigger elements are the ones that should receive focus, but not being links they are not in the tabbing order so do not, hence the helper text never appears for keyboard users. [[User:Norm|Norm]] 10:39, 6 November 2009 (UTC)
** Quick fix: remove '''visibility:hidden''' from '''.term .info'''. [[User:Andr3|Andr3]]

=== page semantics ===
* should be made into 's for semantic reasons. ;) [[User:Andr3|Andr3]]
** Note that the <code></code> element is used deliberately for "instance" of a term - this is an [[HTML5]] semantic, and is more accurate in this instance than "em"phasis. — [[User:Tantek|Tantek]] 18:29, 11 November 2009 (UTC)

=== not possible to use dtstart with timezone in abbr title ===
* Adding a timezone to dtstart using abbr pattern leads to The Shining-style debug output repeating “Object is a string”. I tried adding a time with timezone via the value class pattern, and while the vcard downloads the time is incorrect ~~[[User:Oli|Oli]] 00:53 15 February 2010 (+09:00)

=== resolved ===
Resolved issues are moved to this section. If this grows too big we can move it to [[h2vx-issues-resolved]]
* ...

* 2009-11-11 We were using the Technorati hosted service. Surprised to see it redirected to H2XV, took a minute to realize what was going on. Thanks for picking up the service! Both the hosting provider and the new user agent are blocked by default on our side to prevent scraping. To be more transparent, maybe you could change the UA similar to the old one: from <nowiki>"Technorati contacts proxy (http://technorati.com/contacts/)"</nowiki> to <nowiki>"H2VX contacts proxy (http://h2vx.com/vcf/)"</nowiki> [[User:DineMonkey|DineMonkey]] 15:47, 11 November 2009 (UTC)
** I've updated the user agent strings per your recommendation and documented them above as well. [[User:Tantek|Tantek]] 18:29, 11 November 2009 (UTC)
*** <nowiki>H2VX contacts proxy (http://h2vx.com/vcf/)</nowiki>
*** <nowiki>H2VX events proxy (http://h2vx.com/ics/)</nowiki>

=== closed ===
Once a resolved issue has no further actions (and ideally is verified by the issue reporter), it can be closed and moved to this section. If this grows too big we can move it to [[h2vx-issues-closed]]
* 2009-11-04 It would be good to have the option to pass "referer" instead of a URL. [[User:Adactio|Adactio]] 10:47, 4 November 2009 (UTC)
** http://h2vx.com/vcf/referrer and http://h2vx.com/ics/referrer are now up and running. Example of /vcf/referrer is live on http://tantek.com/ and the alternate spelling /vcf/referer is used live on http://clearleft.com/ - as such, closing this issue. [[User:Tantek|Tantek]] 20:25, 5 November 2009 (UTC)
* ...

== see also ==
* [[X2V]]
* [[hCard]]
* [[hCalendar]]
* [[implementations]]

irc-people

2010-02-14T15:12:23Z

Oli: adding myself

A list of [[irc|IRC]] regulars, sorted by nick, and their normal timezones (winter/summer).

* {{irc user|Amodal1| amodal1|-0500/-0600}}
* {{irc user|Adam Ballai|AdamBallai|-700/-700}}
* {{irc user|Adam Craven|AdamCraven|+0000}}
* {{irc user|Alenonimo|Alenonimo|-0300}}
* {{irc user|Alexander Graf|AlexanderGraf|+0100}}
* {{irc user|Axelator|ax|-0700}}
* {{irc user|Tomasino|aloneone|-0500}}
* {{irc user|AmanuelTewolde|Amanuel|-0500/-0400}}
* {{irc user|Amette|amette|+1000}}
* {{irc user|Amir Guindehi|AmirGuindehi|+1000}}
* {{irc user|Andr3|andr3|+0000}}
* {{irc user|Ajaswa|Andrew Jaswa|-0500}}
* {{irc user|AndrewDisley|AndrewDisley|+0000}}
* {{irc user|Andrii Ponomarov|Andrii|+0300}}
* {{irc user|AngeloGladding|angelogladding|-0800/-0700}}
* {{irc user|AnselHalliburton|anselxyz|-0800/-0700}}
* {{irc user|Ashe Dryden|Ashe|-600}}
* {{irc user|Atamido|Atamido|-0600/-0500}}
* {{irc user|Barce|Barce|-0800/-0700}}
* {{irc user|Azathoth|Florian Beer|+1000}}
* {{irc user|Tyler Roehmholdt|Baristo|-0800/-0700}}
* {{irc user|Belling|Belling|-0800/-0700}}
* {{irc user|BenjaminCarlyle|BenjaminCarlyle|+1000}}
* {{irc user|HenriBergius|bergie|+0200/+0300}}
* {{irc user|Ben Ward|BenWard|-0800/-0700}}
* {{irc user|BenWest|bewest|-0800/-0700}}
* {{irc user|B.K._DeLong|bkdelong|-0500/-0400}}
* {{irc user|Robert|blueace|+0100}}
* {{irc user|Robert|blueace|+0100}}
* {{irc user|BluesMoon|bluesmoon|+0530}}
* {{irc user|BobChao|BobChao|+0800}}
* {{irc user|Bob Jonkman|BobJonkman|-0500/-0400}}
* {{irc user|Oli|boblet|+0900}}
* {{irc user|Boneill|boneill|+0000}}
* {{irc user|Brian|briansuda|+0000}}
* {{irc user|TimT|bringo|-0800/-0700}}
* {{irc user|Briski|Briski|+0000}}
* {{irc user|BryanL|BryanL|-0500/-0400}}
* {{irc user|BryanRieger|Bryan Rieger|+0000}}
* {{irc user|Bug-E|Bug-E|+0200}}
* {{irc user|CarlaHufstedler|carlamagpie|-0500/-0400}}
* {{irc user|Colin_Barrett|cbarrett|-1000}}
* {{irc user|Cognizance|Cognizance|-0800/-0700}}
* {{irc user|ColinDDevroe|cdevroe|-0500/-0600}}
* {{irc user|Cgriego|cgriego|-0600/-0500}}
* {{irc user|Charlvn|Charl|+0200/+0200}}
* {{irc user|CharlesRoper|charles_r|0000/+0100}}
* {{irc user|Chris_Cressman|Chris Cressman|-0500/-0400}}
* {{irc user|ChristopherStJohn|cks|-0600/-0500}}
* {{irc user|JeremyBoggs|clioweb|-5000/-4000}}
* {{irc user|Cloud|Cloud|+0000}}
* {{irc user|Cruster|cruster|+0200}}
* {{irc user|Csarven|csarven|-0500/-0400}}
* {{irc user|ChrisBrentano|ctb|-0800/-0700}}
* {{irc user|DanC|DanC|-0600/-0500}}
* {{irc user|DanielBurka|DanielBurka|-0400}}
* {{irc user|DanielJohnLewis|danieljohnlewis|0000}}
* {{irc user|DannyAyers|danja|+0100/+0200}}
* {{irc user|Dave Cardwell|davecardwell|+0000}}
* {{irc user|DavidMead|DavidMead|-0400}}
* {{irc user|DavidRussell|davidrussell|-0600/-0500}}
* {{irc user|DBounds|Darren Bounds|-0500}}
* {{irc user|Ddonat|David Gratton|-0800/-700}}
* {{irc user|DenisDefreyne|ddfreyne|+0100/+0200}}
* {{irc user|DeanEro|deanero|-0800/-0700}}
* {{irc user|DeepText|Deep Text|-0800/-0700}}
* {{irc user|DerrickPallas|DerrickPallas|-0800/-0700}}
* {{irc user|DimitriGlazkov|dglazkov|-0600/-0500}}
* {{irc user|DiegoBudny|DiegoBudny|-unspecified-}}
* {{irc user|DKerzman|DKerzman|-0600}}
* {{irc user|Dan Kubb|dkubb|-0800/-0700}}
* {{irc user|Dreamisle|dreamisle|-0500}}
* {{irc user|DrErnie|DrErnie|-0800/-0700}}
* {{irc user|DrewMcLellan|drewinthehead|+0000/+0100}}
* {{irc user|DrewBell|droob|-0600/-0500}}
* {{irc user|DimitriosZachariadis|dzach|+0200/+0300}}
* {{irc user|Ed Summers|edsu|-0500/-0400}}
* {{irc user|Enric|Enric|-0800/-0700}} (alt sp "enric")
* {{irc user|Evan|evanpro|-0500}}
* {{irc user|Evan|e_s_p|-0500}}
* {{irc user|Ket Majmudar|ethicaljunction|+0100}}
* {{irc user|EdwardWelker|ewelker|-0500}}
* {{irc user|ChrisMessina|factoryjoe|-0800/-0700}}
* {{irc user|Fil|Fil|+0200}}
* {{irc user|CFinke|Finke|-0700/-0600}}
* {{irc user|MarkoMrdjenovic|friedcell|+0100/+0200}}
* {{irc user|GarethR|garethr|+0000/+0100}}
* {{irc user|GeorgeBrock|georgebrock|+0000/+0100}}
* {{irc user|Grantbow|Grantbow|-0800/-0700}}
* {{irc user|Griffin|Griffin|-0600/-0500}}
* {{irc user|Guillaume Lebleu|glebleu|-0800}}
* {{irc user|Aubergine10|Guy Fraser|+0100/+0000}}
* {{irc user|HenrichPoehls|HenrichP|+0100}}
* {{irc user|IanHickson|Hixie|-0800/-0700}}
* {{irc user|Hlb|hlb|+0800-0700}}
* {{irc user|EdwardOConnor|hober|-0800/-0700}}
* {{irc user|Ichigo|ichigo|+1000}}
* {{irc user|Alper|illustir|+0100}}
* {{irc user|Inkbase|inkbase|-0800/-0700}}
* {{irc user|IwaiMasaharu|iwaim|+0900}}
* {{irc user|Izo|IZO|-unspecified-}}
* {{irc user|Jabz|Jabz|+0000}}
* {{irc user|JamieKnight|JamieKnight|+1000/0000}}
* {{irc user|JayMyers|jaymyers|-0600/-0500}}
* {{irc user|JoeGregorio|jcgregorio|-unspecified-}}
* {{irc user|WizardIsHungry|jcw9|-0500/-0400}}
* {{irc user|Adactio|Jeremy Keith|+0000}}
* {{irc user|jrodgers|JesseRodgers|-0500}}
* {{irc user|JasonK|jkridner|-0600/-0500}}
* {{irc user|JeffMcNeill|jeffmcneill|-1000}}
* {{irc user|JimboJW|jimbojw|-0600/-0500}}
* {{irc user|Jonathan_Arkell|jonnay|-0700/0600}}
* {{irc user|JonathanMalek|JonathanMalek|-0800/-0700}}
* {{irc user|JosephHolsten|josephholsten|-0600/-0500}}
* {{irc user|JulianStahnke|julianstahnke|+0000}}
* {{irc user|Kapowaz|kapowaz|+0000/+0100}}
* {{irc user|Keri Henare|kerihenare|+1200}}
* {{irc user|KevBurnsJr|kevburnsjr|-0800}}
* [http://epeus.blogspot.com/ KevinMarks] (-0800/-0700)
* {{irc user|RyanKing|kingryan|-0800/-0700}}
** [http://theryanking.com/blog/archives/2006/04/19/office-hours/ Office hours]: Wednesday, 21:00 UTC
* {{irc user|Lachlan Hunt|Lachy|+1000/+1100}}
* {{irc user|Levitation|levitation[A]|+0200/+0300}}
* {{irc user|Linmic|linmic|+0800-0700}}
* {{irc user|MarkNg|madness|+0000/+0100}}
* {{irc user|Mark Mansour|Mark Mansour|+1100}}
* {{irc user|MarkNormanFrancis|Mark Norman Francis|+0000/+0100}}
* {{irc user|Maddiin|Martin Czura|+0100}}
* {{irc user|MattBowen|Matt Bowen|-0500/-0400}}
* {{irc user|Groningen|Matthias Kluth|+0100}}
* {{irc user|MattisManzel|Mattis Manzel|+0100/+0200}}
* {{irc user|CiaranMc|McNulty|+0000/+0100}}
* [[mfbot]] - a bot which logs all edits to this wiki. It appends a number with a '+' or '-' sign, to indicate the number of characters added or removed as a result of the edit.
* {{irc user|MicroAngelo|MicroAngelo|+0000/+0100}}
* {{irc user|Mike|Michael McCracken(mmc)|-0800/-0700}}
* {{irc user|MikeKaply|mkaply|-0600/-0500}}
* {{irc user|SteveIvy|monkinetic/redmonk|-0700}}
* {{irc user|MWTE|mwte|+0000/+0100}}
* {{irc user|RobManson|nambor|+1000}}
* {{irc user|Naterkane|Nater Kane|-0500}}
* {{irc user|Nelix|nelix|+1000}}
* {{irc user|neuro|neuro|-unspecified-}}
* {{irc user|Niekie|niekie|+0100/+0200}}
* {{irc user|NTollervey|ntoll|+0000/+0100}}
* {{irc user|Pawlik|pawlik|+0100/+0200}}
* {{irc user|Andy Pemberton|pembertona|-0500/-0400}}
* {{irc user|Phae|Phae|+0000/+0100}}
* {{irc user|pius|Pius Uzamere|+0500}}
* {{irc user|PriitLaes|plaes|+0200/+0300}}
* {{irc user|ChrisCasciano|pnhChris|-0500/-0400}}
* {{irc user|Hugopeixoto|Politoed|+0000/+0100}}
* {{irc user|PetarPopov|popov|-0800/-0700}}
* {{irc user|Pfefferle|pfefferle|+0100/+0200}}
* {{irc user|Lauren Scime|pseudowish|-0800/-700}}
* {{irc user|DavidOsolkowski|qid|-0500}}
* {{irc user|RCanine|RCanine|-0500/-0400}}
* {{irc user|Remi|Remi|-0500/-0400}}
* {{irc user|ZachCarter|riah|-0500/-0400}}
* {{irc user|RobertBachmann|RobertBachmann|+0100/+0200}}
** Office hours: <s>Wednesday, 18:00-20:00 UTC</s> (Currently no office hours}}
* {{irc user|RobLinton|RobLinton|-0800/-0700}}
* {{irc user|Ronnos|Ron Kok|+0000}}
* {{irc user|SamJohnston|samj|+0100/+0200}}
* {{irc user|SarahWorsham|sazbean|-0500/-0400}}
* {{irc user|ScottNelle|snelle|-0500/-0400}}
* {{irc user|ScottRozic|gravitas|-0500/+0100}}
* {{irc user|Dana Benson|Snowden|-0800/-0700}}
* {{irc user|SinDoc|SinDoc|+0100/+0200}}
* {{irc user|Savell Martin|Savell|+0000/+0000}}
* {{irc user|Smackman|Steve Farrell|-0800/-0700}}
* {{irc user|SpikeUK|SpikeUK|+0000/+0100}}
* {{irc user|Steve Ganz|SteveGanz|-0800/-0700}}
* {{irc user|Stii|Stii|+0200 GMT}}
* {{irc user|ReinierZ|surial|+0100 GMT}}
* {{irc user|SuperPhly|SuperPhly|-600/-500}}
* {{irc user|SyedSRahman|syedsrahman|+0530}}
* sym[[User:LynX|lynX]] or (better) [[User:LynX|lynX]] on [http://about.psyc.eu PSYC] (+0100}}
* {{irc user|DavidLehn|taaz|-0500/-0400}}
* {{irc user|Tantek|Tantek|-0800/-0700}}
* {{irc user|tbmartin|tbmartin|-0800/-0700}}
* {{irc user|themattharris|themattharris|-0800/-0700}}
* {{irc user|Wojciech|theanxy|+0100/+0200}}
* {{irc user|TheJbf|thejbf|+0100/+0200}}
* {{irc user|Thomasknoll|thomasknoll|-0800}}
* {{irc user|thuddwhirr|thuddwhirr|-0800/-0700}}
* {{irc user|TobyInk|tobyink|+0000/+0100}}
* {{irc user|Trovster|trovster|-0800/-0700}}
* {{irc user|Vadania|vadania|-0600/-0700}}
* {{irc user|Vant|vant|+0900}}
* {{irc user|venkateswaran|vensilver|+5.30 GMT}}
* {{irc user|Victor|victor|+0100/+0200}}
* {{irc user|V-I-P|V-I-P|+0100/+0200}}
* {{irc user|KrissWatt|VoodooChild|+0000/+0100}}
* {{irc user|WebOrganics|weborganics|+0100}}
* {{irc user|JacksonWilkinson|whafro|-0500/-0400}}
* {{irc user|Richard Conyard|WhiskeyM|+0000}}
* {{irc user|Veeliam|William Lawrence|-0800/-0700}}
* {{irc user|StevenWoods|woodss|+0000 GMT}}
* {{irc user|Ianloic|yakk|-0800/-0700}}
* {{irc user|LarsStrojny|mastaYoda|+0100}}
* {{irc user|ZimbaTm|zimbatm|+0100}}
* {{irc user|FoundAtion|Foundation|-0800}}
* {{irc user|PJKix|pjkix|-0800/-700}}
* {{irc user| ChrisBroadfoot|broady|+1000}}
* {{irc user|Natalie Downe|NatBat|+0000}}
* {{irc user|Dotjay|dotjay|+0000}}
* {{irc user|PeterHellberg|zil|+0100}}
* {{irc user|Kiryl Zhybul|zkv|+0400}}
* {{irc user|ScottThorpe|Salve|-0800/-0700}}
* {{irc user|Dane|imdane|-0600/-0500}}
* {{irc user|ThomasLoertsch|tl|+0100/+0200}}
* {{irc user|Francisco Bernardo|frantic0|+0100/+0200}}
* {{irc user|Steven Osborn|steve918|-0700/-0800}}
* {{irc user|Trodrigues|trodrigues|+0000}}

User:Oli

2010-02-14T05:53:00Z

Oli: it’d be nice if I could add class="url" to this

Oli Studholme I’m interested in HTML5, and live in Japan. [http://oli.jp/ Oli.jp]

html5

2010-02-14T05:42:05Z

Oli: /* Issues */ adding HTML5 validation issue with colon-less timezones (as recommended on value-class-pattern page)

<entry-title>Microformats in HTML 5</entry-title>

''This page is to document '''future''' use of microformats in [http://www.w3.org/html/wg/html5 HTML 5]. None of the items documented are supported now, and may change upon proper development within the microformats community, or changes in the HTML 5 specification. This page is to track HTML5 enabled enhancements to microformats, and issues that HTML5 raises. It may be used to track issues which we need to push back into the HTML 5 development process.''

If there are things that Microformats would like to mark up that aren't handled by HTML5 explicitly, please let the WHATWG know, so we can improve HTML5. This is how <code>time</code> came to be, for instance.

==New features in HTML5==

=== time element ===
'''<code>time</code> element for representing date times'''. In HTML5, the machine form of datetimes can be represented natively. It should be possible to replace the date-time design pattern with native HTML.
* <code>time</code> takes an optional <code>pubdate</code> attribute, to indicate the publication date of an <code>article</code>. Synonymous with [[hAtom]] <code>published</code>, may imply [[hAtom]] <code>updated</code>, may imply [[hReview]] <code>dtreviewed</code>, may imply [[hListing]] <code>dtlisted</code>

=== article element ===
'''<code>article</code>''' element for major, independent compositions of content within a page. Perhaps synonymous with [[hAtom]] <code>hentry</code>. Could be parsed as <code>hentry</code> within explicit <code>hfeed</code> blocks?

=== microdata ===
'''[[microdata]]'''. HTML5 provides a set of attributes and associated DOM APIs for extracting data from web pages.
* <code>itemprop</code> attribute is a more specific version of <code>class</code>, for field names
* <del><code>subject</code> attribute allows semantically linking within the page. Conceptually similar to the [[include-pattern]].</del>
* <code><itemref refid="x" /></code> allows semantically linking within the page. Conceptually similar to the [[include-pattern]].
* <code>content</code> attribute on the <code>meta</code> element can be used to invisibly include data. Conceptually similar to the [[value-class-pattern]].
* <code>itemscope</code> attribute identifies blocks to be marked as structure data. Conceptually similar to the [[mfo]] brainstorming?
* <code>itemtype</code> attribute to specify the type for an item (for example: <code><nowiki>itemtype="http://microformats.org/profile/hcard"</nowiki></code>)

==== microdata vocabularies ====
* [http://dev.w3.org/html5/mdvcard/ microdata vCard] - use [[hCard]] instead, taking into account the [[hcard-faq|hCard FAQ]] and [[hcard-issues-resolved|resolved]]+[[hcard-issues-closed|closed issues]]. hCard 1.0.1 (under development) is incorporating these errata. Avoid the "microdata vCard" vocabulary as it is an out-of-date fork/snapshot of hCard.
* [http://dev.w3.org/html5/mdvevent/ microdata vEvent] - use [[hCalendar]] instead, taking into account the [[hcalendar-faq|hCalendar FAQ]] and [[hcalendar-issues-resolved|resolved]]+[[hcalendar-issues-closed|closed issues]]. hCalendar 1.0.1 is incorporating these errata. Avoid the "microdata vEvent" vocabulary, as it is an out-of-date fork/snapshot of hCalendar's vevent root class name and applicable properties.
* [http://dev.w3.org/html5/mdwork/ microdata Licensing Works] - see also [[licensing-brainstorming]]

=== data attributes ===
'''<code>data-</code> naming convention for tag attributes'''. the draft specification states that any attribute that starts with "data-" will be treated as a storage area for private data.
* Note that the data-* stuff is explicitly not for microformats. Those attributes are defined in such a way that browsers will never do anything special with them, ever. They are intended for script authors to have a space in which they can play without ever clashing with anything the browser does. There may be some cases of private [[poshformats]] that are never intended for interchange that may be used in data-* attributes.

== Current microformat compatibility ==
There seems to be no issue with current implementation of the following microformats in HTML 5:
* [[hcard]]
* [[xfn]]

== Requests ==
* "how to use with HTML5" sections that include (a) microformats examples that use [[HTML5]], and (b) microformats parsing details that specify what to do (if anything special is required) with HTML5 elements (e.g. how to parse the <code>time</code> element for dates and times for microformats). See (and add to if necessary) :
** [[hcard-brainstorming#how_to_use_with_HTML5|hCard brainstorming - how to use with HTML5]]
** [[hcalendar-brainstorming#how_to_use_with_HTML5|hCalendar brainstorming - how to use with HTML5]] e.g. hCalendar with the <code>time</code> element
** [[citation-brainstorming#how_to_use_with_HTML5|citation brainstorming - how to use with HTML5]]
** if nothing special is required for HTML5, then after performing the analysis, that should be noted as well, for the purpose of clarity.

==Issues==
<div class='discussion issues'>
* '''The <code>rev</code> attribute has been removed'''. In HTML5, <code>rel</code> and <code>rev</code> are no-longer paired, and the <code>rel</code> attribute nolonger describes the direction of a relationship. Microformats which use <code>rev</code> will need to use <code>rel</code> instead.
** Or something like data-rev="vote-for"
*** As above, <code>data-</code> attributes are for application-context functionality, ''not'' shared vocabularies. Further, the HTML5 specification makes <code>rel</code> the correct attribute to use, regardless of direction, through the changed specification. --[[User:BenWard|BenWard]] 17:53, 12 May 2009 (UTC)
* '''The <code>profile</code> attribute has been removed'''. In HTML, the <code>profile</code> attribute from the <code>head</code> has been removed, with no direct replacement. This causes issues for GRDDL support. It's been suggested that profile URLs be represented in <code>link</code> elements instead, or even as a custom HTTP header. See [[grddl]] and [[profile-uris]]
** See [[rel-profile]] which is the replacement for the profile attribute. [[User:Tantek|Tantek]] 23:24, 5 November 2009 (UTC)
* '''Microdata <code>itemprop</code> duplicates <code>class</code> data'''. the new attribute itemprop is designed to hold some meaningful data about an element, but class already exists to hold this data. Unsure of reasons why itemprop required?
** This is because microdata is designed to be generically parsable, even when the parser does not understand the vocabulary. As such, property names have to be on an explicit attribute, not shared with other, non-data classnames. --[[User:BenWard|BenWard]] 21:12, 4 September 2009 (UTC)
* '''The [http://microformats.org/wiki/value-class-pattern#Date_and_time_parsing recommended removal of the colon in timezone] doesn’t validate''' The relevant uF wiki text is “However the colons ":" separating the hours and minutes of any timezone offset are optional and discouraged in order to make it less likely that a timezone offset will be confused for a time.” ref: [http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#global-dates-and-times HTML5 time microsyntax for <time>] --[[User:Oli|Oli]] 14:40, 14 February 2010 (+9)
</div>

== see also ==
* [[HTML3]]

events/2010-02-17-webkit-html5-benkyokai

2010-02-13T14:15:18Z

Oli: creating page and adding info about event

<entry-title>3rd Webkit/HTML5 Benkyokai (第3回Webkit/HTML5勉強会)</entry-title>
__TOC__
One of several microformats [[events]].

<div class="event-page vevent">
== details ==
;When
:2010-02-17 from 19:00–20:00
;Where
:グリー株式会社, 東京都港区六本木4-1-4 黒崎ビル5F (Tokyo, Japan)
;What
:3rd Webkit/HTML5 Benkyokai (第3回Webkit/HTML5勉強会)
;Presenter
:[http://oli.jp/ Oli Studholme]
;Web
:http://atnd.org/events/3058

'''[http://feeds.technorati.com/events/microformats.org/wiki/events/2010-02-17-webkit-html5-benkyokai Add this event to your diary or calendar program]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== microformats & microdata ==

Oli Studholme will give an overview of Microformats & Microdata, and discuss using them in HTML5 for contact and event data (in Japanese)

== tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):

<kbd class="tags" style="display:block">
'''#html5j'''
microformats
tokyo
</kbd>

If you use Twitter, mention ''@microformats''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats Twitter Search].

== notes ==
Topics discussed:

* Microformats
* Microdata

== articles and blog posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below. Newest first.

* ...

</div> 

== related pages==
{{events-related-pages}}

events

2010-02-13T14:04:28Z

Oli: /* February */ shortening URL bf making event detail page

<entry-title>Microformats events</entry-title>
Please add microformats related events (including events which have sessions on microformats) below.

Use the [[events-template|events template]] to create events pages, and list URLs, details, attendees, recommended tags, link to photos afterwards, etc. Add links to slides and other media to the [[presentations]], [[podcasts]] pages respectively.

Encourage the use of microformats on event sites' pages themselves, e.g. [[hCalendar]] and [[hCard]] for the schedule, sessions, speakers, and venues.

== Add events to your calendar ==
Subscribe to current and future microformats events:

http://h2vx.com/ics/sub/microformats.org/wiki/events

Clicking that link will open your local calendar program (e.g. MacOSX iCal, Evolution, etc.)

Set it to update (i.e. <nowiki>[x]</nowiki> Refresh) every day and new events will appear automatically.

You may also download [http://h2vx.com/ics/microformats.org/wiki/events events on this page as an iCalendar file].

__TOC__

== regular ==
* [[weekly-meetup]] - weekly community meetups. details inside.

== upcoming ==


=== February ===
*2010-02-02 at 18:30: [[events/2010-02-02-weekly-dinner-mv|Microformats Weekly Meetup Mountain View]] at Gyros House, Mountain View, California. http://microformats.org/wiki/events/2010-02-02-weekly-dinner-mv

*2010-02-17 at 19:00: [[events/2010-02-17-webkit-html5-benkyokai|3rd Webkit/HTML5 Benkyokai (第3回Webkit/HTML5勉強会)]] at グリー株式会社（東京都港区六本木4-1-4 黒崎ビル5F (Tokyo, Japan)）. [http://oli.jp/ Oli Studholme] will talk about Microformats and Microdata (in Japanese). http://atnd.org/events/3058

=== March ===
*2010-03-10 to 2010-03-16: [[events/2010-03-12-sxsw|<abbr title="South by Southwest Interactive Festival">SXSWi</abbr>]] at Austin Convention Center, Austin.

== recent ==


=== January 2010 ===
*2010-01-19 at 19:00: [[events/2010-01-19-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2010-01-19-weekly-dinner-sf

*2010-01-12 at 18:30: [[events/2010-01-12-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pancho Villa Taqueria, San Francisco, California. http://microformats.org/wiki/events/2010-01-12-weekly-dinner-sf

*2010-01-05 at 18:30: [[events/2010-01-05-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California. http://microformats.org/wiki/events/2010-01-05-weekly-dinner-sf

=== December 2009 ===
*2009-12-08 at 18:30: [[events/2009-12-08-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2009-12-08-weekly-dinner-sf

*2009-12-04: [[events/2009-12-04-sf-workshop|San Francisco microformats workshop]] at San Francisco, CA. Taught by [http://tantek.com Tantek Çelik], this workshop covers just about everything you need to know to get started with microformats. http://microformats-sf.eventbrite.com

*2009-12-01 at 20:00: [[events/2009-12-01-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California. http://microformats.org/wiki/events/2009-12-01-weekly-dinner-sf

=== November 2009 ===
*2009-11-18: [[events/2009-11-18-nyc-workshop|New York City microformats workshop]] at New York City, NY. Taught by [http://tantek.com Tantek Çelik], this workshop covers just about everything you need to know to get started with microformats. http://microformats-nyc.eventbrite.com

=== October 2009 ===
*2009-10-20 at 19:00: [[events/2009-10-20-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2009-10-20-weekly-dinner-sf

*2009-10-07: [[events/2009-10-07-intro-to|Introduction to microformats]] at Uptown Sports Bar and Grill, Albuquerque, NM. Local microformats expert and Webuquerque co-manager, Emily Lewis, will discuss the history and basic premise of microformats, and will show examples of common microformats.. http://www.webuquerque.com/Events/Introduction-Microformats.php

*2009-10-06 at 19:00: [[events/2009-10-06-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at On The Corner Cafe, San Francisco, California. http://microformats.org/wiki/events/2009-10-06-weekly-dinner-sf

=== September 2009 ===
*2009-09-29 at 20:00: [[events/2009-09-29-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at Crossroads Cafe, San Francisco, California. http://microformats.org/wiki/events/2009-09-29-weekly-dinner-sf

*2009-09-23 at 20:00: [[events/2009-09-23-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California. http://microformats.org/wiki/events/2009-09-23-weekly-dinner-sf

*2009-09-01 at 18:30: [[events/2009-09-01-weekly-dinner-sf|Microformats Dinner San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2009-09-01-weekly-dinner-sf

=== August 2009 ===

*2009-08-25: [[events/2009-08-25-search-landscape|Expert Panel Event - The Evolving Search Landscape: Charting Seismic Shifts]] at Microsoft (San Francisco Campus), 835 Market st., San Francisco, CA. http://upcoming.yahoo.com/event/4356044

*2009-08-18 at <abbr class="value" title="18:00">6pm</abbr>: [[events/2009-08-18-sf-meetup|Diso + microformats + activity streams meetup]] at 21st Amendment. We'll be having an informal Diso + microformats + activity streams meetup/dinner. At 8pm, those who are interested will head to Citizen Space to get some work done reviewing the activity streams implementors draft spec: http://upcoming.yahoo.com/event/4234949/

*2009-08-12: [[events/2009-08-12-nyc-workshop|New York City microformats workshop]] at New York City, NY. Taught by [http://tantek.com Tantek Çelik], the workshop covered just about everything you need to know to get started with microformats. http://microformats.eventbrite.com

=== July 2009 ===

*2009-07-25..<abbr style="border:0" class="value" title="2009-07-26">26</abbr> til <abbr class="value" title="17:00">5pm</abbr>: [[events/2009-07-25-dev-camp|microformatsDevCamp]] at San Francisco, CA. The first ever microformatsDevCamp, for authors, designers, publishers, developers, engineers building pages, sites, and tools with microformats http://upcoming.yahoo.com/event/2888376

*2009-07-09 at 10:30: [[events/2009-07-09-scibarcamp-open-data|SciBarCamp session: open science open data on today's web]] at Room 1, 2nd floor, IFTF offices, Palo Alto, CA.

*2009-07-07 at 19:00: [[events/2009-07-07-weekly-dinner-sf|Microformats Dinner San Francisco]] at Andalu, 3198 16th st., San Francisco, California. http://upcoming.yahoo.com/event/3068255

=== June 2009 ===
*2009-06-27 at 18:00: [[events/2009-06-27-microformats-vevent-london|London Microformats vEvent]] at TBC, London.

*2009-06-26 at 19:00: [[events/2009-06-26-microformats-4th-bday|microformats 4th birthday party]] at [http://www.yelp.com/biz/b-restaurant-and-bar-san-francisco B Restaurant and Bar], 720 Howard Street, Yerba Buena Upper Terrace, San Francisco, CA 94103 USA. http://upcoming.yahoo.com/event/3010807

*2009-06-23 at 19:30: [[events/2009-06-23-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pancho Villa Taqueria, San Francisco, California. http://upcoming.yahoo.com/event/2988905/

*2009-06-18 at 13:00-18:00 and 2009-06-19 from 9:00-18:00: VoCamp at Yahoo's Sunnyvale campus.

*2009-06-17 at 15:45: [http://www.semantic-conference.com/session/2144/ Semantics at Google: RDFa, Microformats, and more] at the Fairmont Hotel, San Jose, California.[http://www.semantic-conference.com/2009/travel/ 2009 Semantic Technology Conference]

*2009-06-16 at 19:00: [[events/2009-06-16-weekly-dinner-sf|Microformats Dinner San Francisco]] at Mercury Lounge, 1582 Folsom Street, San Francisco, CA 94103 USA.http://upcoming.yahoo.com/event/2922429/

*2009-06-09 at 18:30: [[events/2009-06-09-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pizza Zone & Grill, San Francisco, California.http://upcoming.yahoo.com/event/2852506/

*2009-06-08: [[events/2009-06-08-london-web-standards|London Web Standards June: microformats]] at join http://www.meetup.com/londonwebstandards/ to see the location. http://www.meetup.com/londonwebstandards/calendar/10387218/

*2009-06-02 at 19:00: [[events/2009-06-02-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California.http://upcoming.yahoo.com/event/2801069/

=== May 2009 ===
*2009-05-20 at 20:00: [[events/2009-05-20-adr-geo-where20|geo/adr microformats BOF session at Where 2.0]] at Gold Room, 2nd floor, Fairmont San Jose, 170 South Market Street, San Jose, California 95113. Join us to discuss the all the recent buzz around [[geo]], [[adr]], and [[hCard]] microformats, support by [[google-search|Google in rich snippets]], and by [[yahoo-search|Yahoo in YQL and Y! Placemaker]]. http://upcoming.yahoo.com/event/2718033

*2009-05-19 at 19:00: [[events/2009-05-19-weekly-dinner-sf|Microformats Dinner San Francisco]] at Banana House, San Francisco, California. http://upcoming.yahoo.com/event/2656903

*2009-05-15 at 11:30: Twiist.be conference: Microformats and Transient Semantics. http://twiist.be/speakers/briansuda

*2009-05-12 at 19:00: [[events/2009-05-12-weekly-dinner-sf|Microformats Dinner San Francisco]] at Crepevine on Church st. in San Francisco, California. http://upcoming.yahoo.com/event/2656901

*2009-05-05: [[events/2009-05-05-weekly-dinner-sf|Microformats Dinner San Francisco]] at Chevy's on 3rd street in San Francisco, California. http://upcoming.yahoo.com/event/2568451

=== April 2009 ===
*2009-04-07: [[events/2009-04-07-weekly-dinner-sf|Microformats Dinner San Francisco]] at Crepes on Cole, San Francisco, California. http://upcoming.yahoo.com/event/2376470
*2009-04-14: [[events/2009-04-14-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pancho Villa Taqueria, San Francisco, California. http://upcoming.yahoo.com/event/2376478
*2009-04-20: [http://www.w3qc.org/communiques/archives/invitation-a-la-soiree-conference-du-20-avril-2009/ Microformats presentation] at Laika, Montéral, Québec. http://upcoming.yahoo.com/event/2423142/
*2009-04-21: [[events/2009-04-21-weekly-dinner-sf|Microformats Dinner San Francisco]] at Taylor's Automatic Refresher, San Francisco, California. http://upcoming.yahoo.com/event/2376483
*2009-04-28: [[events/2009-04-28-weekly-dinner-sf|Microformats Dinner San Francisco]] at Third Street Grill, San Francisco, California. http://upcoming.yahoo.com/event/2376485

=== March 2009 ===
*2009-03-31: [[events/2009-03-31-weekly-dinner-sf|Microformats Dinner San Francisco]] at Metreon Food Court, San Francisco, California. http://upcoming.yahoo.com/event/2295743
*2009-03-24: [[events/2009-03-24-weekly-dinner-sf|Microformats Dinner San Francisco]] at Naan N' Chutney, San Francisco, California. http://upcoming.yahoo.com/event/2171301
*2009-03-14: [[events/2009-03-14-sxsw-revolution|Microformats: A Quiet Revolution]] at Room 10, Austin Convention Center, Austin, TX. http://upcoming.yahoo.com/event/1825864/
*2009-03-03: [[events/2009-03-03-weekly-dinner-sf|Microformats Dinner San Francisco]] at Flippers, San Francisco, California.http://upcoming.yahoo.com/event/1918295/

=== February 2009 ===
*2009-02-24: [[events/2009-02-24-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California.http://upcoming.yahoo.com/event/1900098/
*2009-02-17: [[events/2009-02-17-weekly-dinner-sf|Microformats Dinner San Francisco]] at Naan N' Chutney, San Francisco, California. http://upcoming.yahoo.com/event/1840841/
* 2009-02-10 at 7pm: [[events/2009-02-10-weekly-dinner-sf|Microformats Dinner San Francisco]] at California Pizza Kitchen, San Francisco, California. http://upcoming.yahoo.com/event/1765705/
* 2009-02-03 at 7pm: [[events/2009-02-03-weekly-dinner-sf|Microformats Dinner San Francisco]] at Taqueria Pancho Villa, San Francisco, California. http://upcoming.yahoo.com/event/1519710/

=== January 2009 ===
* 2009-01-27 at 7pm: [[events/2009-01-27-weekly-dinner-sf|Microformats Dinner San Francisco]] at Crepes on Cole, San Francisco, California. http://upcoming.yahoo.com/event/1519151/
* 2009-01-20 at 8pm: [[events/2009-01-20-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, 2nd Street, San Francisco, California
* 2009-01-13 at 6:30pm: [[events/2009-01-13-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, 2nd Street, San Francisco, California · http://upcoming.yahoo.com/event/1489360/
* 2009-01-06 at 6:30pm: [[events/2009-01-06-weekly-dinner-sf|Microformats Dinner San Francisco]] at Westfield Shopping Centre Food Court, 818 Mission Street, San Francisco, California · http://upcoming.yahoo.com/event/1467444/

== Previous events ==
Previous years' events can be found at the following:
* [[events-2009]]
* [[events-2008]]
* [[events-2007]]
* [[events-2006]]

== Other languages ==
* [[current_events-fr|événements en cours]] (fr)

== Quicktime Broadcaster Notes ==

See [[quicktime]]

==Related pages==
{{events-related-pages}}

events-template

2010-02-13T13:58:34Z

Oli: someone forgot ""

<entry-title>Template for events</entry-title>

You can cut & paste the following for [[events]] pages. Delete any unwanted sections, and remove comment mark-up from those you wish to use at latter stage.:

<pre><nowiki>

<entry-title>Microformats Event</entry-title>
__TOC__
One of several microformats [[events]].

<div class="event-page vevent">
== details ==
;When
:2010-mm-dd–2010-mm-dd
;Where
:xxxVenuexxx, xxxAddressMicroformatComponentsxxx xxxCountryxxx
;What
:xxxxx
;Presenter
:[xxxUrlxxx xxxNamexxx]
;Web
:http://example.com

'''[http://feeds.technorati.com/events/microformats.org/wiki/events/xxxPageURLxxx Add this event to your diary or calendar program]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):


<kbd class="tags" style="display:block">
'''EVENTSPECIFICTAG'''
microformats
san-francisco
''upcoming:event=00000000'' 
</kbd>

If you use Twitter, mention ''@microformats''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats Twitter Search].

== attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended.

* [[User:YourUserName|Your full name (fn)]]
* ...

== photographs ==

* ...

== notes ==
Topics discussed, comments, and Q&A.

* …

== articles and blog posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below. Newest first.

* ...

</div> 

== related pages==
{{events-related-pages}}

</nowiki></pre>

==Related pages==
{{events-related-pages}}

events-template

2010-02-13T13:57:11Z

Oli: changing 2009 to 2010

<entry-title>Template for events</entry-title>

You can cut & paste the following for [[events]] pages. Delete any unwanted sections, and remove comment mark-up from those you wish to use at latter stage.:

<pre><nowiki>

<entry-title>Microformats Event</entry-title>
__TOC__
One of several microformats [[events]].

<div class="event-page vevent">
== details ==
;When
:2010-mm-dd–2010-mm-dd
;Where
:xxxVenuexxx, xxxAddressMicroformatComponentsxxx xxxCountryxxx
;What
:xxxxx
;Presenter
:[xxxUrlxxx xxxNamexxx]
;Web
:http://example.com

'''[http://feeds.technorati.com/events/microformats.org/wiki/events/xxxPageURLxxx Add this event to your diary or calendar program]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== tags ==
Use the following tags on related content (blog posts, photos, [http://twitter.com tweets]):


<kbd class="tags" style="display:block">
'''EVENTSPECIFICTAG'''
microformats
san-francisco
''upcoming:event=00000000'' 
</kbd>

If you use Twitter, mention ''@microformats''' in tweets about the event, and track them on [http://search.twitter.com/search?q=microformats Twitter Search].

== attendees ==
Add yourself alphabetically sorted by family name if you plan on attending or attended.

* [[User:YourUserName|Your full name (fn)]]
* ...

== photographs ==

* ...

== notes ==
Topics discussed, comments, and Q&A.

* …

== articles and blog posts ==
Articles and blog posts following up on the meetup. Add a link to your post in the list below. Newest first.

* ...

</div> 

== related pages==
{{events-related-pages}}

</nowiki></pre>

==Related pages==
{{events-related-pages}}

events

2010-02-13T13:47:38Z

Oli: heh, can’t mark myself up using vcard

<entry-title>Microformats events</entry-title>
Please add microformats related events (including events which have sessions on microformats) below.

Use the [[events-template|events template]] to create events pages, and list URLs, details, attendees, recommended tags, link to photos afterwards, etc. Add links to slides and other media to the [[presentations]], [[podcasts]] pages respectively.

Encourage the use of microformats on event sites' pages themselves, e.g. [[hCalendar]] and [[hCard]] for the schedule, sessions, speakers, and venues.

== Add events to your calendar ==
Subscribe to current and future microformats events:

http://h2vx.com/ics/sub/microformats.org/wiki/events

Clicking that link will open your local calendar program (e.g. MacOSX iCal, Evolution, etc.)

Set it to update (i.e. <nowiki>[x]</nowiki> Refresh) every day and new events will appear automatically.

You may also download [http://h2vx.com/ics/microformats.org/wiki/events events on this page as an iCalendar file].

__TOC__

== regular ==
* [[weekly-meetup]] - weekly community meetups. details inside.

== upcoming ==


=== February ===
*2010-02-02 at 18:30: [[events/2010-02-02-weekly-dinner-mv|Microformats Weekly Meetup Mountain View]] at Gyros House, Mountain View, California. http://microformats.org/wiki/events/2010-02-02-weekly-dinner-mv

*2010-02-17 at 19:00: [[events/2010-02-17-3rd-webkit-html5-benkyokai|3rd Webkit/HTML5 Benkyokai (第3回Webkit/HTML5勉強会)]] at グリー株式会社（東京都港区六本木4-1-4 黒崎ビル5F (Tokyo, Japan)）. [http://oli.jp/ Oli Studholme] will talk about Microformats and Microdata (in Japanese). http://atnd.org/events/3058

=== March ===
*2010-03-10 to 2010-03-16: [[events/2010-03-12-sxsw|<abbr title="South by Southwest Interactive Festival">SXSWi</abbr>]] at Austin Convention Center, Austin.

== recent ==


=== January 2010 ===
*2010-01-19 at 19:00: [[events/2010-01-19-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2010-01-19-weekly-dinner-sf

*2010-01-12 at 18:30: [[events/2010-01-12-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pancho Villa Taqueria, San Francisco, California. http://microformats.org/wiki/events/2010-01-12-weekly-dinner-sf

*2010-01-05 at 18:30: [[events/2010-01-05-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California. http://microformats.org/wiki/events/2010-01-05-weekly-dinner-sf

=== December 2009 ===
*2009-12-08 at 18:30: [[events/2009-12-08-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2009-12-08-weekly-dinner-sf

*2009-12-04: [[events/2009-12-04-sf-workshop|San Francisco microformats workshop]] at San Francisco, CA. Taught by [http://tantek.com Tantek Çelik], this workshop covers just about everything you need to know to get started with microformats. http://microformats-sf.eventbrite.com

*2009-12-01 at 20:00: [[events/2009-12-01-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California. http://microformats.org/wiki/events/2009-12-01-weekly-dinner-sf

=== November 2009 ===
*2009-11-18: [[events/2009-11-18-nyc-workshop|New York City microformats workshop]] at New York City, NY. Taught by [http://tantek.com Tantek Çelik], this workshop covers just about everything you need to know to get started with microformats. http://microformats-nyc.eventbrite.com

=== October 2009 ===
*2009-10-20 at 19:00: [[events/2009-10-20-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2009-10-20-weekly-dinner-sf

*2009-10-07: [[events/2009-10-07-intro-to|Introduction to microformats]] at Uptown Sports Bar and Grill, Albuquerque, NM. Local microformats expert and Webuquerque co-manager, Emily Lewis, will discuss the history and basic premise of microformats, and will show examples of common microformats.. http://www.webuquerque.com/Events/Introduction-Microformats.php

*2009-10-06 at 19:00: [[events/2009-10-06-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at On The Corner Cafe, San Francisco, California. http://microformats.org/wiki/events/2009-10-06-weekly-dinner-sf

=== September 2009 ===
*2009-09-29 at 20:00: [[events/2009-09-29-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at Crossroads Cafe, San Francisco, California. http://microformats.org/wiki/events/2009-09-29-weekly-dinner-sf

*2009-09-23 at 20:00: [[events/2009-09-23-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California. http://microformats.org/wiki/events/2009-09-23-weekly-dinner-sf

*2009-09-01 at 18:30: [[events/2009-09-01-weekly-dinner-sf|Microformats Dinner San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2009-09-01-weekly-dinner-sf

=== August 2009 ===

*2009-08-25: [[events/2009-08-25-search-landscape|Expert Panel Event - The Evolving Search Landscape: Charting Seismic Shifts]] at Microsoft (San Francisco Campus), 835 Market st., San Francisco, CA. http://upcoming.yahoo.com/event/4356044

*2009-08-18 at <abbr class="value" title="18:00">6pm</abbr>: [[events/2009-08-18-sf-meetup|Diso + microformats + activity streams meetup]] at 21st Amendment. We'll be having an informal Diso + microformats + activity streams meetup/dinner. At 8pm, those who are interested will head to Citizen Space to get some work done reviewing the activity streams implementors draft spec: http://upcoming.yahoo.com/event/4234949/

*2009-08-12: [[events/2009-08-12-nyc-workshop|New York City microformats workshop]] at New York City, NY. Taught by [http://tantek.com Tantek Çelik], the workshop covered just about everything you need to know to get started with microformats. http://microformats.eventbrite.com

=== July 2009 ===

*2009-07-25..<abbr style="border:0" class="value" title="2009-07-26">26</abbr> til <abbr class="value" title="17:00">5pm</abbr>: [[events/2009-07-25-dev-camp|microformatsDevCamp]] at San Francisco, CA. The first ever microformatsDevCamp, for authors, designers, publishers, developers, engineers building pages, sites, and tools with microformats http://upcoming.yahoo.com/event/2888376

*2009-07-09 at 10:30: [[events/2009-07-09-scibarcamp-open-data|SciBarCamp session: open science open data on today's web]] at Room 1, 2nd floor, IFTF offices, Palo Alto, CA.

*2009-07-07 at 19:00: [[events/2009-07-07-weekly-dinner-sf|Microformats Dinner San Francisco]] at Andalu, 3198 16th st., San Francisco, California. http://upcoming.yahoo.com/event/3068255

=== June 2009 ===
*2009-06-27 at 18:00: [[events/2009-06-27-microformats-vevent-london|London Microformats vEvent]] at TBC, London.

*2009-06-26 at 19:00: [[events/2009-06-26-microformats-4th-bday|microformats 4th birthday party]] at [http://www.yelp.com/biz/b-restaurant-and-bar-san-francisco B Restaurant and Bar], 720 Howard Street, Yerba Buena Upper Terrace, San Francisco, CA 94103 USA. http://upcoming.yahoo.com/event/3010807

*2009-06-23 at 19:30: [[events/2009-06-23-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pancho Villa Taqueria, San Francisco, California. http://upcoming.yahoo.com/event/2988905/

*2009-06-18 at 13:00-18:00 and 2009-06-19 from 9:00-18:00: VoCamp at Yahoo's Sunnyvale campus.

*2009-06-17 at 15:45: [http://www.semantic-conference.com/session/2144/ Semantics at Google: RDFa, Microformats, and more] at the Fairmont Hotel, San Jose, California.[http://www.semantic-conference.com/2009/travel/ 2009 Semantic Technology Conference]

*2009-06-16 at 19:00: [[events/2009-06-16-weekly-dinner-sf|Microformats Dinner San Francisco]] at Mercury Lounge, 1582 Folsom Street, San Francisco, CA 94103 USA.http://upcoming.yahoo.com/event/2922429/

*2009-06-09 at 18:30: [[events/2009-06-09-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pizza Zone & Grill, San Francisco, California.http://upcoming.yahoo.com/event/2852506/

*2009-06-08: [[events/2009-06-08-london-web-standards|London Web Standards June: microformats]] at join http://www.meetup.com/londonwebstandards/ to see the location. http://www.meetup.com/londonwebstandards/calendar/10387218/

*2009-06-02 at 19:00: [[events/2009-06-02-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California.http://upcoming.yahoo.com/event/2801069/

=== May 2009 ===
*2009-05-20 at 20:00: [[events/2009-05-20-adr-geo-where20|geo/adr microformats BOF session at Where 2.0]] at Gold Room, 2nd floor, Fairmont San Jose, 170 South Market Street, San Jose, California 95113. Join us to discuss the all the recent buzz around [[geo]], [[adr]], and [[hCard]] microformats, support by [[google-search|Google in rich snippets]], and by [[yahoo-search|Yahoo in YQL and Y! Placemaker]]. http://upcoming.yahoo.com/event/2718033

*2009-05-19 at 19:00: [[events/2009-05-19-weekly-dinner-sf|Microformats Dinner San Francisco]] at Banana House, San Francisco, California. http://upcoming.yahoo.com/event/2656903

*2009-05-15 at 11:30: Twiist.be conference: Microformats and Transient Semantics. http://twiist.be/speakers/briansuda

*2009-05-12 at 19:00: [[events/2009-05-12-weekly-dinner-sf|Microformats Dinner San Francisco]] at Crepevine on Church st. in San Francisco, California. http://upcoming.yahoo.com/event/2656901

*2009-05-05: [[events/2009-05-05-weekly-dinner-sf|Microformats Dinner San Francisco]] at Chevy's on 3rd street in San Francisco, California. http://upcoming.yahoo.com/event/2568451

=== April 2009 ===
*2009-04-07: [[events/2009-04-07-weekly-dinner-sf|Microformats Dinner San Francisco]] at Crepes on Cole, San Francisco, California. http://upcoming.yahoo.com/event/2376470
*2009-04-14: [[events/2009-04-14-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pancho Villa Taqueria, San Francisco, California. http://upcoming.yahoo.com/event/2376478
*2009-04-20: [http://www.w3qc.org/communiques/archives/invitation-a-la-soiree-conference-du-20-avril-2009/ Microformats presentation] at Laika, Montéral, Québec. http://upcoming.yahoo.com/event/2423142/
*2009-04-21: [[events/2009-04-21-weekly-dinner-sf|Microformats Dinner San Francisco]] at Taylor's Automatic Refresher, San Francisco, California. http://upcoming.yahoo.com/event/2376483
*2009-04-28: [[events/2009-04-28-weekly-dinner-sf|Microformats Dinner San Francisco]] at Third Street Grill, San Francisco, California. http://upcoming.yahoo.com/event/2376485

=== March 2009 ===
*2009-03-31: [[events/2009-03-31-weekly-dinner-sf|Microformats Dinner San Francisco]] at Metreon Food Court, San Francisco, California. http://upcoming.yahoo.com/event/2295743
*2009-03-24: [[events/2009-03-24-weekly-dinner-sf|Microformats Dinner San Francisco]] at Naan N' Chutney, San Francisco, California. http://upcoming.yahoo.com/event/2171301
*2009-03-14: [[events/2009-03-14-sxsw-revolution|Microformats: A Quiet Revolution]] at Room 10, Austin Convention Center, Austin, TX. http://upcoming.yahoo.com/event/1825864/
*2009-03-03: [[events/2009-03-03-weekly-dinner-sf|Microformats Dinner San Francisco]] at Flippers, San Francisco, California.http://upcoming.yahoo.com/event/1918295/

=== February 2009 ===
*2009-02-24: [[events/2009-02-24-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California.http://upcoming.yahoo.com/event/1900098/
*2009-02-17: [[events/2009-02-17-weekly-dinner-sf|Microformats Dinner San Francisco]] at Naan N' Chutney, San Francisco, California. http://upcoming.yahoo.com/event/1840841/
* 2009-02-10 at 7pm: [[events/2009-02-10-weekly-dinner-sf|Microformats Dinner San Francisco]] at California Pizza Kitchen, San Francisco, California. http://upcoming.yahoo.com/event/1765705/
* 2009-02-03 at 7pm: [[events/2009-02-03-weekly-dinner-sf|Microformats Dinner San Francisco]] at Taqueria Pancho Villa, San Francisco, California. http://upcoming.yahoo.com/event/1519710/

=== January 2009 ===
* 2009-01-27 at 7pm: [[events/2009-01-27-weekly-dinner-sf|Microformats Dinner San Francisco]] at Crepes on Cole, San Francisco, California. http://upcoming.yahoo.com/event/1519151/
* 2009-01-20 at 8pm: [[events/2009-01-20-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, 2nd Street, San Francisco, California
* 2009-01-13 at 6:30pm: [[events/2009-01-13-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, 2nd Street, San Francisco, California · http://upcoming.yahoo.com/event/1489360/
* 2009-01-06 at 6:30pm: [[events/2009-01-06-weekly-dinner-sf|Microformats Dinner San Francisco]] at Westfield Shopping Centre Food Court, 818 Mission Street, San Francisco, California · http://upcoming.yahoo.com/event/1467444/

== Previous events ==
Previous years' events can be found at the following:
* [[events-2009]]
* [[events-2008]]
* [[events-2007]]
* [[events-2006]]

== Other languages ==
* [[current_events-fr|événements en cours]] (fr)

== Quicktime Broadcaster Notes ==

See [[quicktime]]

==Related pages==
{{events-related-pages}}

events

2010-02-13T13:44:34Z

Oli: Adding an event in Tokyo

<entry-title>Microformats events</entry-title>
Please add microformats related events (including events which have sessions on microformats) below.

Use the [[events-template|events template]] to create events pages, and list URLs, details, attendees, recommended tags, link to photos afterwards, etc. Add links to slides and other media to the [[presentations]], [[podcasts]] pages respectively.

Encourage the use of microformats on event sites' pages themselves, e.g. [[hCalendar]] and [[hCard]] for the schedule, sessions, speakers, and venues.

== Add events to your calendar ==
Subscribe to current and future microformats events:

http://h2vx.com/ics/sub/microformats.org/wiki/events

Clicking that link will open your local calendar program (e.g. MacOSX iCal, Evolution, etc.)

Set it to update (i.e. <nowiki>[x]</nowiki> Refresh) every day and new events will appear automatically.

You may also download [http://h2vx.com/ics/microformats.org/wiki/events events on this page as an iCalendar file].

__TOC__

== regular ==
* [[weekly-meetup]] - weekly community meetups. details inside.

== upcoming ==


=== February ===
*2010-02-02 at 18:30: [[events/2010-02-02-weekly-dinner-mv|Microformats Weekly Meetup Mountain View]] at Gyros House, Mountain View, California. http://microformats.org/wiki/events/2010-02-02-weekly-dinner-mv

*2010-02-17 at 19:00: [[events/2010-02-17-3rd-webkit-html5-benkyokai|3rd Webkit/HTML5 Benkyokai (第3回Webkit/HTML5勉強会)]] at グリー株式会社（東京都港区六本木4-1-4 黒崎ビル5F (Tokyo, Japan)）. <a class="fn url" href="http://oli.jp/" title="Writing & such by Oli Studholme (@boblet)">Oli Studholme</a> will talk about Microformats and Microdata (in Japanese). http://atnd.org/events/3058

=== March ===
*2010-03-10 to 2010-03-16: [[events/2010-03-12-sxsw|<abbr title="South by Southwest Interactive Festival">SXSWi</abbr>]] at Austin Convention Center, Austin.

== recent ==


=== January 2010 ===
*2010-01-19 at 19:00: [[events/2010-01-19-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2010-01-19-weekly-dinner-sf

*2010-01-12 at 18:30: [[events/2010-01-12-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pancho Villa Taqueria, San Francisco, California. http://microformats.org/wiki/events/2010-01-12-weekly-dinner-sf

*2010-01-05 at 18:30: [[events/2010-01-05-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California. http://microformats.org/wiki/events/2010-01-05-weekly-dinner-sf

=== December 2009 ===
*2009-12-08 at 18:30: [[events/2009-12-08-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2009-12-08-weekly-dinner-sf

*2009-12-04: [[events/2009-12-04-sf-workshop|San Francisco microformats workshop]] at San Francisco, CA. Taught by [http://tantek.com Tantek Çelik], this workshop covers just about everything you need to know to get started with microformats. http://microformats-sf.eventbrite.com

*2009-12-01 at 20:00: [[events/2009-12-01-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California. http://microformats.org/wiki/events/2009-12-01-weekly-dinner-sf

=== November 2009 ===
*2009-11-18: [[events/2009-11-18-nyc-workshop|New York City microformats workshop]] at New York City, NY. Taught by [http://tantek.com Tantek Çelik], this workshop covers just about everything you need to know to get started with microformats. http://microformats-nyc.eventbrite.com

=== October 2009 ===
*2009-10-20 at 19:00: [[events/2009-10-20-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2009-10-20-weekly-dinner-sf

*2009-10-07: [[events/2009-10-07-intro-to|Introduction to microformats]] at Uptown Sports Bar and Grill, Albuquerque, NM. Local microformats expert and Webuquerque co-manager, Emily Lewis, will discuss the history and basic premise of microformats, and will show examples of common microformats.. http://www.webuquerque.com/Events/Introduction-Microformats.php

*2009-10-06 at 19:00: [[events/2009-10-06-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at On The Corner Cafe, San Francisco, California. http://microformats.org/wiki/events/2009-10-06-weekly-dinner-sf

=== September 2009 ===
*2009-09-29 at 20:00: [[events/2009-09-29-weekly-dinner-sf|Microformats Weekly Meetup San Francisco]] at Crossroads Cafe, San Francisco, California. http://microformats.org/wiki/events/2009-09-29-weekly-dinner-sf

*2009-09-23 at 20:00: [[events/2009-09-23-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California. http://microformats.org/wiki/events/2009-09-23-weekly-dinner-sf

*2009-09-01 at 18:30: [[events/2009-09-01-weekly-dinner-sf|Microformats Dinner San Francisco]] at Westfield Food Court, San Francisco, California. http://microformats.org/wiki/events/2009-09-01-weekly-dinner-sf

=== August 2009 ===

*2009-08-25: [[events/2009-08-25-search-landscape|Expert Panel Event - The Evolving Search Landscape: Charting Seismic Shifts]] at Microsoft (San Francisco Campus), 835 Market st., San Francisco, CA. http://upcoming.yahoo.com/event/4356044

*2009-08-18 at <abbr class="value" title="18:00">6pm</abbr>: [[events/2009-08-18-sf-meetup|Diso + microformats + activity streams meetup]] at 21st Amendment. We'll be having an informal Diso + microformats + activity streams meetup/dinner. At 8pm, those who are interested will head to Citizen Space to get some work done reviewing the activity streams implementors draft spec: http://upcoming.yahoo.com/event/4234949/

*2009-08-12: [[events/2009-08-12-nyc-workshop|New York City microformats workshop]] at New York City, NY. Taught by [http://tantek.com Tantek Çelik], the workshop covered just about everything you need to know to get started with microformats. http://microformats.eventbrite.com

=== July 2009 ===

*2009-07-25..<abbr style="border:0" class="value" title="2009-07-26">26</abbr> til <abbr class="value" title="17:00">5pm</abbr>: [[events/2009-07-25-dev-camp|microformatsDevCamp]] at San Francisco, CA. The first ever microformatsDevCamp, for authors, designers, publishers, developers, engineers building pages, sites, and tools with microformats http://upcoming.yahoo.com/event/2888376

*2009-07-09 at 10:30: [[events/2009-07-09-scibarcamp-open-data|SciBarCamp session: open science open data on today's web]] at Room 1, 2nd floor, IFTF offices, Palo Alto, CA.

*2009-07-07 at 19:00: [[events/2009-07-07-weekly-dinner-sf|Microformats Dinner San Francisco]] at Andalu, 3198 16th st., San Francisco, California. http://upcoming.yahoo.com/event/3068255

=== June 2009 ===
*2009-06-27 at 18:00: [[events/2009-06-27-microformats-vevent-london|London Microformats vEvent]] at TBC, London.

*2009-06-26 at 19:00: [[events/2009-06-26-microformats-4th-bday|microformats 4th birthday party]] at [http://www.yelp.com/biz/b-restaurant-and-bar-san-francisco B Restaurant and Bar], 720 Howard Street, Yerba Buena Upper Terrace, San Francisco, CA 94103 USA. http://upcoming.yahoo.com/event/3010807

*2009-06-23 at 19:30: [[events/2009-06-23-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pancho Villa Taqueria, San Francisco, California. http://upcoming.yahoo.com/event/2988905/

*2009-06-18 at 13:00-18:00 and 2009-06-19 from 9:00-18:00: VoCamp at Yahoo's Sunnyvale campus.

*2009-06-17 at 15:45: [http://www.semantic-conference.com/session/2144/ Semantics at Google: RDFa, Microformats, and more] at the Fairmont Hotel, San Jose, California.[http://www.semantic-conference.com/2009/travel/ 2009 Semantic Technology Conference]

*2009-06-16 at 19:00: [[events/2009-06-16-weekly-dinner-sf|Microformats Dinner San Francisco]] at Mercury Lounge, 1582 Folsom Street, San Francisco, CA 94103 USA.http://upcoming.yahoo.com/event/2922429/

*2009-06-09 at 18:30: [[events/2009-06-09-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pizza Zone & Grill, San Francisco, California.http://upcoming.yahoo.com/event/2852506/

*2009-06-08: [[events/2009-06-08-london-web-standards|London Web Standards June: microformats]] at join http://www.meetup.com/londonwebstandards/ to see the location. http://www.meetup.com/londonwebstandards/calendar/10387218/

*2009-06-02 at 19:00: [[events/2009-06-02-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California.http://upcoming.yahoo.com/event/2801069/

=== May 2009 ===
*2009-05-20 at 20:00: [[events/2009-05-20-adr-geo-where20|geo/adr microformats BOF session at Where 2.0]] at Gold Room, 2nd floor, Fairmont San Jose, 170 South Market Street, San Jose, California 95113. Join us to discuss the all the recent buzz around [[geo]], [[adr]], and [[hCard]] microformats, support by [[google-search|Google in rich snippets]], and by [[yahoo-search|Yahoo in YQL and Y! Placemaker]]. http://upcoming.yahoo.com/event/2718033

*2009-05-19 at 19:00: [[events/2009-05-19-weekly-dinner-sf|Microformats Dinner San Francisco]] at Banana House, San Francisco, California. http://upcoming.yahoo.com/event/2656903

*2009-05-15 at 11:30: Twiist.be conference: Microformats and Transient Semantics. http://twiist.be/speakers/briansuda

*2009-05-12 at 19:00: [[events/2009-05-12-weekly-dinner-sf|Microformats Dinner San Francisco]] at Crepevine on Church st. in San Francisco, California. http://upcoming.yahoo.com/event/2656901

*2009-05-05: [[events/2009-05-05-weekly-dinner-sf|Microformats Dinner San Francisco]] at Chevy's on 3rd street in San Francisco, California. http://upcoming.yahoo.com/event/2568451

=== April 2009 ===
*2009-04-07: [[events/2009-04-07-weekly-dinner-sf|Microformats Dinner San Francisco]] at Crepes on Cole, San Francisco, California. http://upcoming.yahoo.com/event/2376470
*2009-04-14: [[events/2009-04-14-weekly-dinner-sf|Microformats Dinner San Francisco]] at Pancho Villa Taqueria, San Francisco, California. http://upcoming.yahoo.com/event/2376478
*2009-04-20: [http://www.w3qc.org/communiques/archives/invitation-a-la-soiree-conference-du-20-avril-2009/ Microformats presentation] at Laika, Montéral, Québec. http://upcoming.yahoo.com/event/2423142/
*2009-04-21: [[events/2009-04-21-weekly-dinner-sf|Microformats Dinner San Francisco]] at Taylor's Automatic Refresher, San Francisco, California. http://upcoming.yahoo.com/event/2376483
*2009-04-28: [[events/2009-04-28-weekly-dinner-sf|Microformats Dinner San Francisco]] at Third Street Grill, San Francisco, California. http://upcoming.yahoo.com/event/2376485

=== March 2009 ===
*2009-03-31: [[events/2009-03-31-weekly-dinner-sf|Microformats Dinner San Francisco]] at Metreon Food Court, San Francisco, California. http://upcoming.yahoo.com/event/2295743
*2009-03-24: [[events/2009-03-24-weekly-dinner-sf|Microformats Dinner San Francisco]] at Naan N' Chutney, San Francisco, California. http://upcoming.yahoo.com/event/2171301
*2009-03-14: [[events/2009-03-14-sxsw-revolution|Microformats: A Quiet Revolution]] at Room 10, Austin Convention Center, Austin, TX. http://upcoming.yahoo.com/event/1825864/
*2009-03-03: [[events/2009-03-03-weekly-dinner-sf|Microformats Dinner San Francisco]] at Flippers, San Francisco, California.http://upcoming.yahoo.com/event/1918295/

=== February 2009 ===
*2009-02-24: [[events/2009-02-24-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, San Francisco, California.http://upcoming.yahoo.com/event/1900098/
*2009-02-17: [[events/2009-02-17-weekly-dinner-sf|Microformats Dinner San Francisco]] at Naan N' Chutney, San Francisco, California. http://upcoming.yahoo.com/event/1840841/
* 2009-02-10 at 7pm: [[events/2009-02-10-weekly-dinner-sf|Microformats Dinner San Francisco]] at California Pizza Kitchen, San Francisco, California. http://upcoming.yahoo.com/event/1765705/
* 2009-02-03 at 7pm: [[events/2009-02-03-weekly-dinner-sf|Microformats Dinner San Francisco]] at Taqueria Pancho Villa, San Francisco, California. http://upcoming.yahoo.com/event/1519710/

=== January 2009 ===
* 2009-01-27 at 7pm: [[events/2009-01-27-weekly-dinner-sf|Microformats Dinner San Francisco]] at Crepes on Cole, San Francisco, California. http://upcoming.yahoo.com/event/1519151/
* 2009-01-20 at 8pm: [[events/2009-01-20-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, 2nd Street, San Francisco, California
* 2009-01-13 at 6:30pm: [[events/2009-01-13-weekly-dinner-sf|Microformats Dinner San Francisco]] at 21st Amendment, 2nd Street, San Francisco, California · http://upcoming.yahoo.com/event/1489360/
* 2009-01-06 at 6:30pm: [[events/2009-01-06-weekly-dinner-sf|Microformats Dinner San Francisco]] at Westfield Shopping Centre Food Court, 818 Mission Street, San Francisco, California · http://upcoming.yahoo.com/event/1467444/

== Previous events ==
Previous years' events can be found at the following:
* [[events-2009]]
* [[events-2008]]
* [[events-2007]]
* [[events-2006]]

== Other languages ==
* [[current_events-fr|événements en cours]] (fr)

== Quicktime Broadcaster Notes ==

See [[quicktime]]

==Related pages==
{{events-related-pages}}