Microformats Wiki - User contributions [en]

mfbot

2009-01-13T23:56:05Z

RyanKing: test

I've created a simple little [[irc]] bot to publish changes from this wiki to #microformats. The code is available on [http://github.com/ryanking/mfbot/tree/master github].

== see also ==
* [[irc]]
* [[mflogbot]]

test

mfbot

2009-01-13T20:45:55Z

RyanKing: delta test

mfbot

2009-01-12T21:02:01Z

RyanKing: update for new mfbot

<h1>mfbot</h1>

I've created a simple little [[irc]] bot to publish changes from this wiki to #microformats. The code is available on [http://github.com/ryanking/mfbot/tree/master github].

== see also ==
* [[irc]]
* [[mflogbot]]

mfbot

2009-01-12T20:54:56Z

RyanKing: it might be working now

<h1>mfbot</h1>

I've created a simple little [[irc]] bot (from parts provided by MediaWiki) to publish changes from this wiki to #microformats.

If [[mfbot]] leaves the room, please feel free to bug me (irc, aim or email) -> [http://theryanking.com/blog/contact/]

--[[User:RyanKing|RyanKing]] 21:06, 8 Oct 2005 (PDT)

== edit character counts ==

mfbot appends a number with a '+' or '-' sign, to indicate the number of characters added or removed as a result of the edit.

== see also ==
* [[irc]]
* [[mflogbot]]

test1

mfbot

2009-01-12T20:47:49Z

RyanKing: testing for new mfbot

mfbot

2009-01-12T20:34:04Z

RyanKing: testing for new mfbot

mfbot

2009-01-12T20:32:55Z

RyanKing:

mfbot

2009-01-09T21:38:58Z

RyanKing: hopefully the last test

mfbot

2009-01-09T21:35:16Z

RyanKing: still testing new mfbot

mfbot

2009-01-09T03:03:29Z

RyanKing: yet another mfbot test

mfbot

2009-01-09T03:02:26Z

RyanKing: another mfbot test

mfbot

2009-01-09T02:53:56Z

RyanKing: testing for new mfbot

User talk:JasonGarber

2009-01-08T20:08:35Z

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

{{welcome}}

:[[User:AndyMabbett|Andy Mabbett]] 08:26, 23 Mar 2007 (PDT)

User:MarkLentczner

2009-01-08T20:08:24Z

RyanKing: Reverted edits by OumonCacbo (Talk) to last version by Tantek

== Mark Lentczner ==

You can find out more at [http://www.ozonehouse.com/mark/ my home page].

I work at [http://lindenlab.com Linden Lab], engineering the infrastructure of [http://secondlife.com Second Life].

I am the principle designer by the experimental (and far from complete) programming language [http://www.wheatfarm.org/ Wheat].

RyanKing

2009-01-08T20:08:17Z

RyanKing: Reverted edits by TrocnOerla (Talk) to last version by Tantek

#REDIRECT [[User:RyanKing]]

presentations

2009-01-08T20:08:07Z

RyanKing: Reverted edits by VipasRodar (Talk) to last version by Csarven

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

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

Most recent presentations/sessions listed first.

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

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

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

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

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

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

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

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

== 2004 ==

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

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

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

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

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

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

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

rest/opacity

2009-01-08T20:07:53Z

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

''(Adapted from a post by RESTfather [http://roy.gbiv.com/ Roy Fielding] on [http://groups.yahoo.com/group/rest-discuss/message/5369 rest-discuss]; used by permission. The context was a discussion about what Tim Berners-Lee meant by his so-called 'Opacity Axiom', specifically how it applies to REST.)''

= Roy on Opacity in REST =

== Historical Context ==
...In order to understand TimBL's design notes, you have to know about the context in which
he is writing a response. In this case, various thoughts were
recorded as the "Opacity Axiom" in response to a discussion about
client behavior and the perceived need for URNs. It has long
since been taken out of context and abused in various ways.

Also, keep in mind that TimBL's design note was written two
years after Henrik and I [Roy Fielding] worked out the important bits of what
would become the HTTP object model, later re-named REST to get
away from OOM terms, about 18 months after we had similar
discussions at MIT with TimBL and the rest of the W3C team, and
more than a year after HTTP/1.0 was finished and HTTP/1.1 proposed.
So, saying it was something that I "didn't really care to
integrate so much" is missing the mark by quite a bit -- he is
trying to describe our model to people who did not understand it.

== Original Intent ==

The opacity principle, as actually used on the Web, refers only
to the machine interpretation of request processing as being
dependent on control data (e.g., hypertext anchors and message
field names) rather than on metadata appearing within the URI.
It is the same reason why we distinguish media types from data
formats -- the fact that a string of bytes looks like angle tags
doesn't mean we want to process it as HTML. Ignoring any
semantically significant data in a URI allows operations on a
resource to be orthogonal to identification of the resource.

REST does include the opacity axiom in the original sense of
that phrase. I did not use it by name in REST because it isn't
a principle at all -- opacity is just a name TimBL used for the
set of constraints around URI processing by clients (a byproduct
of the constraints that you will find in REST). The principle
involved is orthogonal design.

== Applicability to Clients ==

"Opacity of URI" only applies to clients and, even then, only to
those parts of the URI that are not defined by relevant standards.
Origin servers, for example, have the choice of interpreting a
URI as being opaque or as a structure that defines how the server
maps the URI to a representation of the resource. Cool URIs will
often make a transition from being originally interpreted as
structure by the server and then later treated as an opaque
string (perhaps because the server implementation has changed
and the owner wants the old URI to persist). The server can make
that transition because clients are required to act like they
are ignorant of the server-private structure.

Clients are allowed to treat a URI as being structured
if that structure is defined by standard (e.g., scheme and
authority in "http") or if the server tells the client how its
URI is structured. For example, both GET-based FORM actions and
server-side image map processing compose the URI from a
server-provided base and a user-supplied suffix constructed
according to an algorithm defined by a standard media type.

== The Bottom Line ==

Note, however, that some people have taken the mere title of
"opacity" and assumed that it meant URIs should not have
meaningful construction at all. TimBL's axiom doesn't say
that and neither does REST.

= Summary by Jon Hanna =
(extracted from the microformats-rest mailing list; headers added later)

== Opacity Option ==

I think it's important that URIs *can* be treated opaquely - you can
link to them, you can cache their resources without processing them
beyond naive string-matching, process RDF graphs again without
processing them beyond naive string-matching, and so on.

== Non-Opacity Option ==

This does not preclude the fact that agents *may* construct or parse
URIs in more sophisticated ways, it just means that agents don't have
to, especially in the case of agents that are not aware of the specific
purpose of the application.

= Further Clarification by Roy =

== Not Quite ==

Er, not quite. The key is that the '''server''' is free to tell the client
that there does exist structure in a given URI-space, and then the
client is free to make use of ''that'' knowledge in future requests.
That is how server-side imagemaps worked -- HTML says that the src
URI is structured such that appending "?X,Y" to that URI, where
X and Y are non-negative integers, corresponds to points on a map
that can respond to future GET requests.

Thus, one way for the server to tell the client that a given URI
is structured is to provide the URI in a standard element of a
standard media type that has been defined as such. Another is to
include the URI in a response header field.

== Caveat to the Caveat ==

Note, however, that I am also one of the creators of the robots.txt
standard. That particular scenario requires that the spider find out
the constraints on a site prior to the very first access of a real
hypertext link. It is too late to obtain that information by
looking at header fields after a normal request is made. Adding a
new method to HTTP was out of the question because it would have
to be deployed before it could be used
''[OPTIONS could fulfill that purpose today, 12 years after robots.txt was defined]''.
Adding fields to DNS wasn't an option back then, either. Reserving /robots.txt
remains the best option given the alternatives available.

Note, however, that no other "reserved URI" features have the same
requirements as spiders, so it is still true that favicon and pics
chose the wrong solution.

= Final Comment By Dr. Ernie Prabhakar =

This implies to me that the ''server'' could use a specific microformat to indicate that a given URL can be treated in a particular way. In the absence of a such a microformat, clients should not make any such assumptions; further, servers should avoid requiring clients to understand that microformat in order to receive service.

= See Also =

* The treatment of URI opacity on the [http://rest.blueoxen.net/cgi-bin/wiki.pl?RestAndUriOpacity RestWiki].
* Sean McGrath's parable on [http://www.itworld.com/Tech/2327/nlsebiz070123/pfindex.html ITworld].

= Issues=
==Questions by Mike Schinkel==
1.) Ernie, you state the following:
<blockquote>''Cool URIs will often make a transition from being originally interpreted as structure by the server and then later treated as an opaque string (perhaps because the server implementation has changed and the owner wants the old URI to persist). The server can make that transition because clients are required to act like they are ignorant of the server-private structure.''</blockquote>
This doesn't quite sit right with me for some reason. Doesn't "opacity" refer to how a client sees the URI, not how a server sees it? To the server, nothing is/needs to be opaque, right? As such the change from a file/directory to a virtual reference inside the server configuration should have absolutely no relevence to the client and no relevence to the fact that the server/authority might have previously defined the URI structure for specific processing by a client. In the later case a change in server implementation should be totally invisible to any given client. Right?
:Sure, "the opacity axiom" is specifically about client-side implementations, but I was referring to the more general concept of an "opaque string." My point was merely to illustrate that the server could choose whether or not to treat the URI as opaque (contrast how Apache and Squid satisfy URI requests) '''because'' the client (absent information to the contrary for the server) '''is''' required to treat the URI as opaque.[[User:DrErnie|Dr. Ernie]] 13:48, 23 Jan 2007 (PST)

2.) Additionally, you state:

<blockquote>''This implies to me that the server could use a specific microformat to indicate that a given URL can be treated in a particular way. In the absence of a such a microformat, clients should not make any such assumptions; further, servers should avoid requiring clients to understand that microformat in order to receive service. ''</blockquote>

Can you give an example of such a Microformat? Does one exist, or is it hypothetical on your part? Also, wouldn't such a "Microformat" be, almost by definition, non-visible and thus according to community concensus not a Microformat? (more of a "Microdirective", if you will. :)
:Actually, it might be more helpful to think of this in the context of an HTML form, which is a type of semantic markup that provides guidance for humans (and potentially machines) about how to contruct appropriate URLs. A hypothetical microformat (no, I don't know of any so far) would most likely be some sort of "rel" relation on an anchor or form tag, and thus still "visible" in the usual sense.[[User:DrErnie|Dr. Ernie]] 13:48, 23 Jan 2007 (PST)

Thanks in advance for the clafifications.

[[User:MikeSchinkel|MikeSchinkel]] 14:44, 19 Nov 2006 (PST)

microformats-fr

2009-01-08T20:07:04Z

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

<h1> microformats </h1>
{{TOC-right}}
== Que sont les microformats ? ==

* Auteur / Editeur : '''Tantek Çelik'''
* (traduction Christophe Ducamp)

=== les microformats sont ===
* un moyen de penser aux données
* des conventions de design pour les formats
* adaptés aux comportements actuels et aux formes d'usages ([http://www.elanceur.org/microformats/traductions/paverlechemindesvaches.html "Paver le chemins des vaches." - Adam Rifkin])
* hautement corrélés avec le XHTML sémantique, aussi connu comme le [http://www.elanceur.org/microformats/slides/semantiquevraimonde.html sémantique du vrai monde, aussi connu comme le web sémantique en bas de casse], à savoir un [http://www.elanceur.org/microformats/traductions/losslessxhtml.html XTHML sans fin]
* décrits [http://tantek.com/log/2005/03.html#d13t1722 par la présentation de Tantek au SXSW : The Elements of Meaningful XHTML] (NDT : [http://www.elanceur.org/microformats/slides/XHTML-ayant-du-sens.html fr])
* un ensemble de standards de formats de données ouverts et simples que beaucoup (y compris Technorati) sont actuellement en train de développer activement et d'implémenter pour un blogging plus/mieux structuré et la publication de micro-contenus web en général.
* [http://www.elanceur.org/microformats/traductions/unerevolutionevolutionnai.html ""Une révolution évolutionnaire"" - Ryan King]
* tout ce qui est au-dessus.

=== ce que ne sont pas les microformats ===
* un nouveau langage
* infiniment extensibles et ouverts sans fins
* une approche complètement nouvelle qui jette ce qui fonctionne aujourd'hui
* une panacée pour toutes les taxonomies, ontologies et autres abstractions de la sorte
* en train de définir le monde entier, ou même simplement en train de faire bouillir l'océan
* rien de tout ce qui est au-dessus

== les principes des microformats ==
Voir [[principles-fr|principes]].

== citations ==
Voir aussi [[principles-fr#citations|citations en rapport avec les microformats]].
== microformats actuels ==
Voir la [[Main_Page-fr|page principale]] pour une liste actuelle des spécifications de microformats, brouillons et discussions.

== Plus d'idées sur la façon dont les microformats sont différents ==
Il existe beaucoup de formats existants qui sont ''presque'' totalement inutiles/ignorés.

Ils ne sont néanmoins pas ''complètement'' inutiles. Ils sont utiles en ce sens qu'ils illustrent ce qu'au moins quelqu'un a pensé à quoi qu'ils pourraient être utiles, ce qui malheureusement relève d'un inventeur seul travaillant à priori sans quelque expertise dans un domaine.

Ou il y a l'autre extrême. Beaucoup d'inventeurs en entreprise travaillant avec beaucoup d'expérience, sur-designant un format pour ce qui ''pourrait'' être demandé un jour. Dans les mauvais cas particuliers, les vendeurs de sociétés sont de connivence pour empêcher l'ouverture et/ou l'adoption par la communauté open source. Les standards média [http://dannyayers.com/archives/2005/09/24/qotd-23/ souffrent souvent de cette forme de positionnement délibérément "stratégique"].

Nous cherchons à combattre tous ces problèmes avec l'approche microformat.

* Nous ne sommes pas des inventeurs isolés ; nous sommes une [http://microformateurs.org/discussion/ communauté].
* Nous ne travaillons pas [http://fr.wikipedia.org/wiki/A_priori a-priori] ; nous exigeons de la documentation provenant d'exemples existants, des essais précédents sur les formats. Voir le [[process-fr|processus]].
* Quand nous manquons d'une expertise dans un domaine, nous cherchons les experts du domaine pour la fournir, et nous nous immergeons nous-mêmes dans les exemples et l'art initial du domaine (voir point précédent)
* Nous faisons notre travail dans l'[[Main_Page-fr|ouverture]] avec les [http://microformateurs.org/discussion/ forums de discussion ouverts].
* Nous sommes un mélange diversifié d'indépendants, d'entreprises, d'amateurs et d'enthousiastes.
* Nous ne faisons pas d'over-design. Nous faisons de l'under-design, délibérément et puis nous n'ajoutons seulement des choses que quand elles sont absolument nécessaires.
* Nous adoptons une politique de licence/copyright très libérale (<span class="vevent"><span class="summary">domaine public - [http://microformateurs.org/2007/12/30/tantek-celik-faire-que-les-standards-ouverts-soient-aussi-ouverts-que-possible-licence-domaine-public-exigee-pour-toutes-les-contributions-sur-le-wiki-des-microformats/ requis à partir du <span class="dtstart">2007-12-29</span> pour les contributions sur le wiki des microformats]</span></span>, [[creative-commons-fr|CC]], [[gmpg-fr|GMPG]], [[ietf-fr|IETF]], [[w3c-fr|W3C]]) et positions sur le brevets (<abbr title="royalty free">libres de droit</abbr>, [[ietf-fr|IETF]], [[w3c-fr|W3C]])
* Nous nous auto-critiquons impitoyablement en nous basant sur nos [[principles-fr|principes]] afin de maintenir les points ci-dessus.

Quelques personnes se demandent quel est l'objectif des standards (voulus)

Pourquoi avez-vous besoin d'un but ? Plus souvent que non, la concentration prématurée sur le but tend à altérer les formats de données envers une application particulière qui peut ne pas du tout être pertinente. Par conséquent, plutôt que de se concentrer sur un but à priori, nous nous concentrons sur la modélisation du comportement existant, en sachant qu'une structure additionnelle parviendra à beaucoup d'usages intéressants, que pour la plupart d'entre eux nous ne pourrions pas prévoir à priori.

Ceci est évidemment une approche très différente des efforts fournis sur les formats traditionnels de données.

Positivez avec itération plutôt que négativement avec de l'inaction.

Les Microformats tendent à adopter une attitude positive de développement et en utilisant les meilleurs techniques nous pouvons en sortir (et itérer dessus), plutôt que de bannir ou bloquer les techniques pour des raisons de crainte. Pour laisser tomber quelque chose, il doit y avoir une meilleure alternative fournie qui résoud au moins tout aussi bien le(s) même(s) problème(s), à des coûts moins élevés.

xoxo-fr

2009-01-08T20:06:47Z

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

<h1> XOXO 1.0 : eXtensible Open XHTML Outlines </h1>

XOXO est un simple format ouvert d'outline écrit en XHTML standard et adaptable pour embarquement dans (X)HTML, Atom, RSS et le XML arbitraire.
XOXO est l'un des nombreux [[microformats-fr|microformats]] standards ouverts .

__TOC__

== Spécification Brouillon du 01-Octobre-2004 ==

=== Editeur ===
[http://tantek.com/ Tantek Çelik], ([http://technorati.com Technorati, Inc])

=== Auteurs ===
* [http://epeus.blogspot.com/ Kevin Marks], ([http://technorati.com Technorati, Inc])
* [http://tantek.com/ Tantek Çelik], ([http://technorati.com Technorati, Inc], formerly of [http://microsoft.com/ Microsoft Corporation])
* [http://diveintomark.org/ Mark Pilgrim], ([http://ibm.com IBM])
* [http://www.blogologue.com/ Morten W. Petersen]

=== Traducteur(s) ===
* [[Christophe Ducamp]]

=== Copyright ===
{{MicroFormatCopyrightStatement2003-fr}}

* [[User:Tantek|Tantek]] : Je "release" toutes mes contributions sur cette spécification dans domaine public et encourage les autres auteurs à faire de même.
** Quand tous les auteurs/éditeurs auront fait ainsi, nous pourrons retirer le modèle MicroFormatCopyrightStatement de réféence et le remplacer avec le modèle MicroFormatPublicDomainContributionStatement.

=== Brevets ===
{{MicroFormatPatentStatement-fr}}

== Préambule ==
Quand nous avons discuté d'[http://developers.technorati.com/wiki/attentionxml Attention.xml], Tantek faisait remarquer que XHTML a tout ce qui est nécessaire pour exprimer sémantiquement des outlines et des abonnements comme des blogrolls dans un format XML qui soit à la fois restituable interactivement par des navigateurs et parsable par des moteurs XML strict. Cette page est ici pour disctuer de cette idée.

=== Nom ===
XOXO veut dire eXtensible Open XHTML Outlines, et se prononce selon 'icks oh icks oh', 'zho-zho', ou 'cho-cho'.

== Abstract ==
XOXO est l'un des nombreux [[microformats-fr|microformats]]. Cette spécification définit un nouveau type de document XHTML basé sur le squelette module et les modules définis dans Modularisation du XHTML ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). Le but du type de document XOXO est de servir de base pour des outlines XHTML faciles qui puissent être traités par les moteurs XML et pour une restitution interactive facile par les navigateurs.

== Le type de Document XOXO ==
Le type de document XOXO est construit sur les modules suivants XHTML.
Les éléments, attributs et modèles de contenu minimal associés avec ces modules sont définis dans "Modularization of XHTML" ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]).
Les éléments sont listés ici à des fins d'information, mais les définitions dans "Modularization of XHTML" devraient être considérées comme définitives. Dans la version en ligne de ce document, les noms de modules dans la liste en-dessous pointent dans les définitions des modules dans la version actuelle de "Modularization of XHTML".

[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_structuremodule Structure Module]
body, head, html, title
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_hypertextmodule Hypertext Module]
a
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_listmodule List Module]
dl, dt, dd, ol, ul, li
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_metamodule Metainformation Module]
meta
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_stylemodule Stylesheet Module]
style element
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_styleattributemodule Style Attribute Module]
style attribute
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_linkmodule Link Module]
link
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_legacymodule Legacy Module]
Attribute compact on ol and ul

=== Le Profil XOXO ===

Voir [[xoxo-profile-fr|xoxo-profile]] pour le profil [http://gmpg.org/xmdp XMDP] de XOXO qui définit les valeurs XOXO pour l'attribut class.

== Fragment Simple XOXO ==

=== Balisage ===

<pre><nowiki><ol class='xoxo'>
<li>Sujet 1
<ol>
<li>souspoint a</li>
<li>souspoint b</li>
</ol>
</li>
<li>Sujet 2
<ol compact="compact">
<li>souspoint c</li>
<li>souspoint d</li>
</ol>
</li>
<li>Sujet 3
<ol>
<li>souspoint e</li>
</ol>
</li>
</ol>
</nowiki></pre>

=== Restitution Echantillon ===
<pre><nowiki>
1. Sujet 1
a. souspoint a
b. souspoint b
2. Sujet 2
3. Sujet 3
a. souspoint e
</nowiki></pre>
=== Usage de l'attribut 'compact' ===
Notez l'utilisation de l'attribut 'compact' pour indiquer que les sous-points du titre "Sujet 2"
ne sont pas dans un état déployé. L'absence de l'attribut 'compact' ailleurs indique que les autres titres
sont en état déployé.

=== Règles de Style par Défaut pour une Restitution Echantillon ===
<pre><nowiki>
ol.xoxo { list-style:decimal; }
ol.xoxo ol { list-style:lower-latin; }
ol[compact="compact"] { display:none; }
</nowiki></pre>

== Plus d'Exemples Simples ==
MarkP a un ensemble d'exemples qui démontrent à la fois la simplicité du balisage et la richesse de présentation possible :

* [http://diveintomark.org/public/2004/01/xo-flat.xo fichier simple XO qui peut être directement embarqué à l'intérieur d'une page XHTML]
* [http://diveintomark.org/public/2004/01/xo-embeddable.xo XO avec groupes imbriqués, aussi directement embarcables dans le XHTML]
* [http://diveintomark.org/public/2004/01/xo-standalone.xo XO comme page XHTML autonome] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-standalone.xo XHTML valide])
* [http://diveintomark.org/public/2004/01/xo-with-style.xo XO comme page XHTML autonome, mise en forme avec CSS] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-with-style.xo aussi valide XHTML])
* [http://homepage.mac.com/ctholland/thelab/outlines/ Chris Holland Outline Helper] : tordu l'un des exemples au-dessus, yanked CSS pour la simplicité, ajouté référence vers [http://homepage.mac.com/ctholland/thelab/outlines/outlines.css outlines.css] et [http://homepage.mac.com/ctholland/thelab/outlines/outlines.js outlines.js], copié quelques combinaisons différentes de ul/ol/li avec l'attribut compact.
** en essayant de rester compatible avec les principes de l'attribut "compact" pour les éléments ol et ul est ce qui conduit à l'état d'affichage.
Via la programmation, je suis en train d'installer des classes sur l'élément conteneur li pour une flexibilité ajoutée de style, même si les gourous CSS pourraient être capables de remplacer "li.expanded" dans outlines.css avec quelque autre sélecteur CSS qui dise "sélectionnez un noeud li qui contient un noeud ol avvec un réglage d'attribut sur 'compact' ".

*** Le sélecteur CSS pour "un noeud li qui contient un noeud ol avec un ensemble d'attribut 'compact'" serait 'li ol[compact="compact"]'

== Propriétés des Items Outline ==
Outlines consiste généralement en une hiérarchie de points et sous-points.
Chacun de ces points (items outlines) peut avoir lui-même quelques propriétés (comme des attributs ou des méta-données) qui ont besoin d'être représentées. Peut-être que la propriété supplémentaire la plus commune sur les items d'outline est en pratique l'URL comme cela est démontré dans les exemples de Mark Pilgrim au-dessus. Même le texte label/title d'un item outline pourrait être considéré comme une propriété commmune. Quelques propriétés communes :
* text
* description
* url (souvent appelé xmlurl ou htmlurl ; parfois appelé permalink)
* title
* type (truc du MIME type de la ressource indiqué par l'URL)

En général, les propriétés d'un item outline <code><nowiki><li></nowiki></code> sont représentées par une liste de définitions imbriquées <code><nowiki><dl></nowiki></code>. A strictement parler, c'est le premier <code><nowiki><dl></nowiki></code> à l'intérieur du <code><nowiki><li></nowiki></code> et avant tout <code><nowiki><ol></nowiki></code>, <code><nowiki><ul></nowiki></code>, ou <code><li></code> suivant, par ex. voici un item "item 1" avec une propriété de description (les sous-points sont là purement comme un point de référence vers un exemple antérieur).

<pre><nowiki>
<ol class='xoxo'>
<li>item 1
<dl>
<dt>description</dt>
<dd>cet item représente le point principal que nous essayons de produire.</dd>
</dl>
<ol>
<li>souspoint a</li>
<li>souspoint b</li>
</ol>
</li>
</nowiki></pre>

=== Propriétés Spéciales ===
Il existe un paquet de propriétés spéciales que nous pouvons représenter plus directement
et de façon commode avec les blocs de construction du XHTML sémantique que nous avons inclus, au lieu de termes dans une liste de définition. La plupart sont extraits de la liste au-dessus des propriétés communes, ce sont :
* text, url, title, type, et rel (raccourci de relationship)

Si nous devions les représenter simplement comme des termes de définition (y compris la propriété "description" tirée du précédent exemple), cela pourrait ressembler à quelque chose comme ça :

Exemple pour recherche de discussion seulement / pas un exemple canonique XOXO :

<pre><nowiki>
<ol class='xoxo'>
<li>
<dl>
<dt>text</dt>
<dd>item 1</dd>
<dt>description</dt>
<dd> Cet item représente le point principal que nous essayons de produire.</dd>
<dt>url</dt>
<dd>http://exemple.com/plus.xoxo</dd>
<dt>title</dt>
<dd>titre de item 1</dd>
<dt>type</dt>
<dd>text/xml</dd>
<dt>rel</dt>
<dd>aide</dd>
</dl>
</li>
</nowiki></pre>

Néanmoins, en tirant profit de l'élément sémantique <code><a href></code>, nous pouvons dramatiquement simplifier les cases communes qui utilisent ces propriétés. Du point de vue d'un parseur, ceci s'applique au premier élément <code><a href></code> diretement dans le <code><nowiki><li></nowiki></code>.

Exemple véritable XOXO :

<pre><nowiki>
<ol class='xoxo'>
<li><a href="http://exemple.com/more.xoxo"
title="titre item 1"
type="text/xml"
rel="help">item 1</a>

<dl>
<dt>description</dt>
<dd>Cet item présente le point principal que nous essayons de produire.</dd>
</dl>
</li>
</nowiki></pre>

Toutes les autres propriétés sont simplement ajoutées à la liste de définition
de la même façon que la propriété "description".

=== Propriétés Multi-valeurs ===

Les propriétés qui ont plusieurs valeurs sont ajoutées en utilisant une liste, imbriquée à l'intérieur de l'élément correspondant <code>dl</code> :

<pre><nowiki>
<ol class='xoxo'>
<li>item 1
<dl>
<dt>multivalpropriete1</dt>
<dd><ul>
<li>valeur-a</li>
<li>valeur-b</li>
</ul></dd>
</dl>
</li>
</ol>
</nowiki></pre>

== Publier XOXO ==
XOXO peut être pubié sous deux formes, XHTML valide, et XML simple et bien formé.

=== XOXO XHTML Valide ===
Une page XOXO XHTML Valide est un document XHTML complet.

<pre><nowiki>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>XOXO page</title>
</head>
<body>
<ol class="xoxo">
<li><a href="URL-un">TEXT-un</a></li>
<li><a href="URL-deux">TEXT-deux</a></li>
...
</ol>
</body>
</html>
</nowiki></pre>

=== XOXO XML Simple bien-formé ===
L'élément racine d'une page XOXO XML simple bien formé est soit un <code>ol</code> ou <code>ul</code> avec le nom de classe de "xoxo". Cette variante est idéale pour la syndication et la transclusion à l'intérieur de pages (X)HTML avec [[rest/ahah|AHAH]].

<pre><nowiki>
<ol class="xoxo">
<li><a href="URL-un">TEXTE-un</a></li>
<li><a href="URL-deux">TEXTE-deux</a></li>
...
</ol>
</nowiki></pre>

=== Content-Type ===
Le XHTML XOXO valide et bien formé DEVRAIT être servi avec cet en-tête Content-Type pour une compatibilité navigateur maximale :
<pre><nowiki>
Content-Type: text/xml; charset=utf-8
</nowiki></pre>

Il DOIT être servi avec un de ces en-têtes Content-Type :

<pre><nowiki>
Content-Type: text/html; charset=utf-8
Content-Type: application/xhtml+xml
Content-Type: application/xml
</nowiki></pre>

== Exemples dans la Jungle ==
Cette section est '''informative'''.

Il existe beaucoup trop d'exemples dans la jungle. Presque chaque blogroll sur le web peut être parsée avec XOXO, parce qu'elles sont généralement une liste non ordonnée d'items de listes d'hyperliens, ce qui est dans le profil XOXO. Listez ici les exemples et quand la liste sera trop longue, nous la migrerons sur une page dédiée.

* [http://api.talis.com/bf/stores/ukbib/services/facet?query=feynman&fields=title%2Csubject&top=10&output=html sortie HTML à partir d'un service à facette pour des données de livres]

== Implémentations ==
Cette section est '''informative'''.

* [http://chneukirchen.org/blog/ Christian Neukirchen] a [http://chneukirchen.org/blog/archive/2006/01/xoxo-rb-0-1-released.html écrit un xoxo.rb, un parseur XOXO et un générateur pour Ruby]
* [http://odeo.com Odeo] publie les liste d'abonnements utilisateurs dans XOXO. Voir la liste de Ryan King [http://odeo.com/profile/RyanKing/xoxo ici].
* [http://www.decafbad.com/blog/ Les Orchard] a [http://www.decafbad.com/blog/2005/07/12/xoxo_outliner_experiment écrit] un [http://www.decafbad.com/2005/07/map-test/tree2.html bel éditeur XOXO en javascript].
* http://homepage.mac.com/ctholland/thelab/outlines/ est une démonstration géniale du XOXO dynamique et interactif avec l'utilisation de "compact" et du DHTML pour déployer/replier.
* http://tool-man.org/examples/sorting.html est une démonstration géniale de listes XOXO "glisser déposer" triables avec javascript and CSS.
* http://www.joshpeek.com/projects/opmltoxoxo est un convertisseur extensible de OPML vers XOXO.
* http://www.opendarwin.org/~drernie/xoxo-datatypes.html Mapper XOXO en [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Concepts/XMLPListsConcept.html listes de propriétés Mac OS X]
* [http://weblog.techno-weenie.net/2005/9/30/if_i_had_a_tumblelog ligne unique de rails pour convertir XOXO en HTML]

=== Code échantillon ===
* Voir la page [[xoxo-sample-code-fr|xoxo-code-échantillon]] pour un code échantillon open source afin de lire et écrire des fichiers XOXO.
* Voir aussi la page [[xoxo-compact-sample-fr|xoxo-échantillon-compact]] avec la source pour le CSS et JS qui altère le "look and feel" de quelque XOXO pour avoir des triangles dépliables dans les listes imbriquées qui respectent aussi l'attribut compact.

== Schémas XOXO ==
Cette section est "informative".

Note : ces liens peuvent être démodés et ont besoin d'être mis à jour pour refléter l'utilisation de <dl> pour l'annotation d'items XOXO avec des propriétés arbitraires.
* [[DTDs]]
* [http://www.nidelven-it.no/projects/XOXO/xoxo-0.1.tgz Schemas (Relax NG and DTDs)]

== Références ==
=== Références "Normatives" ===
* [http://www.w3.org/TR/xhtml1 XHTML 1.0]
* [http://www.w3.org/TR/xhtml-modularization XHTMLMOD]
* [http://gmpg.org/xmdp/ XMDP]
* [http://gmpg.org/xfn/ XFN]

=== Références "Informatives" ===
Cette section est '''informative'''.
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]
* [[vote-links-fr|VoteLinks]]
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]
* [http://opml.scripting.com/spec OPML 1.0]
* Contribution provenant de http://developers.technorati.com/wiki/XOXO

=== Travaux similaires ===
* [http://dannyayers.com/archives/001961.html XHTML Outlines] - DannyAyers a sorti indépendamment l'idée en octobre 2003 (juste un mois ou deux avant que Kevin et Tantek se sortent indépendamment XOXO) d'utiliser un simple profil XHTML
pour représenter sémantiquement les outlines en utilisant des blocs de constrution existant provenant du XHTML.
* [http://semtext.org/2004-02/ XOW] - les rend éditables, produisant des listes de RDF et bookmark à partir d'eux (DannyAyers)

=== Lecture en Rapport ===
* [http://patricklogan.blogspot.com/2005/08/lists-really-can-we-expect-better.html Patrick Logan sur pourquoi OPML et une extension Microsoft Lists sont tous deux non nécessaires].

=== Lecture sans aucun rapport ===
* [http://www.questionablecontent.net/view.php?comic=493 Questionable Content comic #493] - apparemment le personnage Faye est un fan of XOXO.

=== Contenus Promotionnels / Schwag ===
* Il existe toute une ligne de vêtements et d'accessoires en ligne. [http://www.xoxo.com/home.php Buy XOXO stuff online].

== Discussions ==
Cette spécification est un chantier en cours. Au fur et à mesure que des aspects supplémentaires sont discutés, compris et écrits, ils seront ajoutés. Il existe un document séparé où nous gardons traces de nos brainstorms et autres explorations en rapport avec XOXO :

* Voir [[xoxo-brainstorming-fr]] pour des idées supplémentaires sur la façon d'utiliser XOXO pour des usages spécifiques.
* Voir aussi [http://www.technorati.com/cosmos/referer.html les blogs qui discutent de cette page].
** [http://blogxoxo.blogspot.com/ XOXO Blog]

=== Q&R ===
* Si vous avez quelque question à propos de XOXO, regardez les [[xoxo-faq-fr|xoxo-faq]], et si vous ne trouvez pas de réponses, ajoutez vos questions !

=== Problématiques ===
* ajoutez svp toute problématique sur la spécification à la page document séparée [[xoxo-issues-fr|problématiques xoxo]].

events/2006-09-30-london-microformats-vevent

2009-01-08T20:06:05Z

RyanKing: Reverted edits by CopasBocri (Talk) to last version by DronvArget

vargettr
= London Microformats vEvent =

This is a social [[events|event]] planned for 30 September 2006 in London.

__TOC__

== Details ==


;Date: Saturday, September 30th
;Time: 7:30pm til Late
;Location: '''Brew Wharf''' Yard, Stoney Street, London, SE1 9AD
(Brew Wharf is situated in its own yard off Borough Market)

To find out more about the location visit their website: [http://www.brewwharf.com Brew Wharf]

Add yourself to the [http://upcoming.org/event/100107/ Upcoming.org entry]

== Summary ==
This is an informal social for anyone interested in Microformats. Level of expertise, interest or involvement isn't really important. There is no structure for the evening other than having a few drinks at a London ''Micro''brewery and getting the opportunity to meet up with some of the community.

It'll be a good chance to get more involved and maybe learn a bit, discuss any projects you've got on the go, or problems you might be having with Microformats!

== Attending ==
*[[User:Phae|Frances Berriman]] - http://www.fberriman.com
*[[User:DrewMcLellan|Drew McLellan]] - http://allinthehead.com
*[[User:David|David Singleton]] - http://dsingleton.co.uk
*[[User:DavidRandall|Dave Randall]] - http://www.ie.com
*[[User:Robert Brook|Robert Brook]] - http://www.robertbrook.com, hopefully!
*[[User:MarkNormanFrancis|Mark Norman Francis]] - http://cackhanded.net/
*..

== Blog Posts ==
2006-08-21 [http://www.fberriman.com/?p=90 Microformats London Social] - by [[User:Phae|Frances Berriman]]

== Photos ==

== Additional Links / Information ==

Hotels:
*[http://www.st-christophers.co.uk/london-hostels/london/london-bridge London Bridge]

class

2009-01-08T20:05:58Z

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

'''class''' is a property of the [[hcard|hCard]] and [[hcalendar|hCalendar]] microformats.

For a list of all (X)HTML classes used in microformats, see: [[existing-classes]].

stable-pages

2009-01-08T20:05:49Z

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

= Stable pages =

This is a list of pages that are relatively stable, and have only minimal/editorial changes, which makes them much easier to keep in sync with the English versions when doing translations.

This is somewhat priority ordered, so if you are doing a translation, look at translating earlier pages on the list first.

== Introductory / About ==
# [[Main_Page]]
# [[introduction]]
# [[press]]
# [[presentations]]

== Stable and broadly implemented specifications ==

# [[xoxo]]
# [[rel-tag]]
# [[rel-license]]
# [[hcard]]
# [[hcalendar]]
# [[hreview]]

== Community ==

# [[how-to-play]]
# [[process]]

hcalendar-issues-fr

2009-01-08T20:05:41Z

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

<h1> Problématiques hCalendar </h1>

Ce sont des problématiques externes sur [[hcalendar-fr|hCalendar]] avec différents degrés de mérite. De ce fait, quelques problématiques sont REJETEES pour un bon nombre de raisons évidentes (mais encore documentées ici si elles sont exprimées à nouveau), et d'autres qui contiennent des discussions plus longues.

'''IMPORTANT''' : Lisez SVP les [[hcalendar-faq-fr|FAQ hCalendar]] ''avant'' de donner toute réaction ou soulever quelque problématique parce que vos réactions/quetions peuvent déjà avoir été résolues/fait l'objet d'une réponse.

Les problématiques proposées peuvent (et le seront probablement) éditées et récrites pour une meilleure concision, clarté, rationalité et rester sur un point de vue aussi neutre que possible. Formulez bien vos problématiques. — [http://tantek.com/ Tantek]

Ajoutez SVP vos nouvelles problématiques en '''haut''' de la liste. Relancer SVP vers les problématiques résolues/rejetées avec de nouvelles information plutôt que de soumettre à nouveau de telles problématiques. Les ajouts de problématiques en doublon seront réinitialisés.

Voir [[hcard-issues-fr|problématiques hCard en rapport]].

__TOC__

== Problématiques ==
Ajoutez de nouvelles problématiques '''en haut''' de la liste :

* {{OpenIssue-fr}} 2007-05-12 Un point pertinent extrait de la [http://microformats.org/wiki?title=hcalendar-issues&oldid=16115 version du 22 février 2007] des problématiques hCalendar. Vaut la peine d'être conservé et résolu :
:* {{OpenIssue-fr}} 2007-01-20 soulevée par [[User:AndyMabbett|Andy Mabbett]]
:: Là où <code>DTEND</code> est une date, et non une date-time, il est requis que ce soit le jour après la fin de l'événement, par conséquent : <code><nowiki>
<abbr class="dtend" title="2007-04-30">29 avril 2007</abbr></nowiki></code>. Néanmoins, "29 Avril 2007" n'est '''''pas''''' une abréviation de 2007-04-30 ; c'est une abréviation de 2007-04-29. Le balisage comme montré est sémantiquement incorrect et sujet probablement à problèmes pour les utilisateurs ou agents utilisateurs qui utilisent l'attribut 'title', et non la valeur texte, de l'élément <code>abbr</code>.
::[[User:Webf2|Webf2]] 23:23, 11 May 2007 (PDT)
::*La date ISO 2007-04-30 est directement équivalente à 2007-04-30 00:00:00, ce qui est la raison pour laquelle elle est utilisée à l'heure de fin d'un événement arrivant le 2007-04-29. Dans ce contexte plus complet vous pouvez alors visualiser cela comme une abréviation de 'la fin du 29 avril 2007'. Les auteurs peu à l'aise avec ça pourrait utiliser <nowiki><abbr class="dtend" title="2007-04-29 23:59:59">29 avril 2007</abbr></nowiki>, ou être plus spécifique avec leurs horaires.
:::[[User:CiaranMc|Ciaran McNulty]] 09:21, 12 May 2007 [GMT]
::* This certainly risks confusion. The abbr title includes different information than the content; different when read by a 'normal' user who does not know about the exclusive-end-date.
:::* Le problème va se passer avec les dates (plutôt que les dates-times). L'attente utilisateur est différente qi vous parler de "3 heures", ce qui est vraiment un point dans le temps, et de 29 avril, quelque chose qui dure 24 heures. Pas de problème pour dire qu'une heure de fin est 'exclusive', mais une date de fin peut être et est généralement inclusive.
:::* Utiliser un <code>dtend</code> plus précis est simplement un contournement, vous pourriez ne pas vouloir dire la seconde à laquelle un événement se finit (comme dans 2007-04-29 23:59:59). Vous pourriez facilement vouloir dire que cela tourne du Mercredi au Vendredi sans vous engager sur des horaires préciss - ou que l'événement soit parfois sur ce vendredi mais vous ne savez pas quand.
::: Les options possibles pourraient être :
:::* Inclure une note dans le standard qui aille en marquage contradictoire tel que
:::: <code><nowiki><abbr class="dtend" title="2007-04-30">29 avril 2007</abbr></nowiki></code>
:::: mauvais en pratique et devrait être évité
:::* Faire un break avec l'usage ical que le fait que les dates de fin soient exclusives.
:::* Clarifier le sens :
:::: <code><nowiki><abbr class="dtend" title="value=date:value=inclusive:2007-04-29">29 Avril 2007</abbr></nowiki></code>
:::: <code><nowiki><abbr class="dtend" title="value=exclusive:2007-04-30">29 avril 2007</abbr></nowiki></code>
:::: ou peut-être
:::: <code><nowiki><abbr class="dtend;value=date:value=inclusive" title="2007-04-29">29 avril 2007</abbr></nowiki></code>
::: [[User:Webf2|Webf2]] 00:25, 13 May 2007 (PDT)
* {{OpenIssue-fr}} 2007-01-07 soulevée par [[User:Webf|Webf]]
*# "A la recherche d'un mécanisme pour spécifier un dtstart sans utiliser <nowiki><abbr></nowiki>. Ce serait utilisé où il existe un certain nombre d'événements (comme dans les [http://www.webfeet.org/events.html listes d'événéments de Webfeet]) où vous ne voulez pas avoir la date visible répétée."
*#* <code>abbr</code> est le seul élément correct à utiliser, à moins que vous ne souhaitiez afficher le date-time brut ISO-formaté pour l'utilisateur. Utilisez-le avec l'[[include-pattern-fr|include-pattern]], ce qui donne :

<code>
<pre>
<nowiki>
<dt id="D20070120">
<abbr class="dtstart" title="20070120">
Samedi 20 janvier 2007
</abbr>
</dt>
<dd>
<span class="vevent">
<object class="include" data="#D20070120"></object>
[Détails du premier événement]
</span>

<span class="vevent">
<object class="include" data="#D20070120"></object>
[Détails du second événement]
</span>
</dd>
</nowiki>
</pre>
</code>

:mais notez svp que vous devriez valider votre HTML - il a plus de 3000 erreurs ! le nombre élevé de nombre de microformats hCalendar (>500) amène les parseurs comme Tails de Firefox et Operator à répondre très lentement. Vous devriez utiliser CSS, des espaces non cassés et de nombreux sauts de lignes pour metter en page votre page - ceci réduira sa taille et permettra aux parseurs de travailler plus rapidement. Vous aurez besoin de styler <code>object .include</code> en <code>display:none</code> [[User:AndyMabbett|Andy Mabbett]] 04:10, 16 Jan 2007 (PST)

* {{OpenIssue-fr}} 2006-10-21 soulevée par [[User:AndyMabbett|AndyMabbett]]
*# "Il devrait y avoir quelque moyen de dire que l'URL d'une hCard ou d'un événement hCalendar est l'URL de la page elle-même, sans avoir à inclure un lien redondant et dommageable en accessibilité vers cette page, sur la page elle-même."

* {{OpenIssue-fr}} 2006-09-22 soulevée par [[User:AndyMabbett|AndyMabbett]]
*# "Commment sont affichées les dates Julian ? A la limite de ce que je connais, ISO8601 n'a pas de facilité pour baliser les dates Julian, ainsi la forme <pre><nowiki><abbr class="dtstart" title="[Gregorian date]">[Julian date]</abbr> </nowiki></pre> serait utilisée ? Si oui, ce devrait être indiqué par un exemple."

* {{OpenIssue-fr}} 2006-08-14 soulevée par [[User:Elias|Elias Sinderson]]
*# ''Problématique 1 : Bien qu'ISO 8601 permette à la fois des formats basiques (sans délimiteurs) et des formats étendus, le format étendu est largement préféré (là où les traits d'unions et les 'colons' sont explicitement ajoutés) pour le web. Alors que la RFC 2445 spécifie que le format basique soit utilisé dans les champs iCalendar date / time, le W3C a publié une [http://www.w3.org/TR/NOTE-datetime note] technique (soumise par Reuters), qui recommande que le format étendu (délimité) soit utilisé et la [http://www.w3.org/TR/html401/types.html#h-6.11 spéc HTML 4.0] utilise le format étendu. En outre, la RFC 3339 définit un profil ISO 8601 pour les représentations des dates et time sur l'internet que les spécifications futures DEVRAIENT utiliser ; recommandant une représentation complètement délimitée (voir sec. 5.6). Pour finir, il devrait être noté que les types [http://www.w3.org/TR/xmlschema-2/#date xsd:date] et [http://www.w3.org/TR/xmlschema-2/#dateTime xsd:dateTime] sont spécifiés comme étant le froamt étendu ISO 8601. Par conséquent, compte tenu du fait que hCalendar soit basé sur iCalendar, il est compréhensible que cela permette les deux formats, néanmoins c'est clairement un cas dans lequel il serait vraiment raisonnable de convertir d'obliger les utilisateurs à convertir vers le haut le format vers la représentation la moins ambigue et la plus facilement parsée/validée. Pensez à l'enfant.
* {{OpenIssue-fr}} 2006-03-07 soulevée par [[User:Ragdoll|Justin McDowell]]
*# ''Problématique 1 : j'aimerais voir une liste de propriétés, similaire à celle qui est vue sur la spec hCard, qui liste toutes les propriétés disponibles et sous propriétés dans une liste jolie et compacte. Ceci me ferait gagner beaucoup de temps et s'avère vraiment utile pour faire rapidement et facilement connaissance avec les possibilités de vCalendar.''

* 2006-02-17 soulevée par [[User:Mark Mansour|Mark Mansour]] - les remarques sont résumées [[hcalendar-irc-meetup-20060225|ici]]
*# Est-ce que vcalendar devrait être une classe ? La section 4.4 de RFC2445 dit : "The Calendaring and Scheduling Core Object is a collection of calendaring and scheduling information. Typically, this information will consist of a single iCalendar object. However, multiple iCalendar objects can be sequentially grouped together." Aussi la classe vcalendar permettrait des propriétés sur le calendrier lui-même telles que METHOD et CALSCALE (Je ne pense pas que VERSION et PRODID soient particulièrement pertinents).
*#* SPEC. UPDATE/FAQ ACCEPTEE Est-ce un cas de réparer qeulque chose qui n'est pas cassée ? Remarquez que "iCalendar object" != "vcalendar".
Ceci est un peu confus aussi lisez calmement et avec attention la RFC 2445 à cet égard. En outre, la spec. [[hcalendar-fr|hCalendar]] dirait *précisément* comment générer des propriétés VCALENDAR en son absence.
*# Comment vont se comporter les axes et en-têtes ?
*#* ACCEPTE. Ceci est documenté dans le [[hcalendar-brainstorming-fr]] mais DOIT être migré vers le propre [[hcalendar-fr|hCalendar]] parce que les éditeurs et implémenteurs se sont tous mis d'accord là-dessus (il y a des mois). Ajoutez ceci comme une [[to-do]] pour Tantek.
*# Il y a eu une discussion que l'axe de la table et les en-têtes devraient être utilisés pour saiir l'information du calendrier sous une format plus compact, mais aucun exemple n'est disponible. Est-ce quelqu'un aurait des exmples ou devrions-nous essayer d'en inventer quelques-uns ?
*#* REJETE. Svp RTFM. Chercher la spec [[hcalendar-fr|hCalendar]] pour *soit* l'"axe" ou les "en-têtes" aurait été trouvé en suivant l'exemple suivant dans la jungle : [http://we05.com/ Web Essentials 05] a balisé son [http://we05.com/program.cfm tableau de planning de programme avec hCalendar], en utilisant les attributs 'axes' et les attributs 'en-têtes'.
*# Les composants embarqués devraient-ils être autorisés ? [[RyanKing]] a déjà remarqué que vJournal chevauche les billets de blog (même si ce n'est pas toujours accepté à cette heure), mais les composants to-do, free/busy, timezone, alarms devraient-ils être acceptés ?
Ils ont tous imaginé cela comme aussi pertinent par la spec ical parce que les événements se déroulent (mon implémentation).
*#* SPECUPDATE/FAQ - ACCEPTEE. une autre [[to-do]] pour Tantek.
Spécifiez explicitement quels sont les objets iCalendar (en plus de VEVENT) qui sont permis dans hCalendar. Candidats actuels en plus : VTODO (plein d'exemples de cette information sur le web), VFREEBUSY (déjà au moins sur un site de publier cette info), VALARM (peut-être, me semble grossier, mais sans une exigence du vrai monde pour utiliser le cas que nous devrions probablement ometre). Actuellement en cours de dépose : (construction horrible), VJOURNAL (démodé par [[hatom-fr|hAtom]]).
*# Validation des tests hCalendar. Les tests de hCalendar ont été rendus disponibles depuis un moment, mais seu Brian Suda et moi avons produit des contributios à leurs contenus. Est-ce que quelqu'un d'autre saurait des idées et devrions-nous essyar de faire que ces idées-là et devrions-nous essyer de les produire pour produire des tests 'officiels' de tests [[hcalendar-fr|hCalendar]] ?
*#* ACCEPTATION PARTIELLE. Nous avons probablement d'un ''validateur'' hCalendar avant que nous ne déclarions quelque collection de tests pour que ce soit officiel.
*# L'utilisation de fragments n'est pas claire. L'interprétation de fragments semble être dépendante de l'agent. Les fragments annoncent généralement un titre ou une balise, comme une déclaration goto pour HTML. Malheureusement, cela peut sauter au milieu des éléments (plutôt que vers le début d'un élément). Comment cela devrait-il être géré. par ex :
<pre>
<a name="myfrag">Titre</a>
<div class="vevent">
<div class="description">Un bel événement</div>
<abbr class="dtstart" title="2005-10-05">5 octobre</abbr>
</div>
</pre>
*#* ACCEPTEE. Nous devrions clarifier aux convertisseurs comment interpréter un fragment id. Les interprétations sont toutes cohérentes. Cela pointe vers l'élément qui doit être converti. Si cet élément est vide alors ainsi se fait la conversion. Il n'y a pas de problématique ici autre qu'un besoin pour plus de documentation.
* 2006-02-01 soulevée par [[RyanKing]]
*# ''Problématique 1 : Du fait que maintenant, ou plus tard nous aurons hAtom, devrions-nous ne plus permettre vJournal, afin que nous n'ayons pas deux formats de billets de blogs ?''
*#* ACCEPTEE. Oui, nous devrions explicitement ABANDONNER "vjournal" venant de [[hcalendar-fr|hCalendar]].
* 2006-01-04 soulevée par [[User:CGranade|CGranade]]
*# ''Les interactions avec de solide espace-nom. A ce stade il semble que hCalendar ne puisse pas être embarqué dans des schémas non-XHTML qui sont aussi solidement sous espaces-noms (par ex. : RDF, Atom) sans une erreur résultante de validation, parce que l'attribut <code>class</code> n'est ''pas'' portable à travers les schémas.''
*#* REJETEE. L'attribut class est utilisé sur les éléments XHTML, qui sont XML, qui peuvent être embarqués dans tout autre XML. La problématique telle que posée ne fait pas de sens.
*# ''Tous les exemples en XHTML. XHTML ne devrait pas être l'unique hébergeur vers les microformats, et de ce fait il ne devait pas être l'unique exemple de langage hôte. A la place de cela, des exemples dans Atom, RSS, RDF, etc. devraient être aussi fournis.''
*#* ACCEPTEE. Ceci est définitivement quelque chose à ajouter aux *-pages d'exemples pour chaque microformat.
* 2005-10-14 soulevée par [[User:MarkoMrdjenovic|MarkoMrdjenovic]]
*# ''UID has to be present in iCal events if they want to be used in Microsoft Outlook. [Suggestion:] it should probably be added to the vevent tag as html attribute id. There is also the problem of converters - x2v has UID commented out. [http://www.ietf.org/rfc/rfc2445.txt RFC] recommends use of addr format for uids which is problematic in html id (does not validate). [[User:HenriBergius|HenriBergius]] pointed out some calendaring software crashes when @ is in the UID, so some other form of identification should be used - along the lines of dtstart-dtend-hash(title,summary)-sample-org''
*#* ACCEPTEE-PARTIELLEMENT. Yes, it appears RFC2445 requires UID. However, typical mentions of events by web authors do not provide anything equivalent to a UID, nor should we require authors to do so. Thus we must come up with an algorithm for implied UID, similar to some of the other properties. We REJECT the use of the html 'id' attributre as a substitute for UID as they are of different scopes and thus such a translation will likely be problematic. As part of this algorithm, we MUST disallow "@" signs since the issue points out that such UIDs crash some calendaring software.
*# ''DTSTAMP also has to be present in iCal event for Microsoft Outlook. I think DTSTAMP should be user visible information so implementation with class="dtstamp" is fine. x2v already supports it so it should just be added to the standard and examples. The converters might also think of a way to force (create) dtstamp if it's not present.''
*#* ACCEPTEE. We should come up with a way to encourage/synthesize/imply DTSTAMP property values.
*# ''Here is an example from Midgard CMS (which will be easy to change according to bergie on irc):''
*#* For more discussion of this, please see [http://microformats.org/wiki/hcalendar-brainstorming#UID_handling hCalendar brainstorming: UID handling]
<pre><nowiki>
<li class="vevent" id="2678c3f94af4a49f9ccbb69b92a82aba-midgardGuid">
<abbr class="dtstart" title="2005-10-20T14:34:45Z">Torstai 20. Lokakuu 17:34</abbr> -
<abbr class="dtend" title="2005-10-20T15:33:56Z">18:33</abbr>
<a class="url" href="/bergie/another-calendar/82457028ba83407451edd8aaeaa40622.html">
<span class="summary">From the other cal</span>
</a>
<abbr class="dtstamp" title="2005-10-14T12:16:45Z">Torstai 14. Lokakuu 12:16</abbr>
</li></nowiki></pre>
* 2005-09-29 soulevée par RyanKing
*# ''How does one use ATTENDEE?''
*#* ACCEPTEE. Another [[to-do]] for Tantek - document how to use ATTENDEE with [[hcard|hCard]].
* 2005-07-27 raised by Paolo Massa
*# ''I tried to add a hcalendar event in my blog but it rendered orribly. The problem was I already have a 'class="summary' in my normal HTML (it is the title of the posts) and my CSS displays it bigger and bold. In this way the summary of the event was as big as the titles of the posts, destroying readability. The problem is Overloading of class attributes, it might be the case that a blogger already use, for example, class="summary" for different purposes. What can be a solution? Providing in every microformat wiki page a CSS file that users can download and insert in their blog as additional CSS. This CSS file will "shield" attribute "inside" microformats from being interpreted as "normal" attributes. For example for the hCalendar microformats the relative CSS could be something like:

.vevent .summary {

//remove all the previously set properties, for example:

text-decoration: none;

font-size: 100%;

...

}

Since the hCalendar microformat is the following,

<span class="vevent">

<a class="url" href="http://www.web2con.com/">

<span class="summary">Web 2.0 Conference</span>:

...

I hope to have been clear but I'm not so sure ;-)''

* 2005-07-21 soulevée par Neil Jensen
*# ''should we create a vfreebusy class for HTML representations of freebusy data? Discussion [http://microformats.org/wiki/hcalendar-brainstorming#Free.2FBusy_information on hCalendar brainstorming]. Additional background: [http://www.ifreebusy.com/cyclical/blog/calendar/3.html here].''

* 2005-07-11 soulevée par Kragen
*# ''La spécification class="url" telle que <a href="..."> devrait être un "should", et non un "must". D'autres moyens de référencer l'URL event, comme <iframe src="..."> et <embed src="...">, devraient être mentionnées. A ce jour X2V ne semble pas les gérer. Ceci provient d'une discussion à propos de [[xfolk-fr|xFolk]].''
*#* REJETEE. Manque de cas d'utilisation. Nous ne devrions pas ajouter de "moyens supplémentaires de référencer l'URL event" à moins que vous ne puissiez présenter un exemple concret du vrai monde sur le web qui l'exige.

* 2005-06-21 soulevée par Hixie
*# ''Issue H-1 : Cette spécification manque d'une section agent utilisateur. Il n'y a basiquement rien qui dise comment les hCalendars doivent être parsés, comment gérer les erreurs et ainsi de suite. Elle est définie en termes de DOM ? Est-elle définie en termes de sérialisation ? Comment gérer le contenu inattendu ou le contenu manquant ?
*#* ACCEPTEE. Another [[to-do]] for Tantek, write-up [[hcalendar-parsing-fr]] that documents precisely how user agents are to parse [[hcalendar-fr|hCalendar]] markup.

* 2005-02-22 soulevée par Matt Raymond [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003124.html sur la liste whatwg]:
*# Il n'y pas de déclaration de copyright et pas de déclaration de brevets.''
*#* ACCEPTEE. J'ai mis à jour [[hcalendar-fr|hCalendar]] (et [[hcard-fr|hCard]], et tous les autres microformats) avec une déclaration de copyright standard et une déclarationd e brevet.

* 2005-02-18 soulevée par Matt Raymond [http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/2005-February/003116.html on the whatwg list]:
*# Il n'y a pas moyen pour quelqu'un de lire le marquage pour dire si un nom de classe est le nom d'un attribut ou simplement le nom d'une classe utilisée pour la mise en forme.''
*#* REJETEE (strawman, hypohtèse pauvre). Il n'y a pas besoin de différencier dans le cas général. Dans le cas spécifique, un vocabulaire est défini à l'intérieur d'un contexte.
*# ''As a result of the above, user agents would not be able to reliably allow users to access extension properties such as "x-mozilla-alarm-default-length" (which is an actual extension used in Sunbird).''
*#* REJETEE (hors du sujet). Les propriétés extension sont en dehors du champ actuel de hCalendar.
*# ''L'utilisation de <abbr> pour les dates est incorrect. "August 5th, 2004" n'est pas l'abréviation de 2004-09-05. En fait, le contraire est plus proche de la vérité.''
*#* REJETEE (déclaration fausse). Ceci est simplement une déclaration fausse. Voir cet article pour une explication de cet usage d'<abbr> : [http://tantek.com/log/2005/01.html#d26t0100 Human vs. ISO8601 dates problem solved]
*# ''Vous devez créer un ensemble complexe de règles pour toutes les utilisations possibles d'un marquage légal dans <span class="vcalendar"> qui puisse être facilement implémenté incorrectement.''
*#* REJETE (déclarations fausses, strawman). Pas de marquage légal. Pas besoin de créer des règles pour toutes les utilisations possibles de marquage légal. pas besoin de créer un ensemble de règles complexes.
*# ''Il existe des problématiques de stylisation et de tooltip qui restent non résolues.''
*#* REJETEE (déclarations vides). Voir [[hcalendar-faq-fr|hCalendar FAQ]] pour les réponses aux questions concernant la stylisation et les tooltips. Autrement, soulevez svp des problématiques spécifiques avec des exemples valides et clairs.
*# ''hCalendar/hCard est plus compliqué pour les webmestres à lire et comprendre et plus compliqué pour les développeurs à mettre en place.''
*#* REJETEE (déclarations invalides, comparateur invalide). Please state specific examples which show the perceived complexity. The comparison "more complicated" requires two items, no second item was provided.
*# ''I dislike the entire system of using class names as markup. Class names should be reserved for user-defined semantics.''
*#* ACCEPTEE-PARTIELLEMENT. When specific elements are available, they should be used instead of class names, but even then class names work well to "subclass" specific elements. This is thoroughly discussed in the essay [http://tantek.com/log/2002/12.html#L20021216 A Touch of Class]. And yes, class names can and should be used for user-defined semantics. [[hcalendar-fr|hCalendar]] is one such user, and it is reasonable for users to use each others class names.
*#* ''Would it be more in the spirit of HTML to define these classes in a [http://www.w3.org/TR/html401/struct/global.html#h-7.4.4.3 metadata profile], so that "User agents may... perform some activity based on known conventions for that profile"? Should this be a part of [[microformats-fr|microformats]] specifications in general? (If not, why not?)''
*#** ACCEPTEE. Yes, all [[microformats-fr|microformats]] that introduce new classnames SHOULD include an [http://gmpg.org/xmdp/ XMDP] profile (which itself is a microformat for defining HTML metadata profiles) that defines those classnames.
*#*** ''Ok, but in order to refer to a profile, it needs a URI. Tantek writes in [http://microformats.org/discuss/mail/microformats-discuss/2005-July/000407.html a message of Jul 21] "This is precisely the reason that GMPG was founded and created, to provide permanent URLs/homes for microformat profiles." How does one cause GMPG to issue a profile URL?''
*#**** ACCEPTEE. voir [[profile-uris]] ; ceci est une migration à partir de la liste [[to-do]] de Tantek, pour que les deux puissent fournir des probils d 'auteurs amateurs et d'URLs (probablement sur gmpg.org) pour ces profils sur hCalenar.
* {{OpenIssue-fr}} 2006-04-10 raised by [[User:ScottReynen|Scott Reynen]].
*# ''Quand quelqu'un cherche des pages [[hcalendar-fr|hCalendar]], on ne voit pas de collection de publication du vrai monde de données événements ni de discussion des propriétés implicites par de tels exemples, je pense que c'est bien plus facile d'inférer que les microformats proviennent d'autres formats plus que des comportements véritables. Il n'y a rien dans le [[process-fr|processus]] ni dans les pages hCalendar expliquant ce décalage. J'argumenterais qu'il devrait y avoir une explication, probablement dans les deux lieux.''
* {{OpenIssue-fr}} 2006-04-13 soulevée par Tantek
*# ''Besoin d'ajouter une section sur "Exceptions de Propriétés" comme dans [[hcard-fr|hCard]] pour documenter comment publier / gérer la propriété '''METHOD''' et potentiellement d'autres. Par ex, généralement les auteurs peuvent omettre la propriété METHOD, néanmoins les convertisseurs dont la fonction est de convertir [[hcalendar-fr|hCalendar]] vers iCalendar pour la consommation / abonnnement par un agrégateur de calendrier, devrait probablement insérer un '''METHOD:PUBLISH''' par défaut sur l'objet '''VCALENDAR''' dans le flux résultant .ics.''

== Gabarit ==

Utilisez svp ce format :
* <nowiki>{{OpenIssue-fr}}</nowiki> AAAA-MM-JJ soulevée par NOMAUTEUR
*# ''Problématique 1 : Voici la première problématique que j'ai .''
*# ''Problématique 2 : Voici la seconde problématique que j'ai .''

== Pages en rapport ==
{{hcalendar-related-pages-fr}}

posh

2009-01-08T20:05:32Z

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

<div style="float:right;margin-left:1em">__TOC__</div>
<h1>Plain Old Semantic HTML (POSH)</h1>

Welcome to the <abbr title="Plain Old Semantic HTML">POSH</abbr> home page.

== Origins ==
The acronym '''POSH''' was coined [http://rbach.priv.at/Microformats-IRC/2007-04-06#T091456 on 6 April 2007] on the microformats IRC channel, by <kwijibo> as a shorthand abbreviation for "plain old semantic HTML". A discussion on among John Allsopp, Tantek Çelik, Jeremy Keith, and Chris Messina at the [[events/2007-04-18-web-2-expo-dinner|Microformats Dinner 2007 April 18 following Web 2.0 Expo]] reraised the idea of POSH and the importance of promoting the broader goal of POSH, which microformats are built from and are a proper subset of. For more see [[posh#History|History]].

== Why ==
The term [[semantic-html]] is a mouthful, and belies both how simple it is, how well established it is among modern web designers, and the fact that it has benefits far beyond the obvious doing the right thing for the Web by using semantic markup. We need a simple short mnemonic term that captures the essence of the concept, and is easily verbed (to posh, poshify, poshed up).

== What ==
POSH encapsulates the best practices of using [[semantic-html|semantic HTML]] to author web pages. Semantic HTML is the subset of HTML 4.01 (or XHTML 1.0) elements and attributes that are ''[[semantic]]'' rather than ''[[presentational]]''. The best way to learn and understand POSH is to do it. Pick a page on your web site to begin with, and apply the [[posh#The_POSH_Process|POSH Checklist]] to it. Continue with the [[posh#The_POSH_Process|POSH Process]]. Read [[posh#Resources|POSH Resources]] to learn more about POSH.

== The POSH Process ==
What can you do to be POSH and to make your websites POSH?

# Publish POSH content. Read POSH [[posh#Resources|resources]] and make sure your website publishes valid [[semantic-html|semantic (X)HTML]], and uses [[semantic-class-names]] accordingly.
# Spread POSH. Encourage others to be POSH and POSHify their websites by linking to this page.
# Improve POSH. Help us gather resources to enable more people to easily POSHify their websites.

== The POSH Checklist ==
* The first rule of POSH is that you must [http://validator.w3.org validate] your POSH.
* Second, drop the use of TABLEs for purely presentational purposes, spacer GIFs, and [[presentational-html]] in general.
* Next, fix your [http://tantek.com/log/2002/10.html#L20021022t1432 '''B'''ed and '''BR'''eakfast] markup.
* Eliminate [http://tantek.com/log/2002/11.html#L20021128t1352 Anorexic Anchors].
* Use good [[semantic-class-names]].
* ...

== poshformats ==
The term "poshformats" distinguishes one-off, ad-hoc or more informal class-name based formats efforts from the more formally researched and documented microformats. Another way of describing the distinction is that microformats are the proper subset of poshformats which have been developed via the microformats [[process]] and [[principles]], rather than made-up a-priori.

See [[poshformats]] for more.

== Resources ==
=== POSH Tutorials ===
Step by step tutorials to create POSH content or upgrade existing content to POSH.

* [http://westciv.com/style_master/house/tutorials/quick/validation/index.html Validating your css and html] A simple step by step guide to how and why you should validate your markup
* ...

=== POSH Bookmarks ===
* Check out the Ma.gnolia [http://ma.gnolia.com/groups/posh POSH Group]
* See pages tagged both [http://del.icio.us/tag/posh+microformats POSH and microformats] on del.icio.us.

=== POSH Presentations ===
Presentations which explain and advocate concepts and techniques for utilizing semantic HTML. If/when this section gets too big, we can move it to [[posh-presentations]].
* [http://tantek.com/presentations/2003SXSW/stylesheets.html CSS: Between the Style Sheets by Tantek Çelik (2003-03)], specifically, see slides 3-4,6 starting with "Leaving the [http://tantek.com/log/2002/10.html#L20021022t1432 <B>ed & <BR>eakfast]", and slide 9 "CSS & the Semantic Spectrum" which provides an overview of the semantic spectrum of (X)HTML tags.
* [http://www.tantek.com/presentations/2004etech/realworldsemanticspres.html real world semantics] (2004-02-11)
* [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]).
* ...
* See also more microformats [[presentations]] in general.

=== POSH Books ===
Modern web design books which document good semantic HTML practices.
* <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, <strong>Third Edition</strong>]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">Jennifer</span> <span class="additional-name">Niederst</span> <span class="family-name">Robbins</span></span> See [http://jenville.com/ Jenville].</span>
* <cite>[http://microformatique.com/book/ Microformats empowering your markup for Web 2.0]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">John</span> <span class="family-name">Allsopp</span>.</span></span> Chapter 3 is a detailed and practical overview of the appropriate use of structural, valid and semantic HTML.
* <cite>[http://htmlmastery.com/ http://htmlmastery.com/images/hm-cover-sm.gif][http://htmlmastery.com/ Semantics, Standards and Styling]</cite> by <span class="vcard"><span class="url fn n"><span class="given-name">Paul</span> <span class="family-name">Haine</span>.</span></span>
* <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> by <span class="vcard"><span class="url fn n"><span class="given-name">Ian</span> <span class="family-name">Lloyd</span>.</span></span>

=== POSH Magazines ===
Online (and off) magazines which frequently publish articles about semantic HTML. If/when this section gets too big, we can move it to [[posh-magazines]].

* [http://alistapart.com/ A List Apart: For People Making Websites] (see in particular [http://www.alistapart.com/topics/code/htmlxhtml/ HTML and XHTML Articles])
* [http://www.digital-web.com/ Digital Web Magazine]

=== POSH Blogs ===
Blogs that with some regularity post high quality discussions, insights, and in general have advanced the state of the art of POSH. If/when this section gets too big, we can move it to [[posh-blogs]].

* [http://dbaron.org/log/current David Baron's weblog]
* [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] (see in particular [http://simplebits.com/bits/simplequiz/ SimpleQuiz])
* [http://tantek.com/ Tantek Çelik]
* ...

=== POSH Blog posts ===
Blog posts that provide specific, modern, guidance, techniques and tips for using more and better semantic HTML. This list is ''incomplete''. We know there are lots more blog posts out there that fit the aforementioned description - please add them! If/when this section gets too big, we can move it to [[posh-blog-posts]].

* [http://www.456bereastreet.com/archive/200711/posh_plain_old_semantic_html/ POSH - Plain Old Semantic HTML] by Roger Johansson.
* [http://www.plaintxt.org/wp-content/uploads/sandbox-v09_readme.html The Sandbox theme for WordPress readme.html] discusses what POSH is and how the theme helps users use it.
* [http://tantek.com/log/2002/10.html#L20021022t1432 Bed and BReakfast markup (B&BR)] (2002-10-22) - avoiding nonsemantic uses of <nowiki><b>old and <br>eak</nowiki> tags and using <nowiki><h3>adings and <p>aragraphs</nowiki> instead.
* [http://tantek.com/log/2002/11.html#L20021128t1352 <nowiki><A>norexic </A>nchors</nowiki>] (2002-11-28) - use the "id" attribute on existing elements instead of adding empty <code><nowiki><a name="foo"></a></nowiki></code> elements. Use [[rel-bookmark]] for post permalinks within the document.
* [http://tantek.com/log/2002/12.html#L20021216t2238 A Touch of Class] (2002-12-16) - introduction to proper use of the HTML 'class' attribute.
* [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) - how to markup a list of comments, including example use of the rare "hreflang" attribute.
* [http://meyerweb.com/eric/thoughts/2004/07/18/competent-classing Competent Classing by 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 by Jesse Skinner] (2006-02-22)
* [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] by 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] A list of the semantic elements and attributes of HTML by 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://factoryjoe.com/blog/2007/04/21/getting-back-to-posh-plain-ol-semantic-html/ Getting back to POSH (Plain ol’ Semantic HTML)] by Chris Messina (2007-04-21)
* [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)
* [http://nate.koechley.com/blog/2006/12/15/divitis_and_correct_div_usage/ On Appropriate Use of DIVs, or When Divitis Doesn’t Apply] by 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 by Richard Leland (2006-07-31)
* [http://nascentguruism.com/journal/perfection/ Perfection] - by Steve Marshall (2007-11-02)
* ...

See [http://technorati.com/search/%22semantic%20HTML%22 more blogs talking about "semantic HTML"] and [http://technorati.com/search/posh+semantic+HTML POSH].

===POSH Podcasts===
If/when this section gets too big, we can move it to [[posh-podcasts]].
* 2007-05-03: [http://www.netmag.co.uk/podcasts/07-05-03-net.mp3 A talk about POSH] in the .Net magazine podcast episode 8 (56 minutes; 26 Mb. Relevant section 30:10-42:40)
* 2005-09-29: [http://microformats.org/media/2005/09/we05-2-tantek-celik.mp3 The Elements of Meaningful XHTML] - podcast of Tantek's presentation by the same name ([http://tantek.com/presentations/2005/09/elements-of-xhtml/ slides])

=== Hidden POSH Treasures ===
The following sites have POSH related articles, tutorials etc. on them, but you have to dig for them from the home page. Help find the hidden POSH treasures in these sites and add ''direct'' links to POSH related articles, tutorials etc. to the specific sections above. You can leave the top level site links here until/unless you have dug thru the entire site and found all the treasures.
* [http://www.w3schools.com/ W3Schools Online Web Tutorials]
* [http://dev.opera.com/ Dev.Opera]

=== POSH Bling for your Blog ===
If you want to improve your existing blog, there are some pretty simple things you can do:

==== WordPress ====
* Use the [http://www.plaintxt.org/themes/sandbox/ Sandbox] or [http://getk2.com K2] themes that already support hAtom and hCard
* Add the [http://redmonk.net/archives/2007/04/18/wordpress-widget-hcard-about-box/ hCard About Widget] to your site

== Spread POSH ==
Now that you've poshified your website(s), what next? Well, help spread POSH to other websites!

* Promote POSH. Make a POSH button (perhaps using semantic HTML and CSS ;) linking to this page and put it on your site, in your blogroll, in your footer, etc. Maybe even come up with a nice POSH button graphic and share it with the microformats community with a liberal license (public domain, CC-by-3.0, MIT, etc.) Like these:
** [http://redmonk.net/archives/2007/04/25/the-new-question/ http://redmonk.net/wp-content/uploads/2007/04/are_you_posh.png] - [http://creativecommons.org/licenses/by/3.0/ CC-by-3.0]
** [http://redmonk.net/archives/2007/04/26/chic/ http://redmonk.net/wp-content/uploads/2007/04/chic_fancy.png] - [http://creativecommons.org/licenses/by/3.0/ CC-by-3.0]
** [http://www.hauntedpalace.net/pandora/craic/poshscribbles.png http://www.hauntedpalace.net/pandora/craic/poshscribbles.png] — [http://creativecommons.org/licenses/by/3.0/ CC-by-3.0]
** [http://www.hauntedpalace.net/pandora/craic/poshChopin.png http://www.hauntedpalace.net/pandora/craic/poshChopin.png] — [http://creativecommons.org/licenses/by/3.0/ CC-by-3.0]
* Tell a friend. Talk to web design friends about POSH and convince and help them to poshify both their personal websites, and the websites they build for others. Blog about your experience with poshification and what steps you went through to poshify your websites. Write a [[posh-testimonial]]!
* Come up with more ideas to help spread POSH. Here are a few.
** Hold a PoshPit - a one or half day marathon session mixing semantic HTML experts with folks who maintain/run web sites in general and see how many websites you can collectively upgrade to POSH during the course of the day.
** ...

== Improve POSH ==
As you read the [[posh#Resources|POSH resources]] documented here, what other POSH resources did you find? Add them to this page.

With your experience with both poshifying your sites and helping others do so, what have you learned? What kind of [[posh-issues|issues]] did you run into? What questions were commonly asked? What do you feel like you need to more easily and quickly help more people poshify their content?

== History ==
A brief history of references to "POSH" in this context and "plain old semantic HTML".

=== plain old semantic HTML ===
The earliest references to <strong>"plain old semantic HTML"</strong> that have been found so far are:
* [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 <strong>plain old semantic HTML</strong>. "
* [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 <strong>plain old semantic HTML</strong> to mark up your content in all other cases." (retrieved by [[User:Tantek|Tantek]] 08:20, 20 Apr 2007 (PDT))
If you can find earlier references, please ''add'' them and include a brief quotation of the context of the reference to "plain old semantic HTML".

xfolk-fr

2009-01-08T20:05:19Z

RyanKing: Reverted edits by AceloLotre (Talk) to last version by RaccgEtroc

trcnanoc4
<h1> xFolk (RC1) </h1>

'''xFolk''' est un format simple et ouvert pour publier des collections de signets. Il permet aux services de mieux amÃ©liorer l'expÃ©rience utilisateur et de partager des donnÃ©es dans un logiciel de signet basÃ© sur le web. xFolk peut Ãªtre embarquÃ© dans (X)HTML, Atom, RSS et du XML arbitraire. C'est l'un des nombreux [[microformats-fr|microformats]] standards ouverts.

__TOC__

== SpÃ©cification Brouillon ==

=== Editeur/Auteur ===
[http://thecommunityengine.com/ Bud Gibson], [http://thecommunityengine.com The Community Engine]

(traduction [[Christophe Ducamp]])

=== Copyright ===
{{MicroFormatCopyrightStatement2005-fr}}

=== Brevets ===
{{MicroFormatPatentStatement-fr}}

=== Inspiration et Reconnaissances ===
Merci Ã : [http://www.cnbc.cmu.edu/~plaut/ David Plaut] qui m'a prÃ©sentÃ© l'idÃ©e que les items peuvent appartenir partiellement Ã beaucoup de catÃ©gories en une fois. Plus rÃ©cemment, merci Ã : [http://tantek.com/ Tantek Ãelik], [http://epeus.blogspot.com/ Kevin Marks], [http://steve.osdir.com/ Steve Mallet], [http://hybernaut.com/ Brian DelVecchio] et [http://blogmarks.net FranÃ§ois Hodierne] qui ont contribuÃ© au dÃ©veloppement de xFolk avec des critiques sensÃ©es et des implÃ©mentations.

== Introduction ==
Les services de signets sociaux laissent les utilisateurs sauvegarder et taguer leurs signets pour les partager avec d'autres utilisateurs. Durant la derniÃ¨re annÃ©e, le nombre de ces services a poussÃ© comme des champignons (plus de [http://en.wikipedia.org/wiki/Social_bookmarking 20], avec des exemples comprenant : [http://del.icio.us del.icio.us], [http://furl.net furl], [http://de.lirio.us de.lirio.us], [http://jots.com jots] et [http://blogmarks.net blogmarks].

Le manque d'un standard ouvert et interopÃ©rable de donnÃ©es est une problÃ©matique majeure Ã utiliser les services de signets sociaux. Un standard ouvert ferait qu'il soit possible de collecter facilement des donnÃ©es signets et de les remixer pour inventer de nouveaux services le long de la ligne du moteur expÃ©rimental de recherche de signets [http://gataga.com gataga]. Un standard ouvert ferait qu'il serait aussi possible d'Ã©crire des javascripts qui fonctionnent transversalement sur les services [http://johnvey.com/features/deliciousdirector/ comme le font certains actuellement pour del.icio.us], permettant des amÃ©liorations en expÃ©rience utilisateur.

xFolk est un standard ouvert de signet social qui a pour but de parvenir Ã tous ces avantages. Les services de signets sociaux qui adoptent xFolk continueront Ã se diffÃ©rencier eux-mÃªmes des services de donnÃ©es. Mais, la donnÃ©e elle-mÃªme sera facile Ã manipuler par des scripts tiers et sera facile Ã partager. En tant que rÃ©sultat, les services de signets pourront offrir Ã leurs utilisateurs un ensemble plus large d'options Ã un moindre coÃ»t et se concentrer sur ce qui les diffÃ©rencie vraiment. Les individus ou les groupes opÃ©rant seul des rÃ©pertoires de signets auront accÃ¨s Ã un plus large ensemble de fonctionnalitÃ©s que celles qu'ils pourraient produire seuls.

== Principes de Design XHTML SÃ©mantique ==
{{semantic-xhtml-design-principles-fr}}

== Format ==
Une analyse extensive des services de signets sociaux et des linkblogs, dÃ©posÃ©e [http://thecommunityengine.com/home/archives/xfolk ailleurs], rÃ©vÃ¨le que les donnÃ©es publiÃ©es par tous les services de signets et '''beaucoup''' de linkblogs diffÃ©rents sont dÃ©crites par le schÃ©ma implicite suivant :

* Un lien bookmarkÃ© ou taguÃ©.
* Un titre pour l'entrÃ©e.
* Les tags pour le lien.
* Une description Ã©tendue ou un rÃ©sumÃ© du lien.

Comme dÃ©montrÃ© dans les premiÃ¨res itÃ©rations du standard xFolk, ce schÃ©ma gÃ©nÃ©ral peut Ãªtre traduit en balisage par :
# crÃ©er un Ã©lÃ©ment conteneur pour chaque entrÃ©e de la classe <code>xfolkentry</code>,
# utiliser un Ã©lÃ©ment <a> pour le lien bookmarkÃ© ou taguÃ© de la classe <code>taggedlink</code>,
# utiliser l'attribut title pour l'Ã©lÃ©ment lien taguÃ© <a>, s'il existe, comme l'entrÃ©e title, autrement utiliser la valeur de l'Ã©lÃ©ment,
# utiliser [[rel-tag-fr|RelTag]] pour les tags, et
# utiliser un Ã©lÃ©ment conteneur de classe <code>description</code>, tel que <p>, pour toute autre description Ã©tendue ou rÃ©sumÃ©.

Une entrÃ©e donnÃ©e xFolk contiendra toujours un lien taguÃ© comprenant un 'title' avec d'autres Ã©lÃ©ments optionnels. Les entrÃ©es peuvent avoir plus d'un tag tout comme plus d'un Ã©lÃ©ment de classe <code>description</code>. Plusieurs Ã©lÃ©ments de classe <code>description</code> sont triÃ©s par l'ordre du document par dÃ©faut. Les Ã©lÃ©ments sÃ©mantiques dans les entrÃ©es xFolk peuvent Ãªtre imbriquÃ©s Ã des profondeurs abritraires.

Beaucoup de systÃ¨mes de signets sociaux existent, chacun d'eux avec se propres conventions de balisage. En outre, beaucoup de personnes publient dÃ©jÃ des blogs de liens. xFolk est conÃ§u en prioritÃ© pour faciliter l'adoption de ces pratiques actuelles. Par consÃ©quent, peu d'hypothÃ¨ses ont Ã©tÃ© produites comme les types exacts des Ã©lÃ©ments utilisÃ©s pour une entrÃ©e xFolk. Le travail de dÃ©finir la sÃ©mantique est entiÃ¨rement laissÃ© Ã la casse et aux valeurs d'attribut rel (dans le cas de [[rel-tag-fr|reltag]]).

Il est attendu que les dÃ©veloppeurs utiliseront [http://www.w3.org/TR/xpath XPath] ou une syntaxe Ã©quivalente en accÃ©dant Ã des Ã©lÃ©ments d'entrÃ©e xFolk. Une exigence pour xPath est que le document (X)HTML soit bien formÃ© mais pas nÃ©cessairement valide. Par consÃ©quent, bien que non dÃ©sirable, il est possible d'utiliser xFolk dans un document (X)HTML qui ne valide pas.

=== XMDP Profile ===

Voir le [[xfolk-profile-fr|xFolk profile]] pour le profil [http://gmpg.org/xmdp XMDP] de xFolk.

== Exemple ==
VoilÃ un signet Ã©chantillon comme affichÃ© dans la syntaxe standard de [http://del.icio.us del.icio.us]. Les lignes oÃ¹ les attributs de classe d'Ã©lÃ©ments doivent changer pour se conformer Ã xFolk sont marquÃ©es avec un commentaire Ã la fin.
<pre><div class="post"> 
<div>
<a class="delLink" href="http://www.sifry.com/alerts/archives/000306.html"> 
Sifry's Alerts: Technorati launches Related Tags
</a>
</div>
<div class="extended"> 
Ever wanted to see what posts are related to other posts, what tags
are related to others? Now you can! Just check under the Tag
description on most tag pages, like this one, or this one, and you'll
see the patterns. Can you smell the emergence?
</div>
<div class="meta">
to
<a class="delNav" href="/fpgibson/folksonomy">folksonomy</a> 
<a class="delNav" href="/fpgibson/technorati">technorati</a> 
... <a class="delNav" href="/url/cbcabf7de070fdb46598ee679367be49">
and 1 other person
</a>
... on 2005-04-09
</div>
</div></pre>

L'Ã©quivalent dans xFolk se fait comme suit. Les commentaires sont placÃ©s Ã la fin des lines oÃ¹ les modifiations d'attribut de classe sont requises
<pre><nowiki>
<div class="xfolkentry"> 
<div>
<a class="taggedlink" href="http://www.sifry.com/alerts/archives/000306.html"> 
Sifry's Alerts: Technorati launches Related Tags
</a>
</div>
<div class="description"> 
Ever wanted to see what posts are related to other posts, what tags
are related to others? Now you can! Just check under the Tag
description on most tag pages, like this one, or this one, and you'll
see the patterns. Can you smell the emergence?
</div>
<div class="meta">
to
<a rel="tag" href="/fpgibson/folksonomy">folksonomy</a> 
<a rel="tag" href="/fpgibson/technorati">technorati</a> 
... <a class="delNav" href="/url/cbcabf7de070fdb46598ee679367be49">
and 1 other person
</a>
... on 2005-04-09
</div>
</div>
</nowiki></pre>

Un autre exemple simple, basÃ© sur un balisage de listes non-ordonnÃ©es :
<pre>
<nowiki>
<ul>
<li>
<ul class="xfolkentry">
<li><a class="taggedlink" href="http://microformats.org/wiki/Main_Page-fr">Le wiki du projet microformats</a></li>
<li class="description">Un bon lieu de dÃ©part pour dÃ©couvrir et jouer avec les microformats</li>
<li class="description">Site wiki communautaire</li>
<li class="meta">
Tags :
<a rel="tag" href="http://del.icio.us/tag/microformats">microformats</a>
<a rel="tag" href="http://del.icio.us/tag/websocial">websocial</a>
<a rel="tag" href="http://del.icio.us/tag/semantique">semantique</a>
</li>
</ul>
</li>

<li>

</li>

</ul>
</nowiki>
</pre>

Convertir le balisage pour Ãªtre conforme Ã xFolk est presque toujours aussi facile. L'avantage de xFolk est que cela fournit un ensemble d'attributs de classe qui peuvent Ãªtre rÃ©utilisÃ©s sur tous les services et blogs de liens, presque toujours sans aucune perte de granularitÃ©. La prochaine section prÃ©sentera plusieurs autres exemples pour illustrer ce point.

== Beaucoup plus d'exemples ==

Nous avons de nombreux exemples pour aider les dÃ©veloppeurs Ã incorporer xFolk dans leurs sites.

=== Dans la jungle ===

Ce sont de vrais exemples de systÃ¨mes qui fonctionnent et qui publient les signets dans xFolk. Ceci est une endroit idÃ©al pour commencer Ã regarder des exemples "dans la jungle" pour essayer de parser, indexer, organiser, etc. Si vous publiez en utilisant xFolk, sentez-vous Ã l'aise pour ajouter en haut de cette liste. Une fois que la liste sera trop grosse, nous ferons une page wiki sÃ©parÃ©e.
* [http://waferbaby.com/hussy waferbaby's Hussy] publie actuellement les liens en utilisant xFolk.
* [http://unalog.com unalog] publie actuellement tous les liens partagÃ©s (y compris les rÃ©sultats de recherche) en utilisant xFolk.
* [http://smarking.com/ Smarking] publie actuellement tous les liens partagÃ©s (y compris les rÃ©sultats de recherche) en utilisant xFolk.
* [http://de.lirio.us de.lirio.us] publie actuellement ses signets en utilisant xFolk (avec l'attribut de classe dÃ©prÃ©ciÃ© <code>extended</code> a lieu de <code>description</code>, voir [[xfolk-profile-fr| le XMDP]]).
* [http://dev.blogmarks.net/wiki/BlogSync blogmarks] exporte actuellement les signets vers les blogs en xFolk (dÃ©filez plus bas pour voir l'exemple d'export sur la page ; l'attribut de classe dÃ©prÃ©ciÃ© <code>extended</code> est utilisÃ© au lieu de <code>description</code>, voir [[xfolk-profile-fr| le XMDP]]).
* [http://thecommunityengine.com The Community Engine] utilise xFolk (avec l'attribut de classe dÃ©prÃ©ciÃ© <code>extended</code> utilisÃ© au lieu de <code>description</code>, voir [[xfolk-profile-fr| le XMDP]]) pour ses [http://thecommunityengine.com/home entrÃ©es principales] et pour ses [http://thecommunityengine.com/webcites signets republiÃ©s].
* [http://groovymother.com/links/ Groovy Links] est un blog de liens qui est balisÃ© avec xFolk.

=== Services de signets sociaux supplÃ©mentaires ===

Cet exemple illustre comment xFolk peut Ãªtre appliquÃ© Ã un service additionnel :

* [[xfolk-scuttle-fr| scuttle]]

=== Blogs de liens ===

Les services de signets sociaux sont seulement les exemples les plus rÃ©cents de personnes publiant des liens. Les blogs de liens ont presque toujours existÃ© depuis le dÃ©but du blogging. Ils reprÃ©sentent en quelque sorte plus qu'un dÃ©fi pour xFolk parce que leurs balisages tendent Ã Ãªtre moins sÃ©mantiques qu'au dÃ©but. Les exemples suivants illustrent quelques dÃ©fis particuliers et comment ils peuvent Ãªtre surmontÃ©s.

* [[xfolk-kottke | kottke]]
* [[xfolk-pollas | pollas]]
* [[xfolk-jacobian | jacobian]]
* [[xfolk-julian-bez | julian-bez]]

=== Spam ===
Quelques spammers sont en train d'ajouter des tags xFolk Ã leurs fermes Ã liens. (C'est probablement une mauvaise idÃ©e de lier vers ces sites). Par exemple :
* phontron.info

== ImplÃ©mentations ==

Les implÃ©mentations suivantes ont Ã©tÃ© dÃ©veloppÃ©es et elles gÃ©nÃ¨rent ou utilisent xFolk. Si vous avez une implÃ©mentation xFolk, sentez-vous Ã l'aise pour l'ajouter en haut de cette liste. Une fois que la liste sera trop grosse, nous ferons une page wiki sÃ©parÃ©e.
* [http://buzka.com Buzka], un service de signet social supporte maintenant xFolk
* [http://blip.tv Blip.tv], un site d'hÃ©bergement vidÃ©o [http://blog.blip.tv/blog/2006/08/19/blip-supports-xfolk/ supporte maintenant xFolk].
* [http://www.s9y.org/ Serendipity], une application de Blogging/CMS motorisÃ©e par PHP a maintenant un [http://www.numblog.de/archives/241-Social-Bookmarks-Plugin-for-Serendipity.html plugin de signets sociaux] qui supporte xFolk.
* [http://claimid.com claimID] a implÃ©mentÃ© xFolk pour les liens vers les personnes.
* [http://ma.gnolia.com ma.gnolia] supporte maintenant xFolk.
* [http://smarking.com/ Smarking.com] (un service de signet social) balise ses liens taguÃ©s avec xFolk ! truc : [http://3spots.blogspot.com/2006/05/social-bookmarking-smarking.html 3spots: Social + bookMARKING = Smarking] qui lui-mÃªme est un [[hreview-fr|hReview]].
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port de l'extension Tails pour Flock 0.5.12 qui cherche les hCards, hCalendar, xFolk et hReview et les porte dans une barre supÃ©rieure Ã portÃ©e de main.
* [http://blog.codeeg.com/tails-firefox-extension/ Tails est une Extension Firefox] qui affiche la prÃ©sence de microformats ([[hcard-fr|hCard]], [[hcalendar-fr|hCalendar]], [[hreview-fr|hReview]], [[xfolk-fr|xFolk]]) sur une page web.
* Bud Gibson et Mike Migurski [http://thecommunityengine.com/home/archives/2005/09/vegomatic_an_al.html ont Ã©crit] [http://thecommunityengine.com/veg-o-matic veg-o-matic], un outil et service xFolk de reblogging.
* [http://inside.glnetworks.de/ Martin Rehfeld] a mis Ã jour le travail de [http://blogmatrix.blogmatrix.com/ David Janes] et produit un [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] [[Greasemonkey-fr|GreaseMonkey]] qui trouve beaucoup d'Ã©lÃ©ments microformats, y compris xFolk et [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 fournit un menu en popup d'actions]. ''Ceci fonctionnera maintenant avec FireFox 1.5+/GreaseMonkey 0.6.4+.''
* [http://www.midgard-project.org/midcom-permalink-6416db7e1f0e297b4cf3dcc285702a8d net.nemein.bookmarks], le gestionnaire de signets dans [http://www.midgard-project.org/ Midgard CMS] utilise xFolk comme le format natif de production, avec un ajout <code>abbr class=posted</code> pour la date de publication et <code>abbr class=poster</code> pour l'utilisateur qui a ajoutÃ© le signet. Vor l'[http://bergie.iki.fi/links/ exemple]
* [http://de.lirio.us de.lirio.us] publie actuellement ses signets en utilisant xFolk 0.4 (l'attribut de classe <code>extended</code> est utilisÃ© au lieu de <code>description</code>).
* [http://dev.blogmarks.net/wiki/BlogSync blogmarks] exporte actuellement les signets vers les blogs en xFolk 0.4 (scrollez vers le bas pour voir l'exemple d'exportation sur la page ; l'attribut de classe <code>extended</code> est utilisÃ© au lieu de <code>description</code>).
* [http://pokkari.com/microformat/javadoc/ Sivitols] est une librairie Java pour les microformats. Actuellement seul le standard xFolk RC1 est implÃ©mentÃ© mais le support microformat additionnel est planifiÃ©. (adaptÃ© Ã partir de [http://blog.blip.tv/blog/microformats/])

== RÃ©fÃ©rences ==
=== RÃ©fÃ©rences Normatives ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [[rel-tag-fr|rel-tag]]

=== RÃ©fÃ©rences Informatives ===
* [http://thecommunityengine.com/home/archives/xfolk articles about xFolk]
* [http://thecommunityengine.com/home/archives/tags/microformats articles about the business value of microformats]
* [http://gataga.com gataga social bookmark search engine]
* [http://johnvey.com/features/deliciousdirector/ an ajax based interface for del.icio.us]
* [http://en.wikipedia.org/wiki/Social_bookmarking social bookmarking defined at wikipedia]

=== Travaux similaires ===
* [[hreview-fr| hReview]]

== Chantier en cours ==
Bien que cette spÃ©cification ait rÃ©cemment commencÃ© Ã se stabiliser comme indiquÃ© par la version RC1, c'est encore un chantier en cours. Si garantie, je suis prÃªt Ã aller vers plusieurs versions candidates pour parvenir Ã l'objectif de produire des entrÃ©es de signets plus gÃ©nÃ©ralement accessibles avec un format aussi lÃ©ger que possible. Tous les changements depuis la derniÃ¨re itÃ©ration ont Ã©tÃ© motivÃ©s par l'expÃ©rience d'implÃ©mentations des dÃ©veloppeurs tentant de parvenir Ã cet objectif. Des changements plus en profondeur seront aussi probablement motivÃ©s par les problÃ¨mes d'implÃ©mentation. Voir "directions futures" ci-dessous pour des possibilitÃ©s supplÃ©metaires de microformat.

=== Changements depuis xFolk 0.4 ===
La valeur de l'attribut de classe <code>extended</code> a Ã©tÃ© dÃ©prÃ©ciÃ©e en faveur de <code>description</code> pour mieux se conformer Ã d'autres usages de microformats et quelques requÃªtes durant l'implÃ©mentation. L'autre changement a Ã©tÃ© de permettre l'utilisation de plusieurs Ã©lÃ©ments de classe <code>extended</code> basÃ©s sur quelque cas d'utilisation dÃ©couverts dans l'implÃ©mentation.

=== Directions futures ===
Il y a plusieurs extenstion qu'on pourrait imaginer pour xFolk. FrÃ©quemment, ces extensions sont mieux abouties en combinant xFolk avec un autre microformat. Par exemple, on pourrait vouloir indiquer son Ã©valuation de l'item mis en signet. Ceci pourrait Ãªtre rÃ©alisÃ© en utilisant [[vote-links-fr| Vote Links]] ou [[hreview-fr | hReview]] avec xFolk.

On peut aussi imaginer d'Ã©tendre xFolk pour fournir des donnÃ©es conformes avec plusieurs APIs de services de signets sociaux, par exemple pour fournir tous les signets par tag. Ces APIs sont actuellement trop fluides pour la spÃ©cification de quelque type de standard. Les APIs et la fonctionnalitÃ© qu'elles fournissent reprÃ©sentent un moyen dont les services de signets sociaux et les mÃ©ta-services peuvent eux-mÃªmes se diffÃ©rencier.

Un format compagnon appelÃ© "xFolk definition" est en dÃ©veloppement. "xFolk definition" fournira un moyen de dÃ©finir explicitement les tags utilisÃ©s dans les signets sociaux.

=== Brainstorming ===
* [[xfolk-brainstorming-fr|xFolk brainstorming]]

== Discussions ==

=== Q&R ===
* Si vous avez quelque question Ã propos d'xFolk, regardez les [[xfolk-faq-fr|FAQ xFolk]], et si vous ne trouvez pas de rÃ©ponses, ajoutez vos questions !

=== ProblÃ©matiques ===
* SVP, ajoutez toute problÃ©matique avec la spÃ©cification au document sÃ©parÃ© [[xfolk-issues-fr| xFolk issues]].

==Pages apparentÃ©es==
{{template:xfolk-related-pages-fr}}

Template:cheatsheets

2009-01-08T20:04:47Z

RyanKing: Reverted edits by BotrrIcsit (Talk) to last version by AndyMabbett

User talk:DanielMorrison

2009-01-08T20:04:39Z

RyanKing: Reverted edits by EltboTadom (Talk) to last version by AndyMabbett

{{welcome}}

:[[User:AndyMabbett|Andy Mabbett]] 00:51, 29 Mar 2007 (PDT)

User:HenrichPoehls

2009-01-08T20:04:30Z

RyanKing: Reverted edits by ZelmoNpase (Talk) to last version by HenrichPoehls

'''Henrich C. Pöhls'''

is doing his PhD in CS at the University of Hamburg[http://www.informatik.uni-hamburg.de/SVS/personnel/henrich/index.php], and is concerned with the security of Semantically Annotated Content.

His idea: Digitally sign microformatted content and store the Digital Signature in a Microformat
([http://www.informatik.uni-hamburg.de/SVS/personnel/henrich/hsig.php hsig]).

hproduct-feedback

2009-01-08T20:04:09Z

RyanKing: Reverted edits by DeldeLnodr (Talk) to last version by RyanKing

'''This should be incorporated into [[product-brainstorming]].'''
----

Why not use DL for name-value pairs? --[[User:Etoastw|Etoastw]] 05:52, 27 Feb 2007 (PST)
Forget it, already in there :)--[[User:Etoastw|Etoastw]] 05:14, 2 Mar 2007 (PST)

==EAN / GTIN==

On UPC and product codes:
The properties 'isbn' and 'upc' are anticipated for p-v keys. They should be extended by other common properties (p.e. 'issn') and at least the EAN, which is now world-wide standard for product codes. isbn and upc are covered by the EAN and can be converted to and from the EAN.

http://www.adams1.com/pub/russadam/isbn.html
http://www.gs1.org/

[[User:Tux|Tux]] 06:16, 31 Aug 2007 (PDT)

*Per [http://en.wikipedia.org/wiki/Global_Trade_Item_Number Wikipedia: Global Trade Item Number]: <blockquote>Global Trade Item Number (GTIN) is an identifier for trade items developed by GS1 (comprising the former EAN International and Uniform Code Council).</blockquote>
:: [[User:AndyMabbett|Andy Mabbett]] 06:41, 31 Aug 2007 (PDT)

hcalendar-implementations

2009-01-08T20:03:59Z

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

<h1>hCalendar Implementations</h1>
{{TOC-right}}
This page is an '''informative''' section of the [[hcalendar|hCalendar specification]].

The following implementations have been developed which either generate or parse hCalendars. If you have an [[hcalendar|hCalendar]] implementation, feel free to add it to the New Implementations section. If you have a page or site which just ''publishes'' hCalendar events, please use [[hcalendar-examples-in-wild]] instead.

==New Implementations==
Add new implementations here:

* [http://www.w3.org/People/Bos/HcalProxy/ Hcalproxy] runs as an HTTP server, either standalone or under inetd(8), and converts hCalendar to iCalendar.
* The calendar of [http://TikiWiki.org TikiWiki CMS/Groupware] uses hCalendar markup for events. It's a built-in feature (no need to download separate module/plugin/etc). You can see in action over at [http://wiki-translation.com wiki-translation.com]
* [http://code.google.com/p/schoorbs Schoorbs] has bookings flavored with hCalendar in view_entry.php since revision 175 (becoming 1.0-Alpha2).
* [http://buzzword.org/cognition/ Cognition] supports [[User:TobyInk/hcalendar-1.1|hcalendar 1.1]]
* ...

==Authoring==
Implementations you can use to author, create, and publish hCalendar events.

===Web-based Creators===
;hCalendar Creator : [http://microformats.org/code/hcalendar/creator hCalendar creator] ([[hcalendar-creator-feedback|hCalendar creator feedback]]) - create your own hCalendar events.
;Conference Schedule Creator : [http://dmitry.baranovskiy.com/work/csc/ Conference Schedule Creator] ([[hcalendar-schedule-creator-feedback|Conference Schedule Creator feedback]]) - create your conference schedule with hCalendar events.
;Permatime hCalendar vevent generator : [http://permatime.com/ Permatime] enables sharing of points in time as well as acting as a quick way to generate hcalendar vevents.

===Blogging and CMS tools===
;Midgard CMS : [http://www.midgard-project.org/documentation/net-nemein-calendar/ Midgard CMS - net.nemein.calendar] - as [http://bergie.iki.fi/blog/new-event-calendar-for-midcom.html blogged by Henri Bergius]

;Drupal module : [http://hybernaut.com/upcoming-hcal Drupal Upcoming.org syndication module emits hCalendar]
;MovableType and WordPress plug-ins : [http://structuredblogging.org/formats.php StructuredBlogging] is a set of plugins [http://structuredblogging.org/structuredblogging-wp-latest.zip for WordPress] and [http://structuredblogging.org/structuredblogging-wp-latest.zip for MovableType] that supports embedding hCalendar and other microformats in templates and blog posts.
;Textpattern plug-ins :
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding hCalendar and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].
* [http://euphemize.net/blog/plugins/textpattern/jmc_event_manager/ jmc_event_manager] is a plugin for [http://textpattern.com/ Textpattern] that outputs events and locations in hCalendar (and hCard) formats. Written by [http://euphemize.net/ Joel Courtney].

===Browser scripts and plug-ins===
Browser plugins that work with existing authoring tools:
; Any browser with javascript and a little bit of CSS : [http://microformats.org/code/hcalendar/creator microformats.org hCalendar creator] (see also original: [http://theryanking.com/ Ryan King] has an [http://theryanking.com/microformats/hcalendar-creator.html hCalendar creator]).
; Firefox Greasemonkey user script hCalendar creator : [http://www.decafbad.com/blog/2005/06/08/greasemonkey_magic magic_hcalendar Greasemonkey user script by Les Orchard] - allows easy form entry of an event into any textarea, e.g. into a blog post text area.
; Firefox Greasemonkey user script hCalendar to Google Calendar: [http://torrez.us Elias Torres] has created a [http://torrez.us/archives/2006/04/13/431/ simple script] that will parse hCalendar entries and create a link to add event to [http://www.google.com/calendar/ Google Calendar's] service. Based on [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats George's] and [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats Arve's] work.

===Desktop Authoring Tools===
;Dreamweaver Extension : [http://www.webstandards.org/action/dwtf/microformats/ Extension suite] for Dreamweaver 8 from the [http://webstandards.org/ Web Standards Project].
;xfy :
In [https://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations.
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=15&lid=25 hCalendar via RSS] parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=19&lid=23 hCalendar Marker XVCD] helps to mark up an event information in XHTML document with hCalendar.
* [https://www.xfytec.com/community/modules/mydownloads/singlefile.php?cid=15&lid=17 Simple RDF Calendar XVCD] is a schedule tool which uses RDF Calendar format. It also converts RDF Calendar format to iCalendar and hCalendar format.
;Windows Live Writer :
* WLW's [http://gallery.live.com/liveItemDetail.aspx?li=9751e563-1408-4fc3-8028-bd4351edb1fb&l=8 Event Plugin] formats events in blog posts with hCalendar.

==Search and Discovery==
* [http://kitchen.technorati.com/search Technorati Microformats Search] indexes [[hcard|hCard]], [[hcalendar|hCalendar]], and [[hreview|hReview]] as [http://tantek.com/log/2006/05.html#d31t1802 announced by Tantek].
* [http://leftlogic.com/info/articles/microformats_bookmarklet Microformats Bookmarklet] is a bookmarklet designed for Safari (works in Firefox and Camino) that overlays on the current page to allow users to import individual [[hcard|hCards]] or [[hcalendar|hCalendars]]. Written by [http://leftlogic.com Remy Sharp].

==Conversion and Import==
Implementations you can use to importing into a calendar application, typically by converting hCalendar to iCalendar/vCalendar.

===Web Services===
These return iCalendar (.ics) and other calendar formats for easy importing into typical calendar programs or other processing.
* [http://feeds.technorati.com/events Technorati Events Feed service] uses X2V library to parse hCalendar and return iCalendar (.ics).
**Note friendly URL, e.g. http://feeds.technorati.com/events/http%3A//microformats.org
**The [http://georgebrock.com/projects/enhanced-hcalendar-downloads/ enhanced-hcalendar-downloads] script detects links to this service and displays a menu when they are clicked containing the original Technorati link and links to add the event to Google, Yahoo! and 30boxes.
* [http://suda.co.uk/projects/X2V/ X2V] parses hCalendar and produces a .ics (iCalendar) stream.
**Note: needs to be updated to track changes in the specification as they occur.

* [http://spanningsalesforce.com/ Spanning Salesforce] produces hCalendar-enabled RSS feeds and .ics calendars from Salesforce.com.
* [http://makedatamakesense.com/myspace/event/ MySpace Events RSS Creator] creates RSS feeds of MySpace events with hCalendar markup.

===Firefox Greasemonkey Plugins===
* [http://george.hotelling.net/90percent/ George] has built a [http://george.hotelling.net/90percent/geekery/greasemonkey_and_microformats.php Greasemonkey user script that detects hCalendar events and allows users to easily add them to their calendar application(s)].
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including hCalendar events, and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. The hCalendar to vCalendar conversion is done internally within the script. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''

===Aggregators===
* [http://placenamehere.com/mf/nnwextract/ Extract Microformats] is a script for NetNewsWire that supports extracting hCard and hCalendar data in blog posts (via Technorati service). Written by [[User:ChrisCasciano|Chris Casciano]]
* [http://kula.jp/software/endo/screenshots/ Endo], an OS X aggregator, supports discovering hCalendar and adding those events to iCal. Look at the last screenshot at the bottom of the page.

===Converters===
* [http://www.w3.org/People/Bos/HcalProxy/ Hcalproxy] runs as an HTTP server, either standalone or under inetd(8), and converts hCalendar to iCalendar. E.g., if Hcalproxy is running on localhost port 8000 and <nowiki>http://example.org/page.html</nowiki> points is an HTML page, then <nowiki>http://localhost:8000/http://example.org/page.html</nowiki> is an iCalendar document with the events from that page.

==Browsing==
Implementations that detect, display and otherwise highlight hCalendar events in pages.

* In [http://www.xfytec.com/community/ xfy Community], there are some hCalendar implementations. "hCalendar via RSS" parses an RSS feed, retrieves XHTML documents linked from that feed, and syndicates hCalendars into a calendar view.
* [http://code.google.com/p/js-hcalendar js-hcalendar] parses hCalendar and produces a displayable HTML table/CSS-based calendar (formerly called JSCalendar).
* [http://thebitterpill.com/07-2007/a-jquery-hcal-parser/ jqueryhcal] is a jQuery-based hCalendar parser that supports multi-day events, dtend, and other features.

===Firefox extension===
*[http://www.orch8.net/ AlchemyPoint] is a Firefox extension and proxy service that can detect microformats in HTML documents and display browsing/mashup suggestions based on their contents.
*[http://blog.codeeg.com/tails-firefox-extension/ Tails is a Firefox Extension] that will display the presence of microformats ([[hcard|hCard]], [[hcalendar|hCalendar]], [[hreview|hReview]], [[xfolk|xFolk]]) on a webpage.
*[https://addons.mozilla.org/en-US/firefox/addon/4106 Operator] also displays the presence of microformats, is extensible, and allows you to add actions such as "Add hCalender to Yahoo! Calendar".

====Pending====
*[http://reminderfox.mozdev.org/ ReminderFox] have hCalendar import on their "to do " list.

===Flock extension===
*[http://www.orch8.net/ AlchemyPoint] is a Flock extension and proxy service that can detect microformats in HTML documents and display browsing/mashup suggestions based on their contents.
*[http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar

==Libraries==
Open source libraries of hCalendar parsers and other related code for building hCalendar implementations. Note: it is very likely that some of the above implementations may be duplicated in this section. That's ok.
; Javascript :
* [http://virtuelvis.com/archives/2005/11/learn-to-love-microformats simple hCalendar parser] by [http://virtuelvis.com/ Arve Bersvendsen]
* [http://microformats.org/code/hcalendar/creator hCalendar creator] ([[hcalendar-creator-feedback|hCalendar creator feedback]])
; PHP :
*[http://randomchaos.com/microformats/base/ Microformat Base] is an open-source PHP microformat aggregation crawler, currently recognizing hreview, hcalendar, and hcard (Source code no longer available as of 6 Dec 06).
*[http://enarion.net/phpmicroformats/ phpMicroformats] is a PHP class library that generates microformats for calendar events (hCalendar) and vcards (hCard).
* [http://fresh.t-systems-sfr.com/unix/src/www/WebCalendar-devel-1.1.1.tar.gz:a/WebCalendar-1.1.1/includes/classes/hKit/hcal.profile.php hCalendar profile] for the [http://allinthehead.com/hkit/ hKit] parser.
; Ruby [http://rubyforge.org/projects/uformats/ uformats]: is a ruby library that can parse [[hCalendar]], [[hCard]], [[hReview]] and [[rel-tag]]
; XSLT :
* X2V is available as an XSLT library
* [http://dev.w3.org/cvsweb/2001/palmagent/ palmagent] by [[User:DanC]] includes toICal.xsl and test materials; it works much like xhtml2vcal.xsl in X2V. See also: [http://www.w3.org/2002/12/cal/ RDF Calendar workspace] with icalendar test materials.
; Python :
* [http://vobject.skyhouseconsulting.com/ vObject], part of the Chandler project, claims experimental hCalendar support.

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

2006-in-review

2009-01-08T20:03:48Z

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

This is a draft of some text for a 2006 year in review for the microformats blog. Feel free to add more information, events, link etc. then it can be distilled down for the main page of the site

= 2006, Year in Review =

<em>Just when you thought you wouldn't have to read another "year in review" blog post…</em>

Last year I did a <a href="http://microformats.org/blog/2006/01/04/2005-year-in-review/">2005 year in review post</a>. I decided too look back and see how much of that came true, how far we've come, and make a few 2007 predictions.

In terms of community, I think Microformats has blossomed from the hand-full of folks who started it all, to a thriving community of people contributing to the mailing list, the wiki, writing blog posts, writing books and articles, and evangelizing microformats within their organizations and communities.

We've also seen Microformats creep into the mainstream. At Mix06 Bill Gates said <a>"We need more Microformats"</a>, we saw the possibilities of "<a>Live Clipboard</a>", an application to do a "smart copy and paste" from the web to desktop applications, "<a>Live Writer</a>", a new blogging writer that uses microformats for events, rumblings of <a>FireFox 3 natively supporting Microformats</a>, <a>IE 8 as well</a>. We've seen <a>Apple computers use hCard</a> in their web Mail and <a>Flickr introduce geo-tagging</a> of images and within weeks there were millions of instances of microformatted data available. We've even seen Microformats make it to the <a>homepage of the W3C</a>.

If 2005 was the year we hammered out formats, then 2006 was the year of adoption. As Microformats were presented at <a>BarCamps and conferences worldwide</a>, more and more people started to add <a>hCards</a>, <a>hCalendar</a> and <a>hReviews</a> to their blogs. With all the enthusiasm several sites have popped-up that are dedicated to microformats, <a>microformatique.com</a> and <a>whymicroformats.com</a> are just two. Among the many usefimplementations, the new 'operastor' toolbar for Firefox is noteworthy.

So what does 2007 hold? There is still lot of work going on both developing existing formats and working on new ones. In 2006 there were Microformat presentations at several big conferences. In 2007 there will be even more - in fact, if you look at Conference proposals, microformats has been broken out into it's own bullet point under web-technologies.

Ongoing proposals which may well come to fruition in 2007 include currency (for amounts of money), species (for the names of living things), and an extension to geo (to allow for the marking-u[ of coordinates on the Moon, Mars and such bodies) [+ others?].

My predictions for 2007 include more Microformats related books, articles and presentations. Microformats integration with other technologies, such as <a>GRDDL</a> and <a>SPARQL</a> to help bridge the gap to <a>Tim Berners Lee's vision of the Semantic Web</a>. <a>Dan Cederholm</a> said Microformats are "Oblivious Development"(???). Which means that for little extra effort you can add Microformats to your site and without even knowing it, you are allowing other people to develop highly advanced applications using the data. 2007 will see more mash-ups that couldn't have been done previously without Microformatted data. With the <a>W3C starting to incrementally advance HTML</a> there are opportunities to bake some of the semantics of Microformats right into the next version of HTML. The WHATWG, which is working on their version of <a>HTML5</a>, has added two new elements <calendar> and <contact> which are analogous to hCalendar and hCard. I would bet some of the Microformats principles and formats will be seen in the next versions of HTML.

Work that needs to be done in 2007 includes more advocacy, evidence gathering for xxx, cheatsheet creation and refinement, wiki development and translation, plus xxxx. Why not get involved?

As for everyone involved in the community, you should look back on 2006 with pride. We've done a lot of work and it wouldn't have been possible without your support.

==Comment==
* Would this be better in the second-person-plural ("Last year we did...", "Our predictions...")? [[User:AndyMabbett|Andy Mabbett]]

semantic-html

2009-01-08T20:03:34Z

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

<h1> Semantic (X)HTML </h1>
{{TOC-right}}
Semantic (X)HTML refers to:
# The semantic elements and attributes of (X)HTML (as opposed to the [[presentational-html|presentational HTML]] elements and attributes)
# (X)HTML documents that are written using semantic (X)HTML.
# The practice of writing semantic (X)HTML
# [[posh|plain old semantic HTML (POSH)]]

== Contributors ==
* [http://tantek.com/ Tantek]
* [[User:AndyMabbett|Andy Mabbett]]
* [[User:RobManson|Rob Manson]]

== Semantic Elements ==
Based on the [http://www.w3.org/TR/html401/index/elements.html Index of HTML 4 Elements].

=== alphabetical ===
Elements for marking up <em>visible</em> text and user interactivity only.
* a
* abbr
* acronym
* address
* area
* base
* bdo
* blockquote
* body
* button
* caption
* cite
* code
* col
* colgroup
* dd
* del
* dfn
* dir (deprecated)
* div
* dl
* dt
* em
* fieldset
* form
* h1
* h2
* h3
* h4
* h5
* h6
* html
* img
* input
* ins
* isindex (deprecated)
* kbd
* label
* legend
* li
* map
* menu (deprecated)
* noframes
* noscript
* object
* ol
* optgroup
* option
* p
* pre
* q
* samp
* select
* span
* strong
* table (when used for tabular data, not layout)
* tbody
* td
* textarea
* tfoot
* th
* thead
* title
* tr
* ul
* var
==== invisible semantics ====
* head
* link
* meta
* param
==== layer hooks ====
* script
* style

=== semantically clustered ===
These lists/clusterings are incomplete.
==== hypertext ====
* a
* area
* map

==== common prose document ====
* abbr
* acronym
* em
* h1
* h2
* h3
* h4
* h5
* h6
* p
* strong
* title

==== quotes and references ====
* blockquote
* cite
* q

==== contact ====
* address

==== infrastructure ====
* html
* body (because of 'profile' attribute)
* base
* del
* ins

==== international ====
* bdo

==== forms ====
* form
** fieldset
*** legend
*** label
*** button
*** input
*** isindex (deprecated)
*** select
**** optgroup
**** option
**** textarea

==== programming ====
* code
* kbd
* pre
* samp
* var

==== tabular data ====
* table (when used for tabular data, not layout)
** caption
** col
** colgroup
** thead
*** th
** tbody
*** tr
**** td
** tfoot

==== definitions ====
* dfn
* dl
** dt
** dd

==== text user interface ====
* dir (deprecated)
* menu (deprecated)

==== media ====
* img
* object

==== lists ====
* ol
* ul
** li

==== generic ====
* div
* span

== Semantic Attributes ==
(This list is incomplete, please add!)
* axis
* caption
* class
* data
* headers
* href
* hreflang
* id
* lang
* rel
* rev
* scope
* summary
* title
* type

== Presentations ==
See [[posh#POSH_Presentations|POSH Presentations]].

== See also ==
* [[semantic-xhtml-design-principles]]
* [[semantic-class-names]]

== References ==
* [http://w3.org/TR/xhtml1 XHTML 1.0]
* [http://w3.org/TR/html401 HTML 4.01]

currency-examples-fr

2009-01-08T20:03:26Z

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

= Exemples de Devises =
Les exemples qui suivent sont des exemples du vrai-monde et un brainstorming pour baliser les '''[[currency-fr|currency]]'''.
== Le Problème ==

Le problème : comment spécifier explicitement a) qu'un chiffre/nombre est apparenté à de l'argent ; b) la devise d'un chiffre déclaré et c) la période dans laquelle ce chiffre est en cours.

*Le signe de la devise ne peut pas être utilisé en toute confiance car le même signe (ou symbole) peut représenter plus d'une devise, par exemple $ est utilisé pour beaucoup de dollars différents (USD, AUD, CAD...) et même [http://en.wikipedia.org/wiki/Currency_sign#Examples d'autres unités comme les pesos].

*La langue de la page n'est pas suffisante pour définir la devise des prix sur la page :
** Pus d'une devise peut être utilisée par les personnes qui parlent la même langue.
** La page peut être écrite dans une langue et citer encore des prix/chiffres dans la devise d'un pays différent.
Même si un pays peut être identité, plus d'une devise peut être utilisée dans ce pays.

Convertir les chiffres des devises est un problème relativement facile à résoudre comme indiqué par les [[#Pratiques_Existantes]]. Néanmoins beaucoup d'outils de conversion automatique doivent produire des hypothèse sur la devise du chiffre original - par exemple supposer un USD pour tous les usages de $, ou Livre Anglaise pour £ (qui est aussi [http://en.wikipedia.org/wiki/Lira parfois utilisée pour indiquer la Lire]).

=== Changements dans les Devises ===
Je souhaite m'étende sur un des points mentionnés au-dessus : il pourrait y avoir deux ou plus de devises dans le même pays : par exemple en Roumanie : * ROL - Romanian Lei [being phased out]
* RON - Nouveau Lei roumain
* une fois que la Roumanie aura rejoint l'UE, le RON sera remplacé par l'Euro, (pas immédiatement, probablement dans 2 à 3 ans)

Même si le code à trois lettres est différent dans ce cas, la devise est souvent donnée comme le ''Lei''. Il existe d'autres pays, où des exemples similaires existent ou ont existé. Les deux devises pourraient avoir un nom identique, à cette heure elles ont deux sens vraiment très différents. Généralement il existe une différence de 3-4 ordres de grandeurs entre la vieille devise et la nouvelle devise. [[discoleo]]

===Problèmes apparentés ===
Le "Montant" en unité arbitraire est un peu plus difficile et nécessaire pour plusieurs applications.

Par exemple, regardez le travail qui a été réalisé sur un microformat de recette.

[[recipe-examples-fr|exemples de recettes]]

Bien que nous ne soyons pas parvenus à ce problème dans la recherche, je peux le voir venir :

Disons que vous vouliez créer une application de "liste de courses" qui vous dirait quelles recettes vous voulez cuisiner, et avoir automatiquement l'addition de toutes les diverses quantités d'ingrédients et qui vous donne le montant net des choses que vous voulez prendre.

Cela nécessiterait de pouvoir déterminer des montants/unités de chaque ingrédient. Ce pourrait se transformer comme le problème de la devise, ou cela pourrait être plus complexe, compte tenu de la variété des unités utilisées dans les recettes, système métrique vs anglo-saxon, etc. C'est un cas qui aurait besoin d'un microformat. Nous avons besoin de plus de recherche et d'analyse pour vraiment le justifier, mais je peux le voir dans le royaume de la possibilité probable.

===Utilisation de montants en devises dans les tableaux===

Représenter les montants en devises dans un format tableau est très courant. Regardez par exemple [http://investor.google.com/fin_data.html Google Financials].

In this table representation, it does not make sense to provide the currency information for each cell. Instead, it should be provided once at the table, thead, tr, or th, level, and then a td may override the default value. This is very similar to the common practice of indicating the currency and formatting in plain english: "Numbers in thousands of dollars" in the table title/subtitle or legend.

The microformat for currency amounts should provide a way to represent a default currency for all children of a table, thead, tr, or th nodes.
The currency symbol/abbreviation should be optional in for elements defined as containing currency values/amounts, if a default currency has been defined in one of the ancestor elements.

== Contributeurs ==
* [http://weblog.200ok.com.au/ Ben Buchanan] (proponent)
* Arve Bersvendsen
* [http://tantek.com/log/ Tantek Çelik]
* [http://steve.ganz.name/ Steve Ganz]
* Charles Iliya Krempeaux
*[[User:AndyMabbett|Andy Mabbett]] (2nd proponent)
* Ciaran McNulty
* Mike Stickel
* Ben Ward
* Guillaume Lebleu

(traduction en cours : [[Christophe Ducamp]])

== Exemples du Vrai Monde ==
''Liens vers des pages web publiques, soit populaires ou soit pertinentes''

=== [http://www.skype.com/products/skypeout/ Tarifs Skyepout] ===
<pre>2.1 US cents/2.4 CAN cents per minute</pre> (sur la page Web)

<pre>¢2.1 USD (ou ¢2.4 CAD) par minute.</pre> (in the announcement email)

Voir aussi [[measure-fr|measure]]

=== [http://enterpriseforum.mit.edu/mindshare/startingup/dilution.html MIT Enterprise Forum ] ===

<pre>$1 million in equity</pre>

<pre>$2.50 a share</pre>

Voir aussi [[measure-fr|measure]]

=== [http://tonto.eia.doe.gov/oog/info/ngw/historical/2004/06_24/ngupdate.asp Energy Information Administration] ===

<pre>23 cents per barrel</pre>

Aussi dans cette [http://www.eia.doe.gov/emeu/international/oilprice.html page]:

<pre>(U.S. Cents per Gallon)</pre>

<pre>(Euros per Thousand Liters)</pre>

<pre>(U.S. Dollars per Gallon)</pre>

Voir aussi [[measure-fr|measure]]

=== [http://www.cbc.ca/money/story/2005/08/08/oil-050808.html CBCNews] ===

<pre>$63.94 US per barrel, up $1.63 US</pre>

=== [http://finance.google.com/finance?q=google&hl=en Google Finance] ===

La valeur en cours d'une action :

<pre><span class="pr">401.90</span></pre>

=== [http://www.ebay.com eBay] ===

eBay marque les prix sous "ebcPr". eBay c? Price.

<pre>
<td class="ebcPr"><span class="bold">$11.70</span><br/><span>$12.95</span><br/></td>
</pre>

=== [http://code.google.com/webstats/2005-12/classes.html Google] ===
Le Service de Publication de Statistiques de Google mentionne que "price" est le 40° nom de classe utilisé.

Quelque chose comme :

<pre>
<span class="price">$39.99</span>
</pre>

=== [http://us.mcafee.com/root/package.asp?pkgid=100 McAfee] ===
<pre>
<span class="price">$39.99 <span class="currency">(USD)</span></span>
</pre>

=== [http://www.amazon.com/gp/product/0764597582/sr=8-9/qid=1153301402/ref=sr_1_9/002-9103678-0608852?ie=UTF8 Amazon] ===
<pre><td class="price">$34.85</td></pre>

=== [https://secure.vmp.com/signup/adv_signup.php?locale=fr_CA Bell Canada in French Canadian] ===
<pre><b>Niveau de service Premium - 125 $*</b></pre>

Notez le placement du signe dollar APRES le nombre.

=== [https://secure.vmp.com/signup/adv_signup.php?locale=en_US Bell Canada in US English] ===

<pre><b>Premium Service Level - $125*</b></pre>

===Prix Historiques===
*[http://www.westmidlandbirdclub.com/biblio/worcs.htm#MalvernHand West Midland Bird Club Bibliography] (Prix publiés de livres anciens)
*[http://www.westmidlandbirdclub.com/reviews/rarer.htm West Midland Bird Club CD-ROM review] (prix à la date de la critique ; réduit depuis)
**[http://www.westmidlandbirdclub.com/archive/jubilee-54.htm Silver Jubilee] (1954) - prices in text ("'''five shilling subscriptions'''", "'''10/-'''") shown in footnotes as "'''1 shilling = 5p'''" and "'''10/- = 10 shillings (50p)'''" respectively.

*[http://en.wikipedia.org/wiki/Bleak_House#Original_publication Wikipedia: Bleak House]
**"Like most Dickens novels, Bleak House was published in 19 monthly instalments, each containing 32 pages of text and two illustrations by Phiz. Each cost one shilling, except for the last, which was a double issue and cost two." Dates in the subsequent table range monthly from March 1852 - September 1853
*[http://en.wikipedia.org/wiki/1922_in_Germany#Inflation_and_Repercussions Wikpedia: 1922 in Germany]
**"Despite the ending of cash payments for the rest of 1922, the main cause of Germany's inability to pay, the steady depreciation of the mark, was ongoing. Towards the end of the year it assumed a disastrous rapidity. On August 1, the US Dollar still stood at 643 Marks to the Dollar and the British Pound at 2,850 Marks to the Pound. But on September 5 the dollar had already risen to 1,440 Marks and the pound to 6,525 Marks, and in December the pound was worth between 30,000 and 40,000 marks and the dollar between 7,000 and 9,000."
*[http://news.bbc.co.uk/1/hi/business/1096916.stm BBC News story dated 2 January, 2001]
**"A barrel of Brent crude for February delivery came within range of $25 a barrel on Tuesday before slipping to $24.35, a closing price 48 cents above Friday's closing price of $23.87. In New York, the price of Nymex (New York Merchantile Exchange) crude reached $27.40 a barrel before settling at $27.40, a gain of 41 cents or 1.5% on the day. Nymex oil prices in 2000 averaged $30.20 a barrel, the highest level since 1983, and well above the 1999 average of $19.25. Traders also saw support for the oil price from the Opec basket of seven crude oils which stood at $21.75 a barrell on 29 December 2000. That was the seventh day the price stayed below a preferred range of $22-$28 a barrell. Under an Opec price stability measure, output will be cut by 500,000 barrels a day if the basket price stay below $22 for more than 10 days."
*[http://news.bbc.co.uk/1/hi/uk/911569.stm BBC News story dated 5 September, 2000]
**"The Millennium Commission's decision to grant an extra £47m to the Dome has been widely condemned by MPs on various political hues."
*[http://www.jamaica-gleaner.com/pages/history/story0014.html Jamaica and the Great War]
**"in 1917 [...] unemployment was high and wages were low - men received 9 pence a day to cut cane."
*[http://www.wilkiecollins.demon.co.uk/coinage/coins.htm Money and Coinage in Victorian Britain]
*[http://www.margaretmorgan.com/wesley/state.html Macaulay on the State of England in 1685]
**"In 1661 the justices at Chelmsford had fixed the wages of the Essex labourer, who was not boarded, at six shillings in winter and seven in summer."
*[http://www.bbc.co.uk/ww2peopleswar/stories/74/a4095074.shtml BBC - WW2 People's War]
**"I left [school] at Easter 1938. As soon as I had left school, my Father insisted that I went to work for my Uncle. My wages were 5 shillings per week plus board & lodgings"
*[http://privatewww.essex.ac.uk/~alan/family/N-Money.html Relative Value of Sums of Money]

== Pratiques Existantes ==

===Extension Firefox ===
[http://viewmycurrency.wordpress.com/about/ Firefox Currency Converter - ViewMyCurrency]

Note : la [http://viewmycurrency.backpackit.com/pub/403081 liste actuelle de bug] illustre quelques problèmes d'identifier les devises en se fondant seulement sur le contenu de la page :
<blockquote>
<ul>
<li>Tous les symboles $ sont traités comme des USD. Très ennuyeux si vous êtes Australien, Canadien, etc. (Besoin d'une nouvelle fonctionnalité)</li>
<li>‘Euro 2006 Championship’ ne devrait pas être converi.</li>
<li>...</li>
<li>Ne convertissez pas les mots-clés CVS. $Revision: 1.3 $ ne devrait pas être traité comme des dollars.</li>
</ul>
</blockquote>

===Scripts Greasemonkey ===
[http://nybblelabs.org.uk/projects/exchequer Exchequer]

[http://6v8.gamboni.org/Greasemonkey-Yahoo-Finance.html Yahoo! Finance Currency Converter]

[http://www.xe.com/iso4217.htm ISO 4217 Codes]

[http://viewmycurrency.wordpress.com/about/ Firefox Currency Converter - ViewMyCurrency]

<p>Note: the [http://viewmycurrency.backpackit.com/pub/403081 current bug list] illustrates some problems of identifying currencies based on page content alone:</p>
<blockquote>
<ul>
<li>All $ symbols are treated as USD Very annoying if you are Australian, Canadian etc. (Needs a new feature)</li>
<li>‘Euro 2006 Championship’ should not be converted.</li>
<li>...</li>
<li>Don’t convert CVS keywords . $Revision: 1.3 $ should not be treated as dollars.</li>
</ul>
</blockquote>

===Standards pertinents ===
[http://www.xe.com/iso4217.htm ISO 4217 Codes]

== Voir aussi ==
{{currency-related-pages-fr}}
* [[abbr-design-pattern-fr]]

hreview-issues

2009-01-08T20:03:17Z

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

<h1> hReview issues </h1>

These are externally raised issues about [[hreview|hReview]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec.

'''IMPORTANT''': Please read the [[hreview-faq|hReview FAQ]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [http://tantek.com/ Tantek]

Please add new issues to the '''top''' of the list. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

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

__TOC__

== Issues ==

=== rel="self" ===

OpenIssue 2005-01-04 by [[User:DavidJanes|David Janes]]:

Atom defines rel="self" [http://atompub.org/2005/07/11/draft-ietf-atompub-format-10.html#rfc.section.4.2.7 here]

: The value "self" signifies that the IRI in the value of the href attribute identifies a resource equivalent to the containing element.

HTML rel="boomark" [http://www.w3.org/TR/REC-html40/types.html#type-links here]

: Refers to a bookmark. A bookmark is a link to a key entry point within an extended document. The title attribute may be used, for example, to label the bookmark. Note that several bookmarks may be defined in each document.

Since we're using "bookmark" to mean the entry point to the hReview, isn't the "self" redundant or overly subtle?

=== Multilinguism ===

*{{OpenIssue}} 2006-03-22 raised by Fil
*# the reviewer spec can't say ''For anonymous reviews, use "anonymous" (without quotes) for the full name of the reviewer.'' as this word ("anonymous") is going to be apparent on the page, and is not multilingual (and even in English someone might want to use another word, like "an anonymous coward")

=== Price ===
* {{OpenIssue}} 2006-04-04 raised by [[User:Evan|Evan]].
*# It doesn't seem possible to give an approximate, average, or absolute '''price''' of the product or service in question. Examples: for a piece of software, the suggested retail price. For a restaurant, average price of an entree, ''or'' a '''price range'''. Prices should almost definitely have a ''currency'' marker and an ''amount''. Suggestion: ''<nowiki><span class="price"><abbr class="currency" title="Canadian dollars">$</abbr><span class="amount">10.99</span></span></nowiki>''. For a range, ''<nowiki><span class="pricerange"><span class="price"> ... </span> to <span class="price"> ... </span></span></nowiki>''.

== Template ==

{{issues-format}}

== Resolved Issues ==
Issues that are resolved but may have outstanding [[to-do]] items.
* ...

== Closed Issues ==
Resolved issues that have no further actions to take.

=== default lower bound ===
* YYYY-MM-DD????? raised by [[User:ScottReynen|Scott Reynen]]
*# ''Why is the default lower bound 1 when the [[reviews-formats|real world examples]] almost all have a lower bound of 0?''
*#* REJECTED INVALID ASSUMPTION. Most [[review-examples|real-world examples]] have a lower bound of 1, not 0.

=== default range ===
* 2006-02-23 raised by Andy Mabbett
*# ''Not all marks give ratings "out of five". The value should be a percentage. Zero should be allowed.''
*#* REJECTED IGNORES RESEARCH. Most [[review-examples|real-world examples]] have a range of 1.0-5.0 not a percentage. You may set the "best" bound to 100 explicitly, and the "worst" bound to 0 explicitly per the spec if necessary.
*#* "most" != "all"; indeed, the page you cite has examples of "1-10" and "0-100%". I never claimed that many examples use percentages, but I'm sure a mathematician would explain that values in the range "1-5" may be expressed as percentages.
*#* REJECTED RTFM. Most examples are what the defaults are based on. Please re-read both the spec and the previous resolution, 1-10 is allowed (you have to explicitly set "best" to 10), and so is 0-100 (you have to explicitly set "worst" to 0 and "best" to 100).

=== Specification Clarifications ===
* 2006-02-01 raised by [http://tantek.com Tantek].
*# ''The spec needs to clarify that there is only one "item" per "hreview".''
*#* ACCEPTED. Resolved in hReview 0.3.

=== Date and Time ===
* 2006-08-24 raised by [[User:Elias|Elias Sinderson]]
*# ''Issue 1: (This is copied from the hcalendar-issues page, as it applies to hreview as well.) Although ISO 8601 allows both basic (sans delimiters) and extended formats, the extended format (where hyphens and colons are explicitly added) is broadly preferred for the web. While RFC 2445 specifies that the basic form be used in in iCalendar date / time fields, the W3C has published a technical [http://www.w3.org/TR/NOTE-datetime note] (submitted by Reuters), which recommends that the extended (delimited) format be used, and the [http://www.w3.org/TR/html401/types.html#h-6.11 HTML 4.0 spec] uses the extended format. Further, RFC 3339 defines a ISO 8601 profile for dates and time representations on the internet that future specs SHOULD use; recommending a fully delimited representation (see sec. 5.6). Lastly, it should be noted that the [http://www.w3.org/TR/xmlschema-2/#date xsd:date] and [http://www.w3.org/TR/xmlschema-2/#dateTime xsd:dateTime] types are specified as being the ISO 8601 extended format. So, given that hCalendar is based on iCalendar, it is understandable that it allows both formats, however this is clearly a case in which it would be very reasonable to require users to upconvert the format into the least ambiguous and most easily parsed / validated representation. Think of the children.
*#* REJECTED. INCORRECT METHODOLOGY. "Require users to upconvert"?? No. We optimize for publishers (the "users" in this context) more than developers. Whenever you find yourself saying or even <em>thinking</em> "require users", you're probably thinking along the wrong lines of reasoning. In particular we have already made the decision/resolution to permit the broader range of datetime values permitted by RFC2445, and explicitly included some shortcuts (e.g. timezone offsets) specifically to make things <em>easier</em> for <em>users</em>.

==Related pages==
{{hreview-related-pages}}

items-brainstorming

2009-01-08T20:03:06Z

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

#REDIRECT [[item-brainstorming]]

hatom-fr

2009-01-08T20:02:57Z

RyanKing: Reverted edits by NocorElalo (Talk) to last version by ElzelDarno

[http://betheres.qsh.eu/comment-1025.htm punjabi music video] [http://betheres.qsh.eu/comment-755.htm http] [http://fispruil.qsh.eu/news1963.html kiss sable torrie video wilson] [http://tarobasal.strefa.pl/article1773.htm switchback movie] [http://golxando.0lx.net/1022526121.html schoolgirl movie thumbs]
<h1> hAtom 0.1 </h1>
{{TOC-right}}

hAtom est un microformat pour le contenu qui peut Ãªtre syndiquÃ©, initialement conÃ§u pour les billets de blog mais pas exclusivement. hAtom est basÃ© sur un sous-ensemble du format de syndication [http://www.atomenabled.org/ Atom]. hAtom est l'un des nombreux [[microformats-fr|microformats]] standards ouverts.

== SpÃ©cification Brouillon ==

;Editeur/Auteur
:[http://blogmatrix.blogmatrix.com/ David Janes] ([http://www.blogmatrix.com BlogMatrix, Inc.])
;Contributeurs
:[http://members.optusnet.com.au/benjamincarlyle/benjamin/blog/ Benjamin Carlyle]
:[http://tantek.com/ Tantek Ãelik] ([http://technorati.com Technorati, Inc.])

(Traduction en cours par [[Christophe Ducamp]])

=== Copyright ===
{{MicroFormatCopyrightStatement2005-fr}}

* [[User:Tantek|Tantek]] : Je sors toutes mes contributions Ã cette spÃ©cification dans le domaine public et j'encourage les autres auteurs Ã faire ainsi.
** Quand tous les auteurs/Ã©diteurs auront fait ainsi, nous pourrons retirer la rÃ©fÃ©rence au modÃ¨le MicroFormatCopyrightStatement et la remplacer avec le modÃ¨le MicroFormatPublicDomainContributionStatement.

=== Brevets ===
{{MicroFormatPatentStatement-fr}}

== Introduction ==
hAtom est un [[microformat-fr|microformat]] pour identifier l'information sÃ©mantique dans les billets de blog et pratiquement n'importe quel autre endroit [http://www.atomenabled.org/ Atom] peut Ãªtre utilisÃ©, comme les articles d'actualitÃ©s. Le contenu hAtom est facilement ajoutÃ© Ã la plupart des blogs par de simples modifications aux dÃ©finitions du gabarit du blog.

{{rfc-2119-intro-fr}}

== Principes de Design XHTML SÃ©mantique ==
{{semantic-xhtml-design-principles-fr}}

== Format ==
=== En GÃ©nÃ©ral ===
Le [http://atomenabled.org/developers/syndication/#person Format de Syndication Atom] fournit la base conceptuelle pour ce microformat, avec les mises en garde suivantes :

* Atom fournit beaucoup plus de fonctionnalitÃ©s qu'il n'en faut pour un microformat "billet blog", aussi nous avons pris le nombre minimal d'Ã©lÃ©ments requis.
* le modÃ¨le "logique" de hAtom est celui d'Atom. S'il y a un conflit, Atom devrait Ãªtre pris comme correct.
* le modÃ¨le "physique" de hAtom -- la vÃ©ritable Ã©criture des Ã©lÃ©ments -- est bien plus variÃ© que ce que fournit Atom, du fait de la variÃ©tÃ© des maniÃ¨res dont sont effectivement produits les weblogs dans la jungle. Le microformat hAtom fournit un certain nombre de rÃ¨gles pour "ponter le fossÃ©"

=== SchÃ©ma ===
Les Ã©lÃ©ments du schÃ©ma sont basÃ©s sur la nomenclature Atom et suivent le modÃ¨le de prÃ©fixer un identifiant unique (dans ce cas, '<code>h</code>') sur la plupart des Ã©lÃ©ments conteneurs -- le Fil ou l'EntrÃ©e. Les parties de ce microformat sont basÃ©es sur l'analyse de beaucoup de weblogs, de bulletin board et de billets mÃ©dia et peuvent Ãªtre lus sur [[blog-post-brainstorming-fr#El.C3.A9ments_D.C3.A9couverts|blog-post-brainstorming#ElÃ©ments dÃ©couverts]].

Le schÃ©ma hAtom comprend les points suivants :

* hfeed ('''<code>hfeed</code>'''). optionnel.
** '''<code>feed category</code>'''. optionnel. mots-clÃ© ou phrases, en utilisant '''[[rel-tag-fr|rel-tag]]'''.
** hentry ('''<code>hentry</code>''').
*** '''<code>entry-title</code>'''. requis. texte.
*** '''<code>entry-content</code>'''. optionnel (voir desription champ). texte. [*]
*** '''<code>entry-summary</code>'''. optionnel. texte.
*** '''<code>updated</code>'''. requis en utilisant le [[datetime-design-pattern-fr|datetime-design-pattern]]. [*]
*** '''<code>published</code>'''. optionnel en utilisant le [[datetime-design-pattern-fr|datetime-design-pattern]].
*** '''<code>author</code>'''. requis en utilisant '''[[hcard-fr|hCard]]'''. [*]
*** '''<code>bookmark</code>''' (permalink). optionnel en utilisant '''[[rel-bookmark-fr|rel-bookmark]]'''.
*** tags. optionnel. mots-clÃ©s ou phrases, utilise '''[[rel-tag-fr|rel-tag]]'''.

[*] Quelques Ã©lÃ©ments requis ont des valeurs par dÃ©faut si elles manquent, voir en-dessous.

=== DÃ©tails Champ et ElÃ©ment ===

===== Fil =====
* un Ã©lÃ©ment Fil est identifiÃ© par le nom de classe <code>hfeed</code>
* un Ã©lÃ©ment Fil reprÃ©sente le concept d'un [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.1 fil Atom]
* l'Ã©lÃ©ment Fil est optionnel et s'il manque, il est supposÃ© Ãªtre la page
* les documents hAtom {{may-fr}} avoir plusieurs Ã©lÃ©ments Fil.

===== Fil CatÃ©gorie =====
* un Ã©lÃ©ment Fil CatÃ©gorie est identifiÃ© par [[rel-tag-fr|rel-tag]]
* un Fil PEUT avoir un Fil CatÃ©gorie
* un Ã©lÃ©ment Fil CatÃ©gorie reprÃ©sente le concept d'une [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 catÃ©gorie Atom] dans un [http://www.atomenabled.org/developers/syndication/#optionalFeedElements fil]
* les Ã©lÃ©ments CatÃ©gorie Fil DOIVENT apparaitre Ã l'intÃ©rieur d'un Ã©lÃ©ment Fil mais pas Ã l'intÃ©rieur d'un Ã©lÃ©ment EntrÃ©e
* le [[rel-tag-fr|rel-tag]] <code>href</code> encode le <code>category:term</code> atom ; le lien texte dÃ©finit la <code>category:label</code> atom.

===== EntrÃ©e =====
* un Ã©lement EntrÃ©e est identifiÃ© par le nom de classe <code>hentry</code>
* un Ã©lement EntrÃ©e reprÃ©sente le concept d'une [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.1.2 entrÃ©e Atom]
* tout contenu microformat Ã l'intÃ©rieur d'un Ã©lÃ©ment <code><blockquote></code> ou <code><q></code> dans l'EntrÃ©e ne devrait pas Ãªtre considÃ©rÃ© comme partie de l'EntrÃ©e.
: ''Ceci permet la citation d'autres donnÃ©es microformatÃ©es sans se soucier de corrompre le modÃ¨le''

===== CatÃ©gorie EntrÃ©e =====
* un Ã©lÃ©ment CatÃ©gorie EntrÃ©e est identifiÃ© par [[rel-tag-fr|rel-tag]]
* une EntrÃ©e PEUT avoir une CatÃ©gorie EntrÃ©e
* un Ã©lÃ©ment CatÃ©gorie EntrÃ©e reprÃ©sente le concept d'une [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.2 catÃ©gorie Atom] Ã l'intÃ©rieur d'une [http://www.atomenabled.org/developers/syndication/#optionalEntryElements entrÃ©e]
* le [[rel-tag-fr|rel-tag]] <code>href</code> encode le <code>category:term</code> atom ; le lien texte dÃ©finit la <code>category:label</code> atom

===== EntrÃ©e Titre =====
* un Ã©lÃ©ment EntrÃ©e Titre ('entry-title') est identifiÃ© par le nom de classe <code>entry-title</code>
* une EntrÃ©e DEVRAIT avoir une EntrÃ©e Titre
* un Ã©lÃ©ment 'Entry Title' reprÃ©sente le concept d'une [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.14 entrÃ©e titre Atom]
* si 'Entry Title' manque, utilisez
** le premier Ã©lÃ©ment <code><h#></code> dans l'EntrÃ©e, ou
** le <code><title></code> de la page, s'il n'y a pas d'Ã©lÃ©ment Feed enclos, ou
** supposez que ce soit la chaÃ®ne vide

===== EntrÃ©e Contenu =====
* un Ã©lÃ©ment "Entry Content" est identifiÃ© par le nom de classe <code>entry-content</code>
* une EntrÃ©e DEVRAIT ({{should-fr}}) avoir une EntrÃ©e Contenu
* un Ã©lÃ©ment "Entry Content" reprÃ©sente le concept d'un [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#atomContent contenu Atom]
* une EntrÃ©e PEUT ({{may-fr}}) avoir 0 or plus Ã©lÃ©ments "Entry Content". L'"Entry Content" logique d'une EntrÃ©e est la concatÃ©nation, par ordre d'apparition, de toutes les EntrÃ©es de Contenus dans l'EntrÃ©e.
: ''Beaucoup de weblogs dÃ©coupent le contenu en plusieurs sections avec un lien "En savoir plus" et des trucs javascript. Ceci est aussi requis dans les cas oÃ¹ les 'entry-title' sont codÃ©s dans la ligne et sont considÃ©rÃ©s comme partie du contenu.''
* si 'Entry-Content' manque, supposez que c'est la chaÃ®ne vide.

===== EntrÃ©e RÃ©sumÃ© =====
* un Ã©lÃ©ment EntrÃ©e RÃ©sumÃ© est identifiÃ© par le nom de classe <code>entry-summary</code>
* un Ã©lÃ©ment 'Entry Summary' reprÃ©sente le concept d'un [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.13 summary Atom]
* une EntrÃ©e PEUT ({{may-fr}}) avoir 0 ou plus d'Ã©lÃ©ments 'Entry Summary'. L'"Entry Summary" logique d'une EntrÃ©e est la concatÃ©nation par ordre d'apparition, de tous les 'Entry Summary' dans l'EntrÃ©e.

===== EntrÃ©e Permalien =====
* un Ã©lÃ©ment 'EntrÃ©e Permalien' est identifiÃ© par [[rel-bookmark-fr|rel-bookmark]]
* une EntrÃ©e DEVRAIT ({{should-fr}}) avoir une 'EntrÃ©e Permalien'
* un Ã©lÃ©ment 'EntrÃ©e Permalien' reprÃ©sente le concept d'un [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.7 lien Atom dans une entrÃ©e]
* si 'EntrÃ©e Permalien' manque, utilisez l'URI de la page ; si l'EntrÃ©e n'a pas d'attribut "id", ajoutez cela comme un fragment vers l'URI de la page pour distinguer les entrÃ©es individuelles

===== EntrÃ©e Mise Ã jour =====
* un Ã©lÃ©ment 'EntrÃ©e Mise Ã jour' est identifiÃ© par le nom de classe <code>updated</code>
* un Ã©lÃ©ment 'EntrÃ©e Mise Ã jour' reprÃ©sente le concept de [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.15 Atom updated]
* une EntrÃ©e DEVRAIT ({{should-fr}}) avoir un Ã©lÃ©ment 'EntrÃ©e Mise Ã jour'
* utiliser le [[datetime-design-pattern-fr|datetime-design-pattern]] pour encoder la date et l'heure de mise Ã jour
* s'il n'existe pas d'Ã©lÃ©ment 'EntrÃ©e Mise Ã jour',
** utilisez l'Ã©lÃ©ment 'EntrÃ©e PubliÃ©e' si prÃ©sent
** autrement la page est invalide hAtom

===== EntrÃ©e PubliÃ©e =====
* un Ã©lÃ©ment 'EntrÃ©e PubliÃ©e' est identifiÃ© par le nom de classe <code>published</code>
* un Ã©lÃ©ment 'EntrÃ©e PubliÃ©e' reprÃ©sente le concept de [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.9 Atom published]
* utilisez le [[datetime-design-pattern-fr|datetime-design-pattern]] pour encoder la date et l'heure de publication

===== EntrÃ©e Auteur =====
* un Ã©lÃ©ment 'EntrÃ©e Auteur' est reprÃ©sentÃ© par le nom de classe <code>author</code>
* un Ã©lÃ©ment 'EntrÃ©e Auteur' reprÃ©sente le concept d'un [http://www.atomenabled.org/developers/syndication/atom-format-spec.php#rfc.section.4.2.1 Atom author]
* un Ã©lÃ©ment 'EntrÃ©e Auteur' DOIT ({{must-fr}}) Ãªtre encodÃ© dans une [[hcard-fr|hCard]]
* un Ã©lÃ©ment 'EntrÃ©e Auteur' DEVRAIT ({{should-fr}}) Ãªtre encodÃ© dans un Ã©lÃ©ment <code><address></code>
* une EntrÃ©e DEVRAIT avoir au moins un Ã©lÃ©ment 'EntrÃ©e Auteur'
* une EntrÃ©e PEUT avoir plus qu'un Ã©lÃ©ment 'EntrÃ©e Auteur'
* si l'EntrÃ©e Auteur manque
** trouvez le(s) Ã©lÃ©ment(s) <code><address></code> [[algorithm-nearest-in-parent-fr|Plus Proche En Parent]] avec le nom de classe <code>author</code> et qui soit/soient une [[hcard-fr|hCard]] valide.
** autrement l'entrÃ©e est hAtom invalide

=== Profil XMDP ===
<pre>
<dl class="profile">
<dt>class</dt>
<dd><p>
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class">
HTML4 definition of the 'class' attribute.</a>
This meta data profile defines some 'class' attribute values (class names)
and their meanings as suggested by a
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile">
draft of "Hypertext Links in HTML"</a>.
<dl>
<dt>hfeed</dt>
<dd>
The concept of atom:feed from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>hentry</dt>
<dd>
The concept of atom:entry from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>entry-title</dt>
<dd>
The concept of atom:title inside of an atom:entry from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>entry-content</dt>
<dd>
The concept of atom:content from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>entry-summary</dt>
<dd>
The concept of atom:summary from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>bookmark</dt>
<dd>
The concept of atom:link (without any "rel") with an atom:entry from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>published</dt>
<dd>
The concept of atom:published from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>updated</dt>
<dd>
The concept of atom:updated from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
<dt>author</dt>
<dd>
The concept of atom:author from
<a href="http://www.atomenabled.org/developers/syndication/atom-format-spec.php">The Atom Syndication Format</a>,
constrained and modified as per the <a href="http://microformats.org/wiki/hatom">hAtom microformat spec</a>.
</dd>
</dl>
</dd>
</dl>
</pre>

== Exemples ==
Voir [[hatom-examples-fr|exemples hatom]].

== Exemples dans la jungle ==
Cette section est '''informative'''.
Voir [[hatom-examples-in-wild-fr|hAtom-exemples dans la jungle]]

== ImplÃ©mentations ==
Cette section est '''informative'''.

Les implÃ©mentations qui suivent ont Ã©tÃ© dÃ©veloppÃ©es et elles gÃ©nÃ¨rent ou parsent les liens hAtom. Si vous avez une implÃ©mentation hAtom, sentez-vous libre de l'ajouter en haut de cette liste. Une fois que la liste sera devenue trop grosse, nous produirons une page wiki sÃ©parÃ©e.



* [http://spinn3r.com/opensource.php Spinn3r Open Source] - implementÃ© dans [http://spinn3r.com Spinn3r] et partie du [http://code.tailrank.com/feedparser FeedParser] et notre annonce de [http://blog.spinn3r.com/2008/01/announcing-spin.html hAtom dans Spinn3r 2.1]
* [http://dichotomize.com/uf/hatom/creator.html hAtom Creator] modifiÃ© Ã partir des autres crÃ©ateur par BenWest.
** semble Ãªtre cassÃ© en date du 14 Oct 2007. renvoie une erreur 404, comme son rÃ©pertoire parent. le site renvoie vers la page d'accueil par dÃ©faut de l'installation Apache.
* [http://www.fberriman.com fberriman.com] utilise hAtom 0.1 pour les billets de blog (boucle wordpress) et hCard -- par [[User:Phae|Frances Berriman]]
* Le [http://tools.blogmatrix.com/extract/ Parseur Microformat Presque Universel] peut extraire le contenu hAtom Ã partir de pages web. ([http://tools.blogmatrix.com/extract/?uri=http%3A%2F%2Fblog.davidjanes.com&microformat=hatom&submit=Submit example])
* le script [http://www.trinityanne.com/tools/greasemonkey/microformat-action.user.js microformat-action] [[greasemonkey-fr|Greasemonkey]] dÃ©tecte le contenu hAtom sur les pages web et appellera le [http://tools.blogmatrix.com/extract/ Parseur Microformat Presque Universel]
* [http://rbach.priv.at/hAtom2Atom/ hAtom2Atom.xsl] transforme hAtom en Atom (comme le suggÃ¨re le nom.)
* Il existe dÃ©sormais un [http://www.lukearno.com/projects/hatom2atom/ proxy hatom2atom] qui utilise hAtom2Atom.xsl.
* [http://placenamehere.com/article/185/SubscribingTohAtomFeedsWithNetNewsWire Subscribe To hAtom] est un script qui fournit aux utilisateurs de [http://ranchero.com/netnewswire/ NetNewsWire 2.x] la capacitÃ© de s'abonner Ã des documents hAtom comme ils le feraient avec n'importe quel autre fil. par [[User:ChrisCasciano|Chris Casciano]].
* [http://boxtheweb.mihopa.net/code/apis/#outlineclasses Outline Classes] - a GPLisÃ© son code PHP pour lire hAtom
* [http://boxtheweb.4x2.net/ BoxtheWeb] - supporte l'abonnement Ã hAtom sous un format fil



== RÃ©fÃ©rences ==
=== RÃ©fÃ©rences Normatives ===
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]
* [http://www.ietf.org/rfc/rfc4287 RFC4287 : Le Format de Syndication Atom]
* [[hcard-parsing-fr|parsage hcard]]
* [[rfc-2119-fr|RFC 2119]]
* [[iso-8601-fr|ISO8601]]

=== RÃ©fÃ©rences Informatives ===
* [http://www.atomenabled.org/ Atom]

==== SpÃ©cifications Qui utilisent hAtom ====

==== Travail Similaire ====
* [http://rdfs.org/sioc/ Semantically-Interlinked Online Communities (SIOC) RDF Ontology]

== Chantier en Cours ==
Cette spÃ©cification est un chantier en cours. Au fur et Ã mesure que des aspects supplÃ©mentaires sont discutÃ©s, compris et Ã©crits, ils seront ajoutÃ©s. Il existe un document sÃ©parÃ© oÃ¹ nous conservons nos brainstorms et autres explorations en rapport avec hAtom :

* [[blog-post-brainstorming-fr|blog-post Brainstorming]]

=== Version 0.1 ===
La version 0.1 est sortie le 28 fÃ©vrier 2006.

== Discussions ==
* voir [http://www.technorati.com/cosmos/referer.html les blogs discutant de cette page].

=== Q&R ===
* Si vous avez quelque question Ã propos de hAtom, regardez les [[hatom-faq-fr|FAQ hAtom]], et si vous ne trouvez pas de rÃ©ponses, ajoutez vos questions !

=== ProblÃ©matiques ===
* SVP ajoutez toutes les problÃ©matiques de la spÃ©cification au document sÃ©parÃ© [[hatom-issues-fr|problÃ©matiques hAtom]].

==Voir aussi ==
{{hatom-related-pages-fr}}
* [[rel-enclosure-fr|rel-enclosure]] - comment rÃ©fÃ©rencer sÃ©mantiquement les piÃ¨ces jointes (par ex. les podcasts) dans hAtom
* [[blog-post-brainstorming-fr|blog-post-brainstorming]]
* [[blog-post-formats-fr|blog-post-formats]]
* [[blog-post-examples-fr|blog-post-exemples]]
* [[blog-description-format-fr|blog-description-format]] - comment dÃ©crire un blog (Ã l'opposÃ© des entrÃ©es individuelles, ce qui n'est pas ce que nous sommes en train de faire ici)

hcard-implied-examples

2009-01-08T20:02:49Z

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

<h1>Implied hCard examples</h1>

Example implied [[hcard|hCards]], see [[hcard-implied]] for a description and [[hcard-implied-brainstorming]] for ideas.

== Authors ==
* [http://ryancannon.com/ Ryan Cannon]

== Instructive Examples ==

=== References to a person within a blog post ===

Blog writers specifically, but other writers on the Web as well frequently link to an individual's homepage by linking that persona's name. One example from [http://www.quirksmode.org/blog/archives/2006/12/24ways_hide_and.html Quirksblog]:

<pre><nowiki>
<p>Just as last year, <a href="http://allinthehead.com" class="external">Drew McLellan</a>
has created his web geek advent calendar 24ways, in which a few web developers of note share
some tips and tricks to impress your friends. Today my contribution:
<a href="http://24ways.org/2006/hide-and-seek-in-the-head" class="external">Hide and Seek
in the Head</a>.</p>
</nowiki></pre>

Displaying as:

Just as last year, [http://allinthehead.com Drew McLellan] has created his web geek advent calendar 24ways ...

Changing "Drew McLellan" to an hCard would currently require the at least following additional markup:

<pre><nowiki>
<p>Just as last year,
<span class="vcard">
<a href="http://allinthehead.com" class="external fn url">Drew McLellan</a>
</span>
has created his web geek advent calendar 24ways...
</p>
</nowiki></pre>

If not:

<pre><nowiki>
<p>Just as last year,
<span class="vcard">
<a href="http://allinthehead.com" class="external fn n url">
<span class="given-name">Drew</span>
<span class="family-name">
<span class="sort-string">M</span>cLellan
</span>
</a>
</span>
has created his web geek advent calendar 24ways...
</p>
</nowiki></pre>

an implied hCard would simplify this construct into a single element with a pre-defined class name.

=== Simple hCards nested in other Microformats ===

==== Citation ====

Brian Suda marked up his citation as

<pre><nowiki>
<p class="author vcard"><a class="fn url" href="http://suda.co.uk/" rel="me">Brian Suda</a></p>
</nowiki></pre>

Which could be shortened into a single element and two class names, and not require knowledge of Citation and hCard.

==== hReview ====

Many reviewers use a construct similar to [http://www.pacificspirit.com/Restaurants-Vancouver.html David Orchard]:

Reviews ... are by <span class="reviewer vcard"><span class="fn">David Orchard</span></span></span>

Or the following invalid construct (from [http://jg.typepad.com/ciel/2006/02/daniel_bouluds_.html Joan], listed on the [[hreview-examples-in-wild|hReview Examples in the wild]]:

<pre><nowiki>
<span class="reviewer fn"><A HREF="http://jg.typepad.com/ciel">Joan Gelfand</A></span>
</nowiki></pre>

An implied hCard would simplify the markup and prevent (some) user error.

==== hAtom ====

The Strangelove Wordpress ([http://www.whump.com/sandbox/Strangelove.zip zip]) theme creates the following construct for authors:

<pre><nowiki>
<span class="vcard author"><a class="url fn" href="http://www.example.com/author">Nickname</a></span>
</nowiki></pre>

While the [http://www.plaintxt.org/themes/sandbox/ Sandbox] theme creates:

<pre><nowiki>
<span class="entry-author author vcard">By
<a class="url fn" href="http://www.example.com/author" title="View all posts by Nickname">Nickname</a>
</span>
</nowiki></pre>

Implied hCards would simplify hAtom implementations for developers.

User:AndyMabbett

2009-01-08T20:02:40Z

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

{{TOC-right}}

==Me==

<div class="vcard">

Hi,

I'm <span class="fn">Andy Mabbett</span>, from <span class="adr"><span class="locality">Birmingham</span>, <span class="country-name">England</span></span>.

I blog at <span class="url">http://pigsonthewing.wordpress.com/</span> and have a neglected website at <span class="url uid">http://www.pigsonthewing.org.uk/</span>

I'm known as <span class="nickname">Pigsonthewing</span> on some websites.

</div>

You can also find me on Twitter and Facebook, but please don't be offended that I only "befriend" people I know well enough to share my home address and phone number with, to the latter.

==My background==

Having programmed machines with paper tape and punched cards (at a very young age!), I'm glad to see things have moved on a little. I gave up programming many years ago, but have been involved in the design and management of pioneering, large-scale websites in the UK's public sector since 1994.

I am a published author and journalist - but (as anyone who's corrected my 'tyops' will tell you) I can't type.

I am a trustee, and webmaster, of the [http://www.westmidlandbirdclub.com/ West Midland Bird Club].

==Web for all==

I believe strongly in adherence to web standards, making web pages as accessible as possible, to everyone, and that it's important to communicate using the simplest language necessary, to convey ideas clearly. Hence [[what-are-microformats#Andy_Mabbett|my proposal for a brief description of microformats]].

==My microformats interests==

I am the proponent of:

*[[luna]]
*[[mars]]
**combined in [[geo-extension-strawman]]
*[[species]]

and have reactivated the previously-proposed:

*[[currency]]

Other pages I have created include:
*[[criticism]]
*[[firefox-extensions]]
*[[hcalendar-intro]]
*[[mediawiki-mark-up-issues]]
*[[rfc-2119]]
** the various [[rfc-2119#Templates]]
*[[iso-8601]]
*lots of redirects, [[cheatsheet|cheatsheets]], templates and splitting of over-long pages

and (at the time of writing) I'm responsible for most of:
*[[advocacy]]

See also: [[Special:Contributions/AndyMabbett|my contributions]]

I have published microformats on:
*This wiki!
*[http://www.westmidlandbirdclub.com/ West Midland Bird Club] including:
** Footers of all pages, as they are updated ([[hcard|hCard]] with logo, using [[include-pattern]]
** [http://www.westmidlandbirdclub.com/club/contact.htm Contact Details] et seq (hCard)
** [http://www.westmidlandbirdclub.com/diary/ Diary events pages] et seq ([[hcalendar|hCalendar]])
** [http://www.westmidlandbirdclub.com/new.htm What's New] ([[hatom|hAtom]])
** [http://www.westmidlandbirdclub.com/ Home Page] ([[rel-tag|[tags]])
*Wikipedia - hCalendar, hCard, [[geo]] and [[adr]]: see [http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Microformats Wikipedia's microformats project]
*Wikitravel - hCard, geo and adr: see [http://wikitravel.org/en/Wikitravel:Microformats Wikitravel's microformats page]
*Wikispecies - pilot use of [[species]]: see [http://species.wikimedia.org/wiki/Wikispecies:Microformat Wikispecies' microformats page]

and am responsible for their use on many other web sites, as listed on our [[advocacy]] pages.

==Browsing==
I usually surf with whatever is the latest formal release of [http://www.mozilla.com/ FireFox], using far too many extensions (including [https://addons.mozilla.org/firefox/4106/ Operator] for parsing microformats), under Windows XP, on a 20" or 2x17" monitor at 1280x1024 resolution.

I use FireFox's live bookmarks and the Sage extension, to view hAtom feeds.

==Censorship==

I object strongly to the [http://microformats.org/wiki?title=faq&diff=0&oldid=9568 removal of this answer], from the [[faq|FAQ]]:

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

A2. Possibly quite considerably, especially if your original data doesn't make use of, or only has few, class names.

For example:

<pre><nowiki>
<tr class="X">
<th scope="row">Friday 3<br>
7:30–9:30pm</th>
<td>
<abbr class="wmbc" title="West Midland Bird Club">
WMBC
</abbr>
<a href="../solihull/indoor.htm" title="Solihull Branch indoor meetings">
Solihull Branch indoor meeting
</a>.
</td>
<td>Solihull College, New Lecture Rooms, Blossomfield Road, Solihull B91 1SB (SP142790).</td>
<td>Steve Smith: The Farne Islands and the Bass Rock.</td>
</tr>
</nowiki></pre>

vs:

<pre><nowiki>
<tr id="D20061103a" class="vevent X">
<th scope="row">Friday 3<br>
<abbr class="dtstart" title="2006-11-03T19:30:00+00:00">
7:30
</abbr>
–<abbr class="dtend" title="2006-11-03T21:30:00+00:00">
9:30
</abbr>
pm
</th>
<td class="summary">
<abbr class="wmbc" title="West Midland Bird Club">WMBC</abbr>
<a class="url" href="../solihull/indoor.htm"
title="Solihull Branch indoor meetings">Solihull Branch indoor meeting
</a>.
</td>
<td class="location vCard">
<span class="fn org">Solihull College</span>,
<span class="adr">
<span class="extended-address">New Lecture Rooms</span>,
<span class="street-address">Blossomfield Road</span>,
<span class="locality">Solihull</span>
<span class="postal-code">B91 1SB</span>
</span>
(<abbr class="geo" title="52.4095; -1.7921">SP142790</abbr>).
</td>
<td class="description">Steve Smith: The Farne Islands and the Bass Rock.</td>
</tr>
</nowiki></pre>

That's 399 characters increased to 860; over double.

===Non-food recipes===
"other musings are purely theoretical [...] [[recipe-brainstorming|recipes]] means only food recipes"
* Google finds hits for [http://www.google.com/search&q=%22weedkiller+recipe%22 "weedkiller recipe"]; [http://www.google.com/search&q=%22paint+recipe%22 "paint recipe"] (about 22,800); [http://www.google.com/search?q=%22whitewash+recipe%22 whitewash recipe]; [http://www.google.com/search?q=%22glue+recipe%22 "glue recipe"] (about 9,910 ); [http://www.google.co.uk/search?&q=%22play+dough+recipe%22 "play dough recipe"] (about 10,300); [http://www.google.co.uk/search?&q=%22concrete+recipe%22 "concrete recipe"]; [http://www.google.co.uk/search?&q=%22gunpowder+recipe%22 "gunpowder recipe"] and [http://www.google.com/search&q=%22plaster+recipie%22 "plaster recipe"] - and again for all those in the format "recipe for..."; e.g. [http://www.google.com/search?q=%22recipe+for+concrete%22 recipe for concrete] (about 11,000). [[User:AndyMabbett|Andy Mabbett]] 09:41, 15 Mar 2007 (PDT)

==Copyright==
<div id="publicdomainrelease" cellspacing="1" cellpadding="1" style="background: #f7f8ff; border: 1px solid #88a; padding: 5px; font-size: 80%;"><span style="float:left;margin:.8em 0">http://upload.wikimedia.org/wikipedia/commons/thumb/6/62/PD-icon.svg/64px-PD-icon.svg.png</span><span style="float:right;margin:.8em 0">http://upload.wikimedia.org/wikipedia/commons/thumb/6/62/PD-icon.svg/64px-PD-icon.svg.png</span>
<div style="background:#fff;margin:0 68px;padding:2px"><div style="text-align: center; background: #ccf;">'''Released into public domain'''</div>
<p>I agree to release all my text and image contributions (past, present and future) to this wiki, into the [[#public-domain|public domain*]]. Please be aware that other contributors might not have done the same, so if you want to use pages with my contributions under public domain terms, please check past contributors' user pages.</p><p id="public-domain">"^ [http://creativecommons.org/licenses/publicdomain/ Creative Commons Public Domain License], the original at http://creativecommons.org/licenses/publicdomain/ or any later version published by Creative Commons; with either a waiver of rights, or an assertion that no rights attach to a particular work."</p></div></div>
[[Category:public domain license|{{PAGENAME}}]]

==Scratchpad==
[[/scratchpad]]

==Overall==

...I'd rather be out bird-watching.

:Keywords: Mabbett, pigsonthewing, birmingham, webmaster, firefox, operator, species, West-Midland-Bird-Club, birder

adr-fr

2009-01-08T20:02:30Z

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

<h1> adr </h1>

{{TOC-right}}

http://rbach.priv.at/2006/buttons/adr.png

'''adr''' (nom de code pour travailler, prononcez "adeure" ; FAQ : [[hcard-faq-fr#Devrais-je_utiliser_ADDRESS_pour_les_hCards|pourquoi "adr"]] ?) est un format simple pour baliser l'information adresse, approprié pour l'embarquement dans le HTML, XHTML, Atom, RSS et le XML arbitraire. '''adr''' est une représentation 1:1 de la propriété ''adr'' dans le standard vCard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]) en HTML, l'un des nombreux standards ouverts [[microformats-fr|microformats]]. C'est aussi une propriété de [[hcard-fr|hCard]].

== Spécification Brouillon ==

; Editeur/Auteur : [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc.])
; Traduction : [[User:ChristopheDucamp|Christophe Ducamp]]

=== Copyright ===
Selon la sortie dans le domaine public sur [[User:Tantek|ma page utilisateur]], cette spécification est publiée dans le domaine public.

{{MicroFormatPublicDomainContributionStatement-fr}}

=== Brevets ===
{{MicroFormatPatentStatement-fr}}

=== Inspiration et Remerciements ===
Merci à tous ceux qui ont participé dans le [[geo-bof-2005-06-30|Geo Microformat BOF at O'Reilly's Where 2.0 conference]], et tout particulièrement [http://radar.oreilly.com/nat/ Nat Torkington] et Vee McMillen de [http://oreilly.com O'Reilly] pour [http://conferences.oreillynet.com/cs/where2005/view/e_sess/7476 organiser et héberger le BOF].

== Introduction et Historique ==
Le standard vCard ([http://www.ietf.org/rfc/rfc2426.txt RFC2426]), a été largement implémenté de façon interopérable (par ex. l'application carnet d'adresses d'Apple). Le microformat [[hcard-fr|hCard]] a de manière similaire reçu une adoption significative de la part de nombreux sites publiant le format des proxies hCards aux vCards, jusqu'aux parseurs javascript côté client.

A la [http://conferences.oreillynet.com/where/ conférence Where 2.0] en juin 2005, il y a eu une reconnaissance largement acceptée que la communauté avait besoin d'un moyen pour publier simplement et facilement sur le web une information d'adresse qui soit visible, extractible, compte tenu du fait que souvent les blogueurs et les nombreux autres sites publient des informations d'adresses. Le [[geo-bof-2005-06-30|geo microformat BOF]] a discuté tout particulièrement de ce sujet et conclu avec une décision consensuelle de simplement essayer d'utiliser ''adr'' venant de vCard/hCard.

Cette spécification présente le microformat '''adr''', qui est une représentation 1:1 de la propriété mentionnée ci-dessus ''adr'' extraite du standard vCard en réutilisant simplement la propriété ''adr'' et les sous-propriétés telles quelles extraites du microfomat [[hcard-fr|hCard]].

Les auteurs peuvent à la fois embarquer directement des adresses '''adr''' dans leurs pages web et fils, tout comme baliser des adresses existantes dans le contexte du reste de l'information dans leurs pages web et fils.

Si l'auteur connaît et publie le '''name''' de l'endroit en plus de son adresse, alors l'auteur DOIT utiliser [[hcard-fr|hCard]] au lieu de simplement '''adr''' pour publier le nom et l'adresse du lieu.

== Principes de Design XHTML Sémantique ==
{{semantic-xhtml-design-principles-fr}}

== Format ==
=== Propriétés Singulières ===

Remarquez que toutes les propriétés dans '''adr''' sont des propriétés singulières et par conséquent le premier élément descendant avec cette classe devrait prendre effet, tous les autres étant ignorés.

=== Lisible Humain vs Machine ===

Si un élément <code><abbr></code> est utilisé pour une propriété, alors l'attribut <code>title</code> de l'élément <code><abbr></code> est la valeur de la propriété, au lieu des contenus de l'élément, ce qui fournit à la place une version humainement présentable de la valeur.

De la même façon, si un élément <code><img></code> est utilisé pour une ou plusieurs propriétés, il doit être traité comme suit :
# Pour la propriété <code>PHOTO</code> et toute autre propriété qui prend un <abbr title="Uniform Resource Locator">URL</abbr> comme sa valeur, l'attribut <code>src</code> fournit la valeur de la propriété.
# Pour d'autres propriétés, l'attribut <code>alt</code> de <code><img></code> est la valeur de la propriété.

=== Extraction Valeur ===

Parfois, seule la part d'un élément qui est l'équivalent pour une propriété devrait être utilisée pour la valeur de la propriété. A cette intention, le nom de classe <code>value</code> est utilisé pour extraire la partie de l'élément qui est la valeur de la propriété. Voir [[hcard-fr|hCard]] pour les détails à ce sujet.

=== Nom Classe Racine ===

Le nom de classe racine pou une adresse '''adr''' est <code>adr</code>.

=== Liste Propriétés ===

Ceci est la liste des propriétés dans '''adr''', extraite de [[hcard-fr|hCard]] :

* <code>post-office-box</code> (boîte postale)
* <code>extended-address</code> (suite adresse)
* <code>street-address</code> (adresse-rue)
* <code>locality</code> (localité)
* <code>region</code> (région)
* <code>postal-code</code> (code postal)
* <code>country-name</code> (nom du pays)

La sous-propriété <code>type</code> est omise parce que sans le contexte d'un type d'adresse pour ''whom'', cela ne fait pas beaucoup plus de sens.

=== Profil XMDP ===

Voir [[hcard-profile-fr|profil hCard]] pour le profil [http://gmpg.org/xmdp XMDP] de hCard qui contient la liste complète au-dessus des propriétés, avec des références vers leurs définitions RFC 2426.

=== Détails Parsage ===
Voir [[hcard-parsing-fr|parsage hCard]], avec la seule différence étant que "adr" est le nom de classe racine, plutôt que "vcard".

== Exemples ==
Cette section est informative.

=== Echantillon adr ===

Voilà un échantillon <code>adr</code> :

<pre><nowiki>
<div class="adr">
<div class="street-address">50 rue Saint Denis</div>
<div class="extended-address">Suite 207</div>
<span class="postal-code">75001</span> <span class="locality">Paris</span>
<div class="region">Ile de France</div>
<div class="country-name">France</div>
</div>
</nowiki></pre>

qui pourrait être affichée comme :

<div class="adr">
<div class="street-address">50 rue Saint Denis</div>
<div class="extended-address">Suite 207</div>
<span class="postal-code">75001</span> <span class="locality">Paris</span>
<div class="region">Ile de France</div>
<div class="country-name">France</div>
</div>

Remarquez que c'est un microformat <code>adr</code> vivant, qui sera trouvé sur cette page par les parseurs.

=== Plus d'exemples ===

Voir [[hcard-examples-fr#3.2.1_D.C3.A9finition_Type_ADR|exemples ADR hCard]] pour plus d'exemples.

Voir [http://microformats.org/wiki/adr-examples-fr exemples adr] pour des usages supplémentaires de ADR.

== Exemples dans la jungle ==
Voir [[hcard-examples-in-wild-fr|hcard-exemples-dans-la-jungle]])

== Implémentations ==
Cette section est '''informative'''.

Les implémentations suivantes ont été développées et soit génèrent ou parsent des adrs en dehors du contexte des hCards. Si vous avez une implémentation adr, sentez-vous libre de l'ajouter en haut de la liste. Une fois que la liste sera devenue trop grosse, nous ferons une page wiki séparée.

* [http://georss.org/geopress GeoPress] est un plugin [http://wordpress.org WordPress] qui supporte l'embarquement des adrs, geo, maps (commutable dynamiquement entre le Cartes Google-Yahoo-Microsoft Maps), et les fils [http://georss.org GeoRSS].

* [http://code.highearthorbit.com/greaseroute/index.php GreaseRoute] est un script utilisateur GreaseMonkey (aussi disponibles comme une simple extension Firefox) qui ajoutera des icônes pour afficher l'endroit, ou la route vers une [[adr-fr|adr]] en utilisant une carte MapQuest. La route est affichée à partir du lieu de départ fondé sur l'Adresse-IP du spectateur déterminée par le service de géolocalisation [http://hostip.info HostIP].

* [http://code.highearthorbit.com/greaseroute/index.php GreaseRouteEmbed] est un autre script utilisateur GreaseMonkey qui embarquera une image de la route dans la page web quand l'utilisateur cliquera sur le lien "route".

* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] est un plugin pour [http://textpattern.com/ Textpattern] qui supporte l'embarquement des adrs et d'autres microformats dans les gabarits et billets de blog. Ecrit par [http://placenamehere.com/ Chris Casciano].

* Le [http://tantek.com/microformats/hcard-creator.html hCard creator], même s'il crée des hCards complètes, peut aussi être utilisé simplement pour créer des adrs en ne remplissant que la portion d'adresse et en copiant et collant simplement l'élément <div class="adr"> et ses contenus.

== Références ==
=== Références Normatives ===
* [[hcard-fr|hCard]]

=== Références Informatives ===
* [http://www.ietf.org/rfc/rfc2426.txt vCard RFC2426] ([http://www.w3.org/2002/12/cal/rfc2426 HTML reformatted version of RFC2426])
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]

=== Travaux Similaires ===
* [[geo-fr|geo]]
* [[hcalendar-fr|hCalendar]]
* [[XOXO-fr|XOXO]]

== Chantier en cours ==
Cette spécification est un travail en cours. Au fur et à mesure que des aspects additionnels seront discutés, compris et écrits, ils seront ajoutés.

== Discussions ==

* Voir [http://www.technorati.com/cosmos/referer.html les blogs qui discutent de cette page].

=== Q&R ===
* Si vous avez quelque question à propos de hCard, regardez d'abord les [[hcard-faq-fr|FAQ hCard]] et si vous ne trouvez pas de réponses, ajoutez vos questions ! (Les chances sont celles que toute question '''adr''' s'appliquera tout aussi bien à [[hcard-fr|hCard]]).
* Voir aussi [http://microformats.org/discuss/ pour d'autres méthodes de feedback].

=== Problématiques ===
* SVP, ajoutez toutes les problématiques avec la spécification sur le document séparé [[hcard-issues-fr|problématiques hCard]]. Ditto.

== Pages en rapport ==
* {{adr-fr}}

voting-examples

2009-01-08T20:02:17Z

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

= Voting Examples =

== The Problem ==

There has been a good bit of discussion relating to how to represent the intent of a link from one site to another as an endorsement of that site or not. See Kevin Marks on voting ([http://epeus.blogspot.com/2003/03/vote-links.html Vote Links]) for initial arguments for a way to represent this information.

This page serves to document the current list of voting examples from real world sites for the design of a simple voting [[microformat]]. - [[User:SteveIvy|Steve Ivy]]

__TOC__

== Participants ==
* Kevin Marks
* Tantek Çelik
* Steve Ivy

== Related Pages ==
* [[voting-brainstorming]]

== Discussion/Concepts ==
(This may belong on a page of its own)
* [http://www.ashbykuhlman.net/blog/2002/09/06/0546 When is a link an endorsement?] - Nathan Ashby-Kuhlman
* [http://epeus.blogspot.com/2003/03/anti-links-linking-to-things-you.html Anti-links - linking to things you disagree with and saying so] - Kevin Marks
* [http://epeus.blogspot.com/2003/03/vote-links.html Vote Links] - Kevin Marks
* [http://jeremy.zawodny.com/blog/archives/000751.html PageRank is Dead] - Jeremy Zawodny

== Real-World Examples ==

=== Centralized Implementations ===
* [http://digg.com Digg] - Digg is essentially a centralized voting system for links. Digg users can "digg" (vote-for) a link. Links with more diggs float to the top of the popular lists, hence getting more exposure and getting more diggs/votes for and against. Markup is plain html - links and images. However, the semantics of a digg are still unclear - links often get many diggs though the majority of commenters disagree with the content of the linked page. Comments on links can also be voted for or against - 'digg' or 'bury'.
** Link and descriptions
** # of votes ('for' votes)
** controls to vote ('digg')
** controls to vote on comments ('digg' or 'bury')

* [http://www.urbandictionary.com Urban Dictionary] - dictionary of colloquialisms where users can vote up or down (for/against) terms in the dictionary. Markup is plain html - tables and images.
** Term and Definition
** # of votes 'up' and 'down'
** controls to vote ('up' or 'down')

* Google's [http://en.wikipedia.org/wiki/PageRank#PageRank_uses_links_as_.22votes.22 PageRank] - "In essence, Google interprets a link from page A to page B as a vote, by page A, for page B." Issues with PageRank's "any link is a good link" model are a major impetus to standardizing on a format for link-intention.
* [http://yro.slashdot.org/yro/07/01/04/1544210.shtml Slashdot] - users can give comments a [http://slashdot.org/faq/com-mod.shtml#cm700 karma] score which affects what comments are seen (comments can be filtered based on the score)
* [http://del.icio.us del.icio.us], [http://ma.gnolia.com/ ma.gnolia], [http://technorati.com/ Technorati favorites] - bookmarking sites that more or less represent a "for" vote

=== Vote Links ===
There are a few implementations based on the [[vote-links|VoteLinks microformat]] combined with other technologies:
* [http://www.artweb-design.de/articles/2006/06/05/distributed-votings-using-microformats Distributed votings using microformats] from Artweb Design
* [http://24ways.org/2006/boost-your-hyperlink-power Boost Your Hyperlink Power] - Jeremy Keith, using CSS to surface vote information

=== Example: Vote Links ===
(from: [[vote-links|VoteLinks microformat]])
<pre><nowiki>
<a rev="vote-for" href="http://ragingcow.blogspot.com"
title="neat spoof">Raging Cow</a>
<a rev="vote-against" href="http://ragingcow.com"
title="nasty corn syrup drink">Raging Cow</a>
</nowiki></pre>

== Existing Practices ==
* Most example sites, including Digg, UrbanDictionary.com, and Slashdot all use plain text labels or images for marking up their voting features.

== See Also ==
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML SE]
* [[vote-links]]
* [http://dbpubs.stanford.edu:8090/pub/1999-66 Stanford paper describing an early version of PageRank]

naming-principles

2009-01-08T05:00:18Z

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

<h1>Naming Principles</h1>
{{TOC-right}}
One of the key [[microformats]] [[principles]] is re-use, and in particular, re-use of names of objects, properties, and values from existing formats and standards when possible.

;<span id="Author">Author</span>
:[[User:Tantek|Tantek Çelik]]

== Introduction ==
One of the key [[microformats]] principles is re-use, and in particular, re-use of names of objects, properties, and values from existing formats and standards when possible. -Tantek

I explicitly created this principle in response to the anti-patterns that I saw in many (most?) existing standards efforts such as:

* Making up names from thin air
* Ignoring all earlier work
* Actual hostility towards using names/terms from other standards
* Using others' names to mean different things
* Using new names to mean the same thing
* Endlessly debating and "name-smithing" in order to come up with a slightly more perfect name

=== human nature ===
Perhaps it is human nature to want to create new names, or name new things. Certainly there is some amount of ego involved in the creation of a new thing which you can then claim to have invented or named. Some of these tendencies are also a form of "Not Invented Here" (NIH) syndrome which unfortunately is quite common among software engineers.

=== novelty hurts interoperability ===
Unfortunately such desire for novelty is bad for standards, and certainly bad for interoperability, which depends on being able to depend on the same name meaning the same thing. It's also bad for language and communication among humans. Even though humans can deal with some ambiguity and overloading of terms (using context to disambiguate), it's easier for humans as well when there is less ambiguity and less overloading.

=== documenting principles helps ===
We're not going to be able to fully eliminate such "Tower of Babel" tendencies, but at least we can minimize them, especially when they are bad for standards and interoperability.

With the experience of developing new microformats such as [[xfolk|xFolk]], [[hreview|hReview]], and [[hatom|hAtom]], it has become quite clear that we need to explicitly document some of the specific design principles that went into naming the objects and properties of some of the early established microformats like [[hcard|hCard]] and [[hcalendar|hCalendar]], and that's the purpose of this document.

== Naming Principles ==
=== Semantic XHTML Design Principles ===

First, it is important to note the naming principles which have been defined and explicitly referenced in (most of) the above-mentioned microformats.

{{semantic-xhtml-design-principles}}

=== Some Details ===

* '''hyphen-separated-lowercase-words'''. [http://w3.org/ W3C] [http://w3.org/Style/CSS/ CSS] (cascading style sheets) introduced the convention of lowercasing all property/value names (identifiers) and separating words with hyphen"-" characters for reasons of better human readability as compared to other approaches like CamelCase (or even camelCase). Microformats property names strictly adopt this approach as well.

=== Unique Root Class Names ===

I've also written a bit about the design principles that went into the *root* class names (which require a bit different treatment than property class names) in the microformats, but this is described in the hcard-parsing page currently:

http://microformats.org/wiki/hcard-parsing#root_class_name

Need to copy some of that text here and make it not-hCard specific.

=== Minimal Vocabulary ===

This is one of two additional key principles that I think I need to outline in more detail. The [[principle]] of "[[minimal vocabulary]]" is actually directly derived from the principle of [[solve-simpler-problems-first|start as simple as possible]].

* minimal vocabulary. We try to introduce as few new microformat terms as possible.

=== Reuse ===

Reuse microformats first, other standards second.

This is actually outlined quite clearly in the [[principles|microformats principles]], but deserves both explicit repeating here with <strong>strong emphasis</strong>:

* reuse building blocks from widely adopted standards
** semantic (http://tantek.com/presentations/20040928sdforumws/semantic-xhtml.html), meaningful (X)HTML (http://tantek.com/presentations/2005/03/elementsofxhtml). See SemanticXHTMLDesignPrinciples for more details.
** <strong>existing microformats</strong>
** <strong>well established schemas from interoperable RFCs</strong>

The key here is that this principle is not only about reusing whole microformats (e.g. don't invent a new person property for your microformat, just reuse [[hcard|hCard]]), but also about where to get names for properties.

In particular, if you find that your new microformat has a property which means the same thing as an exsiting microformat, you SHOULD (maybe I should make this a MUST) reuse the class name from that existing microformat. This practice also follows the principle of minimal vocabulary, and of re-using the same name to mean the same thing (instead of using two names to mean the same thing).

==== For Other Standards, Prefer Older to Newer ====

If there is no microformat name for a property, and we are reusing names based upon research of existing formats, then often there is more than one format with more than one name for the particular concept.

Often times new standards are developed which (most often) needlessly rename names from older standards. Thus to repair such naming drift, all other things being equal (e.g. both standards have been widely interoperably implemented), we prefer the older name over the newer name.

== Examples of Following the Naming Principles ==

We've followed these naming principles from the start, and made changes to microformats in development as a result. For example, [[xfolk|xFolk]] was changed from v0.4 to v1RC. xFolk dropped the new class name "extended" in preference for re-using the existing "description" class name. See [http://microformats.org/wiki/xfolk#Changes_since_xFolk_0.4 Changes since xFolk 0.4] for details.

== Naming Patterns Under Consideration as Principles ==

A few patterns have arisen in the naming of class names for microformats, and while these patterns are not conventions (yet), it may be worth considering them.

=== dt properties ===

So far, all datetime class names start with "dt", and all class names that start with "dt" are ISO8601 datetime properties. E.g.

* dtend - [[hcalendar|hCalendar]]
* dtstart - [[hcalendar|hCalendar]]
* dtreviewed - [[hreview|hReview]]

Note that "dt" is also [[rest/datatypes#Proposal|under consideration for type XOXO]].

Undefined: dtstamp - [[hcalendar|hCalendar]]

==== exceptions to dt prefix ====
However, some proposed/underdevelopment microformats currently have class names for datetime properties without the "dt" prefix:

Draft:
* rev - [[hcard|hCard]]
* bday - [[hcard|hCard]]

Proposed:
* updated - [[hatom|hAtom]]
* published - [[hatom|hAtom]]
* not yet named (date of authority) - [[species|Species]]

=== h word ===
So far, all uses of a single "h" prefix in a property name apply to (potential) root elements. But not all (potential) root elements start with "h" (which is ok).

E.g.:

* [[hatom]]
* hentry - [[hatom|hAtom]]
* [[hreview]]
* [[hlisting-proposal|hlisting]] (proposed)

Should we enforce the rule that only (potential) root elements may begin with an "h" prefix?

Non-h-prefixed root elements:
* vcard - [[hcard|hCard]]
* vcalendar - [[hcalendar|hCalendar]]
* vevent - [[hcalendar|hCalendar]]
* [[xfolk]]

== Anti-Patterns ==
Here are things ''not'' to do when creating names

=== Namespaces ===
Avoid namespaces (i.e. class names of ''microformat''-''key'']); read [[namespaces-considered-harmful]]. [[hatom|hAtom]] uses a limited amount of namespacing to [[hatom-faq#Why_does_hAtom_use_class_name_namespaces|exactly reuse a particular semantic]] from the Atom spec.

==Issues==
* Shouldn't '''brevity''' be a consideration? Not to the point of loosing meanings ('''class="b"''') but to prevent needless verbosity ('''class="thing-that-we-have-no-short-name-for"'''). More prgmatically, abreviations should be meaningful and appropriate (e.g. '''var''' for '''variety''' as used in botanical naming) - Andy Mabbett

== See Also ==
* [[existing-classes]] for class names already in use
* [[class-design-pattern]] to see how class names are used in microformats
* [[semantic-xhtml-design-principles]]
* [[naming-conventions]] for microformats.org wiki pages

User talk:TekeTen

2009-01-08T00:17:22Z

RyanKing: Reverted edits by TrocdRondr (Talk) to last version by AndyMabbett

Ongi etorri!

{{welcome}}

:[[User:AndyMabbett|Andy Mabbett]] 03:50, 4 May 2007 (PDT)

geo-issues

2009-01-08T00:17:11Z

RyanKing: Reverted edits by RocnaElvia (Talk) to last version by AndyMabbett

#REDIRECT:[[hcard-issues]]

presentational-html

2009-01-07T20:12:21Z

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

<h1> Presentational (X)HTML </h1>
{{TOC-right}}
Presentational (X)HTML refers to:
# The presentational elements and attributes of (X)HTML (as opposed to the [[semantic-html|semantic HTML]] elements and attributes)
# (X)HTML documents that are written using presentational (X)HTML.
# The practice of writing presentational (X)HTML

== Contributors ==
* [http://tantek.com/ Tantek]

== Presentational Elements ==

Presentational elements sensu lato can be divided into two groups. "Deliberate" presentational elements (b, i, small, …) have no semantic meaning and were deliberately designed/created for presentational purposes. "Abused" presentational elements (table, blockquote, …) have a semantic meaning, but are abused because of their default appearance in browsers (the blockquote element could be used for indenting text, for example).

=== Deliberate ===
Deprecated:
* basefont
* center
* font
* hr
* s
* strike
* tt
* u

Frames:
* frame
* frameset
* iframe

Strict but mostly presentational:
* b
* br (when used for spacing, or when used inappropriately where a div or p would have been semantically correct)
* big
* i
* small
* sub
* sup

=== Abused ===

* blockquote (when used for indenting text)
* table (when used for layout)

== Presentational Attributes ==
(This list is incomplete, please add!)
* align
* alink
* bgcolor
* color
* face
* height
* link (on body)
* size (on font element)
* valign
* vlink
* width

== See also ==
* [[POSH]]
* [[semantic-html]]

== References ==
* [http://w3.org/TR/xhtml1 XHTML 1.0]
* [http://w3.org/TR/html401 HTML 4.01]

User:ErinCaton

2009-01-07T20:12:11Z

RyanKing: Reverted edits by BasacEllaa (Talk) to last version by ErinCaton

I am a general web geek with a love of research and documentation. I'm hoping to help out with making the information on the site more accessible to newbies.

*[http://erincaton.ca/ My professional site] is currently being vamped up.

*[[pocket-cheat-sheet|I made a folding cheat sheet]]([http://erincaton.ca/media/cheatsheetHandout.pdf PDF]) but I'm not entirely certain it's correct as I'm just learning microformats.

Microformats

2009-01-07T17:56:03Z

RyanKing: Reverted edits by CaeltZelze (Talk) to last version by RyanKing

#REDIRECT [[microformats]]

User:Kwilson

2009-01-07T17:55:53Z

RyanKing: Reverted edits by BocdeLzelv (Talk) to last version by Kwilson

== Kenn Wilson ==

Linux sysadmin and web geek in San Francisco.

== External Links ==

* [http://www.inmostlight.org/ Personal site] (includes hCard)
* [http://www.corvidworks.com/ Professional site] (includes hCard and hResume)

internet-explorer-extensions

2009-01-07T17:55:43Z

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

<h1>Internet Explorer extensions</h1>

A list of extensions for the [http://microsoft.com/ie/ Microsoft Internet Explorer web browser] (IE), which detect or extract microformats.

[[Oomph]]: A Microformats Toolkit includes an [http://www.codeplex.com/Oomph/Release/ProjectReleases.aspx?ReleaseId=18505 Internet Explorer Add-On] that detects and processes microformats in web pages. The Add-On and associated tools are created by Microsoft and maintained as [http://www.codeplex.com/Oomph an open-source project] (Ms-Pl) with community submissions.

== Bookmarklets ==

For now see [[bookmarklets]] (AKA [[favelets]]).

== Related ==

The [[implementations#Maxthon|Maxthon Browser]] also runs on Microsoft Windows, and has a plugin for detecting and acting upon microformats in web pages. See the [[implementations#Maxthon|Maxthon entry]] on the [[implementations]] page for more details.

implementation-guidelines

2009-01-07T17:55:26Z

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

=Guidelines and Strategies for Implementing Microformats=

'''NEEDS CLEANUP'''

This pages needs some clean up and re-organization in order to be useful as "guidelines" to implementers.

For now, this page currently contains a semi-random bunch of implementation thoughts.

If you are an implementer, feel free to jump in and help clean it up.

Thanks,

Tantek

__TOC__

==Publishers==

* Embedding in XHTML documents is the easiest thing to do with microformats.
* Microformats can be embedded in Atom entries:
<pre>
<entry>
<title>Review of Some Object</title>
<link href="http://microformats.org/wiki/" />
<id>urn:uuid:1225c695-cfb8-4ebb-aaaa-80da344efa6a</id>
<updated>20050730T1900-0700</updated>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<div class="hreview">
<h3 class="summary"><span class="item fn">Some Object</span> Being Reviewed</h4>
<p>Reviewer: <span class="reviewer fn">author name</span> -
<abbr class="dtreviewed" title="20050730T1900-0700">July 30, 2005</abbr></p>
<blockquote class="description"><p>The review content</p></blockquote>
<span><span class="rating">5</span> out of 5</span>
</div>
</div>
</content>
</entry>
</pre>

Questions:

* Should an XMDP profile be linked to the Atom entry?
* Should the hreview class appear in the content container div?

==Identification==

There are several user agent identification strategies. Currently, Firefox provides strong support for XPath based discovery methods. Some of these can be adapted to Internet Explorer 6 with a small loss in efficiency and others not at all. The following examples are in extreme summary form. It is suggested that you click through on the links for more explanation.

===Firefox/Mozilla Strategies===

The simplest method is just to use an XPath expression to identify the microformat. Here is an example that does just that:
<pre>
var allDivs, thisDiv;

allDivs = document.evaluate(
"//*[contains(@class, 'xfolkentry')]",
document,
null,
XPathResult.UNORDERED_NODE_SNAPSHOT_TYPE,
null);

// Just run through all elements matched by the XPATH expression and change
// the background color to an attractive red.
for (var i = 0; i < allDivs.snapshotLength; i++) {
thisDiv = allDivs.snapshotItem(i);
// do something here. For example, change the background color to red.
thisDiv.style.backgroundColor = 'red';
}
</pre>

A greasemonkey script that applies this strategy to [http://de.lirio.us de.lirio.us] and an [http://thecommunityengine.com/webcites/ individual linkblog republished from del.icio.us] is available [http://thecommunityengine.com/resources/xfolk-colorize.user.js here] with a tutorial on how the script works and how to modify it for other microformats [http://thecommunityengine.com/home/archives/2005/07/greasemonkey_mi.html here]. Alf Eaton uses this exact XPath strategy in an early [http://hublog.hubmed.org/archives/001149.html script] that he created for [[hreview]].

However, as Alf Eaton also notes, the XPath-only strategy is subject to potential collisions where the class value that denotes the microformat's container element is contained in another class value. For example 'xfolkentry' is contained in 'mixfolkentry', and the XPath expression would identify both as an [[xfolk]] entry. While the danger of this particular collision occurring are slight, such may not be the case with other microformats.

To avoid collisions in microformat container values, Alf proposes an amendment to the above strategy that works well for microformats where the container element is identified by a class value. Alf's strategy is contained in the following code pattern (that does not run as is):
<pre>
var mf = 'hreview';

var micropath = "//*[contains(@class,'" + mf + "')]";
var micromatch = new RegExp('\\b' + mf + '\\b');

var mc = document.evaluate(micropath, document, null,
XPathResult.ORDERED_NODE_SNAPSHOT_TYPE, null);
for (var i = 0; i < mc.snapshotLength; i++) {
iNode = mc.snapshotItem(i);
if (iNode.className.match(micromatch))
doSomething();
}
</pre>
Note that this solution introduces regular expression checking as a second test on the nodes isolated by the XPath expression. Modifying the first example to use this strategy in a bit of code that is runnable we get:
<pre>
var allDivs, thisDiv;
var mf = 'xfolkentry';

var micropath = "//*[contains(@class,'" + mf + "')]";
var micromatch = new RegExp('\\b' + mf + '\\b');

allDivs = document.evaluate(
micropath,
document,
null,
XPathResult.UNORDERED_NODE_SNAPSHOT_TYPE,
null);

for (var i = 0; i < allDivs.snapshotLength; i++) {
thisDiv = allDivs.snapshotItem(i);
// do something here. For example, change the background color to red.
if (iNode.className.match(micromatch)) // apply the second test
thisDiv.style.backgroundColor = 'red';
}
</pre>

===Internet Explorer Strategies===

XPath-based strategies can be made to work sometimes in Internet Explorer with [http://glazkov.com/2004/04/06/xpath-unleashed/ Dimitri Glazkov's javascript library] that harnesses IE's built-in XPath support for traversing HTML DOM.

== Parsing ==

Parsing Microformats can be as easy or as hard as you want it to be. Since many of the elementary building blocks are based on anchor tags, its possible possible to implement some fairly effective functionality without needing to mess around with the complexities of tag nesting and unknown class names. Simple rule: ignore anything you don't need.

=== hCard ===

see: [http://microformats.org/wiki/hcard-parsing hCard Parsing]

== See Also ==

* [[xmdp-faq|XMDP FAQ]]

Microformats Wiki - User contributions [en]

mfbot

mfbot

mfbot

mfbot

mfbot

mfbot

mfbot

mfbot

mfbot

mfbot

mfbot

mfbot

User talk:JasonGarber

User:MarkLentczner

RyanKing

presentations

rest/opacity

microformats-fr

xoxo-fr

tagcloud-examples

events/2006-09-30-london-microformats-vevent

class

stable-pages

hcalendar-issues-fr

posh

xfolk-fr

Template:cheatsheets

User talk:DanielMorrison

User:HenrichPoehls

hproduct-feedback

hcalendar-implementations

2006-in-review

semantic-html

currency-examples-fr

hreview-issues

items-brainstorming

hatom-fr

hcard-implied-examples

User:AndyMabbett

adr-fr

voting-examples

naming-principles

User talk:TekeTen

geo-issues

presentational-html

User:ErinCaton

Microformats

User:Kwilson

internet-explorer-extensions

implementation-guidelines