Microformats Wiki - User contributions [en]

h2vx

2015-10-13T14:29:26Z

Brian: Helping debug the code a bit from afar

<entry-title>H2VX</entry-title>

<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.
* 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).

=== open source ===
H2VX is available on the microformats github:
* https://github.com/microformats/h2vx.com

==== setting up your own H2VX ====
* get the files from https://github.com/microformats/h2vx.com
* ...
(in progress)

==== history ====
Some of the open source history behind H2VX can be found with history of X2V. E.g.
* 2006-04-19 Dan Connolly: [http://dig.csail.mit.edu/breadcrumbs/node/127 busy day in #microformats]
* ...

== 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]]

'''The contact conversion service''' @ http://h2vx.com/vcf/ fails with the error :
Fatal error: Call-time pass-by-reference has been removed in /home/tantek/domains/h2vx.com/public_html/vcf/get-contact.php on line 106

Why this error now ?
Is it possible to repair it ?
This link is very useful
Thank you

The error is on line 106, looking at the source-code, 106 is a print statement. It might be useful to turn on error reporting http://php.net/manual/en/function.error-reporting.php to get a better explanation and what line in the code that is on the server is failing. Then we can debug. Like 114 the regular expression smells like it might be the problem. There is an & which would be pass-by-reference.

=== value class pattern empty span fails ===
* This calendar: http://www.ustreetmusichall.com/calendar results in a ics file that gives Error at line 11: Unparseable date: "T220000" when imported into Google calendar
** 2012-154 verified with both h2vx.com and dev.h2vx.com. Page uses [[value class pattern]], in particular, empty span technique which seems valid. Need to make a test case of this to isolate and track down. - [[User:Tantek|Tantek]] 19:42, 2 June 2012 (UTC)
<source lang=html4strict>


10:00 pm

</source>

=== empty document from arjw.ifmw.mobi ===
(needs investigation)
* Have been getting an error where it says that its a "empty document; no HTML can be found" from [https://arjw.ifmw.mobi/index.php my site]. As with the comment below, there are no issues with using Operator to extract. I used to use this service a good while ago, but since moving to PHP/HTML5 for this page, I'm getting this error. [[User:ARJWright|Antoine RJ Wright]] 04:17:49, 7 January 2010 (UTC)

=== unable to extract hCards on marinersmexico ===
(needs investigation)
* The last few days I've not been able to retrieve vCards from hCards on [http://www.marinersmexico.com/contact/ this site] using H2VX yet Operator is nicely extracting them. Comments and insights appreciated. [[User:ChipD|ChipD]] 05:13, 12 November 2010 (UTC)

=== hCard ids not working with referrer ===
(needs investigation)
* Can't seem to get #hcard-ids working with the /referrer option. [[User:Jnpcl|Jnpcl]] 00:01, 14 October 2010 (UTC)
** Could you provide the URL you are having trouble with? [[User:Tantek|Tantek]] 18:51, 29 October 2010 (UTC)

=== hard to find URLs to put on a page ===
* 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)

=== possible problem with iOS6 ===
from: https://twitter.com/equivalentideas/status/275120059788169216

<blockquote class="twitter-tweet">#microformats there seems to be a problem with downloading the #hcard via @h2vx in #IOS6 @t— Luke Bacon (@equivalentideas) December 2, 2012</blockquote>

=== robots.txt prevents subscription in Google Reader ===
Google Reader won't subscribe to any h2vx hCalendar files due to robots.txt. [[User:TomMorris|TomMorris]] 15:33, 1 June 2011 (UTC)
:Google Calendar also fails because of their [http://h2vx.com/robots.txt robots.txt] which disallows robots from fetching and therefore caching the ical files. [[User:Jayvdb|Jayvdb]] 22:16, 5 May 2012 (UTC)

Apparently, I was correct in thinking Google would likely have a unique user-agent specifically for calendar fetches (see e.g. quote below) but they don't. It's not on [http://support.google.com/webmasters/bin/answer.py?hl=en&answer=1061943 the UA list] and I tested empirically (`sudo nc -v -l -p 80`) and it is a generic UA. ;( Someone should retest Google Reader to see if it works.
<blockquote>Google has several other user-agents, including Feedfetcher (user-agent Feedfetcher-Google). Since Feedfetcher requests come from explicit action by human users who have added the feeds to their [http://www.google.com/ig Google home page] or to [http://www.google.com/reader Google Reader]], and not from automated crawlers, Feedfetcher does not follow robots.txt guidelines. You can prevent Feedfetcher from crawling your site by configuring your server to serve a 404, 410, or other error status message to user-agent Feedfetcher-Google.[http://support.google.com/webmasters/bin/answer.py?answer=178852 More information about Feedfetcher.]</blockquote> <ref>http://support.google.com/webmasters/bin/answer.py?hl=en&answer=182072</ref> --[[User:Jeremyb|Jeremyb]] 22:34, 12 June 2012 (UTC)
:On second thought, I tested w/ a real webserver (+tcpdump) to see if /robots.txt was fetched with a different agent than the actual feed. no such luck.
<pre>From: googlebot(at)googlebot.com
User-Agent: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)</pre>
:--[[User:Jeremyb|Jeremyb]] 22:34, 12 June 2012 (UTC)

=== Date incorrect when not using abbr element for dtstart ===

I had a date marked up like so Wednesday, October 20, 2010. It was not being parsed correctly until I changed it to use <abbr>, but the element shouldn't really make any difference.

=== .vcf not formed properly ===

When opening the resultant .vcf files with Outlook, all non-standard characters are not shown correctly, due to the fact that the returned file is not encoded as UTF-8 without the BOM. Thus, these files are useless for use with Outlook - one of the most used e-mail clients.

Can we get a UTF-8 file returned without the BOM?

=== Missing data/Wrong encoding ===

* We'd like to use your service for the new version of our location list ([http://www.freewave.at/en/ Free WiFi Hotspots in Austria]) but ran into problems:
** After importing the vCard, the Mac OS X Address book showed only the phone number (not as work), the URL, zip code and city. No name and no street.
** The vCard itself is encoded in ISO-8859-1, although having “CHARSET=utf-8” instructions. The source is also encoded in UTF-8.
** Here's the HTML code, we've been using:
<source lang=html4strict>
<div class="vcard">
<h2 class="fn org"><img class="photo" src="http://static.freewave.at/logos/testa_rossa_caffe_150.gif" alt="Testa Rossa Caffèbar Logo" />Testa Rossa Caffèbar</h2>
<div class="adr work">Mahlerstraße 4 
1010 Wien 
Österreich</div>
<div>+43 699 161 616 61 
<a class="url work" href="http://www.testarossawien.at/">http://www.testarossawien.at/</a> 
<a class="email work" href="mailto:"></a></div>
<div class="geo">48.20275,16.37079</div>
</div>
</source>

Thanks! --[[User:Vividvisions|Vividvisions]] 17:25, 4 May 2010 (UTC)

I got the same type of problem with non ASCII content. Don't know which part is responsible, though. --[[User:jlgeering|Jean-Luc Geering]] 2010-05-10

+1, I was coaching the dudes at http://hagreve.com/ implementing hCalendar and they reached the roadblock of having the accented chars wrongly encoded on the .ics They resorted to using other ways of building an ics. :sadface:
Thanks. -- [[User:andr3|andr3]]

=== 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:
** '''2010-09-01 UPDATE: new HTML5 elements and <code><time datetime></code> preliminary support added to http://dev.h2vx.com/''' - try it out - give feedback!
*** Once h2vx.com is updated, reply to https://twitter.com/marcustucker/status/268200044128251904

<div class="discussion">
'''Please give feedback on the http://dev.h2vx.com/ HTML5 support here:'''
* Is there a timeout/throttling on requests to dev.h2vx? I've been getting inconsistent returns on ics and webcal requests from the same markup. Don't know what else could be the issue. When it works, it works great though!
** Any throttling we've been adding manually as necessary. What URL are you trying? [[User:Tantek|Tantek]] 18:04, 14 July 2011 (UTC)
* ...
</div>

Previously:
* Possible options
** 1. Use a proper PHP html5lib (being coded by the HTML5 community, but not available/functional yet AFAIK) - still might do this long term.
** 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)
** Oli, could you provide a URL to a live example/test case that you were using so we can test with it to try to see exactly what is going on? Thanks! [[User:Tantek|Tantek]] 17:35, 15 February 2010 (UTC)

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

* 2013-06-19 h2vx vcf service fails to parse a vcard if the vcard class is set on an HTML5 <article> element. Will return with a test page URL. [[User:Urlyman|Urlyman]] 15:12, 19 June 2013 (UTC)
** Try it with dev.h2vx.com - which supports new HTML5 elements. - [[User:Tantek|Tantek]] 23:08, 28 September 2013 (UTC)

* 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)
* ...

== feedback ==
Have feedback on H2VX like suggested improvements? 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]]
* "a short 'about' page would be worthwhile IMO, especially for adding to the homepage." - Norm on microformats-discuss.
* It would be very useful to be able to POST or GET an HTML snippet to request a conversion. I have created a Javascript button that will easily rip out the code and send it to H2VX.com: http://1daylater.com/H2VX_snippets.html useful for dynamic or password protected webpages
* [[microformats2]] support - when is it coming? from https://twitter.com/schofeld/status/347395201607806977 : <blockquote>Wondering if h2vx will be (has been?) updated for #microformats2 or if the vision is that other forthcoming tools will make it redundant.</blockquote>
* [[HTML5]] support - update from dev to live per https://twitter.com/schofeld/status/347371870242361344 : <blockquote>@h2vx Seems vcard parsing fails if class is set on an <article> element: http://microformats.org/wiki/h2vx#feedback</blockquote>

* ...

== related ==
There is at least one related H2V service that uses the same X2V XSLT files as H2VX:
* http://h2v.1daylater.com/

== old ==
Previously Technorati hosted X2V conversion services:
* [[feed.technorati.com/contacts]] - for hCards to vCards
* [[feed.technorati.com/events]] - for hCalendar to iCalendar

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

Main Page

2011-03-29T10:53:16Z

Brian: Reverted edits by Magento12 (Talk) to last version by Tantek

<entry-title>Welcome to the microformats wiki!</entry-title>
__TOC__
Please start with the [[introduction]] page and read [[how-to-play]] before making any edits.

==Introduction==
This wiki is the central resource of the microformats community. You'll find current versions of published microformat specifications, specification drafts and publishing patterns. The wiki also hosts development resources, such as brainstorming pages for new formats and issue tracking pages for all current and in-development microformats.

== Get Started==
To get started with microformats:

* First, be familiar writing your pages and applications with semantically rich, descriptive, ‘[[posh|<abbr title="Plain Old Semantic HTML">POSH</abbr>]]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.
* Learn about microformats from the [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] pages.
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.
* Want to learn more in person? Check out microformats [[events]].

==Definition==
Microformats are small patterns of HTML to represent commonly published things like [[hcard|people]], [[hcalendar|events]], [[hatom|blog posts]], [[hreview|reviews]] and [[rel-tag|tags]] in web pages.

Microformats enable the publishing of higher fidelity information on the Web; the fastest and simplest way to provide feeds and APIs for the information in your website.

* Read more explanations of [[what-are-microformats|what microformats are]], and [[what-can-you-do-with-microformats|what you can do with them]].

== How to contribute ==
Do you want to help take microformats to the next level? You can:

* [[get-started|Get started]] by adding microformats to your website, services, and products.
* [[advocacy|Advocate]] the use of microformats on other web sites, especially those you use.
* Write a [[testimonial]].
* Do something on the [[to-do|to do list]].
* Join the [[irc|IRC Channel]] and [[mail|mailing lists]] to learn and help answer questions (read the [[mailing-lists#General_guidelines|general guidelines]] before posting).
* [[Main_Page#microformats_wiki_translations|Translate this microformats wiki into other languages]] to make microformats more accessible to readers of languages around the world.
* Before proposing any new microformats, make sure your website is [[POSH]], [[get-started|uses existing microformats]], and then read the [[process]].

This wiki has a number of enhancements to assist development and contributions to microformats. Before you start editing, see the [[wiki-2|wiki introduction page]] for instructions.

== Specifications ==
The list of current, stable [[microformats|Microformats]] open standard specifications.

* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]
* [[XMDP]]
* [[xoxo|XOXO]]

''If you're tempted to try your hand at writing a microformat please read '''[[process|the process]]''' page first!''

== Drafts ==
Drafts are newer microformats, for which the specifications haven't been completed yet. Drafts are somewhat mature in the development [[process]] (see [[exploratory-discussions]] for additional efforts that are not as far along in the process). The stability of these documents cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Please watch the wiki pages for updates.

* [[adr|adr]] - for marking up address information
* [[geo|geo]] - for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude)
* [[hatom|hAtom]] - syndicating episodic content (e.g. weblog postings)
* [[haudio|hAudio]]
* [[hlisting|hListing]] - open, distributed listings
* [[hmedia|hMedia]] - A single media publishing format that relates to Images, Video and Audio.
* [[hnews|hNews]]
* [[hproduct|hProduct]]
* [[hrecipe|hRecipe]] - for cooking+baking recipes
* [[hresume|hResume]] - for publishing resumes and CVs
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page
* [[rel-enclosure]] - for indicating attachments (e.g. files) to download and cache
* [[rel-home]] - indicate a hyperlink to the homepage of the site
* [[rel-payment]] - indicate a payment mechanism
* [[robots-exclusion|robots exclusion]]

* [[xfolk|xFolk]]

== Design Patterns ==
{{design_patterns}} 

== Exploratory Discussions ==
See: [[exploratory-discussions]] for details of research and analysis of real-world [[examples]], existing formats, and brainstorming of possible new microformats, per the microformats [[process]].

== Examples ==
* [[examples-in-the-wild]]
* [[implementations]]
* [[zen-garden]]

== Resources ==
See [[resources]].

== User centric development ==
*[[user-interface]]
*[[data-portability]]
*[[social-network-portability]]

== Shared work areas ==
* [[to-do]]
* [[templates]]
* [http://microformats.org/wiki/delete pages for deletion] 
* [[Special:Specialpages|"Special" wiki pages]]
* [[year-in-review]]

== Tools, test cases, additional research ==
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting [[tools|tools and services]] that need to process more than one microformat. That section is intended for editors, [[parsers]], [[validators]], test cases, and other information relevant across multiple microformats.

== Microformats wiki translations ==
You may read and edit microformats articles in many other languages:

* languages with over 100 articles
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}
* languages with over 10 articles
** [[Main_Page-pt-br|Português (Brazilian Portuguese)]]
** [[Main_Page-ja|日本語 (Japanese)]]
** [[Main_Page-ru|Русский (Russian)]]
* languages with over 2 articles
** [[Main_Page-cs|Česky (Czech)]] {{NewMarker}}
** [[Main_Page-de|Deutsch (German)]]
** [[Main_Page-es|Español (Spanish)]]
** [[Main_Page-gl|Galego (Galician)]] {{NewMarker}}
** [[Main_Page-pl|Polski (Polish)]]
** [[Main_Page-ro|Română (Romanian)]] {{NewMarker}}
** [[Main_Page-zh|汉语 (Chinese)]]
** [[Main_Page-id|Indonesia (Bahasa Indonesia)]] {{NewMarker}}
* languages just started
** [[Main_Page-fa|پارسی (Farsi)]] {{NewMarker}}
** [[Main_Page-ar|العربية (Arabic)]]
** [[Main_Page-th|ภาษาไทย (Thai)]]
** [[Main_Page-it|Italiano (Italian)]] {{NewMarker}}
** [[Main_Page-ko|한국어 (Korean)]] {{NewMarker}}
* elsewhere
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.

See also [[other-languages]], and [[how-to-start-new-translation|how-to-start-a-new-translation]].

citation-examples

2010-09-11T14:36:30Z

Brian: replaced dead link

<h1> Citation Examples </h1>

The following examples are real world examples of citations found on the web. Please add to this list. The idea is that we get a solid sample of examples and see what commonalities there are amonst them and try to build this microformat so that it can meet 80% of typical uses.

'''To add examples:''' please first add a copy of the HTML source for your example at the [[citation-examples-markup]] page, then add a description of the example to this page, with a link to the corresponding section on [[citation-examples-markup]]. Thanks!

__TOC__

== Contributors ==
* ...
* [http://suda.co.uk/ Brian Suda]
* Tantek Çelik
* [[User:AndyMabbett|Andy Mabbett]]
* [http://michael-mccracken.net/wp/ Michael McCracken]
* Tim White
* [http://inkdroid.org Ed Summers]

== Citation Mark Up in the Wild ==
Mark up examples from reference publisher's websites (online catalogs), including ABC-CLIO, Greenwood Press, Marshall Cavendish, Oxford University Press (USA) and Thomson Gale. Examples are broken down and organized by element.

(For a cleaner version, see [http://www.tjameswhite.com/citation-examples.htm]) -- ''is this link now out of date?''--[[User:Mike|Mike]] 18:19, 30 Aug 2006 (PDT)

=== ABC-CLIO Product detail page ===
[http://www.abc-clio.com/products/overview.aspx?productid=109327 ABC-CLIO example]
[[citation-examples-markup#ABC-CLIO_Product_detail_page.C2.A0.28http:.2F.2Fwww.abc-clio.com.2Fproducts.2Foverview.aspx.3Fproductid.3D109327.29|ABC-CLIO Original Markup]]

* title
* subtitle
* author
* image
* publication date
* pages
* volumes
* specifications (book dimentions 8.5x11, weight, etc)
* Format - (Hardback, softback)
* Price
* ISBN

=== ACM Digital Library Search Result Examples ===

The [http://www.acm.org/dl/ ACM Digital Library] is a heavily used computer science literature database.

The [[citation-examples-markup#ACM_Digital_Library_Search_Result_Examples|ACM Original Markup]] contained two examples, a journal article and a conference proceedings article.

''Journal article:''

* title
* authors
* Pages
* format (PDF)
* Additional Information
* abstract
* index terms
* journal
* issue
* volume
* pubdate
* DOI

''Conference Proceedings:''

* title
* authors
* author institutions
* source (conference + proceedings name)
* page
* year
* isbn
* publisher name & address
* DOI
* abstract
* subject category labels
* keywords

=== Amazon.com citation info ===

This is from a detail page on Amazon.com for a book.

[[citation-examples-markup#Amazon.com_citation_info|Amazon's Original Markup]]

* title
* author
* series title
* page

=== CiteSeer database search results ===

The [http://citeseer.ist.psu.edu CiteSeer] database has been another heavily used Computer Science online resource, and it has minimal markup:
#[[citation-examples-markup#CiteSeer_database_search_results|CiteSeer's Original Markup]]
#[[citation-examples#CiteSeer|CiteSeer's Original Example 2]]

* author
* title
* journal
* pages
* publication date
* URL
* Accessed On

=== CiteULike.org citation listing ===

[http://www.citeulike.org/ CiteULike]

[[citation-examples-markup#CiteULike.org_citation_listing|CiteULike's Original Markup]]

* title
* author
* subjects
* image
* Volume
* Number
* publication date
* page

Links to services with the following IDs embedded in the link
* Z3988
* DOI
* Pubmed
* Hubmed

=== CiteProc XHTML Output ===
[[citation-examples-markup#CiteProc_XHTML_Output|CiteProc Original Markup]]

The XHTML output for CiteProc[http://xbiblio.sourceforge.net/citeproc/] wasn't designed per se as a microformat, but is probably not a bad place to start. It is designed to handle a wide range of content. Here is the APA output:

* refID (HTML @ID)
* creator
* role (to indicate editors and translators)
* date
* title
* volume
* issue
* page
* issue
* container (a book serves as container for a chapter)
* type (book, newspaper, proceedings)
* edition
* publisher
* place
* location (for urls and physical locations)
* access date (for online items)

=== Google Cache ===
[http://microformats.org/wiki?title=citation-examples-markup&action=submit#Google Original Markup]
* url
* retrieved date

=== Greenwood Press featured book ===
[http://www.greenwood.com/ greenwood press home page]
[http://microformats.org/wiki/citation-examples-markup#Greenwood_Press_home_page.C2.A0.28http:.2F.2Fwww.greenwood.com.2F.29_featured_book Original Markup]
* title
* subtitle
* author
* ISBN
* Price
* Description

=== Greenwood Press product detail page ===
[http://www.greenwood.com/catalog/GR2847.aspx Product detail page]
[http://microformats.org/wiki/citation-examples-markup#Greenwood_Press_Product_detail_page.C2.A0.28http:.2F.2Fwww.greenwood.com.2Fcatalog.2FGR2847.aspx.29 Original Markup]

* Title
* subtitle
* authors
* AuthorsNote
* BookCode (internal code system)
* ISBN
* Page
* Publisher
* Publication Date
* Price
* Availability
* MediaType
* categories
* LC Card Number
* LCC Class
* Dewey Class

=== IEEE IEEExplore Search Results Markup ===
[http://microformats.org/wiki/citation-examples-markup#IEEE_IEEExplore_Search_Results_Markup Original Markup]

* title
* authors
* journal
* issue
* volume
* issue
* pubdate
* page
* Digital Object Identifier (DOI)
* summary

=== Marshall Cavendish product page===
[http://www.marshallcavendish.com/marshallcavendish/academic/redirector.xml?url=/marshallcavendish/academic/catalogue/books/regionalism_n_regional_security/9812102108.xml product page]
[http://microformats.org/wiki/citation-examples-markup#Marshall_Cavendish_product_page.C2.A0.28http:.2F.2Fwww.marshallcavendish.com.2Fmarshallcavendish.2Facademic.2Fredirector.xml.3Furl.3D.2Fmarshallcavendish.2Facademic.2Fcatalogue.2Fbooks.2Fregionalism_n_regional_security.2F9812102108.xml.29 Original Markup]

* ISBN
* Series
* Title
* publisher
* Specifications (dimentions/weight)
* Authors
* Target Audience
* Price
* description

=== Ning ===
[http://microformats.org/wiki?title=citation-examples-markup&action=submit#Ning.com Original Example]
* title
* publications date
* retrieved on

=== Oxford University Press (USA) home page ===
[http://www.us.oup.com/us/?view=usa homepage]
[http://microformats.org/wiki/citation-examples-markup#Oxford_University_Press_.28USA.29_homepage.C2.A0.28http:.2F.2Fwww.us.oup.com.2Fus.2F.3Fview.3Dusa.29 Original Markup]

* title
* subTitle
* edition
* byline
* ISBN
* format - hardback
* publication Date
* price
* description
* related

=== Oxford University Press (USA) product detail page ===
[http://www.us.oup.com/us/catalog/general/subject/HistoryAmerican/ColonialRevolutionary/?view=usa&ci=0195162471#Product_Details Product page]
[http://microformats.org/wiki/citation-examples-markup#Oxford_University_Press_.28USA.29_Product_page.C2.A0.28http:.2F.2Fwww.us.oup.com.2Fus.2Fcatalog.2Fgeneral.2Fsubject.2FHistoryAmerican.2FColonialRevolutionary.2F.3Fview.3Dusa.26ci.3D0195162471.23Product_Details.29 Original Markup]

* title
* subTitle
* edition
* byline
* image
* isbnNumber
* format - hardback
* pages
* publication Date
* availability
* price

=== Thomson Gale product detail page ===
[http://microformats.org/wiki/citation-examples-markup#Thomson_Gale_product_detail_page Original Markup]

* title
* excerp
* Volume
* Publisher
* description
* Published date
* ISBN
* Product number (internal code system)
* Pages
* Shipping Weight
* price

=== RFC vCard Example ===
[http://microformats.org/wiki/citation-examples-markup#RFC_vCard_Example Original Markup]

* refID (HTML @ID)
* title
* publication
* title
* Journal
* Volume
* Issue
* page
* pubdate
* RFC ID

=== University of Virginia ===
[http://microformats.org/wiki?title=citation-examples-markup&action=submit#University_of_Virginia Original Markup]
* title
* publication date
* retrived on
* location
* organization

=== W3C XHTML Spec Example ===
[http://microformats.org/wiki/citation-examples-markup#W3C_XHTML_Spec_Example Original Markup]

* refID (HTML @ID)
* URL
* title
* subtitle
* part (1 of X)
* journal
* authors
* pubdate
* language
* ISO/IEC ID
* RFC ID

[http://www.w3.org/TR/xhtml1/#refs XHTML1.0 Spec references]

=== PubMed Medical Journal Example ===
[http://microformats.org/wiki/citation-examples-markup#PubMed_Medical_Journal_Example Original Markup]

* abstract
* title
* publisher
* journal
* date of publication
* volume
* issue
* pages
* language
* Review (BOOLEAN YES/NO)
* PubMedID

=== BibDesk Default Template ===
[[citation-examples-markup#BibDesk_default_HTML_export_example|Original Markup]]

This is a pretty simplistic template for a very general app, but it seems to be OK for most BD users.

* Title
* Author
* Journal
* Volume
* Pages
* Date
* Url
* Abstract

=== Wikipedia ===
[http://wikipedia.org Wikipedia] makes extensive use of bibliographic citations, in particular to point readers to further information sources. There are differing formats depending on Wikipedia's language.

Note that Wikipedia values are often links to other pages on Wikipedia (used elsewhere, those URLs might be more canonical, such as to an author or publisher's website).

==== English Wikipedia ====
The kinds of citations used on the site run the full gamut. Here are breakdowns of four categories previously mentioned:

===== Original Markup =====
[http://microformats.org/wiki?title=citation-examples-markup&action=submit#Wikipedia Original Markup]
* id
* title
* url
* Retrieved/Accessed On
* Publication Date
* Journal

===== Book =====
[http://en.wikipedia.org/wiki/Richard_feynman#_note-8 Example]
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_Book Example Markup]

* title
* author
* publisher
* year
* ISBN
* url (indirectly via special wikipedia ISBN page)

===== Book Infobox =====

The [http://en.wikipedia.org/wiki/Template:Infobox_Book Book Infobox template] from wikipedia shows a separate schema that is being used for many book pages on wikipedia to mark up a summary box about the book.

See also [http://en.wikipedia.org/wiki/Category:Book_templates Other Wikipedia book templates] & [http://en.wikipedia.org/wiki/Category:Citation_templates Wikipedia citation templates].

* name
* title_orig
* translator
* image
* image_caption
* author
* illustrator
* cover_artist
* country
* language
* series
* subject
* genre
* publisher
* release_date
* english_release_date
* media_type
* pages
* isbn
* preceded_by
* followed_by

===== Journal Articles =====
See also:[http://en.wikipedia.org/wiki/Template:Infobox_Journal Wikipedia infobox for journals]

[http://en.wikipedia.org/wiki/DNA#Citations Example]
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_Journal_Article Example Markup]

* author (truncated list)
* year
* title
* journal title
* journal number
* page range
* [http://doi.org DOI]

===== Court cases =====
[http://en.wikipedia.org/wiki/List_of_leading_legal_cases_in_copyright_law Example]
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_Court_Case Example Markup]

* title
* case number
** ''note that legal standards for referring to cases include some inscrutable abbreviations that are probably more detailed than just "case number"''
* court name
* year
* description/abstract

===== U.S. Law =====
[http://en.wikipedia.org/wiki/Foreign_Intelligence_Surveillance_Act#endnote_FISA Example]
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_US_Law Example Markup]

* title (title number, for example "50" in "50 U.S.C. chapter 36."
* chapter title (name, for example "Foreign Intelligence Surveillance" )
* chapter number
* section, paragraph, subparagraph numbers (optionally)

===== Conference presentations =====
[http://en.wikipedia.org/wiki/Paul_R._Pillar#Conference_presentation_by_Pillar Example]
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_Conference_Presentation Example Markup]

* title
* location
* date
* author (implied - the page is about this person)

===== Historical Sources =====
[http://en.wikipedia.org/wiki/American_Civil_War#Primary_sources Example]
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_Primary_Historical_Source Example Markup]

* source / location
* title
* publisher
* year
* description
* url

===== U.S. Patent =====
[http://en.wikipedia.org/wiki/List_of_software_patents Example]
[http://microformats.org/wiki/citation-examples-markup#Wikipedia_U.S._Patent Example Markup]

* number

==== German Wikipedia ====
* [http://de.wikipedia.org/wiki/Wikipedia:Literatur citing styles]

=== EPrints.org ===

[http://eprints.ecs.soton.ac.uk/12070/ example]
[http://microformats.org/wiki/citation-examples-markup#EPrints.org_generated_output example markup]

Based on [http://dublincore.org/documents/dcq-html/ Expressing Dublin Core in HTML/XHTML meta and link elements] and [http://www.ietf.org/rfc/rfc2731.txt rfc2731], Eprints.org uses the following Dublin Core terms in meta tags in the HTML HEAD of each paper's page:

* title
* creator (author)
* description (abstract)
* date
* type
* identifier (a url)
* format
** a strange syntax for the meta content:"pdf http://eprints.ecs.soton.ac.uk/12070/01/Alani-final.pdf"" for the format term...
* fulltext
** this is in a rel-alternate link element. The class is 'fulltext', and the href is the same link as in format, only a valid URL this time.

In the body of the page, they use the following classes, now no longer DC terms:
* title
* authors (a flat list with abbreviated names)
* year
* conference
* conference location

=== Wolfram Mathworld ===

[http://mathworld.wolfram.com/Quasi-MonteCarloMethod.html example]
[http://microformats.org/wiki/citation-examples-markup#Wolfram_Mathworld example markup]

A book. First citation from the page on "Quasi-Monte Carlo Method". Has very little markup.

* authors
* title
* publisher (name and location)
* date (just year)

===LibraryThing===
*[http://www.librarything.com/] (on-line book cataloguing and reviews
**e.g. [http://www.librarything.com/catalog.php?view=trealawboy]

=== Self-Citation Example ===
[http://cbio.mskcc.org/~hoffmann/lifecycles/olv/index.html One example] of an article that includes a statement "please cite as" (a self-description):

* title
* author
* periodical (journal) title
* volume
* issue
* pages
* year

=== Citation of an Online Resource ===
[http://microformats.org/wiki/citation-examples-markup#Citation_of_an_Online_Resource example markup]

At University of Michigan's [http://www.crlt.umich.edu/publinks/facment_biblio.html Center for Research on Learning and Teaching] you see citations like this:

Chief Academic Officers of the Big 12 Universities (2000). Big 12 Faculty Fellowship Program. Retrieved December 20, 2000 from the World Wide Wed: http://www.k-state.edu/provost/academic/big12/big12guide.htm.

* title
* publication year
* department/author
* retrieval date
* URL

[http://www.firstmonday.org/issues/issue12_2/tulloch/index.html "Many, Many Maps," ''First Monday''] contains citations to online resources like this:

E.S. Raymond, 2000. “The Cathedral and the Bazaar,” version 3.0, at http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar, accessed 18 October 2006.

* author
* publication year
* web page title
* URL
* accessed date

[http://chnm.gmu.edu/resources/essays/d/44 "The Role of Technology in World History Teaching" by T. Mills Kelly] uses the following citation format for online resources:

''Hitler Historical Museum'', http://www.hitler.org/. Accessed March 21, 2006.

* title
* URL
* accessed date

=== OCLC WorldCat Online ===

==== Book ====
[http://www.worldcat.org/oclc/41238513 example] [http://microformats.org/wiki/citation-examples-markup#Book example-makrup]

* title
* type (book)
* publisher name
* publisher location
* copyright date
* isbn
* oclc number
* subjects
* author
* z39.88 (COinS)

==== Journal ====
[http://www.worldcat.org/oclc/4538259 example]
[http://microformats.org/wiki/citation-examples-markup#Journal example-makrup]

* title
* type (journal)
* publisher
* issn
* oclc number
* subjects
* z39.88 (COinS)

====West Midland Bird Club====
Uses OpenCOinS
* [http://www.westmidlandbirdclub.com/biblio/warwks.htm Bibliography page]
* [http://www.westmidlandbirdclub.com/archive/reports1970s.htm Annual Reports]
* [http://www.westmidlandbirdclub.com/biblio/birdnotes/23-5-172.htm 'Bird Notes' article reproduction]
* [http://www.westmidlandbirdclub.com/biblio/bb/73-478.htm 'British Birds' article reproduction]
* [http://www.westmidlandbirdclub.com/biblio/bb/40-184.htm 'British Birds' article reproduction with additional citation]
*[http://www.westmidlandbirdclub.com/biblio/bb/index.htm List of 'British Birds' articles]

Features include:
*title
*author
*date
*price (historic, at time of publication)
*format
*publisher
*number of pages
*ISBN/ ISSN
*product dimensions
*page numbers of article
*image(s)

====Amazon====
Product listings, e.g.
[http://www.amazon.com/gp/product/1590596145/ref=pd_qpt_gw_1/026-5782158-8338825]
*title
*author
*price
*format
*publisher
*number of pages
*language
*ISBN
*product dimensions
*shipping weighta
*average customer review
*image
*Amazon.com Sales Rank

====ABE====
Product listings, e.g. [http://www.abebooks.com/servlet/BookDetailsPL?bi=637112345&searchurl=sts%3Dt%26an%3Dmabbett%26y%3D0%26x%3D0]
*title
*author
*ISBN
*publisher
*publication date
*country
*edition
*condition
*whether signed
*format/binding
*number of pages
*bookseller
*inventory number
*price
*shipping costs
*quantity

===Open URL===

* See [[OpenURL_1.0_%28Z39.88%29|OpenURL]]

===Upcoming===
====Open Library====
*[http://www.openlibrary.org/ Open Library]
**<blockquote>There are data fields for every possible bit of information that could exist about each published work.</blockquote> - [http://news.bbc.co.uk/1/hi/magazine/6924022.stm BBC news story 2007-07-31]

== Implied schema ==

=== List of all properties ===
This are a summation of all the properties in the examples, I have tried to logically group them together.

* title
* subtitle
* author
* editor
* translator
* image
* date (issued, copyrighted, accessed)
* language
* description/Summary/abstract
* excerpt
* index terms
* categories (keywords, tags, labels, etc.)

RELATIONS
* container (publication; periodicals, books, etc.)
* collection (series and so forth)
* event (conference, etc.)
* original (for republished material)

LOCATION INFORMATION
* pages
* volume
* series title
* Series
* edition
* issue
* publication
* journal
* part (1 of X)

PHYSICAL ATTRIBUTES
* Specifications (dimentions/weight)
* Format/type (book, newspaper, proceedings)

IDENTIFIERS
* ISBN
* LC Card Number
* LCC Class
* Dewey Class
* URL
* RFC ID
* ISO/IEC ID
* DOI
* PubMedID

PUBLISHER
* publisher

These are sort of left overs, the are not really about citations, but more about commerce or other things. If they are important we can move them to the above list.
* refID (HTML @ID)
* Reviewed (BOOLEAN YES/NO)
* Availability
* Price
* Shipping Weight
* related
* Product number (internal system code)
* BookCode (internal system code)
* AuthorsNote
* Additional Information
* Target Audience

=== Analysis of Examples ===
With exception of just a few properties, all of the above appeared in atleast two different examples. The following properties were very common in most the example formats:
* title
* subtitle
* author
* publication date
* description
* pages
* ISBN
* publisher

== Styles ==
This does NOT define a format, but instead shows how the format should be displayed. This is something out of the direct scope of this project. CSS styles will handle the look-and-feel of the text, and the author can put it in any order they choose. These links are mentioned for two reasons, one is informative, the other is so we know at least meet the minimum properties that are used in the styles.

* [http://www.liu.edu/cwis/cwp/library/workshop/citmla.htm MLA Style]
* [http://www.bu.edu/library/guides/citation.html Chicago, MLA, and APA styles]
* [http://www.english.uiuc.edu/cws/wworkshop/writer_resources/citation_styles/citation_styles.htm Writer's Workshop citation style page] (detailed citation style info)
* [http://www.legalbluebook.com/ Blue Book] for legal citations
* [http://www.guidetoonlineschools.com/tips-and-tools/mla-apa-chicago-cse The Ultimate Style Guide Resources for MLA, APA, Chicago, and CSE]

==Other examples==
*[[citations_in_the_wild]]
*[[blog-quote-examples]]

==See also==
{{citation-related-pages}}

value-class-date-time-tests

2009-10-07T23:11:54Z

Brian: catchin' up!

<entry-title>value class pattern date and time tests</entry-title>
This page provides links to individual test case pages for handling date and time values published using the [[value-class-pattern]].

;short URL
:http://tr.im/vcpdt

== tests ==
Tests grouped by microformat:

=== hCalendar ===
* [[value-dt-test-YYYY-MM-DD--HH-MM]] - separate YYYY-MM-DD and HH:MM
* [[value-dt-test-abbr-YYYY-MM-DD--HH-MM]] - separate YYYY-MM-DD in abbr and HH:MM
* [[value-dt-test-abbr-YYYY-MM-DD-abbr-HH-MM]] - separate YYYY-MM-DD in abbr and HH:MM in abbr
* [[value-dt-test-YYYY-MM-DD--HHpm]] - separate YYYY-MM-DD and whole hour HH "pm" time
* [[value-dt-test-YYYY-MM-DD--Hpm-EEpm]] - separate YYYY-MM-DD, single digit H "pm" start time, time only EE "pm" hours dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--abbr-HH-MMpm]] - separate YYYY-MM-DD, HH:MM "pm" start and end times in abbr, time only dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--12am-12pm]] - separate YYYY-MM-DD, 12 "am" start time, time only 12 "pm" dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--H-MMam-Epm]] - separate YYYY-MM-DD, single-digit-hour H:MM "am" start time, time only single-digit E "pm" hours dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--0Ham-EEam]] - separate YYYY-MM-DD, single-digit leading zero H "a.m." start time, time only double-digit EE "a.m." hours dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--H-MM-SSpm-EE-NN-UUpm]] - separate YYYY-MM-DD, single-digit hour H:MM:SS " p.m." start time, time only double-digit hours EE:NN:UU " p.m." dtend (imply date from dtstart)
* [[value-dt-test-YYYY-DDD--HH-MM-SS]] - separate YYYY-DDD and HH:MM:SS
* [[value-dt-test-YYYY-MM-DD--HH-MMZ-EE-NN-UUZ]] - separate YYYY-MM-DD, HH:MM explicit Z start time, and EE:NN:UUZ end time (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--HH-MM-XX-YY--EE-NN-UU--XXYY]] - separate YYYY-MM-DD, HH:MM with -XX:YY timezone, end time EE:NN:UU with separate -XXYY timezone (imply date from dtstart).
* [[value-dt-test-YYYY-MM-DD--HH-MM-XX--EE-NN-UU--Y]] - separate YYYY-MM-DD, HH:MM with +XX timezone, end time EE:NN:UU with separate single-digit-hour +Y timezone (imply date from dtstart).
* [[value-dt-test-YYYY-MM-DD--HH-MM-SS-XXYY--EE-NN--Z]] - separate YYYY-MM-DD, HH:MM:SS with +XXYY timezone, end time EE:NN with separate Z timezone (imply date from dtstart).

==== error tests ====
Tests are necessary to make sure implementations aren't "over" implementing some aspects, and properly handling errors in markup, e.g. using the "title" attribute when they shouldn't be.
* [[value-dt-test-e-title-YYYY-MM-DD--HH-MM]] - separate YYYY-MM-DD in span (with errant value in title) and HH:MM in span (with errant value in title).
* ...

=== hAtom ===
* ...

== results ==
This table documents implementations that support at least some value class pattern features. As implementations pass at least one of the tests above, they should be added to this table.
{| style="border:1px solid"
! test !! [[X2V]] 0.9.7 || [[Operator]] 0.9.5b
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-abbr-YYYY-MM-DD--HH-MM]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-abbr-YYYY-MM-DD-abbr-HH-MM]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--HHpm]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--Hpm-EEpm]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--abbr-HH-MMpm]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--12am-12pm]] || {{testpass}} || {{testfail}}
|-
| [[value-dt-test-YYYY-MM-DD--H-MMam-Epm]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--0Ham-EEam]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--H-MM-SSpm-EE-NN-UUpm]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-DDD--HH-MM-SS]] || {{testfail}} || {{testfail}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MMZ-EE-NN-UUZ]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM-XX-YY--EE-NN-UU--XXYY]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM-XX--EE-NN-UU--Y]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM-SS-XXYY--EE-NN--Z]] || {{testpass}} || {{testpass}}
|-
| [[value-dt-test-e-title-YYYY-MM-DD--HH-MM]] || {{testpass}} || {{testpass}}
|}

== old tests ==
The handling of date and time values in the value class pattern was originally [[value-excerption-pattern-brainstorming#date_and_time_separation|brainstormed on the value-excerption-pattern-brainstorming]] page and the following page of tests was used to make sure pattern both worked for publishers and was reasonably parsable:
* [[value-excerption-dt-separation-test]]

== see also ==
* [[value-class-pattern]]
* [[value-class-pattern-tests]]

value-class-date-time-tests

2009-10-04T13:16:34Z

Brian: updated results

<entry-title>value class pattern date and time tests</entry-title>
This page provides links to individual test case pages for handling date and time values published using the [[value-class-pattern]].

;short URL
:http://tr.im/vcpdt

== tests ==
Tests grouped by microformat:

=== hCalendar ===
* [[value-dt-test-YYYY-MM-DD--HH-MM]] - separate YYYY-MM-DD and HH:MM
* [[value-dt-test-abbr-YYYY-MM-DD--HH-MM]] - separate YYYY-MM-DD in abbr and HH:MM
* [[value-dt-test-abbr-YYYY-MM-DD-abbr-HH-MM]] - separate YYYY-MM-DD in abbr and HH:MM in abbr
* [[value-dt-test-YYYY-MM-DD--HHpm]] - separate YYYY-MM-DD and whole hour HH "pm" time
* [[value-dt-test-YYYY-MM-DD--Hpm-EEpm]] - separate YYYY-MM-DD, single digit H "pm" start time, time only EE "pm" hours dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--abbr-HH-MMpm]] - separate YYYY-MM-DD, HH:MM "pm" start and end times in abbr, time only dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--12am-12pm]] - separate YYYY-MM-DD, 12 "am" start time, time only 12 "pm" dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--H-MMam-Epm]] - separate YYYY-MM-DD, single-digit-hour H:MM "am" start time, time only single-digit E "pm" hours dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--0Ham-EEam]] - separate YYYY-MM-DD, single-digit leading zero H "a.m." start time, time only double-digit EE "a.m." hours dtend (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--H-MM-SSpm-EE-NN-UUpm]] - separate YYYY-MM-DD, single-digit hour H:MM:SS " p.m." start time, time only double-digit hours EE:NN:UU " p.m." dtend (imply date from dtstart)
* [[value-dt-test-YYYY-DDD--HH-MM-SS]] - separate YYYY-DDD and HH:MM:SS
* [[value-dt-test-YYYY-MM-DD--HH-MMZ-EE-NN-UUZ]] - separate YYYY-MM-DD, HH:MM explicit Z start time, and EE:NN:UUZ end time (imply date from dtstart)
* [[value-dt-test-YYYY-MM-DD--HH-MM-XX-YY--EE-NN-UU--XXYY]] - separate YYYY-MM-DD, HH:MM with -XX:YY timezone, end time EE:NN:UU with separate -XXYY timezone (imply date from dtstart).
* [[value-dt-test-YYYY-MM-DD--HH-MM-XX--EE-NN-UU--Y]] - separate YYYY-MM-DD, HH:MM with +XX timezone, end time EE:NN:UU with separate single-digit-hour +Y timezone (imply date from dtstart).
* [[value-dt-test-YYYY-MM-DD--HH-MM-SS-XXYY--EE-NN--Z]] - separate YYYY-MM-DD, HH:MM:SS with +XXYY timezone, end time EE:NN with separate Z timezone (imply date from dtstart).

==== error tests ====
Tests are necessary to make sure implementations aren't "over" implementing some aspects, and properly handling errors in markup, e.g. using the "title" attribute when they shouldn't be.
* [[value-dt-test-e-title-YYYY-MM-DD--HH-MM]] - separate YYYY-MM-DD in span (with errant value in title) and HH:MM in span (with errant value in title).
* ...

=== hAtom ===
* ...

== results ==
This table documents implementations that support at least some value class pattern features. As implementations pass at least one of the tests above, they should be added to this table.
{| style="border:1px solid"
! test !! [[X2V]] 0.9.6
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM]] || <div style="text-align:center;background:#cfc ">pass</div>
|-
| [[value-dt-test-abbr-YYYY-MM-DD--HH-MM]] || <div style="text-align:center;background:#cfc">pass</div>
|-
| [[value-dt-test-abbr-YYYY-MM-DD-abbr-HH-MM]] || <div style="text-align:center;background:#cfc">pass</div>
|-
| [[value-dt-test-YYYY-MM-DD--HHpm]] || <div style="text-align:center;background:#cfc">pass</div>
|-
| [[value-dt-test-YYYY-MM-DD--Hpm-EEpm]] || <div style="text-align:center;background:#cfc">pass</div>
|-
| [[value-dt-test-YYYY-MM-DD--abbr-HH-MMpm]] || <div style="text-align:center;background:#cfc">pass</div>
|-
| [[value-dt-test-YYYY-MM-DD--12am-12pm]] || <div style="text-align:center;background:#cfc">pass</div>
|-
| [[value-dt-test-YYYY-MM-DD--H-MMam-Epm]] || <div style="text-align:center;background:#cfc">pass</div>
|-
| [[value-dt-test-YYYY-MM-DD--0Ham-EEam]] || <div style="text-align:center;background:#cfc">pass</div>
|-
| [[value-dt-test-YYYY-MM-DD--H-MM-SSpm-EE-NN-UUpm]] || <div style="text-align:center;background:#cfc">pass</div>
|-
| [[value-dt-test-YYYY-DDD--HH-MM-SS]] || <div style="text-align:center;background:#cfc">pass</div>
|-
| [[value-dt-test-YYYY-MM-DD--HH-MMZ-EE-NN-UUZ]] || <div style="text-align:center;background:#fcc">fail</div>
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM-XX-YY--EE-NN-UU--XXYY]] || <div style="text-align:center;background:#fcc">fail</div>
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM-XX--EE-NN-UU--Y]] || <div style="text-align:center;background:#fcc">fail</div>
|-
| [[value-dt-test-YYYY-MM-DD--HH-MM-SS-XXYY--EE-NN--Z]] || <div style="text-align:center;background:#fcc">fail</div>
|-
| [[value-dt-test-e-title-YYYY-MM-DD--HH-MM]] || <div style="text-align:center;background:#cfc">pass</div>
|}

== old tests ==
The handling of date and time values in the value class pattern was originally [[value-excerption-pattern-brainstorming#date_and_time_separation|brainstormed on the value-excerption-pattern-brainstorming]] page and the following page of tests was used to make sure pattern both worked for publishers and was reasonably parsable:
* [[value-excerption-dt-separation-test]]

== see also ==
* [[value-class-pattern]]
* [[value-class-pattern-tests]]

events/2009-07-25-dev-camp

2009-07-25T23:12:30Z

Brian: request for translations of the microformats cheatsheet

<entry-title>microformatsDevCamp</entry-title>
http://farm3.static.flickr.com/2460/3726302070_7b834b9443_o.jpg

<div class="event-page vevent">
;When
:2009-07-25 from 12:00 to 2009-07-26 at 17:00
;Where
:Automattic, Pier 38, The Embarcadero between Brannan and Townsend, San Francisco, CA, 94107. [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&view=map&q=%2BAutomattic,+The+Embarcadero,+San+Francisco,+CA+94107&sll=37.752736,-122.402826&sspn=0.13844,0.217667&gl=us&ie=UTF8&t=h&layer=c&cbll=37.782877,-122.388062&panoid=kB1DhzPP5DYl5pgHBRxdPg&cbp=12,123.84,,0,2.44&ll=37.783053,-122.388044&spn=0,359.996599&z=18 View location at latitude:37.782769, longitude:-122.387837]
:'''MUNI''': [http://playfoursquare.com/venue/72202 Brannan] (N,T)
:'''BART''': Embarcadero station, then [http://www.nextmuni.com/predictor/prediction.shtml?a=sf-muni&r=N&d=N__IB3&s=6992&ts=4506 take MUNI N-Judah inbound] or T-Third inbound to Brannan stop.
:'''Caltrain''': 4th & King st., then [http://www.nextmuni.com/predictor/prediction.shtml?a=sf-muni&r=N&d=N__OB2&s=5240&ts=7145 take MUNI N-Judah outbound] or T-Third outbound to Brannan stop.
;What
:microformatsDevCamp! The first ever microformatsDevCamp, for authors, designers, publishers, developers, engineers building pages, sites, and tools with microformats.
;How much
:$20 suggested donation (gets you a t-shirt while supplies last). No one turned away for lack of funds.
;URLs
:http://microformats.org/wiki/events/2009-07-25-dev-camp
:http://upcoming.yahoo.com/event/2888376/
:http://www.facebook.com/event.php?eid=102571118403
;short URL
:http://tr.im/ufdevcamp

'''[http://suda.co.uk/projects/microformats/hcalendar/get-cal.php?uri=http://microformats.org/wiki/events/2009-07-25-dev-camp Add this event to your calendar]''' http://www.boogdesign.com/images/buttons/microformat_hcalendar.png

== Sponsors ==
microformatsDevCamp is made possible thanks to the generosity of our corporate and individual sponsors!

* Venue
**[http://automattic.com Automattic]
* Meals
** [http://spinn3r.com Spinn3r]
** [http://commerce.net CommerceNet]
** [http://visitmix.com/Lab/Oomph Microsoft MIX Online]
** [http://mBLAST.com/ mBLAST]
** [http://steve.ganz.name/ Steve Ganz]
** [http://www.carlaborsoi.com/ Carla Borsoi]
* Promotion
** [http://objectadjective.com Object Adjective]
** [http://cindyli.com Cindy Li]

=== Sponsorships ===
Help sponsor microformatsDevCamp:

* Saturday 25th
** Lunch - sponsored by [http://spinn3r.com Spinn3r]
** Dinner - sponsored by [http://commerce.net CommerceNet]
** Evening Social & Snacks - sponsored by [http://mBLAST.com/ mBLAST]
*** Beer - sponsored by [http://steve.ganz.name/ Steve Ganz]
* Sunday 26th
** Breakfast - sponsored by [http://www.carlaborsoi.com/ Carla Borsoi]
** Lunch - sponsored by [http://visitmix.com/Lab/Oomph Microsoft MIX Online]
* More Ideas...
** Stickers - sponsored by [http://objectadjective.com Object Adjective]
** Buttons - sponsored by [http://cindyli.com Cindy Li]
** Coffee
** Snacks
** ______?

For meals, we're planning on something simple like bagels+coffee for breakfast (note: Tantek will purchase supplies for Sunday morning); or pizza or <del>indian delivery</del> ([http://www.mydeedees.com/ Deedees Indian Food!]). We'll arrange for sponsors to pay vendors directly...

== attendees ==
microformatsDevCamp, like any BarCamp, needs you - Sign up to volunteer, attend, design, code, and build with microformats!

=== volunteers ===
Like all [http://barcamp.org BarCamps], this event is what it is because of what everyone puts into it. Volunteer to help setup, check people in, get them setup with a name badge, clean up, and help people in general have a good time and get things done.
* Cindy Li - designer, helping with microformatsDevCamp logo design. done!
** full resolution logo: <nowiki>http://farm3.static.flickr.com/2460/3726302070_7b834b9443_o.jpg</nowiki>
** on Flickr: http://www.flickr.com/photos/cindyli/3726302070/
** designed and ordered buttons for event.Done!

* [[User:BeauLebens|Beau Lebens]] - developer, Automattic, [[http://dentedreality.com.au/ Dented Reality]]. I know my way around the venue, so can help sort out power strips, projectors etc
* ...

=== participants ===

Please register with this [http://spreadsheets.google.com/viewform?formkey=dERvcnQ4SlFsX0ZLQi1KOE8wbk5obUE6MA.. online form].

Want to design interfaces or build stuff with microformats and want help doing it? Sign up! Add yourself. Note your site (with [[hCard]] if you have it), interests/projects, and tag yourself as a web '''author''', '''designer''', '''<abbr title="information architect">IA</abbr>''', '''publisher''', '''developer''', '''UI-tester''' - pick at least one.
# [http://tantek.com Tantek Çelik] - developer, designer (user interface interaction)
# [http://yury.name Yury Lifshits]
# [http://www.markng.co.uk Mark Ng]
# [http://www.ics.uci.edu/~rohit Rohit Khare] - developer
# [http://www.jasonbolton.com Jason Bolton] - front-end designer
# [http://alpern.org Micah Alpern] - designer (user interface interaction) (will be there Sunday).
# [[User:EdwardOConnor |Edward O'Connor]] (Ted) - author, designer, developer, publisher
# [http://singpolyma.net Stephen Paul Weber] - developer, publisher
# [http://feedblog.org Kevin Burton] - developer
# [http://jobspice.com Dane Hurtubise] - developer
# [http://developer.netflix.com JR Conlin] - developer, publisher
# Chirag Shah - developer
# [http://www.wezaggle.com Jesse Hammons] - developer [http://www.wezaggle.com Zaggle Social Calendar]
# [http://matthewlevine.com Matthew Levine] - developer
# [http://farukat.es/ Faruk Ateş] - UX Designer, developer
# [http://fourkitchens.com/ David Strauss] - Drupal, developer
# [http://huyhong.com/ Huy Hong] - Frontend Developer, UI/UX/UE, UGC nut
# [http://objectadjective.com Jeremy Anderson] - UX/UI/ID Designer, developer
# [http://objectadjective.com Lauren Scime] - front end designer / developer
# [http://blog.oofn.net Chad Weider] developer, designer, front-end, back-end, etc.
# (and about 35 more folks, according to [http://upcoming.yahoo.com/event/2888376/ Upcoming] as of noon Thursday 2009-7-23)
# ...

==schedule==
Outline of schedule for the weekend - more details at the DevCamp!
* Saturday July 25th
** 11:00am - planners+volunteers onsite for setup
** 12:00pm - registration, lunch
** intro session, what is a devcamp, introductions
** hack/project brainstorming and proposals
** day 1 building sessions
** dinner and group photo
** day 1 demos and social hour
** evening open hacking session (like DevHouse) / iteration on hacks/projects

* Sunday July 26th
** 10:00am - breakfast
** day 2 working sessions on hacks/projects
** 12:30pm lunch
** day 2 working sessions continued
** second day demos and wrap-up
** venue clean-up
** 5pm venue exit

==venue==
Automattic has very graciously agreed to host microformatsDevCamp. The venue has:
* wifi
* power. power outlets, extension cords, power strips
* 4-5 rooms/meeting areas.
* 3 projectors
* 1 whiteboard.
* sink, water.

As Automattic is donating the venue, as participants it is our responsibility to take excellent care of the venue, leaving it as good or better than we found it.

Some amount of camping overnight at the venue will be possible.

=== nearby food ===
Suggestions for nearby (easy/quick walking distance) drinks, snacks, food.
* Bayside Market - fresh fruit and vegetables, sandwiches. http://www.yelp.com/biz/bayside-market-san-francisco-2
* Crossroads Cafe - coffee, espresso drinks, shakes, smoothies, bagels, sandwiches. http://www.yelp.com/biz/crossroads-cafe-san-francisco-3
* ...

== tags ==
Please use the following tags when tagging related content (blog posts, photos, videos):

tags:
<kbd class="tags" style="display:block">
'''#ufdevcamp'''
ufdevcampsf
microformats
microformatsDevCamp
microformatsDevCampSF
microformats-meetup
BarCamp
BarCamp2009
Automattic
The-Embarcadero
san-francisco
upcoming:event=2888376
</kbd>

Track:
* [http://search.twitter.com/search?q=ufdevcamp #ufdevcamp on Twitter Search].
* [http://identi.ca/tag/ufdevcamp #ufdevcamp] tagspace on identi.ca.

Groups:
* [http://identi.ca/group/microformats !microformats Identi.ca group] (aliases: !mf and !uf). Join and address the whole group. Notices to this group can also be tracked from [http://identi.ca/tag/microformats #microformats]

== notes ==
topics discussed:
* ...

== hack ideas ==
Have an idea for a hack/project session? Please read <cite>[http://factoryjoe.com/blog/2007/07/13/what-is-a-devcamp/ What is a DevCamp?]</cite> and then suggest something or add a "+1" to existing suggestions, and sign your suggestion or opinion with your Username with <nowiki>~~~</nowiki>
<div class="discussion">
* '''microformats and user sign-up user interface''' - how can importing and subscribing to hCards help make user sign-up easier and thus get more users signed up quicker? [[User:Tantek|Tantek]]
* '''using hCard to build a self-updating address book''' - in the search for an address book/contact list that actually stays up to date, hCard may be the key. [[User:Beaulebens|Beau Lebens]]
** +1 [[User:Tantek|Tantek]]
* '''microWall''' - make sure to print a screen-shot of every microformat-savvy tool that comes up during the camp, and stick them on the wall. It will be an amazing backdrop for a group photo... [[User:Rohit|Rohit]]
** +1 [[User:Tantek|Tantek]]
* '''(Sunday)''' '''CSS3, HTML5 and microformats "Zen Garden"''' - same premise as the CSS Zen Garden of yore, but with a strong emphasis on CSS3 advancements, microformats enrichment and done in HTML5. [[User:KuraFire|Faruk Ateş]]
* '''hCard to Google Address Book''' bookmarlet. [[User:Singpolyma|Singpolyma]]
* '''Microformat Aggregation''' [[User:jessehammons|Jesse Hammons]], [[User:yurylifshits|Yury Lifshits]], Andrew McCollum, Dane Hurtibuse, Randy Kerber
* '''CheatSheet Translation''' [[User:Brian|Brian Suda]] This is a request to anyone who is speaks another language. I created the PDF cheatsheet awhile ago http://suda.co.uk/projects/microformats/cheatsheet/ if someone wants to translate it into Spanish, or another language, please let me know. I can send the source InDesign file, or if they send me the translations, I'd be happy to update it myself.
</div>

== projects ==
Please create a wiki page for any hack/project session you lead or attend and link to it from here.
* [[hCardInputInterface]] for easy input of user data (creating hCards).
* [[hcard-contact-autocompletion]]
* [[Micro Format Services]]
* [[unified-rsvp]]

== photographs ==
* ...

== blog posts ==
Blog posts about the devCamp. Newest first.
* [http://microformats.org/blog/2009/07/20/microformatsdevcamp-this-weekend/ 2009-07-21 microformats.org: microformatsDevCamp this weekend!]
* [http://radar.oreilly.com/2009/07/four-short-links-17-july-2009.html O'Reilly Radar: Four short links]
* ...

== see also ==
* [http://factoryjoe.com/blog/2007/07/13/what-is-a-devcamp/ Chris Messina: What is a DevCamp?]
* ...

</div> 

== Related Pages==
microformatsDevCamp is one of several microformats [[events]].

{{events-related-pages}}

== planner to-do ==

=== planners ===
Want to help organize and plan the first microformatsDevCamp? Sign up and be sure to pick up a planner role (see below).
* [[User:Tantek|Tantek Çelik]] - '''organizing, venue acquisition, intro and kickoff'''
* [[User:Rohit|Rohit Khare]] - '''venue acquisition, sponsor wrangler, food'''
* [[User:EdwardOConnor |Edward O'Connor]] (Ted) - '''volunteer coordinator, setup, welcome desk'''
* [[User:Pseudowish|Lauren Scime]] - '''t-shirts, other coordination needs tbd'''
* [[User:Chris Messina|Chris Messina]] - '''connector and advisor'''

=== planner roles ===
Role info / details:
* '''intro and kickoff''' - run the introductory session and help start the microformatsDevCamp with traditional BarCamp intros/3tags and explanation of the BarCamp format.
* '''food''' - coordinate / match up sponsors with meals and make sure the meals arrive and are setup for event participants during the event.
* '''sponsor wrangler''' - for food, t-shirts. per definition given in: http://www.cleverclevergirl.com/?p=10 : <blockquote>Drafts a message to send to potential sponsors, follows up leads from others for potential sponsors, collects info, logos (in vector format), and money from sponsors and also sees that receipts (if necessary) are issued at the end. </blockquote>
* '''t-shirts''' - get estimate, make sure to order in time for the event. Ben Ward has done some work on this - check with him.
* '''volunteer coordinator''' - recruit and organize volunteers the day of the event to help out with food, setup
* '''cleanup''' - enlist help of volunteers and all devCamp participants to help with cleanup
* '''setup''' - be in charge of setup the day of, coordinate with venue on setup plenty of time *before* the start of the camp! setup: power cords, power strips, calendar grid for sessions, tables and chairs in rooms/meeting areas, projectors
* '''welcome desk''' - welcome microformatsDevCamp attendees at the entrance of the venue, make sure they get a name tag and instruct them to tag themselves as primarily/secondarily being a web '''author''', '''designer''', '''publisher''', '''developer''', pick at least one. (as they should also do when the sign up on the wiki in the attendees section above!)

===T-shirts===
* get estimates from vendor(s) for different quantities
** get vendor contact info from Ben Ward who has already looked into this and found a reliable vendor that can deliver high quality t-shirts in a week or less time.
** Suggestion: 100 shirts, provide them to individuals who sponsor microformatsDevCamp with a $20 or more donation to help pay for t-shirts and snacks/food (if any funds from covering t-shirts are remaining). [[User:Tantek|Tantek]] 17:40, 17 July 2009 (UTC)
* make/reuse design (get original t-shirt design details from Dan Cederholm)
* order/print - make sure folks who donated at the [[events/2009-06-26-microformats-4th-bday|4th bday party]] get their shirts

* '''T-shirts are ordered!''' Printer is [http://www.screenprintguy.com The Screen Print Guy] located out on 23rd Ave. Will be available for pickup by Friday July 24th. (This is great! [[User:Tantek|Tantek]] 01:03, 21 July 2009 (UTC))
** Total # of shirts ordered: 100. Size breakdown: Men's: 10 small, 30 medium, 25 large. Women's: 10 small, 15 medium, 10 large.
** Total cost: $918.00 (would have been cheaper but they had a surcharge for the rush order). I have charged 50% of the cost already to place the order. Other 50% due at time of pickup.

Note that, including cash donations from the 4th birthday party, we have pledges for ~$1850 to budget with as of 2009-7-24 [[User:Rohit|Rohit]]

WYSIWYG-plugins

2009-07-06T22:00:47Z

Brian: we'll need some buttons

This is a list of WYSIWYG editors and the plugins to be developed and translated so that it is easy to add microformats into CMS systems.

==TinyMCE==
* Homepage link
* Developer notes
* Plugins to Create
** rel-license
** rel-tag
** (more)

==(more???)==
* Homepage link
* Developer notes

=Icons=
We will need some standardized icon styles for these buttons. Recommendations? Styles?

WYSIWYG-plugins

2009-07-06T21:48:06Z

Brian: stubbed

x2v

2009-06-26T19:31:59Z

Brian: testing on this page instead of live page

<entry-title>X2V</entry-title>
[http://suda.co.uk/projects/X2V/ X2V] is an open source [[microformats]] XSLT [[implementation]] by [[User:Brian|Brian Suda]] that [[parsers|parses]] [[hCard]] or [[hCalendar]] events in (X)HTML and transforms them into the corresponding vCard (.vcf) or iCalendar (.ics) file respectively.

[[implementors#Technorati|Technorati]] hosts a deployment of X2V for converting hCard contacts or hCalendar events at:
* http://feeds.technorati.com/contacts/
* http://feeds.technorati.com/events/

The latest beta and development versions of X2V can be tested at:
* http://suda.co.uk/projects/X2V/

== feedback ==
Feature requests and other general feedback.
When this section grows to big we can move it to [[x2v-feedback]].
<div class="discussion">
* Would be great if X2V implemented the full [[value-class-pattern]] or even parts thereof, e.g. value-title. [[User:Tantek|Tantek]] 07:20, 25 June 2009 (UTC)
</div>

==Test==
<div class="event-page vevent" id="party">
;When
:2009-06-26 at 19:00 to 2009-06-26 at 22:00
;Where
:[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
;What
:microformats.org 4th birthday party!
;Web
:http://microformats.org/wiki/events/2009-06-26-microformats-4th-bday
:http://upcoming.yahoo.com/event/3010807
;Donation
:Donation requested at the door: sliding scale $5-$20.
</div> 

== issues ==
Bugs or other apparent problems. See [[x2v-issues]].

== see also ==
* [[hCard]]
* [[hcard-implementations]]
* [[vcard-implementations]]
* [[hCalendar]]
* [[hcalendar-implementations]]
* [[icalendar-implementations]]
* [[implementations]]

x2v

2009-06-26T19:30:08Z

Brian: testing on this page instead of live page

<entry-title>X2V</entry-title>
[http://suda.co.uk/projects/X2V/ X2V] is an open source [[microformats]] XSLT [[implementation]] by [[User:Brian|Brian Suda]] that [[parsers|parses]] [[hCard]] or [[hCalendar]] events in (X)HTML and transforms them into the corresponding vCard (.vcf) or iCalendar (.ics) file respectively.

[[implementors#Technorati|Technorati]] hosts a deployment of X2V for converting hCard contacts or hCalendar events at:
* http://feeds.technorati.com/contacts/
* http://feeds.technorati.com/events/

The latest beta and development versions of X2V can be tested at:
* http://suda.co.uk/projects/X2V/

== feedback ==
Feature requests and other general feedback.
When this section grows to big we can move it to [[x2v-feedback]].
<div class="discussion">
* Would be great if X2V implemented the full [[value-class-pattern]] or even parts thereof, e.g. value-title. [[User:Tantek|Tantek]] 07:20, 25 June 2009 (UTC)
</div>

==Test==
<div class="event-page vevent" id="party">
== summary ==
;When
:2009-06-26 aT 19:00:00 to 2009-06-26 aT 22:00:00
;Where
:[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
;What
:microformats.org 4th birthday party!
;Web
:http://microformats.org/wiki/events/2009-06-26-microformats-4th-bday
:http://upcoming.yahoo.com/event/3010807
;Donation
:Donation requested at the door: sliding scale $5-$20.
</div> 

== issues ==
Bugs or other apparent problems. See [[x2v-issues]].

== see also ==
* [[hCard]]
* [[hcard-implementations]]
* [[vcard-implementations]]
* [[hCalendar]]
* [[hcalendar-implementations]]
* [[icalendar-implementations]]
* [[implementations]]

events/2009-06-26-microformats-4th-bday

2009-06-26T19:23:20Z

Brian: removed hCalendar test

http://anendlessarray.com/microformats/728x90.jpg
<entry-title>microformats.org 4th birthday party!</entry-title>

Celebrate the 4th birthday of http://microformats.org! One of several microformats [[events]].

If you'd like to help out with or attend the party, please add your name below.

[[#attending|RSVP]] required for venue capacity tracking.

<div class="event-page vevent" id="party">
== summary ==
;When
:2009-06-26 aT 19:00:00 to 2009-06-26 aT 22:00:00
;Where
:[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
;What
:microformats.org 4th birthday party!
;Web
:http://microformats.org/wiki/events/2009-06-26-microformats-4th-bday
:http://upcoming.yahoo.com/event/3010807
;Donation
:Donation requested at the door: sliding scale $5-$20.
</div> 

'''[http://feeds.technorati.com/events/microformats.org/wiki/events/2009-06-26-microformats-4th-bday%23party Add this event to your calendar]''' [http://feeds.technorati.com/events/microformats.org/wiki/events/2009-06-26-microformats-4th-bday%23party http://www.boogdesign.com/images/buttons/microformat_hcalendar.png]

== sponsors ==
Please sign up to sponsor the microformats.org 4th birthday party!

* [http://objectadjective.com Object Adjective] is a proud sponsor of this event.
* [http://www.ribbit.com/ Ribbit] is proud to sponsor the party
* [http://spinn3r.com Spinn3r] is a proud sponsor of the party
* ...

== attending ==
I'm going to show up and help celebrate so I'm signing up here with my name linked to my user page (or personal web site).
# [[User:Tantek|Tantek Çelik]]
# [[User:Kevin_Marks|Kevin Marks]]
# [[User:BenWard|Ben Ward]]
# [[User:Pseudowish|Lauren Scime]]
# [[User:Repeatpenguin|Jeremy Anderson]]
# [[User:Richardault|Richard Ault]]
# [[User:KevinBurton|Kevin Burton]] of [http://spinn3r.com Spinn3r] - I will be by for an hour or so... Spinn3r's 3.0 launch dinn3r is that evening too.
# [[User:Singpolyma|Singpolyma]]
# [http://brynnevans.com Brynn Evans]
# [http://factoryjoe.com Chris Messina]
# [http://lizdunn.com Liz Dunn]
# [http://www.myspace.com/ciberch Monica Keller]
# [http://www.reelgeek.com Erin Caton]
# [http://www.dustindiaz.com Dustin Diaz]
# [http://pixelimplosion.com Robert Andersen]
# ...

== regrets ==
I'd love to be there but can't. Happy 4th birthday from afar!
* [[User:Rohit|Rohit Khare]]
* [[User:Cindyli|Cindy Li]]
* [[User:Tonystubblebine|Tony Stubblebine]]
* [[User:Anildash|Anildash]] 20:07, 24 June 2009 (UTC)
* [[User:NiallKennedy|Niall Kennedy]] - in Los Angeles
* [[User:KaviGoel|Kavi Goel]]
* [[User:DrErnie|Ernest Prabhakar]]
* ...

== location ==
* [http://www.yelp.com/biz/b-restaurant-and-bar-san-francisco B Restaurant and Bar] - June 26th, 2009 at 7pm
** Will have hors d'oeuvres and about 50-60 drink tix to hand out to people at the door. Attendees can buy drinks at cash bar after drink tix are used.

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

tags:
<kbd class="tags" style="display:block">
'''ufbday4'''
microformats-party
microformats-4th-birthday
microformats
san-francisco
soma
howard-street
Yerba-Buena
B-Restaurant-And-Bar
B-Bar
''microformats-party-2009-06-26''
''upcoming:event=3010807''
</kbd>

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

== Promotional Graphics ==
* Banners & Images of Various Sizes: Promote Microformats 4 Year Birthday Party!
** [http://anendlessarray.com/microformats/88x31.jpg 88x31px] [http://anendlessarray.com/microformats/88x31.jpg http://anendlessarray.com/microformats/88x31.jpg]
** [http://anendlessarray.com/microformats/728x90.jpg 728x90px] [http://anendlessarray.com/microformats/728x90.jpg http://anendlessarray.com/microformats/728x90.jpg]
** [http://anendlessarray.com/microformats/728x90-pink.jpg 728x90px w/Pink] [http://anendlessarray.com/microformats/728x90-pink.jpg http://anendlessarray.com/microformats/728x90-pink.jpg]
** [http://anendlessarray.com/microformats/125x125.jpg 125x125px] [http://anendlessarray.com/microformats/125x125.jpg http://anendlessarray.com/microformats/125x125.jpg]
** [http://anendlessarray.com/microformats/200x100.jpg 200x100px] [http://anendlessarray.com/microformats/200x100.jpg http://anendlessarray.com/microformats/200x100.jpg]
** [http://anendlessarray.com/microformats/200x200.jpg 200x200px] [http://anendlessarray.com/microformats/200x200.jpg http://anendlessarray.com/microformats/200x200.jpg]
** [http://anendlessarray.com/microformats/300x225.jpg 300x225px] [http://anendlessarray.com/microformats/300x225.jpg http://anendlessarray.com/microformats/300x225.jpg]
** [http://anendlessarray.com/microformats/120x240.jpg 120x240px] [http://anendlessarray.com/microformats/120x240.jpg http://anendlessarray.com/microformats/120x240.jpg]
** [http://anendlessarray.com/microformats/250x250.jpg 250x250px] [http://anendlessarray.com/microformats/250x250.jpg http://anendlessarray.com/microformats/250x250.jpg]
** [http://anendlessarray.com/microformats/468x60.jpg 468x468px] [http://anendlessarray.com/microformats/468x60.jpg http://anendlessarray.com/microformats/468x60.jpg]
** [http://anendlessarray.com/microformats/160x600.jpg 160x600px] [http://anendlessarray.com/microformats/160x600.jpg http://anendlessarray.com/microformats/160x600.jpg]

* Note: If you are DYING to have a different size than the ones up here I can either send you the photoshop file or make you a custom one - Just send a request to lauren@objectadjective.com or find pseudowish on the [[IRC]]

== planners ==
This section is for organizing a party for the upcoming 4th birthday of http://microformats.org.

I'm donating my time before the event to help plan and make the party happen!
* [[User:Tantek|Tantek Çelik]] - coordinating, sponsors
* [[User:Rohit|Rohit Khare]] - sponsors
* [[User:Kevin_Marks|Kevin Marks]] - sponsors
* [[User:BenWard|Ben Ward]] - tshirts, sponsors
* [[User:Pseudowish|Lauren Scime]] - design / venue / sponsors / publicity
* [[User:Repeatpenguin|Jeremy Anderson]] - will be assisting Lauren w/ above.

We need:
* a volunteer coordinator. someone to coordinate the volunteers listed below.
* [[stickers]] - Lauren is on it
** 500 rounded square 2" stickers w/logo on black background have come in the mail
* tshirts - Ben is on it

== volunteers ==
Sign up to be a volunteer!
We need volunteers to check people in at the door, take donations, hand out stickers, t-shirts etc.
* [[User:Richardault|Richard Ault]] - Checking names and taking donations for at least first hour. Need to find money box. Also need more volunteers to do same.
* ...

== donations ==
* Donation requested at the door: sliding scale $5-$20. $10 or more gets you a t-shirt (may have to order them on demand and hand out at the next dinner depending on whether t-shirts arrive or not).
* Donations go towards the party and [[events/2009-07-18-dev-camp|microformatsDevCamp]] this summer.

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

events/2009-06-26-microformats-4th-bday

2009-06-26T19:22:10Z

Brian: updating hcalendar code

http://anendlessarray.com/microformats/728x90.jpg
<entry-title>microformats.org 4th birthday party!</entry-title>

Celebrate the 4th birthday of http://microformats.org! One of several microformats [[events]].

If you'd like to help out with or attend the party, please add your name below.

[[#attending|RSVP]] required for venue capacity tracking.

<div class="event-page vevent" id="party">
== summary ==
;When
:
2009-06-26 at 19:00 to 2009-06-26 aT 22:00:00
;Where
:[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
;What
:microformats.org 4th birthday party!
;Web
:http://microformats.org/wiki/events/2009-06-26-microformats-4th-bday
:http://upcoming.yahoo.com/event/3010807
;Donation
:Donation requested at the door: sliding scale $5-$20.
</div> 

'''[http://feeds.technorati.com/events/microformats.org/wiki/events/2009-06-26-microformats-4th-bday%23party Add this event to your calendar]''' [http://feeds.technorati.com/events/microformats.org/wiki/events/2009-06-26-microformats-4th-bday%23party http://www.boogdesign.com/images/buttons/microformat_hcalendar.png]

== sponsors ==
Please sign up to sponsor the microformats.org 4th birthday party!

* [http://objectadjective.com Object Adjective] is a proud sponsor of this event.
* [http://www.ribbit.com/ Ribbit] is proud to sponsor the party
* [http://spinn3r.com Spinn3r] is a proud sponsor of the party
* ...

== attending ==
I'm going to show up and help celebrate so I'm signing up here with my name linked to my user page (or personal web site).
# [[User:Tantek|Tantek Çelik]]
# [[User:Kevin_Marks|Kevin Marks]]
# [[User:BenWard|Ben Ward]]
# [[User:Pseudowish|Lauren Scime]]
# [[User:Repeatpenguin|Jeremy Anderson]]
# [[User:Richardault|Richard Ault]]
# [[User:KevinBurton|Kevin Burton]] of [http://spinn3r.com Spinn3r] - I will be by for an hour or so... Spinn3r's 3.0 launch dinn3r is that evening too.
# [[User:Singpolyma|Singpolyma]]
# [http://brynnevans.com Brynn Evans]
# [http://factoryjoe.com Chris Messina]
# [http://lizdunn.com Liz Dunn]
# [http://www.myspace.com/ciberch Monica Keller]
# [http://www.reelgeek.com Erin Caton]
# [http://www.dustindiaz.com Dustin Diaz]
# [http://pixelimplosion.com Robert Andersen]
# ...

== regrets ==
I'd love to be there but can't. Happy 4th birthday from afar!
* [[User:Rohit|Rohit Khare]]
* [[User:Cindyli|Cindy Li]]
* [[User:Tonystubblebine|Tony Stubblebine]]
* [[User:Anildash|Anildash]] 20:07, 24 June 2009 (UTC)
* [[User:NiallKennedy|Niall Kennedy]] - in Los Angeles
* [[User:KaviGoel|Kavi Goel]]
* [[User:DrErnie|Ernest Prabhakar]]
* ...

== location ==
* [http://www.yelp.com/biz/b-restaurant-and-bar-san-francisco B Restaurant and Bar] - June 26th, 2009 at 7pm
** Will have hors d'oeuvres and about 50-60 drink tix to hand out to people at the door. Attendees can buy drinks at cash bar after drink tix are used.

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

tags:
<kbd class="tags" style="display:block">
'''ufbday4'''
microformats-party
microformats-4th-birthday
microformats
san-francisco
soma
howard-street
Yerba-Buena
B-Restaurant-And-Bar
B-Bar
''microformats-party-2009-06-26''
''upcoming:event=3010807''
</kbd>

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

== Promotional Graphics ==
* Banners & Images of Various Sizes: Promote Microformats 4 Year Birthday Party!
** [http://anendlessarray.com/microformats/88x31.jpg 88x31px] [http://anendlessarray.com/microformats/88x31.jpg http://anendlessarray.com/microformats/88x31.jpg]
** [http://anendlessarray.com/microformats/728x90.jpg 728x90px] [http://anendlessarray.com/microformats/728x90.jpg http://anendlessarray.com/microformats/728x90.jpg]
** [http://anendlessarray.com/microformats/728x90-pink.jpg 728x90px w/Pink] [http://anendlessarray.com/microformats/728x90-pink.jpg http://anendlessarray.com/microformats/728x90-pink.jpg]
** [http://anendlessarray.com/microformats/125x125.jpg 125x125px] [http://anendlessarray.com/microformats/125x125.jpg http://anendlessarray.com/microformats/125x125.jpg]
** [http://anendlessarray.com/microformats/200x100.jpg 200x100px] [http://anendlessarray.com/microformats/200x100.jpg http://anendlessarray.com/microformats/200x100.jpg]
** [http://anendlessarray.com/microformats/200x200.jpg 200x200px] [http://anendlessarray.com/microformats/200x200.jpg http://anendlessarray.com/microformats/200x200.jpg]
** [http://anendlessarray.com/microformats/300x225.jpg 300x225px] [http://anendlessarray.com/microformats/300x225.jpg http://anendlessarray.com/microformats/300x225.jpg]
** [http://anendlessarray.com/microformats/120x240.jpg 120x240px] [http://anendlessarray.com/microformats/120x240.jpg http://anendlessarray.com/microformats/120x240.jpg]
** [http://anendlessarray.com/microformats/250x250.jpg 250x250px] [http://anendlessarray.com/microformats/250x250.jpg http://anendlessarray.com/microformats/250x250.jpg]
** [http://anendlessarray.com/microformats/468x60.jpg 468x468px] [http://anendlessarray.com/microformats/468x60.jpg http://anendlessarray.com/microformats/468x60.jpg]
** [http://anendlessarray.com/microformats/160x600.jpg 160x600px] [http://anendlessarray.com/microformats/160x600.jpg http://anendlessarray.com/microformats/160x600.jpg]

* Note: If you are DYING to have a different size than the ones up here I can either send you the photoshop file or make you a custom one - Just send a request to lauren@objectadjective.com or find pseudowish on the [[IRC]]

== planners ==
This section is for organizing a party for the upcoming 4th birthday of http://microformats.org.

I'm donating my time before the event to help plan and make the party happen!
* [[User:Tantek|Tantek Çelik]] - coordinating, sponsors
* [[User:Rohit|Rohit Khare]] - sponsors
* [[User:Kevin_Marks|Kevin Marks]] - sponsors
* [[User:BenWard|Ben Ward]] - tshirts, sponsors
* [[User:Pseudowish|Lauren Scime]] - design / venue / sponsors / publicity
* [[User:Repeatpenguin|Jeremy Anderson]] - will be assisting Lauren w/ above.

We need:
* a volunteer coordinator. someone to coordinate the volunteers listed below.
* [[stickers]] - Lauren is on it
** 500 rounded square 2" stickers w/logo on black background have come in the mail
* tshirts - Ben is on it

== volunteers ==
Sign up to be a volunteer!
We need volunteers to check people in at the door, take donations, hand out stickers, t-shirts etc.
* [[User:Richardault|Richard Ault]] - Checking names and taking donations for at least first hour. Need to find money box. Also need more volunteers to do same.
* ...

== donations ==
* Donation requested at the door: sliding scale $5-$20. $10 or more gets you a t-shirt (may have to order them on demand and hand out at the next dinner depending on whether t-shirts arrive or not).
* Donations go towards the party and [[events/2009-07-18-dev-camp|microformatsDevCamp]] this summer.

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

events

2009-05-12T14:59:41Z

Brian: added Twiist.be conference link

<entry-title>Microformats related events</entry-title>
Please add microformats 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 ==
Track current and future microformats events by subscribing to <kbd style="display:block;margin:1em 0">'''webcal://feeds.technorati.com/events/microformats.org/wiki/events'''</kbd> in your calendar app. Set it to update once a day and new events will appear automatically.

You may also download [http://technorati.com/events/microformats.org/wiki/events events on this page as a standalone iCalendar file].

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

== upcoming ==


*2009-05-12 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-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

== recent ==


=== May 2009 ===
*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-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}}

Main Page

2009-03-24T10:35:31Z

Brian: Reverted edits by Admins (Talk) to last version by Stilist

<entry-title>Welcome to the microformats wiki!</entry-title>
__TOC__
Please start with the [[introduction]] page and read [[how-to-play]] before making any edits.

==Introduction==

This wiki is the central resource of the microformats community. You'll find current versions of published microformat specifications, specification drafts and publishing patterns. The wiki also hosts development resources, such as brainstorming pages for new formats and issue tracking pages for all current and in-development microformats.

To get started with microformats:

* First, be familiar writing your pages and applications with semantically rich, descriptive, ‘[http://microformats.org/wiki/posh <abbr title="Plain Old Semantic HTML">POSH</abbr>]’ <abbr title="HyperText Mark-up Language">HTML</abbr>.
* Learn about microformats from the [http://microformats.org/about/ about page], [http://microformats.org/ blog], [[press]], [[presentations]], [[books]], [[podcasts]], & [[screencasts]] pages.
* Take a look at established specifications such as [[hcard|hCard]] and [[hcalendar|hCalendar]], and follow the [[hcard-examples|examples]] to start publishing microformats.
* Have questions? Read the [[faq|frequently asked questions]] and see the [[glossary]] for terms and definitions. You can also post to the {{MicroformatsMailingList}}.
* Want to learn more in person? Check out microformats [[events]].

Also, this wiki has a number of neat enhancements to assist development and contributions to microformats. Before you start editing, see the [[wiki-2|wiki introduction page]] for instructions.

==Definition==
Microformats are small patterns of HTML to represent commonly published things like [[hcard|people]], [[hcalendar|events]], [[hatom|blog posts]], [[hreview|reviews]] and [[rel-tag|tags]] in web pages.

Microformats enable the publishing of higher fidelity information on the Web; the fastest and simplest way to provide feeds and APIs for the information in your website.

* Read more explanations of [[what-are-microformats|what microformats are]], and [[what-can-you-do-with-microformats|what you can do with them]].

== How to contribute ==
Do you want to help take microformats to the next level? You can:

* [[get-started|Get started]] by adding microformats to your website, services, and products.
* [[advocacy|Advocate]] the use of microformats on other web sites, especially those you use.
* Write a [[testimonial]].
* Do something on the [[to-do|to do list]].
* Join the [[irc|IRC Channel]] and [[mail|mailing lists]] to learn and help answer questions (read the [[mailing-lists#General_guidelines|general guidelines]] before posting).
* [[Main_Page#microformats_wiki_translations|Translate this microformats wiki into other languages]] to make microformats more accessible to readers of languages around the world.
* Before proposing any new microformats, make sure your website is [[POSH]], [[get-started|uses existing microformats]], and then read the [[process]].

== Specifications ==
The list of current, stable [[microformats|Microformats]] open standard specifications.

* [[hcalendar|hCalendar]] - [http://microformats.org/code/hcalendar/creator hCalendar creator]
* [[hcard|hCard]] - [http://microformats.org/code/hcard/creator hCard creator]
* [[rel-license]]
* [[rel-nofollow]]
* [[rel-tag]]
* [[vote-links|VoteLinks]]
* [[XFN]] - [http://gmpg.org/xfn/creator XFN creator]
* [[XMDP]]
* [[xoxo|XOXO]]

''If you're tempted to try your hand at writing a microformat please read '''[[process|the process]]''' page first!''

== Drafts ==
Drafts are newer microformats, for which the specifications haven't been completed yet. Although drafts are somewhat mature in the development process, the stability of these documents cannot be guaranteed, and implementers should be prepared to keep abreast of future developments and changes. Please watch the wiki pages for updates.

* [[adr|adr]] - for marking up address information
* [[geo|geo]] - for marking up [http://en.wikipedia.org/wiki/WGS84 WGS84] geographic coordinates (latitude; longitude)
* [[hatom|hAtom]] - syndicating episodic content (e.g. weblog postings)
* [[haudio|hAudio]]
* [[hproduct|hProduct]]
* [[recipe|hRecipe]]
* [[hresume|hResume]] - for publishing resumes and CVs
* [[hreview|hReview]] - [http://microformats.org/code/hreview/creator hReview creator]
* [[rel-directory]] - to indicate that the destination of a hyperlink is a directory listing containing an entry for the current page
* [[rel-enclosure]] - for indicating attachments (e.g. files) to download and cache
* [[rel-home]] - indicate a hyperlink to the homepage of the site
* [[rel-payment]] - indicate a payment mechanism
* [[robots-exclusion|robots exclusion]]
* [[xfolk|xFolk]]

== Design Patterns ==
{{design_patterns}} 
* [[elemental-microformat|elemental microformats]]
* [[compound-microformat|compound microformats]]

== Exploratory Discussions ==
See: [[exploratory-discussions]] for details of research and analysis of real-world [[examples]], existing formats, and brainstorming of possible new microformats, per the microformats [[process]].

== Examples ==
* [[examples-in-the-wild]]
* [[implementations]]
* [[zen-garden]]

== Resources ==
See [[resources]].

== User centric development ==
*[[user-interface]]
*[[data-portability]]
*[[social-network-portability]]

== Shared work areas ==
* [[to-do]]
* [[templates]]
* [http://microformats.org/wiki/delete pages for deletion] 
* [[Special:Specialpages|"Special" wiki pages]]
* [[year-in-review]]

== Tools, test cases, additional research ==
The first place to look for examples, code, and test cases is in the pages for each individual microformat. There are only a few cross-cutting [[tools|tools and services]] that need to process more than one microformat. That section is intended for editors, [[parsers]], [[validators]], test cases, and other information relevant across multiple microformats.

== Microformats wiki translations ==
You may read and edit microformats articles in many other languages:

* languages with over 100 articles
** [[Main_Page-fr|Français (French)]] {{UpdateMarker-fr}}
* languages with over 10 articles
** [[Main_Page-pt-br|Português (Brazilian Portuguese)]]
** [[Main_Page-ja|日本語 (Japanese)]]
** [[Main_Page-ru|Русский (Russian)]]
* languages with over 2 articles
** [[Main_Page-cs|Česky (Czech)]] {{NewMarker}}
** [[Main_Page-de|Deutsch (German)]]
** [[Main_Page-es|Español (Spanish)]]
** [[Main_Page-gl|Galego (Galician)]] {{NewMarker}}
** [[Main_Page-pl|Polski (Polish)]]
** [[Main_Page-ro|Română (Romanian)]] {{NewMarker}}
** [[Main_Page-zh|汉语 (Chinese)]]
* languages just started
** [[Main_Page-ar|العربية (Arabic)]]
** [[Main_Page-th|ภาษาไทย (Thai)]]
** [[Main_Page-it|Italiano (Italian)]] {{NewMarker}}
** [[Main_Page-ko|한국어 (Korean)]] {{NewMarker}}
* elsewhere
**[http://en.wikipedia.org/wiki/Microformat Wikipedia's article on microformats] has been translated into a number of languages.

See also [[other-languages]], and [[how-to-start-new-translation|how-to-start-a-new-translation]].

existing-rel-values

2009-02-16T20:35:16Z

Brian: added Rel-Canonical to the POSH list

<h1> existing rel values </h1>
{{TOC-right}}

This page contains tables of known HTML rel values from specifications, formats, proposals, brainstorms, and non-trivial [[POSH]] usage in the wild. In addition, dropped and rejected values are listed at the end for comprehensiveness.

usage: see [[rel-faq#How_is_rel_used|how is 'rel' used]]. Regarding rev, see: [[rel-faq#Should_rev_even_be_used|should 'rev' even be used]].

== formats ==
These rel values are defined formats from specifications (HTML 4, microformats) are thus are recommended for general use. Alphabetically ordered by value.

Note:
* Do not add rel values you find in the wild to this table of rel formats, instead add them to the table in the [[existing-rel-values#POSH_usage|POSH section]].
* Do not add non-HTML rel values you find to this table of rel formats, instead add them to the table in the [[existing-rel-values#non_HTML_rel_values|non HTML rel values section]].
* Do not add rel values from obsolete/superceded proposals or drafts, instead add them to the table in the "dropped" section.

Sources:
* W3C [http://www.w3.org/TR/html401/types.html#h-6.12 HTML 4 link type] and [http://www.w3.org/TR/grddl/ GRDDL] specs.
* [[xfn]] and other [[microformats]]

{| border="1"
|+
! rel value !! summary (from the relevant specification where possible)) !! defining specification

|-
| [[rel-acquaintance|acquaintance]] || the person represented by the current document considers the person represented by the referenced document to be an acquaintance || [[XFN]]

|-
| [[rel-alternate|alternate]] || Designates substitute versions for the document in which the link occurs. When used together with the <code>lang</code> attribute, it implies a translated version of the document. When used together with the <code>media</code> attribute, it implies a version designed for a different medium (or media). || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-appendix|appendix]]|| Refers to a document serving as an appendix in a collection of documents. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-bookmark|bookmark]] || Refers to a bookmark. A bookmark is a link to a key entry point within an extended document. The <code>title</code> attribute may be used, for example, to label the bookmark. Note that several bookmarks may be defined in each document. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-chapter|chapter]] || Refers to a document serving as a chapter in a collection of documents. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-child|child]] || the referenced person is a child of the person represented by the current document|| [[XFN]]

|-
| [[rel-colleague|colleague]] || the referenced person is a colleague of the person represented by the current document|| [[XFN]]

|-
| [[rel-contact|contact]] || the person represented by the current document considers the person represented by the referenced document to be a contact || [[XFN]]

|-
| [[rel-contents|contents]] || Refers to a document serving as a table of contents. Some user agents also support the synonym ToC (from "Table of Contents"). || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-copyright|copyright]] || Refers to a copyright statement for the current document. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-co-resident|co-resident]] || the referenced person lives in the same residence as the person represented by the current document|| [[XFN]]

|-
| [[rel-co-worker|co-worker]] || the referenced person is a co-worker of the person represented by the current document|| [[XFN]]

|-
| [[rel-crush|crush]] || this person considers the referenced person to be a crush (i.e. has a crush on the referenced person)|| [[XFN]]

|-
| [[rel-date|date]] || this person considers the referenced person to be a date (i.e. is dating the referenced person)|| [[XFN]]

|-
| [[rel-friend|friend]] || the person represented by the current document considers the person represented by the referenced document to be a friend || [[XFN]]

|-
| [[rel-glossary|glossary]]|| Refers to a document providing a glossary of terms that pertain to the current document.||[http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-help|help]] || Refers to a document offering help (more information, links to other sources information, etc.) || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-index|index]] || Refers to a document providing an index for the current document. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-kin|kin]] || the referenced person is part of the extended family of the person represented by the current document|| [[XFN]]

|-
| [[rel-license|license]] || …indicates that the <nowiki>[referenced document]</nowiki> is a license for the current page. || [[rel-license]]

|-
| [[rel-me|me]] || the referenced document represents the same person as does the current document || [[XFN]]

|-
| [[rel-met|met]] || this person has met the referenced person || [[XFN]]

|-
| [[rel-muse|muse]] || the referenced person inspires the person represented by the current document|| [[XFN]]

|-
| [[rel-neighbor|neighbor]] || the referenced person lives nearby the person represented by the current document || [[XFN]]

|-
| [[rel-next|next]] || Refers to the next document in a linear sequence of documents. User agents may choose to preload the "next" document, to reduce the perceived load time. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-nofollow|nofollow]] || indicates that the destination of that hyperlink {{should-not}} be afforded any additional weight or ranking by user agents which perform link analysis upon web pages (e.g. search engines). || [[rel-nofollow]]

|-
| [[rel-parent|parent]] || the referenced person is a parent of the person represented by the current document|| [[XFN]]

|-
| [[rel-prev|prev]]|| Refers to the previous document in an ordered series of documents. Some user agents also support the synonym "Previous". || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-previous|previous]] || Synonym of <code>prev</code> || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-section|section]] || Refers to a document serving as a section in a collection of documents. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-sibling|sibling]] || the referenced person is a sibling of the person represented by the current document|| [[XFN]]

|-
| [[rel-spouse|spouse]] || the referenced person is a spouse of the person represented by the current document|| [[XFN]]

|-
| [[rel-start|start]] || Refers to the first document in a collection of documents. This link type tells search engines which document is considered by the author to be the starting point of the collection. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-stylesheet|stylesheet]] || a style sheet for the current document used with the invisible <link href> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <a href> are strongly preferred. Unfortunately the use of stylesheet in user visible content like <a href> appears to be strictly theoretical. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-subsection|subsection]] || Refers to a document serving as a subsection in a collection of documents. || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-sweetheart|sweetheart]] || this person considers the referenced person to be their sweetheart || [[XFN]]

|-
|[[rel-tag|tag]] || …indicates that the <nowiki>[referenced document]</nowiki> is an author-designated "tag" (or keyword/subject) for the current page. || [[rel-tag]]

|-
|[[rel-toc|toc]] || Synonym of <code>contents</code> (from "Table Of Contents") || [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4 link type]

|-
| [[rel-transformation|transformation]] || Relates a source document to a transformation, usually represented in XSLT, that relates the source document syntax to the RDF graph syntax. Used in [[grddl|GRDDL]] || [http://www.w3.org/TR/grddl/#transformation GRDDL spec]

|-
|}

=== notes ===
*<code>rel="alternate"</code> can take further meaning from additional attributes, such as
** <code>rel="alternate" lang="fr"</code> (French language version of this page)
** <code>rel="alternate" media="print"</code> (printable version of this page)
** <code>rel="alternate" media="handheld"</code> (version of the page intended or better for handheld/portable devices like PDAs, cell phones, etc.)

*Synonyms such as "previous", "toc" are not as widely supported as the main term.

== proposals ==
A few rel values have been developed as drafts as a result of going through most of the microformats [[process]], and are thus listed here for your serious consideration. You may use these values, and if you find any problems with them please point them out on the respective "issues" page for the rel value.

{| border="1"
|+
! rel value !! summary !! proposed in !! external spec (if any)
|-
| [[rel-directory|directory]] || …indicates that the destination of the hyperlink is a directory listing containing an entry for the current page. || [[rel-directory]]
|-
| [[rel-enclosure|enclosure]] || …indicates that the destination of that hyperlink is intended to be downloaded and cached. || [[rel-enclosure]] || [http://www.apps.ietf.org/rfc/rfc4287.html RFC4287]
|-
| [[rel-home|home]] || …indicates that the <nowiki>[referenced document]</nowiki> is the homepage of the site in which the current page appears. || [[rel-home]]
|-
| [[rel-payment|payment]] || … || [[rel-payment]]
|}

== brainstorming ==
Several rel values are being brainstormed as potential microformats and are thus listed here. If you find you have a use for such semantics in real world examples, consider trying out these values and provide feedback on the respective brainstorming page(s) with your results and experiences.

{| border="1"
|+
! rel value !! summary !! brainstormed in

|-
| [[rel-bibliography|bibliography]] || indicate[s] that the destination of that hyperlink is a bibliography for the current page. || [http://microformats.org/discuss/mail/microformats-discuss/2007-October/010863.html mailing list post, 2007-10-15]

|-
| [[rel-cite|cite]] || indicate[s] that the destination of that hyperlink is an authoritative source or a precedent to the current page. || [[distributed-conversation-brainstorming]]

|-
| [[rel-group|group]] || the referenced document represents a group to which the person represented by the current document belongs || [[group-brainstorming]]

|-
| [[rel-map|map]] || Link to a map. Possibly embedded within an adr, hCard, geo or hCalendar. Parsers {{may}} attempt to parse the URL if it is a link to a known map site (e.g. Geohash, Google Maps, Multimap) and extract co-ordinates and other useful data. || (to [[User:TobyInk|TobyInk]] by email)

|-
| [[rel-member|member]] || the referenced document represents a member of the group represented by the current document || [[group-brainstorming]]

|-
| [[rel-product|product]] || … || [[product-brainstorming]]

|-
| [[rel-profile|profile]] || indicate[s] that the destination of that hyperlink is a metadata profile (e.g. an [[XMDP]] profile) for the current page or portion thereof || [[xmdp-brainstorming]]

|-
| vcalendar-parent || link from an event to a containing event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-child || link from an event to a contained event || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]
|-
| vcalendar-sibling || link from an event to a related event with the same container || [[User:TobyInk/hcalendar-1.1|hCalendar 1.1 draft]]

|}

=== more brainstorming ===
See also:
* [[genealogy-brainstorming]] for some thoughts on possible additional values for family relationships (use existing [[XFN]] [[rel-parent|parent]], [[rel-child|child]], [[rel-sibling|sibling]], [[rel-spouse|spouse]], [[rel-kin|kin]] values first though)
* [[xpn-brainstorming]] for some thoughts on possible additional values for professional relationships (use existing [[XFN]] [[rel-co-worker|co-worker]], [[rel-colleague|colleague]] values first though)

== POSH usage ==
There are numerous rel values used as [[POSH]], both in the wild, whose origins are not necessarily known, nor are their meanings consistent. There are also numerous rel values from external proposals of varying degrees of merit. It is useful to document their existence and summarize their implied meanings/usage intent as research that may be used to perhaps take one or more of them thru the microformats [[process]] if there is both sufficient interest and sufficient in the wild usage.

Note: this list is incomplete, please help complete it from the following sources:

External sources:
* [http://developer.mozilla.org/about/meta Meta Information in DevMo Docs] (DevMo)
* [http://wiki.mozilla.org/Microsummaries Microsummary]
* [http://lachy.id.au/dev/markup/specs/wclr/ Web Communication Link Relationships] (WCLR)
* [http://www.w3.org/MarkUp/Relationships.html W3C Link Relationship values draft] (LRdraft) - from a draft of the HTML spec circa 1991.
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes HTML5 draft] '''Liable to change'''
* [http://wiki.foaf-project.org/Autodiscovery FOAF Project Wiki: Autodiscovery] (FOAF)
* [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]
* [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html Google Blog]

{| border="1"
|+
! rel value !! summary !! origin !! proposal(s)

|-
| [[rel-archive|archive]] || index of archived entries || unknown, perhaps Wordpress open source blogging software || WCLR

|-
| [[rel-archives|archives]] || Provides a link to a collection of records, documents, or other materials of historical interest. || || HTML5

|-
|[[rel-author|author]]||…||unknown || DevMo

|-
| [[rel-canonical|canonical]] || To help search engines disambiguate the same page with multiple representations || Google || Google/Microsoft/Yahoo!

|-
| [[rel-comment|comment]] || … || … || WCLR

|-
| [[rel-contribution|contribution]] || … || … || WCLR

|-
| [[rel-details|details]] || … || (seen on w3c.org news log in a "read more" permalink) || …

|-
| [[rel-EditURI|EditURI]] || … || Seen in WordPress, e.g. [http://www.tom-watson.co.uk/] || …

|-
| [[rel-endorsed|endorsed]] || … || … || WCLR

|-
| [[rel-external|external]] || Indicates that the referenced document is not part of the same site as the current document. || … || HTML5

|-
| [[rel-fan|fan]] || xxxx. || … || [[hcard-user-profile-authoring]]

|-
| [[rel-feed|feed]] || Gives the address of a syndication feed for the current document. || … || WCLR/ HTML5

|-
| [[rel-icon|icon]] || Imports an icon to represent the current document. (Allowed in <code>link</code> only) || … || WCLR/ HTML5

|-
| [[rel-lightbox|lightbox]] || … || ([http://www.google.co.uk/search?q=rel%3D%22lightbox%22 Google search for rel=lightbox in the wild]) || …

|-
| [[rel-made|made]] || … || … || LRdraft

|-
| [[rel-meta|meta]] || … || [http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#transport 1999 W3C RDF syntax REC] || FOAF

|-
| [[rel-microsummary|microsummary]]|| … || … ||[http://wiki.mozilla.org/Microsummaries Microsummary], be aware of: [[page-summary-formats#Issues_2|microsummary issues]]

|-
| [[rel-openid-delegate|openid.delegate]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-openid-server|openid.server]] || … || ([http://www.google.co.uk/search?q=%22rel%3Dopenid%22 Google search for rel=openid.* in the wild]) || …

|-
| [[rel-permalink|permalink]] || … || … || WCLR

|-
| [[rel-pgpkey|pgpkey]] || (see also rel-publickey) || … || [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html], [http://golem.ph.utexas.edu/~distler/blog/archives/000325.html]

|-
| [[rel-pingback|pingback]] || Gives the address of the pingback server that handles pingbacks to the current document. (Allowed in <code>link</code> only) || … || WCLR/ HTML5

|-
| [[rel-prefetch|prefetch]] || Specifies that the target resource should be pre-emptively cached. (Allowed in <code>link</code> only) || … || HTML5

|-
| [[rel-publickey|publickey]] || (see also rel-pgpkey) || … || [http://rasterweb.net/raster/2002/12/12/20021212072812/]

|-
| [[rel-referral|referral]] || … || … || WCLR

|-
| [[rel-related|related]] || … || … || WCLR

|-
| [[rel-replies|replies]] || indicates a continued thread || unknown || [http://www.apps.ietf.org/rfc/rfc4685.html RFC4685]

|-
| [[rel-resource|resource]] || … || … || WCLR

|-
| [[rel-search|search]] || … || unknown || unknown

|-
| [[rel-sidebar |sidebar ]] || Specifies that the referenced document, if retrieved, is intended to be shown in the browser's sidebar (if it has one). || || HTML5

|-
| [[rel-sponsor|sponsor]] || … || … || WCLR

|-
| [[rel-trackback|trackback]] || … || unknown, perhaps open source Movable Type blogging software || WCLR

|-
| [[rel-unendorsed|unendorsed]] || (probably redundant to [[rel-nofollow|nofollow]]) || … || WCLR

|-
| [[rel-up|up]] || Provides a link to a document giving the context for the current document. || …|| HTML5

|-
| [[rel-user|user]] || … || … || WCLR

|-
| [[rel-via|via]] || … || … || WCLR

|}

=== WCLR ===

The WCLR proposal is described by its author (in e-mail, 2007-09-25) as:

<blockquote>
…now effectively obsolete, since HTML5 and Microformats cover all the worthwhile relationships in that already.

These are [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-links.html#linkTypes covered by HTML5 already]:

* permalink -> bookmark
* archive -> archives
* feed
* pingback
* unendorsed -> nofollow

The rest now seem unnecessary.
</blockquote>

Nonetheless, there may be some mileage in using them in microformats, at least until HTML5 is widely available.

== non HTML rel values ==
There are markup languages other than HTML that also have a rel attribute, often based upon the HTML rel attribute.
It is useful to document some of these other languages and their rel values for both reference purposes, and to provide background research for the possible development and re-use of these values in HTML, as [[poshformats]] or [[microformats]]

Sources:
* [[Atom]] [[RFC4287]] specification.
* See http://www.iana.org/assignments/link-relations.html for more.

{| border="1"
|+
! rel value !! summary (from the relevant specification where possible)) !! defining specification

|-
| self || See http://www.rfc-editor.org/rfc/rfc4287.txt || [[Atom]]

|-
| ... || ... || ...

|}

== dropped ==
The following rel values were in earlier version(s) of specification(s) and it is presumed by their absence from the most recent version of the respective specification(s) that they have been deprecated or obsoleted. Use of them could be considered a bit more standard than just POSH, although you may wish to research why such values were omitted from latter specifications before using them. If you do discover the reasoning, please add a short statement or link to thereof into the appropriate place in the following table.

In general, you {{should not}} use any dropped values.

In addition, if any such values have been superceded by standard values (see the first table on this page), then you {{must not}} use the dropped versions.

Sources:
* [http://www.w3.org/MarkUp/html3/ HTML3] (HTML3) - has been superceded by [http://www.w3.org/MarkUp/Wilbur/ HTML 3.2] - which itself has been superceded by [http://www.w3.org/TR/REC-html40 HTML 4.0] - which itself has been updated by [http://w3.org/TR/html401 HTML 4.01], commonly referred to as "HTML 4" in this wiki and other places.)
* [http://www.w3.org/TR/relations.html Proposed HTML 4.0 link types] (HTML4dropped) - obsoleted/superceded by the HTML 4.0 Recommendation. Any values that were in the "Proposed HTML 4.0 link types" document but didn't make it into the HTML 4.0 Recommendation were thus explicitly dropped and should be avoided.

{| border="1"
|+
! rel value !! summary !! defining specification !! why dropped
|-
|[[rel-banner|banner]]||Was used to reference another document to be used as banner for this document (i.e. a form of "include" statement).|| HTML3 ||unknown
|-
| [[rel-begin|begin]] || identifies the author-defined start of a sequence of documents of which the current document is a node.
|| HTML4dropped||unknown
|-
| [[rel-biblioentry|biblioentry]] || identifies a bibliographic entry || HTML4dropped||unknown
|-
| [[rel-bibliography|bibliography]] || identifies a bibliography || HTML4dropped||unknown
|-
| [[rel-child|child]] (obsolete/superceded) || the target document is a hierarchical child, or subdocument, of the current document|| HTML4dropped||unknown
|-
| [[rel-citation|citation]] || the target is a bibliographic citation || HTML4dropped||unknown
|-
| [[rel-collection|collection]] || the target document is an collection that contains the current document || HTML4dropped||unknown
|-
| [[rel-definition|definition]] || identifies a definition of a term || HTML4dropped||unknown
|-
| [[rel-disclaimer|disclaimer]] || identifies a hypertext link to a legal disclaimer || HTML4dropped||unknown
|-
| [[rel-editor|editor]] || identifies a hypertext link to an editor || HTML4dropped||unknown
|-
| [[rel-end|end]] || identifies the author-defined end of a sequence of documents of which the current document is a node. || HTML4dropped||unknown
|-
| [[rel-first|first]] || synonym for <code>begin</code> || HTML4dropped||unknown
|-
| [[rel-footnote|footnote]] || the anchor is a footnote marker and the target is a footnote || HTML4dropped||unknown
|-
| [[rel-last|last]] || synonym for <code>end</code> || HTML4dropped||unknown
|-
| [[rel-navigate|navigate]] || the target document contains information such as a image map that will help users to gain a sense of how and where to found information || HTML4dropped||unknown
|-
| [[rel-origin|origin]] || synonym for <code>top</code> || HTML4dropped||unknown
|-
| [[rel-parent|parent]] (obsolete/superceded) || the target document is the hierarchical parent, or container, of the current document|| HTML4dropped||unknown
|-
| [[rel-pointer|pointer]] || the target is a pointer to the real target. This value can be used by a user agent to perform a pre-fetch of the specified target for evaluation until the real target is reached || HTML4dropped||unknown
|-
| [[rel-publisher|publisher]] || identifies a hypertext link to a publisher || HTML4dropped||unknown
|-
| [[rel-sibling|sibling]] (obsolete/superceded) || the target document is a child of a common parent, or a hierarchical peer of the current document|| HTML4dropped||unknown
|-
| [[rel-top|top]] || the target document is the logical top node of the tree (see also <code>begin</code>) || HTML4dropped||unknown
|-
| [[rel-trademark|trademark]] || identifies a hypertext link to a trademark notice || HTML4dropped||unknown
|-
| [[rel-translation|translation]] || the target is a translation to another language || HTML4dropped||unknown
|-
|[[rel-up|up]]||When the document forms part of a hierarchy, this link references the immediate parent of the current document.||HTML3||unknown, but proposed for re-introduction in HTML5
|-
| [[rel-urc|urc]] || identifies a Universal Resource Citation || HTML4dropped||unknown
|-
|}

== rejected ==
Some rel values have been proposed and rejected. They are listed here to make that explicit. Authors {{must not}} use rejected rel values.

Source: [[rejected-formats]].

{| border="1"
|+
! rel value !! origin / proposal !! why rejected
|-
|[[rel-pavatar|pavatar]] || [http://pavatar.com/ pavatar] || [[rejected-formats#Pavatar]]
|-
|}

== unspecified ==
Some rel values have been added to this page perhaps in one of the tables above, but no examples, nor an actual specification explicitly stating that the value(s) should be used in the HTML4 'rel' attribute could be found. They are listed here in the hopes someone can discover more specific/precise URLs to examples or specifications about them (preferably both). Until such precise URLs to examples/specs are provided, the values can be treated as they are purely theoretical and thus of little interest.

{| border="1"
|+
! rel value !! summary !! source
|-
| schema.DC || … || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]

|-
| schema.DCTERMS || … || [http://www.dublincore.org/documents/dcq-html/ Dublin Core]
|-
|}

Notes:
* Dublin Core. This search may help: [http://www.google.co.uk/search?as_q=rel%3Dschema.*&hl=en&num=10&btnG=Google+Search&as_epq=&as_oq=&as_eq=&lr=&as_ft=i&as_filetype=&as_qdr=all&as_occt=any&as_dt=i&as_sitesearch=http%3A%2F%2Fdublincore.org&as_rights=&safe=images].
** '''examples from that search only use invisible <code><link href></code> element'''. At first glance it appears the results from the search show only uses with the invisible <code><link href></code> element which is not ideal for content relationships. Content relationships should be user visible and thus uses with <code><a href></code> are strongly preferred.
*** [http://www.ietf.org/rfc/rfc2731.txt RFC2731] defines <code>rel="schema.AC"</code> and <code>rel="schema.RC"</code> with the pattern <code>rel="schema.PREFIX"</code> as a syntax for defining namespaces for use in meta[@name], *[@rel], *[@rev] and (as per eRDF) *[@class] attributes. A link to a Dublin Core metadata schema is generally not suitable for end users, so <code><link href></code> appears to be more appropriate than <code><a href></code> for those that use Dublin Core metadata schemas.
** '''proposal to use in content currently only theoretical'''. Thus unfortunately the use of Dublin Core in user visible content like <code><a href></code> appears to be strictly theoretical. See [http://microformats.org/discuss/mail/microformats-discuss/2008-January/011445.html microformats-discuss/2008-January/011445.html] for a proposal to use Dublin Core in user visible content.

== tools ==
See [[implementations]].

== related ==
{{rel-related-pages}}
* [[elemental-microformats]]
* [[existing-class-names]]

Template:NewMarker-fr

2009-01-08T10:09:50Z

Brian: Reverted edits by RolboRotro (Talk) to last version by AndyMabbett

nouveau !

User:RobCrowther

2009-01-08T10:09:49Z

Brian: Reverted edits by OrdelDrond (Talk) to last version by RobCrowther

[http://www.dotrob.com/cv.html Rob Crowther], a web developer from London, UK. Currently employed at [http://www.serviceworksglobal.com Service Works Global], my 'spare time' pursuits are mostly online at [http://www.boogdesign.com boogdesign.com].

{{public-domain-release}}

digital-signatures

2009-01-08T10:09:47Z

Brian: Reverted edits by CrelnOvare (Talk) to last version by Brian

<h1>Digital Signatures</h1>

This page documents a discussion about digitally signed Microformatted data.

__TOC__

== Introduction ==

Defined Microformats such as [[hCard]], [[hCalendar]] or [[hReview]] can be formatted to include a digital signature. This document is a definition of a proposed format for the digital signing of Microformatted data. As this format is content agnostic it can be used to build compound signed Microformats from all existing and future Microformats.

In a broad sense, this format (sometimes referred to as hSig) aims to protect the authenticity and authority of content that has been made machine-readable through the use of semantic annotations (e.g. Microformatted data).

== Format ==

The structure and names are chosen in the style of the W3C Recommendation for XML-Signature Syntax and Processing [http://www.w3.org/TR/xmldsig-core/], the existing XML structure for digital signatures.

<pre><nowiki>
// Proposed format with example values
....
<div class="hsig">
<a class="canonicalizationmethod url"
href="http://www.w3.org/TR/2001/REC-xml-c14n-20010315">
</a>
Signed using RSA.
Hashed using SHA1.
<abbr class="manifest" title="vcard:fn,vcard:email">
Name and eMail signed.
</abbr>
<abbr class="digestvalue" title="57c8105e6d944[...]a14c4cea7f53">
The Hash.
</abbr>
<abbr class="signaturevalue" title="7m6NS6ANCa[...]Kl42Rr+Pfw==">
The signature.
</abbr>
<abbr class="keyinfo" title="X509">
I have an X509 certified key.
</abbr>
<abbr class="keyvalue" title="-----BEGIN CERTIFICATE----- E693c4[...]
[...]MIICIzCCAc2gAgANB-----END CERTIFICATE-----" >
My X509 certificate containing my public-key.
</abbr>.
</div>
...
</nowiki></pre>

There are several differences between this format and the original XML Signature structure:
* Most notably, the proposed Microformat is less nested. For example, instead of placing digestmethod and digestvalue into a sub-container called reference, the structure was flattened.
* Fields were added which allow more room for capturing different signature formats. For example, in addition to flattening keyinfo keyvalue was added, which stores information about the key.

== Integration of signature ==

To bind the signature to existing Microformatted content, there are three possibilities (again conforming to the use of XML Signatures).

=== Enveloping signature ===
For an enveloping signature the hsig container contains the Microformatted content that is signed. The content's sub-properties are referenced in the manifest using the Microformat's name followed by the sub-property, separated by a colon (e.g. vcard:fn).
=== Enveloped signature ===
In the case of an enveloped signature the hsig container is contained within the Microformatted micro content that is signed. Again the micro content's sub-properties are referenced in the manifest using the Microformat's name followed by the sub-property, separated by a colon (e.g. vcard:fn ). Figure 2 shows this case.
=== Detached signature ===
This case is needed when a signature shall cover more than one micro content from that page. The micro contents that are part of the signature are then referenced using an <object> or <a> HTML element inside the hsig -section. In this case the micro content needs an id, which is then used for reference instead of the Microformat's name. This case is the most complex one and is not further elaborated for brevity.

<pre><nowiki>
// Signed content using an enveloped hsig

<div class="vcard">
<h1 class="fn">SVS - Office</h1>
<a href="mailto:svs-office@informatik.uni-hamburg.de" class="email">Email us.</a> 
Tel.: +49 40 42883 - 2510 
Fax: +49 40 42883 - 2086 
Room: F-631 
<div class="hsig">
<abbr class="manifest" title="vcard:fn, vcard:tel, vcard:email">
This
</abbr>
<abbr class="digestvalue" title="57c8105e6dd944[...]a14c4cea7f53">
content
</abbr>
<abbr class="signaturevalue title="7m6NS6NCa[...]Kl42Rr+Pfw==">
is signed.
</abbr>
<abbr class="digestmethod" title="SHA1">It was hashed using SHA1.</abbr>
<abbr class="signaturemethod" title="RSA">And signed using RSA.</abbr>
<abbr class="keyvalue" title="-----BEGIN CERTIFICATE----- [....]
[...] CIzCCAc2gAgA-----END CERTIFICATE-----" >
My X509 public-key certificate.
</abbr>.
</div>
</div>
</nowiki>
</pre>

== Manifest and sig generation details ==

In our prototype, the manifest is stored under the class name manifest (see above). The manifest is also embedded into the signature this aids security. The manifest first identifies for which Microformat structure the signature has been generated.

After the Microformat identifier, the sub-properties are expressed using their class names (e.g. vcard:fn). Hashes are computed over each sub-property in the manifest and the manifest itself. The hahses are then concatenated in the order they appear in the manifest with the manifest's hash first. This concatenation of hashes is hashed again and stored in digestvalue.

Finally, it is digitally signed using a digital signature algorithm (specified in signaturemethod) and the value is stored in signaturevalue. To allow for an easier verification of the signature and to aid authentication of the signer, the key can be added to hSig as keyvalue. The key could be anything ranging from a PGP Key to an X509 Certificate from a CA. Exactly what key information is appended should be specified in keyinfo even if it might be deductable from the values of the key itself or the signing method used.

== References ==
=== Normative References ===
* [[hcard]]
* [[hCalendar]]

=== Informative References ===
* [http://www.informatik.uni-hamburg.de/SVS/personnel/henrich/hsig.php A Microformat for Digital Signatures]

=== Related pages ===
* [[digitalsignature-brainstorming]]
* [[digitalsignature-examples]]

events/2007-01-18-sf-microformats-dinner

2009-01-08T10:09:45Z

Brian: Reverted edits by ChipaScaer (Talk) to last version by Brian

= January 2007 San Francisco Microformats Dinner =

One of several microformats [[events]].

Where: Nova. 555 Second St San Francisco, CA 94107. (415) 543-2282. has wifi. can handle perhaps up to about 15 people.

When: Thursday January 18th, 6pm-...

Tags: sanfrancisco soma sopa southpark 2ndstreet nova microformats dinner microformatsdinner microformatsdinnersf microformatsdinnersf20070118 upcoming:event=142548

Who (food prefs).

# [http://tantek.com/ Tantek Çelik] (vegetarian or fish options)
# [http://theryanking.com/ Ryan King]
# [http://meyerweb.com/ Eric Meyer] (not spicy)
# William Lawrence (vegetarian)
# Kevin Marks (eats anything)
# Ben West
# Derrick Pallas
# [http://www.flickr.com/people/nhanusek/ Nicole Hanusek]
# Steve Cohen
# Barrett Weisshaar (will eat his co-workers if necessary)
# Chris Messina
# Tara Hunt
# James Craig

Upcoming: http://upcoming.org/event/142548

Photos: http://flickr.com/photos/tags/microformatsdinnersf20070118

hresume-issues

2009-01-08T10:09:39Z

Brian: Reverted edits by BastaCadom (Talk) to last version by GeoffreySneddon

<h1> hResume issues </h1>

These are externally raised issues about [[hresume|hResume]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec. Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/log/ Tantek]

See related [[hcalendar-issues]].
See related [[hcard-issues]].

__TOC__

== Issues ==

* {{OpenIssue}} 2007-10-02 raised by [[User:JeffMcNeill|jeffmcneill]].
*# ''Support for Awards and for Service sections are not currently implemented''
*#* I have attempted to use the Experience tag, however am unclear whether this will break things. Please see [http://jeffmcneill.com/microformats/hresume-jeffmcneill.html the example here]. --[[User:JeffMcNeill|jeffmcneill]] 04:09, 2 Oct 2007 (PDT)

* {{OpenIssue}} 2007-06-21 raised by [[User:Steve_Ganz|Steve Ganz]].
*# ''rel-tag can be difficult to implement for "skill" ''
*#* In Draft, version 0.1 it is required that each "skill" be marked up with rel-tag. While this is a good idea, and easy to do for individuals, it poses some challenges in the real world for large publishers of user generated resume data. If rel-tag was optional for "skills", it would be easier to implement.
*#* +1, expecting a resume author to link out to a hypothetical tagspace is an unnecessary barrier to entry. In reality authors end up linking to places like WikiPedia, which is not a real tagspace as defined in rel-tag. We should look at a more complex skill format for both this and the issue below opened by NTollervey. --[[User:CiaranMc|Ciaran McNulty]]

* {{OpenIssue}} 2007-01-04 raised by [[User:NTollervey|ntoll]].
*# ''With regard to the "skill" attributes in a resume: often skills have an indication of the level of attainment - be it as a descriptive "tag" or a duration denoting the length of experience of the referenced skill. In fact, abstracting out a "skill" microformat might be useful for re-use in the job-listing (Vacancy?) microformat. That way, job requirements can be married to CVs. Although not a job-site, I like Sourceforge.net's skill inventory feature (that captures both a level and length of experience) although I think its implementation is horrendous.''

* {{OpenIssue}} 2006-10-19 raised by [[RyanKing]].
*# ''There's currently no way to say 'present' in hCalendar''
*#* Many job experience listings will include jobs that the person is presently working at. Ciaran McNulty [http://microformats.org/discuss/mail/microformats-discuss/2006-October/006477.html correctly pointed out] that a blank DTEND does not indicate that the event is still ongoing. We need to find an easy way to make this work in hResume.
*#* Any solution should also be a valid hCalendar, which makes things even more difficult. One possible solution would be to use an event without a DTEND for the current period of employment but have some extra class that indicates that within the semantics of hResume it's an ongoing event and let the hCalendar version just indicate the start of the employment. --[[User:CiaranMc|Ciaran McNulty]]
*#* Although not the best solution, for the time being, a date far ahead in the future (e.g., 2049-12-31) may have practical use (Note: Google Calendar can handle up to but not including year 2050) -- --[[User:Csarven|Sarven Capadisli]] 21:34, 18 November 2008 (UTC)
*#* I tend to just use the current date for dtend: anything else seems semantically wrong as an abbr of "present". [[User:GeoffreySneddon|GeoffreySneddon]] 21:46, 19 November 2008 (UTC)

* {{OpenIssue}} 2006-10-19 raised by [[User:Steve_Ganz|Steve Ganz]].
*# ''There's currently no way to distinguish different hCard types in hResume''
*#* In Draft, version 0.1 it is specified that a parent element of <code>address</code> should be used to the distinguish an hCard as the subject's contact info. This proves problematic to implement because <code>address</code> cannot contain block level elements. To avoid sacrificing semantic value by restricting the child elements of an hCard to inline elements, we need to settle on an alternate method to classify a subject's hCard as thier contact info.
*#* In any given experience there may be one or more hCards. One which would be the subject's hCard for that experience and the other for a supervisor or manager, etc. We need a way to distinguish different hCards in a given experience.
:::* Agreed, when adding my references in hCard to the bottom of my hResume it became apparent there was no way I could mark 'my' hCard as the one belonging to the subject of the hResume. Perhaps @class="hcard subject" as a child of the hResume? [[User:CiaranMc|Ciaran McNulty]]

== Template ==

{{issues-format}}

== Related Pages ==
{{hresume-related-pages}}

geo-elevation-examples

2009-01-08T10:09:37Z

Brian: Reverted edits by OudarOloli (Talk) to last version by RyanKing

=Elevation examples=

Examples of published elevations (also known as "altitude" or "height") to support the proposed [[geo-extension-elevation|elevation extension]] to the [[geo|Geo]] microformat.

== Contributors ==
* [http://www.aetherworld.org/ Alexander Graf], [http://www.deri.at/ DERI Innsbruck]
* [[User:AndyMabbett|Andy Mabbett]]

==Examples==

=== State High Points ===
*http://www.waypoint.org/gps2-list210.html

<pre><nowiki>

<tr>
<th>Abbr</th>
<th>Date</th>
<th>State</th>
<th>Location</th>
<th>Altitude</th>
<th>Lat/Long</th>
<th>GPS Coords</th>
<th>Topo quad</th>

</tr>

<tr>
<td>CA</td>
<td><a href="./batting.500/">7/2/2001</a></td>
<td><a href="./batting.500/">California</a></td>
<td>Mount Whitney</td>
<td>14,494</td>
<td>36° 35'N, 118° 17'W</td>

<td>36° 34.721'N, 118° 17.466'W</td>
<td>CA Mt. Whitney 1:24,000, Mt. Langley 1:24,000</td>
</tr>
</nowiki></pre>

=== Nepal GPS Waypoints ===
*http://gpsnepal.com/waypoint.php?trek=everest

=== Waypoints Netherland ===
*http://www.way-points.nl/waypoints/rubriek.asp?cat=2&type=rubriek

===Misc===
* Used by Wikipedia e.g. [http://en.wikipedia.org/wiki/Avers Avers]; [http://en.wikipedia.org/wiki/List_of_volcanoes_in_Argentina volcanoes in Argentina]; [http://en.wikipedia.org/wiki/Special:Whatlinkshere/Template:Infobox_Telescope telescopes]
*Used (as "height") by PoI66 in GPS tracks, e.g [http://www.poi66.com/maps/show_earth.php?album=wip&lat=35.58756&lon=27.06803&extent=0.1&title=Beach%20van%20Lefkos%20]
*Used by Great Circle Mapper, e.g [http://gc.kls2.com/airport/BHX BHX]
*Used by UK Govt. Met Office
**as "AMSL" = height Above Mean Sea Level e.g. [http://www.metoffice.gov.uk/climate/uk/averages/19611990/sites/penkridge.html Penkridge Weather station]
** as "Altitude above mean sea level" e.g. [http://www.metoffice.gov.uk/weather/uk/wm/coleshill_latest_weather.html Coleshill Latest Weather]
*[http://www.gpsvisualizer.com/ GPS Visualizer] - plots waypoints with altitudes as a [http://www.gpsvisualizer.com/profile profile] ([http://www.gpsvisualizer.com/examples/profile_biking_uc.gif example profile])

== See Also ==
{{geo-related-pages}}

hcard-user-interface

2009-01-08T10:09:34Z

Brian: Reverted edits by AcelcOzell (Talk) to last version by Brian

<h1> hCard User Interface </h1>
{{TOC-right}}
This page is for techniques and issues surrounding [[user-interface|user-interfaces]] to author, publish, and display [[hcard|hCards]].

== Authors ==
* [http://allinthehead.com/ Drew McLellan]
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]

== Single Input Field for Names ==
When capturing name data that is later to be presented as a hCard, it's important that the data is collected at the highest fidelity possible. As not all names are suitable for hCard's implied-n optimisation (and therefore can't be output as <code>fn</code>, with <code>n</code> omitted), capturing component parts of the name individually enables the proper construction on <code>n</code> when generating the hCard.

Sometimes, however, constraints require a name be collected with a single field. Once such example is common blog CMSs (WordPress, TextPattern) that use a single database field to store the name against each post comment. In such cases it is always desirable to find a way to collect the name with higher fidelity. However, if this simply cannot be done, the implementer could chose to attempt to best-guess the component parts of the name to form a valid <code>n</code>.

One suggested 'best-guess' algorithm might be:

# If the name is one word, attempt [[hcard#Implied_.22nickname.22_Optimization|implied nickname optimization]]
# If the name is two words, attempt [[hcard#Implied_.22n.22_Optimization|implied n optimization]]
# For three or more words
## Perform a lookup against known sub-name combinations (e.g. 'Sarah Jane', 'Vander Wal')
## Apply the grammar "(honorific-prefix) given-name additional-name(s) family-name (honorific-suffix)"

The principal behind this suggestion is that it's better to make a good guess and potentially miscategorise an ambiguous name component than to generate an invalid hCard.

== Additional user interface ==
Some examples of additional user interface for hCard. Note that most of these actions should be applicable to all instances of the microformat on the page at once (e.g. export all contacts), of for a selection of instances (e.g. export selected contacts), or one just one specific instance (e.g. export contact XYZ).

=== address book integration ===
* "Add to Address Book" (convert the hCard to a vCard (.vcf) and pass it onto the OS to automatically open/incorporate into the user's preferred local address book application)
* add to Gmail, Yahoo Mail, Hotmail address book (etc.)
=== desktop to phone transfer ===
* send to Bluetooth, for quick transfer of contact info from the web to a cell phone.
* display contact details in an on-screen or downloadable [[semacode]], [[qr_code]] or other [[2d_barcodes]] (to allow them to be read by mobile devices)

=== telephony integration ===
* If a <code>tel</code> (phone number) having type <code>home</code>, <code>work</code> or <code>cell</code> is present, provide options to dial it (NB applies to one number at a time only; except for possible conference-call uses) directly, or via
** built-in modem
** bluetooth command to a paired device (e.g. cell phone)
** default telephony app (e.g. skype-out)
* If a <code>tel</code> (phone number) having type <code>home</code>, <code>work</code> or <code>cell</code> is present, provide options to send MMS:
**directly
**using on-line service
** bluetooth command to a paired device (e.g. cell phone)
=== fax integration ===
* If a <code>tel</code> of type <code>fax</code> is present, provide options to send a fax to it via:
** efax online service
** built-in fax modem
=== birthday planning ===
* If a birth-date is present, treat it as a recurring hCalendar event.
=== address canonicalization ===
* Given a postal code (or other partial address) fetch the full, canonical postal address for the relevant authority's website (e.g. [http://postcode.royalmail.com/portal/rm/postcodefinder]). If no country is defined, used the user's locality as the default.

=== data export ===
* export as text/ [[csv|comma-separated-variables]] (CSV) to allow editing, sorting and/ or import into spreadsheets/ databases, etc. (or concatenate to existing file)

==see also==
{{hcard-related-pages}}

User talk:JamesCraig

2009-01-08T10:09:32Z

Brian: Reverted edits by EltliOucna (Talk) to last version by AndyMabbett

Hi,

Welcome to the microformats wiki. I [http://microformats.org/wiki?title=hcard-issues&diff=next&oldid=13735 moved your issues about country-codes to the hCard issue page]. "[[adr]]" is a subset of [[hCard]], and "issues" pages are used for raising such matters. [[User:AndyMabbett|Andy Mabbett]] 01:24, 25 Feb 2007 (PST)

faq-ja

2009-01-08T10:09:29Z

Brian: Reverted edits by ViracCacna (Talk) to last version by Brian

<h1> Microformats FAQ </h1>

microfotmatsについてよく聞かれる質問とその答えのページです。 For frequently asked questions from the [[press]], see [[press-faq]].

If you're looking for a microformat for marking up FAQs, see [[question-answer]].

__TOC__

== Wiki特有の質問 ==
===Q: ''ユーザー名はどうやって作りますか? どのようなユーザー名が望ましいですか?''===

A: まずは、 http://en.wikipedia.org/wiki/Wikipedia:Username を読んでください。また、ユーザー名としては、ペンネームやハンドルなどよりも本名の方が好まれます。本名を用いると、より高い透明性や責任を伴うと考えられるからです。さらに、ユーザー名の最初の文字は大文字である必要があります。これは登録の際に最も問題になることの一つです。ユーザー名としては、例えば「RyanKing」のようにあなたの氏名のWikiCaseバージョンはどうでしょうか?

== Email list ==
===Q: ''I've joined the discussion mailing list but am not seeing my replies anywhere. Why?''===

A: There is no moderation on microformats-discuss, but it only accepts posts from subscribers. You MUST post to microformats-discuss using the email address you used to subscribe.

===Q: ''What does "The message's content type was not explicitly allowed" mean?'' ===

A: Please go read [http://microformats.org/mailinglists-policies/ mailinglists-policies]. In particular note:
<blockquote>
'''No HTML or RTF e-mail''' period, end of story, full stop. Your mail client should let you configure it so you can send plain text messages. Make use of this ability or else there are no guarantees that anyone will be able to read your email.
</blockquote>
The mailing lists are set up to automatically reject email that is sent as text/html. Thus please configure your email client to send plain text (text/plain) email.

== microformatについての基本的な質問 ==
===Q: ''What does ''xxx'' mean?''===

A: See our [[glossary]].

===Q: ''Who uses microformats?'' ===

A: See a list of [[notable-users|some notable users]]; [[examples-in-wild|other microformat users]] and [[implementations|tools using microformats]].

===Q: ''When should I use a microformat? What are they for?"===

A: You are writing some HTML that contains useful human-readable information (such as a piece of contact information). You say to yourself: I would like to mark this up with some classes now for styling. You look up the relevant microformat, and you
pull in the standard names. You don't have to make your own up, and now your page is machine-readable too. Bonus!

Microformats are designed to make the data you already publish for humans available to machines. It allows applications as simple as cut-and-paste or as complex as a search engine to use your data effectively.

===Q: ''microformatsは(X)HTMLに依存していますか?''===

A: Microformatsは埋め込んで使うものです。(X)HTMLやRSS、Atomなどに埋め込むことができます。

===Q: ''microformatsは素晴らしいと思います。私にも何か協力できることがありますか?''===


A: Take a look at [[get-started]] for how to implement microformats yourself, and the [[to-do]] list for things to help out with. See http://microformats.org/discuss to see some ways to join the conversations about microformats.

===Q: ''I'd like to make a donation to the microformat cause. How can I do this?''===

A: Thank you for your willingness to support microformats. We've only recently started this site and have decided that while we are figuring out exactly how to accept donations, we will be passing along donations to other good causes. Please consider donating to another cause like Red Cross, perhaps directed to help victims of recent natural disasters.

===Q: ''microformatsにはどのような実装がありますか?'' ===

A: [[implementations-ja|実装]]ページを見てください。

===Q: ''Which microformats should I implement?''===

A: Chances are you that your website already has data very similar to several microformats. For example, you probably have people and/or their contact information somewhere. That information could be marked up with [[hcard|hCard]], see the [[hcard-authoring|hCard authoring]] page for step by step instructions. If you are publishing press releases, try using [[hatom|hAtom]].

===Q: ''Do you have any link badges I can add to my website/blog?''===

A: There are some [[buttons]] but we can certainly use more! Please contribute what you come up with!

===Q. ''Are there any tools that support microformats?''===

A. Yes...tons... [[implementations]].

===Q. ''Is there a way to indicate that a given web page contains markup that conforms to one or more microformats?'' ===

A. The HTML HEAD element's '<code>profile</code>' attribute alerts applications to the potential presence of microformats. The [http://www.w3.org/TR/1999/REC-html401-19991224/struct/global.html#h-7.4.4.3 W3C HTML Specification] describes more about the profile attribute, and the [http://gmpg.org/xmdp/description XMDP description] documents how it is used.

===Q. ''What about using new URI schemes instead of class names, e.g. for geo information?''===

A. In general, it is more work, and less content-publisher friendly, to ask publishers to use URI schemes instead of class names.

Authors aren't publishing links to geo information.

They're publishing *visible text* of [[geo]] information.

So the easiest thing to do, for the author, is to leave it as visible text.

Thus, it makes the most sense to do the simple thing of just wrapping that
visible text with a little bit of markup, rather than asking the author to
move (or copy) it into an attribute, which may or may not require a
reformatting of the data as well.

It would make sense from a usability persepective to hyperlink geo information to a maps page or something, so that clicking it actually does something. If you forced them to use a hypothetical "geo:" protocol instead, then that would interfere, since you can only hyperlink something to one destination.

===Q: ''Who controls microformats?''===

A: An open community. Microformats are open standards licensed under Creative Commons Attribution. Much of the work here was begun on [http://developers.technorati.com/wiki Technorati's Developer Wiki], but Technorati has since divested control of these microformat standards to the open community here. The microformats.org domain is registered to Rohit Khare(see [http://whois.uberdose.com/microformats.org Whois microformats.org]), CommerceNet is graciously hosting the servers, but claims no control over microformat standards. Anyone may follow the established [[process]] and contribute towards the development of microformat standards.
Any required [[governance]] of the microformats IRC channel, wiki, and mailing lists (and very little ''has been'' required) is discussed by a group of volunteer administrators, who are listed on that page.

===Q: ''Who is the registrar for microformats?''===

A: There is no central registry. Microformats are registered in a distributed manner using profiles. For more information on profiles see http://microformats.org/wiki/profile-uris and http://gmpg.org/xmdp/

Conflicts and interoperability are managed through social processes rather than a formal registry. Current microformat profiles can be found at http://gmpg.org, http://w3.org, and http://microformats.org.

===Q: ''So multiple microformats with the same name can be valid?''===

A: Yes. The community at microformats.org can hopefully play a role in determining which is preferred by bringing interested folks together in one place and helping them resolve that question. As long as each microformat maintains a valid profile, each can be used effectively.

===Q: ''How do I validate my microformated content?''===

A: Currently there is no automatic general-purpose validator for microformats (See [[to-do#for_all_microformats|To Do - for all microformats]]). There are however some microformat-specific tools listed on the [[implementations]] page which can help with validation. [https://addons.mozilla.org/firefox/4106/ Operator] does a good job of compliant parsing for microformats in general. For [[hcard|hCard]], try the [http://feeds.technorati.com/contacts/ Technorati Contacts Feed service]. For [[hcalendar|hCalendar]], try the [http://feeds.technorati.com/events/ Technorati Events Feed service]. Also, posting your examples to the [http://microformats.org/discuss microformats-discuss mailing list], and adding them to the respective examples/implementations sections/pages will very often get folks from the community to review and validate them for you.

===Q: ''How do microformats breach language barriers?''===
'''Would we have to "force" non-English speaking web page developers to use something like class="name" (as opposed to "namen" or "nom") for their productions to be properly indexed by agents?'''

A: Yes, but that's no different to using English words like "class", "span" or "head". This was briefly discussed on the microformats-discuss list most recently as "Language Maps" but has been raised before that. Some folks have raised the issue that microformats use English names for properties, and they would like alternate (non-English) names in other (natural) languages, and perhaps try to establish a mapping between them. As microformats property names are based on existing standards (see [[process]], and [[naming-principles]]), this is another problem that is far outside the scope of microformats. As Ryan King put it, this is a pre-existing (unsolved) "problem" with English-based HTML, the English-based CSS, the English-based HTTP and so on. Note that this is NOT about the internationalization of the content and data itself - which is of course an excellent goal, advocated and promoted by microformats and the standards they are based on (e.g. W3C, IETF). This is purely about the names of the properties (and enumerated values) in the formats. See also [[internationalization]].

===Q: ''How come microformats sometimes to linger as Drafts even though they seem usable?'' ===

A: [http://microformats.org/wiki/faq#Q:_Who_controls_microformats.3F Tantek] went over this at the recent [http://2007.sxsw.com/interactive/programming/panels/?action=show&id=IAP060234 The Growth and Evolution of Microformats] panel at [http://en.wikipedia.org/wiki/South_by_Southwest SXSW]. He conveyed that it was important to have a basic software implementation -- even an experimental one -- before moving a format from Draft to Specification. It can sometimes be hard to recognize subtle inconsistencies within a format by eye; however, in the process of implementing a format-reader in code, inconsistencies (if any) can become much more noticeable (due to [[dry | DRY / Don't Repeat Yourself]], among other programming best practices). Then, once such a tool has been created (in effect, confirming the programmability of the format), it can be transitioned to a Specification (so as to encourage other machine-based implementations).

== 新しいmicroformatsの作成や提案について ==

===Q. ''I would like to author a new microformats open standards specification for my site/business. How do I get started?''===

A. The first thing to do before attempting a new microformat open standard is to make as much use of [[POSH]] and existing [[microformats]] open standards as possible in whatever site you are looking to mark up with your new microformat, as a way of learning what is left to be done. That is, at a minimum first:
* Mark up all people and organizations as [[hcard|hCards]].
* Mark up all events and time based things as [[hcalendar|hCalendar]] events.
* Mark up all reviews as [[hreview|hReviews]].
* etc.
Then join the microformats [http://microformats.org/discuss discuss list], and ask folks what they think of your use of the microformats and if it can be improved.

From that experience you will then be able to figure out what is left to be specified. Otherwise it is too hard to approach the "whole problem".

Once you have completed that, take a look at the microformats [[process]] for how to walk through the steps of creating a new microformat, and note the specific problem you are trying to solve to the microformats-discuss list. This will help you find more people to help you solve the problems you are trying to solve.

===''Q 過去に提案されたmicroformatsのアイデアにを知りたいのですが、どうすればいいですか?''===

A. 提案されて却下されたmicroformatsのリストがありますので、それをチェックしてください。
* [[rejected-formats]]

===Q. ''What if I can't find real-world examples of a standard I'd like to propose?''===

A. If we can't find real-world examples of the '''types of data''' a proposal would address, it's probably not suitable for a microformat. If we only can't find real-world examples of the '''specific markup''' a proposal would use for that data, however, that's not really a problem. It's actually the lack of such standard markup in real-world publishing around a specific problem that suggests the need for increased consensus.

== それぞれのmicroformasに関する質問 ==
個別のmicroformatsに関する質問については、それぞれのFAQを見てください。
* [[hatom-faq]]
* [[hcalendar-faq]]
* [[hcard-faq]]
* [[hreview-faq]]
* [[rel-faq]]
* [[rel-tag-faq]]
* [http://gmpg.org/xfn/faq xfn-faq]
* [[xfolk-faq]]
* [[xmdp-faq]]
* [[xoxo-faq]]

== Class interactions ==

===Q. ''ページスタイリング上の問題が発生するようなclass名はありますか?''===

A. あるかも知れません。ただ、仮に問題が発生したとしても、文脈セレクタを用いることで容易に回避できるでしょう。

===Q. ''How does the use of class values for semantics interact with the use of class values for attaching CSS styles?''===

A. The class attribute takes a space separated set of class names [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 HTML4 reference]. Thus both author and microformat defined class names may be used in the same class attribute. In addition, microformat class names provide the author with a consistent set of class names to use for styling. If the author is already using using specific class names, they can continue to do so, and include microformat class names. If the author is already using a class name that happens to also be a microformat class name, then the author may want to consider using contextual CSS class selectors to make sure that avoid any unintentional styling effects.

See also:
* [http://tantek.com/log/2002/12.html#L20021216 A Touch Of Class]
* [http://tantek.com/log/2004/07.html#classmeaningnotshow Class For Meaning Not For Show]
* [http://www.meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competant Classing], by Eric Meyer for discussion of choosing class names in (X)HTML
* [http://www.microformats.org/blog/2005/10/19/more-than-styling/ Class attributes are about more than styling] - Ryan King dispells common misconceptions about the ''HTML'' class attribute.

== <code><div></code>と<code></code>のセマンティクス ==

===Q. ''Is it semantically meaningless to use divs?'' ===

A. Yes, both <code><div></code> and <code></code> have nearly no semantics. <code><div></code> can be used to represent a "division" of the page content. Similarly <code></code> can be used to reperesent that that "span" of text has some meaning, but the specifics of what that meaning is undefined by the <code></code>.

===Q. ''Does the use of <code><div></code> and <code></code> elements add any semantics to web pages?''===

A. According to the [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.4 HTML 4 spec], <code><div></code> and <code></code> "offer a generic mechanism for adding structure to documents." Their only meaning is in dividing documents into sections, and as such, their presence implies that the content within has a specific, but undefined by the element markup, semantic. Thus they are nearly semantic-free.

===Q. ''Why do the examples on the wiki use <code class="element"></code> and <code class="element"><div></code> for nearly everything?''===

A. <code class="element"></code> and <code class="element"><div></code> are generic elements in HTML. When you use microformats, you should pick the most specific semantic element available for the semantics you are trying to express. You might, for example, apply <code>class="vevent"</code> to a <code><nowiki><tr></nowiki></code>, or <code>class="vcard"</code> to a <code><nowiki></nowiki></code>.

== classのセマンティクス ==

===Q. ''How will microformat class names impact page size?''===

A. You probably won't notice any impact on page size when authoring with microformats. Our experience is that people use comparably sized class names, and [[semantic-class-names|semantic class names]] are now considered an industry best practice. Some sites are successfully publishing millions of microformats, and we haven't heard any complaints yet. You are more likely to gain space savings by more fully adopting [[microformats#the_microformats_principles|the principles of microformats]], and eliminating tables for layout.
''TODO: Consider creating a new section for web authoring tips? Or at least linking to another site that advocates good authorship.''

===Q. ''1つの要素に複数のclass名を付けることはできますか?''===

A. できます。class属性の値は、空白区切りを入れることで複数のclass名を書くことができます。例えば次のようになります。
Write high quality and simple mark-up.

W3C HTML 4.01 Specificationのclass属性についての記述も見てください: [http://www.w3.org/TR/html401/struct/global.html#adef-class 7.5.2 Element identifiers: the id and class attributes]

===Q. ''Do (X)HTML class names have semantics?''===

A. The HTML4 specification does not define any particular class values [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF], nor does it define any particular semantic for class values [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF], except that they "may be used for general user agent processing" [http://www.w3.org/TR/REC-html40/struct/global.html#h-7.5.2 REF]. However, the [http://www.w3.org/TR/WD-htmllink-970328#profile" draft of "Hypertext Links in HTML"], allows for a "profile" to define meanings for those classes. [http://gmpg.org/xmdp/ XMDP] is a format for defining meta data profiles for (X)HTML, and thus an XMDP profile can be used to define the meanings of class names.

See also:
* [http://tantek.com/log/2002/12.html#L20021216 A Touch Of Class]
* [http://www.w3.org/TR/WD-htmllink-970328 Hypertext Links in HTML]

===Q. ''I thought one of the main goals of CSS was to separate data from presentation. Isn’t this sneaking presentation back into data?''===

A. This is a quite commonly expressed objection to the way microformats uses class, but it's based on a misunderstanding of the way the class attribute in HTML was designed. Yes, class is very commonly,and appropriately used by web designers in conjunction with CSS to style pages, and in truth, it is often overused for that, but despite this, class, according to the HTML specification "has several roles in HTML", including [http://www.w3.org/TR/html4/struct/global.html#h-7.5.2 "for general purpose processing by user agents"].

Microformats utilize this second aspect of the class (and id) attribute, and do so legitimately. It is not an abuse of the class or id attribute to use it to add semantic context to a document. Nor is the use of class in and of itself presentational - in fact, it is an important mechanism for separating presentation from structured content.

For some more on using class semantically, here are some articles

* [http://meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competent Classing by Eric Meyer]
* [http://www.w3.org/QA/Tips/goodclassnames Use class with semantics in mind, W3C]
* [http://tantek.com/log/2004/07.html#d20t2359 More about the class attribute, Tantek Çelik]

== microformatsとspam ==
===Q. ''Given that Google now looks at hidden content as potential spam, will invisible microformats be considered spam?''===

A. It is advisable not to hide information in your site, regardless of whether it is microformatted or not. Microformats provide a mechanism for marking up ''visible'' content. Any mechanism for embedding ''invisible'' or hidden content risks being considered spam due to the fact that invisible (meta)data inevitably ends up being abused. Avoid invisible (meta)data. Publish visible data.

== abbrとtitleに関するデザインパターン ==
===Q. ''Why is ABBR being used when the title attribute is available on all HTML elements?''===

In the datetime design pattern the title attribute is used for the value of the property and the node value is used as the display value. <abbr title="value-here">Display-Here</abbr>.

A. The short answer is that <abbr> has the correct semantics.

The longer answer is that the value is often an abbreviated version of the formal value. Of course, if you don't want to use an <abbr>, you can use another element like this:

<abbr title="2006-12-31T12:59:59Z" class="dtstamp">New Year</abbr>

2006-12-31T12:59:59Z

In addition, microformats encourage the content to be visible and thus prefer the text of an element rather than using the 'title' attribute or any other less visible alternative. The exception is made for datetimes and abbr due to the fact that microformats are for humans first, machines second. Thus the content of the abbr element is used to provide human visible content and the machine equivalent is placed in the less visible (but still easily verifiable) 'title' attribute.

== 要素の入れ子 ==
===Q. ''<code>...</code>としたいのですが、良いのでしょうか?''===

A. ダメです。[[hcard-faq#nesting-properties]]を見てください。

== See Also ==
* [[misconceptions]]

distributed-conversation-brainstorming-fr

2009-01-06T08:07:30Z

Brian: Reverted edits by ZelgeTtrpa (Talk) to last version by Brian

=citeRel brainstorming=
Différentes parties ont proposé des microformats apparentés aux citations et aux conversations en ligne distribuées. Ryan King et Eran Globen ont démarré avec hVia (qui est devenu citeVia et plus tard citeRel :-)). Vous pouvez voir la conversation dans ces billets de blogs :

Les gens citent déjà leurs sources dans leurs billets de blogs et ce serait génial (et ne devrait pas être trop difficle) de tracer cette information. Dans cette veine-là, lisez [http://theryanking.com/blog/archives/2005/05/06/hvia/ ce billet] qui couvre l'idée initiale sur le sujet. ([http://theryanking.com/blog/archives/2005/05/09/citevia/ Ceci] était un billet de relance).

Plus tard, [http://hellononline.com Eran] [http://hellonline.com/blog/?p=18 a étendu l'idée] pour couvrir non seulement via des citations, mais aussi les réponses et mises à jour. Billet de relance [http://hellonline.com/blog/?p=19 ici].

[[distributed-conversation-examples-fr|distributed-conversation-exemples]]

== Note pour les citations générales de texte ==

Cette page est complètement dédié à propos de citations d'hyperliens, soit explicitement à travers l'usage d'un <code><a href></code> ou d'un attribut essentiellement caché "cite" sur les éléments <code><blockquote></code> et <code><q></code>.

Pour les citations de texte général, jetez un oeil svp sur :
* [[cite-examples-fr|cite-exemples]], [[cite-formats-fr|cite-formats]], [[cite-brainstorming-fr|cite-brainstorming]]

==Problème==
L'idée basique que nous essayons de résoudre ici est le suivi de conversation distribuée - plus spécifiquement, la conversation distribuée entre billets de blog - l'étendue est intentionnellement limitée ici, même si d'autres aspects de conversation distribuée sont certainement importants et en rapport.

:Une plus petite portion du problème est dans l'identification des sources faisant le plus autorité dans un fil de discussion à l'échelle du web. En recherchant n'importe quoi, la capacité d'identifier une source primaire est inestimable. Ajouter ce type d'ordinalité ajouterait de la valeur à n'importe quelle liste de liens apparentés tel qu'une page tag.

::Trouver une source faisant autorité n'est pas un problème plus petit, mais un plus grand problème - vous devez avoir la totalité du graphe de la conversation afin de trouver les noeuds racines. --RyanKing

:::la définition de l'Autorité ici est trouble au possible. Bien au delà du champ de cette discussion. --[[User:EranGloben|EranGloben]] 13:41, 21 Jan 2006 (PST)

:Citer ('quoting' ou faire référence à une source faisant autorité ou précédente) et donner un coup de chapeau (donner crédit à une source non primaire pour appeler l'attention vers un source initiale d'autorité) sont sûrement deux animaux différents. L'étiquette commune suggère l'utilisation de tags ancres parce qu'ils peuvent être mis en marche par l'utilisateur

:J'ai plongé aux alentours du [http://www.w3.org W3C] et trouvé que rel="cite" est ''already déjà défini'' dans [http://www.w3.org/TR/2005/WD-xhtml2-20050527/mod-metaAttributes.html XHTML Metainformation Attributes Module]. Dans [http://www.w3.org/TR/2005/WD-xhtml2-20050527/mod-hyperAttributes.html XHTML 2.0 Hypertext Attribute Collection], les attributs href et cite sont définis et peuvent coexister mais se comportent différemment : L'attribut href "spécifie un URI qui est déclenché quand l'élément est activé". Pour l'attribut cite, "Les Agents Utilisateurs DOIVENT fournir un moyen pour l'utilisateur de mettre en marche le lien".

::Ceci a déjà été couvert dans les billets de blogs ci-dessus. Il est admis néanmoins que cela ait besoin d'être porté dans ce document. --RyanKing

:Attendu que les auteurs apprécient en général de voir leurs travaux cités avec des hyperliens, et attendu que les utilisateurs peuvent être recensés dessus pour citer des sources primaires et non primaires simultanément sans les différencier, et attendu que l'unique différence entre une citation primaire et une citation non primaire est le potentiel pour des vias skippés au moment d'être considérés dans une conversation distribuée, et attendu que l'utilisation de spécifications existantes est préférées à la création de systèmes redondants, et alors qu'augmenter les attributs est moins sévères que d'accroître les éléments imbriqués, je propose qu'une bonne définition et l'utilisation de rel="cite" résoudra le problème de créditer les sources via des ancres. <cite>Andy Skelton</cite>

::Je vois la conclusion comme complètement à l'opposé. Parce que rel="cite" *est* défini dans les drafts XHTML2, et que les microformats vous permettent d'ajouter *désormais* des valeurs rel au HTML4/XHTML1, adopter la même convention fait beaucoup de sens.

::Si c'est le cas, cela soutient le cas en faveur de rel="cite" (à l'opposé de quelque autre valeur comme rel="source").

::Dans un microformat relCite, vous définiriez la valeur "cite" en la référençant normativement XHTML2, plutôt que de la redéfinir (même en copiant collant la définition à partir de la spec XHTML2 -- bien qu'on pourrait faire ainsi "informativement"), tout simplement comme dans [[hcard-fr|hCard]], nous définissons les propriétés en référençant normativement vCard. <cite>Tantek</cite>

:::[http://www.w3.org/TR/2005/WD-xhtml2-20050527/ XHTML 2.0] déclare que ce ne "devrait en aucun cas être considéré comme stable, et ne devrait pas être référencé normativement pour quelque objectif que ce soit." <cite>Andy Skelton</cite>

:::: Très bon point Andy. De ce fait nous devrions définir rel-cite comme compatible, et puis donner l'attribution et la référence informativement au XHTML2. <cite>Tantek</cite>

:Il y a un problème apparenté qui n'est pas exactement le même. Disons que vous avez un peu de données microformatées qui sous-tendent une assertion, et l'autorité est la page conteneur. Par exemple, un relTag pourrait avoir une valeur sémantique comme "je prétends que cet objet est FOO." Quand cette assertion est copiée sur une nouvelle page, l'identité de l'"asserteur" doit être produite explicitement : "selon la page originale contenant sur BAR, cet objet est un FOO." Maintenant disons que quelqu'un copie cela sur la copie. Ceci pourrait arriver s'il y a un B-lister qui avait une entrée prise par un A-lister, et que l'entrée du A-lister soit ensuite copiée sur un grand nombre de C-listers. (Un modèle typique pour la diffusion de données). Pour que la donnée garde toute son intégrité, la source de la citation devrait être la page original contenant (celle du B-lister) plutôt que la page conteneur d'où la copie a été extraite (celle du A-lister). <cite>Lucas Gonze</cite>

::Lucas- c'est la raison pour laquelle Dieu a inventé <blockquote>. Le contenu ''copié'' à partir d'un site vers un autre devrait être cité. --RyanKing

::La question n'est pas de savoir si quelque chose a été copié mais quel source de citation c'est. Ceci est un cas où la différence entre une citation primaire et une citation non-primaire impacte le sens de la donnée. <cite>Lucas Gonze</cite>

::Ceci illustre les différences entre les types de citations. C citant le texte de A trouvé sur le blog de B. C utiliserait une réponse ou une citation de type forward au moment de référencer le texte de A et ajouterait une citation de type via quand il mentionne sa source B. --[[User:EranGloben|EranGloben]] 13:41, 21 Jan 2006 (PST)

:J'ai un problème apparenté qui peut donner quelque lumière là-dessus. Je suis venu sur cette page parce qu'ai simplement regardé une citation de journal scientifique et pensait que "cela pourrait être un microformat." Il existe déjà des formats standards pour les citations de toutes sortes, y compris les sites web (par ex. [http://owl.english.purdue.edu/handouts/research/r_mla.html Modern Language Association]), aussi peut-être que convertir ceux-ci en microformats résoudrait le problème déclaré ici, et plus encore. -- Scott Reynen

== Tags imbriqués cite/anchor ==

== rel="cite" / rev="cite" ==

Ce pourrait être un moyen d'indiquer une citation de contenu lié, généralement des pages web (ou des portions, comme des billets de blogs) mais y compris toute forme de ressource avec un URL. "Cite" est défini comme "to quote or refer to as a precedent or authority."

En ajoutant <code>rel="cite"</code> à un hyperlink, un auteur pourrait indiquer que la destination de cet hyperlien est une source officielle ou un précédant vers la page en cours. rel="cite" devrait être utilisé si un auteur cites par citation :
<pre><blockquote>Our liberty depends on the freedom of the
press, and that cannot be limited without being lost.
<a href="http://en.wikiquote.org/wiki/Thomas_Jefferson" rel="cite">
Thomas Jefferson</a></blockquote></pre>
ou par référence seulement :
<pre><a href="http://exemple.com/jeanschtroumph/article/99/" rel="cite">
La dernière humeur de Jean Schtroumph</a> c'est faux, faux, faux,...</pre>

Les hyperliens <code>rel="cite"</code> sont prévus pour être visibles sur les pages et billets. Notez que d'autres balisages peuvent être utilisés pour indiquer la citaton
<pre><blockquote cite="http://en.wikiquote.org/wiki/Thomas_Jefferson">
Our liberty depends on the freedom of the press, and that cannot be
limited without being lost.<cite>Thomas Jefferson</cite></blockquote></pre>
mais les Agents Utilisateur ne sont pas obligés d'exposer un lien vers la ressource citée. Les hyperliens sont préférés par la plupart des auteurs parce qu'ils permettent un accès facile pour l'utilisateur à la ressource citée.

== citeRel vs. relCite ==
Pour une structure basique et un balisage de citations, il a été suggéré que nous utilisions ce qui suit :
<pre>

<a rel="cite" href="source.url">source.titre</a>
</pre>
au lieu de
<pre>

<cite><a href="source.url">source.titre</a></cite>
</pre>

Il y a plusieurs raisons de préférer la forme citeRel à la forme de balisage relCite :
# citeRel n'utilise uniquement que des éléments XHTML existants et des valeurs là ou relCite utilise une nouvelle valeur rel.
# citeRel est facilement extensible sans casser son sens existant.

==Quand est-ce que le href nu est (ou pas) une citation ==
Un href est une citation quand :
* Un billet de blog fait référence à un autre billet ou pour une présentation, puis parle ensuite de ce billet ou de cette présenation. par ex "je crois que c'était plus ou moins la même <a href="...">présentation</a> qu'il a donné cette année à SxSW" [http://theryanking.com/blog/archives/2005/05/06/hvia/ Ryan King].

Un href n'est pas une citation quand :
* Un billet de blog fait référence à l'auteur d'un billet ou d'une présentation en utilisant l'url de la page personnelle de l'auteur, puis parle du billet ou de la présentation. par ex. "For my Internet Systems Research class last night, we had <a href="...">Tantek Çelik</a> come speak on microformats" [http://theryanking.com/blog/archives/2005/05/06/hvia/ Ryan King]
* Un blog fournit une blog-roll, ou un panel de "signets récents"

== Pas en Avant ==
En se basant sur les exemples trouvés dans ma recherche, les précédents formats et des discussions avec plusieurs personnes, j'ai vu les possibilités suivantes pour ce format.

'''Option 1'''
<cite class=”foo”><a href=”source url”>source title</a></cite>
<blockquote>
Texte cité
</blockquote>

'''Option 2a'''
<blockquote cite=”sourceurl” class=”foo”>
Texte cité
</blockquote>

'''Option 2b'''
<a href=”source url”>source title</a>
<blockquote cite=”sourceurl” class=”foo”>
Texte cité
</blockquote>

'''Option 3'''
<a href=”source url” rev=”cite/via”>source title</a>
<blockquote>
Texte cité
</blockquote>

'''Notes'''
# Dans les exemples précédents, vous pouvez substituer <Q> par <BLOCKQUOTE>
# Les options 1 et 2 ne sont pas nécessairement exclusive-mutuellement.
# A la fois dans 1 et 2 remplacez foo par le nom de classe approprié (par ex. via, rev-reply, rel-update, etc.)

'''Discussion'''

L'option 1 est basé sur la suggestin de Tantek dans [http://tantek.com/presentations/2005/03/elementsofxhtml/ The Elements of Meaningful XHTML] et a été atteinte de façon indépendante par (voir [[distributed-conversation-examples-fr| la page d'exemples]]). Elle semble sous-entendre que le document actuel est en train de citer la totalité du document lié.

L'option 2a est basé sur des standards HTML existants et émérgent est quelque modèles d'utilisation existants. Pour rendre la relation explicite, l'attribut de classe est utilisé mais peut être repmplacé par un attribut rel/rev dès qu'un est introduit dans des éléments quote. Cette option est actuellement problématique parce qu'aucun agent utilisateur que je connaisse n'exposer la valeur de l'attribut cite à l'utiliateur.

L'option 2b essaye de résoudre ce problème en ajoutant un lien au document cité. Cette solution a l'avantage évident de répéter l'information mais évoluera naturellent dès que les agents utilisateurs amélioreront leur gestion des attributs cite.

L'option 3 est basée sur la valeur cite rel introduite dans plusieurs standards et la valeur via rel value introduite dans atom. Elle se construit sur ce qui semble être le format le plus populaire en utilisation. Mises en garde :
* Compte tenu de l'existence de l'élément CITE il semble que la valeur cite rel est redondante même s'il apparaît qu'elle fera bientôt partie des standards à venir.
* Un autre problème avec ce format est que les valeurs cite et via ne sont pas assez spécifiques. Utiliser ce format d'une manière plus précise exigera d'utiliser des valeurs rel non standards.

'''Résolution En cours'''

Après discussions les options ci-dessus ont convergé dans la syntaxe suivante :

<cite id="$cite.id$" class="$relationship$"><a href="$source.url$">titre
source</a></cite>
<blockquote cite="#$cite.id$">
texte cité
</blockquote>

L'utilisation de l'attribut cite connecte l'élément blockquote (ou quote) avec le cite approprié. L'utilisation de cette fonctionnaltié est optionnelle.

==Ressources Supplémentaires ==
* Thread Description Language - TDL est un vocabulaire RDF pour décrire les discussions en mode fil, telles que Usenet, les weblogs, les bulletin boards et les conversations par e-mail.
** http://www.eyrie.org/~zednenem/2002/web-threads/
** http://www.eyrie.org/~zednenem/2002/wtprofile/
* Les discussions Usenet ont utilisé le champ references qui inclut TOUS les billets référencés avec celui répnondu au dernier dans une espace liste séparé.
** http://www.w3.org/Protocols/rfc1036/rfc1036.html Voir section 2.2.5
* [http://www.faqs.org/rfcs/rfc2076.html RFC2076 - Common Internet Message Headers] section 3.6 couvre ce qui suit :
** In-Reply-To - Référence au message dont ce message est un répondre-à.
** References - In e-mail : référence vers d'autres messages en rapport, dans la référence UseNet News vers des 'replied-to-articles'.
** See-Also - Références à d'autres articles en rapport dans Usenet News.
** Obsoletes - Référence au message précédent étant corrigé et remplacé.
** Supersedes - Communément utilisé dans Usenet News avec des manières similaires au header "Obsoletes" décrit au-dessus. Dans Usenet News, néanmoins, Supersedes provoque un effacement total de l'article remplacé dans le serveur, alors que "Supersedes" et "Obsoletes" dans l'e-mail sont implémentés dans le client et souvent ne retire pas la vieille version du texte.
** Article-Updates - seulement dans Usenet News, similaire à "Supersedes:" mais ne provoque pas l'article référencé d'être effacé physiquement.
** Article-Names - Référence à des articles particulièrement importants pour un Newsgroup Usenet spécifique.
* Essayer de Googler autour d'"IBIS" (Issue-Based Information Systems), c'est une approche vers une résolution collaborative de problème qui ressemble beaucoup aux fils de discussion, voir aussi le [http://collab.blueoxen.net/cgi-bin/wiki.pl?HomePage BlueOxen Wiki], [http://collab.blueoxen.net/cgi-bin/wiki.pl?MailingLists BlueOxen Mailing Lists]

books-fr

2009-01-06T08:07:29Z

Brian: Reverted edits by CobocDarde (Talk) to last version by ChristopheDucamp

<h1> Livres </h1>

Cette page liste les livres qui fournissent une description et de la documentation sur les microformats. Les plus récents en premier, groupés par années.

== 2007 ==

*"[http://www.friendsofed.com/book.html?isbn=1590598148 Microformats: Empowering Your Markup for Web 2.0]" par John Allsopp
** Friends of Ed, ISBN 9781590598146, March 2007
** Lisez [http://www.friendsofed.com/extras/1590598148/Appendices.pdf les annexes de John Allsopp (PDF)] et le [http://www.friendsofed.com/samples/1590598148.pdf chapitre 4 sur les microformats geo et adr (PDF)].

== 2006 ==

* ''[http://www.oreilly.com/catalog/neogeography/ Introduction to Neogeography]'' par Andrew Turner
**O'Reilly, ISBN 9780596529956, Décembre 2006
** Ceci est un livre PDF, faisant partie de la série des "O'Reilly Short Cuts". Couvre les microformats ADR et GEO.

* [http://www.oreilly.fr/catalogue/2354020031 Utiliser les Microformats] de Brian Suda
**O'Reilly, ISBN 2-35402-003-1, 2006
** Il s'agit d'un e-book au format PDF publié par les éditions O'Reilly et traduit en français. Une introduction solide à tous les microformats établis, l'histoire, la philosophie et un regard où avancent les microformats.

* ''[http://www.amazon.com/gp/product/0596009879 Web Design In A Nutshell, Third Edition]'' par Jennifer Niederst Robbins. '''IMPORTANT : ceci s'applique seulement à la TROISIEME EDITION !'''
** O'Reilly Media, ISBN 9780596009878, 2006
** Fournit une fondation moderne et excellente des standards pour le design web qui est idéale pour comprendre les microformats, et un chapitre d'introduction global sur les microformats.
** Voir aussi [http://www.oreilly.com/catalog/wdnut3/ Web Design in a Nutshell, Third Edition] (sur le site oreilly.com).

*''[http://www.friendsofed.com/book.html?isbn=1590597656 HTML Mastery]'' par Paul Haine
**Friends of Ed, ISBN 1-59059-765-6, 2006
**Chapitre 5, <abbr title="pages">pp.</abbr> 117-154: ''Purpose Built Semantics: Microformats and Other Stories.''

== 2005 ==

* [http://www.amazon.com/gp/product/0764597582 Hacking RSS and Atom] par Leslie M. Orchard
** Wiley, ISBN 0-76459-758-2, 2005
** Le dernier chapitre a une belle section sur à la fois la façon de publier et consommer des événements [[hcalendar-fr|hCalendar]] dans soit un fil ou comme une partie d'une page. Leslie a implémenté différents microformats (le formulaire de saisie hCalendar sous un script greasemonkey, l'édition dynamique [[xoxo-fr|XOXO]]).
** Vous pourrez trouver le code source pour les scripts [[hcalendar-fr|hCalendar]] extraits de mon livre [http://decafbad.com/trac/wiki/HackingRssAndAtom sur mon site]. Regardez les fichiers démarrant par <code>ch18</code>. Achetez le livre si vous aimez ! [[User:LesOrchard|LesOrchard]] 20:11, 25 Mar 2006 (PST)

books

2009-01-06T08:07:17Z

Brian: Reverted edits by TrlidArere (Talk) to last version by Azathoth

<h1> Books </h1>

This page lists books which provide description and documentation of microformats. Most recent first, grouped by year.

== Errata ==
For errata in any of the following, if any, see '''<nowiki>http://en.wikibooks.org/wiki/Errata/[ISBN]</nowiki>''', where [ISBN] is the ISBN with no hyphens or spaces. (Perhaps this could be added to [[Special:Booksources]]?)

== 2008 ==
* [http://www.amazon.de/gp/redirect.html?ie=UTF8&location=http%3A%2F%2Fwww.amazon.de%2FMicroformats-jedermann-semantische-Entwicklung-vorantreiben%2Fdp%2F3836492210%3Fie%3DUTF8%26s%3Dbooks%26qid%3D1210271777%26sr%3D8-3&site-redirect=at&tag=blognopanicat-21&linkCode=ur2&camp=1638&creative=6742 "Microformats - Semantik für jedermann: Das semantische Web und wie Microformats die Entwicklung vorantreiben werden"] by [http://blog.no-panic.at/ Florian Beer] a german book about microformats, technical and historical background and references for the most important formats.
* Japanese translation of Allsopp's ''Microformats: Empowering Your Markup for Web 2.0''; translated by Noriyo Asano, under the editorship of Kazuhito Kidachi
** Mainichi Communications Inc., early 2008?
** [http://iaspectrum.net/about.html Noriyo] has translated "Ambient Findability" and "Designing Interfaces"; [http://kidachi.kazuhi.to/ Kazuhito] is one of the well-known advocates of Web Standards and microformats in Japan.
** Read their posts about the translation: [http://blog.iaspectrum.net/2007/09/microformats_d0f7.html#more Noriyo's] and [http://kidachi.kazuhi.to/blog/archives/002367.html Kazuhito's] (both in Japanese).

== 2007 ==

* ''[http://www.friendsofed.com/book.html?isbn=1590598148 Microformats: Empowering Your Markup for Web 2.0]'' by John Allsopp
** Friends of Ed, ISBN 9781590598146, March 2007
** Read [http://www.friendsofed.com/extras/1590598148/Appendices.pdf Allsopp's Appendix (PDF)].

== 2006 ==

* ''[http://www.oreilly.com/catalog/neogeography/ Introduction to Neogeography]'' by Andrew Turner
**O'Reilly, ISBN 9780596529956, December 2006
** This is a PDF book, part of the O'Reilly Short Cuts series. Covers the ADR and GEO microformats.

* ''[http://www.oreilly.com/catalog/microformats/ Using Microformats]'' by Brian Suda
**O'Reilly, ISBN 9780596528218, 2006
** This is a PDF book, part of the O'Reilly Short Cuts series. It is a solid introduction to all the established microformats, the history, philosophy and a look at where microformats are headed.

* ''[http://www.amazon.com/gp/product/0596009879 Web Design In A Nutshell, Third Edition]'' by Jennifer Niederst Robbins. '''IMPORTANT: This applies to the THIRD EDITION only!'''
** O'Reilly Media, ISBN 9780596009878, 2006
** Provides an excellent modern standards based foundation for web design that is ideal for understanding microformats, and a whole introductory chapter on microformats as well.
** See also [http://www.oreilly.com/catalog/wdnut3/ Web Design in a Nutshell, Third Edition] (on oreilly.com).

*''[http://www.friendsofed.com/book.html?isbn=1590597656 HTML Mastery]'' by Paul Haine
**Friends of Ed, ISBN 9781590597651, 2006
**Chapter 5, <abbr title="pages">pp.</abbr> 117-154: ''Purpose Built Semantics: Microformats and Other Stories.''

== 2005 ==

* ''[http://www.amazon.com/gp/product/0764597582 Hacking RSS and Atom]'' by Leslie M. Orchard
** Wiley, ISBN 9780764597589, 2005
** The last chapter has a nice section on both publishing and consuming [[hcalendar|hCalendar]] events in either a feed or as part of a page. Les has implemented various microformats (hCalendar entry form as a greasemonkey script, [[xoxo|XOXO]] dynamic editing).
** You can find source code for the [[hcalendar|hCalendar]] scripts from my book [http://decafbad.com/trac/wiki/HackingRssAndAtom at my site]. Look for the files starting with <code>ch18</code>. Buy the book if you like it! [[User:LesOrchard|LesOrchard]] 20:11, 25 Mar 2006 (PST)

grouping-brainstorming

2009-01-06T08:07:16Z

Brian: Reverted edits by AcelvArlet (Talk) to last version by Brian

= Discussion Participants =

== Editors ==
* [[User:ManuSporny | Manu Sporny]], [http://www.bitmunk.com/ Bitmunk] - [http://blog.digitalbazaar.com Digital Bazaar], Inc.

== Contributors ==

* Manu Sporny
* Danny Ayers
* Rudy Desjardins
* Scott Reynen

= Purpose =

It is useful to understand the relationship between objects on a website. A blogger may want to describe several different objects on a web page and group them explicitly. It is important that the structure of the page not affect this grouping as network relationships are often not hierarchical (HTML is always hierarchical).

Where an object resides in a network of relationships can clarify its purpose. For example, an audio album can have a number of audio tracks. It is desirable that the tracks and the album can be associated with one another without needing to be hierarchically grouped. The same goes for chapters in a DVD movie, sections of a podcast, and a set of geographic points.

Grouping relationships are fundamental to how we understand object interactions. The purpose of this brainstorming session is to create possibilities for a grouping proposal.

= Terminology =

== Common Terminology for Grouping ==

== Recommendation ==

= Discovered Methodology =

== Method of Grouping ==

== Ordered Grouping ==

== Unordered Grouping ==

== Sparse Grouping ==

== Dense Grouping ==

== Additional Possibilities ==

= Possible Solutions =

== Option 1: Implicit grouping ==

<pre>
<div class="haudio">
Ammonite
Reconnection
<div class="haudio">
Sunset
</div>
</div>
</pre>

Pros:

* Less verbose for grouping markup.
* No extra collection Microformat necessary.

Pro/con:

* Grouping is handled on a uF by uF basis. Might not be consistent.

Cons:

* Impossible to know if nested microformats belong to the group.
* Does not allow for sparse (unstructured) grouping.

== Option 2: Explicit id-based grouping ==

<pre>
<div id="reconnection" class="haudio">
Ammonite
Reconnection
</div>
[...]
<div id="reconnection.sunset" class="haudio">
Sunset
</div>
</pre>

Pros:

* Explicitly defined groups.
* Grouping is solved for all Microformats.
* Allows for sparse grouping.

Cons:

* New type of Microformat/design pattern may emerge.
* Parser may have to become more complex.
* Use of id isn't very microformatty.

== Option 3: Explicit class-based grouping ==

<pre>
<div class="haudio grouping.reconnection">
Ammonite
Reconnection
</div>
[...]
<div class="haudio grouping.reconnection.sunset">
Sunset
</div>
</pre>

Pros:

* Explicity defined groups.
* Grouping is solved for all Microformats.
* Fits more with the Microformat way than Option #2
* Allows for sparse grouping.

Cons:

* Parser may have to become slightly more complex.

== Option 4: id-class grouping with anchors ==

<pre>
<div class="haudio" id="reconnection">
Ammonite
Reconnection
</div>
[...]
<div class="haudio reconnection">
Sunset
Part of <a name="#reconnection">Reconnection</a>
</div>
</pre>

Pro:
* Supports all types of grouping

Con:
* Anchors are used, displaying links that may confuse the person that is browsing.
* Using IDs are not very microformatty and only support one ID.

== Option 5: class-based grouping with keywords ==
<pre>
<div class="haudio reconnection">
Ammonite
Reconnection
</div>
[...]
<div class="haudio reconnection.member">
Sunset
</div>
</pre>

Pros:
* Uses class instead of id.
* Supports the class attribute being used as an implicit indication of set-membership.
* Indicates the direction of the relationship, ie: which item is the container, as opposed to just using 'albumname' as a class value for both album and song, which would ambiguously indicate that both things are part of a group called 'albumname'.
* Is subject-agnostic - this approach can be used for any type of grouping where one item is contained by another.
* Works for N-N relationships, ie: class="album.member soundtrack1.member soundtrack2.member".

Cons:
* Needs the concept of keywords.
* More verbose than is needed. [[User:ManuSporny|ManuSporny]] 21:18, 14 May 2007 (PDT)
* Difficult to recognize if something is a grouping member until reading the entire identifier. [[User:ManuSporny|ManuSporny]] 21:18, 14 May 2007 (PDT)

== Option 6: per-microformat grouping ==

It has been proposed that we should not attempt to create a grouping mechanism that spans all Microformats. Scott Reynen writes:

My current proposal is to keep grouping semantics specific to each
individual microformat. In this case, albums could be identified by
something like class="album", audio tracks by something like
class="audio-track", and parsers could simply recognize that albums are
groups of tracks, just as hatom parsers recognize that feeds are groups
of entries. Of course, I still think hatom could cover most of the
semantics of audio downloads.

Pros:

* Grouping can be fine-tuned to the particular Microformat
* We avoid the name-spacing issue entirely.

Pro/Con:
* There wouldn't be a standard method of grouping items.

Cons:

* Grouping hell - a new mechanism of grouping would have to be created for every Microformat.
* Many different methods of grouping would look almost exactly the same, leading to redundant, per-uF methods of grouping. [[User:ManuSporny|ManuSporny]] 06:33, 2 May 2007 (PDT)
* This would lead to an explosion in uF class names: album, speech, podcast, audio-track, speech-section, podcast-part, video, video-clip, geo-set, waypoint, etc.
* Due to the explosion in class names, it would be difficult for web developers to remember every method of grouping.

== Option 7: id-class grouping ==

This problem solution proposal was put forward by Chris Griego:

Internal
and With-Client Events
<ol>
<li class="with-client-event vevent">FOO Sales
Pitch [...]</li>
<li class="internal-event vevent">Company
Picnic [...]</li>
<li class="with-client-event vevent">BAR Photo
Shoot [...]</li>
</ol>

Using the hset class names attaches special meaning to the element's
ID value, marking it as the machine-readable group name, and then any
other element in the document with a class name that matches the ID
should be considered a set member. The class attribute is a natural
grouping mechanism, by simply marking contacts across the internet
with 'vcard' we've grouped them in the category of contact
information.

Pros:

* Explicity defined groups.
* Grouping is solved for all Microformats.
* Fits more with the Microformat way than Option #2
* Allows for sparse grouping.

Cons:

* Parser may have to become slightly more complex.
* It splits the specification of a set into two parts (id and class).
* It is impossible to define two top-level sets (option #3 allows this).
* It mixes identifiers and class names (option #3 doesn't need this).
* It uses IDs - something Microformats want to avoid (option #3 doesn't need this).
* It is more complex than option #3, requiring greater cognitive load on the author.

= Possible Uses =

This section describes potential applications for an audio info microformat.

== Transformational Uses ==

It may be desirable to process an audio blog using a transformational tool, such as XSLT, to produce a different representation that can be used elsewhere - such as in a REST invocation.

== Archival Uses ==

Being able to scrape information from a web page and store it long term may be desirable for search companies.

=== Personal Database ===

=== Search Engines ===

=== Partial Text Blogs ===

=Issues=

=See Also=

*[[grouping-examples]]
*[[grouping-formats]]
*[[grouping-proposal]]

User talk:DanMoore

2009-01-06T08:07:15Z

Brian: Reverted edits by CobasLachi (Talk) to last version by AndyMabbett

{{welcome}}
:[[User:AndyMabbett|Andy Mabbett]] 23:13, 31 Mar 2007 (PDT)

posh-fr

2009-01-06T08:07:12Z

Brian: Reverted edits by NotroRacel (Talk) to last version by ChristopheDucamp

{{TOC-right}}
<h1>Code HTML Intrinsèquement Classe (CHIC)</h1>
Bienvenue sur la page d'accueil du <abbr title="Plain Old Semantic HTML">POSH</abbr>. En français, vous commencerez à entendre parler de <abbr title="Code HTML Intrinsèquement Classe">CHIC</abbr>. Rien n'est encore définitif, vos suggestions et revendications peuvent être encore [http://jyte.com/cl/en-fran%C3%A7ais-posh-se-traduit-par-chic discutées].

== Origines ==
L'acronyme '''POSH''' a été inventé [http://rbach.priv.at/Microformats-IRC/2007-04-06#T091456 le 6 avril 2007] sur le canal IRC des microformats, par <kwijibo> pour désigner une abréviation raccourcie de [[plain-old-semantic-html-fr|plain-old-semantic-html]].
Une discussion partagée par John Allsopp, Tantek Çelik, Jeremy Keith et Chris Messina
lors du [[events/2007-04-18-web-2-expo-dinner|Dîner Microformats du 18 avril 2007 faisant suite à l'Expo Web 2.0]] a fait renaître l'idée du POSH et l'importance de promouvoir l'objectif plus large de POSH, quels sont les microformats qui en sont originaires et en sont un propre sous-ensemble. Pour en savoir plus voir [[posh-fr#Historique|Historique]].

== Pourquoi POSH est traduit en CHIC ==
Le terme [[semantic-html-fr|html sémantique]] peut intimider par sa longueur et donne une fausse mauvaise impression de sa simplicité, de sa bonne adoption par les designers web modernes, et les avantages qu'il possède vont bien au delà de développer pour le web comme il faut en utilisant un balisage sémantique. Nous avons besoin d'un terme court et facile à retenir qui capte l'essence du concept, et soit facile à conjuguer. CHIC a été proposé par Kevin Marks et la déclinaison de l'acronyme '''C'''ode '''H'''TML '''I'''ntrinsèquement '''C'''lasse proposée par Stéphane Gigandet colle bien au sens du 'POSH'.

== Quoi ==
Le CHIC regroupe les meilleures pratiques d'utilisation du [[semantic-html-fr|HTML sémantique]] pour publier des pages web. Le HTML sémantique est le sous-ensemble des éléments et attributs du HTML 4.01 (ou du XHTML 1.0) qui sont ''[[semantic-fr|sémantiques]]'' plutôt que ''[[présentationnels]]''. La meilleure façon d'apprendre et de comprendre CHIC est de le mettre en oeuvre. Prenez une page sur votre site web pour démarrer et appliquez-lui la [[posh-fr#La_Checklist_CHIC|Checklist CHIC]]. Continuez avec le [[posh-fr#Le_Processus_CHIC|Processus CHIC]]. Lisez les [[posh-fr#Ressources|Ressources CHIC]] pour en savoir encore plus à propos de CHIC.

== Le processus du CHIC ==
Que pouvez-vous faire pour être CHIC et faire que vos sites web soient CHICs ?
# Publier du contenu CHIC. Lire les [[posh-fr#Ressources|ressources]] posh et vous assurer que votre site web publie du [[semantic-xhtml-fr|(X)HTML sémantique]] valide et utilise des [[semantic-class-names-fr|noms de classes sémantiques]] en rapport.
# Répandre le CHIC. Encourager les autres à être CHIC et à CHICquifier leurs sites web en faisant un lien vers cette page.
# Améliorer le CHIC. Nous aider à assembler des ressources pour permettre à plus de personnes de POSHifier facilement leurs sites web.

== La Checklist CHIC ==
* La première règle de CHIC est que vous devez [http://validator.w3.org valider] votre CHIC.
* Deuxièmement, laissez tomber l'usage des TABLES utilisées purement à des fins de présentation, les GIFs d'espacement et le [[presentational-html-fr|html de présentation]] en général.
* Puis, réparez votre syntaxe [http://tantek.com/log/2002/10.html#L20021022t1432 '''B'''ed and '''B'''reakfast].
* Eliminez les [http://tantek.com/log/2002/11.html#L20021128t1352 Ancres Anorexiques].
* Utilisez de bons [[semantic-class-names-fr|noms de classes sémantiques]].
* ...

== Ressources ==
=== Tutoriels CHICs ===
Etape par étape, les tutoriels pour créer du contenu CHIC ou comment mettre à jour du contenu existant vers CHIC.

* [http://xtof.livejournal.com/14428.html validez votre css et html] Un guide simple étape par étape sur la manière et les raisons pour lesquelles vous devriez valider votre syntaxe
* [http://www.w3schools.com/ Retournez à l'école] W3C Schools le couteau suisse des tutoriels CHIC (en)
* ...

=== Signets CHICs ===
* Regardez le [http://ma.gnolia.com/groups/posh Groupe POSH] sur Ma.gnolia
* Regardez les pages taguées [http://del.icio.us/tag/posh+microformats POSH et microformats] sur del.icio.us.

=== Présentations CHICs ===
Les présentations qui expliquent et encouragent les concepts et techniques pour l'utilisation du HTML sémantique.
Si/Quand cette section sera trop importante, nous pourrons la migrer sur [[posh-presentations-fr|présentations-chic]].
* [http://www.elanceur.org/microformats/slides/CSSEntrelesFeuillesdeStyl.html CSS : Entre les Feuilles de Style par Tantek Çelik (2003-03)] (traduite en français). Voir spécifiquement les dias 3-4,6 démarrant par "Abandonner les [http://tantek.com/log/2002/10.html#L20021022t1432 ed & eakfast]", et la dia 9 "CSS & le Spectre Sémantique" qui fournit un aperçu du spectre sémantique des balises (X)HTML.
* [http://www.tantek.com/presentations/2004etech/realworldsemanticspres.html real world semantics] (2004-02-11) - [http://www.elanceur.org/microformats/slides/semantiquevraimonde.html traduction en cours en français ici]
* [http://tantek.com/presentations/20040928sdforumws/semantic-xhtml.html Semantic XHTML: Can your website be your API? - Using semantic XHTML to show what you mean] (2004-09-28)
* [http://tantek.com/presentations/2005/09/elements-of-xhtml/ The Elements of Meaningful XHTML] (2005-09-29, first version: [http://tantek.com/presentations/2005/03/elementsofxhtml/ 2005-03-13 at SXSW Interactive]).
* ...
* Voir aussi les [[presentations-fr|présentations]] microformats en général.

=== Les Livres CHIC ===
Les livres de design web moderne qui documentent de bonnes pratiques html sémantique.
* <cite>[http://www.oreilly.com/catalog/wdnut3/ http://www.oreilly.com/catalog/covers/0596009879_thumb.gif] [http://www.oreilly.com/catalog/wdnut3/ Web Design in a Nutshell, Third Edition]</cite> by Jennifer Niederst Robbins See [http://jenville.com/ Jenville].
* <cite>[http://microformatique.com/book/ Microformats empowering your markup for Web 2.0]</cite> de John Allsopp. Le Chapitre 3 est un aperçu général et pratique de l'utilisation appropriée du HTML sémantique valide et structuré.
* <cite>[http://htmlmastery.com/ http://htmlmastery.com/images/hm-cover-sm.gif][http://htmlmastery.com/ Semantics, Standards and Styling]</cite> par Paul Haine.
* <cite>[http://www.sitepoint.com/books/html1/ http://www.sitepoint.com/images/books/html1/books-index.gif][http://www.sitepoint.com/books/html1/ Build Your Own Web Site The Right Way Using HTML & CSS]</cite> par Ian Lloyd.

=== Magazines CHIC ===
Les magazines en ligne (et hors-ligne) qui publient fréquemment des articles à propos du html sémantique.
Si/Quand cette section sera trop grosse, nous la migrerons vers [[posh-magazines-fr|magazines-posh]].

* [http://alistapart.com/ A List Apart: For People Making Websites] (voir en particulier [http://www.alistapart.com/topics/code/htmlxhtml/ les articles HTML et XHTML])
* [http://www.digital-web.com/ Digital Web Magazine]

=== Blogs CHIC ===
Les blogs avec des billets réguliers sur des discussions de grande qualité, des idées et qui font en général avancer l'état de l'art de POSH/CHIC. Si/Quand cette section sera trop importante nous la migrerons vers [[posh-blogs-fr|blogs CHIC et POSH]].
* [http://www.plaintxt.org/wp-content/uploads/sandbox-v09_readme.html Le thème Sandbox pour WordPress readme.html] discute de ce qu'est POSH et comment le thème aide les utilisateurs à l'utiliser.
* [http://dbaron.org/log/current le blog de David Baron]
* [http://zeldman.com/ Jeffrey Zeldman Presents]
* [http://meyerweb.com/ meyerweb.com - Eric Meyer]
* [http://microformatique.com/ Microformatique - John Allsopp]
* [http://simplebits.com/ SimpleBits - Dan Cederholm] (voir en particulier [http://simplebits.com/bits/simplequiz/ SimpleQuiz])
* [http://tantek.com/ Tantek Çelik]
* ...

=== Billets de Blog CHIC===
Les billets de Blog qui fournissent des trucs et techniques, spécifiques, modernes, des guides pour utiliser plus souvent et mieux le HTML sémantique.
Si/Quand cette section sera trop grosse, nous la migrerons vers [[posh-blog-posts-fr|billets de blog CHIC]].
* [http://www.456bereastreet.com/archive/200711/posh_plain_old_semantic_html/ POSH - Plain Old Semantic HTML] par Roger Johansson.
* [http://tantek.com/log/2002/10.html#L20021022t1432 Bed and BReakfast markup (B&BR)] (2002-10-22) - éviter les utilisations non-sémantiques des tags <nowiki>old et eak</nowiki> et utiliser à la place les <nowiki>ajouts de <h3> et les aragraphes</nowiki>.
* [http://tantek.com/log/2002/11.html#L20021128t1352 <nowiki><A>norexic </A>nchors</nowiki>] (2002-11-28) - utilisation de l'attribut "id" sur les éléments existants au lieu d'ajouter des éléments vides <code><nowiki><a name="foo"></a></nowiki></code>. Utilisez [[rel-bookmark-fr|rel-bookmark]]
pour poster des permaliens dans le document.
* [http://tantek.com/log/2002/12.html#L20021216t2238 A Touch of Class] (2002-12-16) - introduction à l'usage approprié de l'attribut HTML 'class'.
* [http://tantek.com/log/2002/12.html#L20021231t1850 Dive into Semantic MARKup] (2002-12-31)
* [http://tantek.com/log/2003/01.html#L20030104t1249 Comment markup, presentation and plumbing] (2003-01-04) - comment baliser une liste de commentaires, y compris un exemple d'utilisation
de l'attribut rare "hreflang".
* [http://meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competent Classing] par Eric Meyer (2004-07-18)
* [http://tantek.com/log/2004/07.html#d20t2359 More about the 'class' attribute] (2004-07-20)
* [http://www.uie.com/articles/holzschlag_interview/ Web Standards in the Real World: An Interview with Molly Holzschlag] (2005-06-01)
* [http://westciv.typepad.com/dog_or_higher/2005/11/webpatterns_and.html Webpatterns and websemantics] (2005-11-18)
* [http://www.thefutureoftheweb.com/blog/2006/2/writing-semantic-html Writing Semantic HTML] par Jesse Skinner (2006-02-22)
* [http://nate.koechley.com/blog/2006/12/15/divitis_and_correct_div_usage/ On Appropriate Use of DIVs, or When Divitis Doesn’t Apply] par Nate Koechley, 2006-12-15
* [http://nate.koechley.com/blog/2006/12/22/note_on_structural_and_semantic_meaning/ Quick Comment: Choose Class/ID Names Based on Semantic and/or Structural Meaning] by Nate Koechley, 2006-12-22
* [http://leland.nu/think/2006/07/31/seeing-is-believing/ SEEing is believing] - using standards and efficient design, coding, maintenance, and marketing to produce a search-engine-efficient site par Richard Leland (2006-07-31)
* [http://www.thefutureoftheweb.com/blog/2007/1/who-will-read-your-semantic-html Who will read your Semantic HTML?] by Jesse Skinner (2007-01-04)
* [http://microformatique.com/?page_id=109 Semantics in HTML] par John Allsopp (2007-01-08 - 2007-03-12)
** [http://microformatique.com/?p=83 Part I - Traditional HTML Semantics] (2007-01-08)
** [http://microformatique.com/?p=97 Part II - standardizing vocabularies] (2007-02-20)
** [http://microformatique.com/?p=108 Part III - Towards a semantic web] (2007-03-12)
* [http://microformatique.com/?p=82 Built in HTML semantics] Une liste des éléments sémantiques et des attributs du HTML par John Allsopp (2007-01-08)
* [http://tantek.com/log/2007/04.html#d20t0823 The Importance of Being POSH] by Tantek Çelik (2007-04-20) -> [http://socialsynergyweb.net/cgi-bin/wiki/XtofWiki/EtreChic Etre Chic] traduction en cours pour publication en français sur le blog des microformateurs
* [http://factoryjoe.com/blog/2007/04/21/getting-back-to-posh-plain-ol-semantic-html/ Getting back to POSH (Plain ol’ Semantic HTML)] par Chris Messina (2007-04-21) -> ([http://socialsynergyweb.net/cgi-bin/wiki/XtofWiki/CommentTraduirePosh amorçage de traduction en français]
* [http://friedcellcollective.net/outbreak/2007/04/22/im-posh-are-you/ I'm POSH - are you?] (2007-04-23)
* [http://www.unintentionallyblank.co.uk/2007/04/24/plain-old-semantic-html/ The Internet's Upper Class Or Why Your Site Should Be POSH] (2007-04-24)
* ...

Voir aussi [http://technorati.com/search/%22semantic%20HTML%22 plus de blogs parlant du "semantic HTML"] et
[http://technorati.com/search/posh+semantic+HTML POSH].

===Podcasts CHIC et POSH===
Si/quand cette section deviendra trop grosse, nous pourrons la migrer vers [[posh-podcasts-fr|CHIC-podcasts]].
* 2007-05-03: [http://www.netmag.co.uk/podcasts/07-05-03-net.mp3 A talk about POSH] dans le podcast du magazine .Net épisode 8 (56 minutes ; 26 Mb. Section où ou en parle 30:10-42:40)
* 2005-09-29: [http://microformats.org/media/2005/09/we05-2-tantek-celik.mp3 The Elements of Meaningful XHTML] - podcast de la présentation de Tantek du même nom ([http://tantek.com/presentations/2005/09/elements-of-xhtml/ diapos])

=== Trésors cachés CHIC ===
Le sites suivants ont des articles en rapport avec CHIC, des tutoriels, et. Sur eux, vous devrz plonger à partir de la page d'accueil. Aidez-nous à trouver les trésors CHIC dissimulés dans ces sites et ajoutez des liens ''directs'' vers des articles en rapport avec CHIC, des tutoriels pour les hisser aux sections spcécifiques au-dessus. Vous pouvez laisser les liesn vers le niveau le plus haut du siteà moins que n'ayez à plonger dans le site en entier pour y trouver tous les trésors.
* [http://www.w3schools.com/ W3Schools Tutoriels Web en ligne] (en)
* [http://dev.opera.com/ Dev.Opera] (en)
* [http://pompage.net pompage] (fr)

=== Faites que votre Blog soit CHIC ===
Si vous voulez améliorer votre blog existant, il existe quelques choses
vraiment simples que vous pouvez faire vous-même :

==== WordPress ====
* Utilisez les thèmes [http://www.plaintxt.org/themes/sandbox/ Sandbox] ou [http://getk2.com K2] qui supportent déjà hAtom et hCard
* Ajoutez le [http://redmonk.net/archives/2007/04/18/wordpress-widget-hcard-about-box/ Widget hCard About] à votre site

== Répandez CHIC ==
Maintenant que vous avez CHICquifié vos sites web, que faire ensuite ?
Bien, aidez à répandre CHIC sur d'autres sites web !
* Faites la promo de CHIC. Fabriquez un bouton CHIC (peut-être en utilisant une sémantique HTML et CSS) faisant un lien vers cette page et placez-le sur votre site, dans votre blogroll, en pied de page, etc. Venez même peut-être avec un joli bouton graphique CHIC et partagez-le avec la communauté microformats avec une licence libre (domaine public, CC-by-3.0, MIT, etc.). Inspirez-vous de ceux-ci :
** http://redmonk.net/wp-content/uploads/2007/04/chic_fancy.png - [http://creativecommons.org/licenses/by/3.0/ CC-by-3.0]
* Parlez-en à un ami. Parlez à vos amis designers de POSH et convainquez les de ''chicquifier'' leurs sites web personnels, et les sites web qu'ils construisent pour les autres. Bloguez votre expérience de CHICquification et les étapes que vous avez traversées pour CHICquifier vos sites web.
Ecrivez un [[posh-testimonial-fr|témoignage CHIC]] !
* Revenez avec plus d'idées pour aider à propager CHIC. En voici quelques-unes.
** Organisez un [http://socialsynergyweb.net/cgi-bin/wiki/XtofWiki/ChicPit CHICPit] - une journée ou demi-journée de session marathon mélangeant des experts du HTML sémantique avec des types qui maintiennent/font tourner des sites web en général, et regardez comment vous pouvez les mettre à jour en groupe vers CHIC durant la journée.
** ...

== Améliorez CHIC ==
Au fur et à mesure que vous lisez les [[posh-fr#Ressources|ressources CHIC]] documentées ici, quelles sont les autres ressources CHIC que vous avez trouvées ? Ajoutez-les à cette page.

Avec votre expérience et votre capacité à pouvoir à la fois "poshifier" vos sites et aider les autres à faire ainsi, qu'avez-vous appris ? Quels sont les types de [[posh-issues-fr|problématiques]] que vous avez rencontrées ? Quelles sont les questions souvent posées ? Quels seraient vos besoins pour aider facilement et rapidement plus de personnes à poshifier leurs contenus ?

== Historique ==

Une historique rapide de références à "CHIC" dans ce contexte et au "bon vieux html sémantique".

=== bon vieux HTML sémantique ===
Les premières références au "bon vieux HTML sémantique" qui ont été trouvées à cette heure sont :
* [http://groups.google.com/group/comp.infosystems.www.authoring.site-design/msg/2373e9043c08cba4 1998-05-01: Kirrily 'Skud' Robert on comp.infosystems.www.authoring.site-design] - "The site is implemented in HTML 4.0 Transitional with style sheets; this means that anyone with an older browser won't get presentational markup, just plain old semantic HTML. "
* [http://www.highrankings.com/advisor/tables-seo/ 2006-09-21 Drew's comment by on "Tables and SEO"]: "I’d say it’s well worth it for a variety of reasons to only use tables when you’re presenting tabular data, and use plain old semantic HTML to mark up your content in all other cases." (retrouvée par [[User:Tantek|Tantek]] 08:20, 20 Apr 2007 (PDT))
Si vous pouvez trouver des références plus anciennes, ''ajoutez-les'' les svp et joignez-y une citation brève du contexte de la référence à "bon vieux html sémantique".

events/2007-04-18-web-2-open-media

2009-01-05T10:45:48Z

Brian: reverted spam

<h1>Microformats for media at Web 2 Open 2007</h1>
One of several microformats [[events]].

== Summary ==
This session will start with an explanation of Microformat principles and the Microformats process, then focus on the state of microformats for media information, with a call to the community to participate in moving this forward. We have a good set of examples, which have languished for sometime. Let's move this to the stage of scheme convergence so that the conversation can continue on the list and on the wiki.
== Where ==
[http://www.web2expo.com/pub/w/53/venue.html Moscone West, San Francisco (room ALPHA)]

== When ==
[https://www.socialtext.net/web2open/index.cgi?mary_hodder Session Details]

2007-04-18
* 2pm-2.50pm

== Speakers ==
*Mary Hodder
*Kevin Marks

== Attending ==
Please add your name here if you attended these sessions, speaking or not.

*John Allsopp
*Tantek Çelik
*Simon Willison
*Heidi
* ...

== Session Comments and Q&A ==
* ...

== Photos ==
Please tag with "[http://flickr.com/photos/tags/microformatswdn2007/ microformatsweb2expo] microformatsweb2open microformatsmedia".

* ...

== Blog Posts ==
Please tag with "[http://flickr.com/photos/tags/microformatswdn2007/ microformatsweb2expo] microformatsweb2open microformatsmedia".

* ...

== Podcasts ==
* Coming!

== See Also ==
* [[events/2007-04-17-web-2-expo|Web 2 Expo 2007 microformats events]]

alternates-examples

2009-01-05T10:40:20Z

Brian: Reverted edits by AcchiLicna (Talk) to last version by Brian

= Introduction =
This page is to collect examples of '''alternates''', that is, places where a user may be given several different items to choose amongst that at some logical level are considered equivalent.

== Discussion Participants ==

=== Editor ===
* [http://blogmatrix.blogmatrix.com/ David Janes], [http://www.blogmatrix BlogMatrix, Inc.]

=== Authors ===
* [http://blogmatrix.blogmatrix.com/ David Janes], [http://www.blogmatrix BlogMatrix, Inc.]
* Lucas Gonze
* Greg Borenstein

=== Interested Folks ===

= Specific Examples from the Wild =

== MediaRSS ==
Yahoo's [http://search.yahoo.com/mrss Media RSS] provides the <media:group> tag to group alternate choices for the same media file together. Here's an example from their spec:

<pre><nowiki>
<rss version="2.0">
<channel>
<title>Song Site</title>
<link>http://www.foo.com</link>
<description>Songs galore at different bitrates</description>
<item>
<title>Cool song by an artist</title>
<link>http://www.foo.com/item1.htm</link>
<media:group>
<media:content url="http://www.foo.com/song64kbps.mp3"
fileSize="1000" bitrate="64" type="audio/mpeg"
isDefault="true" expression="full"/>
<media:content url="http://www.foo.com/song128kbps.mp3"
fileSize="2000" bitrate="128" type="audio/mpeg"
expression="full"/>
<media:content url="http://www.foo.com/song256kbps.mp3"
fileSize="4000" bitrate="256" type="audio/mpeg"
expression="full"/>
<media:content url="http://www.foo.com/song512kbps.mp3.torrent"
fileSize="8000" type="application/x-bittorrent;enclosed=audio/mpeg"
expression="full"/>
<media:content url="http://www.foo.com/song.wav"
fileSize="16000" type="audio/x-wav" expression="full"/>
<media:credit role="musician">band member 1</media:credit>
<media:credit role="musician">band member 2</media:credit>
<media:category>music/artist name/album/song</media:category>
<media:rating>nonadult</media:rating>
</media:group>
</item>
</channel>
</rss>
</nowiki></pre>

Note the mixing of alternates and related metadata together under the group tag.

== hVlog ==

The [http://vpip.org/ vPIP] (Videos Playing in Place) library uses a format called [http://formats.cinegage.com/index.php?title=HVlog hVlog] to identify media enclosures in blog posts.

= See Also =
* [[alternates-examples]]
* [[alternates-formats]]
* [[alternates-brainstorming]]
* [[media-metadata-examples]] -- Yahoo's Media RSS uses this

hcalenar

2009-01-05T10:40:18Z

Brian: Reverted edits by SitreLtali (Talk) to last version by Tantek

#REDIRECT [[hcalendar]]

be-strict

2009-01-05T10:40:13Z

Brian: Reverted edits by CaricElbas (Talk) to last version by Brian

=Be strict in what you send, but generous in what you receive=

"'''Be strict in what you send, but generous in what you receive'''" is a principle in computing (originally referring to e-mail), which suggests that systems (such as e-mail relays or microformat parsers) should be very strict in making sure that their output conforms to standards, but flexible in interpreting data received, which may not adhere to the relevant standard, but whose meaning is still unambiguous.

It is a variant of [http://en.wikipedia.org/wiki/Jon_Postel#Postel.27s_Law Postel's Law], "''be conservative in what you do, be liberal in what you accept from others''".

==Background==

See [[hcard-brainstorming#ADR with no children]] for an example of how this might be applied. [[User:AndyMabbett|Andy Mabbett]]

(Anyone got a better explanation, references, or etymology?) [[User:AndyMabbett|Andy Mabbett]]

*Having had many years developing and implementing standards, IMHO there are both plusses and minusses to Postel's law. [[User:Tantek|Tantek]] 08:23, 26 Mar 2007 (PDT)
**What do you perceive are the disadvantages (especially in the context of microformats)? [[User:AndyMabbett|Andy Mabbett]] 08:34, 26 Mar 2007 (PDT)
*** Much of the complexity of building an HTML implementation (AKA/EG parser, browser, table-formatter) has been blamed on the adoption of Postel's Law by early browser implementers. It is now effectively impossible to build a new browser from scratch without putting in a multimillion dollar investment of time and engineering resources, in spite of the fact that the first browser was built by a single individual, Tim Berners-Lee. Essentially, following Postel's Law can have the impact of raising the barrier to entry to implementation development so high as to be prohibitive to individuals or small teams, and only possible by large corporations. It is undesirable to implicitly require the resources of a large corporation (and thus be dependent on) in order to build microformats implementations, which are currently implementable (have been implemented) by both individuals and small teams. [[User:Tantek|Tantek]] 08:46, 26 Mar 2007 (PDT)
****So, a matter of degree: ''be generous in what you receive - within reason''? [[User:AndyMabbett|Andy Mabbett]] 08:57, 26 Mar 2007 (PDT)
*** Additionally, Postel's Law has been blamed for making interoperability ''more'' difficult in the case of HTML, or rather, even discouraging interoperability, as different implementations "liberally/generously" have treated errors (invalid HTML) differently over time. [[User:Tantek|Tantek]] 08:46, 26 Mar 2007 (PDT)
****Resolved, in our case, by documenting solutions here ? [[User:AndyMabbett|Andy Mabbett]] 08:58, 26 Mar 2007 (PDT)
***** Perhaps. The more important principle may be the balance of simplicity between publisher and implementer. I think we (the microformats community) are still figuring the optimal level of this balance, but I believe we are on the right track. Asking just a little of publishers in order to make it reasonably easy for implementers to implement. [[User:Tantek|Tantek]] 09:01, 26 Mar 2007 (PDT)

==References==
*[http://en.wikipedia.org/wiki/Robustness_Principle Robustness Principle]

mfcomment

2009-01-05T10:40:12Z

Brian: Reverted edits by C4tliDarla (Talk) to last version by AndyMabbett

{{DeprecatedHistoricalPage}}
If you are interested in using microformats to markup your comments, [[hatom|hAtom]] is recommended.

== Author ==
* [http://an9.org/devdev Andy Smith]

== Introduction ==
I'm no spec draft lawyer, so just take this as being "in the same vein" as hReview, hCalendar and the like. I feel the examples are pretty self-explanatory.

== Examples ==
The big example, using as many properties as seemed could apply to a comment:
<pre><nowiki>
<div class="mfcomment">
0.1
 Regarding: <a class="url" rel="target" href="http://an9.org/blog/2005/06/07/super-sekret-project/">Super Sekret Project</a>
By: 
<a class="url nickname" href="http://anarkystic.com/blog">termie</a>
Andy Smith</a>
<img class="photo" src="http://an9.org/images/small_andy.png" alt="Photo of Andy Smith" />

<a class="url" rel="thread parent" href="http://sxore.com/comment/view/14">parent</a>
<div class="summary">Just a comment...</div>
<abbr class="dtcommented" title="20050612T21:30-0700">June 12th, 2005</abbr>
<div class="description">
Boy, I really like that thing
</div>
<a class="url" rel="self bookmark" href="http://sxore.com/comment/view/14">link to this comment</a>
</div>
</nowiki></pre>
The small example, using a minimum set of data:
<pre><nowiki>
<div class="mfcomment">
<a class="url" rel="target" href="http://an9.org/blog/2005/06/07/super-sekret-project/">Super Sekret Project</a>
anonymous
<abbr class="dtcommented" title="20050612T21:30-0700">June 12th, 2005</abbr>
<div class="description">
Gosh, this is neat.
</div>
<a class="url" rel="self bookmark" href="http://sxore.com/comment/view/14">link to this comment</a>
</div>
</nowiki></pre>

resume-examples-fr

2009-01-05T10:40:08Z

Brian: Reverted edits by CaletOboac (Talk) to last version by Brian

<h1> Exemples de CV </h1>

Cet espace est destiné à assembler et faire une analyse simple des curriculum vitae trouvés sur le WWW en tant que section du [[process-fr|processus]] dans le dévelopement d'un microformat [[resume-fr|résumé]] ou CV. Voir le draft [[hresume-fr|hResume]].
__TOC__

== Styles de Résumés ==
Dans la discussion humaine typique, quand les personnes font référence à des "formats de résumé.", elles veulent dire comment vous organisez et mettez en page votre C.V. pour une consommation humaine. Néanmoins ce terme est ambigu car il pourrait aussi faire référence au format de données du résumé (comme cela se fait sur microformats.org). Par conséquent, l'aspace humain de l'organisation/mise en page d'un résumé que nous étiquetons le "style de résumé", et réservons le sens d'un "format de résumé" pour le format de *données* du C.V. Pour la recherche sur les formats de données du résumé., voir [[resume-formats-fr|resume-formats]].

En discussion avec les types de SimplyHired, ils faisaient remarquer qu'ils avaient vu deux styles généraux de résumés qui couvrent la majorité des cas.

Souvenez-vous, dans cette discussion, nous voulons essayer et couvrir les généralités de 80-90% des styles de résumés humains (conventions sur la façons dont les personnes publient, que ce soit sur le web ou sur papier).

Aussi, cette page est destinée uniquement à documenter et analyser les exemples actuels de CV sur le Web, et décrire les formats de résumés communs. Pour l'analyse et les idées, voir [[resume-brainstorming-fr|résumé-brainstorming]].

=== autres styles de Résumés ===
* Voir [http://www.dummies.com/WileyCDA/DummiesArticle/id-636,subcat-JOB.html Choosing a resume format] pour un aperçu basique du format chronolique inversé (Reverse Chronological format (RC), le format Fonctionnel, le format Hybride, le format Réalisation, le format Ciblé, le format Linéaire, le format Professionnel, le format Mot-clé, le format Académique Curriculum Vitae (CV), le format International Curriculum et le format Portfolio.

== CV extraits de la jungle ==
=== Tantek Çelik ===
* [http://tantek.com/projects/resume.html Tantek Çelik] (a besoin d'être mis à jour, celui-là a environ deux ans)

==== Résumé ====

Tantek a une liste pour son Résumé en haut :
<blockquote><pre><nowiki>
<ul class="quals">
<li>
Manager & technical leader (10 years). Led and set direction for teams of up to 12.
</li>
...
</nowiki></pre></blockquote>

==== Emploi ====

Tantek listes ensuite son historique d'emploi :
<blockquote><pre><nowiki>
<h2>Employment & Products</h2>
<ol class="experience">
<li class="job" id="technorati">
<h3>2004 - present<a href="http://www.technorati.com" class="company">Technorati</a>,
<a href="http://maps.yahoo.com/py/maps.py?BFCat=&Pyt=Tmap&addr=665+3rd+St&csz=San+Francisco+CA+94107"
class="location">San Francisco, CA</a></h3>
<h4>2004 July - present
Senior Technologist.</h4>
Investigate and define new standards and new technologies companywide. Lead adoption of and implementation of valid
semantic XHTML and CSS across all web sites. A primary contributor to the design, development, and launch of
<a href="http://politics.technorati.com">politics.technorati.com</a> "Election Watch 2004" site in 13 days.
<div class="completed">
<h5>Websites Developed and Launched</h5>
<ul class="websites">
<li><a href="http://www.technorati.com/">Technorati main site</a> (valid XHTML+CSS green redesign, XHTML strict
update)</li>
<li><a href="http://politics.technorati.com/">Election Watch 2004</a> (initial valid XHTML+CSS release, XHTML
strict update with new Attention Index, Charts features)</li>
</ul>
</div>
</li>
</nowiki></pre></blockquote>

Les schéma implicite semble être (en sélecteurs CSS) :

<blockquote><pre><nowiki>
ol.experience
ol.experience li.job
ol.experience li.job .dates
ol.experience li.job .company
ol.experience li.job .jobtitle
ol.experience li.job .completed
ol.experience li.job .products
</nowiki></pre></blockquote>

Le réglage des .jobtitle, .completed et .products est répété pour les cas où il aurait plus d'une position dans la société.

==== brevets ====
Tantek a aussi une section sur les brevets :

<blockquote><pre><nowiki>
<div class="patents" id="patents">
<h2><abbr title="United States">US</abbr> Patents</h2>
<div class="issued">
<h3 class="sidelabel">Issued(6):</h3>
<ol>
<li id="PatNo5752056" value="5752056">
<h4>
<a href="http://patft.uspto.gov/netacgi/nph-Parser?d=PALL&p=1&u=%2Fnetahtml%2F
srchnum.htm&r=1&f=G&l=50&s1=5,752,056&OS=&RS=">
System for binding document parts and handlers by fidelity of parts or by automatic
translation of parts</a></h4>
<a class="altlink" href="http://www.delphion.com/details?pn=US05752056__">(delphion US05752056)</a>
<a class="inventor">[sole inventor]</a></li>
...
</nowiki></pre></blockquote>

Je ne vais pas plonger là-dedans, parce que je doute vraiment que ce soit suffisamment commun pour l'inclusion. --[[User:RyanKing|RyanKing]] 13:33, 18 Jan 2006 (PST)

==== Publications ====

<blockquote><pre><nowiki>
<div class="publications" id="publications">
<h2>Publications & Presentations</h2>

<h3 id="recs">Recommendations and Candidate Recommendations (CRs)</h3>
<ol>

<li>Çelik T.
"<a class="title" href="http://www.w3.org/TR/css3-ui">CSS3 Basic User Interface Module</a>"
<a class="publisher" href="http://w3.org/TR">W3C Technical Reports and Publications</a>
&lt;<a class="URL" href="http://www.w3.org/TR/2004/CR-css3-ui-20040511">http://www.w3.org/TR/2004/CR-css3-ui-20040511</a>&gt;
(2004)
</li>
</nowiki></pre></blockquote>

Le contenu défini pour le microformat citation fonctionne. Besoin d'analyse dans ce contexte. --[[User:RyanKing|RyanKing]] 13:33, 18 Jan 2006 (PST)

==== présentations ====
<blockquote><pre><nowiki>
<h3 id="presentations">Invited Presentations</h3>
<ol>
<li>Marks K, Çelik T.
"<a class="title" href="http://sdforum.org/SDForum/Templates/CalendarEvent.aspx?CID=1524"> Semantic XHTML:
Can your website be your API? - Using semantic XHTML to show what you mean</a>",
<a class="publisher" href="http://sdforum.org/"><abbr title="Software Development Forum">SD Forum</abbr></a>
<a class="event" href="http://www.sdforum.org/SDForum/Templates/Level1.aspx?pid=10117&sid=7">Web Services
<abbr title="Special Interest Group">SIG</abbr></a>,
eBay's Silicon Valley Conference Center 2161 North First Street San Jose, CA 95131
(28 September 2004)
</li>
...
</nowiki></pre></blockquote>

Tantek a une liste de présentations qui comprennent les noms des présentateurs, l'URL de l'événement, l'éditeur (semble être utilisé comme 'organizer'), l'URL de l'événement (par ex. conférence, atelier) et le nom, le lieu et la date.

==== Education ====
<blockquote><pre><nowiki>
<div class="education">
<h2>Education</h2>
<ol>
<li class="school">
<h3>20 June 2001<a href="http://www.edwardtufte.com/tufte/"
class="institution">Edward Tufte</a></h3>
<ul class="courses">
<li><a href="http://www.edwardtufte.com/tufte/courses">Presenting Data and Information</a></li>
</ul>
</li>
....
</nowiki></pre></blockquote>

Tantek liste ses études, en y incluant des 'dates', une liste de 'cours' qui comprennent le nom et l'URL optionnelle) et une liste de diplômes.

==== Récompenses ====
<blockquote><pre><nowiki>
<div class="awards" id="awards">
<h2>Awards</h2>
<ol>
<li>2004
<a href="http://2004.sxsw.com/interactive">SXSW interactive conference</a>,

<a href="http://2004.sxsw.com/interactive/panels/ratings04/">Top rated moderator (4.70 out of possible 5.0)</a>.</li>
</nowiki></pre></blockquote>

Liste avec dates, nom d'événement, url et nom de la récompense.

==== Centres d'Intérêts ====
<blockquote><pre><nowiki>
<div class="interests">
<h2>Other Interests</h2>
<ul>
<li>Alternative transport: skate, bicycle, motorcycle. Run? Only
<a href="http://www.asylumsfx.com/movies/belly.mov" target="m">when chased</a>.</li>
</nowiki></pre></blockquote>

==== Affiliations ====
<blockquote><pre><nowiki>
<h2>Member of</h2>
<ul><li><a href="http://www.cpsr.org">Computer Professionals for Social Responsibility (<abbr>CPSR</abbr>)</a> (life),</li>
</nowiki></pre></blockquote>

Liste d'affiliations/adhésions chacune avec URL et nom.

==== Schéma Global Implicite ====

Le schéma global implicite tel qu'illustré par cet exemple.

{|
! Field name !! description
|-
| summary || une liste de qualifications et compétences
|-
| employment || une liste de jobs, chacun incluant les dates, sociétés, titre du job, réalisations, produits
|-
| patents || une liste de brevets - en cours et accordés avec descriptions, une URL, la liste des inventeurs
|-
| publications || une liste des publications, chacun indiquant les auteurs, le titre, l'url et l'année de publication
|-
| presentations || une liste des présentations, chacune incluant les noms des présentateurs, le titre de la présentation, l'occasion/événément et le lieu
|-
| education || une liste, chaque itemp contenant la date (gamme), l'institution et une liste de cours, chacun avec des URLs et noms
|-
| awards || une liste des récompenses, chacun avec un nom, url et date
|-
| interests || une liste d'intérêts personnels
|-
| affiliations || une liste des affiliations, chacun avec un nom d'organisation, url et type d'association
|}

=== Dan Connolly ===
[http://www.w3.org/People/Connolly/misc/vita Dan Connolly] (a besoin d'améliorations à des fins de MIT ; a été GRDDL'd pour certains points)

==== Affilitations ====
Pour les affiliations, Dan a
<blockquote><pre><nowiki>
<div class="affiliation">
Research Scientist 
MIT Computer Science and Artificial Intelligence Laboratory (<a rel="aff"
href="http://www.csail.mit.edu/">CSAIL</a>)
</div>
</nowiki></pre></blockquote>

Schéma Implicite :
{|
! css selector !! semantics
|-
| div.affiliation || wrapper
|-
| div.affiliation em.position || the job position/title
|-
| div.affiliation b.org || the organization with which he is affiliated
|-
| div.affiliation b.org a[rel="aff"] || href is URL of the organization and textnode is an abbreviation of the organization name
|}

==== Contact ====
Pour l'information de contact :
<blockquote><pre><nowiki>
<div class="contact">
200 Technology Square
Cambridge, MA
02139 
<code class='homePageAddr'>http://www.w3.org/People/Connolly/</code>
</div>
</nowiki></pre></blockquote>

Dan a une série de <div>'s, (devrait être une liste, non ?), chacune avec ce schéma implicite :

{|
! css selector !! semantics
|-
| div.contact || wrapper
|-
| div.contact span.street || hcard:street-address?
|-
| div.contact span.city || hcard:locality ?
|-
| div.contact span.st || hcard:region ?
|-
| div.contact span.zip || hcard:postal-code ?
|-
| div.contact homePageAddr || hcard:url ?
|}

==== Education ====

<blockquote><pre><nowiki>
<h2>Education</h2>
</nowiki></pre></blockquote>
...followed by more affiliation <code>div</code>'s (see above).

Sous son entrée education, il a une liste de ce qui apparaît comme des honneurs/récompenses :

<blockquote><pre><nowiki>
<ul>
<li>National Merit Scholar</li>
<li>Natural Sciences <a
href="http://www.cs.utexas.edu/users/cline/dsbrochure.html">Dean's
Scholar</a></li>
<li><a href="http://www.arlut.utexas.edu/">Applied Research
Laboratories</a> Scholarship</li>
</ul>
</nowiki></pre></blockquote>

==== Publications ====

Section Publications :

<blockquote><pre><nowiki>
<h2>Selected Publications</h2>
<ul>
<li>Berners-Lee, Connolly, Swick, <a href="/1999/04/WebData"><cite>Web
Architecture: Describing and Exchanging Data</cite></a> (World Wide Web
Consortium Note, 1999)</li>
<li><dl>
<dt>Connolly, <a
href="http://helix.nature.com/webmatters/xml.html"><cite>The XML
Revolution</cite></a> Nature's <a
href="http://helix.nature.com/webmatters/">Web Matters</a>, Oct 1998 
</dt>
</dl>
</li>
....
</nowiki></pre></blockquote>

Cette liste de publications a des auteurs, URL et titre du travail.

==== Expérience Professionnelle ====

<blockquote><pre><nowiki>
<div>
<h2>Professional Experience</h2>
<ul>
<li>Domain Lead, W3C Architecture Domain, 1996-1998</li>
...
</nowiki></pre></blockquote>

A list of items, each with job title, the organization and a date range.

==== Présentations et Récompenses ====

<blockquote><pre><nowiki>
<div>
<h2>Selected Appearances and Awards</h2>
<ul>
<li><a
href="http://www.zdnet.com/intweek/printhigh/120897/top25.html"><cite>The
Top 25 Unsung Heroes Of The Net</cite></a> by <a
href="http://www.zdnet.com/intweek/">Inter@ctive Week</a> 1997</li>
....
</nowiki></pre></blockquote>

Une liste, chaque item avec URL, titre et publication/événement.

==== Schéma Implicite Global ====

Les schéma implicite du CV de Dan semble être :

{|
! field !! description
|-
| affiliations || a list of affiliations, current and past, each with organization info
|-
| contact info || current contact info including mailing address and URL
|-
| education || a list of affiliations, like above, then a list of honors/awards
|-
| publications || a list of citations
|-
| professional experience || a list of: title, timeframe, organization
|-
| appearances and awards || a list of events
|}

=== Mark Pilgrim ===
* http://diveintomark.org/about/resume/

==== Contact ====

Mark utilise un [[hcard-fr|hCard]] pour donner son information de contact :

<blockquote><pre><nowiki>
<div class="vcard">
<h1 class="fn">Mark Pilgrim</h1>
<address class="adr">
Apex, NC 
<a class="email" href="pilgrim@gmail.com">pilgrim@gmail.com</a> 
other contact information available upon request
</address>
</div>
</nowiki></pre></blockquote>

==== Statut ====

Mark déclare son statut acturel de recherche de travail/job :

<blockquote><pre><nowiki>
<h2>Status</h2>
seeking full-time employment in the Raleigh, NC area (telecommuting OK)
</nowiki></pre></blockquote>

==== Publications ====

Une liste de publications :

<blockquote><pre><nowiki>
<h2>Publications</h2>
<ul>
<li><cite>Greasemonkey Hacks</cite> – 2005, O'Reilly Media.</li>
<li><cite>Dive Into Python</cite> – 2004, Apress. Also available for free online
at <samp><a href="http://diveintopython.org/">diveintopython.org</a></samp>.
The book was written in DocBook XML and transformed into HTML, PDF, Word, Windows
Help, and plain text with XSL stylesheets. It has been translated into six languages.</li>
<li>Columns on <cite>XML.com</cite> – 2002-2004, O'Reilly Media. Full list at
<samp><a href="http://xml.com/pub/at/25">xml.com/pub/at/25</a></samp></li>
</ul>
</nowiki></pre></blockquote>

==== Projets/Publications ====

Plus de publications et de projets open source :

<blockquote><pre><nowiki>
<h2>Open Source and 
Self-Publications</h2>
<ul>
<li><cite>Universal Feed Parser</cite> – <samp><a href="http://feedparser.org/">
feedparser.org</a></samp> – parse RSS and Atom feeds in Python</li>
<li><cite>Feed Validator</cite> – <samp><a href="http://feedvalidator.org/">
feedvalidator.org</a></samp> – validate RSS and Atom feeds</li>
<li><cite>Dive Into Greasemonkey</cite> – <samp><a href="http://diveintogreasemonkey.org/">
diveintogreasemonkey.org</a></samp> – a book on remixing web sites with JavaScript</li>
<li><cite>Dive Into Accessibility</cite> – <samp><a href="http://diveintoaccessibility.org/">
diveintoaccessibility.org</a></samp> – a book on web accessibility techniques</li>
<li>Python web services libraries – <samp><a href="http://diveintomark.org/projects/">
diveintomark.org/projects</a></samp></li>
<li>Screencasts (video tutorials) – <samp><a href="http://howto.diveintomark.org/">
howto.diveintomark.org</a></samp></li>
</ul>
</nowiki></pre></blockquote>

==== Expérience Professionnelle ====
<blockquote><pre><nowiki>
<h2>Professional Experience</h2>

<div class="employer">
<h3>March 2004 – present, accessibility architect at IBM</h3>
<ul>
<li>Implemented advanced web accessibility in AJAX applications using Firefox 1.5 and
WindowEyes screenreader. Co-wrote best practices guidelines for these techniques.</li>
<li>Wrote developer guidelines for creating accessible applications and custom graphical
controls in SWT-based Eclipse applications.</li>
<li>Designed accessibility API for OpenOffice.org-based office suite. Coordinated with
Freedom Scientific (assistive technology vendor) and development team to ensure interoperability.</li>
</ul>
...
</nowiki></pre></blockquote>

Plusieurs <code><div></code>'s de <code>class="employer"</code>, chacune avec des espaces temps et listes de réalisations.

==== Education ====
<blockquote><pre><nowiki>
<h2>Education</h2>
<h3>June 1995, Earlham College</h3>
BA of philosophy, 3.8 GPA
</nowiki></pre></blockquote>

==== Schéma global implicite ====
{|
! field !! description
|-
|contact || info de contact actuelle, déjà un [[hcard-fr|hCard]]
|-
|status || texte décrivant la disponibilité professionnelle
|-
|publications || liste de citations
|-
|projects/ Self-Publications || une liste des projets (w/ URLs) et livres publiés en ligne
|-
|professional Experience || une liste des jobs, chacun avec des cadres temporels et réalisations
|-
|education || une lsite : école, date de diplôme, degré et GPA
|}

=== Eran Globen ===
http://hellonline.com/resume.html

==== Objectif ====

<blockquote><pre><nowiki>
<h2>Objective</h2>

Pursuing a hands-on...
</nowiki></pre></blockquote>

==== Résumé ====

<blockquote><pre><nowiki>
<h2>Summary</h2>

Software engineer with
over 7 years experience in all...
</nowiki></pre></blockquote>

==== Expérience Professionnelle ====

<blockquote><pre><nowiki>
<h2>Professional Experience</h2>

2001-Present: limbo Technologies 
Chief Technology Officer
 
Provided services to several companies on various projects in several fields
including scaling of web server farms, security planning and auditing and
updating ASP based applications to ASP.NET technology.
...
</nowiki></pre></blockquote>

Appears to be a list of:

* time range
* company
* job title
* description

==== Education/ Militaire ====
<blockquote><pre><nowiki>
<h2>Education and Military Service</h2>

Tel Aviv Univeristy 
Computer Science 
Graduated with Bachelor's Degree (BSc.) 

Israeli Defense Force 

Army Intelligence Core 
Honorable Discharge in 1996 for one full standard term of Isreali Military Service. 
...
</nowiki></pre></blockquote>

Liste les organisations (école, militaire), diplôme.

==== Intérêts ====
<blockquote><pre><nowiki>
<h2>Related Knowledge and Interests</h2>

Platforms: Administrative knowledge of Window NT through
Server2003. Working knowledge of Linux 2.2.19 to current. 

Database: MS-SQL Server 6.5-2k nearing DBA level, MS-Access, working knowledge of Oracle Database Systems.

Languages: VB, VBScript, Java, C, C++, C#, (T-)SQL, WML, XML, and Perl. 

Technologies: ADO, ASP, ASP.NET, COM, WAP, Client/Server; Expansive knowledge
of networking, specifically TCP/IP, with a strong interest in systems and
network security 

Current Studies and Interests: 
Expansive knowledge of networking, specifically
TCP/IP, with a strong interest in systems and network security. Also interested
in wireless, including cellular and Ethernet based internet technologies including
Location Based Services and Wireless Gaming. 
...
</nowiki></pre></blockquote>

Un ensemble de centres d'intérêts groupés par catégories.

==== Schéma Implicite Global ====

{|
! field !! summary
|-
|objective || text describing career goals
|-
|summary || an overview of qualifications
|-
|professional Experience || list of employment, each as an event
|-
|education/ Military || list of education and military service, each with title/degree, org and timeframe
|-
|interests || text describing current interests
|}

=== Tara Hunt ===
http://horsepigcow.com/tararesume.htm

==== Contact Info ====
(balisage simplifié pour protéger le coupable --[[User:RyanKing|RyanKing]] 15:38, 19 Jan 2006 (PST))
<blockquote><pre><nowiki>
<div align="left">
762 Adelaide West, Toronto,
ON M6J 1B1 
e. <a href="mailto:tara@roguestrategies.com">tara@roguestrategies.com</a>
w. <a href="http://www.roguestrategies.com" target="_blank">www.roguestrategies.com</a> 
c. 416-837-8972 h. 416-703-5391 


</div>
</nowiki></pre></blockquote>

==== Résumé ====

<blockquote><pre><nowiki>
<td>We
live in the world of uber-savvy consumers and never-ceasing media inundation.
It is simple to have a market presence, but nearly impossible to make a
market connection. These connections are what today's entrepreneur requires
to survive. Creating authentic bonds is at the core of every one of my strategies.
This is marketing uncommon.</td>
</nowiki></pre></blockquote>

==== Qualifications ====
<blockquote><pre><nowiki>
I AM QUALIFIED
I have experience in each of the following areas:
...
<ul ...>
<li>e-Marketing (e-Content Development) 
<li>CMS (Content Management)
...
</nowiki></pre></blockquote>

==== Education ====
<blockquote><pre><nowiki>
I AM EDUCATED 
Bachelor of Arts (Communications & Culture) - University of Calgary 1994-1999
</nowiki></pre></blockquote>

==== Qualifications / Experience ====
<blockquote><pre><nowiki>
<font...>I AM VERSATILE 
Computer Programs:
Microsoft CMS, Adobe Photoshop CS, Illustrator CS, Acrobat 6, Macromedia Flash
MX, Dreamweaver 4, Fireworks 4, HTML, DHTML, XML, Javascript, CSS, Microsoft
Word, Excel, Outlook, PowerPoint, FrontPage, Access, Project, CMS - Mac &
PC platforms.
Public Speaking Experience:
Delivered academic papers, developed and presented a self-branding seminar,
and enjoy networking and speaking to groups of people.
...
</nowiki></pre></blockquote>

==== Portfolio ====
<blockquote><pre><nowiki>
Designed recently:
...
<li><a href="http://www.joestiff.com" target="_blank">www.joestiff.com</a> 
...
</nowiki></pre></blockquote>

==== Expérience Professionnelle ====
<blockquote><pre><nowiki>
I AM A PROFESSIONAL 
HR PROFESSIONALS ASSOCIATION OF ONTARIO 2003 - current 
New Media Manager (www.hrpao.org)
SKILLS USED: New media management,
digital marketing, brand development, strategic planning, budgeting, project
management, customer relationship management, market research, trend analysis,
copywriting/editing, presentation development & delivery, web design
At HRPAO, I: 
<ul type="square">
<li>pilot and manage a major
Content Management System (CMS) changeover/upgrade 

...
</ul>
</nowiki></pre></blockquote>

==== Affiliations ====
<blockquote><pre><nowiki>
CURRENT PROFESSIONAL
AFFILIATIONS 
Canadian Marketing Association (CMA) 
Second Wind Network 
Creative Class 100 - www.creativeclass.org
</nowiki></pre></blockquote>

==== publications ====
<blockquote><pre><nowiki>
RECENTLY PUBLISHED 
Business in the Blogosphere: Conference & Corporate Blogging as a Marketing Tool 
Marketing Watchdog Journal, May 2005
</nowiki></pre></blockquote>

==== Schéma Global Implicite ====

{|
! field !! summary
|-
|contact info || contact info - address, email, url
|-
|summary || summary of qualification
|-
|qualifications || list of qualification
|-
|education || list of education events, includes school, timeframe, school location
|-
|qualifications?/Experience || list of skills and tools
|-
|portfolio || list of URLs and titles
|-
|professional Experience || a list of job events
|-
|affiliations || a list of URL/name of organization
|-
|publications || a list of citations
|}

=== Casey Conroy ===
http://caseyconroy.com/a_resume.html

==== Expérience Professionnelle ====
<blockquote><pre><nowiki>
PROFESSIONAL EXPERIENCE 

GRAPHIC DESIGNER, Webster University 
August 2004–present 
Responsible for the design and production of one- two- and four-color printed and interactive publications.
Also responsible for vendor and account management. All clients are internal. 
</nowiki></pre></blockquote>

Comprend : titre du job, organisation, date de début et date de fin et un résumé.

==== Education ====

<blockquote><pre><nowiki>
EDUCATION 
Missouri State University 
BFA in Design, magna cum laude, December 2001 
Dual Emphasis: Graphic Design and Illustration 
</nowiki></pre></blockquote>

Comprend : nom de l'école, diplôme reçu, honneurs, date de diplôme et résumé des études.

==== Compétences Professionelles ====
<blockquote><pre><nowiki>
PROFESSIONAL SKILLS (Macintosh Platform) 
ADOBE: Illustrator, ImageReady, InDesign, Photoshop, Streamline 
MACROMEDIA: Dreamweaver, Fireworks, Flash, FreeHand 
MICROSOFT: Excel, PowerPoint, Word 
OTHER: BBEdit, QuarkXPress 
PROGRAMMING LANGUAGES: HTML, CSS 
</nowiki></pre></blockquote>

Une liste de compétences et outils.

==== Travaux Publiés ====
<blockquote><pre><nowiki>
PUBLISHED WORK 
CMYK magazine, issue #19, 2002, Design Annual 
Print magazine, September/October, 2002, Continental Shift 
</nowiki></pre></blockquote>

Une liste des publications, avec l'information de publication.

==== Exhibitions ====
<blockquote><pre><nowiki>
EXHIBITIONS 
AIGA Design Show Nine, Saint Louis: Fall 2002 
University & College Designers Association, British Columbia: Spring 2001 
</nowiki></pre></blockquote>

==== Memberships ====
<blockquote><pre><nowiki>
MEMBERSHIPS 
American Institute of Graphic Arts 
</nowiki></pre></blockquote>

Une liste des organisations dans lesquelles il est membre.

==== Schéma Implicite Global ====

{|
! field !! description
|-
| professional Experience || a list including title, organization, timeframe and a description
|-
| education || a list including organization (school), degree, honors, graduation date and area of study
|-
| professional Skills || an outline of skills/tools broken down by general categories
|-
| published Work || a list of citations
|-
| exhibitions || a list of events
|-
| memberships || a list of organizations
|-
|}

=== Brian Suda ===
http://suda.co.uk/cv/

==== Objective ====
<blockquote><pre><nowiki>
<h2 id="objective">Objective</h2>
I am currently looking to work full-time in an environment that allows me to use both my technical and
creative backgrounds. I am seeking a position that does not have a rigid structure or inflexible goals, but
one which allows me to create new initiatives.
</nowiki></pre></blockquote>

==== Education ====

<blockquote><pre><nowiki>
<h2 id="education">Education</h2>

<a class="ex-ref" href="http://www.ed.ac.uk" title="Master of Science, Computer Systems and Software Engineering">
The University of Edinburgh</a> 
Edinburgh, Scotland 
Master of Science, 
Informatics, Computer Science 

</nowiki></pre></blockquote>

Includes degree, school, location.

==== Employment ====
<blockquote><pre><nowiki>
<h2 id="employment">Employment</h2>

9/01–9/02, 1/05–Present 
Technology Developer 
<a class="ex-ref" href="http://www.google.com/search?hl=en&lr=&ie=ISO-8859-1
&q=paradigm+new+media+group" title="Technology Developer">Paradigm New Media Group</a> 
Saint Louis, <abbr title="Missouri">MO</abbr> <abbr title="United States of America" class="initialism">USA</abbr>
 

</nowiki></pre></blockquote>

Includes the start and end date, job title, company url, company name and company location.

==== Overall Implied Schema ====

{|
! !!
|-
|objective || a summary of career goals
|-
|education || a list including the school (organization), the degree/program and the location
|-
|employment || a list including the organization, timeframe, job title and location
|}

== Experiences en microfomatage ==
* [http://cs.usfca.edu/~rking/resume.html ryan king]
* [http://cs.usfca.edu/~rking/niall.html Niall Kennedy] (microformaté par RyanKing)
* Mon CV utilise hCard, hCalendar, XFN, et rel-license : http://edward.oconnor.cx/resume/ [[User:EdwardOConnor|EdwardOConnor]]
* [http://steve.ganz.name/resume/resume.html Steve Ganz] - Chantier en cours, utilisant actuellement [[hcard-fr|hCard]], [[hcalendar-fr|hCalendar]] et un peu [http://gmpg.org/xfn/ XFN]. Là où il n'y avait pas de microformat approprié existant à tirer, j'ai regardé sur [http://xmlresume.sourceforge.net/ XML Resume] pour la sémantique ou simplement improvisé (class="qualifications"). J'ai aussi créé quelques valeurs de type liens personnalisées : rel="employer current" et rel="employer former" (pas de profil à cette heure).
* [http://maetl.coretxt.net.nz/cv/ Mark Rickerby] - un CV écrit durant la première semaine de 2006
* [http://xavierroy.com/resume/ Xavier Roy] - un échantillon de cv bricolé et copié à partir de différentes sources incluant celles au-dessus...

== Analyse Regroupée ==
La table ci-dessous est un tri/fusion des tables au-dessus "Overall Aggregate Analysis".
Ceci devrait faire sortir là où nous avons des irrégularités à travers les exemples.

{|
! affiliations/memberships
|-
|affiliations || a list of affiliations, current and past, each with organization info
|-
|affiliations || a list of affiliations, each with organization name, url and association type
|-
|affiliations || a list of URL/name of organization
|-
|memberships || a list of organizations
|-

! appearances/awards
|-
|appearances and awards || a list of events
|-
|awards || a list of awards, each with name, url and date
|-

! contact info
|-
|contact || current contact info, already an hcard
|-
|contact info || contact info - address, email, url
|-
|contact info || current contact info including mailing address and URL
|-

! education/military
|-
|education || a list including organization (school), degree, honors, graduation date and area of study
|-
|education || a list including the school (organization), the degree/program and the location
|-
|education || a list of affiliations, like above, then a list of honors/awards
|-
|education || a list of: school, graduation date, degree and GPA
|-
|education || a list, each item including the date (range), the institution and a list of courses, with a URLs and names
|-
|education || list of education events, includes school, timeframe, school location
|-
|education/ military || list of education and military service, each with title/degree, org and timeframe
|-

! employment/professional experience
|-
|employment || a list including the organization, timeframe, job title and location
|-
|employment || a list of jobs, each including dates, company, jobtitle, completed, products
|-
|professional experience || a list including title, organization, timeframe and a description
|-
|professional experience || a list of job events
|-
|professional experience || a list of jobs, each with timeframes and accomplishments
|-
|professional experience || a list of: title, timeframe, organization
|-
|professional experience || list of employment, each as an event
|-

!exhibitions
|-
|exhibitions || a list of events
|-

! interests
|-
|interests || a list of personal interests
|-
|interests || text describing current interests
|-

! objective
|-
|objective || a summary of career goals
|-
|objective || text describing career goals
|-

!patents
|-
|patents || a list of patents- pending and granted with descriptions, a URL, list of inventors
|-

! portfolio
|-
|portfolio || list of URLs and titles
|-

! presentations
|-
|presentations || a list of invited presentations, each including presenters names, the presentation's title, the occassion/event and location
|-

! skills
|-
|professional skills || an outline of skills/tools broken down by general categories
|-

!publications
|-
|publications || a list of citations
|-
|publications || a list of citations
|-
|publications || a list of writings, each including author(s), title, url and published year
|-
|publications || list of citations
|-
|published work || a list of citations
|-
|projects/ self-publications || a list of projects (w/ URLs) and books published online
|-

! qualifications
|-
|qualifications || list of qualification
|-
|qualifications/experience || list of skills and tools
|-

! status
|-
|status || text describing work availability
|-

! summary
|-
|summary || a list of qualifications and competencies
|-
|summary || an overview of qualifications
|-
|summary || summary of qualification
|-
|}

== Exemples de Diplômes ==

Il a été suggéré que hResume inclut les diplômes/certificats. Voir [http://microformats.org/discuss/mail/microformats-discuss/2006-June/004364.html]

Cette section est destinée à ajouter des exemples de diplômes.

== Premier Exemple ==
==== Emploi ====
<blockquote><pre><nowiki>
l'exemple de syntaxe va ici
</nowiki></pre></blockquote>

Rapide description ici.

== Voir aussi ==
{{hresume-related-pages-fr}}

rel-license-fr

2009-01-05T10:40:05Z

Brian: Reverted edits by AcelvArroa (Talk) to last version by ChristopheDucamp

= rel="license" =

Rel-License est un format simple, ouvert pour indiquer les licences de contenus qui sont embarquables dans le (X)HTML, Atom, RSS, et le XML arbitraire. Rel-License est l'un des nombreux [[microformats-fr|microformats]] standards ouverts.

__TOC__

== Spécification 06-02-2005 ==
=== Auteur ===
[http://tantek.com/ Tantek Çelik], ([http://technorati.com Technorati, Inc.], précédemment chez [http://microsoft.com/ Microsoft Corporation])
(traduction française [[Christophe Ducamp]])
=== Copyright ===
Selon la release dans le domaine public sur [[User:Tantek|ma page utilisateur]], cette spécification est diffusée dans le domaine public.

{{MicroFormatPublicDomainContributionStatement-fr}}

=== Patents ===
{{MicroFormatPatentStatement-fr}}

== Abstract ==
Rel-License est l'un des nombreux MicroFormats. En ajoutant <code>rel="license"</code> à un hyperlien, une page indique que la destination de cet hyperlien est une licence pour la page en cours, par exemple pour l'hyperlien suivant :

<pre><nowiki>
<a href="http://creativecommons.org/licenses/by/2.0/" rel="license">cc by 2.0</a>
</nowiki></pre>

L'auteur indique que la page est sous une licence Creative Commons Paternité 2.0.

== Plusieurs Licences ==
Plusieurs hyperliens comme rel="license" indiquent que la page est disponible sous n'importe laquelle des licences mises en référence. Par exemple, les hyperliens suivants pourraient être utilisés pour déclarer qu'une page est disponible soit sous une licence "Creative Commons Paternité 2.0" ou une licence Apache 2.0 :

<pre><nowiki><a href="http://creativecommons.org/licenses/by/2.0/" rel="license">cc by 2.0</a>
<a href="http://www.apache.org/licenses/LICENSE-2.0" rel="license">Apache 2.0</a></nowiki></pre>

== Profil XMDP ==
<pre><nowiki>
<dl class="profile">
<dt id="rel">rel</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel">
Définition HTML4 de l'attribut 'rel'.</a>
Voici une valeur supplémentaire.
<dl>
<dt id="license">licence</dt>
<dd>Indique que la ressource référencée est une licence pour la page de référence.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== Implémentations ==
* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] extrait du [http://webstandards.org/ Web Standards Project] permet la publication de liens rel-license à partir de Dreamweaver 8. Inclut les (cc) par défaut.
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] est un plugin pour [http://textpattern.com/ Textpattern] qui supporte l'embarquement de rel-license et d'autres microformats dans les gabarits et billets de blogs. Ecrit par [http://placenamehere.com/ Chris Casciano].
* [http://creativecommons.org/license/ Choix de Licence Creative Commons (cc)]
* [http://search.yahoo.com/cc Recherche Yahoo! (cc)] (semble prendre le link-rel dedans pas d'éléments liens)
* [http://www.google.com/support/bin/answer.py?answer=29508 Google "Usage Rights" search] (semble aussi prendre le link-rel dedans pas d'éléments liens)

== Liste de Licences ==
''Ajoutez svp toutes les licences qui pourraient s'avérer ici utiles.''
* [http://creativecommons.org CC]
** [http://fr.creativecommons.org/ CC] en français
* [http://www.opensource.org/licenses/ Open Source Initiative] licences -- essentiellement centrées sur le logiciel
* [http://fr.wikipedia.org/wiki/Licence_Art_Libre licence art libre] (fr)

== Réferences ==
=== Références Normatives ===
* [http://gmpg.org/xmdp/ XMDP]

=== Références "Informatives" ===
* 20040211 rel="license" a d'abord été proposée en présentation [http://tantek.com/presentations/2004etech/realworldsemanticspres.html real world semantics] à "2004 O'Reilly Emerging Technologies Conference", San Diego, CA, USA.
* 20040225 [http://tantek.com/log/2004/02.html#d25t1805 Thorough discussion of rel="license"] couvre les avantages et possibilités de présentations.
* [http://creativecommons.org/licenses/by/2.0/deed.fr Licence Creative Commons Paternité 2.0]
* [http://www.apache.org/licenses/LICENSE-2.0 Licence Apache 2.0]
* contribution provenant de http://developers.technorati.com/wiki/RelLicense
* [http://microformatique.com/?p=60 Know your rel-license at Microformatique]

== Voir aussi ==
* Voir [[rellicense-issues-fr|problématiques rel-license]] pour les problématiques qui ont été soulevées par ce [[microformat-fr|microformat]].
* [[rel-faq-fr|rel-faq]]

relenclosure

2009-01-05T10:40:03Z

Brian: Reverted edits by DelouGetsi (Talk) to last version by RyanKing

#REDIRECT [[rel-enclosure]]

rel-license-pt-br

2009-01-05T10:40:00Z

Brian: Reverted edits by DroncHialc (Talk) to last version by Token

= rel="license" =

'''Rel-License''' é um simples e aberto microformato para indicação de conteúdo de licença que estiver embutido em um (X)HTML, Atom, RSS e o arbitrário XML.

Rel-License é um dos muitos [[microformats-pt-br|microformatos]] de padrão aberto.

__TOC__

== Especificação 2005-02-06 ==
=== Autor ===
[http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.] (anteriormente da [http://microsoft.com/ Microsoft Corporation])

=== Copyright ===
{{MicroFormatCopyrightStatement2004}}

=== Patentes ===
{{MicroFormatPatentStatement}}

== Sumário ==

Rel-License é um dos muitos MicroFormatos. Por inclusão <code>rel="license"</code> é para um hyperlink, uma página indica que o destino daquele hyperlink é licenciado para a página atual. Ex. com o seguite hyperlink:

<pre><nowiki>
<a href="http://creativecommons.org/licenses/by/2.0/" rel="license">cc by 2.0</a>
</nowiki></pre>

o autor indica que a página está licenciada sob Creative Commons 2.0 Attribution Required license.

== Multiplas Licenças ==
Multiple such rel="license" hyperlinks indica que a página está disponível sobre alguma licença referida. Ex:. a seguinte licença poderia ser usada para declarar que a página está disponível sob Commons 2.0 Attribution Required ou licença Apache 2.0:

<pre><nowiki><a href="http://creativecommons.org/licenses/by/2.0/" rel="license">cc by 2.0</a>
<a href="http://www.apache.org/licenses/LICENSE-2.0" rel="license">Apache 2.0</a></nowiki></pre>

== XMDP profile ==
<pre><nowiki>
<dl class="profile">
<dt id="rel">rel</dt>
<dd>
<a rel="help" href="http://www.w3.org/TR/html401/struct/links.html#adef-rel">
HTML4 definition of the 'rel' attribute.</a>
Here is an additional value.
<dl>
<dt id="license">license</dt>
<dd>Indicates that the referred resource is a license for the referring page.</dd>
</dl>
</dd>
</dl>
</nowiki></pre>

== Implementações ==
* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of rel-license links from within Dreamweaver 8. Includes (cc) defaults.
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding rel license and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* [http://creativecommons.org/license/ Creative Commons (cc) license chooser]
* [http://search.yahoo.com/cc Yahoo! (cc) search]
* [http://www.google.com/support/bin/answer.py?answer=29508 Google "Usage Rights" search]

== Referencias ==
=== Referencias Normativa ===
* [http://gmpg.org/xmdp/ XMDP]

=== Referencias Informativas ===
* 20040211 rel="license" primeira proposta na apresentação [http://tantek.com/presentations/2004etech/realworldsemanticspres.html semantica no mundo real] em 2004 O'Reilly Emerging Technologies Conference, San Diego, CA, USA.
* 20040225 [http://tantek.com/log/2004/02.html#d25t1805 Completa discussão de rel="license"] incluindo vantagens e apresentação de possibilidades.
* [http://creativecommons.org/licenses/by/2.0/ Creative Commons 2.0 By (Attribution Required) license]
* [http://www.apache.org/licenses/LICENSE-2.0 Apache 2.0 license]
* Contribuido de http://developers.technorati.com/wiki/RelLicense

== ver também ==
* Veja [[rellicense-issues]] para assuntos o qual tem sido levantado com esse [[microformats|microformato]].

book-info-formats

2009-01-05T10:39:58Z

Brian: Reverted edits by CcnoaCelta (Talk) to last version by NaBrown78

== The book-info microformat ==
In discussions about the [[hReview]] microformat, it has been suggested that it would be useful to have a book-info format to markup book metadata. This page is dedicated to developing such a format. The [[book-info-examples]] page has examples of pages that present book information, particularly reviews.

See also [[citation]]. In fact, books are entirely covered by [[citation]], so efforts should be focused on finalizing that format.

== Book metadata ==
Information about a book commonly includes:
* book title
* book author - see [[hcard|hCard]]
* book editor(s) - see [[hcard|hCard]]
* book translator - see [[hcard|hCard]]
* classification (e.g. fiction, non-fiction)
* cover thumbnail
* price - see proposed [[currency]] microformat
* publisher - see [[hcard|hCard]]
* date of publication
* number of pages
* ISBN

issues

2009-01-05T10:39:57Z

Brian: Reverted edits by VarbaSleto (Talk) to last version by Brian

<h1> Microformat Issues </h1>
{{TOC-right}}
These are externally raised issues about microformats in general (these issues MUST apply to more than one microformat, which MUST be explicitly listed, otherwise the issue should be raised on the format specific issues page) with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec. Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/log/ Tantek]

As this is a general microformats issues page, please only note ''concrete'' real world issues. Theoretical issues will be deleted, as will any issues raised that do not contain documentation of specific real-world examples that use real-world microformats (not just brainstorms).

== Closed Issues ==
Resolved issues that have no further actions to take. These will likely be moved to a separate page like [[microformats-issues-closed]].

* 2005-07-?? raised by Bud(?).
*# ''Documents with user-generated content are hard to parse, and microformats present particular parsing challenges.''
*#* REJECTED. This is a straw man issue.
* 2005-07-13T19:44-07:00 raised by [[User:Bud|Bud]]
*# Follow-up to previous issue: ''Tantek needs to supply some justification for why this is a strawman as every developer I have talked to has raised it. It may be that the solutions described below are sufficient to solve the issue. More neutral statements to that effect might be more constructive.''
*#* REJECTED. Bud, saying "particular parsing challenges", without stating them is meaningless. Hence strawman. I think you may be mistaking questions for issues.

== Resolved Issues ==
Issues that are resolved but may have outstanding [[to-do]] items. As issues are resolved, they will be moved from the top of the [[microformats-issues#Issues|Issues list]] to the bottom of this section.
* ...

== Issues ==
=== Format Specific Issues ===

Please raise format specific issues on the respective page:

* [[citation-issues]]
* [[hatom-issues]]
* [[hcard-issues]]
** [[representative-hcard-issues]]
* [[hcalendar-issues]]
* [[hlisting-issues]]
* [[hresume-issues]]
* [[hreview-issues]]
* [[rel-issues]]
** [[rel-home-issues]]
** [[rel-license-issues]]
* [[vote-links-issues]]
* [[xfn-issues]]
* [[xfolk-issues]]
* [[xmdp-issues]]
* [[xoxo-issues]]
** [[xoxo-opml-issues]]
* etc.

=== Pattern Specific Issues ===

Please raise pattern specific issues on the respective page:

*[[abbr-design-pattern-issues]]
* [[datetime-design-pattern#Accessibility_issues]]
*[[include-pattern-issues]]
* etc.

=== IP Issues ===
* 2006-12-08 raised by [[User:AndyMabbett|Andy Mabbett]].
*# As evidenced in [http://microformats.org/discuss/mail/microformats-discuss/2006-December/007531.html discussion of an emailed response from eBay], the current position on the IP rights relating to microformats is unclear, or at least not clearly expressed. It seems to me that there should be an unambiguous statement of the current position, either for each individual format, or collectively, on a page to which people with concerns may be directed.
*#* ACCEPTED. A clearer statement of both copyright and patents both in specific specs and in general would be a good thing. In general, the end result that our current copyright/patent statements seek is Creative Commons, W3C, and IETF compatibility in terms of both copyrights, and royalty free patent policies. I [[to-do#Tantek|will work]] on this [[User:Tantek|Tantek]] 11:58, 9 Dec 2006 (PST)
*#** {{OpenIssue}} This appears to be unresolved; and in the light of, for example, [[hCard#Copyright the hCard 'spec']], the statement in the FAQ that "[http://microformats.org/wiki/faq#Q:_Who_controls_microformats.3F Microformats are open standards licensed under Creative Commons Attribution]" to be, at best, erroneous and misleading. [[User:AndyMabbett|Andy Mabbett]] 11:04, 10 Mar 2007 (PST)
*#**Also [http://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Attribution&curid=7391090&diff=117538680&oldid=117536621 causing concern here]. '''Prompt resolution would be advisable''' [[User:AndyMabbett|Andy Mabbett]] 09:04, 24 Mar 2007 (PDT)
*#*** First, [[citation]] is not ready for use in Wikipedia anyway. Second, what is unclear about the Creative Commons/W3C/IETF license and patent statements? This appears to be a theoretical issue / nitpick. Yes, things can be made clearer, but "erroneous" and "misleading" are inaccurate labels.
*#*** This is not a citation issue. For example, [[hcard#Copyright|hCard's current copyright statement]] is not compatible with the Creative Commons license: <blockquote>{{MicroFormatCopyrightStatement2004}}</blockquote> If you look at the wikicode, this is actually the "MicroFormatCopyrightStatement2004" default microformat copyright.--[[User:JoeAndrieu|JoeAndrieu]] 15:09, 24 Mar 2007 (PDT)

* Further to the above (but out-dented for clarity), [[hresume|hResume]] cedes copyright to "the authors": "This specification is (C) 2006 by the authors"; and names just one author; Ryan King. What legal standing does the "the authors (sic) intend to submit..." clause have? What exists, to reassure someone (or some mega corporation's lawyers) contemplating or already using hResume that they won't be invoiced by Mr King? Why aren't the other people who contributed to that spec jointly credited with its copyright? [[User:AndyMabbett|Andy Mabbett]] 17:34, 24 Mar 2007 (PDT)

*Also, there appears to be nothing on [[buttons]] to say that they're freely licensed, or public-domain. [[User:AndyMabbett|Andy Mabbett]] 03:01, 25 Mar 2007 (PDT)

=== Legal Entity Issues ===
2007-03-24 raised by [[User:JoeAndrieu|Joe Andrieu]], clarified by [[User:Rohit|Rohit Khare]] on 2007-03-27.
# What is the legal entity responsible for operating microformats.org?
#* [[User:Rohit|Rohit Khare]] originally registered the microformats.com and .org domain names on 2005-01-25 and [http://commerce.net| CommerceNet, LLC], a non-profit 'think tank' with a long history as a neutral sponsor for developing standards for Internet commerce (often, in conjunction with other formal standards bodies). CommerceNet currently underwrites the server hosting costs and, in the past, has co-ordinated donations with other sponsors for events such as the [http://microformats.org/blog/2006/06/16/microformatsorg-anniversary-party/|first anniversary party], the [http://wiki.commerce.net/wiki/ZCommerceWS#Microformats workshop] where the site was launched, and promotional items.
# What is the legal entity responsible for the intellectual property on microformats.org?
#* The current [[Template:MicroFormatCopyrightStatement|microformats copyright statement]] recognizes that IP is originally vested in the author(s), who are then expected to share those rights with the community by permitting their redistribution on microformats.org's wiki, blog, and mailing list archives. The additional distinction of becoming a specification may come with additional obligations to redistribute IP, such as a formal Creative Commons copyright license and a royalty-free patent license. The community is currently encouraging contibutors to [http://microformats.org/discuss/mail/microformats-discuss/2007-July/010221.html voluntarily adopt a public domain release].
#* Note that CommerceNet, LLC does ''not'' exercise any editorial control over the content of the site, mailing list, specifications, or the process, nor does it accept funds on behalf of microformats.org (see the [[Microformats:General_disclaimer|disclaimer]]). Conversely, the [[faq#Q:_Who_controls_microformats.3F|Admins]] do not have any independent legal identity at present, such as a partnership, foundation, or corporation. Please refer any legal questions or concerns directly to [mailto:rohit@khare.org Rohit Khare] before raising them as a matter of public record, as discussed on the mailing list [http://microformats.org/discuss/mail/microformats-discuss/2006-November/007086.html].

=== Governance Issues ===
:See: [[governance-issues]]

===Miscellaneous issues===

<div class="vevent">
* {{OpenIssue}} 2006-10-17 raised by [[User:AndyMabbett|Andy Mabbett]] on [[wiki-feedback]]; moved here 2007-03-10.
<div class="description">
*# What is currently described as a "specification" on [[hCard]] and [[hCalendar]] is no such thing.
*# Andy, what would it take to turn it into a "specification"?--[[User:JoeAndrieu|JoeAndrieu]] 15:13, 24 Mar 2007 (PDT)
*# [Belated response; only just seen the question!] - for a start, removal of user commentary; versioning. [[User:AndyMabbett|Andy Mabbett]] 02:37, 14 Jan 2008 (PST)</div>
</div>

<div class="vevent">
* {{OpenIssue}} 2008-02-04 raised by [[User:ManuSporny|Manu Sporny]]
<div class="description">
*# See [[namespaces-inconsistency-issue]]
</div>
</div>

See also:
*[[accessibility-issues]]
*[[code-issues]]
*[[external-issues]]
*[[tests-issues]]

=== New Issues ===

* {{OpenIssue}} 2007-04-01 raised by [[User:AndyMabbett|Andy Mabbett]].
*# Shouldn't microformats be recognised on <code>ID</code> as well as <code>class</code>? In other words, if I know I'm gong to have only one review or only one location, or whatever, on a page, then <code>"id=hReview"</code>, <code>id="geo"</code> etc. are semantically valid and appropriate. [[User:AndyMabbett|Andy Mabbett]] 11:32, 1 Apr 2007 (PDT)

* ...

== Template ==
{{issues-format}}

==See also==
*[[accessibility]]
*[[criticism]]
*[[wiki-feedback]]
*The [[faq|microformats FAQ]], which answers many general criticisms/ issues that have been raised with microformats.

User:JoshieSurber

2009-01-05T10:39:53Z

Brian: Reverted edits by TroczElric (Talk) to last version by JoshieSurber

Find my website at http://joshie.surber.us

User:Steve Ganz

2009-01-05T10:39:51Z

Brian: Reverted edits by BasroRonot (Talk) to last version by Steve Ganz

[http://steve.ganz.name/ Steve Ganz]

{{cc-public-domain-release}}

hreview-examples

2009-01-05T10:39:49Z

Brian: Reverted edits by AcelcAerel (Talk) to last version by AndyMabbett

= hReview examples =

Example [[hreview|hReviews]].

__TOC__

== Authors ==
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc.]
* [http://360.yahoo.com/alidiabali Ali Diab],[http://yahoo.com Yahoo! Inc.]
* [http://spaces.msn.com/members/ianmcallister/ Ian McAllister], [http://microsoft.com/ Microsoft Corporation]
* [http://journals.aol.com/panzerjohn/abstractioneer John Panzer], [http://www.aol.com America Online, Inc.]
* [http://ifindkarma.com/blog Adam Rifkin], [http://labs.commerce.net/ CommerceNet Labs]
* [http://sippey.typepad.com/ Michael Sippey], [http://sixapart.com Six Apart, Ltd.]

Here are a few examples of reviews from current web sites, and how they could be easily enhanced to support the hReview structured review microformat.

== Restaurant review ==

Here is an example of a simple online restaurant review:

<pre><nowiki>
<div>
5 stars out of 5 stars
<h4>Crepes on Cole is awesome</h4>
Reviewer: Tantek - April 18, 2005
<blockquote>
Crepes on Cole is one of the best little creperies in San Francisco.
Excellent food and service. Plenty of tables in a variety of sizes
for parties large and small. Window seating makes for excellent
people watching to/from the N-Judah which stops right outside.
I've had many fun social gatherings here, as well as gotten
plenty of work done thanks to neighborhood WiFi.
</blockquote>
Visit date: April 2005
Food eaten: Florentine crepe
</div>
</nowiki></pre>

Adding hReview to this review is quite simple:

<pre><nowiki>
<div class="hreview">
5 out of 5 stars
<h4 class="summary">Crepes on Cole is awesome</h4>
Reviewer: Tantek -
<abbr class="dtreviewed" title="20050418T2300-0700">April 18, 2005</abbr>
<blockquote class="description">
Crepes on Cole is one of the best little creperies in San Francisco.
Excellent food and service. Plenty of tables in a variety of sizes
for parties large and small. Window seating makes for excellent
people watching to/from the N-Judah which stops right outside.
I've had many fun social gatherings here, as well as gotten
plenty of work done thanks to neighborhood WiFi.
</blockquote>
Visit date: April 2005
Food eaten: Florentine crepe
</div>
</nowiki></pre>

Note that some of the properties of this sample review are not captured by hReview (visit date, food eaten). This is deliberate per the scope of keeping hReview minimal and simple.

This sample hReview could be rendered like this:

5 stars out of 5 stars 
'''Crepes on Cole is awesome''' 
Reviewer: Tantek - April 18, 2005 

<blockquote>Crepes on Cole is one of the best little creperies in San Francisco. Excellent food and service. Plenty of tables in a variety of sizes for parties large and small. Window seating makes for excellent people watching to/from the N-Judah which stops right outside. I've had many fun social gatherings here, as well as gotten plenty of work done thanks to neighborhood wifi.</blockquote>

Visit date: April 2005 
Food eaten: Florentine crepe 

=== Multidimensional Restaurant Review ===

Some restaurant reviews indicate ratings for different aspects of the restaurant. Such details are represented in hReview using tagged ratings. In addition, note the inline tags inside the description of this review.

Here is one such review in text format:

Cafe Borrone

1010 El Camino Real, Menlo Park, CA 94025, +1-650-327-0830;
cafeborrone.com

Food: 18/30; Ambience: 19/30; Service: 15/30; Price: $$...

This cafe is a welcoming oasis on the Peninsula. It even has a fountain
outside which cloaks the nearby sounds of El Camino traffic. Next door to a
superb indy bookstore, Cafe Borrone is an ideal spot to grab a coffee or a
snack to accompany a newly purchased book or imported periodical. Soups and
sandwich specials rotate daily. The corn chowder with croutons and big
chunks of cheese goes especially well with a freshly toasted mini-baguette.
Evenings are often crowded and may require sharing a table with a perfect
stranger. Espresso afficionados will appreciate the Illy coffee. Noise
levels can vary from peaceful in the late mornings to nearly overwhelming on
jazz band nights.

As an hReview:

<pre><nowiki>
<div class="hreview">
<div class="item vcard">
<div class="fn org summary">Cafe Borrone</div>

1010 El Camino Real,
San Francisco,
CA
94025,

+1-650-327-0830;
<a class="url" href="http://cafeborrone.com">cafeborrone.com</a>
</div>
<ul class="categories">
<li><a href="http://en.wikipedia.org/wiki/Food" rel="tag">
Food: 18/30</a>;</li>
<li><a href="http://flickr.com/photos/tags/Ambience" rel="tag">
Ambience: 19/30</a>;</li>
<li><a href="http://en.wikipedia.org/wiki/Service" rel="tag">
Service: 15/30</a>;</li>
<li><a href="http://en.wikipedia.org/wiki/Price" rel="tag">
Price: <abbr class="rating" title="2">$$</abbr>...</a></li>
</ul>
<blockquote class="description">
This <abbr class="type" title="business">
<a href="http://en.wikipedia.org/wiki/cafe" rel="tag">cafe</a></abbr>
is a welcoming oasis on the Peninsula.
It even has a fountain outside which nearly eliminates
the sounds of El Camino traffic. Next door to a superb indy bookstore,
Cafe Borrone is an ideal spot to grab a
<a href="http://en.wikipedia.org/wiki/coffee" rel="tag">coffee</a>
or a meal to accompany a newly purchased book or imported periodical.
<a href="http://technorati.com/tag/soup" rel="tag">Soups</a> and
<a href="http://technorati.com/tag/sandwich" rel="tag">sandwich</a>
specials rotate daily. The corn chowder with croutons and big chunks of cheese
goes especially well with a freshly toasted mini-baguette. Evenings are
often crowded and may require sharing a table with a perfect stranger.
<a href="http://flickr.com/photos/tags/espresso" rel="tag">Espresso</a>
afficionados will appreciate the
<a href="http://en.wikipedia.org/wiki/Illy" rel="tag">Illy</a> coffee.
Noise levels can vary from peaceful in the late mornings to nearly overwhelming on
<a href="http://en.wikipedia.org/wiki/jazz" rel="tag">jazz</a> band nights.
</blockquote>
Review (<a href="http://microformats.org/wiki/hreview">
hReview v0.2</a>)
by anonymous,
<abbr class="dtreviewed" title="20050428T2130-0700">April 28th, 2005</abbr>.
</div>
</nowiki></pre>

With an accompanying CSS style sheet like:

<pre><nowiki>
a.url { display:block }
ul.categories { margin:1em 0; padding:0 }
.categories li { display:inline }
</nowiki></pre>

This hReview could be presented similar to the original text:

Cafe Borrone 
1010 El Camino Real, Menlo Park, CA 94025, +1-650-327-0830; 
[http://cafeborrone.com/ cafeborrone.com] 
 
[http://en.wikipedia.org/wiki/Food Food: 18/30];
[http://flickr.com/photos/tags/Ambience Ambience: 19/30];
[http://en.wikipedia.org/wiki/Service Service: 15/30];
[http://en.wikipedia.org/wiki/Price Price: $$...] 

<blockquote>This [http://en.wikipedia.org/wiki/cafe cafe] is a welcoming oasis on the Peninsula. It even has a fountain outside which cloaks the nearby sounds of El Camino traffic. Next door to a superb indy bookstore, Cafe Borrone is an ideal spot to grab a [http://en.wikipedia.org/wiki/coffee coffee] or a snack to accompany a newly purchased book or imported periodical. [http://technorati.com/tag/soup Soups] and [http://technorati.com/tag/sandwich sandwich] specials rotate daily. The corn chowder with croutons and big chunks of cheese goes especially well with a freshly toasted mini-baguette. Evenings are often crowded and may require sharing a table with a perfect stranger. [http://flickr.com/photos/tags/espresso Espresso] afficionados will appreciate the [http://en.wikipedia.org/wiki/Illy Illy] coffee. Noise levels can vary from peaceful in the late mornings to nearly overwhelming on [http://en.wikipedia.org/wiki/jazz jazz] band nights.</blockquote>

Review ([http://microformats.org/wiki/hreview hReview v0.2]) by anonymous, April 28th, 2005.

== Product review ==

Here is an example of a product review:

<pre><nowiki>
<div>
<a href="http://www.amazon.com/exec/obidos/ASIN/B000089CJI/">
<img src="http://images.amazon.com/images/P/B000089CJI.01._SCTHUMBZZZ_.jpg"
alt="Album cover photo: The Postal Service: Give Up." />
The Postal Service: Give Up</a>
<blockquote>
"The people thought they were just being rewarded for treating others
as they like to be treated, for obeying stop signs and curing diseases,
for mailing letters with the address of the sender... Don't wake me,
I plan on sleeping in..."

"Nothing Better" is a great track on this album, too...
</blockquote>
(*****)
</div>
</nowiki></pre>

Adding hReview to this review is also quite simple, but in this case requires a few more elements for the rating and reviewer which are required by hReview:

<pre><nowiki>
<div class="hreview">
<a class="item url" href="http://www.amazon.com/exec/obidos/ASIN/B000089CJI/">
<img src="http://images.amazon.com/images/P/B000089CJI.01._SCTHUMBZZZ_.jpg"
alt="Album cover photo: The Postal Service: Give Up. "
class="photo" />
The Postal Service: Give Up</a>
<blockquote class="description">
"The people thought they were just being rewarded for treating others
as they like to be treated, for obeying stop signs and curing diseases,
for mailing letters with the address of the sender... Don't wake me,
I plan on sleeping in..."

"Nothing Better" is a great track on this album, too...
</blockquote>
(<abbr class="rating" title="5">*****</abbr>)
Review by
<a class="url fn" href="http://ifindkarma.com/blog/">Adam Rifkin</a>,
<abbr class="dtreviewed" title="200502">February 2005</abbr>

</div>
</nowiki></pre>

And this hReview might be presented like this:

[Album cover photo: ]
[The Postal Service:]
[ Give Up ]

The Postal Service: Give Up

<blockquote>"The people thought they were just being rewarded for treating others as they like to be treated, for obeying stop signs and curing diseases, for mailing letters with the address of the sender... Don't wake me, I plan on sleeping in..."</blockquote>

<blockquote>"Nothing Better" is a great track on this album, too... </blockquote>

(*****)

Review by Adam Rifkin, February 2005.

== Movie Review ==
Finally, here is an example of a movie review.

<pre><nowiki>
<div>
anonymous, April 18th, 2005
<div>
<a lang="zh" href="http://www.imdb.com/title/tt0299977/">
Ying Xiong (HERO)
</a>
</div>
<div>Rating: 4 out of 5</div>
<blockquote>
This movie has great visuals and music.
</blockquote>
</div>
</nowiki></pre>

With hReview:

<pre><nowiki>
<div class="hreview">

anonymous,
<abbr class="dtreviewed" title="20050418">April 18th, 2005</abbr>

<div class="item">
<a lang="zh" class="url fn" href="http://www.imdb.com/title/tt0299977/">
Ying Xiong (HERO)
</a>
</div>
<div>Rating: 4 out of 5</div>
<blockquote class="description">
This movie has great music and visuals.
</blockquote>
</div>
</nowiki></pre>

Which could be presented like this:

anonymous, April 18th, 2005 
Ying Xiong (HERO) 
Rating: 4 out of 5 

This movie has great music and visuals.

== Examples in the wild ==

This section is '''informative'''.

The following sites have published hReviews, and thus are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you publish hReviews on your own page, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.

* [http://blog.ftwr.co.uk/ Peter Westwood] has written an [http://blog.ftwr.co.uk/archives/2005/10/03/blubeckers-hampton-court/ hReview of Blubeckers Hampton Court]
* [http://dougal.gunters.org/blog/ Dougal] has published an [http://dougal.gunters.org/blog/2005/08/03/french-vanilla-latte hReview of Wolfgang Puck’s Gourmet French Vanilla Latte].
* [http://www.dinnerbuzz.com/ Dinnerbuzz] is a great site for posting tagged reviews of restaurants, and they publish and summarize all their reviews in hReview!
* [http://soldierant.net/ Bryce Glass] posted an [http://soldierant.net/archives/2005/06/product_review.html hReview of the Uniden ELBT 595 Bluetooth Cordless Phone].
* dda posted an [http://sungnyemun.org/wordpress/?p=20 hReview of hReview] :)
* An [http://tbp.xomerang.com/?p=3 hReview of Caffè Camardo coffee].
* [http://loadaveragezero.com/hnav/contact.php Douglas Clifton] posted [http://loadaveragezero.com/#May-12-2005 comments] regarding adapting his list of ~800 [http://loadaveragezero.com/app/drx Developer Resources] as a format for evaluating hReview.
* [http://www.oliverbrown.me.uk/ Oliver Brown] [http://www.oliverbrown.me.uk/2005/05/09/sitereviewsorg-supports-hreview-i-think/ has announced] that his [http://en-us.sitereviews.org/ SiteReviews.org] (which reviews websites) publishes its reviews using hReview, e.g. here is the [http://en-us.sitereviews.org/review-photomatt.net review on SiteReviews.org for photomatt.net].
* [http://www.myelin.co.nz/post/ Phillip Pearson] is publishing hReviews in the [http://coffee.gen.nz/rss/reviews RSS feed of cafe reviews] on his [http://coffee.gen.nz/ kiwi coffee review site], which of course has the reviews in HTML with embedded hReview markup as well.
* [http://station11.net/ticker/ Kjell] is publishing his link blog as a [http://station11.net/ticker/ list of hReviews].
* [http://epeus.blogspot.com/ Kevin Marks] has [http://epeus.blogspot.com/2005_04_01_epeus_archive.html#111484565269684374 published two hReviews] and used unicode "star" characters for his ratings!
* JamesStewart is publishing hReviews in the location pages at his [http://grwifi.net Grand Rapids WiFi site].
* [http://soldierant.net/ Soldier Ant] has [http://soldierant.net/archives/2005/06/product_review.html reviewed a cordless phone].
* [http://www.happenchance.co.uk/ Paul Livingstone] uses hreview to voice his opinion on [http://www.happenchance.co.uk/archives/2005/07/war_of_the_worl.php books], [http://www.happenchance.co.uk/archives/2005/03/im_going_to_fin.php movies] and [http://www.happenchance.co.uk/archives/2005/05/eels_carling_ac.php music].

==See also==
{{hreview-related-pages}}

events/2006-06-16-atmedia-microformats

2009-01-05T10:39:46Z

Brian: Reverted edits by DelgeTzelt (Talk) to last version by AmeerDawood

= 2006-06-16 @media2006 microformats sessions =

This is a stub [[events|event]] page and needs sections for speaker(s), attendees, links, schedule, photos etc.

== Details ==

;Date: Tuesday, June 15-16, 2006
;Time: 3:00pm - 4:00pm GMT
;Location: ??? London, UK
;URLs: [http://www.vivabit.com/atmedia2006/sessions/#microformats Microformats: Evolving the web], [http://www.vivabit.com/atmedia2006/ @media homepage].
;Overview: ???

== Summary ==
"[http://tantek.com/presentations/2006/06/microformats-evolution/ Microformats: Evolving the Web]"

Presentatin/slides: http://tantek.com/presentations/2006/06/microformats-evolution/

The microformats community believes that standards should do less, not more. Data formats should adapt to current web publishing behaviors and reuse existing broadly interoperably implemented standards. Easy to adopt formats are enabling a diverse set of web designers and developers to visibly publish, share, and consume all kinds of common information, and microformats are leading the way.

== Attending ==
Please add your name here if you attended @media.

Alphabetically sorted by last name.
* William Lawrence - [[User:Veeliam|veeliam]] 23:25, 17 Aug 2006 (PDT)
*
*

== Session Comments and Q&A ==
*

== Photos ==

See also the [http://flickr.com/photos/tags/atmedia/ atmedia tag on Flickr].

== Podcast ==

* [http://www.vivabit.com/atmedia2006/blog/index.php/tantek-celik-microformats-evolving-the-web-podcast/ official podcast] of the session

picoformats

2009-01-05T10:39:43Z

Brian: Reverted edits by CnacoAcele (Talk) to last version by RyanKing

<h1>picoformats</h1>
{{TOC-right}}
== Introduction ==
Picoformats represent an effort being undertaken led by Chris Messina to codify various standards and openly pursue a nomenclature and syntax for communicating and executing commands with mobile devices over SMS or via command line interfaces (CLI).

An example application is [http://dodgeball.com Dodgeball's] use of the at symbol (@) to express checking in to a place.

Using the Microformats process and principles of building block design, our goal is to openly develop a complete syntax for interacting with various mobile services using the characters available on most mobile devices.

== Problem Statement ==
* send messages to user mobiles - via SMS, or a small application, that contains information like appointment times, locations,
directions, and contact info. For example, when2where.com reminds users when they need to leave to get to their appointment, so the
message may be like:

leave @ 4:35PM ~Dentist Office -> Detroit, MI

where the text itself is simple and readable, but there *may* be an small utility that would parse the @ symbol to add the event to the calendar, the ~ to allow the person to quickly call that contact, or the -> to pull up a Map/directions to the location

* allow users to write messages to query an application - this is similar to what Mozes has started with notes:

when2where: ?today --- what appointments to I have today
new @ 4PM ~Olive Garden -> Novi --- add an appointment

In addition to the obvious mobile device arena, picoformats may be usable in any context where "markup" is too heavy. For example, an IRC bot, whereisbot, that announces user locations as they sign into a channel, or allows people to do:

.whereami, or .whereis <nick> to geolocate other people in a channel.

The intention is to 'markup' the information, but putting actual XHTML or XML is annoying, since IRC doesn't parse the information at all. So right now the response is:

ajturner: .whereami
whereisbot: ajturner is in Northville, MI, US [42.4365 x -83.4884]

So then someone could write a Picoformat parser for X-Chat/Colloquy/other that would parse the [ #### x #### ] and provide a Map url link.

Using arrows to denote time and place, familiar from video recorders and other devices.
Some thoughts: <past >future ^now (the hat is also mnemonic for Here + At) or >5 (in five days time) >>5 (in 5 weeks time) >>>5 (5 months)

Meeting <Leeds went well. ^Home. See you >london
Sorry, saw them <<2 wanna go see film >3?

<div id="Documented_Syntaxes">

== Syntaxes ==

* [[actiontastic-syntax | Actiontastic]]
* [[brightkite-syntax| BrightKite]]
* [[dodgeball-syntax| Dodgeball]]
* [[dopplr-syntax | Dopplr]]
* [[facebook-syntax | Facebook Mobile]]
* [[igtd-syntax | iGTD]]
* [[kiboze-syntax|Kiboze]]
* [[jaiku-syntax|Jaiku]]
* [[mixd-syntax | Mixd]]
* [[plazes-syntax | Plazes]]
* [[poi66-syntax | POI66]] - [http://www.poi66.com/maps/step1.php]
* [[quickpack-syntax | QuickPack]]
* [[remember-the-milk | Remember the Milk for Twitter]]
* [[stikkit-syntax | Stikkit]] [http://stikkit.com/]
* [[swaggle-syntax | Swaggle]] [http://swaggle.mobi/]
* [[textmarks-syntax|Textmarks]]
* [[tfl-syntax | Transport for London]]
* [[tripit-syntax | TripIt]]
* [[twitter-syntax | Twitter]]

</div>

== References ==
* [http://www.kiboze.com/kiboze/CustWorks.aspx Kiboze How it Works]
* Flagr: [http://www.flagr.com/help/howto#mobile_creating_flag Creating mobile flags]
* [http://www.dodgeball.com/glossary Dodgeball Glossary]
* [http://twttr.com/t/help/lingo twttr lingo]
* Twitter (or Jaiku) [[twitter-nanoformats]] brainstorm [http://twitternanoformats.wikispaces.com/ A proposal for Twitter nanoformats]
* [http://skobee.com/email_howto Skobee's email syntax]
* [https://www.billmonk.com/about/sms BillMonk syntax]

== concept ==
Thanks to [http://factoryjoe.com/blog Chris Messina] for collecting a bunch of common work in this area, and exploring the area of short semi-structured text for potential "formats" of a sort that could be agreed upon, perhaps among multiple providers to make it easier for users to remember a common user interface.

User:DavidOsolkowski

2009-01-05T10:39:40Z

Brian: Reverted edits by C4tacMonal (Talk) to last version by DavidOsolkowski

http://wadny.com/ - in hiatus pending a rewrite of my weblog system

Student studying software engineering in the US, western New York state.

directory-examples

2009-01-05T10:39:38Z

Brian: Reverted edits by C4tdrOnnoa (Talk) to last version by RyanKing

#REDIRECT [[directory-inclusion-examples]]

events/2007-03-12-sxsw-growth-evolution-of

2009-01-05T10:37:03Z

Brian: Reverted edits by PasbaSbasl (Talk) to last version by Brian

<h1>The Growth and Evolution of Microformats at SXSW 2007</h1>

One of several microformats [[events]].

__TOC__

== Summary ==
The Growth and Evolution of Microformats is a [http://2007.sxsw.com/interactive/programming/panels/ confirmed panel presentation] session to be held at the 2007 [http://2007.sxsw.com/ SXSW] Interactive Festival, on Monday, March 12th from 2:00-3:00pm in Austin, Texas.

== Tags ==
Please use ''all'' of the following tags when tagging content (blog posts, photos) published related to the microformats session at SXSW interactive 2007:

tags: '''microformats sxsw sxsw07 sxsw2007 sxswi sxswi07 sxswi2007 microformats-sxsw microformats-sxsw2007 microformats-sxswi microformats-sxswi2007'''

== Panelists ==
In order of appearance:
*[[User:Tantek|Tantek Çelik]] (moderator)
*[[User:MikeKaply|Michael Kaply]]
*[http://www.glennjones.net/ Glenn Jones]
*[[User:Phae|Frances Berriman]]
*[[User:Adactio|Jeremy Keith]] (surprise guest panelist)

== Short Session Description ==
Was required to be 25 words or less:

Microformats.org has ushered in the rapid adoption of key formats for publishing and sharing [[rel-tag|tags]], [[rel-license|licenses]], [[hcard|contacts]], [[xfn|relationships]], [[hcalendar|events]] and [[hreview|reviews]]. What happens next?

== Longer Session Description ==
In its first year, microformats.org ushered in the rapid adoption of key formats for publishing and sharing [[rel-tag|tags]], [[rel-license|licenses]], [[hcard|contacts]], [[xfn|relationships]], [[hcalendar|events]] and [[hreview|reviews]] on the Web. See what new microformats are being developed for [[hresume|resumes]], [[hlisting|classified listings]], [[media-info|music, and media]], as well as how tens of millions of established microformats on web sites of individuals, companies, and organizations are driving innovations in desktop applications and advancing personal data portability.

== Attending ==
Please add your name here if you are attending this session, speaking or not.

*[[User:Tantek|Tantek Çelik]] (moderator)
*[[User:MikeKaply|Michael Kaply]]
*[http://www.glennjones.net/ Glenn Jones]
*[[User:Phae|Frances Berriman]]
*[[User:Adactio|Jeremy Keith]] (surprise guest panelist)
*[[User:Veeliam|William Lawrence]]
*[[User:RyanKing|Ryan King]]
*[[User:Cgriego|Chris Griego]]
*[[User:Mike Linksvayer|Mike Linksvayer]]
*[[User:DanC|Dan Connolly]] (attempted to volunteer for Jeremy Keith's phone demo, but was disqualified due to being a known member of the microformats community and with W3C :)
*[[User:AdamDarowski|Adam Darowski]]
*[[User:SuperPhly|Cody Marx Bailey]] - Dumbass who volunteered for Jeremy's phone demo with a development site then go "deer in the headlights" and couldn't remember sibility.com... yeah!
*[[User:Steve Ganz|Steve Ganz]]
*[[User:JasonGarber|Jason Garber]]
*[[User:DanielMorrison|Daniel Morrison]]
*[[User:DavidMead|David Mead]]
*[[User:TimTrentham|Tim Trentham]]

=== Photo of Attendees ===
And create a note around yourself in these photos:
<div>
[http://flickr.com/photos/tantek/436784378/ http://farm1.static.flickr.com/160/436784378_80ec442446.jpg][http://flickr.com/photos/tantek/436784366/ http://farm1.static.flickr.com/161/436784366_bcf03265b0.jpg]
</div>

== Session Notes ==
Tantek did a brief and incomplete history of microformats through t-shirts, for the following:

* http://sxsw.com/ (2003)
* http://gmpg.org/xfn/
* http://blo.gs/
* http://wordpress.org/
* http://eventful.com/
* http://simplebits.com/
* http://microformats.org/
* http://flickr.com/
* http://technorati.com/
* http://odeo.com/
* http://supernova2006.com/
* http://stanford.edu

Mike Kaply

Glenn Jones

Frances Berriman

Q&A (see below)

== Session Comments and Q&A ==
* ...

== Photos ==
See the [http://flickr.com/photos/tags/microformats-sxsw2007 microformats-sxsw2007 tag on Flickr].

[http://www.flickr.com/photos/meyerweb/419771185/ http://farm1.static.flickr.com/132/419771185_da0b2be939_m_d.jpg] [http://www.flickr.com/photos/rcrowley/423201101/ http://farm1.static.flickr.com/165/423201101_931e1d09e5_m_d.jpg]
[http://www.flickr.com/photos/thechunk/420604647/ http://farm1.static.flickr.com/179/420604647_10441d1ffe_m_d.jpg] [http://www.flickr.com/photos/thechunk/420604224/ http://farm1.static.flickr.com/162/420604224_df888058c1_m_d.jpg]
[http://www.flickr.com/photos/ptg/420129138/ http://farm1.static.flickr.com/159/420129138_24fc218517_m.jpg]
[http://www.flickr.com/photos/mn_francis/425446977/ http://farm1.static.flickr.com/155/425446977_50dc90856e_m.jpg]

== Blog Posts ==
Put most recent first.
* [http://techory.com/sxsw/?p=35 SXSW Notes - Notes from SXSW Interactive in Austin, TX - The Growth and Evolution of Microformats] - good capture of the Q&A
** Lazyweb - please transcribe / cleanup Q&A documented in this blogpost to the Q&A section above.
* [http://johnzeratsky.com/archives/001521.php JUST THIS ONE - Microformats]
* [http://blog.wired.com/music/2007/03/microformats_go.html WIRED Blog - Microformats Go Large]
* [http://www.centernetworks.com/sxsw-monday-recap-techquila-microformats-bats-and-the-expo-hall SXSW Monday Recap - Techquila, Microformats, Dogster, Bats and the Expo Hall]
* [http://www.commonplacebook.com/journal/200pm_the_growt.shtm 2:00pm - The Growth and Evolution of Microformats Panel Notes (SXSWi 2007)]
* [http://www.darowski.com/tracesofinspiration/2007/03/12/sxswi-the-growth-and-evolution-of-microformats/ Adam Darowski "SXSWi: The Growth and Evolution of Microformats"] I didn't take the most detailed notes, but this session certainly inspired a few questions. Great job, guys.
* [http://muffinresearch.co.uk/archives/2007/03/12/sxswi-07-notes-the-growth-and-evolution-of-microformats/ SXSWi 07 Notes: The Growth and Evolution of Microformats] - fairly thorough notes
** Lazyweb - please transcribe / cleanup Q&A documented in this blogpost to the Q&A section above.

== Podcasts ==
* [http://www.podtech.net/home/technology/2477/microformats-guru-tantek-celik "Microformats Guru Tantek Celik"] PodTech.net interview just after the session.

citation-brainstorming-fr

2009-01-05T10:36:52Z

Brian: Reverted edits by GettrLidel (Talk) to last version by Tantek

<h1> Citation Brainstroming </h1>

== Voir aussi ==
* [[citation-fr|citation]]
* [[citation-examples-fr|exemples de citations]]
* [[citation-formats-fr|formats de citations]]
* [[citation-faq-fr|citation-faq]]

__TOC__

== Contributeurs ==

* ...
* ... (un paquet de types biens !)
* Tantek Çelik
* Tim White
* Michael McCracken
* Brian Suda
* [[User:AndyMabbett|Andy Mabbett]]

(traduction en cours [[Christophe Ducamp]])

== Cas d'utilisation ==
Pour concentrer la discussion, ajoutez svp en-dessous des cas d'utilisation qui aideront à montrer quels problèmes le microformat citation essaiera de résoudre.

J'en ai inclus deux, se concentrant sur la consommation de l'information - j'ai imaginé qu'utiliser des cas pour générer du contenu microformaté impliquerait simplement de permettre à votre contenu d'être mieux consommé, mais me suis intéressé pour voir s'il y a quelque chose qui m'échappe ici - Mike

=== Acquérir l'information de référence à partir du web ===

Un utilisateur trouve soit une page d'un article d'un auteur, ou visualise les résultats d'une recherche et aimerait importer l'information sur les articles affichés dans sa database locale de référence, afin de cataloguer les choses qu'il a lues, d'y ajouter des notes et d'utiliser l'information plus tard pour générer des citations, potentiellement sous d'autres formes, telles que BibTeX ou Docbook, pour inclusion dans une publication de son cru.

Notes : Dans ce cas, il n'est pas important pour l'utilisateur quel format prend la citation comme affichée sur la page où il la trouve. Ce qui *est* important est qu'elle contienne suffisamment d'inforamtions pour permettre la génération du format dans lequel il la republiera pour finir. Ceci sous-tend qu'il puisse être valable de la dégrader un peu du côté de la verbosité.

Ainsi, les liens vers les représentations complètes téléchargeables du travail cité sont très importants - par ex. un lien vers le PDF d'un article de journal ou vers un fichier de musique.

=== S'abonner à des listes de lectures, périodiques, etc. ===

J'aimerais pouvoir influencer mon agrégateur de nouvelles avec hAtom pour m'abonner à une source distante pour l'information de citation, par exemple :

* une liste de lecture pour un séminaire
* la liste de publication pour une conférence (par ex, m'abonner à SIGGRAPH et voir les comptes-rendus mis à jour chaque année)
* les éditions d'un journal
* un groupe de recherche particulier ou des publications d'un chercheur
* Pas simplement de la recherche : les publications populaires d'un auteur (par ex., l'[http://www.gladwell.com/archive.html Archive de Malcolm Gladwell])

=== Agréger les listes de lectures et critiques ===

Un agrégateur de citation spécifique microformat pourrait fournir une version décentralisée de [http://citeulike.org/ CiteULike]. Les bibliothèques, auteurs, groupes de recherche et éditeurs pourraient baliser leurs collections, tandis que d'autres personnes sur les blogs ou sites de critiques pourraient ajouter des tags et critiques.

Au moins, disposer d'un microformat bien adopté rendrait les outils d'écriture comme CiteULike bien meilleur, parce que cela reposerait dans certains cas sur le raclage-écran de sites web.

=== Copier et Coller à partir de page web ===
Capturer/copier du HTML à partir de pages web pour utilisation dans d'autres applications (tout spécialement quand ces applications présentent le HTML comme une production) comme copier dans Word ou une application spécialisée comme [http://www.google.com/notebook Google Notebook], [http://onfolio.com Onfolio] ou [http://www.kaboodle.com Kaboodle]. Quand de telles captures sont faites, cela fait sens de conserver toutes les données de citation, y compris la date à laquelle elle a été accédée, qui peut ou peut ne pas être la date à laquelle elle a été publiée.

=== Blogs citant d'autres ressources, y compris des blogs===
Tout blog qui cite du contenu en ligne, que ce soit un blog ou un article d'actualités, pourrait utiliser un hCitation pour lier proprement vers la référence citée. De telles citations pourraient inclure la date d'accès quand le blogueur a produit la citation, parce que les ressources de l'autre côté de ces liens peuvent être amenées à changer sans avertissement.

Au lieu de cela, aujourd'hui nous avons un formatage simple avec un lien vers l'URL permanente. La donnée de citation manque complètement. Regardez le blog de [http://doc.weblogs.com Doc Searl] pour un style de référencement qui pourrait bénéficier d'une citation appropriée uF.

Fascinant... après avoir ajouté deux cas d'utilisation, j'ai réalisé qu'ils se dirigeaint sur des cas potentiellement marginaux. Le premier parce que la partie "production" manque du copier et coller, où l'uF serait véritablement utilisé comme partie du collage. Le dernier parce que les blogueurs ont une mécanique de travail de citation qui est juste un lien vers l'URL (je l'espère une url permanente). On pourrait débattre qu'ils ne veulent pas un hCitation complet. Et en fait, jusqu'à ce qu'un outil existe qui facilitera ça, ils ne le feront probablement pas. Néanmoins, un outil qui coupe et colle à partir de n'importe où sur le web à l'intérieur d'un blog avec une citation complète semble comme un bel outil. Mais à nouveau, je ne suis pas vraiment en train de paver le chemin des vaches avec ces idées. -Joe Andrieu

===Trouver dans une Bibliothèque ===
Trouver une copie du travail cité dans une bibliothèque de proximité (comme avec [http://ocoins.info/ OpenCOinS]). [[User:AndyMabbett|AndyMabbett]] 04:55, 4 Nov 2006 (PST)

===Acheter une copie===
Trouver le travail cité, par exemple Amazon ou [http://www.abebooks.com/ ABE] ; ou s'abonner à un journal via son propre site web . [[User:AndyMabbett|AndyMabbett]] 04:55, 4 Nov 2006 (PST)

===Trouver des critiques===
Trouver des critiques tiers du travail cité. [[User:AndyMabbett|AndyMabbett]] 04:55, 4 Nov 2006 (PST)

===Donner des données de citation pour la page étant visitée===
En ajoutant une classe, disons, "self" à un attribut de la proposition épouvantail proposée permettrait aux utilisateurs (ou agents utilisateurs) d'extraire les données exigées pour citer la page en train d'être visitée, au moment d'y faire référence ailleurs. Il y aurait l'avantage supplémentaire de permettre à la citation d'être ignorée par quelque parseur qui pourrait être de construire un "arbre" de citations, et d'éviter le réglage d'une boucle infinie.

Pour l'indication des données publiées "d'auto-citation" (même sur une page secondaire) voir le lien "cite this article" sur toute entrée de Wikipedia, par ex.[http://en.wikipedia.org/w/index.php?title=Special:Cite&page=West_Midland_Bird_Club&id=115894372] extrait de [http://en.wikipedia.org/wiki/West_Midland_Bird_Club].

Voir aussi : [http://en.wikipedia.org/wiki/Wikipedia_talk:Citing_Wikipedia#Citation_data_should_be_on_the_page_concerned Proposition pour inclure sur la page des données de citation dans Wikipedia]
:[[User:AndyMabbett|Andy Mabbett]] 13:47, 20 Mar 2007 (PDT)

===Convertir des formats de citation===
Un agent utilisateur devrait être capable de lire une citation à partir d'une page web, dans un format donné, et de la convertir dans un second format pour utilisation ailleurs. Pour une liste de tels formats et des exemples voir [http://en.wikipedia.org/wiki/Citation#Format_styles Wikipedia, Citation styles]. [[User:AndyMabbett|Andy Mabbett]] 11:05, 30 Mar 2007 (PDT)

==Exemples==
* (extrait d'une liste de diffusion) :
:<blockquote>if you want to cite a [biomedical journal] journal article on Wikipedia [...] you can export a correctly-formatted citation for Wikipedia from HubMed using unAPI... http://hublog.hubmed.org/archives/001408.html</blockquote>
*[http://www.zotero.org/ Zotero], une extension Firefox pour aider à rassembler, gérer et citer des sources de recherche.:[[User:AndyMabbett|Andy Mabbett]] 09:13, 21 Mar 2007 (PDT)

== Discussion hBib originale ==

Durant la Journée WWW2005 des Développeurs sur la session [[microformats-fr|microformats]], Rohit Khare a fait une [[presentations-fr|présentation]] où il a discuté du [[process-fr|processus]] des microformats et puis il a fait une démonstration rapide où un paquet d'entre nous a reçu un document partagé Subethaedit et a brainstormé quelques idées sur ce à quoi pourrait ressembler un microformat de citation "hBib". Rohit a placé le [http://cnlabs.commerce.net/~rohit/hBib%20Discussion.html document sur son site Commercenet].

* http://cnlabs.commerce.net/~rohit/hBib%20Discussion.html

''Un essai pour résumer et mettre le document lié dans ligne suit. -Mike''

Deux objectifs essentiels ont été soulignés par le groupe :
* Eviter de reverrouiller les références
* S'adapter aux nouveaux styles de journaux en modifiant CSS

Le problème fondamental a été discuté en termes d'affichage - la capacité de transformer XHTML+hBib dans les nombreux formats spécifiques aux journaux. Par exemple, comment afficher "et.al" quand tous les auteurs sont présents dans le source, et comment réordonner les éléments si un style définit un ensemble trié d'éléments qui entrent en conflit avec le tri dans la source. Utiliser hCard pour les auteurs fût agréé par les participants, et les débuts d'un exemple ont été montrés.

== Structure XHTML ==

Mon expérience de travail avec X2V et hCa* m'a enseigné quels éléments sont faciles à trouver et quels sont ceux qui ne le sont pas. Le fait que le microformat Citation soit très nouveau, il est possible de ne pas réitérer une fois de plus les mêmes erreurs et de rendre les choses plus faciles pour que l'application d'extraction trouve et sous-tende certaines propriétés.

* Il devrait y avoir une sorte de 'root node' qui sous-tend tous les éléments enfants pour le microformat Citation.
* Parce que la plupart des personnes auront plusieurs Citation il devrait y avoir une façon de représenter chaque objet Citation comme un unique bloc indépendant d'un autre. Ceci pour éviter que le parsage de trouver un 'author' et de l'appliquer à toutes les citations. Chaque citation devrait être dans un container (class="???") qui s'étendait à partir d'autres.
* Peut-être que class="hcite" avec <code><cite></code> est recommandé comme l'élément racine. Par exemple <code><cite class="hcite"></code>

'''Note : Cette section était le contenu original du document. Depuis lors, class='hcite' a été retenu avec un agrément comme le nom de classe racine. Voir [[citation-brainstorming-fr#.27hcite.27_comme_nom_Elément_Racine|explication]].'''

== Citation vs. [[media-info-fr|media-info]] ==

Ce qui distingue un 'cite' d'un disons [[media-info-fr|media-info]] (par ex. [[media-info-examples-fr|les exemples d'info média]]) est qu'un 'cite' est une référence vers quelque chose d'explictement externe au morceau de contenu actuel ou au document, tandis que [[media-info-fr|media-info]] décrit de l'information à propos du contenu embarqué ou dans la ligne du document actuel.

== Sens Sémantique ==
Un des principes fondateurs des Microformats est d'utiliser l'élément le plus riche sémantiquement pour décrire chaque noeud (Point 2 des Principes de Design du XHTML Sémantique : utiliser le bloc de construction XHTML sémantique le plus précis pour chaque objet etc.). Parce que nous traitons avec du HTML et des citations, plusieurs éléments sont candidats pour être utilisés afin d'enrichir le sens sémantique. [http://www.w3.org/TR/REC-html40/struct/text.html CITE, BLOCKQUOTE, Q, A], (y'en a t'il plus ?)

La [[citation-brainstorming-fr|page Citation Brainstorming]] a quelques développements et idés sur la façon de donner à une autre personne le crédit pour un lien. Quelques-unes des idées sémantiques derrière le choix des tags peut s'appliquer à une référence bibliographique complète. ''Est-ce que cette phrase fait sens seulement historiquement ? -Mike''

== WorldCat d'OCLC pour les titres ==
Question : que penser d'utiliser quelque chose comme le [http://www.oclc.org/worldcat/open/isbnissnlinking/default.htm WorldCat] d'OCLC pour lier les titres ? - Tim White

== This et That ==
Après avoir parcouru beaucoup de différents formats d'encodage de citation, j'ai remarqué que chaque format était utilisé de deux façons. Soit pour décrire la page en cours (THIS.PAGE) ou soit utilisé pour encoder des références qui pointent vers des ressources externes (THAT.PAGE)

L'information étant encodée était identique pour les deux ressources (author, date, name, etc) elle référence simplement des choses différentes. Pour ce microformat, je ne suis pas sûr si nous voulons essayer de résoudre les deux problèmes, ou simplement un ? Les méta tags dans l'élément head serait l'endroit idéal pour de l'information à propos de THIS.PAGE, mais cela ne suit pas les idéaux de microformats où l'information doit être lisible par un humain. L'idée de THAT.PAGE où une liste de références est à la fin d'un document sous la forme d'une bibliographie est plus en ligne avec les idéaux d'un microformat où la donnée est lisible par un humain. Cela ne veut pas dire que la donnée à propos du document actuel ne devrait pas être lisible par un humain, ainsi un peu des même propriétés utilisées pour faire référence à des ressources externes peuvent être utilisées pour le document actuel (THIS.PAGE). Pour faire ça, ceci est un item racine différent qui pourrait être utilisé et transformer les applications pourrait soit extraire la donnée citation à propos de la page en cours, ou l'information à propos des références de cette page.

Ceci est ouvert en discussion, mais de toutes les façons, je crois que les propriétés utilisées pour décrire une page seront les mêmes pour à la fois 'THIS' et 'THAT'. [http://suda.co.uk/ brian suda]

== Plus sur 'THIS' et 'THAT'==

Les microformats Citation sont en train d'être explorés comme une possiblité pour la citation d'information généalogique sur le [http://eatslikeahuman.blogspot.com blog de Dan Lawyer].

Ceci est un cas où fréquemment la citation ferait référence à (THIS.PAGE), mais l'aurait imbriqué dans une référence à (THAT.PAGE), possiblement à quelques degrés de profondeur. Par exemple, une page web pourrait contenir une donnée extraite d'un microfilm d'un recensement. La citation aurait besoin d'inclure de l'information à propos de la page web, de l'information à propos du microfilm, et de l'information à propos du recensement. Les citations généalogiques sont attendues pour inclure le repository (où peut on trouver ce livre ou ce microfilm. Est-ce le même que ''juridiction'' ?). Ainsi à chaque niveau l'information devrait contenir le repository de l'item référencé. Un mécanisme imbriqué (récursif) pour les microformats citaions serait utile dans ce cas. Est-ce la fonction de l'élément "container" dans le Format Epouvantail ?

== Mise en Forme de Date ==
Parce que les microformats sont tous au sujet de la réutilisation et du moyen accepté d'encoder Date-Time a été énormément implanté, de ce fait c'est un bon endroit pour démarrer au moment de traiter tous les types de citation de date.

Ci-après tous les différents champs extraits de différents formats de citations qui sont tous d'une nature temporelle :
* Date (available | created | dateAccepted | dateCopyrighted | dateSubmitted | issued | modified | valid)
* originInfo/dateIssued
* originInfo/dateCreated
* originInfo/dateCaptured
* originInfo/dateOther
* month
* year
* Copyright Year
* Date - Generic
* Date of Confernce
* Date of Publication
* Date of update/revisou/issuance of database record
* Former Date
* Entry Date for Database Record
* Database Update
* Year of Publication

Il existe plusieurs propriétés communes à travers différents domaines de citations et elles seront certainement dans le microformat citation, les instances uniques auront besoin de considération plus approfondie, autrement il n'y aurait aucune fin aux possibilités.

Il existe aussi plusieurs propriétés (year, month, Year of publication) qui peuvent être extraites d'une autre source. Par conséquent, si vous encodez seulement une propriété plus spécifique comme Date of Publication, vous pouvez extraire la 'year of publication' à partir de cela. Parce que le format date-time que nous modélisons après est le format ISO date-time, seule la portion Year est une date acceptable. Ainsi, si vous ne connaissez QUE l'année de publciation, alors vous pouvez former une 'Date of Publication' valide sous un microformat (qui à sont tour est une 'year of publication' valide) - votre milliaire peut varier quand il en vient à être importé dans des applications de citation.

...

Il me semble que ceux-ci peuvent être réduits à peut-être une ou deux propriétés date différentes. Aussi loin que la mise en format d'une date lisible par les humains, ceci peut être choisi paru tout ce que dit le guide de présentation du style, et le [[datetime-design-pattern-fr|datetime-design-pattern]] utilisé pour simplifier le balisage. - Tantek

'''Important'''
Parfois nous avons besoin d'une échelle de date et pas simplement d'une date (par ex. 4-6 Mai 2006). Voir les exemples de ''Citation de Conférence'' plus bas sur cette page. - Discoleo

'''Saisons'''
Quelques journaux ont des numéros saisonniers (par ex "Edition Eté 2007") au lieu des éditions étiquetés par mois ou d'autres dates de calendrier. [[User:AndyMabbett|AndyMabbett]] 05:05, 4 Nov 2006 (PST)

== Tags ==
quelques-uns de formats de citation ont un emplacement pour les 'keywords' ou des 'tags génériques', etc. Ce pourrait être un bon emplacement pour réutiliser le [[rel-tag-fr|microformat RelTag]]. L'inconvénient serait qu'ils soient ensuite forcés d'être des liens, ce qui pourrait être la façon correcte de baliser ces termes.

== MARC / MODS / Dublin Core ==
Les transformations MODS ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgmods.xml exemple]) et Dublin Core ([http://www.loc.gov/standards/marcxml/Sandburg/sandburgdc.xml exemple]) de MARC21 peuvent contenir quelques idées utiles.

Voilà un premier essai de récriture des exemples de liens dans le XHTML (écrit en réponse à une [http://microformats.org/discuss/mail/microformats-discuss/2005-December/002438.html demande sur la liste de discussion à propos de l'encodage de l'information book avec des microformats]) :

<pre><nowiki>
<div class="book" lang="en">
<h3 class="fn">Arithmetic /</h3>
By Sandburg, Carl,
1878-1967,
and Rand, Ted
Publisher: Harcourt Brace Jovanovich,
San Diego
Published: 1993
A poem about numbers and their characteristics. Features
anamorphic, or distorted, drawings which can be restored to normal by viewing
from a particular angle or by viewing the image's reflection in the provided
Mylar cone.
One Mylar sheet included in pocket.
Subjects:
<ul>
<li class="subject">Arithmetic</li>
<li class="subject">Children's poetry, American.</li>
<li class="subject">Arithmetic</li>
<li class="subject">American poetry</li>
<li class="subject">Visual perception</li>
</ul>
</div>
</nowiki></pre>

== Structures de Citation Basiques ==
Il existe des structures basiques pour n'importe quelle citation, ceci est un aperçu de quelques-uns des types
[http://www.users.muohio.edu/darcusb/misc/citations-spec.html http://www.users.muohio.edu/darcusb/misc/citations-spec.html]

== Problèmes non résolus par les formats existants ==
Il existe quelques aspects '''NON adéquatement''' couverts par les formats existants. J'ai aussi résolu cette question sur la page wiki OpenOffice.org [voir http://wiki.services.openoffice.org/wiki/Bibliographic_Database pour une discussion, le paragraphe sur ''Reference Types'']

Ces problématiques appartiennent essentiellement aux '''Errata''', '''Commentaires et Réponses de l'Auteur''' et '''Rétractations d'Articles'''.
* un lien bidirectionnel pourrait être nécessaire pour implémenter ces fonctionnalités (article original <=> eratum, réponse, lettre de rétractation)
* '''IMPORTANT : Erratum'''
** Errata : une ou plusieurs corrections pourraient être postées dans différentes questions du journal
** ceci est généralement ciré comme : Données de l'Article Citation Originale (Correction disponible dans ''Journal, numéro, Année, Pages'')
** il est probable qu'il ne soit jamais cité seul
** il devrait y avoir un lien vers l'article original, alors que l'article original contiendrait un lien vers cet ''Errata''
* '''IMPORTANT : Commentaire et Réponse de l'Auteur'''
** similaire à Errata, il pourrait y avoir un ou plusieurs Commentaires et Réponses de l'Auteur ; ceci devrait être enregistré également.
** néanmions, ce n'est généralement pas compris dans la citation originale.
** ce pourrait être utilisé néanmoins dans une citation, mais je ne sais pas exactement comment le citer optimalement (l'article original devrait être tout aussi bien produit)
* '''IMPORTANT : Rétractation Article'''
** un article peut être retiré du fait de plagiat ou toute autre faille
** ceci ne devrait pas être utilisé plus à fond dans la recherche
** néanmions ce pourrait être utilisé par ex. pour un article sur le plagiat ou la recherche d'erreurs
** il devrait y avoir par conséquent un champ stockant cette information et un lien vers
** la lettre de rétractation publiée (qui explique pourquoi l'article a été retiré)

* cette question peut nécessiter un événement contrôlé par le temps
* '''IMPORTANT : la publication électronique avant l'impression '''
** de plus en plus d'articles sont initialement postés en ligne, avant que l'article publié ne soit véritablement imprimé
** Comment ceci devrait être utilisé/cité ?
** Est-ce modifié, après que la version imprimée ne devienne disponible ?

== Problématiques à régler ==
Les 3 points principaux qui me (Brian) sont venus à l'esprit à ce stade sont :
1) IDENTIFIANTS
2) TYPES DE FORMATs
3) IMBRICATION

1) Dans hCard/hCalendar il existe un champ UID. Ajouté à URL, il produit un identifiant unique géant. Il existe des tonnes d'autres identifiant à côté des URL, ISBN, LOC call number, SKU, ISSN, etc. Beaucoup d'entre eux sont uniques en leur domaine, mais pas globalement uniques. Aussi comment les balisons-nous ? Tout comme les propriétés TEL/ADR de la hCard, nous pouvons utiliser quelque chose comme :
<pre>
<nowiki>
<div class="uid">ISBN : 123456</div>
</nowiki>
</pre>
Ceci rend l'encodage le plus extensible... si nous commençons à utiliser class="isbn" alors ce sera une liste énumérée avec class="type" c'est ouvert à la fermeture.

2) Je commence à mal utiliser "format", format est le médium - hardback, softback. Le TYPE (il existe probablement un meilleur mot - conteneur ?) - est book, article, conference, manifesto, etc. Tout comme les indentifiants, nous pouvons produire une liste numérotée de valeurs, class="book", class="article", mais cela nous emboîte, tandis que quelque chose comme : <pre><nowiki>article</nowiki></pre> laisse les choses plus ouvertes.

3) Imbriquer des données de citation dans une citation. La capacité d'imbriquer le même microformat dans lui-même est quelque chose que les autres microformats ne gèrent pas explicitement.

Les deux options sont :
i) Utiliser class="book"
<pre>
<nowiki>
<div class="hcite">
<div class="book">
Titre Livre
<div class="chapter">
Titre Chapitre
</div>
</div>
</div>
</nowiki>
</pre>

Ceci rend les choses faciles à imbriquer et imaginer exactement ce qui est associé à quoi, mais le revers est que nous avons énuméré des listes de valeurs pour les propriétés de classes.

ii) utliser le TYPE pour book
<pre>
<nowiki>
<div class="hcite">
<div class="type">book</div>
Titre Livre
<div class="type">chapter</div>
Titre Chapitre
</div>
</nowiki>
</pre>

maintenant le class="fn" n'est pas imbriqué à l'intérieur du class="book" ou
class="chapter" ainsi il devrait y avoir quelque autre mécanisme à associer les données avec le type.

== Format Epouvantail de Brian ==

=== schéma implicite (exemples) ===
+ publisher
+ language
+ description
+ title
+ creator
+ journal
+ volume
+ issue
+ page
+ edition
+ identifier
+ tags
+ format
+ date published
+ copyright
- audience

=== schéma implicite (formats) ===
+ publisher
+ language
+ description
+ title
+ creator
+ volume
+ pages
+ edition
+ issue
+ identifier
+ tags
+ format
+ date published
+ date copyrighted
- subtitle
- image
- excerpt
- index terms
- series title
- publication
- journal
- part (1 of X)

UNION des deux schémas
+ (PLUS) veut dire propriétés communes
- (MINUS) veut dire unique au schéma

=== Schéma de travail Epouvantail ===

Cette liste enregistre les discussions à propos du schéma commun extrait du dessus. Le format est ''nom descriptif'' (''élément optionnel recommandé'' 'nom de classe') (''lien vers explication'').

S'il n'y a pas de lien explication, ce champ devrait être considéré soit comme évident ou prêt pour le débat. Si vous n'en êtes pas sûr, il est prêt au débat.

* élément racine ('hcite') ([http://microformats.org/wiki/citation-brainstorming-fr#.27hcite.27_comme_nom_Elément_Racine explication])
** titre ('title')
** Auteur / Editeur etc. ('creator')
** Pages ('pages')
*** note : ce peut prendre n'importe quelle valeur
** container ('conteneur hcite')
*** Un élément hcite imbriqué qui représente un item contenant (comme un livre ou un chapitre) ([http://microformats.org/wiki?title=citation-brainstorming#Container discussion et lien vrs le fil de discussion sur la liste)
** Numéro du Volume ('volume')
** Edition ('edition')
** Numéro de Parution ('issue')
** Tags (href rel='tag')
** Format ('format')
*** Note - ceci n'est pas clair à cette heure - est-ce que format veut dire 'type', comme dans 'book' vs. 'article' ? --[[User:Mike|Mike]] 22:53, 16 Jan 2007 (PST)
** date de publication ('date-published') ([http://microformats.org/wiki?title=citation-brainstorming-fr#Champs_Date explication])
** date d'accession ('date-accessed') ([http://microformats.org/wiki?title=citation-brainstorming-fr#Champs_Date explication])
** publisher
** language
** Abstract / description ('description')
** URI (href class='uri') ([http://microformats.org/wiki/citation-brainstorming-fr#L.27El.C3.A9ment_URI explication])
** identifier
*** et (non nécessairement globalement unique) identifiant, tel qu'une clé de citation, un numéro ID pubmed, ou simplement le numéro de référence ou la chaîne dans une publication ([1] or [CLRS2001])

==== Notes à propos des champs manquants / modifiés dans le schéma ====
Cette section liste les champs intentionnellement ''non'' inclus dans le schéma de paille, ou qui ne sont pas représentés directement, et les liens vers la discussion à propos de chacun d'eux.

* date copyrighted ([http://microformats.org/wiki?title=citation-brainstorming-fr#Champs_Date explication])

=== Exemples ===
Exemples de syntaxe utilisant le format au-dessus :

==== Livre ====
Ceci est l'exemple original de Brian

<pre>
<nowiki>
<ul class="bibliography">
<li class="hcite" xml:lang="fr-fr">


<div class="creator vcard">
Jean Bon
...
</div>


Pinko !
Un livre de classe sur le PinkoMarketing
1
1
1
1-10
article


12345678


<a class="keyword" rel="tag" href="/tags/foo">foo</a>
bar


Publié le <abbr class="date-published" title="20060101">1er janvier 2006</abbr>
Copyright <abbr class="copyright" title="20060101">2006</abbr>
</li>
...
</ul>
Avez-vous lu <abbr title="book" class="format">Foo Bar</abbr> ?
Il a été écrit par Jean Bon.
Il n'est sorti qu'il y a <abbr class="dtpublished" title="20060101">quelques mois de cela.</abbr>
</nowiki>
</pre>

Note : la propriété "format" au-dessus est incorrecte. Le format renverrait plus aux caractéristiques physiques d'un item, plutôt qu'à son type ou genre (par ex. "article", "book", etc.). Je verrai plutôt la classe principlae pour le li être un "article" dans ce contexte, que la "citation" ayant vraiment du sens. Bien sûr on pourrait avoir les deux, ce qui serait tout aussi beau. -- bruce

Note : Pourrions-nous utiliser ROLE à partir de la hCard pour identifier les éditeurs, ttraducteurs, auteurs, etc?
Ceci a été discuté sur la liste de discussion et l'idée a été abandonnée [http://microformats.org/discuss/mail/microformats-discuss/2006-September/005694.html]

'''Commentaires''' : [[User:Singpolyma|singpolyma]] 08:03, 16 Jun 2006 (PDT) : les mots-clés devraient être [[rel-tag-fr|rel-tag]], et probablement aussi [[xoxo-fr|XOXO]] (de la même façon que la liste de citation)

[[User:RCanine|RCanine]] 11:55, 18 Dec 2006 (EST) :

* Y'a-t-il une raison de ne pas réutiliser "published" à partir de hAtom au lieu d'inventer un nouveau terme basiquement équivalent à "dtpublished"?
** note - date-published a été décidé pour le champ, l'exemple a été modifié pour refléter la modification --[[User:Mike|Mike]] 10:12, 30 Mar 2007 (PDT)
* Manque un champ d'exemple pour URL/URI/IRI/UID etc. (ISBN pour le Livre).
* Est-ce que la classe "copyright" est en conflit avec la [http://www.whatwg.org/specs/web-apps/current-work/#class WHATWG's definition] ?
* Commentaire de Bruce sur WRT, j'utilise actuellement class="article citation" pour mes écrits, car il a le plus de flexibilité avec les styles CSS pour les titres (par ex. Book titles .citation>.fn doit être mis en italique, alors que les titres d'articles ne le doivent pas, leur conteneur le devrait).
* En parlant de conteneurs, nous avons besoin d'un champ "in" ou "collection" pour les articles de jounaux ou les articles-dans-les-livres- ou est ce couvert par "publisher" ?

==== Citer une Communication Privée ====
Besoin d'un exemple.

==== Citer des Cas légaux====
Besoin d'exemple.
Voir [http://microformats.org/wiki/citation-examples-markup#Wikipedia_Court_Case Exemple de Wikipedia] pour inspiration.

==== Citer un Livre ====
Besoin d'un exemple

==== Citer un article de journal ====
Extrait d'un vieux billet publié dans PubMed - J Aersp Med. [http://www.ncbi.nlm.nih.gov/entrez/query.fcgi?db=pubmed&cmd=Retrieve&dopt=AbstractPlus&list_uids=4611181&query_hl=7&itool=pubmed_docsum lien]

<pre><nowiki>

R R Burton,
S D Leverett, and
E D Michaelson

Man at high sustained +Gz acceleration: a review.
In 
<abbr class="type" title="Journal">J.</abbr><abbr class="title" title="Aerospace medicine">Aersp. Med.</abbr>
urn:issn:0001-9402
45
10
<abbr class="date-published" title="101974">Oct, 1974</abbr>
, pages 1115-36.



</nowiki></pre>

Notez que je ne suis pas complètement certain du numéro issn urn ici.

==== Citer un article de magazine ====
Citer un exemple

==== Citer un brevet ====
Extrait de cet [http://microformats.org/wiki/citation-examples#U.S._Patent exemple extrait de Wikipedia] :

<pre><nowiki>
<li class="hcite"><a href="http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=4,405,829" class="url"
title="http://patft.uspto.gov/netacgi/nph-Parser?patentnumber=4,405,829">
U.S. Patent 4,405,829</a>:
The <a href="/wiki/RSA" title="RSA">RSA</a> patent, a famous software patent on the ground-breaking
and highly unobvious algorithm for public key encryption, widely used for secure communications
in many industries nowdays
</li>
</nowiki></pre>

==== Citer une publication de conférence====

Basé sur les [http://microformats.org/wiki/citation-examples-fr#ACM_Digital_Library_Search_Result_Examples l'exemple de référence pour la publication de conférence ].

Modifié le 6 octobre pour se conformer avec [[citation-brainstorming-fr#Format_Epouvantail_de_Brian le format de Brian]. --[[User:Mike|Mike]] 18:09, 12 Oct 2006 (PDT)
(tout sauf la classe url devrait être en ligne avec cette proposition)

L. Hochstein, J. Carver, F. Shull, S. Asgari, V. Basili, J. K. Hollingsworth, and M. Zelkowitz, “Hpc programmer productivity: A case study of novice hpc programmers,” in Proceedings of ACM/IEEE Supercomputing Conference, 2005.

<pre><nowiki>

Lorin Hochstein
 University of Maryland, College Park ,
 Jeff Carver 
 Mississippi State University ,
 Forrest Shull 
 Fraunhofer Center Maryland ,
 Sima Asgari
 University of Maryland, College Park ,
 Victor Basili
 Fraunhofer Center Maryland ,
 Jeffrey K. Hollingsworth
 University of Maryland, College Park , and
 Marv Zelkowitz
 University of Maryland, College Park ,

<a class="title url" href="http://dx.doi.org/10.1109/SC.2005.53">HPC Programmer Productivity: A Case Study of Novice HPC Programmers</a>.
(conference publication)

<a class="title url" href="...">Proceedings of ACM/IEEE Supercomputing Conference</a>
<abbr class="date-published" title="20051126T0000-0800">2005</abbr>

page 35

IEEE Computer Society


Washington,
DC


<a class="url eprint" href="http://portal.acm.org/...">PDF of full text from ACM</a>

DOI: <a class="url uid" href="http://dx.doi.org/10.1109/SC.2005.53">10.1109/SC.2005.53</a>
Tags:
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Design%22 ...">Design</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Experimentation%22 ....">Experimentation</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Measurement%22...">Measurement</a>,
<a class="keyword" rel="tag" href="results.cfm?query=genterm%3A%22Performance%22 ...">Performance</a>

In developing High-Performance Computing (HPC) software, ....

</nowiki></pre>

'''Note''' (De [[Discoleo]], Sept. 06)
* parfois, la citation doit inclure '''Town/Country''' and '''Precise Date/Date Range''', e.g.
** ''Gillespie SH, Dickens A.'' Variation in mutation rate of quinolone resistance in Streptococcus pneumoniae [abstract P06-17A]. In: Abstracts of the 3rd International Symposium on Pneumococci and Pneumococcal Disease (Anchorage, 5-9 May 2002).Washington, DC: American Society of Microbiology, 2002.
** ''Bassetti, M.; Righi, E.; Rebesco, B.; Molinari, MP.; Costa, A.; Fasce, R.; Cruciani, M.; Bassetti, D.; Bobbio Pallavicini, F.'' 44th Annual Interscience Conference on Antimicrobial Agents and Chemotherapy (ICAAC). Washington, DC; 2004. Epidemiological trends in nosocomial candidemia in ICU: A five-year Italian perspective.
** ''Peacock JE, Wade JC, Lazarus HM, et al.'' Ciprofloxacin/piperacillin vs. tobramycin/piperacillin as empiric therapy for fever in neutropenic cancer patients, a randomized, double-blind trial [abstract 373]. In: Program and abstracts of the 37th Interscience Conference on Antimicrob Agents and Chemotherapy (Toronto). Washington, DC: American Society for Microbiology, 1997.

==== Citation d'un site web externe====
Ceci est fondé sur une citation formelle d'un site web dans la section références d'un article de recherche, mais pourrait aussi être utilisé pour les liens utilisés dans la ligne qui ont ajouté de l'information. Voici l'original :

[25] David Stern, "eprint Moderator Model", http://www.library.yale.edu/scilib/modmodexplain.html (version dated Jan 25, 1999)

<pre><nowiki>
<cite class="hcite">
<a class="fn url" href="http://www.library.yale.edu/scilib/modmodexplain.html">eprint Moderator Model</a>

<a href="http://pantheon.yale.edu/~dstern/dsbio.html" class="url fn">David Stern</a>

<abbr class="dtpublished" title="19990125T0000-0500">
Jan 25, 1999
</abbr>
</cite>
</nowiki></pre>

=== Discussion des éléments du Format Epouvantail===
Cette section est destinée à fournir des explications pour la postérité à propos de éléments du format épouvantail, liant vers des discussions sur la liste et ailleurs si possible.

==== 'hcite' comme nom Elément Racine ====
Cette discussion a eu lieu en janvier 2007, avec un vote [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008098.html sur la liste de discussion].

Il a été décidé d'utiliser 'hcite' comme le noms de classe de l'élément racine pour l'unicité et renvoyer une tendance à utiliser 'h' pour démarrer les noms de microformats.

==== L'Elément URI ====
Il a été décidé d'utilier URI tant pour les liens http vers les copies disponibles ou des URNs. Ceci engloble les URLs qui lient directement vers de copies en ligne tout comme des interpréteurs utilisant des URIs tels que urn:isbn: 0521890012

Voir la discussion extraite de [http://microformats.org/discuss/mail/microformats-discuss/2006-November/007390.html Novembre] et [http://microformats.org/discuss/mail/microformats-discuss/2006-December/007403.html Décembre].

==== Champs Date ====
Le format de paille original de Brian avait trois champs de date, "accessed", "copyrighted" et "published".
Après avoir examiné les exemples d'usages sur le web, il était clair que 'copyrighted' n'était pas utilisé dans les exemples que nous avions.
Il a été utilisé une fois, mais sans un champ correspondant 'published' (OCLC WorldCat), et il semble dans ce cas être utilisé comme un équivalent pour 'published'.

J'ai mis à jour la citation de paille pour inclure seulement 'accessed' et 'published' le 31 janvier. --[[User:Mike|Mike]] 00:26, 31 Jan 2007 (PST)

J'ai cité plus d'une fois que "date-published" est spécifiquement déroutant ; beaucoup trop pour des citations du vrai monde. Considérez que beaucoup de livres sont publiés dans l'année précédent leurs dates de copyright, ce qui est en fait la date utilisée pour la citation. Je préférerais juste "date" et "date-accessed" comme premier jet. --[[User:BDarcus|Bruce]] 3 fév 2007

Voir la discussion extraite du [http://microformats.org/discuss/mail/microformats-discuss/2007-January/008175.html fil de discussion 'dates' sur la liste].

==== Conteneur ====

La discussion concernant la façon de repreésenter le relations contenues est sur le fil [http://microformats.org/discuss/mail/microformats-discuss/2007-March/thread.html 'nesting container elements']

== Vieille discussion sur le format épouvantail ==
=== Suggestion du format épouvantail de Mike===
Afin de démarrer le débat et d'avoir quelque chose de concret à réparer, je suggère la structure suivante pour un format. Elle est probablement très incomplète et je ne revendique aucune expertise en microformat. J'essaye simplement de suivre les patterns existants. Les commentaires et le ridicule sont tous deux sollicités. -Mike

==== En Général ====
Le format ''citation'' est fondé sur un ensemble de champs communs à beaucoup de formats de données bibliographiques, qui sont souvent sous-tendus par les styles d'affichages standards de citation mais non explicitement balisés en pratique sur le web.

==== Schéma ====
Le schéma citation est constitué de ce qui suit :
* cite
** title : requis, texte (class = fn)
** subtitle : optionnel, texte
** authors : optionnel, utilise hCard
** publication date : optionnel
** link(s) vers instantiations, optionnel, url ou utiliser rel-enclosure ? (class=url)
** UID, optionnel (pour ISBN, utilise la classe existante uid) | permalink
** series (aka volume/issuenum) , optionnel (''pas aussi certain de la façon de gérer ça - suggestions ?'')
** pages : startpage & endpage, optionnel, texte
** venue, optionnel (hCard)
** publisher, optionnel (hCard)
** container : optionnel (hCite imbriqué)
** abstract, optionnel (blockquote + class="abstract" ?)
** notes, optionnel (blockquote + class="notes" ?)
** keywords, optionnel (rel-tag)
** image, optionnel (pour inclusion dans la ligne, à la différence de l'url)
** copyright, optionnel (rel-license)
** ''que manque t'il d'autre ?''
*** language, optionnel

''Paraît bien, mais je m'interroge sur l'utilisation de la hCard pour les noms. Du fait des problèmes d'ambiguité, obliger hCard conduirait à un balisage supplémentaire afin de s'appliquer simplement à un nom, de ce fait [http://microformats.org/discuss/mail/microformats-discuss/2006-March/003487.html le besoin d'un élément racine]. Nous devrions extraire l'optimisation N de hCard que nous avons faite avec adr, afin de faciliter ce problème.'' --[[User:RCanine|Ryan Cannon]]

Peut-être qu'une 'Retrieved Date' ou 'Access Date' serait pertinente pour citer des ressources en ligne. Par exemple sur http://www.crlt.umich.edu/publinks/facment_biblio.html
vous voyez des citations comme cela <nowiki>:</nowiki>
<blockquote>
Chief Academic Officers of the Big 12 Universities (2000). Big 12 Faculty Fellowship Program. Retrieved December 20, 2000 from the World Wide Web: http://www.k-state.edu/provost/academic/big12/big12guide.htm.
</blockquote>
--[[User:JoeAndrieu|Joe Andrieu]]

==== Discussion sur la citation de Cas Légaux====
Besoin d'un exemple. Voilà quelque info que j'ai trouvée en citant la loi :

Je ne suis pas juriste, par conséquent je fais confiance au [http://www.legalbluebook.com "blue book" standard] publié, au moins la seule partie que je peux avoir sans payer $25. Je serais heureux d'entendre des améliorations d'experts dans le secteur - comment font les juristes pour baliser les références vers des cas juridiques en HTML ?

Extrait de groklaw.net et eff.org, je trouve essentiellement des liens vers des PDFs avec le nom du cas comme le lien texte. Ou juste ceci, extrait de l'EFF :
<pre><nowiki>
<h1>The Betamax Case</h1>
<h2>Sony Corp. of America v. Universal City Studios, 464 U.S. 417 (1984)</h2>
</nowiki></pre>

Extrait d'un exemple sur les bluepages échantillons : http://www.legalbluebook.com/pdfs/bluepages.pdf
5 composants basiques :
*1 nom du cas (citation title)
*2 source publiée dans lequel le cas peut être trouvé (citation contenant publication ?)
*3 une parenthèse indiquant le tribunal et l'année de décision (lieu citation ?)
*4 autres informations entre parenthèses, s'il y en a (notes de citation ?)
*5 histoire subséquente du cas, s'il y en a (notes citation ?)

Voici deux exemples extrait du bluebook. Notez qu'il existe des règles très strictes à propos des abréviations dans cette source !

Holland v. Donnelly, 216 F. Supp. 2d 227, 230 (S.D.N.Y. 2002), aff'd, 324 F.3d 99 (2d Cir. 2003).

Green v. Georgia, 442 U.S. 95, 97 (1979) (per curiam) (holding that exclusion of relevant evidence at sentencing hearing constitutes denial of due process).

== Exemples dans la jungle ==
Les pages qui commencent à utiliser la discussion au-dessus pour créer des exemples de travail en utilisant hCite :
(Cette section pourrait être utilisé comme une base pour une page à créer plus tard comme "hcite-examples-in-wild-fr").

SVP ajoutez de nouveaux exemples en haut de cette section.
* [http://www.demo.vorlagen.uni-erlangen.de/univis/mitarbeiter.shtml/georg-hager.shtml Exemple de page utilisateur] sur le laboratoire informatique régional d'Erlangen, Allemange, basé sur le système d'information universel UnivIS balisé avec vcard, hcalendar (optionnel, si l'utilisateur fait un court) et hCite.

== discussions ==
* [[citation-irc-notes-2006-04-09]]