http://microformats.org/wiki/api.php?action=feedcontributions&user=Aaronpk&feedformat=atomMicroformats Wiki - User contributions [en]2024-03-29T06:44:04ZUser contributionsMediaWiki 1.38.4http://microformats.org/wiki/index.php?title=irc&diff=70385irc2021-05-26T16:38:38Z<p>Aaronpk: updated instructions for libera.chat</p>
<hr />
<div>{{DISPLAYTITLE:#microformats on libera.chat}}<br />
{{TOC-right}}<br />
;shortURL<br />
:http://ufs.cc/w/irc<br />
<br />
== Quick Start ==<br />
You may use a IRC client application such as [http://colloquy.info/ Colloquy] (Mac or iOS) or [https://market.android.com/details?id=org.yaaic&feature=search_result Yaaic on Android] to join:<br />
* irc://irc.libera.chat/microformats<br />
<br />
<!--<br />
Alternatively you may use a browser to quickly join and chat:<br />
* http://webchat.freenode.net/?channels=microformats&nick=uf-wiki-visitor<br />
--><br />
<br />
<!--* Firefox users: install [https://addons.mozilla.org/en-US/firefox/addon/chatzilla/ Chatzilla] IRC plugin.<br />
As of 2020-12-15 this plugin no longer exists: "If you’ve followed a link from another site for an extension or theme, that item is no longer available." --><br />
<!--* http://leafychat.com/#microformats@irc.freenode.net<br />
** (Leafy Chat redirects to Convore and doesn't appear to connect as of 2011-07-06)--><br />
<br />
The microformats IRC channel is hosted on the libera.chat server. See [[irc#Joining_a_server_and_channel|Joining a server and channel]] help for further information and use of client applications which provide additional services (authenticated nicknames, logging, etc.).<br />
<br />
== Logs ==<br />
Recent logs of the Freenode #microformats IRC channel can be found at:<br />
* https://chat.indieweb.org/microformats<br />
* [http://logbot.glob.com.au/?c=freenode%23microformats&s=today logbot.glob.com.au microformats IRC Logs]<br />
<!--<br />
* [http://krijnhoetmer.nl/irc-logs/microformats krijnhoetmer microformats IRC Logs]<br />
<br />
If the krijnhoetmer logs have stopped logging or have any other problems:<br />
# try this in the IRC channel: <br/><kbd>/invite krijnh #microformats</kbd><br/> if you see <br/><samp>krijnh joined the chat room.</samp><br/> then the krijnhoetmer logs should start working again. if you don't see that, then:<br />
# go http://krijnhoetmer.nl/#contact<br />
# leave a message in the Contact box in the right column for Krijn, e.g. <blockquote><p>"looks like the logs at http://krijnhoetmer.nl/irc-logs/microformats have stopped working, could you take a look?"</p></blockquote><br />
# Krijn is fairly responsive, expect that logging will resume shortly.<br />
--><br />
Older logs can be found at the following locations for the following periods:<br />
* [https://chat.indieweb.org/microformats/2011-02-12 2011-02-12]–[https://chat.indieweb.org/microformats current] at https://chat.indieweb.org/microformats<br />
* [http://logbot.glob.com.au/?c=freenode%23microformats&s=20090220&e=20090220 2009-02-20] - [http://logbot.glob.com.au/?c=freenode%23microformats&s=today current] at [http://logbot.glob.com.au/?c=freenode%23microformats&s=today logbot.glob.com.au microformats IRC Logs]<br />
* [http://krijnhoetmer.nl/irc-logs/microformats/20131028 2013-10-28] (partial) - [http://krijnhoetmer.nl/irc-logs/microformats/ current] at [http://krijnhoetmer.nl/irc-logs/microformats krijnhoetmer microformats IRC Logs]<br />
----<br />
* [http://krijnhoetmer.nl/irc-logs/microformats/20130811 2013-08-11] (partial) - [http://krijnhoetmer.nl/irc-logs/microformats/20130917 2013-09-17] (partial) at [http://krijnhoetmer.nl/irc-logs/microformats krijnhoetmer microformats IRC Logs]<br />
* [http://krijnhoetmer.nl/irc-logs/microformats/20120726 2012-10-09] (partial) - [http://krijnhoetmer.nl/irc-logs/microformats/20130807 2013-08-07] at [http://krijnhoetmer.nl/irc-logs/microformats krijnhoetmer microformats IRC Logs]<br />
* [http://krijnhoetmer.nl/irc-logs/microformats/20120726 2012-07-26] - [http://krijnhoetmer.nl/irc-logs/microformats/20120916 2012-09-16] (partial) at [http://krijnhoetmer.nl/irc-logs/microformats krijnhoetmer microformats IRC Logs]<br />
* [http://krijnhoetmer.nl/irc-logs/microformats/20090220 2009-02-20] - [http://krijnhoetmer.nl/irc-logs/microformats/20120621 2012-06-21] (partial) at [http://krijnhoetmer.nl/irc-logs/microformats krijnhoetmer microformats IRC Logs]<br />
* [http://rbach.priv.at/Microformats/IRC/2011-04-05 2011-04-05] at [http://rbach.priv.at/Microformats-IRC/ rbach microformats IRC Logs]<br />
* [http://rbach.priv.at/Microformats/IRC/2011-02-24 2011-02-24] - [http://rbach.priv.at/Microformats/IRC/2011-03-03 2011-03-03] at [http://rbach.priv.at/Microformats-IRC/ rbach microformats IRC Logs]<br />
* [http://rbach.priv.at/Microformats/IRC/2009-08-28 2009-08-28] - [http://rbach.priv.at/Microformats/IRC/2010-09-27 2010-09-27] at [http://rbach.priv.at/Microformats-IRC/ rbach microformats IRC Logs]<br />
* [http://rbach.priv.at/Microformats/IRC/2009-03-26 2009-03-26] - [http://rbach.priv.at/Microformats/IRC/2009-06-29 2009-06-29] at [http://rbach.priv.at/Microformats-IRC/ rbach microformats IRC Logs]<br />
* 2009-02-09 - 2009-02-20 '''missing'''. if anyone has any logs for this time period, please upload them and add links here.<br />
* [http://rbach.priv.at/Microformats/IRC/2009-01-14 2009-01-14] - [http://rbach.priv.at/Microformats/IRC/2009-02-09 2009-02-09] at [http://rbach.priv.at/Microformats-IRC/ rbach microformats IRC Logs]<br />
* [http://krijnhoetmer.nl/irc-logs/microformats/20080825 2008-08-25] - [http://krijnhoetmer.nl/irc-logs/microformats/20090114 2009-01-14] at [http://krijnhoetmer.nl/irc-logs/microformats krijnhoetmer microformats IRC Logs]<br />
* 2008-08-16 - 2008-08-24 '''missing'''. if anyone has any logs for this time period, please upload them and add links here.<br />
* [http://rbach.priv.at/Microformats/IRC/2005-11-16 2005-11-16] - [http://rbach.priv.at/Microformats/IRC/2008-08-16 2008-08-16] at [http://rbach.priv.at/Microformats-IRC/ rbach microformats IRC Logs]<br />
<br />
Until sometime on 2007-07-16, there was an [http://microformat.makedatamakesense.com/log_feed/ atom feed] provided for the [http://rbach.priv.at/Microformats-IRC/ rbach IRC Logs]. <br />
<br />
=== logs status ===<br />
* [http://logbot.glob.com.au/?c=freenode%23microformats logbot.glob.com.au microformats IRC Logs] are current and live<br />
* [http://krijnhoetmer.nl/irc-logs/microformats krijnhoetmer microformats IRC Logs] appears to have stopped logging as of 2016-01.<br />
** I emailed and heard back from Krijn on 2016-03-19 "Yeah, sorry, I know, server resources are very low for that (old) machine. I think it's sort of EOL.." [http://logs.glob.uno/?c=freenode%23microformats&s=21+Mar+2016&e=21+Mar+2016&h=Krijn#c86411] -- gRegor<br />
* [http://rbach.priv.at/Microformats-IRC/ rbach IRC Logs] appear to have stopped logging as of 2009-06-29.<br />
<br />
== People on IRC ==<br />
See our [[irc-people|list of IRC regulars]] and their normal timezones.<br />
<br />
Our channel has regular admins, who are also mailing list and wiki admins. If you want to get their attention, just say "adminhelp".<br />
<br />
==Bots on IRC==<br />
The IRC channel uses these bots:<br />
* [[Loqi]] - logs IRC, posts notifications to IRC of wiki edits<br />
** If Loqi is missing, see https://indieweb.org/Loqi for instructions<br />
** If Wiki edits are missing, ask an admin for "adminhelp", and reference [[admin-how-to#irc]]<br />
<br />
=== Previous Bots ===<br />
These bots were active ~2005-2009? (actual dates can likely be confirmed by checking old IRC logs)<br />
* [[mfbot]] - logs all edits to this wiki. (Contact: [[User:RyanKing|Ryan King]])<br />
* [[mflogbot]] - logs the irc channel itself to archives on the web. (Contact: [[User:RobertBachmann|Robert Bachmann]])<br />
* [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot]<br />
<br />
==== Greeting Bot ====<br />
To display a brief description of who you are each time you join the channel, you can use “JiBot” to create a definition for your username. To do so pass the <tt>?def</tt> command using something like the following convention (be brief):<br />
<br />
<code>?def jdoe is John Doe and can be found online at <nowiki>http://www.example.com</nowiki></code><br />
<br />
More information about using JiBot commands can be found on the [http://joiwiki.ito.com/joiwiki/index.cgi?jibot jibot website]<br />
<br />
== Getting started with IRC ==<br />
'''Please note:''' These directions relate specifically to the services that [http://libera.chat/ Libera.chat] offers. Other IRC servers may differ with the services they offer and how to operate them. You can also read a complete guide at https://libera.chat/guides<br />
<br />
===Joining a server and channel===<br />
Most clients will offer you a connection dialogue showing the required fields for connection. The details to connect to the server are:<br />
<br />
*Server: <code>irc.libera.chat</code><br />
*Port: <code>6667</code> (usually default)<br />
<br />
You should also fill in any fields to set your alias, real name and email address. If available, save these settings for later to speed up connecting in future.<br />
<br />
More on setting a password protected alias can be [[irc#Creating_a_registered_nickname|read here]].<br />
<br />
Once connected, you will most likely be presented with the "MOTD" (message of the day). For the first visit, it is advisable to read this to find out about the server's policies and other important pieces of news and help, otherwise it can be ignored and you can either [[irc#Creating_a_registered_nickname|authenticate your alias]] or join a channel.<br />
<br />
Your client may display to you a listing of all available channels. Locate <code>#microformats</code> and select to join, or type <code>'''/join #microformats'''</code> into the command line available to you in your client (where you've just been shown your connection).<br />
<br />
Assuming you've connected correctly, you should now find youself in the microformats channel!<br />
<br />
More detailed, but general, advice can be [http://www.irchelp.org/irchelp/irctutorial.html#intro read here].<br />
<br />
===Creating a registered nickname===<br />
Registration means that a password becomes associated with your alias/nickname/sign-in name and from the point of registration authorisation is required to communicate using that alias.<br />
<br />
Registration of a nickname is required for some channels, and should be done to protect your identity.<br />
<br />
To register with [https://libera.chat Libera.chat], you must communicate with their service known as NickServ. The two basic command you will need to get started are:<br />
<br />
For registration: <code>/msg nickserv register ''password'' ''email''</code><br />
<br />
With <code>''password''</code> being a value of your choice. You must also associate an email address with your nickname<br />
<br />
Your client may offer you an option to set your alias and password, so that you will not have to manually enter this information on each join. Refer to your client's help files for more on this.<br />
<br />
These commands can be typed directly into the server window upon join, or whilst in a channel, just as you would normally send a message.<br />
<br />
More detailed user registration command information can be found in [https://libera.chat/guides/registration Libera's guides]<br />
<br />
===Communicating===<br />
Sending a message to a channel may be as simple as joining the channel and typing into the window, just as you would with an Instant Messenger. You can refer to your client's help files for quicker/alternative methods of doing the following. For all clients the following commands are available (the parts in bold must be used, but are not seen by others):<br />
<br />
'''Sending a message to the entire channel you are currently in:'''<br />
<br />
Command: <kbd>'''/msg''' Hello world!</kbd><br />
<br />
Result: <samp><Bill> Hello world!</samp><br />
<br />
'''Sending an action/emotive/3rd person statement:'''<br />
<br />
Command: <kbd>'''/me''' dances a code jig</kbd><br />
<br />
Result: <samp>Bill dances a code jig</samp><br />
<br />
'''Sending a message to one person only (private chat):'''<br />
<br />
Command: <kbd>'''/msg Bob''' Hi, would you like to code jig?</kbd><br />
<br />
Result (for Bob only): <samp><Bill> Hi, would you like to code jig?</samp><br />
<br />
==Clients==<br />
The following clients are recommended by #microformats participants:<br />
<br />
<!--<br />
=== Web ===<br />
* [http://leafychat.com/#microformats@irc.freenode.net Leafy Chat]<br />
--><br />
<br />
===Windows===<br />
* [http://www.mirc.com/ mIRC] — Popular Windows client. Trial version only.<br />
* [http://xchat.org/ X-Chat] — Popular cross-platform client. [http://www.silverex.org/download/ Free Windows version] available.<br />
* [http://www.adiirc.com/ AdiIRC] — Simple C# based IRC client.<br />
* [http://www.miranda-im.org/ Miranda] — Lightweight, muti-protocol instant messenger.<br />
<br />
=== Mac ===<br />
* [http://colloquy.info Colloquy] — open source, free<br />
* [http://homepage.mac.com/philrobin/conversation/ Conversation]<br />
* [http://sourceforge.net/projects/fire Fire] — open source, free<br />
* [http://www.conceitedsoftware.com/products/linkinus Linkinus]<br />
* [http://www.chipersoft.com/minerva/ Minerva]<br />
* [http://www.snak.com/ Snak]<br />
* [http://xchataqua.sourceforge.net/twiki/bin/view/Main/WebHome X-Chat Aqua]<br />
** now has [http://www.portableapps.org PortableApps] version &#8212; [http://www.macupdate.com/info.php/id/21685/portable-x-chat-aqua MacUpdate link]<br />
* [http://www.aquaticx.com/ Xirc]<br />
<br />
===Cross-platform===<br />
* [http://pidgin.im/ Pidgin] — Popular open-source multi-protocol windows client, using libpurple<br />
* [http://irssi.org/ Irssi] — Unix client, often run from a shell, sometimes [http://f0rked.com/articles/irssi in conjunction with 'screen'].<br />
* [http://jirc.hick.org/jirc/ jIRCii]<br />
<br />
== meetups ==<br />
The idea of having IRC meetups (a set time for a meeting on IRC) has been suggested by [[User:RyanKing|Ryan King]], as it appears to work well for the WordPress community and may help us from time-to-time. As of yet, there are no plans to have meetups.<br />
<br />
==IRC and microformats==<br />
=== hCard ===<br />
<div class="discussion"><br />
* ''How do we maintain info about ircing in our hCards (nick, network, fav-channels?)?''<br />
** presumably this would be done with a URL. - [[User:Tantek|Tantek]] 18:42, 30 July 2009 (UTC)<br />
</div><br />
<br />
== Related discussions ==<br />
* [[chat]] [[chat-examples|chat examples]], [[chat-formats|chat formats]], and [[chat-brainstorming|chat brainstorming]]<br />
<br />
==See also==<br />
*[[irc-meetups]]<br />
*[[discuss|Other discussion fora]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=spread-microformats&diff=70325spread-microformats2021-01-21T00:08:35Z<p>Aaronpk: /* Logo */</p>
<hr />
<div>{{DISPLAYTITLE:Spread Microformats}}<br />
<br />
Inspired by [http://spreadfirefox.com/ Spread Firefox], this page is for sharing community resources for marketing microformats such as [[buttons]], banners, wallpaper / desktop screens, logo graphics, [[stickers]], t-shirts etc.<br />
<br />
== Email ==<br />
* See [[advocacy-email-samples]] for some sample emails you can copy/customize and send to site owners to encourage them adopt microformats.<br />
<br />
== Wallpaper ==<br />
=== Wallpaper and desktop screens. ===<br />
* A [https://web.archive.org/web/20111128072549/http://remiprevost.com/images/wallpapers/microformats/ wallpaper] by [[User:Remi|Rémi Prévost]]<br />
<br />
== Logo ==<br />
https://indieweb.org/images/8/80/microformats-logo.png<br />
<br />
=== logo text ===<br />
https://web.archive.org/web/20110820103746/http://img.skitch.com/20090715-c3xmikadkj8udt4sq6aqfkqtac.png<br />
<br />
* The logo [https://web.archive.org/web/20151003234446/http://vault.simplebits.com/notebook/2005/06/22/microformats/ was designed by Dan Cederholm]<br />
* High-resolution [http://vault.simplebits.com/bits/microformats/microformats-logo.eps EPS] and [http://vault.simplebits.com/bits/microformats/microformats-logo.png transparent PNG] versions of the microformats logo text by [[User:DanCederholm|Dan Cederholm]].<br />
* the microformats typeface is [https://www.emigre.com/Fonts/Solex Solex Medium] by Emigre.<br />
<br />
=== logo mark ===<br />
* An [https://web.archive.org/web/20111128072549/http://remiprevost.com/images/wallpapers/microformats/mf-vector.svg SVG] and [https://web.archive.org/web/20111128072549/http://remiprevost.com/images/wallpapers/microformats/mf-vector.png PNG] (for Fireworks) version, by [[User:Remi|Rémi Prévost]]. Released under [https://creativecommons.org/licenses/by-nc-sa/3.0/ CC BY-NC-SA].<br />
* An [https://github.com/btrem/microformats/blob/master/logos/microformats.svg SVG] version (and alternative [https://github.com/btrem/microformats/blob/master/logos/microformats-orange.svg orange colour]) by [https://btrem.com Brian Tremblay]. Released under [https://creativecommons.org/publicdomain/zero/1.0/ CC0 1.0 Universal (CC0 1.0) Public Domain Dedication].<br />
** Also available (slightly modified) [https://github.com/edent/SuperTinyIcons/pull/442 as part of] the [https://github.com/edent/SuperTinyIcons Super Tiny Web Icons collection]. Released under [https://github.com/edent/SuperTinyIcons/blob/e6ea45f6441bd0111295b2713df73c1502de6ec5/LICENSE MIT License].<br />
<br />
== POSH ==<br />
* [[posh|POSH]] logos and buttons<br />
<br />
== stickers ==<br />
See the [[stickers]] page to easily order a set of moo microformats stickers!<br />
<br />
== T-Shirts ==<br />
* See [http://flickr.com/photos/tags/microformatstshirt photos of microformats tshirts on Flickr] (the [http://flickr.com/photos/tags/microformatstshirt/clusters/ clusters] are especially fun)<br />
** Note also [http://pixelsebi.com/2006-10-26/microformats-t-shirt-in-second-life/ microformats t-shirt in Second Life]<br />
=== do it yourself tshirts ===<br />
[[User:TheJbf|Burcu Dogan]] has made her own microformats t-shirt:<br />
<br />
http://web.archive.org/web/20120528054541if_/http://i44.tinypic.com/2s01i1j.jpg<br />
<br />
For those who are not able to find a microformats t-shirt, it is possible to make one at home less than an hour. The requirements for such a pressing process are listed below:<br />
* A high quality microformats logo (which can be found below the '''Logo headline''' on this page)<br />
* A black t-shirt<br />
* An iron-on transfer paper for '''dark t-shirts''' (note that printers doesn't print white, so there're special papers to print white on dark)<br />
* An iron an a hard surface. (Ironing press with a large surface is highly recommended.)<br />
* A laser printer<br />
* Sharp and sensitive scissors<br />
* Non-metalic heat resisting papers<br />
<br />
('''Warning:''' Take the instructions on the transfer paper you bought as the first reference, we're not responsible for unsuccessful attempts. Tips about pressing can change from paper to paper.)<br />
<br />
Firstly, you need to print the logo on the transfer paper. Transfer papers for dark t-shirts are sticky backed white papers which vary in size. You need to decide which size you want to press on your t-shirt. A4 and A3 are suitable for microformats t-shirts.<br />
<br />
Print the logo with a black background. The result of the paper printed should look like this: <br />
<br />
http://web.archive.org/web/20120528052329if_/http://i40.tinypic.com/2ylqqmb.jpg<br />
<br />
(You can, of course decrease, the amount of background area to save ink)<br />
<br />
Now it is time to separate logo from the background. Carefully clip the edges and get the logo all alone. White borders should stay with the green layers, don't make a mistake by clipping them out.<br />
<br />
Prepare the iron press, you will need the highest temperature with no stream to transfer successfully. Give your press at least 10 minutes to heat fully. While the iron is heating, decide which position your logo should appear. Use a ruler to check if the logo is positioned symmetrically.<br />
<br />
http://web.archive.org/web/20120528061614if_/http://i41.tinypic.com/2v334pc.png<br />
<br />
If your iron press is heated, gently peel the tiny paper on the back of the transfer paper to make it sticky. Place it on the t-shirt and put 1 or 2 non-metalic heat resisting paper of any kind on the logo. Be sure that transfer paper doesn't overlap.<br />
<br />
http://web.archive.org/web/20120601000105if_/http://i40.tinypic.com/kcl7gk.png<br />
<br />
Press the iron for 10-15 seconds. This actually depends on the paper you are using, so it is best to follow the instructions on the iron-on transfer paper you purchased. If necessary repress the iron on the whole surface for 5-10 seconds again. <br />
<br />
And, you made a new microformats t-shirt! Don't forget to take a picture and share.<br />
<br />
Note that you should hand wash your t-shirt and iron it from back carefully. Don't forget that it is also possible to use another fabrics such as bags to print microformats logos. We're waiting for your creations.<br />
<br />
== External online community resources ==<br />
<br />
=== Video ===<br />
* See [http://www.youtube.com/results?search_query=microformats videos of microformats on YouTube] or [http://vimeo.com/groups/microformats Vimeo], in particular, a [http://www.youtube.com/watch?v=UAV4SGpPuQI video of a microformats tshirt] ([http://www.flickr.com/photos/fumi/372068162/ photo]).<br />
<br />
===Social networking===<br />
Groups for fans and advocates of microformats to join or follow:<!--listed alphabetically--><br />
* [http://www.facebook.com/microformats Facebook microformats fan page]<br />
* [http://www.facebook.com/group.php?gid=2374732285 Facebook microformats group]<br />
* [http://flickr.com/groups/microformats/ Flickr microformats group]<br />
* [http://getsatisfaction.com/microformats microformats on Satisfaction]<br />
* [http://twitter.com/microformats microformats on Twitter].<br />
<br />
=== wiki-communities ===<br />
* [http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Microformats Wikipedia: Project Microformats]<br />
**[http://ko.wikipedia.org/wiki/%EC%9C%84%ED%82%A4%EB%B0%B1%EA%B3%BC:%EC%9C%84%ED%82%A4%ED%94%84%EB%A1%9C%EC%A0%9D%ED%8A%B8_%EB%A7%88%EC%9D%B4%ED%81%AC%EB%A1%9C%ED%8F%AC%EB%A7%B7 -" - in Korean]<br />
**[http://zh.wikipedia.org/wiki/Wikipedia:%E5%B0%88%E9%A1%8C/%E5%BE%AE%E6%A0%BC%E5%BC%8F -" - in Chinese]<br />
* [http://www.usemod.com/cgi-bin/mb.pl?MicroFormats meatball:microformats] -- a first page (stub to be reviewed) dedicated to have any review/opinion from the meatballers especially on the wiki-formats.<br />
* [http://communitywiki.org/fr/MicroFormats communitywiki:microformats] -- an old multilingual page with a blockcodemachine proposal.<br />
<br />
== See Also ==<br />
* [[advocacy]]<br />
* [[buttons]]<br />
* [[podcasts]]<br />
* [[presentations]]<br />
* [[press]]<br />
* [[2d_barcodes]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=h-recipe&diff=70224h-recipe2020-07-27T20:31:23Z<p>Aaronpk: /* Examples in the Wild */</p>
<hr />
<div>{{DISPLAYTITLE:h-recipe}}<br />
<span class="h-card vcard"><span class="p-name fn">[[User:Tantek|Tantek Çelik]]</span> (<span class="p-role role">Editor</span>)</span><br />
----<br />
<dfn style="font-style:normal;font-weight:bold">h-recipe</dfn> is a simple, open format for publishing recipes on the web. h-recipe is one of several open [[microformats|microformat]] draft standards suitable for embedding data in HTML.<br />
<br />
h-recipe is the [[microformats2]] update to [[hRecipe]].<br />
<br />
{{cc0-owfa-license}}<br />
<br />
== Example ==<br />
Here is a simple minimal recipe example:<br />
<br />
<source lang=html4strict><br />
<article class="h-recipe"><br />
<h1 class="p-name">Bagels</h1><br />
<br />
<ul><br />
<li class="p-ingredient">Flour</li><br />
<li class="p-ingredient">Sugar</li><br />
<li class="p-ingredient">Yeast</li><br />
</ul><br />
<br />
<p>Takes <time class="dt-duration" datetime="1H">1 hour</time>,<br />
serves <data class="p-yield" value="4">four people</data>.</p><br />
<br />
<div class="e-instructions"><br />
<ol><br />
<li>Start by mixing all the ingredients together.</li><br />
</ol><br />
</div><br />
</article><br />
</source><br />
<br />
Parsed JSON:<br />
<source lang=javascript><br />
{<br />
"items": [<br />
{<br />
"type": [<br />
"h-recipe"<br />
],<br />
"properties": {<br />
"name": [<br />
"Bagels"<br />
],<br />
"ingredient": [<br />
"Flour",<br />
"Sugar",<br />
"Yeast"<br />
],<br />
"yield": [<br />
"4"<br />
],<br />
"instructions": [<br />
{<br />
"value": "Start by mixing all the ingredients together.",<br />
"html": "<ol> <li>Start by mixing all the ingredients together.</li> </ol>"<br />
}<br />
]<br />
}<br />
}<br />
]<br />
}<br />
</source><br />
<br />
=== Get started ===<br />
The class '''<code>h-recipe</code>''' is a ''root class name'' that indicates the presence of an h-recipe.<br />
<br />
'''p-name''', '''e-instructions''', '''p-ingredient''' and the other property classnames listed below define elements as ''properties'' of the h-recipe.<br />
<br />
See [[microformats-2-parsing]] to learn more about property classnames.<br />
<br />
== Properties ==<br />
h-recipe properties, inside an element with class '''h-recipe''':<br />
* '''<code>p-name</code>''' - the name of the recipe<br />
* '''<code>p-ingredient</code>''' - describes one or more ingredients used in the recipe.<br />
* '''<code>p-yield</code>''' - Specifies the quantity produced by the recipe, like how many persons it satisfyies <br />
* '''<code>e-instructions</code>''' - the method of the recipe.<br />
* '''<code>dt-duration</code>''' - the time it takes to prepare the meal described by the recipe.<br />
* '''<code>u-photo</code>''' - an accompanying image<br />
<br />
Experimental properties with wide adoption<br />
* '''<code>p-summary</code>''' - provides a short summary or introduction <br />
* '''<code>p-author</code>''' - person who wrote the recipe, optionally embedded with <code>h-card</code> {{main|h-card}}<br />
* '''<code>dt-published</code>''' - the date the recipe was published<br />
* '''<code>p-nutrition</code>''' - nutritional information like calories, fat, dietary fiber etc.<br />
* '''<code>p-category</code>''' - recipe categories/tags<br />
* ...<br />
<br />
<br />
== Status ==<br />
<br />
'''h-recipe''' is a microformats.org draft specification. Public discussion on h-recipe takes place on [[h-recipe-feedback]] and the #microformats [[irc]] channel on irc.freenode.net.<br />
<br />
h-recipe is ready to use and implemented in the wild, but for backwards compatibility you should also mark h-recipes up with classic [[hRecipe]] classnames.<br />
<br />
== Property Details ==<br />
<br />
(stub, add any property explanations here)<br />
<br />
'''dt-duration''' should be marked up using the [http://developers.whatwg.org/common-microsyntaxes.html#durations duration] microsyntax defined in HTML5. TODO: add more examples<br />
<br />
[[hRecipe]] has a number of experimental properties which have real world adoption due to [[Google]] recipe search support of hRecipe. These are: summary, author, published and nutrition.<br />
<br />
== Examples in the Wild ==<br />
* [http://www.eliduke.com Eli Duke] has posted some h-[http://www.eliduke.com/recipes recipes] on his site:<br />
** http://www.eliduke.com/recipes/kale-salad<br />
** http://www.eliduke.com/recipes/hummus<br />
** http://www.eliduke.com/recipes/wacky-cake<br />
** http://www.eliduke.com/recipes/vegan-mac-and-cheese<br />
<br />
* [https://cleverdevil.io Jonathan LaCour] has created several h-[http://cleverdevil.io/content/recipes recipes] using his Known plugin on his site:<br />
** https://cleverdevil.io/2015/kentucky-maid-cocktail<br />
<br />
* [https://makeitperfectly.com Perfect Company] marks up their recipes with h-recipe:<br />
** https://makeitperfectly.com/drink/recipes/1a1913f6-6ba2-11e5-a3ed-f372faffcfa4<br />
** https://makeitperfectly.com/bake/recipes/194a6cea-6ba2-11e5-a3ed-8367b69ac326<br />
<br />
* [https://aaronparecki.com/recipes Aaron Parecki] has several recipes on his website<br />
** https://aaronparecki.com/2020/06/01/19/banana-bread<br />
** https://aaronparecki.com/2018/12/25/8/habanero-sauce<br />
<br />
== Validating ==<br />
{{h-spec-section-validating}}<br />
<br />
== Implementations ==<br />
This section is '''informative'''. <br />
<br />
Tools for generating and consuming h-recipe. When it gets too big we can move it to a separate page like [[h-recipe-implementations]].<br />
<br />
Consuming h-recipe (sites and tools that consume and do something with h-recipe)<br />
* [https://developers.pinterest.com/docs/rich-pins/recipes/ Pinterest] supports h-recipe to create "rich pins"<br />
* ... (stub)<br />
<br />
Generating h-recipe (sites and tools that help produce and publish h-recipe)<br />
* [https://github.com/cleverdevil/Known-Recipes Recipe post generator for Known CMS] by [https://cleverdevil.io Jonathan LaCour].<br />
<br />
Advocacy - open source and other implementations which would benefit from h-recipe support or some degree of support has been requested - feel free to help implement these.<br />
* OpenRecipes [https://github.com/fictivekin/openrecipes/issues/198 issue 198] feature request: update spider to parse for the original hRecipe microformat, and the new h-recipe microformats2 update<br />
<br />
== Backward Compatibility ==<br />
=== Publisher Compatibility ===<br />
(stub)<br />
=== Parser Compatibility ===<br />
Microformats parsers {{should}} detect classic properties only if a classic root class name is found and parse them as microformats2 properties. <br />
<br />
If an "h-recipe" is found, don't look for an "hrecipe" on the same element.<br />
<br />
compat root class name: <code id="hrecipe">hrecipe</code><br/><br />
properties: (parsed as '''p-''' plain text unless otherwise specified)<br />
* <code>fn</code> - parse as '''<code>p-name</code>'''<br />
* <code>ingredient</code><br />
* <code>yield</code><br />
* <code>instructions</code> - parse as '''e-'''<br />
* <code>duration</code> - parse as '''dt-'''<br />
* <code>photo</code> - parse as '''u-'''<br />
* <code>summary</code><br />
* <code>author</code> - including compat root <code>vcard</code> in the absence of <code>h-card</code><br />
* <code>nutrition</code><br />
* <code>category</code><br />
* <code>rel=tag</code> - parse as '''<code>p-category</code>'''. While not a class name nor typical microformats property, rel=tag was the typical way to tag an hrecipe. Thus parsers should look for rel=tag hyperlinks inside an hrecipe, and take the last path segment of their "href" value as a value for a '''<code>p-category</code>''' property.<br />
<br />
== Background ==<br />
h-recipe is based on the existing [[hRecipe]] specification.<br />
<br />
== See Also ==<br />
<br />
* [[h-recipe-feedback]]<br />
* [[microformats-2]]<br />
* [[h-card]] can be embedded in h-recipe<br />
* [[hRecipe]] is the classic microformat replaced by h-recipe<br />
<br />
[[Category:Draft Specifications]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=admin-to-do&diff=70222admin-to-do2020-07-19T17:29:25Z<p>Aaronpk: </p>
<hr />
<div>{{DISPLAYTITLE:admin to-do}}<br />
Filtered and processed [[to-do]] items specifically for [[admins]].<br />
<br />
Only [[admins]] should edit this page with non-minor edits.<br />
<br />
Please add to-do suggestions for admins to the general [[to-do#Admins|to-do page's Admins section]]. Thanks!<br />
<br />
Items here may list who originally suggested the item on the [[to-do]] page.<br />
<br />
Related: [[admin-how-to]].<br />
<br />
== inbox ==<br />
Per GTD, here are inbox items that seem reasonable and thus have been moved here by admins from the [[to-do#Admins|to-do page's Admins section]].<br />
<br />
Mirror server requests:<br />
* Note that requests from 88.190.13.197 are for a mirror server run by [[User:Neuro|neuro]] at 88.190.224.126.<br />
* ...<br />
<br />
== next actions and projects ==<br />
Per GTD, here are processed next-actions for admins, grouped by area/project<br />
<br />
* [[events/2008-03-10-sxsw-admins-meetup#next_actions|next-actions from 2008-03-10 sxsw admins meetup]]<br />
** noted here for tracking purposes.<br />
*** This was a very long time ago - we need to reprocess this item to see what is still relevant >5 years later! - [[User:Tantek|Tantek]] 13:33, 15 September 2013 (UTC)<br />
<br />
<br />
=== irc ===<br />
* Pibb integration for the #microformats IRC channel. It is relatively simple to [http://janrain.com/blog/2007/08/08/how-to-embed-pibb/ embed the Pibb chat widget] into a webpage that bridges to the #microformats IRC channel. This would allow for greater access and transparency to the IRC discussions as well as allow people to participate using only their web browser. [[User:Chris_Messina]] 16:50, 31 Aug 2007 (PDT)<br />
<br />
* maintainer for [[mfbot]]. Ryan King has indicated that he no longer has time to maintain [[mfbot]] and would like another admin to pick up the maintenance and running of mfbot.<br />
<br />
* The https://indieweb.org/discuss options and Loqi cover these needs currently. [[User:GRegorLove|gRegor]] 19:43, 9 May 2017 (UTC)<br />
<br />
=== web site ===<br />
==== home page ====<br />
Main site home page:<br />
* The microformats2 page, should also be referred from the main page of the website http://microformats.org/ like perhaps a new small right box in between "What are microformats?" and "Microformat specifications" saying something like "Microformat version" as a title and place both versions, the old one is the latest with a short description, and the new one should be imediately under the title, with the same description below.<br />
** +1 agreed. We need a home page redesign with at least this, maybe also @microformats tweets. [[User:Tantek|Tantek]] 13:32, 15 September 2013 (UTC)<br />
<br />
ex: [http://screencast.com/t/77YHGASumqm Homepage with the right box implemented] .<br />
<br />
==== blog ====<br />
* Update Blog-Theme to support [[microformats2]]: Publish the microformats theme on GitHub to enable community contributions. See IRC discussion: <nowiki>https://chat.indieweb.org/microformats/2018-06-28#t1530196357894800</nowiki>.<br />
** Todo: Publish all theme sources on GitHub: <nowiki>https://chat.indieweb.org/microformats/2018-06-28/1530198611202600</nowiki><br />
<br />
=== wiki ===<br />
==== proper redirects to avoid dupes ====<br />
Wiki area suggestion:<br />
*Wiki creates duplicate content by allowing duplicate pages for microformats2: the main one is http://microformats.org/wiki/microformats2 and the other one is http://microformats.org/wiki/microformats-2 .<br />
<br />
To eliminate this problem, the 2nd page http://microformats.org/wiki/microformats-2, in the <head> section of the source code, should contain the following line <link rel="canonical" href="http://microformats.org/wiki/microformats2" />. This will tell Search Engines that this page is a duplicate content, thus it won't be indexed.<br />
<br />
This implementation should be done on all other duplicate content pages of the website.<br />
<br />
* This sounds like a good request. Is there a MediaWiki extension/plugin for adding rel=canonical to redirect handling pages? - [[User:Tantek|Tantek]] 13:32, 15 September 2013 (UTC)<br />
** MediaWiki has a config for this as of v1.21.0. Reference: <nowiki>https://www.mediawiki.org/wiki/Manual:$wgEnableCanonicalServerLink</nowiki> [[User:GRegorLove|gRegor]] 01:14, 21 June 2018 (UTC)<br />
** IIRC new MediaWiki has an option to do real redirects as well [[User:Aaronpk|Aaronpk]] 18:27, 15 February 2019 (UTC)<br />
<br />
==== for site update to microformats2 ====<br />
* about<br />
** create [[about]] from updated version of http://microformats.org/about<br />
** change "about" link to /wiki/about<br />
<br />
* get-started<br />
** update [[get-started]] with info from http://microformats.org/2014/03/05/getting-started-with-microformats2<br />
<br />
===== update wiki skin to mf2 =====<br />
See: <br />
* https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Skinning<br />
* update the microformats MediaWiki skin from using [[hAtom]] (e.g. 'hentry' class name) to [[h-entry]]<br />
* update any other classic microformats markup in the skin to mf2<br />
* under a new MediaWiki version we may have to do this with the Vector theme instead of the current theme. I can do the same thing I did with the IndieWeb wiki here as well if that's where we end up. [[User:Aaronpk|Aaronpk]] 18:27, 15 February 2019 (UTC)<br />
<br />
==== more spec styling ====<br />
We have [[specifications]] and [[draft specifications]] which add classnames to the body element ("specification" and "specification draft" respectively), which are then styled by the skin to look more spec-like.<br />
<br />
We should do the same for [[stub specifications]] and update [[process]] accordingly as well.<br />
<br />
==== wiki problems ====<br />
Problems with the microformats wiki that an admin needs to look at and resolve:<br />
<br />
===== Password reset page problems =====<br />
Password reset page doesn't work:<br />
* http://microformats.org/wiki/Special:PasswordReset<br />
* as of 2015-06-15, this is still a problem and is now affecting users. [http://logs.glob.uno/?c=freenode%23microformats&s=15+Jun+2015&e=15+Jun+2015#c81446 relevant irc log]<br />
<br />
==== wiki documentation ====<br />
Need more documentation about how we have the wiki setup, so more [[admins]] are able to fix/update it.<br />
* Update our [[mediawiki customization]] documentation with specifically:<br />
** What plug-ins/add-ons are installed?<br />
** What customizations / patches have been made to MediaWiki?<br />
** What special things does the microformats mediawiki theme depend on?<br />
** [[User:BenWard]] likely best knows these things.<br />
<br />
==== wiki feature requests ====<br />
===== handle feedback =====<br />
* Process [[wiki-feedback]] and add items here accordingly.<br />
===== spam fighting =====<br />
* Install [https://www.mediawiki.org/wiki/Extension:AbuseFilter AbuseFilter]. This would allow admins to set up custom rules (similar to email rules like in Outlook/Thunderbird/Gmail etc.) that could be adapted to current spam on-the-fly.<br />
* Install [http://www.mediawiki.org/wiki/Extension:TitleBlacklist TitleBlackList Extension] and then block creation of pages with "http:" or ".com" in the title to stop spammers from creating autolinks in the IRC logs of wiki edits.<br />
* Consider additional mediawiki.org anti-spam strategies: https://www.mediawiki.org/wiki/Manual:Combating_spam (from Tom Morris)<br />
** also: add reCAPTCHA setting for ConfirmEdit and SimpleAntiSpam (GPHemsley added them to the WAHTWG wiki on 2012-296)<br />
<br />
===== semantic requests =====<br />
* Try adding https://github.com/microformats/LinkAttributes to our wiki install to permit rel and class on links in wiki pages.<br />
* Add Extensions - especially those that help implement more microformats on the wiki itself!<br />
** Evaluate against Wikipedia's [http://en.wikipedia.org/wiki/Special:Version Version Page] for a list of currently installed extensions on the English Wikipedia.<br />
** I'd personally advise getting [http://www.mediawiki.org/wiki/Extension:Cite Cite], [http://meta.wikimedia.org/wiki/ParserFunctions ParserFunctions] --[[User:JimboJW|JimboJW]] 13:38, 25 Sep 2007 (PDT) (Syntax Highlighting is done in Wiki 2.0)<br />
** [http://www.mediawiki.org/wiki/Extension:HTML_Profiles HTML Profiles] - allows people editing the wiki to add URIs to <code>&lt;head profile></code> [[User:TobyInk|TobyInk]] 16:52, 9 March 2009 (UTC)<br />
*** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
** [http://www.mediawiki.org/wiki/Extension:Link_Attributes Link Attributes] - allows easy-ish setting of rel/rev/class attributes on links. [[User:TobyInk|TobyInk]] 16:52, 9 March 2009 (UTC)<br />
*** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
* add a class, <code>noprint</code> to the site's CSS, so that sections (such as "related pages" footers) can be made non- printing.<br />
** ‘noprint’ isn't so semantic, but we should get a proper print stylesheet, for sure.<br />
* Allow <kbd>webcal://</kbd>, <kbd>javascript:</kbd> (for posting [[favelets]]/bookmarklets on the wiki) and perhaps (other) x-protocols to be linkified<br />
** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
* Would be great to have a video template that embeds an object. [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
* Can we imply <code>entry-title</code> from <code>h1</code>? [[User:Tantek|Tantek]]<br />
<br />
===== misc requests =====<br />
* Set up a cron job to export the wiki database (without user details), and make it available in a public location.<br />
* Install creation template extension(s)(see: http://meta.wikimedia.org/wiki/Inputbox or http://www.mediawiki.org/wiki/Extension:CreateBox or http://www.mediawiki.org/wiki/Extension:CreateArticle) [[User:RobManson]] 14:00, 20 Jul 2007 (AEST)<br />
* Add admins sidebar (quick ban list access)<br />
* Do something to allow easy copying of sample input (e.g. add ‘Copy’ UI, or abuse <code>input</code> element<br />
* Fix MediaWiki to lowercase URLs — especially fragment identifiers generated from headings. Content ''should not'' be sub-optimally edited according to the requirements of the CMS.<br />
* Update the interwiki-links table to allow for sensible linking to other wikis doing similar work. See [https://www.mediawiki.org/wiki/Manual:Interwiki help page on mediawiki.org] and [http://microformats.org/wiki/api.php?action=query&meta=siteinfo&siprop=interwikimap current interwikimap as XML from MediWiki API].<br />
** some plausible interwiki links: Wikipedia and other Wikimedia sites, IndieWebCamp, W3C Wiki, WHATWG wiki.<br />
<br />
=== forum ===<br />
In the past there have been requests (e.g. on the lists) for an online forum for microformats discussions.<br />
<br />
If there is an admin who's interested in helping run a forum (has the time to community manage it), take a look at:<br />
<br />
* consider create a new forum on microformats.org<br />
** e.g. install http://vanillaforums.org/ (Geoloqi uses it successfully on https://community.geoloqi.com/ and highly recommends it)<br />
<br />
== ongoing ==<br />
Ongoing and as neeeded duties/tasks:<br />
<br />
* Delete spam and block spammers from the wiki.<br />
* Send emails to the microformats list(s) guiding the community per our [[mailing-lists]] guidelines.<br />
* Helped out with questions on [[IRC]]<br />
* Accepted / filtered comments on the blog (or posted!)<br />
* Help with web server matintenence:<br />
** Apache (reboot Apache if it hangs, debug Apache server problems)<br />
** WordPress (including upgrading installs as needed)<br />
** Mailman (clearing of internal spam queues)<br />
** MediaWiki (upgrades, help package mods for resubmission back to core)<br />
* Provide guidance to other admins<br />
* Remove [http://microformats.org/wiki?title=Special:Whatlinkshere&target=delete pages awaiting deletion]<br />
<br />
== waiting for ==<br />
Per GTD, here are next-actions for admins that are awaiting some external dependency.<br />
<br />
Waiting-for: <br />
* Upgrade the MediaWiki to a new enough version for IndieAuth plugin to work (that is in use on indieweb.org) In order to:<br />
** install and make available IndieAuth login, as a replacement for OpenID login (previously requested by a while ago from [[User:DanC]] and [[User:Chris_Messina]] (especially for comments in WordPress). [[User:Chris_Messina]] 16:50, 31 Aug 2007 (PDT))<br />
** check that [[Special:Renameuser]] exists as a page (should for any Mediawiki 1.18 or later by default, without needing https://www.mediawiki.org/wiki/Extension:Renameuser)<br />
*** ping [[Tantek]] to finish user renaming fix.<br />
<br />
== someday maybe ==<br />
Per GTD, here are parked and otherwise deemed low-priority next-actions and projects for admins.<br />
<br />
=== someday actions ===<br />
* Make the edit comment UI better — textarea, not single line box. (Dev Status: Might be impossible without hacking the core)<br />
<br />
=== someday maybe projects ===<br />
==== improved issue tracking ====<br />
<div class="discussion"><br />
Issue tracking at microformats.org is poor. The wiki is difficult to track, resolutions get lost. A proper bug tracking system is desirable: However, the adminstration overhead of our current infrastructure is too high for volunteers. Questionable whether maintain another custom install of something is the direct we want to move in.<br />
* I don't think this is worth pursuing - issue tracking systems are notoriously problematic, and at least with the wiki, editing/resolving many issues at once is far more efficient - and efficiency for microformats maintainers is an important priority since all this work is all-volunteer. [[User:Tantek|Tantek]] 02:38, 10 September 2009 (UTC)<br />
* I think there are a few benefits to having a tracker. The primary one is simply to track proposals and have an easy platform for people to suggest new ones. That way there is a decent place for a high-level overview of what is going on. But, all of the suggested solutions suck. If it is to be done, we should investigate a custom built tracker for our needs. [[User:Garbee|Garbee]] 00:43, 3 June 2013 (UTC)<br />
* Note that a few specs have started tracking issues on GitHub, e.g. [[h-entry]] [[User:Aaronpk|Aaronpk]] 21:47, 4 December 2017 (UTC)<br />
</div><br />
<br />
* Investigate possibility/feasibility of using Launchpad/Github/Google Code for spec issue tracking<br />
* Wiki is excellent documentation tool. Terrible issue tracking tool.<br />
* External services avoid large maintenance burden<br />
* Could better handle this todo list<br />
* Better handle issue resolutions<br />
* Better handle issue discussions<br />
<br />
* Evaluate options<br />
** Consider integration points with µf.org<br />
** Consider open standards a plus (OpenID)<br />
** Consider effort in porting existing content<br />
* Copy over issues from each wiki page as standalone bugs<br />
* Ensure that each spec editor is added with suitable authorities to manage issues<br />
<br />
=====Custom Install of Trac=====<br />
* + Reliable<br />
* + Well Established<br />
* + Can customise to look like µf.org<br />
* + Flexible milestones etc.<br />
* + Hook into source repository of our choosing<br />
* + OpenID support<br />
* + Support whatever licensing we like<br />
* - Administration overhead<br />
<br />
Need to check permissions structures. Can the hCard editor have control over /hcard, but not over /haudio? Do we care?<br />
<br />
=====Google Code=====<br />
Chris Messina has ‘microformats’ on Google Code<br />
<br />
* + Reliably Hosted, minimal admin overhead<br />
* + Very flexible milestones/tagging<br />
* + SVN repository for test cases, libraries<br />
* - Can't be styled to µf.org<br />
* - No OpenID<br />
* - Ugly as sin<br />
* - No Public Domain license support<br />
<br />
=====Launchpad=====<br />
Ben Ward has ‘microformats’ on Launchpad<br />
<br />
* + BZR repository for test cases, libraries<br />
* + Public Domain License Support<br />
* - Not instantly intuitive<br />
* - Seems better suited to software than specifications<br />
* - Can't style like µf.org, but, quite pretty<br />
* - No OpenID<br />
<br />
=====Github=====<br />
* + Git repository for test cases, libraries<br />
* + Issue tracking is integrated<br />
* - No OpenID<br />
<br />
<br />
== done ==<br />
<br />
Admins Mailing list deliverability<br />
* the last admins mailing was put in spam for kevinmarks@gmail.com by gmail for unclear reasons<br />
** it was labelled: 'security: microformats.org did not encrypt this message link to support.google.com/mail?hl=en&p=tls '<br />
** Authentication-Results: mx.google.com;<br />
dkim=neutral (body hash did not verify) header.i=@gmail.com header.s=20161025 header.b=NpEH0xA1;<br />
spf=pass (google.com: best guess record for domain of microformats-admin-bounces@microformats.org designates 64.207.154.205 as permitted sender) smtp.mailfrom=microformats-admin-bounces@microformats.org<br />
* 2020-07-18 the admin mailing list has been moved to [https://groups.google.com/u/0/g/uf-admin Google Groups] ([[User talk:Aaronpk|talk]])<br />
<br />
=== server migration project ===<br />
<br />
The best option to upgrade everything on the server is to set up a new server and move everything onto it, then switch the DNS over when it's ready. Here is the current status of what we need to do in order to complete this.<br />
<br />
This migration has been completed! Some notes and resources are available [https://github.com/microformats/wiki on GitHub (admin-only repo)] [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)<br />
<br />
==== blog ====<br />
The home page and blog are powered by WordPress. Thankfully WordPress does a pretty good job of providing an upgrade path. We can move the wordpress files to a new server to test this out before doing anything live.<br />
<br />
tasks that need a volunteer:<br />
* check that the theme works in a new version of WordPress<br />
* check that the current WordPress database can handle being upgraded to new WordPress<br />
<br />
If you would like to help out with either of these, get in touch with [https://aaronparecki.com aaronpk] and he can provide you with a copy of the files.<br />
<br />
==== wiki ====<br />
MediaWiki has a good upgrade path that will run database migrations, so it should be possible to restore the database into a new copy of the wiki. <br />
<br />
Things to check:<br />
<br />
* are there any extensions currently installed that we still need (some of them provide functionality that has since been moved into MW core), and do those extensions run under the latest MW<br />
** is there a new recaptcha plugin? some other way to prevent spam accounts?<br />
** (please list out more extensions here)<br />
* does the current theme work in new MediaWiki? and if not, do we revert to the default Vector theme?<br />
* I've reviewed the current plugins and made some upgrade notes on [[mediawiki_customization#Upgrade_MediaWiki]] as of 2018-10. [[User:GRegorLove|gRegor]] 20:01, 31 May 2019 (UTC)<br />
<br />
=== web server ===<br />
==== HTTPS ====<br />
HTTPS / TLS / SSL support:<br />
* Obtain and implement a TLS certificate (perhaps from Let's Encrypt?) for microformats.org and 301 redirect HTTP requests to HTTPS.<br />
* Certificate is running, but http-to-https redirects are not in place, pending further discussion [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:27, 19 July 2020 (UTC)<br />
<br />
==== upgrade PHP ====<br />
* Investigate an upgrade of PHP <br />
** PHP 5.6 active support ended 2017-01-19 and security support will end 2018-12-31 [http://php.net/supported-versions.php]. Upgrading to PHP7 might be a good idea currently. [[User:GRegorLove|gRegor]] 19:40, 9 May 2017 (UTC)<br />
** +1 agreed. [[User:Pfefferle|Pfefferle]] 17:58, 28 June 2018 (UTC)<br />
** this will be taken care of in the server migration project above [[User:Aaronpk|Aaronpk]] 18:27, 15 February 2019 (UTC)<br />
* The server is running PHP 7.4 now [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)<br />
<br />
=== wiki problems ===<br />
===== reCAPTCHA replacement =====<br />
reCAPTCHA replacement needed<br />
* had to edit out the https from a link above to get this to save.<br />
* reCAPTCHA has been removed, account creation currently requires contacting an admin [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)<br />
<br />
===== MediaWiki needs updating =====<br />
MediaWiki needs updating<br />
* Last time update attempt broke the theme, didn't have time time debug and fix. - [[User:BenWard]]<br />
** The IndieWeb wiki had the same problem, our resolution was to just drop the custom theme and switch to the default Vector theme. [[User:Aaronpk|Aaronpk]] 21:48, 4 December 2017 (UTC)<br />
* The wiki has been updated, reverted to the default Vector theme [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)<br />
<br />
== related ==<br />
* [[to-do]]<br />
* [[admins]]<br />
* [[admin-how-to]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=admin-to-do&diff=70221admin-to-do2020-07-19T17:27:33Z<p>Aaronpk: </p>
<hr />
<div>{{DISPLAYTITLE:admin to-do}}<br />
Filtered and processed [[to-do]] items specifically for [[admins]].<br />
<br />
Only [[admins]] should edit this page with non-minor edits.<br />
<br />
Please add to-do suggestions for admins to the general [[to-do#Admins|to-do page's Admins section]]. Thanks!<br />
<br />
Items here may list who originally suggested the item on the [[to-do]] page.<br />
<br />
Related: [[admin-how-to]].<br />
<br />
== inbox ==<br />
Per GTD, here are inbox items that seem reasonable and thus have been moved here by admins from the [[to-do#Admins|to-do page's Admins section]].<br />
<br />
Mirror server requests:<br />
* Note that requests from 88.190.13.197 are for a mirror server run by [[User:Neuro|neuro]] at 88.190.224.126.<br />
* ...<br />
<br />
== next actions and projects ==<br />
Per GTD, here are processed next-actions for admins, grouped by area/project<br />
<br />
* [[events/2008-03-10-sxsw-admins-meetup#next_actions|next-actions from 2008-03-10 sxsw admins meetup]]<br />
** noted here for tracking purposes.<br />
*** This was a very long time ago - we need to reprocess this item to see what is still relevant >5 years later! - [[User:Tantek|Tantek]] 13:33, 15 September 2013 (UTC)<br />
<br />
<br />
=== irc ===<br />
* Pibb integration for the #microformats IRC channel. It is relatively simple to [http://janrain.com/blog/2007/08/08/how-to-embed-pibb/ embed the Pibb chat widget] into a webpage that bridges to the #microformats IRC channel. This would allow for greater access and transparency to the IRC discussions as well as allow people to participate using only their web browser. [[User:Chris_Messina]] 16:50, 31 Aug 2007 (PDT)<br />
<br />
* maintainer for [[mfbot]]. Ryan King has indicated that he no longer has time to maintain [[mfbot]] and would like another admin to pick up the maintenance and running of mfbot.<br />
<br />
* The https://indieweb.org/discuss options and Loqi cover these needs currently. [[User:GRegorLove|gRegor]] 19:43, 9 May 2017 (UTC)<br />
<br />
=== web site ===<br />
==== home page ====<br />
Main site home page:<br />
* The microformats2 page, should also be referred from the main page of the website http://microformats.org/ like perhaps a new small right box in between "What are microformats?" and "Microformat specifications" saying something like "Microformat version" as a title and place both versions, the old one is the latest with a short description, and the new one should be imediately under the title, with the same description below.<br />
** +1 agreed. We need a home page redesign with at least this, maybe also @microformats tweets. [[User:Tantek|Tantek]] 13:32, 15 September 2013 (UTC)<br />
<br />
ex: [http://screencast.com/t/77YHGASumqm Homepage with the right box implemented] .<br />
<br />
==== blog ====<br />
* Update Blog-Theme to support [[microformats2]]: Publish the microformats theme on GitHub to enable community contributions. See IRC discussion: <nowiki>https://chat.indieweb.org/microformats/2018-06-28#t1530196357894800</nowiki>.<br />
** Todo: Publish all theme sources on GitHub: <nowiki>https://chat.indieweb.org/microformats/2018-06-28/1530198611202600</nowiki><br />
<br />
=== wiki ===<br />
==== proper redirects to avoid dupes ====<br />
Wiki area suggestion:<br />
*Wiki creates duplicate content by allowing duplicate pages for microformats2: the main one is http://microformats.org/wiki/microformats2 and the other one is http://microformats.org/wiki/microformats-2 .<br />
<br />
To eliminate this problem, the 2nd page http://microformats.org/wiki/microformats-2, in the <head> section of the source code, should contain the following line <link rel="canonical" href="http://microformats.org/wiki/microformats2" />. This will tell Search Engines that this page is a duplicate content, thus it won't be indexed.<br />
<br />
This implementation should be done on all other duplicate content pages of the website.<br />
<br />
* This sounds like a good request. Is there a MediaWiki extension/plugin for adding rel=canonical to redirect handling pages? - [[User:Tantek|Tantek]] 13:32, 15 September 2013 (UTC)<br />
** MediaWiki has a config for this as of v1.21.0. Reference: <nowiki>https://www.mediawiki.org/wiki/Manual:$wgEnableCanonicalServerLink</nowiki> [[User:GRegorLove|gRegor]] 01:14, 21 June 2018 (UTC)<br />
** IIRC new MediaWiki has an option to do real redirects as well [[User:Aaronpk|Aaronpk]] 18:27, 15 February 2019 (UTC)<br />
<br />
==== for site update to microformats2 ====<br />
* about<br />
** create [[about]] from updated version of http://microformats.org/about<br />
** change "about" link to /wiki/about<br />
<br />
* get-started<br />
** update [[get-started]] with info from http://microformats.org/2014/03/05/getting-started-with-microformats2<br />
<br />
===== update wiki skin to mf2 =====<br />
See: <br />
* https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Skinning<br />
* update the microformats MediaWiki skin from using [[hAtom]] (e.g. 'hentry' class name) to [[h-entry]]<br />
* update any other classic microformats markup in the skin to mf2<br />
* under a new MediaWiki version we may have to do this with the Vector theme instead of the current theme. I can do the same thing I did with the IndieWeb wiki here as well if that's where we end up. [[User:Aaronpk|Aaronpk]] 18:27, 15 February 2019 (UTC)<br />
<br />
==== more spec styling ====<br />
We have [[specifications]] and [[draft specifications]] which add classnames to the body element ("specification" and "specification draft" respectively), which are then styled by the skin to look more spec-like.<br />
<br />
We should do the same for [[stub specifications]] and update [[process]] accordingly as well.<br />
<br />
==== wiki problems ====<br />
Problems with the microformats wiki that an admin needs to look at and resolve:<br />
<br />
===== Password reset page problems =====<br />
Password reset page doesn't work:<br />
* http://microformats.org/wiki/Special:PasswordReset<br />
* as of 2015-06-15, this is still a problem and is now affecting users. [http://logs.glob.uno/?c=freenode%23microformats&s=15+Jun+2015&e=15+Jun+2015#c81446 relevant irc log]<br />
<br />
==== wiki documentation ====<br />
Need more documentation about how we have the wiki setup, so more [[admins]] are able to fix/update it.<br />
* Update our [[mediawiki customization]] documentation with specifically:<br />
** What plug-ins/add-ons are installed?<br />
** What customizations / patches have been made to MediaWiki?<br />
** What special things does the microformats mediawiki theme depend on?<br />
** [[User:BenWard]] likely best knows these things.<br />
<br />
==== wiki feature requests ====<br />
===== handle feedback =====<br />
* Process [[wiki-feedback]] and add items here accordingly.<br />
===== spam fighting =====<br />
* Install [https://www.mediawiki.org/wiki/Extension:AbuseFilter AbuseFilter]. This would allow admins to set up custom rules (similar to email rules like in Outlook/Thunderbird/Gmail etc.) that could be adapted to current spam on-the-fly.<br />
* Install [http://www.mediawiki.org/wiki/Extension:TitleBlacklist TitleBlackList Extension] and then block creation of pages with "http:" or ".com" in the title to stop spammers from creating autolinks in the IRC logs of wiki edits.<br />
* Consider additional mediawiki.org anti-spam strategies: https://www.mediawiki.org/wiki/Manual:Combating_spam (from Tom Morris)<br />
** also: add reCAPTCHA setting for ConfirmEdit and SimpleAntiSpam (GPHemsley added them to the WAHTWG wiki on 2012-296)<br />
<br />
===== semantic requests =====<br />
* Try adding https://github.com/microformats/LinkAttributes to our wiki install to permit rel and class on links in wiki pages.<br />
* Add Extensions - especially those that help implement more microformats on the wiki itself!<br />
** Evaluate against Wikipedia's [http://en.wikipedia.org/wiki/Special:Version Version Page] for a list of currently installed extensions on the English Wikipedia.<br />
** I'd personally advise getting [http://www.mediawiki.org/wiki/Extension:Cite Cite], [http://meta.wikimedia.org/wiki/ParserFunctions ParserFunctions] --[[User:JimboJW|JimboJW]] 13:38, 25 Sep 2007 (PDT) (Syntax Highlighting is done in Wiki 2.0)<br />
** [http://www.mediawiki.org/wiki/Extension:HTML_Profiles HTML Profiles] - allows people editing the wiki to add URIs to <code>&lt;head profile></code> [[User:TobyInk|TobyInk]] 16:52, 9 March 2009 (UTC)<br />
*** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
** [http://www.mediawiki.org/wiki/Extension:Link_Attributes Link Attributes] - allows easy-ish setting of rel/rev/class attributes on links. [[User:TobyInk|TobyInk]] 16:52, 9 March 2009 (UTC)<br />
*** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
* add a class, <code>noprint</code> to the site's CSS, so that sections (such as "related pages" footers) can be made non- printing.<br />
** ‘noprint’ isn't so semantic, but we should get a proper print stylesheet, for sure.<br />
* Allow <kbd>webcal://</kbd>, <kbd>javascript:</kbd> (for posting [[favelets]]/bookmarklets on the wiki) and perhaps (other) x-protocols to be linkified<br />
** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
* Would be great to have a video template that embeds an object. [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
* Can we imply <code>entry-title</code> from <code>h1</code>? [[User:Tantek|Tantek]]<br />
<br />
===== misc requests =====<br />
* Set up a cron job to export the wiki database (without user details), and make it available in a public location.<br />
* Install creation template extension(s)(see: http://meta.wikimedia.org/wiki/Inputbox or http://www.mediawiki.org/wiki/Extension:CreateBox or http://www.mediawiki.org/wiki/Extension:CreateArticle) [[User:RobManson]] 14:00, 20 Jul 2007 (AEST)<br />
* Add admins sidebar (quick ban list access)<br />
* Do something to allow easy copying of sample input (e.g. add ‘Copy’ UI, or abuse <code>input</code> element<br />
* Fix MediaWiki to lowercase URLs — especially fragment identifiers generated from headings. Content ''should not'' be sub-optimally edited according to the requirements of the CMS.<br />
* Update the interwiki-links table to allow for sensible linking to other wikis doing similar work. See [https://www.mediawiki.org/wiki/Manual:Interwiki help page on mediawiki.org] and [http://microformats.org/wiki/api.php?action=query&meta=siteinfo&siprop=interwikimap current interwikimap as XML from MediWiki API].<br />
** some plausible interwiki links: Wikipedia and other Wikimedia sites, IndieWebCamp, W3C Wiki, WHATWG wiki.<br />
<br />
=== forum ===<br />
In the past there have been requests (e.g. on the lists) for an online forum for microformats discussions.<br />
<br />
If there is an admin who's interested in helping run a forum (has the time to community manage it), take a look at:<br />
<br />
* consider create a new forum on microformats.org<br />
** e.g. install http://vanillaforums.org/ (Geoloqi uses it successfully on https://community.geoloqi.com/ and highly recommends it)<br />
<br />
== ongoing ==<br />
Ongoing and as neeeded duties/tasks:<br />
<br />
* Delete spam and block spammers from the wiki.<br />
* Send emails to the microformats list(s) guiding the community per our [[mailing-lists]] guidelines.<br />
* Helped out with questions on [[IRC]]<br />
* Accepted / filtered comments on the blog (or posted!)<br />
* Help with web server matintenence:<br />
** Apache (reboot Apache if it hangs, debug Apache server problems)<br />
** WordPress (including upgrading installs as needed)<br />
** Mailman (clearing of internal spam queues)<br />
** MediaWiki (upgrades, help package mods for resubmission back to core)<br />
* Provide guidance to other admins<br />
* Remove [http://microformats.org/wiki?title=Special:Whatlinkshere&target=delete pages awaiting deletion]<br />
<br />
== waiting for ==<br />
Per GTD, here are next-actions for admins that are awaiting some external dependency.<br />
<br />
Waiting-for: <br />
* Upgrade the MediaWiki to a new enough version for IndieAuth plugin to work (that is in use on indieweb.org) In order to:<br />
** install and make available IndieAuth login, as a replacement for OpenID login (previously requested by a while ago from [[User:DanC]] and [[User:Chris_Messina]] (especially for comments in WordPress). [[User:Chris_Messina]] 16:50, 31 Aug 2007 (PDT))<br />
** check that [[Special:Renameuser]] exists as a page (should for any Mediawiki 1.18 or later by default, without needing https://www.mediawiki.org/wiki/Extension:Renameuser)<br />
*** ping [[Tantek]] to finish user renaming fix.<br />
<br />
== someday maybe ==<br />
Per GTD, here are parked and otherwise deemed low-priority next-actions and projects for admins.<br />
<br />
=== someday actions ===<br />
* Make the edit comment UI better — textarea, not single line box. (Dev Status: Might be impossible without hacking the core)<br />
<br />
=== someday maybe projects ===<br />
==== improved issue tracking ====<br />
<div class="discussion"><br />
Issue tracking at microformats.org is poor. The wiki is difficult to track, resolutions get lost. A proper bug tracking system is desirable: However, the adminstration overhead of our current infrastructure is too high for volunteers. Questionable whether maintain another custom install of something is the direct we want to move in.<br />
* I don't think this is worth pursuing - issue tracking systems are notoriously problematic, and at least with the wiki, editing/resolving many issues at once is far more efficient - and efficiency for microformats maintainers is an important priority since all this work is all-volunteer. [[User:Tantek|Tantek]] 02:38, 10 September 2009 (UTC)<br />
* I think there are a few benefits to having a tracker. The primary one is simply to track proposals and have an easy platform for people to suggest new ones. That way there is a decent place for a high-level overview of what is going on. But, all of the suggested solutions suck. If it is to be done, we should investigate a custom built tracker for our needs. [[User:Garbee|Garbee]] 00:43, 3 June 2013 (UTC)<br />
* Note that a few specs have started tracking issues on GitHub, e.g. [[h-entry]] [[User:Aaronpk|Aaronpk]] 21:47, 4 December 2017 (UTC)<br />
</div><br />
<br />
* Investigate possibility/feasibility of using Launchpad/Github/Google Code for spec issue tracking<br />
* Wiki is excellent documentation tool. Terrible issue tracking tool.<br />
* External services avoid large maintenance burden<br />
* Could better handle this todo list<br />
* Better handle issue resolutions<br />
* Better handle issue discussions<br />
<br />
* Evaluate options<br />
** Consider integration points with µf.org<br />
** Consider open standards a plus (OpenID)<br />
** Consider effort in porting existing content<br />
* Copy over issues from each wiki page as standalone bugs<br />
* Ensure that each spec editor is added with suitable authorities to manage issues<br />
<br />
=====Custom Install of Trac=====<br />
* + Reliable<br />
* + Well Established<br />
* + Can customise to look like µf.org<br />
* + Flexible milestones etc.<br />
* + Hook into source repository of our choosing<br />
* + OpenID support<br />
* + Support whatever licensing we like<br />
* - Administration overhead<br />
<br />
Need to check permissions structures. Can the hCard editor have control over /hcard, but not over /haudio? Do we care?<br />
<br />
=====Google Code=====<br />
Chris Messina has ‘microformats’ on Google Code<br />
<br />
* + Reliably Hosted, minimal admin overhead<br />
* + Very flexible milestones/tagging<br />
* + SVN repository for test cases, libraries<br />
* - Can't be styled to µf.org<br />
* - No OpenID<br />
* - Ugly as sin<br />
* - No Public Domain license support<br />
<br />
=====Launchpad=====<br />
Ben Ward has ‘microformats’ on Launchpad<br />
<br />
* + BZR repository for test cases, libraries<br />
* + Public Domain License Support<br />
* - Not instantly intuitive<br />
* - Seems better suited to software than specifications<br />
* - Can't style like µf.org, but, quite pretty<br />
* - No OpenID<br />
<br />
=====Github=====<br />
* + Git repository for test cases, libraries<br />
* + Issue tracking is integrated<br />
* - No OpenID<br />
<br />
<br />
== done ==<br />
<br />
Admins Mailing list deliverability<br />
* the last admins mailing was put in spam for kevinmarks@gmail.com by gmail for unclear reasons<br />
** it was labelled: 'security: microformats.org did not encrypt this message link to support.google.com/mail?hl=en&p=tls '<br />
** Authentication-Results: mx.google.com;<br />
dkim=neutral (body hash did not verify) header.i=@gmail.com header.s=20161025 header.b=NpEH0xA1;<br />
spf=pass (google.com: best guess record for domain of microformats-admin-bounces@microformats.org designates 64.207.154.205 as permitted sender) smtp.mailfrom=microformats-admin-bounces@microformats.org<br />
* 2020-07-18 the admin mailing list has been moved to [https://groups.google.com/u/0/g/uf-admin Google Groups] [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]])<br />
<br />
=== server migration project ===<br />
<br />
The best option to upgrade everything on the server is to set up a new server and move everything onto it, then switch the DNS over when it's ready. Here is the current status of what we need to do in order to complete this.<br />
<br />
This migration has been completed! Some notes and resources are available [https://github.com/microformats/wiki on GitHub (admin-only repo)] [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)<br />
<br />
==== blog ====<br />
The home page and blog are powered by WordPress. Thankfully WordPress does a pretty good job of providing an upgrade path. We can move the wordpress files to a new server to test this out before doing anything live.<br />
<br />
tasks that need a volunteer:<br />
* check that the theme works in a new version of WordPress<br />
* check that the current WordPress database can handle being upgraded to new WordPress<br />
<br />
If you would like to help out with either of these, get in touch with [https://aaronparecki.com aaronpk] and he can provide you with a copy of the files.<br />
<br />
==== wiki ====<br />
MediaWiki has a good upgrade path that will run database migrations, so it should be possible to restore the database into a new copy of the wiki. <br />
<br />
Things to check:<br />
<br />
* are there any extensions currently installed that we still need (some of them provide functionality that has since been moved into MW core), and do those extensions run under the latest MW<br />
** is there a new recaptcha plugin? some other way to prevent spam accounts?<br />
** (please list out more extensions here)<br />
* does the current theme work in new MediaWiki? and if not, do we revert to the default Vector theme?<br />
* I've reviewed the current plugins and made some upgrade notes on [[mediawiki_customization#Upgrade_MediaWiki]] as of 2018-10. [[User:GRegorLove|gRegor]] 20:01, 31 May 2019 (UTC)<br />
<br />
=== web server ===<br />
==== HTTPS ====<br />
HTTPS / TLS / SSL support:<br />
* Obtain and implement a TLS certificate (perhaps from Let's Encrypt?) for microformats.org and 301 redirect HTTP requests to HTTPS.<br />
* Certificate is running, but http-to-https redirects are not in place, pending further discussion [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:27, 19 July 2020 (UTC)<br />
<br />
==== upgrade PHP ====<br />
* Investigate an upgrade of PHP <br />
** PHP 5.6 active support ended 2017-01-19 and security support will end 2018-12-31 [http://php.net/supported-versions.php]. Upgrading to PHP7 might be a good idea currently. [[User:GRegorLove|gRegor]] 19:40, 9 May 2017 (UTC)<br />
** +1 agreed. [[User:Pfefferle|Pfefferle]] 17:58, 28 June 2018 (UTC)<br />
** this will be taken care of in the server migration project above [[User:Aaronpk|Aaronpk]] 18:27, 15 February 2019 (UTC)<br />
* The server is running PHP 7.4 now [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)<br />
<br />
=== wiki problems ===<br />
===== reCAPTCHA replacement =====<br />
reCAPTCHA replacement needed<br />
* had to edit out the https from a link above to get this to save.<br />
* reCAPTCHA has been removed, account creation currently requires contacting an admin [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)<br />
<br />
===== MediaWiki needs updating =====<br />
MediaWiki needs updating<br />
* Last time update attempt broke the theme, didn't have time time debug and fix. - [[User:BenWard]]<br />
** The IndieWeb wiki had the same problem, our resolution was to just drop the custom theme and switch to the default Vector theme. [[User:Aaronpk|Aaronpk]] 21:48, 4 December 2017 (UTC)<br />
* The wiki has been updated, reverted to the default Vector theme [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)<br />
<br />
== related ==<br />
* [[to-do]]<br />
* [[admins]]<br />
* [[admin-how-to]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=admin-to-do&diff=70220admin-to-do2020-07-19T17:25:20Z<p>Aaronpk: add link to github repo for tracking server migration project</p>
<hr />
<div>{{DISPLAYTITLE:admin to-do}}<br />
Filtered and processed [[to-do]] items specifically for [[admins]].<br />
<br />
Only [[admins]] should edit this page with non-minor edits.<br />
<br />
Please add to-do suggestions for admins to the general [[to-do#Admins|to-do page's Admins section]]. Thanks!<br />
<br />
Items here may list who originally suggested the item on the [[to-do]] page.<br />
<br />
Related: [[admin-how-to]].<br />
<br />
== inbox ==<br />
Per GTD, here are inbox items that seem reasonable and thus have been moved here by admins from the [[to-do#Admins|to-do page's Admins section]].<br />
<br />
Mirror server requests:<br />
* Note that requests from 88.190.13.197 are for a mirror server run by [[User:Neuro|neuro]] at 88.190.224.126.<br />
* ...<br />
<br />
== next actions and projects ==<br />
Per GTD, here are processed next-actions for admins, grouped by area/project<br />
<br />
* [[events/2008-03-10-sxsw-admins-meetup#next_actions|next-actions from 2008-03-10 sxsw admins meetup]]<br />
** noted here for tracking purposes.<br />
*** This was a very long time ago - we need to reprocess this item to see what is still relevant >5 years later! - [[User:Tantek|Tantek]] 13:33, 15 September 2013 (UTC)<br />
<br />
<br />
=== irc ===<br />
* Pibb integration for the #microformats IRC channel. It is relatively simple to [http://janrain.com/blog/2007/08/08/how-to-embed-pibb/ embed the Pibb chat widget] into a webpage that bridges to the #microformats IRC channel. This would allow for greater access and transparency to the IRC discussions as well as allow people to participate using only their web browser. [[User:Chris_Messina]] 16:50, 31 Aug 2007 (PDT)<br />
<br />
* maintainer for [[mfbot]]. Ryan King has indicated that he no longer has time to maintain [[mfbot]] and would like another admin to pick up the maintenance and running of mfbot.<br />
<br />
* The https://indieweb.org/discuss options and Loqi cover these needs currently. [[User:GRegorLove|gRegor]] 19:43, 9 May 2017 (UTC)<br />
<br />
=== web site ===<br />
==== home page ====<br />
Main site home page:<br />
* The microformats2 page, should also be referred from the main page of the website http://microformats.org/ like perhaps a new small right box in between "What are microformats?" and "Microformat specifications" saying something like "Microformat version" as a title and place both versions, the old one is the latest with a short description, and the new one should be imediately under the title, with the same description below.<br />
** +1 agreed. We need a home page redesign with at least this, maybe also @microformats tweets. [[User:Tantek|Tantek]] 13:32, 15 September 2013 (UTC)<br />
<br />
ex: [http://screencast.com/t/77YHGASumqm Homepage with the right box implemented] .<br />
<br />
==== blog ====<br />
* Update Blog-Theme to support [[microformats2]]: Publish the microformats theme on GitHub to enable community contributions. See IRC discussion: <nowiki>https://chat.indieweb.org/microformats/2018-06-28#t1530196357894800</nowiki>.<br />
** Todo: Publish all theme sources on GitHub: <nowiki>https://chat.indieweb.org/microformats/2018-06-28/1530198611202600</nowiki><br />
<br />
=== wiki ===<br />
==== proper redirects to avoid dupes ====<br />
Wiki area suggestion:<br />
*Wiki creates duplicate content by allowing duplicate pages for microformats2: the main one is http://microformats.org/wiki/microformats2 and the other one is http://microformats.org/wiki/microformats-2 .<br />
<br />
To eliminate this problem, the 2nd page http://microformats.org/wiki/microformats-2, in the <head> section of the source code, should contain the following line <link rel="canonical" href="http://microformats.org/wiki/microformats2" />. This will tell Search Engines that this page is a duplicate content, thus it won't be indexed.<br />
<br />
This implementation should be done on all other duplicate content pages of the website.<br />
<br />
* This sounds like a good request. Is there a MediaWiki extension/plugin for adding rel=canonical to redirect handling pages? - [[User:Tantek|Tantek]] 13:32, 15 September 2013 (UTC)<br />
** MediaWiki has a config for this as of v1.21.0. Reference: <nowiki>https://www.mediawiki.org/wiki/Manual:$wgEnableCanonicalServerLink</nowiki> [[User:GRegorLove|gRegor]] 01:14, 21 June 2018 (UTC)<br />
** IIRC new MediaWiki has an option to do real redirects as well [[User:Aaronpk|Aaronpk]] 18:27, 15 February 2019 (UTC)<br />
<br />
==== for site update to microformats2 ====<br />
* about<br />
** create [[about]] from updated version of http://microformats.org/about<br />
** change "about" link to /wiki/about<br />
<br />
* get-started<br />
** update [[get-started]] with info from http://microformats.org/2014/03/05/getting-started-with-microformats2<br />
<br />
===== update wiki skin to mf2 =====<br />
See: <br />
* https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Skinning<br />
* update the microformats MediaWiki skin from using [[hAtom]] (e.g. 'hentry' class name) to [[h-entry]]<br />
* update any other classic microformats markup in the skin to mf2<br />
* under a new MediaWiki version we may have to do this with the Vector theme instead of the current theme. I can do the same thing I did with the IndieWeb wiki here as well if that's where we end up. [[User:Aaronpk|Aaronpk]] 18:27, 15 February 2019 (UTC)<br />
<br />
==== more spec styling ====<br />
We have [[specifications]] and [[draft specifications]] which add classnames to the body element ("specification" and "specification draft" respectively), which are then styled by the skin to look more spec-like.<br />
<br />
We should do the same for [[stub specifications]] and update [[process]] accordingly as well.<br />
<br />
==== wiki problems ====<br />
Problems with the microformats wiki that an admin needs to look at and resolve:<br />
<br />
===== Password reset page problems =====<br />
Password reset page doesn't work:<br />
* http://microformats.org/wiki/Special:PasswordReset<br />
* as of 2015-06-15, this is still a problem and is now affecting users. [http://logs.glob.uno/?c=freenode%23microformats&s=15+Jun+2015&e=15+Jun+2015#c81446 relevant irc log]<br />
<br />
==== wiki documentation ====<br />
Need more documentation about how we have the wiki setup, so more [[admins]] are able to fix/update it.<br />
* Update our [[mediawiki customization]] documentation with specifically:<br />
** What plug-ins/add-ons are installed?<br />
** What customizations / patches have been made to MediaWiki?<br />
** What special things does the microformats mediawiki theme depend on?<br />
** [[User:BenWard]] likely best knows these things.<br />
<br />
==== wiki feature requests ====<br />
===== handle feedback =====<br />
* Process [[wiki-feedback]] and add items here accordingly.<br />
===== spam fighting =====<br />
* Install [https://www.mediawiki.org/wiki/Extension:AbuseFilter AbuseFilter]. This would allow admins to set up custom rules (similar to email rules like in Outlook/Thunderbird/Gmail etc.) that could be adapted to current spam on-the-fly.<br />
* Install [http://www.mediawiki.org/wiki/Extension:TitleBlacklist TitleBlackList Extension] and then block creation of pages with "http:" or ".com" in the title to stop spammers from creating autolinks in the IRC logs of wiki edits.<br />
* Consider additional mediawiki.org anti-spam strategies: https://www.mediawiki.org/wiki/Manual:Combating_spam (from Tom Morris)<br />
** also: add reCAPTCHA setting for ConfirmEdit and SimpleAntiSpam (GPHemsley added them to the WAHTWG wiki on 2012-296)<br />
<br />
===== semantic requests =====<br />
* Try adding https://github.com/microformats/LinkAttributes to our wiki install to permit rel and class on links in wiki pages.<br />
* Add Extensions - especially those that help implement more microformats on the wiki itself!<br />
** Evaluate against Wikipedia's [http://en.wikipedia.org/wiki/Special:Version Version Page] for a list of currently installed extensions on the English Wikipedia.<br />
** I'd personally advise getting [http://www.mediawiki.org/wiki/Extension:Cite Cite], [http://meta.wikimedia.org/wiki/ParserFunctions ParserFunctions] --[[User:JimboJW|JimboJW]] 13:38, 25 Sep 2007 (PDT) (Syntax Highlighting is done in Wiki 2.0)<br />
** [http://www.mediawiki.org/wiki/Extension:HTML_Profiles HTML Profiles] - allows people editing the wiki to add URIs to <code>&lt;head profile></code> [[User:TobyInk|TobyInk]] 16:52, 9 March 2009 (UTC)<br />
*** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
** [http://www.mediawiki.org/wiki/Extension:Link_Attributes Link Attributes] - allows easy-ish setting of rel/rev/class attributes on links. [[User:TobyInk|TobyInk]] 16:52, 9 March 2009 (UTC)<br />
*** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
* add a class, <code>noprint</code> to the site's CSS, so that sections (such as "related pages" footers) can be made non- printing.<br />
** ‘noprint’ isn't so semantic, but we should get a proper print stylesheet, for sure.<br />
* Allow <kbd>webcal://</kbd>, <kbd>javascript:</kbd> (for posting [[favelets]]/bookmarklets on the wiki) and perhaps (other) x-protocols to be linkified<br />
** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
* Would be great to have a video template that embeds an object. [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
* Can we imply <code>entry-title</code> from <code>h1</code>? [[User:Tantek|Tantek]]<br />
<br />
===== misc requests =====<br />
* Set up a cron job to export the wiki database (without user details), and make it available in a public location.<br />
* Install creation template extension(s)(see: http://meta.wikimedia.org/wiki/Inputbox or http://www.mediawiki.org/wiki/Extension:CreateBox or http://www.mediawiki.org/wiki/Extension:CreateArticle) [[User:RobManson]] 14:00, 20 Jul 2007 (AEST)<br />
* Add admins sidebar (quick ban list access)<br />
* Do something to allow easy copying of sample input (e.g. add ‘Copy’ UI, or abuse <code>input</code> element<br />
* Fix MediaWiki to lowercase URLs — especially fragment identifiers generated from headings. Content ''should not'' be sub-optimally edited according to the requirements of the CMS.<br />
* Update the interwiki-links table to allow for sensible linking to other wikis doing similar work. See [https://www.mediawiki.org/wiki/Manual:Interwiki help page on mediawiki.org] and [http://microformats.org/wiki/api.php?action=query&meta=siteinfo&siprop=interwikimap current interwikimap as XML from MediWiki API].<br />
** some plausible interwiki links: Wikipedia and other Wikimedia sites, IndieWebCamp, W3C Wiki, WHATWG wiki.<br />
<br />
=== forum ===<br />
In the past there have been requests (e.g. on the lists) for an online forum for microformats discussions.<br />
<br />
If there is an admin who's interested in helping run a forum (has the time to community manage it), take a look at:<br />
<br />
* consider create a new forum on microformats.org<br />
** e.g. install http://vanillaforums.org/ (Geoloqi uses it successfully on https://community.geoloqi.com/ and highly recommends it)<br />
<br />
== ongoing ==<br />
Ongoing and as neeeded duties/tasks:<br />
<br />
* Delete spam and block spammers from the wiki.<br />
* Send emails to the microformats list(s) guiding the community per our [[mailing-lists]] guidelines.<br />
* Helped out with questions on [[IRC]]<br />
* Accepted / filtered comments on the blog (or posted!)<br />
* Help with web server matintenence:<br />
** Apache (reboot Apache if it hangs, debug Apache server problems)<br />
** WordPress (including upgrading installs as needed)<br />
** Mailman (clearing of internal spam queues)<br />
** MediaWiki (upgrades, help package mods for resubmission back to core)<br />
* Provide guidance to other admins<br />
* Remove [http://microformats.org/wiki?title=Special:Whatlinkshere&target=delete pages awaiting deletion]<br />
<br />
== waiting for ==<br />
Per GTD, here are next-actions for admins that are awaiting some external dependency.<br />
<br />
Waiting-for: <br />
* Upgrade the MediaWiki to a new enough version for IndieAuth plugin to work (that is in use on indieweb.org) In order to:<br />
** install and make available IndieAuth login, as a replacement for OpenID login (previously requested by a while ago from [[User:DanC]] and [[User:Chris_Messina]] (especially for comments in WordPress). [[User:Chris_Messina]] 16:50, 31 Aug 2007 (PDT))<br />
** check that [[Special:Renameuser]] exists as a page (should for any Mediawiki 1.18 or later by default, without needing https://www.mediawiki.org/wiki/Extension:Renameuser)<br />
*** ping [[Tantek]] to finish user renaming fix.<br />
<br />
== someday maybe ==<br />
Per GTD, here are parked and otherwise deemed low-priority next-actions and projects for admins.<br />
<br />
=== someday actions ===<br />
* Make the edit comment UI better — textarea, not single line box. (Dev Status: Might be impossible without hacking the core)<br />
<br />
=== someday maybe projects ===<br />
==== improved issue tracking ====<br />
<div class="discussion"><br />
Issue tracking at microformats.org is poor. The wiki is difficult to track, resolutions get lost. A proper bug tracking system is desirable: However, the adminstration overhead of our current infrastructure is too high for volunteers. Questionable whether maintain another custom install of something is the direct we want to move in.<br />
* I don't think this is worth pursuing - issue tracking systems are notoriously problematic, and at least with the wiki, editing/resolving many issues at once is far more efficient - and efficiency for microformats maintainers is an important priority since all this work is all-volunteer. [[User:Tantek|Tantek]] 02:38, 10 September 2009 (UTC)<br />
* I think there are a few benefits to having a tracker. The primary one is simply to track proposals and have an easy platform for people to suggest new ones. That way there is a decent place for a high-level overview of what is going on. But, all of the suggested solutions suck. If it is to be done, we should investigate a custom built tracker for our needs. [[User:Garbee|Garbee]] 00:43, 3 June 2013 (UTC)<br />
* Note that a few specs have started tracking issues on GitHub, e.g. [[h-entry]] [[User:Aaronpk|Aaronpk]] 21:47, 4 December 2017 (UTC)<br />
</div><br />
<br />
* Investigate possibility/feasibility of using Launchpad/Github/Google Code for spec issue tracking<br />
* Wiki is excellent documentation tool. Terrible issue tracking tool.<br />
* External services avoid large maintenance burden<br />
* Could better handle this todo list<br />
* Better handle issue resolutions<br />
* Better handle issue discussions<br />
<br />
* Evaluate options<br />
** Consider integration points with µf.org<br />
** Consider open standards a plus (OpenID)<br />
** Consider effort in porting existing content<br />
* Copy over issues from each wiki page as standalone bugs<br />
* Ensure that each spec editor is added with suitable authorities to manage issues<br />
<br />
=====Custom Install of Trac=====<br />
* + Reliable<br />
* + Well Established<br />
* + Can customise to look like µf.org<br />
* + Flexible milestones etc.<br />
* + Hook into source repository of our choosing<br />
* + OpenID support<br />
* + Support whatever licensing we like<br />
* - Administration overhead<br />
<br />
Need to check permissions structures. Can the hCard editor have control over /hcard, but not over /haudio? Do we care?<br />
<br />
=====Google Code=====<br />
Chris Messina has ‘microformats’ on Google Code<br />
<br />
* + Reliably Hosted, minimal admin overhead<br />
* + Very flexible milestones/tagging<br />
* + SVN repository for test cases, libraries<br />
* - Can't be styled to µf.org<br />
* - No OpenID<br />
* - Ugly as sin<br />
* - No Public Domain license support<br />
<br />
=====Launchpad=====<br />
Ben Ward has ‘microformats’ on Launchpad<br />
<br />
* + BZR repository for test cases, libraries<br />
* + Public Domain License Support<br />
* - Not instantly intuitive<br />
* - Seems better suited to software than specifications<br />
* - Can't style like µf.org, but, quite pretty<br />
* - No OpenID<br />
<br />
=====Github=====<br />
* + Git repository for test cases, libraries<br />
* + Issue tracking is integrated<br />
* - No OpenID<br />
<br />
<br />
== done ==<br />
<br />
Admins Mailing list deliverability<br />
* the last admins mailing was put in spam for kevinmarks@gmail.com by gmail for unclear reasons<br />
** it was labelled: 'security: microformats.org did not encrypt this message link to support.google.com/mail?hl=en&p=tls '<br />
** Authentication-Results: mx.google.com;<br />
dkim=neutral (body hash did not verify) header.i=@gmail.com header.s=20161025 header.b=NpEH0xA1;<br />
spf=pass (google.com: best guess record for domain of microformats-admin-bounces@microformats.org designates 64.207.154.205 as permitted sender) smtp.mailfrom=microformats-admin-bounces@microformats.org<br />
* 2020-07-18 the admin mailing list has been moved to [https://groups.google.com/u/0/g/uf-admin Google Groups] [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]])<br />
<br />
=== server migration project ===<br />
<br />
The best option to upgrade everything on the server is to set up a new server and move everything onto it, then switch the DNS over when it's ready. Here is the current status of what we need to do in order to complete this.<br />
<br />
This migration has been completed! Some notes and resources are available [https://github.com/microformats/wiki on GitHub (admin-only repo)] [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)<br />
<br />
==== blog ====<br />
The home page and blog are powered by WordPress. Thankfully WordPress does a pretty good job of providing an upgrade path. We can move the wordpress files to a new server to test this out before doing anything live.<br />
<br />
tasks that need a volunteer:<br />
* check that the theme works in a new version of WordPress<br />
* check that the current WordPress database can handle being upgraded to new WordPress<br />
<br />
If you would like to help out with either of these, get in touch with [https://aaronparecki.com aaronpk] and he can provide you with a copy of the files.<br />
<br />
==== wiki ====<br />
MediaWiki has a good upgrade path that will run database migrations, so it should be possible to restore the database into a new copy of the wiki. <br />
<br />
Things to check:<br />
<br />
* are there any extensions currently installed that we still need (some of them provide functionality that has since been moved into MW core), and do those extensions run under the latest MW<br />
** is there a new recaptcha plugin? some other way to prevent spam accounts?<br />
** (please list out more extensions here)<br />
* does the current theme work in new MediaWiki? and if not, do we revert to the default Vector theme?<br />
* I've reviewed the current plugins and made some upgrade notes on [[mediawiki_customization#Upgrade_MediaWiki]] as of 2018-10. [[User:GRegorLove|gRegor]] 20:01, 31 May 2019 (UTC)<br />
<br />
=== web server ===<br />
==== HTTPS ====<br />
HTTPS / TLS / SSL support:<br />
* Obtain and implement a TLS certificate (perhaps from Let's Encrypt?) for microformats.org and 301 redirect HTTP requests to HTTPS.<br />
<br />
==== upgrade PHP ====<br />
* Investigate an upgrade of PHP <br />
** PHP 5.6 active support ended 2017-01-19 and security support will end 2018-12-31 [http://php.net/supported-versions.php]. Upgrading to PHP7 might be a good idea currently. [[User:GRegorLove|gRegor]] 19:40, 9 May 2017 (UTC)<br />
** +1 agreed. [[User:Pfefferle|Pfefferle]] 17:58, 28 June 2018 (UTC)<br />
** this will be taken care of in the server migration project above [[User:Aaronpk|Aaronpk]] 18:27, 15 February 2019 (UTC)<br />
* The server is running PHP 7.4 now [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)<br />
<br />
=== wiki problems ===<br />
===== reCAPTCHA replacement =====<br />
reCAPTCHA replacement needed<br />
* had to edit out the https from a link above to get this to save.<br />
* reCAPTCHA has been removed, account creation currently requires contacting an admin [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)<br />
<br />
===== MediaWiki needs updating =====<br />
MediaWiki needs updating<br />
* Last time update attempt broke the theme, didn't have time time debug and fix. - [[User:BenWard]]<br />
** The IndieWeb wiki had the same problem, our resolution was to just drop the custom theme and switch to the default Vector theme. [[User:Aaronpk|Aaronpk]] 21:48, 4 December 2017 (UTC)<br />
* The wiki has been updated, reverted to the default Vector theme [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)<br />
<br />
== related ==<br />
* [[to-do]]<br />
* [[admins]]<br />
* [[admin-how-to]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=admin-to-do&diff=70219admin-to-do2020-07-19T17:23:37Z<p>Aaronpk: server migration project is done!</p>
<hr />
<div>{{DISPLAYTITLE:admin to-do}}<br />
Filtered and processed [[to-do]] items specifically for [[admins]].<br />
<br />
Only [[admins]] should edit this page with non-minor edits.<br />
<br />
Please add to-do suggestions for admins to the general [[to-do#Admins|to-do page's Admins section]]. Thanks!<br />
<br />
Items here may list who originally suggested the item on the [[to-do]] page.<br />
<br />
Related: [[admin-how-to]].<br />
<br />
== inbox ==<br />
Per GTD, here are inbox items that seem reasonable and thus have been moved here by admins from the [[to-do#Admins|to-do page's Admins section]].<br />
<br />
Mirror server requests:<br />
* Note that requests from 88.190.13.197 are for a mirror server run by [[User:Neuro|neuro]] at 88.190.224.126.<br />
* ...<br />
<br />
== next actions and projects ==<br />
Per GTD, here are processed next-actions for admins, grouped by area/project<br />
<br />
* [[events/2008-03-10-sxsw-admins-meetup#next_actions|next-actions from 2008-03-10 sxsw admins meetup]]<br />
** noted here for tracking purposes.<br />
*** This was a very long time ago - we need to reprocess this item to see what is still relevant >5 years later! - [[User:Tantek|Tantek]] 13:33, 15 September 2013 (UTC)<br />
<br />
<br />
=== irc ===<br />
* Pibb integration for the #microformats IRC channel. It is relatively simple to [http://janrain.com/blog/2007/08/08/how-to-embed-pibb/ embed the Pibb chat widget] into a webpage that bridges to the #microformats IRC channel. This would allow for greater access and transparency to the IRC discussions as well as allow people to participate using only their web browser. [[User:Chris_Messina]] 16:50, 31 Aug 2007 (PDT)<br />
<br />
* maintainer for [[mfbot]]. Ryan King has indicated that he no longer has time to maintain [[mfbot]] and would like another admin to pick up the maintenance and running of mfbot.<br />
<br />
* The https://indieweb.org/discuss options and Loqi cover these needs currently. [[User:GRegorLove|gRegor]] 19:43, 9 May 2017 (UTC)<br />
<br />
=== web site ===<br />
==== home page ====<br />
Main site home page:<br />
* The microformats2 page, should also be referred from the main page of the website http://microformats.org/ like perhaps a new small right box in between "What are microformats?" and "Microformat specifications" saying something like "Microformat version" as a title and place both versions, the old one is the latest with a short description, and the new one should be imediately under the title, with the same description below.<br />
** +1 agreed. We need a home page redesign with at least this, maybe also @microformats tweets. [[User:Tantek|Tantek]] 13:32, 15 September 2013 (UTC)<br />
<br />
ex: [http://screencast.com/t/77YHGASumqm Homepage with the right box implemented] .<br />
<br />
==== blog ====<br />
* Update Blog-Theme to support [[microformats2]]: Publish the microformats theme on GitHub to enable community contributions. See IRC discussion: <nowiki>https://chat.indieweb.org/microformats/2018-06-28#t1530196357894800</nowiki>.<br />
** Todo: Publish all theme sources on GitHub: <nowiki>https://chat.indieweb.org/microformats/2018-06-28/1530198611202600</nowiki><br />
<br />
=== wiki ===<br />
==== proper redirects to avoid dupes ====<br />
Wiki area suggestion:<br />
*Wiki creates duplicate content by allowing duplicate pages for microformats2: the main one is http://microformats.org/wiki/microformats2 and the other one is http://microformats.org/wiki/microformats-2 .<br />
<br />
To eliminate this problem, the 2nd page http://microformats.org/wiki/microformats-2, in the <head> section of the source code, should contain the following line <link rel="canonical" href="http://microformats.org/wiki/microformats2" />. This will tell Search Engines that this page is a duplicate content, thus it won't be indexed.<br />
<br />
This implementation should be done on all other duplicate content pages of the website.<br />
<br />
* This sounds like a good request. Is there a MediaWiki extension/plugin for adding rel=canonical to redirect handling pages? - [[User:Tantek|Tantek]] 13:32, 15 September 2013 (UTC)<br />
** MediaWiki has a config for this as of v1.21.0. Reference: <nowiki>https://www.mediawiki.org/wiki/Manual:$wgEnableCanonicalServerLink</nowiki> [[User:GRegorLove|gRegor]] 01:14, 21 June 2018 (UTC)<br />
** IIRC new MediaWiki has an option to do real redirects as well [[User:Aaronpk|Aaronpk]] 18:27, 15 February 2019 (UTC)<br />
<br />
==== for site update to microformats2 ====<br />
* about<br />
** create [[about]] from updated version of http://microformats.org/about<br />
** change "about" link to /wiki/about<br />
<br />
* get-started<br />
** update [[get-started]] with info from http://microformats.org/2014/03/05/getting-started-with-microformats2<br />
<br />
===== update wiki skin to mf2 =====<br />
See: <br />
* https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Skinning<br />
* update the microformats MediaWiki skin from using [[hAtom]] (e.g. 'hentry' class name) to [[h-entry]]<br />
* update any other classic microformats markup in the skin to mf2<br />
* under a new MediaWiki version we may have to do this with the Vector theme instead of the current theme. I can do the same thing I did with the IndieWeb wiki here as well if that's where we end up. [[User:Aaronpk|Aaronpk]] 18:27, 15 February 2019 (UTC)<br />
<br />
==== more spec styling ====<br />
We have [[specifications]] and [[draft specifications]] which add classnames to the body element ("specification" and "specification draft" respectively), which are then styled by the skin to look more spec-like.<br />
<br />
We should do the same for [[stub specifications]] and update [[process]] accordingly as well.<br />
<br />
==== wiki problems ====<br />
Problems with the microformats wiki that an admin needs to look at and resolve:<br />
<br />
===== Password reset page problems =====<br />
Password reset page doesn't work:<br />
* http://microformats.org/wiki/Special:PasswordReset<br />
* as of 2015-06-15, this is still a problem and is now affecting users. [http://logs.glob.uno/?c=freenode%23microformats&s=15+Jun+2015&e=15+Jun+2015#c81446 relevant irc log]<br />
<br />
==== wiki documentation ====<br />
Need more documentation about how we have the wiki setup, so more [[admins]] are able to fix/update it.<br />
* Update our [[mediawiki customization]] documentation with specifically:<br />
** What plug-ins/add-ons are installed?<br />
** What customizations / patches have been made to MediaWiki?<br />
** What special things does the microformats mediawiki theme depend on?<br />
** [[User:BenWard]] likely best knows these things.<br />
<br />
==== wiki feature requests ====<br />
===== handle feedback =====<br />
* Process [[wiki-feedback]] and add items here accordingly.<br />
===== spam fighting =====<br />
* Install [https://www.mediawiki.org/wiki/Extension:AbuseFilter AbuseFilter]. This would allow admins to set up custom rules (similar to email rules like in Outlook/Thunderbird/Gmail etc.) that could be adapted to current spam on-the-fly.<br />
* Install [http://www.mediawiki.org/wiki/Extension:TitleBlacklist TitleBlackList Extension] and then block creation of pages with "http:" or ".com" in the title to stop spammers from creating autolinks in the IRC logs of wiki edits.<br />
* Consider additional mediawiki.org anti-spam strategies: https://www.mediawiki.org/wiki/Manual:Combating_spam (from Tom Morris)<br />
** also: add reCAPTCHA setting for ConfirmEdit and SimpleAntiSpam (GPHemsley added them to the WAHTWG wiki on 2012-296)<br />
<br />
===== semantic requests =====<br />
* Try adding https://github.com/microformats/LinkAttributes to our wiki install to permit rel and class on links in wiki pages.<br />
* Add Extensions - especially those that help implement more microformats on the wiki itself!<br />
** Evaluate against Wikipedia's [http://en.wikipedia.org/wiki/Special:Version Version Page] for a list of currently installed extensions on the English Wikipedia.<br />
** I'd personally advise getting [http://www.mediawiki.org/wiki/Extension:Cite Cite], [http://meta.wikimedia.org/wiki/ParserFunctions ParserFunctions] --[[User:JimboJW|JimboJW]] 13:38, 25 Sep 2007 (PDT) (Syntax Highlighting is done in Wiki 2.0)<br />
** [http://www.mediawiki.org/wiki/Extension:HTML_Profiles HTML Profiles] - allows people editing the wiki to add URIs to <code>&lt;head profile></code> [[User:TobyInk|TobyInk]] 16:52, 9 March 2009 (UTC)<br />
*** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
** [http://www.mediawiki.org/wiki/Extension:Link_Attributes Link Attributes] - allows easy-ish setting of rel/rev/class attributes on links. [[User:TobyInk|TobyInk]] 16:52, 9 March 2009 (UTC)<br />
*** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
* add a class, <code>noprint</code> to the site's CSS, so that sections (such as "related pages" footers) can be made non- printing.<br />
** ‘noprint’ isn't so semantic, but we should get a proper print stylesheet, for sure.<br />
* Allow <kbd>webcal://</kbd>, <kbd>javascript:</kbd> (for posting [[favelets]]/bookmarklets on the wiki) and perhaps (other) x-protocols to be linkified<br />
** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
* Would be great to have a video template that embeds an object. [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
* Can we imply <code>entry-title</code> from <code>h1</code>? [[User:Tantek|Tantek]]<br />
<br />
===== misc requests =====<br />
* Set up a cron job to export the wiki database (without user details), and make it available in a public location.<br />
* Install creation template extension(s)(see: http://meta.wikimedia.org/wiki/Inputbox or http://www.mediawiki.org/wiki/Extension:CreateBox or http://www.mediawiki.org/wiki/Extension:CreateArticle) [[User:RobManson]] 14:00, 20 Jul 2007 (AEST)<br />
* Add admins sidebar (quick ban list access)<br />
* Do something to allow easy copying of sample input (e.g. add ‘Copy’ UI, or abuse <code>input</code> element<br />
* Fix MediaWiki to lowercase URLs — especially fragment identifiers generated from headings. Content ''should not'' be sub-optimally edited according to the requirements of the CMS.<br />
* Update the interwiki-links table to allow for sensible linking to other wikis doing similar work. See [https://www.mediawiki.org/wiki/Manual:Interwiki help page on mediawiki.org] and [http://microformats.org/wiki/api.php?action=query&meta=siteinfo&siprop=interwikimap current interwikimap as XML from MediWiki API].<br />
** some plausible interwiki links: Wikipedia and other Wikimedia sites, IndieWebCamp, W3C Wiki, WHATWG wiki.<br />
<br />
=== forum ===<br />
In the past there have been requests (e.g. on the lists) for an online forum for microformats discussions.<br />
<br />
If there is an admin who's interested in helping run a forum (has the time to community manage it), take a look at:<br />
<br />
* consider create a new forum on microformats.org<br />
** e.g. install http://vanillaforums.org/ (Geoloqi uses it successfully on https://community.geoloqi.com/ and highly recommends it)<br />
<br />
== ongoing ==<br />
Ongoing and as neeeded duties/tasks:<br />
<br />
* Delete spam and block spammers from the wiki.<br />
* Send emails to the microformats list(s) guiding the community per our [[mailing-lists]] guidelines.<br />
* Helped out with questions on [[IRC]]<br />
* Accepted / filtered comments on the blog (or posted!)<br />
* Help with web server matintenence:<br />
** Apache (reboot Apache if it hangs, debug Apache server problems)<br />
** WordPress (including upgrading installs as needed)<br />
** Mailman (clearing of internal spam queues)<br />
** MediaWiki (upgrades, help package mods for resubmission back to core)<br />
* Provide guidance to other admins<br />
* Remove [http://microformats.org/wiki?title=Special:Whatlinkshere&target=delete pages awaiting deletion]<br />
<br />
== waiting for ==<br />
Per GTD, here are next-actions for admins that are awaiting some external dependency.<br />
<br />
Waiting-for: <br />
* Upgrade the MediaWiki to a new enough version for IndieAuth plugin to work (that is in use on indieweb.org) In order to:<br />
** install and make available IndieAuth login, as a replacement for OpenID login (previously requested by a while ago from [[User:DanC]] and [[User:Chris_Messina]] (especially for comments in WordPress). [[User:Chris_Messina]] 16:50, 31 Aug 2007 (PDT))<br />
** check that [[Special:Renameuser]] exists as a page (should for any Mediawiki 1.18 or later by default, without needing https://www.mediawiki.org/wiki/Extension:Renameuser)<br />
*** ping [[Tantek]] to finish user renaming fix.<br />
<br />
== someday maybe ==<br />
Per GTD, here are parked and otherwise deemed low-priority next-actions and projects for admins.<br />
<br />
=== someday actions ===<br />
* Make the edit comment UI better — textarea, not single line box. (Dev Status: Might be impossible without hacking the core)<br />
<br />
=== someday maybe projects ===<br />
==== improved issue tracking ====<br />
<div class="discussion"><br />
Issue tracking at microformats.org is poor. The wiki is difficult to track, resolutions get lost. A proper bug tracking system is desirable: However, the adminstration overhead of our current infrastructure is too high for volunteers. Questionable whether maintain another custom install of something is the direct we want to move in.<br />
* I don't think this is worth pursuing - issue tracking systems are notoriously problematic, and at least with the wiki, editing/resolving many issues at once is far more efficient - and efficiency for microformats maintainers is an important priority since all this work is all-volunteer. [[User:Tantek|Tantek]] 02:38, 10 September 2009 (UTC)<br />
* I think there are a few benefits to having a tracker. The primary one is simply to track proposals and have an easy platform for people to suggest new ones. That way there is a decent place for a high-level overview of what is going on. But, all of the suggested solutions suck. If it is to be done, we should investigate a custom built tracker for our needs. [[User:Garbee|Garbee]] 00:43, 3 June 2013 (UTC)<br />
* Note that a few specs have started tracking issues on GitHub, e.g. [[h-entry]] [[User:Aaronpk|Aaronpk]] 21:47, 4 December 2017 (UTC)<br />
</div><br />
<br />
* Investigate possibility/feasibility of using Launchpad/Github/Google Code for spec issue tracking<br />
* Wiki is excellent documentation tool. Terrible issue tracking tool.<br />
* External services avoid large maintenance burden<br />
* Could better handle this todo list<br />
* Better handle issue resolutions<br />
* Better handle issue discussions<br />
<br />
* Evaluate options<br />
** Consider integration points with µf.org<br />
** Consider open standards a plus (OpenID)<br />
** Consider effort in porting existing content<br />
* Copy over issues from each wiki page as standalone bugs<br />
* Ensure that each spec editor is added with suitable authorities to manage issues<br />
<br />
=====Custom Install of Trac=====<br />
* + Reliable<br />
* + Well Established<br />
* + Can customise to look like µf.org<br />
* + Flexible milestones etc.<br />
* + Hook into source repository of our choosing<br />
* + OpenID support<br />
* + Support whatever licensing we like<br />
* - Administration overhead<br />
<br />
Need to check permissions structures. Can the hCard editor have control over /hcard, but not over /haudio? Do we care?<br />
<br />
=====Google Code=====<br />
Chris Messina has ‘microformats’ on Google Code<br />
<br />
* + Reliably Hosted, minimal admin overhead<br />
* + Very flexible milestones/tagging<br />
* + SVN repository for test cases, libraries<br />
* - Can't be styled to µf.org<br />
* - No OpenID<br />
* - Ugly as sin<br />
* - No Public Domain license support<br />
<br />
=====Launchpad=====<br />
Ben Ward has ‘microformats’ on Launchpad<br />
<br />
* + BZR repository for test cases, libraries<br />
* + Public Domain License Support<br />
* - Not instantly intuitive<br />
* - Seems better suited to software than specifications<br />
* - Can't style like µf.org, but, quite pretty<br />
* - No OpenID<br />
<br />
=====Github=====<br />
* + Git repository for test cases, libraries<br />
* + Issue tracking is integrated<br />
* - No OpenID<br />
<br />
<br />
== done ==<br />
<br />
Admins Mailing list deliverability<br />
* the last admins mailing was put in spam for kevinmarks@gmail.com by gmail for unclear reasons<br />
** it was labelled: 'security: microformats.org did not encrypt this message link to support.google.com/mail?hl=en&p=tls '<br />
** Authentication-Results: mx.google.com;<br />
dkim=neutral (body hash did not verify) header.i=@gmail.com header.s=20161025 header.b=NpEH0xA1;<br />
spf=pass (google.com: best guess record for domain of microformats-admin-bounces@microformats.org designates 64.207.154.205 as permitted sender) smtp.mailfrom=microformats-admin-bounces@microformats.org<br />
* 2020-07-18 the admin mailing list has been moved to [https://groups.google.com/u/0/g/uf-admin Google Groups] [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]])<br />
<br />
=== server migration project ===<br />
<br />
The best option to upgrade everything on the server is to set up a new server and move everything onto it, then switch the DNS over when it's ready. Here is the current status of what we need to do in order to complete this.<br />
<br />
This migration has been completed! [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)<br />
<br />
==== blog ====<br />
The home page and blog are powered by WordPress. Thankfully WordPress does a pretty good job of providing an upgrade path. We can move the wordpress files to a new server to test this out before doing anything live.<br />
<br />
tasks that need a volunteer:<br />
* check that the theme works in a new version of WordPress<br />
* check that the current WordPress database can handle being upgraded to new WordPress<br />
<br />
If you would like to help out with either of these, get in touch with [https://aaronparecki.com aaronpk] and he can provide you with a copy of the files.<br />
<br />
==== wiki ====<br />
MediaWiki has a good upgrade path that will run database migrations, so it should be possible to restore the database into a new copy of the wiki. <br />
<br />
Things to check:<br />
<br />
* are there any extensions currently installed that we still need (some of them provide functionality that has since been moved into MW core), and do those extensions run under the latest MW<br />
** is there a new recaptcha plugin? some other way to prevent spam accounts?<br />
** (please list out more extensions here)<br />
* does the current theme work in new MediaWiki? and if not, do we revert to the default Vector theme?<br />
* I've reviewed the current plugins and made some upgrade notes on [[mediawiki_customization#Upgrade_MediaWiki]] as of 2018-10. [[User:GRegorLove|gRegor]] 20:01, 31 May 2019 (UTC)<br />
<br />
=== web server ===<br />
==== HTTPS ====<br />
HTTPS / TLS / SSL support:<br />
* Obtain and implement a TLS certificate (perhaps from Let's Encrypt?) for microformats.org and 301 redirect HTTP requests to HTTPS.<br />
<br />
==== upgrade PHP ====<br />
* Investigate an upgrade of PHP <br />
** PHP 5.6 active support ended 2017-01-19 and security support will end 2018-12-31 [http://php.net/supported-versions.php]. Upgrading to PHP7 might be a good idea currently. [[User:GRegorLove|gRegor]] 19:40, 9 May 2017 (UTC)<br />
** +1 agreed. [[User:Pfefferle|Pfefferle]] 17:58, 28 June 2018 (UTC)<br />
** this will be taken care of in the server migration project above [[User:Aaronpk|Aaronpk]] 18:27, 15 February 2019 (UTC)<br />
* The server is running PHP 7.4 now [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)<br />
<br />
=== wiki problems ===<br />
===== reCAPTCHA replacement =====<br />
reCAPTCHA replacement needed<br />
* had to edit out the https from a link above to get this to save.<br />
* reCAPTCHA has been removed, account creation currently requires contacting an admin [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)<br />
<br />
===== MediaWiki needs updating =====<br />
MediaWiki needs updating<br />
* Last time update attempt broke the theme, didn't have time time debug and fix. - [[User:BenWard]]<br />
** The IndieWeb wiki had the same problem, our resolution was to just drop the custom theme and switch to the default Vector theme. [[User:Aaronpk|Aaronpk]] 21:48, 4 December 2017 (UTC)<br />
* The wiki has been updated, reverted to the default Vector theme [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]]) 17:23, 19 July 2020 (UTC)<br />
<br />
== related ==<br />
* [[to-do]]<br />
* [[admins]]<br />
* [[admin-how-to]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=admin-to-do&diff=70218admin-to-do2020-07-19T17:17:44Z<p>Aaronpk: admin mailing list moved</p>
<hr />
<div>{{DISPLAYTITLE:admin to-do}}<br />
Filtered and processed [[to-do]] items specifically for [[admins]].<br />
<br />
Only [[admins]] should edit this page with non-minor edits.<br />
<br />
Please add to-do suggestions for admins to the general [[to-do#Admins|to-do page's Admins section]]. Thanks!<br />
<br />
Items here may list who originally suggested the item on the [[to-do]] page.<br />
<br />
Related: [[admin-how-to]].<br />
<br />
== inbox ==<br />
Per GTD, here are inbox items that seem reasonable and thus have been moved here by admins from the [[to-do#Admins|to-do page's Admins section]].<br />
<br />
Mirror server requests:<br />
* Note that requests from 88.190.13.197 are for a mirror server run by [[User:Neuro|neuro]] at 88.190.224.126.<br />
* ...<br />
<br />
<br />
== server migration project ==<br />
<br />
The best option to upgrade everything on the server is to set up a new server and move everything onto it, then switch the DNS over when it's ready. Here is the current status of what we need to do in order to complete this.<br />
<br />
=== blog ===<br />
The home page and blog are powered by WordPress. Thankfully WordPress does a pretty good job of providing an upgrade path. We can move the wordpress files to a new server to test this out before doing anything live.<br />
<br />
tasks that need a volunteer:<br />
* check that the theme works in a new version of WordPress<br />
* check that the current WordPress database can handle being upgraded to new WordPress<br />
<br />
If you would like to help out with either of these, get in touch with [https://aaronparecki.com aaronpk] and he can provide you with a copy of the files.<br />
<br />
=== wiki ===<br />
MediaWiki has a good upgrade path that will run database migrations, so it should be possible to restore the database into a new copy of the wiki. <br />
<br />
Things to check:<br />
<br />
* are there any extensions currently installed that we still need (some of them provide functionality that has since been moved into MW core), and do those extensions run under the latest MW<br />
** is there a new recaptcha plugin? some other way to prevent spam accounts?<br />
** (please list out more extensions here)<br />
* does the current theme work in new MediaWiki? and if not, do we revert to the default Vector theme?<br />
<br />
* I've reviewed the current plugins and made some upgrade notes on [[mediawiki_customization#Upgrade_MediaWiki]] as of 2018-10. [[User:GRegorLove|gRegor]] 20:01, 31 May 2019 (UTC)<br />
<br />
== next actions and projects ==<br />
Per GTD, here are processed next-actions for admins, grouped by area/project<br />
<br />
* [[events/2008-03-10-sxsw-admins-meetup#next_actions|next-actions from 2008-03-10 sxsw admins meetup]]<br />
** noted here for tracking purposes.<br />
*** This was a very long time ago - we need to reprocess this item to see what is still relevant >5 years later! - [[User:Tantek|Tantek]] 13:33, 15 September 2013 (UTC)<br />
<br />
=== web server ===<br />
==== HTTPS ====<br />
HTTPS / TLS / SSL support:<br />
* Obtain and implement a TLS certificate (perhaps from Let's Encrypt?) for microformats.org and 301 redirect HTTP requests to HTTPS.<br />
<br />
==== upgrade PHP ====<br />
* Investigate an upgrade of PHP <br />
** PHP 5.6 active support ended 2017-01-19 and security support will end 2018-12-31 [http://php.net/supported-versions.php]. Upgrading to PHP7 might be a good idea currently. [[User:GRegorLove|gRegor]] 19:40, 9 May 2017 (UTC)<br />
** +1 agreed. [[User:Pfefferle|Pfefferle]] 17:58, 28 June 2018 (UTC)<br />
** this will be taken care of in the server migration project above [[User:Aaronpk|Aaronpk]] 18:27, 15 February 2019 (UTC)<br />
<br />
=== irc ===<br />
* Pibb integration for the #microformats IRC channel. It is relatively simple to [http://janrain.com/blog/2007/08/08/how-to-embed-pibb/ embed the Pibb chat widget] into a webpage that bridges to the #microformats IRC channel. This would allow for greater access and transparency to the IRC discussions as well as allow people to participate using only their web browser. [[User:Chris_Messina]] 16:50, 31 Aug 2007 (PDT)<br />
<br />
* maintainer for [[mfbot]]. Ryan King has indicated that he no longer has time to maintain [[mfbot]] and would like another admin to pick up the maintenance and running of mfbot.<br />
<br />
* The https://indieweb.org/discuss options and Loqi cover these needs currently. [[User:GRegorLove|gRegor]] 19:43, 9 May 2017 (UTC)<br />
<br />
=== web site ===<br />
==== home page ====<br />
Main site home page:<br />
* The microformats2 page, should also be referred from the main page of the website http://microformats.org/ like perhaps a new small right box in between "What are microformats?" and "Microformat specifications" saying something like "Microformat version" as a title and place both versions, the old one is the latest with a short description, and the new one should be imediately under the title, with the same description below.<br />
** +1 agreed. We need a home page redesign with at least this, maybe also @microformats tweets. [[User:Tantek|Tantek]] 13:32, 15 September 2013 (UTC)<br />
<br />
ex: [http://screencast.com/t/77YHGASumqm Homepage with the right box implemented] .<br />
<br />
==== blog ====<br />
* Update Blog-Theme to support [[microformats2]]: Publish the microformats theme on GitHub to enable community contributions. See IRC discussion: <nowiki>https://chat.indieweb.org/microformats/2018-06-28#t1530196357894800</nowiki>.<br />
** Todo: Publish all theme sources on GitHub: <nowiki>https://chat.indieweb.org/microformats/2018-06-28/1530198611202600</nowiki><br />
<br />
=== wiki ===<br />
==== proper redirects to avoid dupes ====<br />
Wiki area suggestion:<br />
*Wiki creates duplicate content by allowing duplicate pages for microformats2: the main one is http://microformats.org/wiki/microformats2 and the other one is http://microformats.org/wiki/microformats-2 .<br />
<br />
To eliminate this problem, the 2nd page http://microformats.org/wiki/microformats-2, in the <head> section of the source code, should contain the following line <link rel="canonical" href="http://microformats.org/wiki/microformats2" />. This will tell Search Engines that this page is a duplicate content, thus it won't be indexed.<br />
<br />
This implementation should be done on all other duplicate content pages of the website.<br />
<br />
* This sounds like a good request. Is there a MediaWiki extension/plugin for adding rel=canonical to redirect handling pages? - [[User:Tantek|Tantek]] 13:32, 15 September 2013 (UTC)<br />
** MediaWiki has a config for this as of v1.21.0. Reference: <nowiki>https://www.mediawiki.org/wiki/Manual:$wgEnableCanonicalServerLink</nowiki> [[User:GRegorLove|gRegor]] 01:14, 21 June 2018 (UTC)<br />
** IIRC new MediaWiki has an option to do real redirects as well [[User:Aaronpk|Aaronpk]] 18:27, 15 February 2019 (UTC)<br />
<br />
==== for site update to microformats2 ====<br />
* about<br />
** create [[about]] from updated version of http://microformats.org/about<br />
** change "about" link to /wiki/about<br />
<br />
* get-started<br />
** update [[get-started]] with info from http://microformats.org/2014/03/05/getting-started-with-microformats2<br />
<br />
===== update wiki skin to mf2 =====<br />
See: <br />
* https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Skinning<br />
* update the microformats MediaWiki skin from using [[hAtom]] (e.g. 'hentry' class name) to [[h-entry]]<br />
* update any other classic microformats markup in the skin to mf2<br />
* under a new MediaWiki version we may have to do this with the Vector theme instead of the current theme. I can do the same thing I did with the IndieWeb wiki here as well if that's where we end up. [[User:Aaronpk|Aaronpk]] 18:27, 15 February 2019 (UTC)<br />
<br />
==== more spec styling ====<br />
We have [[specifications]] and [[draft specifications]] which add classnames to the body element ("specification" and "specification draft" respectively), which are then styled by the skin to look more spec-like.<br />
<br />
We should do the same for [[stub specifications]] and update [[process]] accordingly as well.<br />
<br />
==== wiki problems ====<br />
Problems with the microformats wiki that an admin needs to look at and resolve:<br />
===== reCAPTCHA replacement =====<br />
reCAPTCHA replacement needed<br />
* had to edit out the https from a link above to get this to save.<br />
<br />
===== MediaWiki needs updating =====<br />
MediaWiki needs updating<br />
* Last time update attempt broke the theme, didn't have time time debug and fix. - [[User:BenWard]]<br />
** The IndieWeb wiki had the same problem, our resolution was to just drop the custom theme and switch to the default Vector theme. [[User:Aaronpk|Aaronpk]] 21:48, 4 December 2017 (UTC)<br />
<br />
===== Password reset page problems =====<br />
Password reset page doesn't work:<br />
* http://microformats.org/wiki/Special:PasswordReset<br />
* as of 2015-06-15, this is still a problem and is now affecting users. [http://logs.glob.uno/?c=freenode%23microformats&s=15+Jun+2015&e=15+Jun+2015#c81446 relevant irc log]<br />
<br />
==== wiki documentation ====<br />
Need more documentation about how we have the wiki setup, so more [[admins]] are able to fix/update it.<br />
* Update our [[mediawiki customization]] documentation with specifically:<br />
** What plug-ins/add-ons are installed?<br />
** What customizations / patches have been made to MediaWiki?<br />
** What special things does the microformats mediawiki theme depend on?<br />
** [[User:BenWard]] likely best knows these things.<br />
<br />
==== wiki feature requests ====<br />
===== handle feedback =====<br />
* Process [[wiki-feedback]] and add items here accordingly.<br />
===== spam fighting =====<br />
* Install [https://www.mediawiki.org/wiki/Extension:AbuseFilter AbuseFilter]. This would allow admins to set up custom rules (similar to email rules like in Outlook/Thunderbird/Gmail etc.) that could be adapted to current spam on-the-fly.<br />
* Install [http://www.mediawiki.org/wiki/Extension:TitleBlacklist TitleBlackList Extension] and then block creation of pages with "http:" or ".com" in the title to stop spammers from creating autolinks in the IRC logs of wiki edits.<br />
* Consider additional mediawiki.org anti-spam strategies: https://www.mediawiki.org/wiki/Manual:Combating_spam (from Tom Morris)<br />
** also: add reCAPTCHA setting for ConfirmEdit and SimpleAntiSpam (GPHemsley added them to the WAHTWG wiki on 2012-296)<br />
<br />
===== semantic requests =====<br />
* Try adding https://github.com/microformats/LinkAttributes to our wiki install to permit rel and class on links in wiki pages.<br />
* Add Extensions - especially those that help implement more microformats on the wiki itself!<br />
** Evaluate against Wikipedia's [http://en.wikipedia.org/wiki/Special:Version Version Page] for a list of currently installed extensions on the English Wikipedia.<br />
** I'd personally advise getting [http://www.mediawiki.org/wiki/Extension:Cite Cite], [http://meta.wikimedia.org/wiki/ParserFunctions ParserFunctions] --[[User:JimboJW|JimboJW]] 13:38, 25 Sep 2007 (PDT) (Syntax Highlighting is done in Wiki 2.0)<br />
** [http://www.mediawiki.org/wiki/Extension:HTML_Profiles HTML Profiles] - allows people editing the wiki to add URIs to <code>&lt;head profile></code> [[User:TobyInk|TobyInk]] 16:52, 9 March 2009 (UTC)<br />
*** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
** [http://www.mediawiki.org/wiki/Extension:Link_Attributes Link Attributes] - allows easy-ish setting of rel/rev/class attributes on links. [[User:TobyInk|TobyInk]] 16:52, 9 March 2009 (UTC)<br />
*** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
* add a class, <code>noprint</code> to the site's CSS, so that sections (such as "related pages" footers) can be made non- printing.<br />
** ‘noprint’ isn't so semantic, but we should get a proper print stylesheet, for sure.<br />
* Allow <kbd>webcal://</kbd>, <kbd>javascript:</kbd> (for posting [[favelets]]/bookmarklets on the wiki) and perhaps (other) x-protocols to be linkified<br />
** +1 [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
* Would be great to have a video template that embeds an object. [[User:Tantek|Tantek]] 09:58, 25 June 2009 (UTC)<br />
* Can we imply <code>entry-title</code> from <code>h1</code>? [[User:Tantek|Tantek]]<br />
<br />
===== misc requests =====<br />
* Set up a cron job to export the wiki database (without user details), and make it available in a public location.<br />
* Install creation template extension(s)(see: http://meta.wikimedia.org/wiki/Inputbox or http://www.mediawiki.org/wiki/Extension:CreateBox or http://www.mediawiki.org/wiki/Extension:CreateArticle) [[User:RobManson]] 14:00, 20 Jul 2007 (AEST)<br />
* Add admins sidebar (quick ban list access)<br />
* Do something to allow easy copying of sample input (e.g. add ‘Copy’ UI, or abuse <code>input</code> element<br />
* Fix MediaWiki to lowercase URLs — especially fragment identifiers generated from headings. Content ''should not'' be sub-optimally edited according to the requirements of the CMS.<br />
* Update the interwiki-links table to allow for sensible linking to other wikis doing similar work. See [https://www.mediawiki.org/wiki/Manual:Interwiki help page on mediawiki.org] and [http://microformats.org/wiki/api.php?action=query&meta=siteinfo&siprop=interwikimap current interwikimap as XML from MediWiki API].<br />
** some plausible interwiki links: Wikipedia and other Wikimedia sites, IndieWebCamp, W3C Wiki, WHATWG wiki.<br />
<br />
=== forum ===<br />
In the past there have been requests (e.g. on the lists) for an online forum for microformats discussions.<br />
<br />
If there is an admin who's interested in helping run a forum (has the time to community manage it), take a look at:<br />
<br />
* consider create a new forum on microformats.org<br />
** e.g. install http://vanillaforums.org/ (Geoloqi uses it successfully on https://community.geoloqi.com/ and highly recommends it)<br />
<br />
== ongoing ==<br />
Ongoing and as neeeded duties/tasks:<br />
<br />
* Delete spam and block spammers from the wiki.<br />
* Send emails to the microformats list(s) guiding the community per our [[mailing-lists]] guidelines.<br />
* Helped out with questions on [[IRC]]<br />
* Accepted / filtered comments on the blog (or posted!)<br />
* Help with web server matintenence:<br />
** Apache (reboot Apache if it hangs, debug Apache server problems)<br />
** WordPress (including upgrading installs as needed)<br />
** Mailman (clearing of internal spam queues)<br />
** MediaWiki (upgrades, help package mods for resubmission back to core)<br />
* Provide guidance to other admins<br />
* Remove [http://microformats.org/wiki?title=Special:Whatlinkshere&target=delete pages awaiting deletion]<br />
<br />
== waiting for ==<br />
Per GTD, here are next-actions for admins that are awaiting some external dependency.<br />
<br />
Waiting-for: <br />
* Upgrade the MediaWiki to a new enough version for IndieAuth plugin to work (that is in use on indieweb.org) In order to:<br />
** install and make available IndieAuth login, as a replacement for OpenID login (previously requested by a while ago from [[User:DanC]] and [[User:Chris_Messina]] (especially for comments in WordPress). [[User:Chris_Messina]] 16:50, 31 Aug 2007 (PDT))<br />
** check that [[Special:Renameuser]] exists as a page (should for any Mediawiki 1.18 or later by default, without needing https://www.mediawiki.org/wiki/Extension:Renameuser)<br />
*** ping [[Tantek]] to finish user renaming fix.<br />
<br />
== someday maybe ==<br />
Per GTD, here are parked and otherwise deemed low-priority next-actions and projects for admins.<br />
<br />
=== someday actions ===<br />
* Make the edit comment UI better — textarea, not single line box. (Dev Status: Might be impossible without hacking the core)<br />
<br />
=== someday maybe projects ===<br />
==== improved issue tracking ====<br />
<div class="discussion"><br />
Issue tracking at microformats.org is poor. The wiki is difficult to track, resolutions get lost. A proper bug tracking system is desirable: However, the adminstration overhead of our current infrastructure is too high for volunteers. Questionable whether maintain another custom install of something is the direct we want to move in.<br />
* I don't think this is worth pursuing - issue tracking systems are notoriously problematic, and at least with the wiki, editing/resolving many issues at once is far more efficient - and efficiency for microformats maintainers is an important priority since all this work is all-volunteer. [[User:Tantek|Tantek]] 02:38, 10 September 2009 (UTC)<br />
* I think there are a few benefits to having a tracker. The primary one is simply to track proposals and have an easy platform for people to suggest new ones. That way there is a decent place for a high-level overview of what is going on. But, all of the suggested solutions suck. If it is to be done, we should investigate a custom built tracker for our needs. [[User:Garbee|Garbee]] 00:43, 3 June 2013 (UTC)<br />
* Note that a few specs have started tracking issues on GitHub, e.g. [[h-entry]] [[User:Aaronpk|Aaronpk]] 21:47, 4 December 2017 (UTC)<br />
</div><br />
<br />
* Investigate possibility/santity of using Launchpad/Github/Google Code for spec issue tracking<br />
* Wiki is excellent documentation tool. Terrible issue tracking tool.<br />
* External services avoid large maintenance burden<br />
* Could better handle this todo list<br />
* Better handle issue resolutions<br />
* Better handle issue discussions<br />
<br />
* Evaluate options<br />
** Consider integration points with µf.org<br />
** Consider open standards a plus (OpenID)<br />
** Consider effort in porting existing content<br />
* Copy over issues from each wiki page as standalone bugs<br />
* Ensure that each spec editor is added with suitable authorities to manage issues<br />
<br />
=====Custom Install of Trac=====<br />
* + Reliable<br />
* + Well Established<br />
* + Can customise to look like µf.org<br />
* + Flexible milestones etc.<br />
* + Hook into source repository of our choosing<br />
* + OpenID support<br />
* + Support whatever licensing we like<br />
* - Administration overhead<br />
<br />
Need to check permissions structures. Can the hCard editor have control over /hcard, but not over /haudio? Do we care?<br />
<br />
=====Google Code=====<br />
Chris Messina has ‘microformats’ on Google Code<br />
<br />
* + Reliably Hosted, minimal admin overhead<br />
* + Very flexible milestones/tagging<br />
* + SVN repository for test cases, libraries<br />
* - Can't be styled to µf.org<br />
* - No OpenID<br />
* - Ugly as sin<br />
* - No Public Domain license support<br />
<br />
=====Launchpad=====<br />
Ben Ward has ‘microformats’ on Launchpad<br />
<br />
* + BZR repository for test cases, libraries<br />
* + Public Domain License Support<br />
* - Not instantly intuitive<br />
* - Seems better suited to software than specifications<br />
* - Can't style like µf.org, but, quite pretty<br />
* - No OpenID<br />
<br />
=====Github=====<br />
* + Git repository for test cases, libraries<br />
* + Issue tracking is integrated<br />
* - No OpenID<br />
<br />
<br />
== done ==<br />
<br />
Admins Mailing list deliverability<br />
* the last admins mailing was put in spam for kevinmarks@gmail.com by gmail for unclear reasons<br />
** it was labelled: 'security: microformats.org did not encrypt this message link to support.google.com/mail?hl=en&p=tls '<br />
** Authentication-Results: mx.google.com;<br />
dkim=neutral (body hash did not verify) header.i=@gmail.com header.s=20161025 header.b=NpEH0xA1;<br />
spf=pass (google.com: best guess record for domain of microformats-admin-bounces@microformats.org designates 64.207.154.205 as permitted sender) smtp.mailfrom=microformats-admin-bounces@microformats.org<br />
* 2020-07-18 the admin mailing list has been moved to [https://groups.google.com/u/0/g/uf-admin Google Groups] [[User:Aaronpk|Aaronpk]] ([[User talk:Aaronpk|talk]])<br />
<br />
<br />
== related ==<br />
* [[to-do]]<br />
* [[admins]]<br />
* [[admin-how-to]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=yandex-search&diff=70217yandex-search2020-07-18T16:35:46Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:Yandex Search Engine}}<br />
<br />
{{stub}}<br />
<br />
== summary ==<br />
<br />
The [http://www.yandex.com/ Yandex] search engine supports [[hCard]], [[hRecipe]], [[hReview]], and [[hProduct]] microformats in main search, per [http://help.yandex.ru/webmaster/?id=1111670 Что такое микроформаты] (English: [http://translate.googleusercontent.com/translate_c?hl=en&ie=UTF8&prev=_t&rurl=translate.google.com&sl=ru&tl=en&twu=1&u=http://help.yandex.ru/webmaster/%3Fid%3D1111670 What are microformats]).<br />
<br />
Yandex launched their microformats support as of [http://lists.w3.org/Archives/Public/public-vocabs/2012Feb/0089.html at least 2012-02-24] or earlier.<br />
<br />
== supported formats ==<br />
Yandex supports the following microformats:<br />
* [[hCard]] ([http://help.yandex.ru/webmaster/?id=1111573])<br />
* [[hRecipe]] ([http://help.yandex.ru/webmaster/?id=1111981])<br />
* [[hReview]] ([http://help.yandex.ru/webmaster/?id=1113262])<br />
* [[hProduct]] ([http://help.yandex.ru/webmaster/?id=1113264])<br />
<br />
== validator ==<br />
{{main|validators}}<br />
In addition, Yandex has a [http://webmaster.yandex.ru/microtest.xml microformats validator] as well.<br />
<br />
== articles ==<br />
* http://www.step-up-web.ru/hcard/<br />
<br />
== see also ==<br />
* [[search]]<br />
* [[validators]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=yahoo-search-fr&diff=70216yahoo-search-fr2020-07-18T16:35:45Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:Yahoo Recherche}}<br />
<br />
Yahoo est l'un des nombreux [[search-engines-fr|moteurs de recherche]] qui indexe et supporte les microformats.<br />
<br />
== recherche principale ==<br />
[http://search.yahoo.com/ search.yahoo.com] supporte [[rel-nofollow-fr|rel-no-follow]] (depuis 2005 (?) citation demandée).<br />
<br />
== recherche avancée ==<br />
A travers des interfaces utilisateurs supplémentaires :<br />
* [http://search.yahoo.com/cc Yahoo Creative Commons search] supporte [[rel-license-fr|rel-license]]<br />
<br />
== APIs de recherche et outils ==<br />
Yahoo fournit des APIs de recherche comme :<br />
=== BOSS ===<br />
* [http://developer.yahoo.com/search/boss/ Yahoo Search BOSS]<br />
** Au moment de faire appel à l'API de recherche web BOSS, vous pouvez retrouver toute la donnée structurée que Yahoo! a extrait pour les URLs spécifiées via SearchMonkey, y compris tous les microformats. Ajoutez simplement les paramètres "view=searchmonkey_feed&format=xml" pour votre appel de l'API de recherche web. C'est probablement le moyen le plus efficace de rapatrier de l'information structurée à partir de Yahoo!.<br />
** [http://www.bosshacks.com/build-semantic-search-boss.html Construire un Moteur de Recherche Sémantique avec BOSS]] documente comment utiliser l'API BOSS de Yahoo! pour accéder au SearchMonkey Yahoo! qui supporte les microformats [[hatom-fr|hAtom]], [[hcalendar-fr|hCalendar]], [[hcard-fr|hCard]], [[hreview-fr|hReview]], [[xfn-fr|XFN]], [[geo-fr|geo]], [[rel-tag-fr|rel-tag]], [[adr-fr|adr]].<br />
<br />
=== SearchMonkey ===<br />
[http://developer.yahoo.net/blog/archives/2008/06/monkey_microformat.html Yahoo SearchMonkey] supporte [[hcard-fr|hCard]], [[hcalendar-fr|hCalendar]], [[hreview-fr|hReview]], [[hatom-fr|hAtom]], et d'autres - lancé en mai 2008. SearchMonkey est le programme de Yahoo! pour collecter et afficher de la donnée structurée, incluant les microformats.<br />
* Vous pouvez inspecter le microformat et d'autres données structurées rassemblées par SearchMonkey en allant sur [http://developer.search.yahoo.com SearchMonkey Developer Tool]. Cependant, si vous êtes uniquement intéressé par de la donnée microformat (par ex. vous ne prévoyez pas de construire une application complète [http://gallery.search.yahoo.com/ SearchMonkey]), il est plus efficace d'utiliser BOSS ou YQL.<br />
* Pour inspecter de la donnée structurée sur la page Yahoo! Search page, installez l'[http://gallery.search.yahoo.com/application?smid=NAo.s Barre d'Info d'Affichage de Donnée Structurée].<br />
* Filtrage Microformat sur Yahoo! Search : La forme générale est "searchmonkey:com.yahoo.page.uf.''<microformat>'' ''<termes complémentaires de requête>''". Par exemple, vous pourriez chercher toutes les pages avec un [[hresume-fr|hResume]] et le mot "php". Remarquez que "searchmonkey:" agit comme un filtre. Vous n'inspectez pas le contenu véritable du hResume ''pour'' le mot "php", vous cherchez toutes les pages qui A) ont hResume et B) seraient renvoyées par une Recherche Yahoo! ordinaire sur "php".<br />
** [http://search.yahoo.com/search?p=searchmonkey%3Acom.yahoo.page.uf.hcard recherche Yahoo de hCards]<br />
** [http://search.yahoo.com/search?p=searchmonkey%3Acom.yahoo.page.uf.hcalendar recherche Yahoo d'évenement hCalendar]<br />
** [http://search.yahoo.com/search?p=searchmonkey%3Acom.yahoo.page.uf.hreview recherche Yahoo de hReviews]<br />
** [http://search.yahoo.com/search?p=searchmonkey%3Acom.yahoo.page.uf.hatom recherche Yahoo de hAtom]<br />
** [http://search.yahoo.com/search?p=searchmonkey%3Acom.yahoo.page.uf.xfn recherche Yahoo de XFN]<br />
** [http://search.yahoo.com/search?p=searchmonkey%3Acom.yahoo.page.uf.hresume recherche Yahoo de hResume]<br />
** [http://search.yahoo.com/search?p=searchmonkey%3Acom.yahoo.page.uf.adr recherche Yahoo de adr]<br />
** [http://search.yahoo.com/search?p=searchmonkey%3Acom.yahoo.page.uf.geo recherche Yahoo de GEO]<br />
** [http://search.yahoo.com/search?p=searchmonkey%3Acom.yahoo.page.uf.tag recherche Yahoo de rel-tag]<br />
** Tous ces filtres microformats peuvent être utilisés tout aussi bien avec l'API BOSS.<br />
<br />
=== YQL ===<br />
[http://developer.yahoo.com/yql Yahoo Query Language] utilise une syntaxe comme-SQL pour "normaliser" les appels de service web. En plus d'inclure des services web tels que Flickr, Yelp, et Zillow, YQL vous permet aussi d'extraire le contenu directement à partir de vos pages web. Faisant partie de cette fonctionnalité, YQL peut [http://developer.yahoo.net/blog/archives/2009/01/yql_with_microformats.html requêter et filtrer sur les microformats]. Par exemple, la requête YQL : <br />
<br />
[http://query.yahooapis.com/v1/public/yql?q=select%20*%20from%20microformats%20where%20url%3D'http%3A%2F%2Fupcoming.yahoo.com%2Fvenue%2F23933%2F'&format=xml http://query.yahooapis.com/v1/public/yql?q=select * from microformats where url%3D'http%3A%2F%2Fupcoming.yahoo.com%2Fvenue%2F23933%2F'&format=xml]<br />
<br />
extrait tous les microformats provenant d'une page particulière sur upcoming.yahoo.com.<br />
<br />
''A la différence'' de BOSS et des filtres simples microformats décrits ci-dessus, vous pouvez utiliser YQL pour exécuter du filtrage det d'autres opérations sur la donnée microformat elle-même.<br />
<br />
== voir aussi ==<br />
* [[search-engines-fr|moteur de recherche]]<br />
* [[implementations-fr|implémentations]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=yahoo-search&diff=70215yahoo-search2020-07-18T16:35:45Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:Yahoo Search}}<br />
Yahoo used to have an independent search engine but switched to using Microsoft Bing (for the most part) [https://en.wikipedia.org/wiki/Yahoo!_Search#Search_technology_acquisition in 2010]. <br />
<br />
Previously: one of several independent [[search-engines]] that index and support microformats.<br />
<br />
== search site ==<br />
* <span id="main_search">[http://search.yahoo.com/ search.yahoo.com]</span> supports [[rel-nofollow]] (since 2005(?) citation needed).<br />
* <span id="advanced search">advanced search</span>. Through additional user interfaces:<br />
** [http://search.yahoo.com/cc Yahoo Creative Commons search] supported [[rel-license]] in the past.<br />
<br />
== search APIs and tools ==<br />
=== BOSS ===<br />
Yahoo supported a custom search API called BOSS until 2016-03-31 which had built-in microformats support.<br />
* [http://developer.yahoo.com/search/boss/ Yahoo Search BOSS]<br />
** When calling the BOSS web search API, you can retrieve all structured data Yahoo! has extracted for the specified URLs via SearchMonkey, including any microformats. Just add the parameters "view=searchmonkey_feed&format=xml" to your web search API call. This is probably the most efficient way to fetch structured data from Yahoo!.<br />
** [https://web.archive.org/web/20090517052503/http://www.bosshacks.com/build-semantic-search-boss.html Build a semantic Search Engine with BOSS] documents how to use Yahoo's BOSS API to access Yahoo SearchMonkey which supports the [[hAtom]], [[hCalendar]], [[hCard]], [[hReview]], [[XFN]], [[geo]], [[rel-tag]], [[adr]] microformats.<br />
<br />
=== SearchMonkey ===<br />
[https://web.archive.org/web/20090216094046/http://developer.yahoo.net:80/blog/archives/2008/12/monkey_finds_microformats_and_rdf.html Yahoo SearchMonkey] supported [[hCard]], [[hCalendar]], [[hReview]], [[hAtom]], others - [https://web.archive.org/web/20090216054934/http://developer.yahoo.net/blog/archives/2008/06/monkey_microformat.html launched 2008 May], [https://web.archive.org/web/20090216094046/http://developer.yahoo.net:80/blog/archives/2008/12/monkey_finds_microformats_and_rdf.html updated 2008-12-07], until it was [https://en.wikipedia.org/wiki/Yahoo!_SearchMonkey#End_of_Life shut down in 2010 October]. SearchMonkey was Yahoo!'s program for collecting and displaying structured data, including microformats.<br />
* You can inspect microformat and other structured data gathered by SearchMonkey by going to the [http://developer.search.yahoo.com SearchMonkey Developer Tool]. However, if you are only interested in microformat data (i.e. you are not planning on building a full-fledged [http://gallery.search.yahoo.com/ SearchMonkey application]), it is more efficient to use BOSS or YQL.<br />
* To inspect structured data directly on the Yahoo! Search page, install the [http://gallery.search.yahoo.com/application?smid=NAo.s Structured Data Display infobar].<br />
* Microformat filtering on Yahoo! Search: The general form is "searchmonkey:com.yahoo.page.uf.''<microformat>'' ''<additional query terms>''". For example, you could search for all pages with [[hResume]] and the word "php". Note that "searchmonkey:" acts as a filter. You aren't inspecting the actual hResume content ''for'' the word "php", you are searching for all pages that A) have hResume and B) would be returned by an ordinary Yahoo! Search for "php".<br />
** [http://search.yahoo.com/search?p=searchmonkey%3Acom.yahoo.page.uf.hcard search Yahoo for hCards] (all of these searches tell you how many Search Monkey has found)<br />
** [http://search.yahoo.com/search?p=searchmonkey%3Acom.yahoo.page.uf.hcalendar search Yahoo for hCalendar events]<br />
** [http://search.yahoo.com/search?p=searchmonkey%3Acom.yahoo.page.uf.hreview search Yahoo for hReviews]<br />
** [http://search.yahoo.com/search?p=searchmonkey%3Acom.yahoo.page.uf.hatom search Yahoo for hAtom]<br />
** [http://search.yahoo.com/search?p=searchmonkey%3Acom.yahoo.page.uf.xfn search Yahoo for XFN]<br />
** [http://search.yahoo.com/search?p=searchmonkey%3Acom.yahoo.page.uf.hresume search Yahoo for hResume]<br />
** [http://search.yahoo.com/search?p=searchmonkey%3Acom.yahoo.page.uf.adr search Yahoo for adr]<br />
** [http://search.yahoo.com/search?p=searchmonkey%3Acom.yahoo.page.uf.geo search Yahoo for GEO]<br />
** [http://search.yahoo.com/search?p=searchmonkey%3Acom.yahoo.page.uf.tag search Yahoo for rel-tag]<br />
** All of these microformat filters can be used with the BOSS API as well.<br />
<br />
=== YQL ===<br />
[http://developer.yahoo.com/yql Yahoo Query Language] used a SQL-like syntax to "normalize" web service calls. In addition to wrapping web services such as Flickr, Yelp, and Zillow, YQL also enabled you to extract content directly from web pages. As part of that functionality, YQL could [https://web.archive.org/web/20100706144149/http://developer.yahoo.net/blog/archives/2009/01/yql_with_microformats.html query and filter on microformats] from <br />
[https://web.archive.org/web/20100706144149/http://developer.yahoo.net/blog/archives/2009/01/yql_with_microformats.html 2009-01-13] until [http://web.archive.org/web/20190110000110/https://developer.yahoo.com/yql/?guccounter=1 YQL shut down on 2019-01-03].<br />
<br />
For example, the YQL query:<br />
<br />
[http://query.yahooapis.com/v1/public/yql?q=select%20*%20from%20microformats%20where%20url%3D'http%3A%2F%2Fupcoming.yahoo.com%2Fvenue%2F23933%2F'&format=xml http://query.yahooapis.com/v1/public/yql?q=select * from microformats where url%3D'http%3A%2F%2Fupcoming.yahoo.com%2Fvenue%2F23933%2F'&format=xml]<br />
<br />
extracts all microformats from a particular page on upcoming.yahoo.com.<br />
<br />
''Unlike'' BOSS and the simple microformat filters described above, you can use YQL to perform filtering and other operations on the microformat data itself.<br />
<br />
== see also ==<br />
* [[search-engines]]<br />
* [[implementations]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xoxo-profile&diff=70214xoxo-profile2020-07-18T16:35:44Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:XOXO Profile}}<br />
<br />
The following is an [http://gmpg.org/xmdp/ XMDP] profile for the [[XOXO]] specification.<br />
<br />
== URLs ==<br />
This profile is hosted as a separate XMDP file on microformats.org:<br />
* http://microformats.org/profile/xoxo<br />
* shortURL: http://ufs.cc/x/xoxo<br />
<br />
== Usage ==<br />
Profiles are referenced in (X)HTML files in the &lt;HEAD&gt; tag, e.g.:<br />
<source lang=html4strict><br />
<head profile='http://microformats.org/profile/xoxo'><br />
</source><br />
<br />
== Profile ==<br />
<source lang=html4strict><br />
<dl class="profile"><br />
<dt>class</dt><br />
<dd><p><br />
<a rel="help" href="http://www.w3.org/TR/html401/struct/global.html#adef-class"><br />
HTML4 definition of the 'class' attribute.</a><br />
This meta data profile defines some 'class' attribute values (class names) <br />
and their meanings as suggested by a <br />
<a href="http://www.w3.org/TR/WD-htmllink-970328#profile"><br />
draft of "Hypertext Links in HTML"</a>:</p><br />
<dl><br />
<dt id="xoxo">xoxo</dt><br />
<dd>A XOXO outline as defined by the <br />
<a rel="help start" href="http://microformats.org/wiki/xoxo">XOXO specification</a>. <br />
Typically an ordered list &lt;ol&gt; or unordered list &lt;ul&gt; element.</dd><br />
<dt id="blogroll">blogroll</dt><br />
<dd>When used with the aforementioned 'xoxo' value, this value means <br />
a particular instance of a XOXO outline which has the additional semantic of being a <br />
<a href="http://en.wikipedia.org/wiki/Blogroll#B">blogroll</a>.<br />
</dd><br />
</dl><br />
</dd><br />
</dl> <br />
</source><br />
<br />
== Under Consideration ==<br />
<br />
See [[xoxo-brainstorming]] for additional class names under consideration, and please add your thoughts there.</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xoxo-ja&diff=70213xoxo-ja2020-07-18T16:35:41Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE: XOXO 1.0: Extensible Open XHTML Outlines }}<br />
<!-- english: 2008-12-16T17:03:01 --><br />
<br />
XOXOとは、標準的なXHTMLで書かれたシンプルでオープンなアウトラインフォーマットで、(X)HTML, Atom, RSS, そしてarbitrary XMLに組み込むのに適しています. XOXOは [[microformats|microformat]] オープンスタンダードの一つです.<br />
<br />
__TOC__<br />
<br />
== 仕様ドラフト 2004-10-01 ==<br />
<br />
=== 編者 ===<br />
[http://tantek.com/ Tantek Celik]([http://technorati.com Technorati, Inc])<br />
<br />
=== 作者 ===<br />
* [http://epeus.blogspot.com/ Kevin Marks]([http://technorati.com Technorati, Inc])<br />
* [http://tantek.com/ Tantek Celik]([http://technorati.com Technorati, Inc], formerly of [http://microsoft.com/ Microsoft Corporation])<br />
* [http://diveintomark.org/ Mark Pilgrim]([http://ibm.com IBM])<br />
* [http://www.blogologue.com/ Morten W. Petersen]<br />
<br />
=== 著作権 ===<br />
{{MicroFormatCopyrightStatement2003}}<br />
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.<br />
** When all authors/editors have done so, we can remove the MicroFormatCopyrightStatement template reference and replace it with the MicroFormatPublicDomainContributionStatement.<br />
<br />
=== 特許 ===<br />
{{MicroFormatPatentStatement-ja}}<br />
<br />
== あらすじ ==<br />
[http://developers.technorati.com/wiki/attentionxml Attention.xml]について話し合っていたとき、XHTMLで作るアウトラインおよびblogrollフォーマットの可能性をTantekが指摘しました。XHTMLで記述することにより、ブラウザで表示することも出来れば厳密なXML処理系でパースすることも可能です。このページはそのフォーマットについて考えるための場所として作られました。<br />
<br />
=== 名称 ===<br />
XOXOはeXtensible Open XHTML Outlinesの略称であり、「エックス オー エックス オー」、「ジョージョー」または「ショーショー」などと発音されています。<br />
<br />
== 要約 ==<br />
[[XOXO]] は[[microformats-ja|マイクロフォーマット]]の一つです。この仕様では、モジュールの骨格と、「XHTML のモジュール化」([http://www.w3.org/TR/xhtml-modularization XHTMLMOD])で定義されたモジュールに基づいて、新しい XHTML ドキュメントタイプを定義します。 XHTML として使いやすく、XML エンジンが処理してブラウザで簡単にインタラクティブな表示ができるようなアウトラインの土台となるのが XOXO の目的です。<br />
<br />
== XOXO ドキュメントタイプ ==<br />
XOXO ドキュメントタイプは次の XHTML モジュールで構成されます。このモジュールにある要素、属性、最小内容モデルは「XHTML のモジュール化」([http://www.w3.org/TR/xhtml-modularization XHTMLMOD])で定義されています。要素は情報を提示するためにここで一覧にしますが、最終的には「XHTML のモジュール化」での定義を参照するべきです。このドキュメントのオンライン版では、下の一覧のモジュール名を、「XHTML のモジュール化」現行バージョン内のモジュール定義へのリンクとしています。<br />
<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_structuremodule 構造モジュール(Structure Module)]<br />
body, head, html, title<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_hypertextmodule ハイパーテキストモジュール(Hypertext Module)]<br />
a<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_listmodule リストモジュール(List Module)]<br />
dl, dt, dd, ol, ul, li<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_metamodule メタ情報モジュール(Metainformation Module)]<br />
meta<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_stylemodule スタイルシートモジュール(Style Sheet Module)]<br />
style 要素<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_styleattributemodule スタイル属性モジュールモジュール(Style Attribute Module)]<br />
style 属性<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_linkmodule リンクモジュール(Link Module)]<br />
link<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_legacymodule レガシーモジュール(Legacy Module)]<br />
ol と ul での compact 属性<br />
<br />
=== XOXO プロファイル ===<br />
<br />
XOXO の class 属性用の値を定義した XOXO の [http://gmpg.org/xmdp XMDP] プロファイルは、[[xoxo-profile]] を参照してください。<br />
<br />
== 簡単な XOXO の断片 ==<br />
<br />
=== マークアップ ===<br />
<br />
<source lang="html4strict"><ol class='xoxo'><br />
<li>項目 1<br />
<ol><br />
<li>下位項目 a</li><br />
<li>下位項目 b</li><br />
</ol><br />
</li><br />
<li>項目 2<br />
<ol compact="compact"><br />
<li>下位項目 c</li><br />
<li>下位項目 d</li><br />
</ol><br />
</li><br />
<li>項目 3<br />
<ol><br />
<li>下位項目 e</li><br />
</ol><br />
</li><br />
</ol><br />
</source><br />
<br />
=== 表示例 ===<br />
<pre><nowiki><br />
1. 項目 1<br />
a. 下位項目 a<br />
b. 下位項目 b<br />
2. 項目 2<br />
3. 項目 3<br />
a. 下位項目 e<br />
</nowiki></pre><br />
=== 'compact' 属性の使用法 ===<br />
<br />
「項目 2」という見出しの下位項目が開いた状態ではない(訳注:折りたたまれた状態である)ことを示すために、'compact' 属性を使ったことに注意してください。そこ以外に 'compact' 属性は無いので、他の見出しは開いた状態です。<br />
<br />
=== 表示例のようになるデフォルトスタイルルールの一例 ===<br />
<br />
<source lang="css"><br />
ol.xoxo { list-style:decimal; }<br />
ol.xoxo ol { list-style:lower-latin; }<br />
ol[compact="compact"] { display:none; }<br />
</source><br />
<br />
<br />
== 別の簡単な例 ==<br />
<br />
<br />
マークアップが簡単なまま表現を豊かにすることが可能であることを示す、MarkP による例の一式があります。<br />
<br />
<br />
<br />
* [http://diveintomark.org/public/2004/01/xo-flat.xo XHTML ページに直接埋め込める XO ファイルの例]<br />
<br />
* [http://diveintomark.org/public/2004/01/xo-embeddable.xo グループを入れ子にした XO。これも XHTML に直接埋め込める]<br />
* [http://diveintomark.org/public/2004/01/xo-standalone.xo standalone XHTML ページとしての XO]([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-standalone.xo 妥当な XHTML です])<br />
* [http://diveintomark.org/public/2004/01/xo-with-style.xo CSS でレイアウトした standalone XHTML としての XO]([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-with-style.xo これも妥当な XHTML です])<br />
* [http://homepage.mac.com/ctholland/thelab/outlines/ Chris Holland Outline Helper]:上の例に手を加え、簡単のため CSS をコピーし、[http://homepage.mac.com/ctholland/thelab/outlines/outlines.css outlines.css] と [http://homepage.mac.com/ctholland/thelab/outlines/outlines.js outlines.js] への参照を追加して、compact 属性をつけた別の ul/ol/li を組み合わせて貼り付けた例<br />
** セマンティックな指針に適合させようとする時、ol や ul 要素の "compact" 属性は、表示状態を操作する物となります。スクリプトの中で、スタイルに柔軟性を持たせるために下位項目を持つ li 要素にクラスを設定しました。CSS の指導者的立場の人達は、「'compact' 属性が設定されている ol ノードを含む li ノードを選択する」他の CSS セレクターで "li.expanded" を置き換えられるかもしれません。<br />
*** 「'compact' 属性が設定されている ol ノードを含む li ノードを選択する」CSS セレクターは「li ol[compact="compact"」になるでしょう(訳注:このセレクターは目的のノードを選択しません)。<br />
<br />
== アウトライン項目のプロパティ ==<br />
アウトラインは通常、項目と下位項目で構成されます。各項目(アウトライン項目)自体に、表示する必要のある何らかのプロパティ(別の言い方をすれば属性、メタデータ)があるかもしれません。上の Mark Pilgrim の例にあるように、実際にアウトライン項目のプロパティとして共通して追加されるのは URL でしょう。テキストによるアウトライン項目のラベル/タイトルも共通のプロパティと考えることができます。共通プロパティを幾つか挙げます。<br />
* text(テキスト)<br />
* description(説明)<br />
* url(よく xmlurl や htmlurl と言われたり固定リンクと呼ばれる)<br />
* title(タイトル)<br />
* type(タイプ;URL が指しているリソースの MIME タイプのヒント)<br />
<br />
アウトライン項目 <code><nowiki><li></nowiki></code> のプロパティは、一般に入れ子になった定義リスト <code><nowiki><dl></nowiki></code> で表現されます。厳密に言うと、<code><nowiki><li></nowiki></code> の内側にあってその下にある全ての <code><nowiki><ol></nowiki></code>、<code><nowiki>&lt;ul&gt;</nowiki></code>、<code>&lt;li&gt;</code>の前にある最初の <code><nowiki><dl></nowiki></code> です。次の例では description(説明)プロパティを持つ「項目 1」という項目です(ここでの下位項目は、純粋に先ほどの例との比較用です)。<br />
<br />
<source lang="html4strict"><br />
<ol class='xoxo'><br />
<li>項目 1<br />
<dl><br />
<dt>description</dt><br />
<dd>この項目が、今考えている主要ポイントを示しています。</dd><br />
</dl><br />
<ol><br />
<li>下位項目 a</li><br />
<li>下位項目 b</li><br />
</ol><br />
</li><br />
</ol><br />
</source><br />
<br />
=== 特別なプロパティ ===<br />
定義リストの代わりに、セマンティックな XHTML ブロックの中にもっと便利で直接に表現できる特別なプロパティは少ししかありません。ほとんどの場合、上の共通プロパティの一覧から持ってこられます。次です。<br />
* text、url、title、type、rel(relationship;関係の省略形)<br />
<br />
これを単に(前の例では "description" プロパティを含んでいる)定義項目として表示するとしたら、次のようになるでしょう。<br />
<br />
議論のためだけで規範的ではない XOXO 例:<br />
<br />
<source lang="html4strict"><br />
<ol class='xoxo'><br />
<li><br />
<dl><br />
<dt>text</dt><br />
<dd>項目 1</dd><br />
<dt>description</dt><br />
<dd>この項目が、今考えている主要ポイントを示しています。</dd><br />
<dt>url</dt><br />
<dd>http://example.com/more.xoxo</dd><br />
<dt>title</dt><br />
<dd>項目 1 のタイトル</dd><br />
<dt>type</dt><br />
<dd>text/xml</dd><br />
<dt>rel</dt><br />
<dd>help</dd><br />
</dl><br />
</li><br />
</source><br />
<br />
ですがセマンティックな <code><a href></code> 要素を生かせば、このプロパティを利用する同じケースを飛躍的に簡単にすることができます。パーサーから見ると、これは <code><nowiki>&lt;li&gt;</nowiki></code> のすぐ内側にある <code><a href></code> 要素に適用されます。<br />
<br />
実際の XOXO 例:<br />
<br />
<source lang="html4strict"><br />
<ol class='xoxo'><br />
<li><a href="http://example.com/more.xoxo"<br />
title="項目 1 のタイトル"<br />
type="text/xml"<br />
rel="help">項目 1</a><br />
<!-- "text" プロパティが単に <a> 要素の内容になっていることに注意 --><br />
<dl><br />
<dt>description</dt><br />
<dd>この項目が、今考えている主要ポイントを示しています。</dd><br />
</dl><br />
</li><br />
</source><br />
<br />
他のプロパティは全て、"description" プロパティのように単純に定義リストに追加します。<br />
<br />
== XOXO の公開 ==<br />
<br />
XOXO は二つの形式で公開できます。妥当な XHTML と簡単な整形式 XML です。<br />
<br />
=== 妥当な XHTML の XOXO ===<br />
<br />
妥当な XHTML の XOXO ページは完全な XHTML 文書です。<br />
<br />
<source lang="html4strict"><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"<br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<meta http-equiv="content-type" content="text/html; charset=utf-8" /><br />
<title>XOXO ページ</title><br />
</head><br />
<body><br />
<ol class="xoxo"><br />
<li><a href="URL-one">テキスト1</a></li><br />
<li><a href="URL-two">テキスト2</a></li><br />
...<br />
</ol><br />
</body><br />
</html><br />
</source><br />
<br />
=== 簡単な整形式 XML の XOXO ===<br />
<br />
簡単な整形式 XML の XOXO ページのルート要素は "xoxo" という class 名を持つ <code>ol</code> か <code>ul</code> です。これは、配信と [[rest/ahah|AHAH]] による(X)HTML ページへのトランスクルージョンに理想的な変形版です。<br />
<br />
<source lang="xml"><br />
<ol class="xoxo"><br />
<li><a href="URL-one">テキスト1</a></li><br />
<li><a href="URL-two">テキスト2</a></li><br />
...<br />
</ol><br />
</source><br />
<br />
=== Content-Type ===<br />
<br />
妥当な、または整形式の XHTML の XOXO は、ブラウザの互換性を最大限にするため次の Content-Type ヘッダーを付けて提供するべきです(SHOULD)。<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
</nowiki></pre><br />
<br />
また、次の Content-Type ヘッダーのうち一つを付けて提供しなければなりません(MUST)。<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
Content-Type: application/xhtml+xml<br />
Content-Type: application/xml<br />
</nowiki></pre><br />
<br />
== 実世界での例 ==<br />
この節は'''参考情報'''です。<br />
<br />
実世界に例がたくさんあります。ブログロールはほとんど全て XOXO としてパースできます。通常ハイパーリンクの項目一覧という順序なしリストであり、それは XOXO プロファイルの範囲内だからです。ここに例を並べてください。リストが長くなりすぎた時には専用ページに移動させることができます。<br />
<br />
* [http://api.talis.com/bf/stores/ukbib/services/facet?query=feynman&fields=title%2Csubject&top=10&output=html 書籍データ切り出しサービス(ファセットサービス)の HTML アウトプット]<br />
<br />
== 実装 ==<br />
この節は'''参考情報'''です。<br />
<br />
* 各種 [[s5-tools|S5 ツール]]<br />
* [http://chneukirchen.org/blog/ Christian Neukirchen] は [http://chneukirchen.org/blog/archive/2006/01/xoxo-rb-0-1-released.html Ruby の XOXO パーサー兼ジェネレーターの xoxo.rb を書きました]<br />
* [http://odeo.com Odeo] はユーザーの予約リストを XOXO で公開しています(訳注:現在 XOXO を使っていないようです --[[User:KitaitiMakoto|KitaitiMakoto]] 13:41, 7 January 2009 (UTC))。[http://odeo.com/profile/RyanKing/xoxo ここにある](訳注:リンク切れ)Ryan King のリストをご覧ください。<br />
* [http://www.decafbad.com/blog/ Les Orchard] は[http://www.decafbad.com/2005/07/map-test/tree2.html XOXO によるすばらしいアウトラインエディター]を[http://www.decafbad.com/blog/2005/07/12/xoxo_outliner_experiment 書きました]。<br />
* http://homepage.mac.com/ctholland/thelab/outlines/ は、折りたたんだり開いたりするのに "compact" と DHTML を使った動的でインタラクティブな XOXO のとてもすばらしいデモンストレーションです。<br />
* http://tool-man.org/examples/sorting.html は、ドラッグ・アンド・ドロップで並べ替えられる、JavaScript と CSS を使った XOXO のリストのとてもすばらしいデモンストレーションです。<br />
* http://www.opendarwin.org/~drernie/xoxo-datatypes.html (訳注:リンク切れ。http://ihack.us/2005/10/03/xoxo-datatypes/ でしょうか)は XOXO を [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Concepts/XMLPListsConcept.html Mac OS X プロパティリスト](訳注:リンク切れ)へマッピングします。<br />
* [http://weblog.techno-weenie.net/2005/9/30/if_i_had_a_tumblelog XOXO を HTML に変換する Rails の一行(single line of rails;単線鉄道)]<br />
<br />
=== サンプルコード ===<br />
<br />
* XOXO ファイルを読み書きするオープンソースのサンプルコードコードは [[xoxo-sample-code]] ページをご覧ください。<br />
* [[xoxo-compact-sample]] ページもご覧ください。極めて単純な XOXO のルック・アンド・フィールを変え、また、ネストされたリスト用の、compact 属性に従って回転する三角マークを持たせる CSS と JavaScript のソースがあります。<br />
<br />
== XOXO スキーマ ==<br />
この節は参考情報です。<br />
<br />
注:以下は古いため、任意のプロパティで XOXO 項目に注釈を付けるという &lt;dl&gt; の使い方を反映させたアップデートが必要です。<br />
* [[DTDs|DTD]]<br />
* [http://www.nidelven-it.no/projects/XOXO/xoxo-0.1.tgz スキーマ(Relax NG と DTD)](訳注:リンク切れ)<br />
<br />
== 参考文献 ==<br />
=== 規範的な参考文献 ===<br />
* [http://www.w3.org/TR/xhtml1 XHTML 1.0]<br />
* [http://www.w3.org/TR/xhtml-modularization XHTMLMOD]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [http://gmpg.org/xfn/ XFN]<br />
<br />
=== その他の参考文献 ===<br />
この節は'''参考情報'''です。<br />
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]<br />
* [[VoteLinks]]<br />
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]<br />
* [http://opml.scripting.com/spec OPML 1.0]<br />
* http://developers.technorati.com/wiki/XOXO による貢献<br />
<br />
=== 類似の試み ===<br />
* [http://dannyayers.com/archives/001961.html XHTML アウトライン] - DannyAyers は 2003 年 10 月(Kevin と Tantek が XOXO を思い付くほんの一、二ヶ月前)に、アウトラインをXHTML の既存の基本的な要素でセマンティックに表現するため、簡単な XHTML プロファイルを使うことを独自に考え出しました。<br />
* [http://semtext.org/2004-02/ XOW] - それを編集可能にし、そこから RDF とブックマークリストを作ります(DannyAyers)<br />
* [http://en.wikipedia.org/wiki/XBEL XBEL、または XML Bookmark Exchange Language(XML ブックマーク交換言語)]。インターネットの URI を共有する XML のオープンスタンダードで、ブックマーク(Internet Explorer ではお気に入り)としても知られます。<br />
* [http://en.wikipedia.org/wiki/OPML OPML(Outline Processor Markup Language)]。アウトライン用の XML フォーマット。<br />
<br />
=== 関係する読み物 ===<br />
* [http://patricklogan.blogspot.com/2005/08/lists-really-can-we-expect-better.html Patrick Loganの、なぜ OPML と Microsoft のリスト拡張が両方とも必要ないかについて]。<br />
<br />
=== 関係のない読み物 ===<br />
* [http://www.questionablecontent.net/view.php?comic=493 Questionable Content comic #493] - キャラクターのフェイは明らかに XOXO のファンです。<br />
<br />
=== 販売促進の素材/グッズ ===<br />
* XOXO の服とアクセサリーが全てあります。[http://www.xoxo.com/home.php XOXO 関連の物をオンラインで買いましょう]。<br />
<br />
== 議論 ==<br />
この仕様は現在進行中です。更なる側面が議論され、理解され、文章になり、そして追加されるでしょう。XOXO 関連のブレインストーミングその他の探求を保存しておくべき文書が別ページにあります。<br />
<br />
* ある用途に XOXO をどのように使うかについては、[[xoxo-brainstorming]] をご覧ください。<br />
* [http://www.technorati.com/cosmos/referer.html このページについて議論しているブログ]([http://technorati.com/search/http%3A%2F%2Fmicroformats.org%2Fwiki%2Fxoxo 英語ページ])もご覧ください。<br />
** [http://blogxoxo.blogspot.com/ XOXO ブログ]<br />
<br />
=== Q&A ===<br />
* XOXO について疑問があれば [[xoxo-faq]] を確認してください。答えが見付からなければ質問を追加しましょう!<br />
<br />
=== 問題 ===<br />
* この仕様に関する問題は、別ページの [[xoxo-issues]] 文書に追加してください。<br />
<br />
[[Category:XOXO]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xoxo-id&diff=70212xoxo-id2020-07-18T16:35:38Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:XOXO 1.0: Extensible Open XHTML Outlines}}<br />
XOXO itu sederhana, susunan garis besarnya ditulis dalam XHTML stardar dan cocok ditancapkan di (X)HTML, Atom, RSS, dan seluruh XML. XOXO adalah salah satu dari beberapa standar [[microformats|microformat]] terbuka.<br />
<br />
__TOC__<br />
<br />
== Spesifikasi Konsep 2004-10-01 ==<br />
<br />
=== Editor ===<br />
[http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc])<br />
<br />
=== Pencipta ===<br />
* [http://epeus.blogspot.com/ Kevin Marks] ([http://technorati.com Technorati, Inc])<br />
* [http://tantek.com/ Tantek Çelik] ([http://technorati.com Technorati, Inc], formerly of [http://microsoft.com/ Microsoft Corporation])<br />
* [http://diveintomark.org/ Mark Pilgrim] ([http://ibm.com IBM])<br />
* [http://www.blogologue.com/ Morten W. Petersen]<br />
<br />
=== Hak Cipta ===<br />
{{MicroFormatCopyrightStatement2003}}<br />
* Saya memberikan seluruh kontribusi kepada spesifikasi ini untuk domain publik dan Saya menganjurkan pencipta lainnya melakukan hal yang sama.<br />
** Ketika semua penulis / editor telah melakukannya, kita dapat menghapus referensi template MicroFormatCopyrightStatement dan menggantinya dengan MicroFormatPublicDomainContributionStatement.<br />
<br />
=== Paten ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Pengantar ==<br />
When we were discussing [http://developers.technorati.com/wiki/attentionxml Attention.xml], Tantek pointed out that XHTML has everything necessary for semantically expressing outlines and blogroll-like subscriptions in an XML format that is both interactively renderable by browsers and parsable by strict XML engines. This page is here to discuss this idea.<br />
<br />
=== Nama ===<br />
XOXO adalah singkatan dari eXtensible Open XHTML Outlines, dan diucapkan dengan berbagai cara, seperti 'Ecks Ecks oh oh', 'zho-zho', atau 'sho-sho'.<br />
<br />
== Abstrak ==<br />
XOXO is one of several [[microformats]]. This specification defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The purpose of the XOXO document type is to serve as the basis for XHTML friendly outlines for processing by XML engines and for easy interactive rendering by browsers.<br />
<br />
== The XOXO Document Type ==<br />
The XOXO document type is made up of the following XHTML modules. The elements, attributes, and minimal content models associated with these modules are defined in "Modularization of XHTML" ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The elements are listed here for information purposes, but the definitions in "Modularization of XHTML" should be considered definitive. In the on-line version of this document, the module names in the list below link into the definitions of the modules within the current version of "Modularization of XHTML".<br />
<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_structuremodule Structure Module]<br />
body, head, html, title<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_hypertextmodule Hypertext Module]<br />
a<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_listmodule List Module]<br />
dl, dt, dd, ol, ul, li<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_metamodule Metainformation Module]<br />
meta<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_stylemodule Stylesheet Module]<br />
style element<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_styleattributemodule Style Attribute Module]<br />
style attribute<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_linkmodule Link Module]<br />
link<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_legacymodule Legacy Module]<br />
Attribute compact on ol and ul<br />
<br />
=== The XOXO Profile ===<br />
<br />
See [[xoxo-profile]] for the [http://gmpg.org/xmdp XMDP] profile of XOXO which defines the XOXO values for the class attribute.<br />
<br />
== Simple XOXO Fragment ==<br />
<br />
=== Markup ===<br />
<br />
<pre><nowiki><ol class='xoxo'><br />
<li>Subject 1<br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
<li>Subject 2<br />
<ol compact="compact"><br />
<li>subpoint c</li><br />
<li>subpoint d</li><br />
</ol><br />
</li><br />
<li>Subject 3<br />
<ol><br />
<li>subpoint e</li><br />
</ol><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
=== Sample Rendering ===<br />
<pre><nowiki><br />
1. Subject 1<br />
a. subpoint a<br />
b. subpoint b<br />
2. Subject 2<br />
3. Subject 3<br />
a. subpoint e<br />
</nowiki></pre><br />
=== Usage of 'compact' attribute ===<br />
<br />
Note the use of the 'compact' attribute to indicate that the subpoints of the headline "Subject 2" are not in an expanded state. The absence of the 'compact' attribute elsewhere indicates that the other headlines are in an expanded state.<br />
<br />
=== Possible Default Style Rules for Sample Rendering ===<br />
<br />
<pre><nowiki><br />
ol.xoxo { list-style:decimal; }<br />
ol.xoxo ol { list-style:lower-latin; }<br />
ol[compact="compact"] { display:none; }<br />
</nowiki></pre><br />
<br />
<br />
== More Simple Examples ==<br />
<br />
MarkP has a set of examples that demonstrates both the simplicity of the markup and the presentational richness that is possible:<br />
<br />
* [http://diveintomark.org/public/2004/01/xo-flat.xo simple XO file that can be embedded directly into an XHTML page]<br />
* [http://diveintomark.org/public/2004/01/xo-embeddable.xo XO with nested groups, also directly embeddedable in XHTML]<br />
* [http://diveintomark.org/public/2004/01/xo-standalone.xo XO as a standalone XHTML page] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-standalone.xo valid XHTML])<br />
* [http://diveintomark.org/public/2004/01/xo-with-style.xo XO as a standalone XHTML page, styled with CSS] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-with-style.xo also valid XHTML])<br />
* [http://homepage.mac.com/ctholland/thelab/outlines/ Chris Holland Outline Helper]: tweaked one of above samples, yanked CSS for simplicity, added reference to [http://homepage.mac.com/ctholland/thelab/outlines/outlines.css outlines.css] and [http://homepage.mac.com/ctholland/thelab/outlines/outlines.js outlines.js], pasted a few different combinations of ul/ol/li with the compact attribute.<br />
** in trying to comply with semantic principles the "compact" attribute to ol and ul elements is what drives the display state. Via scripting, i'm setting classes on containing li element for added styling flexibility, though CSS Gurus might be able to replace "li.expanded" in outlines.css with some other CSS selector that says "select an li node that contains an ol node with a 'compact' attribute set".<br />
*** The CSS selector for "an li node that contains an ol node with a 'compact' attribute set" would be 'li ol[compact="compact"]'.<br />
<br />
== Properties of Outline Items ==<br />
Outlines typically consist of a hierarchy of points and subpoints. Each of those points (outline items) itself may have some properties (AKA attributes or metadata) that need to be represented. Perhaps the most common additional property on outline items in practice is the URL as demonstrated in Mark Pilgrim's examples above. Even the text label/title of an outline item could be considered a common property. A few such common properties:<br />
* text<br />
* description<br />
* url (often called xmlurl or htmlurl; sometimes called permalink)<br />
* title<br />
* type (hint of the MIME type of the resource indicated by the URL)<br />
<br />
In general, properties on an outline item <code><nowiki><li></nowiki></code> are represented by a nested definition list <code><nowiki><dl></nowiki></code>. Strictly speaking, it is the first <code><nowiki><dl></nowiki></code> inside the <code><nowiki><li></nowiki></code> and before any following <code><nowiki><ol></nowiki></code>, <code><nowiki>&lt;ul&gt;</nowiki></code>, or <code>&lt;li&gt;</code>, e.g. here is an item "item 1" with a description property (the subpoints are there purely as a point of reference to an earlier example).<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
</nowiki></pre><br />
<br />
=== Special Properties ===<br />
There are a handful of special properties which we are able to represent more directly and conveniently with the semantic XHTML building blocks that we have included, instead of terms in a definition list. Mostly taken from the above list of common properties, these are:<br />
* text, url, title, type, and rel (short for relationship)<br />
<br />
If we were to represent them simply as definition terms (including the "description" property from the previous example), they might look something like this:<br />
<br />
Example for the sake of discussion only / not a canonical XOXO example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><br />
<dl><br />
<dt>text</dt><br />
<dd>item 1</dd><br />
<dt>description</dt><br />
<dd> This item represents the main point we're trying to make.</dd><br />
<dt>url</dt><br />
<dd>http://example.com/more.xoxo</dd><br />
<dt>title</dt><br />
<dd>title of item 1</dd><br />
<dt>type</dt><br />
<dd>text/xml</dd><br />
<dt>rel</dt><br />
<dd>help</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
However, by taking advantage of the semantic <code><a href></code> element, we are able to dramatically simplify the common cases that utilize these properties. From a parser's perspective, this applies to the first <code><a href></code> element directly inside the <code><nowiki>&lt;li&gt;</nowiki></code>.<br />
<br />
Actual XOXO Example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><a href="http://example.com/more.xoxo"<br />
title="title of item 1"<br />
type="text/xml"<br />
rel="help">item 1</a> <br />
<!-- note how the "text" property is simply the contents of the <a> element --><br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
Any other properties are simply added to the definition list in the same way as the "description" property.<br />
<br />
=== Multi-value Properties === <br />
<br />
Properties that have multiple values are added using a list, nested inside of the corresponding <code>dl</code> element:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>multivalproperty1</dt><br />
<dd><ul><br />
<li>value-a</li><br />
<li>value-b</li><br />
</ul></dd><br />
</dl><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
== Publishing XOXO ==<br />
<br />
XOXO may be published in two forms, valid XHTML, and simple well-formed XML.<br />
<br />
=== Valid XHTML XOXO ===<br />
<br />
A valid XHTML XOXO page is a complete XHTML document.<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"<br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<meta http-equiv="content-type" content="text/html; charset=utf-8" /><br />
<title>XOXO page</title><br />
</head><br />
<body><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
=== Simple well-formed XML XOXO ===<br />
<br />
The root element of a simple well-formed XML XOXO page is either an <code>ol</code> or <code>ul</code> with class name of "xoxo". This variant is ideal for syndication and transclusion into (X)HTML pages with [[rest/ahah|AHAH]].<br />
<br />
<pre><nowiki><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</nowiki></pre><br />
<br />
=== Content-Type ===<br />
<br />
Valid or well-formed XHTML XOXO SHOULD be served with this Content-Type header for maximum browser compatibility.<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
</nowiki></pre><br />
<br />
It MUST be served with one of these Content-Type headers:<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
Content-Type: application/xhtml+xml<br />
Content-Type: application/xml<br />
</nowiki></pre><br />
<br />
== Examples in the Wild ==<br />
This section is '''informative'''.<br />
<br />
There are many wild examples. Nearly every blogroll on the Web can be parsed as XOXO, since they are typically an unordered list of list items of hyperlinks, which is within the XOXO profile. List examples here, when the list becomes too long we can move to a dedicated page.<br />
<br />
* [http://api.talis.com/bf/stores/ukbib/services/facet?query=feynman&fields=title%2Csubject&top=10&output=html HTML output from a faceting service for book data]<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
* CVarious [[s5-tools|S5 tools]]<br />
* [http://chneukirchen.org/blog/ Christian Neukirchen] has [http://chneukirchen.org/blog/archive/2006/01/xoxo-rb-0-1-released.html written a xoxo.rb, a XOXO parser and generator for Ruby]<br />
* [http://odeo.com Odeo] publishes users' subscription lists in XOXO. See Ryan King's list [http://odeo.com/profile/RyanKing/xoxo here].<br />
* [http://www.decafbad.com/blog/ Les Orchard] has [http://www.decafbad.com/blog/2005/07/12/xoxo_outliner_experiment written] a [http://www.decafbad.com/2005/07/map-test/tree2.html nice XOXO outline editor in javascript].<br />
* http://homepage.mac.com/ctholland/thelab/outlines/ is a great demonstration of dynamic interactive XOXO with use of "compact" and DHTML to collapse/expand.<br />
* http://tool-man.org/examples/sorting.html is a great demonstration of drag and drop sortable XOXO lists with javascript and CSS.<br />
* http://www.opendarwin.org/~drernie/xoxo-datatypes.html Mapping XOXO to [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Concepts/XMLPListsConcept.html Mac OS X property lists]<br />
* [http://weblog.techno-weenie.net/2005/9/30/if_i_had_a_tumblelog single line of rails to convert XOXO to HTML]<br />
<br />
=== Contoh Kode ===<br />
<br />
* Lihat halaman [[xoxo-sample-code]] untuk contoh kode open source untuk membaca dan menulis berkas XOXO.<br />
* Lihat juga halaman [[xoxo-compact-sample]] dengan sumber untuk CSS dan JS yang mengubah tampilan dan nuansa XOXO yang sangat polos agar memiliki segitiga twiddlable untuk sekumpulan daftar yang menghargai attribut dengan baik.<br />
<br />
== Skema XOXO ==<br />
Bagian ini adalah informatif.<br />
<br />
Catatan: mungkin sudah usang dan perlu diperbaharui untuk mencerminkan penggunaan &lt;dl&gt; untuk membubuhi keterangan tiap-tiap XOXO dengan properti secara acak.<br />
* [[DTDs]]<br />
* [http://www.nidelven-it.no/projects/XOXO/xoxo-0.1.tgz Skema (Relax NG dan DTDs)]<br />
<br />
== Referensi ==<br />
=== Referensi yang normatif ===<br />
* [http://www.w3.org/TR/xhtml1 XHTML 1.0]<br />
* [http://www.w3.org/TR/xhtml-modularization XHTMLMOD]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [http://gmpg.org/xfn/ XFN]<br />
<br />
=== Referensi yang Informatif ===<br />
Bagian ini adalah '''informatif'''.<br />
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]<br />
* [[VoteLinks]]<br />
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]<br />
* [http://opml.scripting.com/spec OPML 1.0]<br />
* Kontribusi dari http://developers.technorati.com/wiki/XOXO<br />
<br />
=== Similar Work ===<br />
* [http://dannyayers.com/archives/001961.html XHTML Outlines] - DannyAyers independently came up with idea in 2003 October (just a month or two before Kevin and Tantek independently came up with XOXO) to use a simple profile of XHTML to semantically represent outlines using existing building blocks from XHTML.<br />
* [http://semtext.org/2004-02/ XOW] - making them editable, producing RDF and bookmark lists from them (DannyAyers)<br />
* [http://en.wikipedia.org/wiki/XBEL XBEL, or the XML Bookmark Exchange Language], an open XML standard for sharing Internet URIs, also known as bookmarks (or favorites in Internet Explorer).<br />
* [http://en.wikipedia.org/wiki/OPML OPML (Outline Processor Markup Language)], an XML format for outlines.<br />
<br />
=== Bacaan yang terkait ===<br />
* [http://patricklogan.blogspot.com/2005/08/lists-really-can-we-expect-better.html Patrick Logan menuliskan Mengapa kedua ekstensi OPML dan Microsoft Lists extension tidak diperlukan].<br />
<br />
=== Bacaan yang tidak terkait ===<br />
* [http://www.questionablecontent.net/view.php?comic=493 Questionable Content comic #493] - ternyata karakter Faye adalah penggemar XOXO.<br />
<br />
=== Promotional Materials / Schwag ===<br />
* There is an entire XOXO clothing and accessories line. [http://www.xoxo.com/home.php Buy XOXO stuff online].<br />
<br />
== Discussions ==<br />
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to XOXO:<br />
<br />
* See [[xoxo-brainstorming]] for additional thoughts on how to use XOXO for specific uses.<br />
* See also [http://www.technorati.com/cosmos/referer.html blogs discussing this page].<br />
** [http://blogxoxo.blogspot.com/ XOXO Blog]<br />
<br />
=== Tanya Jawab ===<br />
* Jika Anda memiliki pertanyaan seputar XOXO, silahkan kunjungi [[xoxo-faq]] dan jika Anda tidak menemukan jawabannya, tambahkan pertanyaan Anda pada halaman tersebut.<br />
<br />
=== Isu ===<br />
* Silahkan menambahkan isu dengan spesifikasi apapun ke dokumen terpisah [[xoxo-issues]].<br />
<br />
[[Category:Specifications]]<br />
[[Category:XOXO]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xoxo-fr&diff=70211xoxo-fr2020-07-18T16:35:37Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:XOXO 1.0: Extensible Open XHTML Outlines}}<br />
XOXO est un simple format ouvert d'outline écrit en XHTML standard et adaptable pour l'embarquement dans (X)HTML, Atom, RSS et le XML arbitraire. XOXO est l'un des nombreux [[microformats-fr|microformats]] standards ouverts . <br />
<br />
== Spécification Brouillon du 01-Octobre-2004 ==<br />
=== Editeur ===<br />
[http://tantek.com/ Tantek Çelik], ([http://technorati.com Technorati, Inc])<br />
<br />
=== Auteurs ===<br />
* [http://epeus.blogspot.com/ Kevin Marks], ([http://technorati.com Technorati, Inc])<br />
* [http://tantek.com/ Tantek Çelik], ([http://technorati.com Technorati, Inc], formerly of [http://microsoft.com/ Microsoft Corporation])<br />
* [http://diveintomark.org/ Mark Pilgrim], ([http://ibm.com IBM])<br />
* [http://www.blogologue.com/ Morten W. Petersen]<br />
<br />
=== Traducteur ===<br />
* [[Christophe Ducamp]]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2003-fr}}<br />
<br />
* [[User:Tantek|Tantek]] : Je sors toutes mes contributions sur cette spécification dans le domaine public et encourage les autres auteurs à faire de même.<br />
** Quand tous les auteurs/éditeurs auront fait ainsi, nous pourrons retirer le modèle MicroFormatCopyrightStatement de référence et le remplacer avec le modèle MicroFormatPublicDomainContributionStatement.<br />
<br />
=== Brevets ===<br />
{{MicroFormatPatentStatement-fr}}<br />
<br />
== Préambule ==<br />
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 discuter de cette idée.<br />
<br />
=== Nom ===<br />
XOXO veut dire eXtensible Open XHTML Outlines, et se prononce selon 'icks oh icks oh', 'zho-zho' ou 'cho-cho'.<br />
<br />
== Abstract ==<br />
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 la 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.<br />
<br />
== Le type de Document XOXO ==<br />
Le type de document XOXO est construit sur les modules suivants XHTML. <br />
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]). <br />
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".<br />
<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_structuremodule Structure Module]<br />
body, head, html, title<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_hypertextmodule Hypertext Module]<br />
a<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_listmodule List Module]<br />
dl, dt, dd, ol, ul, li<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_metamodule Metainformation Module]<br />
meta<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_stylemodule Stylesheet Module]<br />
style element<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_styleattributemodule Style Attribute Module]<br />
style attribute<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_linkmodule Link Module]<br />
link<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_legacymodule Legacy Module]<br />
Attribute compact on ol and ul<br />
<br />
=== Le Profil XOXO ===<br />
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.<br />
<br />
== Fragment Simple XOXO ==<br />
=== Balisage ===<br />
<br />
<pre><nowiki><ol class='xoxo'><br />
<li>Sujet 1<br />
<ol><br />
<li>souspoint a</li><br />
<li>souspoint b</li><br />
</ol><br />
</li><br />
<li>Sujet 2<br />
<ol compact="compact"><br />
<li>souspoint c</li><br />
<li>souspoint d</li><br />
</ol><br />
</li><br />
<li>Sujet 3<br />
<ol><br />
<li>souspoint e</li><br />
</ol><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
=== Restitution Echantillon ===<br />
<pre><nowiki><br />
1. Sujet 1<br />
a. souspoint a<br />
b. souspoint b<br />
2. Sujet 2<br />
3. Sujet 3<br />
a. souspoint e<br />
</nowiki></pre><br />
<br />
=== Usage de l'attribut 'compact' ===<br />
Notez l'utilisation de l'attribut 'compact' pour indiquer que les sous-points du titre "Sujet 2" <br />
ne sont pas dans un état déployé. L'absence de l'attribut 'compact' ailleurs indique que les autres titres <br />
sont en état déployé.<br />
<br />
=== Règles de Style par Défaut pour une Restitution Echantillon ===<br />
<pre><nowiki><br />
ol.xoxo { list-style:decimal; }<br />
ol.xoxo ol { list-style:lower-latin; }<br />
ol[compact="compact"] { display:none; }<br />
</nowiki></pre><br />
<br />
<br />
== Plus d'Exemples Simples ==<br />
MarkP a un ensemble d'exemples qui démontrent à la fois la simplicité du balisage et la richesse de présentation possible : <br />
* [http://diveintomark.org/public/2004/01/xo-flat.xo fichier simple XO qui peut être directement embarqué à l'intérieur d'une page XHTML]<br />
* [http://diveintomark.org/public/2004/01/xo-embeddable.xo XO avec groupes imbriqués, aussi directement embarcables dans le XHTML]<br />
* [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])<br />
* [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])<br />
* [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.<br />
** 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. <br />
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' ".<br />
*** Le sélecteur CSS pour "un noeud li qui contient un noeud ol avec un ensemble d'attribut 'compact'" serait 'li ol[compact="compact"]'<br />
<br />
== Propriétés des Items Outline ==<br />
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 :<br />
* text<br />
* description<br />
* url (souvent appelé xmlurl ou htmlurl ; parfois appelé permalink)<br />
* title<br />
* type (truc du MIME type de la ressource indiqué par l'URL)<br />
<br />
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>&lt;ul&gt;</nowiki></code>, ou <code>&lt;li&gt;</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).<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>description</dt><br />
<dd>cet item représente le point principal que nous essayons de produire.</dd><br />
</dl><br />
<ol><br />
<li>souspoint a</li><br />
<li>souspoint b</li><br />
</ol><br />
</li><br />
</nowiki></pre><br />
<br />
=== Propriétés Spéciales ===<br />
Il existe un paquet de propriétés spéciales que nous pouvons représenter plus directement <br />
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 : <br />
* text, url, title, type, et rel (raccourci de relationship)<br />
<br />
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 : <br />
<br />
Exemple pour recherche de discussion seulement / pas un exemple canonique XOXO :<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><br />
<dl><br />
<dt>text</dt><br />
<dd>item 1</dd><br />
<dt>description</dt><br />
<dd> Cet item représente le point principal que nous essayons de produire.</dd><br />
<dt>url</dt><br />
<dd>http://exemple.com/plus.xoxo</dd><br />
<dt>title</dt><br />
<dd>titre de item 1</dd><br />
<dt>type</dt><br />
<dd>text/xml</dd><br />
<dt>rel</dt><br />
<dd>aide</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
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>&lt;li&gt;</nowiki></code>.<br />
<br />
Exemple véritable XOXO :<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><a href="http://exemple.com/more.xoxo"<br />
title="titre item 1"<br />
type="text/xml"<br />
rel="help">item 1</a> <br />
<!-- notez comme la propriété "text" est simplement les contenus de l'élément <a> --><br />
<dl><br />
<dt>description</dt><br />
<dd>Cet item présente le point principal que nous essayons de produire.</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
Toutes les autres propriétés sont simplement ajoutées à la liste de définition <br />
de la même façon que la propriété "description".<br />
<br />
=== Propriétés multi-valeurs === <br />
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> :<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>multivalpropriete1</dt><br />
<dd><ul><br />
<li>valeur-a</li><br />
<li>valeur-b</li><br />
</ul></dd><br />
</dl><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
== Publier XOXO ==<br />
XOXO peut être publié sous deux formes, XHTML valide, et XML simple et bien formé.<br />
<br />
=== XOXO XHTML Valide ===<br />
Une page XOXO XHTML Valide est un document XHTML complet.<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"<br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<meta http-equiv="content-type" content="text/html; charset=utf-8" /><br />
<title>XOXO page</title><br />
</head><br />
<body><br />
<ol class="xoxo"><br />
<li><a href="URL-un">TEXT-un</a></li><br />
<li><a href="URL-deux">TEXT-deux</a></li><br />
...<br />
</ol><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
=== XOXO XML Simple bien-formé ===<br />
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]].<br />
<br />
<pre><nowiki><br />
<ol class="xoxo"><br />
<li><a href="URL-un">TEXTE-un</a></li><br />
<li><a href="URL-deux">TEXTE-deux</a></li><br />
...<br />
</ol><br />
</nowiki></pre><br />
<br />
=== Content-Type ===<br />
Le XHTML XOXO valide et bien formé DEVRAIT être servi avec cet en-tête Content-Type pour une compatibilité navigateur maximale :<br />
<pre><nowiki><br />
Content-Type: text/xml; charset=utf-8<br />
</nowiki></pre><br />
<br />
Il DOIT être servi avec un de ces en-têtes Content-Type :<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
Content-Type: application/xhtml+xml<br />
Content-Type: application/xml<br />
</nowiki></pre><br />
<br />
== Exemples dans la Jungle ==<br />
Cette section est '''informative'''.<br />
<br />
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.<br />
* [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]<br />
<br />
== Implémentations ==<br />
Cette section est '''informative'''.<br />
* CVarious [[s5-tools-fr|S5 outils]]<br />
* [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]<br />
* [http://odeo.com Odeo] publie les listes d'abonnements utilisateurs dans XOXO. Voir la liste de Ryan King [http://odeo.com/profile/RyanKing/xoxo ici].<br />
* [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].<br />
* 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.<br />
* http://tool-man.org/examples/sorting.html est une démonstration géniale de listes XOXO "glisser déposer" triables avec javascript and CSS.<br />
* http://www.joshpeek.com/projects/opmltoxoxo est un convertisseur extensible de OPML vers XOXO.<br />
* 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]<br />
* [http://weblog.techno-weenie.net/2005/9/30/if_i_had_a_tumblelog ligne unique de rails pour convertir XOXO en HTML]<br />
<br />
=== Code échantillon ===<br />
* Voir la page [[xoxo-sample-code-fr|xoxo-code-échantillon]] pour un code échantillon open source afin de lire et écrire des fichiers XOXO.<br />
* 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.<br />
<br />
== Schémas XOXO ==<br />
Cette section est "informative".<br />
<br />
Note : ces liens peuvent être démodés et ont besoin d'être mis à jour pour refléter l'utilisation de &lt;dl&gt; pour l'annotation d'items XOXO avec des propriétés arbitraires.<br />
* [[DTDs]]<br />
* [http://www.nidelven-it.no/projects/XOXO/xoxo-0.1.tgz Schemas (Relax NG and DTDs)]<br />
<br />
<br />
== Références ==<br />
=== Références "Normatives" ===<br />
* [http://www.w3.org/TR/xhtml1 XHTML 1.0]<br />
* [http://www.w3.org/TR/xhtml-modularization XHTMLMOD]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [http://gmpg.org/xfn/ XFN]<br />
<br />
=== Références "Informatives" ===<br />
Cette section est '''informative'''.<br />
* [http://developers.technorati.com/wiki/attentionxml Attention.xml]<br />
* [[vote-links-fr|VoteLinks]]<br />
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]<br />
* [http://opml.scripting.com/spec OPML 1.0]<br />
* Contribution provenant de http://developers.technorati.com/wiki/XOXO<br />
<br />
=== Travaux similaires ===<br />
* [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 <br />
pour représenter sémantiquement les outlines en utilisant des blocs de constrution existant provenant du XHTML.<br />
* [http://semtext.org/2004-02/ XOW] - les rend éditables, produisant des listes de RDF et bookmark à partir d'eux (DannyAyers)<br />
* [http://en.wikipedia.org/wiki/XBEL XBEL, ou XML Bookmark Exchange Language], un standard XML ouvert pour partager des URIs internet, connu aussi comme signets ou favoris<br />
* [http://fr.wikipedia.org/wiki/Outline_Processor_Markup_Language OPML (Outline Processor Markup Language)], un format XML pour les outlines.<br />
<br />
=== Lecture en Rapport ===<br />
* [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].<br />
<br />
=== Lecture sans aucun rapport ===<br />
* [http://www.questionablecontent.net/view.php?comic=493 Questionable Content comic #493] - apparamment le personnage Faye est un fan of XOXO.<br />
<br />
=== Contenus Promotionnels / Schwag ===<br />
* Il existe toute une ligne de vêtements et d'accessoires en ligne. [http://www.xoxo.com/home.php Buy XOXO stuff online].<br />
<br />
== Discussions ==<br />
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 :<br />
* Voir [[xoxo-brainstorming-fr]] pour des idées supplémentaires sur la façon d'utiliser XOXO pour des usages spécifiques.<br />
* Voir aussi [http://www.technorati.com/cosmos/referer.html les blogs qui discutent de cette page].<br />
** [http://blogxoxo.blogspot.com/ XOXO Blog]<br />
<br />
=== Q&R ===<br />
* 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 !<br />
<br />
=== Problématiques ===<br />
* ajoutez svp toute problématique sur la spécification à la page document séparée [[xoxo-issues-fr|problématiques xoxo]].<br />
<br />
<br />
[[Category:Specifications]]<br />
[[Category:XOXO]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xoxo&diff=70210xoxo2020-07-18T16:35:36Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:XOXO 1.0: Extensible Open XHTML Outlines}}<br />
XOXO is a simple, open outline format written in standard XHTML and suitable for embedding in (X)HTML, Atom, RSS, and arbitrary XML. XOXO is one of several [[microformats|microformat]] open standards. <br />
<br />
__TOC__<br />
<br />
== Draft Specification 2004-10-01 ==<br />
<br />
=== Editor ===<br />
[http://tantek.com/ Tantek Çelik]<br />
<br />
=== Authors ===<br />
* [http://epeus.blogspot.com/ Kevin Marks]<br />
* [http://tantek.com/ Tantek Çelik]<br />
* Mark Pilgrim<br />
* [http://www.blogologue.com/ Morten W. Petersen]<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2003}}<br />
* [[User:Tantek|Tantek]]: I release all my contributions to this specification into the public domain and I encourage the other authors to do so as well.<br />
** When all authors/editors have done so, we can remove the MicroFormatCopyrightStatement template reference and replace it with the MicroFormatPublicDomainContributionStatement.<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
== Preamble ==<br />
When we were discussing [https://web.archive.org/web/20071017054844/http://developers.technorati.com:80/wiki/attentionxml Attention.xml], Tantek pointed out that XHTML has everything necessary for semantically expressing outlines and blogroll-like subscriptions in an XML format that is both interactively renderable by browsers and parsable by strict XML engines. This page is here to discuss this idea.<br />
<br />
=== Name ===<br />
XOXO stands for eXtensible Open XHTML Outlines, and is pronounced variously as 'ecks oh ecks oh', 'zho-zho', or 'sho-sho'.<br />
<br />
== Abstract ==<br />
XOXO is one of several [[microformats]]. This specification defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The purpose of the XOXO document type is to serve as the basis for XHTML friendly outlines for processing by XML engines and for easy interactive rendering by browsers.<br />
<br />
== The XOXO Document Type ==<br />
The XOXO document type is made up of the following XHTML modules. The elements, attributes, and minimal content models associated with these modules are defined in "Modularization of XHTML" ([http://www.w3.org/TR/xhtml-modularization XHTMLMOD]). The elements are listed here for information purposes, but the definitions in "Modularization of XHTML" should be considered definitive. In the on-line version of this document, the module names in the list below link into the definitions of the modules within the current version of "Modularization of XHTML".<br />
<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_structuremodule Structure Module]<br />
body, head, html, title<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_hypertextmodule Hypertext Module]<br />
a<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_listmodule List Module]<br />
dl, dt, dd, ol, ul, li<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_metamodule Metainformation Module]<br />
meta<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_stylemodule Stylesheet Module]<br />
style element<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_styleattributemodule Style Attribute Module]<br />
style attribute<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_linkmodule Link Module]<br />
link<br />
[http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_legacymodule Legacy Module]<br />
Attribute compact on ol and ul<br />
<br />
=== The XOXO Profile ===<br />
<br />
See [[xoxo-profile]] for the [http://gmpg.org/xmdp XMDP] profile of XOXO which defines the XOXO values for the class attribute.<br />
<br />
== Simple XOXO Fragment ==<br />
<br />
=== Markup ===<br />
<br />
<pre><nowiki><ol class='xoxo'><br />
<li>Subject 1<br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
<li>Subject 2<br />
<ol compact="compact"><br />
<li>subpoint c</li><br />
<li>subpoint d</li><br />
</ol><br />
</li><br />
<li>Subject 3<br />
<ol><br />
<li>subpoint e</li><br />
</ol><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
=== Sample Rendering ===<br />
<pre><nowiki><br />
1. Subject 1<br />
a. subpoint a<br />
b. subpoint b<br />
2. Subject 2<br />
3. Subject 3<br />
a. subpoint e<br />
</nowiki></pre><br />
=== Usage of 'compact' attribute ===<br />
<br />
Note the use of the 'compact' attribute to indicate that the subpoints of the headline "Subject 2" are not in an expanded state. The absence of the 'compact' attribute elsewhere indicates that the other headlines are in an expanded state.<br />
<br />
=== Possible Default Style Rules for Sample Rendering ===<br />
<br />
<pre><nowiki><br />
ol.xoxo { list-style:decimal; }<br />
ol.xoxo ol { list-style:lower-latin; }<br />
ol[compact="compact"] { display:none; }<br />
</nowiki></pre><br />
<br />
<br />
== More Simple Examples ==<br />
<br />
MarkP has a set of examples that demonstrates both the simplicity of the markup and the presentational richness that is possible:<br />
<br />
* [http://diveintomark.org/public/2004/01/xo-flat.xo simple XO file that can be embedded directly into an XHTML page]<br />
* [http://diveintomark.org/public/2004/01/xo-embeddable.xo XO with nested groups, also directly embeddedable in XHTML]<br />
* [http://diveintomark.org/public/2004/01/xo-standalone.xo XO as a standalone XHTML page] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-standalone.xo valid XHTML])<br />
* [http://diveintomark.org/public/2004/01/xo-with-style.xo XO as a standalone XHTML page, styled with CSS] ([http://validator.w3.org/check?uri=http%3A%2F%2Fdiveintomark.org%2Fpublic%2F2004%2F01%2Fxo-with-style.xo also valid XHTML])<br />
* [http://homepage.mac.com/ctholland/thelab/outlines/ Chris Holland Outline Helper]: tweaked one of above samples, yanked CSS for simplicity, added reference to [http://homepage.mac.com/ctholland/thelab/outlines/outlines.css outlines.css] and [http://homepage.mac.com/ctholland/thelab/outlines/outlines.js outlines.js], pasted a few different combinations of ul/ol/li with the compact attribute.<br />
** in trying to comply with semantic principles the "compact" attribute to ol and ul elements is what drives the display state. Via scripting, i'm setting classes on containing li element for added styling flexibility, though CSS Gurus might be able to replace "li.expanded" in outlines.css with some other CSS selector that says "select an li node that contains an ol node with a 'compact' attribute set".<br />
*** The CSS selector for "an li node that contains an ol node with a 'compact' attribute set" would be 'li ol[compact="compact"]'.<br />
<br />
== Properties of Outline Items ==<br />
Outlines typically consist of a hierarchy of points and subpoints. Each of those points (outline items) itself may have some properties (AKA attributes or metadata) that need to be represented. Perhaps the most common additional property on outline items in practice is the URL as demonstrated in Mark Pilgrim's examples above. Even the text label/title of an outline item could be considered a common property. A few such common properties:<br />
* text<br />
* description<br />
* url (often called xmlurl or htmlurl; sometimes called permalink)<br />
* title<br />
* type (hint of the MIME type of the resource indicated by the URL)<br />
<br />
In general, properties on an outline item <code><nowiki><li></nowiki></code> are represented by a nested definition list <code><nowiki><dl></nowiki></code>. Strictly speaking, it is the first <code><nowiki><dl></nowiki></code> inside the <code><nowiki><li></nowiki></code> and before any following <code><nowiki><ol></nowiki></code>, <code><nowiki>&lt;ul&gt;</nowiki></code>, or <code>&lt;li&gt;</code>, e.g. here is an item "item 1" with a description property (the subpoints are there purely as a point of reference to an earlier example).<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
<ol><br />
<li>subpoint a</li><br />
<li>subpoint b</li><br />
</ol><br />
</li><br />
</nowiki></pre><br />
<br />
=== Special Properties ===<br />
There are a handful of special properties which we are able to represent more directly and conveniently with the semantic XHTML building blocks that we have included, instead of terms in a definition list. Mostly taken from the above list of common properties, these are:<br />
* text, url, title, type, and rel (short for relationship)<br />
<br />
If we were to represent them simply as definition terms (including the "description" property from the previous example), they might look something like this:<br />
<br />
Example for the sake of discussion only / not a canonical XOXO example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><br />
<dl><br />
<dt>text</dt><br />
<dd>item 1</dd><br />
<dt>description</dt><br />
<dd> This item represents the main point we're trying to make.</dd><br />
<dt>url</dt><br />
<dd>http://example.com/more.xoxo</dd><br />
<dt>title</dt><br />
<dd>title of item 1</dd><br />
<dt>type</dt><br />
<dd>text/xml</dd><br />
<dt>rel</dt><br />
<dd>help</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
However, by taking advantage of the semantic <code><a href></code> element, we are able to dramatically simplify the common cases that utilize these properties. From a parser's perspective, this applies to the first <code><a href></code> element directly inside the <code><nowiki>&lt;li&gt;</nowiki></code>.<br />
<br />
Actual XOXO Example:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li><a href="http://example.com/more.xoxo"<br />
title="title of item 1"<br />
type="text/xml"<br />
rel="help">item 1</a> <br />
<!-- note how the "text" property is simply the contents of the <a> element --><br />
<dl><br />
<dt>description</dt><br />
<dd>This item represents the main point we're trying to make.</dd><br />
</dl><br />
</li><br />
</nowiki></pre><br />
<br />
Any other properties are simply added to the definition list in the same way as the "description" property.<br />
<br />
=== Multi-value Properties === <br />
<br />
Properties that have multiple values are added using a list, nested inside of the corresponding <code>dl</code> element:<br />
<br />
<pre><nowiki><br />
<ol class='xoxo'><br />
<li>item 1<br />
<dl><br />
<dt>multivalproperty1</dt><br />
<dd><ul><br />
<li>value-a</li><br />
<li>value-b</li><br />
</ul></dd><br />
</dl><br />
</li><br />
</ol><br />
</nowiki></pre><br />
<br />
== Publishing XOXO ==<br />
<br />
XOXO may be published in two forms, valid XHTML, and simple well-formed XML.<br />
<br />
=== Valid XHTML XOXO ===<br />
<br />
A valid XHTML XOXO page is a complete XHTML document.<br />
<br />
<pre><nowiki><br />
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"<br />
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><br />
<html xmlns="http://www.w3.org/1999/xhtml"><br />
<head><br />
<meta http-equiv="content-type" content="text/html; charset=utf-8" /><br />
<title>XOXO page</title><br />
</head><br />
<body><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</body><br />
</html><br />
</nowiki></pre><br />
<br />
=== Simple well-formed XML XOXO ===<br />
<br />
The root element of a simple well-formed XML XOXO page is either an <code>ol</code> or <code>ul</code> with class name of "xoxo". This variant is ideal for syndication and transclusion into (X)HTML pages with [[rest/ahah|AHAH]].<br />
<br />
<pre><nowiki><br />
<ol class="xoxo"><br />
<li><a href="URL-one">TEXT-one</a></li><br />
<li><a href="URL-two">TEXT-two</a></li><br />
...<br />
</ol><br />
</nowiki></pre><br />
<br />
=== Content-Type ===<br />
<br />
Valid or well-formed XHTML XOXO SHOULD be served with this Content-Type header for maximum browser compatibility.<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
</nowiki></pre><br />
<br />
It MUST be served with one of these Content-Type headers:<br />
<br />
<pre><nowiki><br />
Content-Type: text/html; charset=utf-8<br />
Content-Type: application/xhtml+xml<br />
Content-Type: application/xml<br />
</nowiki></pre><br />
<br />
== Examples in the Wild ==<br />
This section is '''informative'''.<br />
<br />
There are many wild examples. Nearly every blogroll on the Web can be parsed as XOXO, since they are typically an unordered list of list items of hyperlinks, which is within the XOXO profile. List examples here, when the list becomes too long we can move to a dedicated page.<br />
<br />
* [http://api.talis.com/bf/stores/ukbib/services/facet?query=feynman&fields=title%2Csubject&top=10&output=html HTML output from a faceting service for book data]<br />
<br />
== Implementations ==<br />
This section is '''informative'''.<br />
<br />
* CVarious [[s5-tools|S5 tools]]<br />
* [http://chneukirchen.org/blog/ Christian Neukirchen] has [http://chneukirchen.org/blog/archive/2006/01/xoxo-rb-0-1-released.html written a xoxo.rb, a XOXO parser and generator for Ruby]<br />
* [http://odeo.com Odeo] publishes users' subscription lists in XOXO. See Ryan King's list [http://odeo.com/profile/RyanKing/xoxo here].<br />
* [http://www.decafbad.com/blog/ Les Orchard] has [http://www.decafbad.com/blog/2005/07/12/xoxo_outliner_experiment written] a [http://www.decafbad.com/2005/07/map-test/tree2.html nice XOXO outline editor in javascript].<br />
* http://homepage.mac.com/ctholland/thelab/outlines/ is a great demonstration of dynamic interactive XOXO with use of "compact" and DHTML to collapse/expand.<br />
* http://tool-man.org/examples/sorting.html is a great demonstration of drag and drop sortable XOXO lists with javascript and CSS.<br />
* http://www.opendarwin.org/~drernie/xoxo-datatypes.html Mapping XOXO to [http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/Concepts/XMLPListsConcept.html Mac OS X property lists]<br />
* [http://weblog.techno-weenie.net/2005/9/30/if_i_had_a_tumblelog single line of rails to convert XOXO to HTML]<br />
<br />
=== Sample Code ===<br />
<br />
* See the [[xoxo-sample-code]] page for open source sample code to read and write XOXO files.<br />
* See also the [[xoxo-compact-sample]] page with source for CSS and JS that alters the look and feel of some very plain XOXO to have twiddlable triangles for nested lists that respect the compact attribute as well.<br />
<br />
== XOXO Schemas ==<br />
This section is informative.<br />
<br />
Note: these may be out of date and require updating to reflect the use of &lt;dl&gt; for annotating XOXO items with arbitrary properties.<br />
* [[DTDs]]<br />
* [http://www.nidelven-it.no/projects/XOXO/xoxo-0.1.tgz Schemas (Relax NG and DTDs)]<br />
<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/xhtml1 XHTML 1.0]<br />
* [http://www.w3.org/TR/xhtml-modularization XHTMLMOD]<br />
* [http://gmpg.org/xmdp/ XMDP]<br />
* [http://gmpg.org/xfn/ XFN]<br />
<br />
=== Informative References ===<br />
This section is '''informative'''.<br />
* [https://web.archive.org/web/20071017054844/http://developers.technorati.com:80/wiki/attentionxml Attention.xml]<br />
* [[VoteLinks]]<br />
* [http://www.w3.org/TR/xhtml11 XHTML 1.1]<br />
* [http://opml.scripting.com/spec OPML 1.0]<br />
* Contributed from <nowiki>http://developers.technorati.com/wiki/XOXO</nowiki><br />
<br />
=== Similar Work ===<br />
* [http://dannyayers.com/archives/001961.html XHTML Outlines] - DannyAyers independently came up with idea in 2003 October (just a month or two before Kevin and Tantek independently came up with XOXO) to use a simple profile of XHTML to semantically represent outlines using existing building blocks from XHTML.<br />
* [http://semtext.org/2004-02/ XOW] - making them editable, producing RDF and bookmark lists from them (DannyAyers)<br />
* [http://en.wikipedia.org/wiki/XBEL XBEL, or the XML Bookmark Exchange Language], an open XML standard for sharing Internet URIs, also known as bookmarks (or favorites in Internet Explorer).<br />
* [http://en.wikipedia.org/wiki/OPML OPML (Outline Processor Markup Language)], an XML format for outlines.<br />
<br />
=== Related Reading ===<br />
* [http://patricklogan.blogspot.com/2005/08/lists-really-can-we-expect-better.html Patrick Logan on why OPML and a Microsoft Lists extension are both unnecessary].<br />
<br />
=== Unrelated Reading ===<br />
* [http://www.questionablecontent.net/view.php?comic=493 Questionable Content comic #493] - apparently the Faye character is a fan of XOXO.<br />
<br />
=== Promotional Materials / Schwag ===<br />
* There is an entire XOXO clothing and accessories line. [http://www.xoxo.com/ Buy XOXO stuff online].<br />
<br />
== Discussions ==<br />
This specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. There is a separate document where we are keeping our brainstorms and other explorations relating to XOXO:<br />
<br />
* See [[xoxo-brainstorming]] for additional thoughts on how to use XOXO for specific uses.<br />
<br />
<br />
=== Q&A ===<br />
* If you have any questions about XOXO, check the [[xoxo-faq]], and if you don't find answers, add your questions!<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[xoxo-issues]] document.<br />
<br />
[[Category:Specifications]]<br />
[[Category:XOXO]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xmdp-profile&diff=70209xmdp-profile2020-07-18T16:35:36Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:XMDP Profile}}<br />
<br />
See '''http://gmpg.org/xmdp/1''' for an [[XMDP]] profile for the [http://gmpg.org/xmdp/description XMDP specification] itself.</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xmdp-origins&diff=70208xmdp-origins2020-07-18T16:35:35Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:XMDP origins}}<br />
<br />
An essay by [[User:Tantek|Tantek Çelik]] on the origins of [[XMDP]]. To be wikified.<br />
<br />
When I was working on [[XFN]] (effectively the first microformat), I specifically designed the underlying technology of XHTML Meta Data Profiles ([[XMDP]]) to *enable* all HTML rel/class additions/extensions (what would later become known as "microformats") to be *optionally* bound by URLs. And not just any URLs, but URLs that were compatible with and looked like RDF vocabulary URLs that ended with a "#" and term name. This was a deliberate design decision on my part, because I knew that there would be those who preferred to define their terms with URLs. Here is an HTML markup fragment that demonstrates this with the above-mentioned [[hCard]]:<br />
<br />
<source lang=html4strict><br />
<html><head profile="http://microformats.org/profile/hcard"><br />
<title>a document with hCards</title></head><br />
<p class="vcard"><span class="fn">Jeni Tennison</span> wrote an article, <br />
<cite><a href="http://www.jenitennison.com/blog/node/124">HTML5/RDFa Arguments</a></cite>, <br />
that compares and critically analyzes HTML5 and RDF approaches to representing and publishing data.<br />
</p><br />
</html><br />
</source><br />
<br />
The terms "vcard" and "fn" which are used as class names are defined by the [http://microformats.org/profile/hcard hCard XMDP] and the respective URLs for those terms are created by referencing the fragment IDs in that document:<br />
<br />
* vcard: http://microformats.org/profile/hcard#vcard<br />
* fn: http://microformats.org/profile/hcard#fn<br />
<br />
Thus providing the necessary URLs for any (meta)data system that stores/reasons about data based on vocabulary based on URLs (whether RDF or some other URL-based vocabulary store).<br />
<br />
In practice, few people use XMDP profiles, well, except for at least the millions [http://wordpress.com Wordpress blogs] out there - just view source on them and you'll find: <code><nowiki>profile="http://gmpg.org/xfn/11"</nowiki></code> near the top of the page.<br />
<br />
The point is that those that want to use profiles have the *option* of using them, while not burdening everyone else with doing so.<br />
<br />
[[User:Tantek|Tantek]] 18:07, 22 August 2009 (UTC)<br />
<br />
== see also ==<br />
* [[XMDP]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xmdp-fr&diff=70207xmdp-fr2020-07-18T16:35:34Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:XMDP}}<br />
<abbr title="XHTML Meta Data Profiles">XMDP</abbr> sont des Profils de Méta Données XHTML et la spécification est documentée sur http://gmpg.org/xmdp/<br />
<br />
== Voir aussi ==<br />
* [[xmdp-origins|xmdp-origines]]<br />
* [[xmdp-examples-fr|xmdp-exemples]]<br />
* [[xmdp-faq-fr|xmdp-faq]]<br />
* [[xmdp-issues-fr|xmdp-problématiques]]<br />
* [[xmdp-brainstorming]]<br />
* [[xmdp-profile-fr|xmdp-profil]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xmdp-brainstorming&diff=70206xmdp-brainstorming2020-07-18T16:35:33Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:XMDP Brainstorming}}<br />
<br />
== introduction ==<br />
Tantek Çelik developed [http://gmpg.org/xmdp/ XMDP] to define extensions to XHTML including rel values, class names, and &lt;meta name&gt; properties and values. Per the [http://gmpg.org/xmdp/description XMDP spec], a link to a microformat's XMDP in the profile attribute of head element indicates that that microformat's vocabulary is formally defined in the document. A parser could read the allowed attribute values from the linked XMDP and thus know explicitly which microformats may be in use, and which class names are meant to convey which meanings.<br />
<br />
This page is for exploring possible additions / extensions to XMDP, contributed by numerous folks in the microformats community.<br />
<br />
See [[xmdp-faq]] and [[xmdp-issues]] for questions and issues.<br />
<br />
Some of the below are probably better addressed as questions and/or issues and should be moved to those pages accordingly. -- [[User:Tantek|Tantek]]<br />
<br />
== requests from TimBL ==<br />
At the [http://www.w3.org/2009/11/TPAC/ 2009 W3C Technical Plenary] I (Tantek) had a conversation with Tim Berners-Lee about what he would like to see in XMDP to enable rich(er) translation into RDFSchema (RDFS).<br />
<br />
The following subsections represent my notes on specific asks/requests/feedback from Tim. [[User:Tantek|Tantek]] 01:16, 5 November 2009 (UTC)<br />
<br />
=== labels ===<br />
<br />
* labels are useful for multiple languages<br />
* "fn" - is a property name<br />
* rdfs:label would be "formatted name" - but not a long explanation, e.g. also "nom" in French<br />
* ok to use existing HTML "lang" attribute and standard language codes<br />
* XMDP should offer labels for terms, with labels in specific (human) languages<br />
<br />
=== serve RDFS using conneg ===<br />
It would be useful/nice if requests to microformats profiles, e.g. http://microformats.org/profile/hcard - if made with the Accept header requesting the mime type of RDFS (conneg / content negotiation), would be returned as an automatic translation (perhaps using XSLT) of the XMDP to RDFS.<br />
<br />
=== aliasing ===<br />
TimBL likes to be able to say this term is the same as this other term.<br />
<br />
=== atomic types ===<br />
It would be useful to specify the atomic type of a microformats property, e.g. one of the following:<br />
* datetime<br />
* url/email<br />
* number/fixed<br />
* string<br />
<br />
TimBL also suggested location lat/long/altitude, however that's more of a composite type (e.g. [[geo]]) that is made of multiple atomic types<br />
<br />
== Possible XMDP Additions ==<br />
=== resolving when microformats may be in use ===<br />
Currently the potential existence of microformats in a document can be declared by referencing the profile URLs for those microformats in the profile attribute of the head element of that document.<br />
<br />
In addition to the profile attribute, the [[rel-profile]] value is being strongly considered for inclusion in an update to XMDP. See the [[rel-profile]] page for details.<br />
<br />
In short: another way would be to include the <nowiki><a rel="profile" href="XMDP URL">powered by microformat xyz</a></nowiki> within the container element for the microformat. The XMDP spec could then specify that when the <a> element is used in this way, it indicates that the microformat is used by the element containing the <a> element.<br />
<br />
Issues:<br />
<br />
* Not every microformat has a container element. Consider [[rel-tag]] one of the most widely used microformats.<br />
** RESOLVED. This is easily resolved by having the context of the [[rel-profile]] be the parent of the element with [[rel-profile]] and descendants, or perhaps latter siblings of the element with [[rel-profile]] and their descendants.<br />
* To some extent, using microformats adds to the size of the document, just as using markup adds to the size of a plain text document. Putting <nowiki><a></nowiki> elements with each microformat adds unwanted links on top of that.<br />
** RESOLVED. There is no need to add an <nowiki><a></nowiki> for each instance of a microformat, as the profile for a microformat can be declared once, perhaps near the top of the body of the document. In practice, many pages that use microformats already link to the microformats specs themselves with badges or "powered by" links which could easily be modified to link to profiles using <code>&lt;a rel="profile"&gt;</code> hyperlinks, no additional links needed.<br />
<br />
=== root class name identification ===<br />
Use-case:<br />
<br />
It could be quite convenient for "generic/universal" microformat parsers if they could read an XMDP profile and understand which of the defined class names were ''root'' class names for microformats, and thus be able to distinguish those object boundaries.<br />
<br />
XMDP profiles can and do contain definitions for multiple root class names (e.g. http://microformats.org/wiki/hcard defines "vcard", "adr", and "geo").<br />
<br />
==== possible solutions ====<br />
===== XMDP definition flag =====<br />
Introduce some sort of markup or textual flag that indicates inside an XMDP definition (&lt;dd&gt;) for a class name that the class name may be used as a root class name.<br />
<br />
==== rejected solutions ====<br />
===== first class name defined in a profile =====<br />
One simple thought would be that the ''first'' class name defined in a profile<br />
(e.g. [[hcard-profile]]) is the root class for that microformat. <br />
<br />
Critical problem(s):<br />
* Does not handle the case of multiple root class names in an XMDP. E.g. a microformat that defines multiple possible root class names (e.g. [[hcalendar|hCalendar]] permits "vcalendar" or "vevent", [[hatom|hAtom]] permits "hfeed" or "hentry").<br />
<br />
===== publisher linking to root class name =====<br />
The author including a reference to the XMDP could link directly to the root class name.<br />
<pre>&lt;!-- This profile link indicates that "vcard" is a root class name. --><br />
&lt;head profile="http://www.w3.org/2006/03/hcard#vcard"></pre><br />
<br />
Critical problem(s):<br />
* The problem is this moves the information of what is the root class to perhaps one of the worst places, which is in every reference to the XMDP, whereas the XMDP itself should be defining what is a root class.<br />
<br />
===== publisher inline additional class name =====<br />
Another possibility that may be worth exploring, is the ability to indicate inline in the code that a class name is the root class name for a microformat, rather than (or perhaps in addition to) the XMDP.<br />
<br />
E.g.<br />
<source lang=html4strict><br />
<span class="vcard ufroot"><br />
<span class="fn">Tantek Çelik</fn><br />
</span><br />
</source><br />
<br />
would indicate that the element with classname of "vcard" is the root of a microformatted piece of information.<br />
<br />
Critical problem(s):<br />
* The problem is this moves the information of what is the root class to perhaps one of the worst places, which is in every instance of the microformat, whereas the XMDP itself should be defining what is a root class.<br />
<br />
Possible drawbacks:<br />
* How would you know which class name (other than "ufroot") was the root class name? e.g. <pre>class="vcard person ufroot"</pre><br />
** perhaps by only looking at classes defined in the XMDPs for the document.<br />
** perhaps by only allowing one root class name in addition to the "ufroot"<br />
** or perhaps by saying that all of the other class names in the same attribute are root class names (so that for example you could say: <pre>&lt;span class="root hreview hentry"&gt;</pre><br />
<br />
This is also very similar to, but not the same as, the [[mfo]] problem, and should be considered in that context as an independent solution.<br />
<br />
=== linking to the XMDP ===<br />
<br />
As hinted in the note on "when microformats may be in use", there are additional methods under discussion for linking to the XMDP in addition to the current method of using the profile attribute of the head element:<br />
* Using <nowiki><link rel="profile" href="link to XMDP"/></nowiki>. This method can be used now and will be formalized in XHTML 2. <br />
** A problem with this method is that it (still) requires access to the head element.<br />
* Using <nowiki><a rel="profile" href="link to XMDP">powered by microformat xyz</a></nowiki> in the body of the document.<br />
** As noted by a number of people, this approach has the added benefit of creating a viral marketing opportunity for the microformats used. For instance, developers could add badges saying they are using microformat xyz as suggested by the example.<br />
** Blog authoring environments allow you to insert links at will, so this squarely <abbr title="avoids">obviates</abbr> the need to access the head element.<br />
<br />
=== includes / aggregate profiles===<br />
<br />
Methods for including one or more values, properties, or an entire XMDP into an other XMDP as a way of creating an aggregate profile that effectively contains definitions from multiple profiles would be quite useful. They would enable documents with microformats to simply refer to a single profile URL rather than a complete space separated set of all the profile URLs of the microformats that may be in use.<br />
<br />
=== vocabulary aliasing ===<br />
<br />
An XMDP document could be used to define a microformat profile that is nothing more than a simple dictionary mapping between an existing, non-standard set of HTML classes and the terms in a standard microformat profile. This would allow a publisher to support a given microformat by merely using the URI of a new profile document as the value of an individual document's head/profile attribute, rather than modifying the individual class values throughout each document to conform to an existing profile. Initial suggestion with use case description in this [http://microformats.org/discuss/mail/microformats-discuss/2005-October/001623.html microformats-discuss post]. Note (from [http://microformats.org/discuss/mail/microformats-discuss/2005-October/001633.html Kevin's response]) that HTML class attributes can contain multiple values, e.g. class="post hentry", so a publisher doesn't have to discard their existing class values to use those of a microformat. <br />
<br />
=== subclassing / ontology addition ===<br />
One may want to introduce a new property (or value) and base it on an existing property (or value). In this sample XMDP, the value "self" is defined, based on the value "me" from XFN 1.1:<br />
<br />
<pre><br />
<nowiki><br />
<dl class="rel"><br />
<dt id='self'><a href="http://www.gmpg.org/xfn/11#me" rev="extends">self</a></dt><br />
<dd>This is a pointer to me, it extends the "me" value of XFN</dd><br />
</dl><br />
</nowiki><br />
</pre><br />
There are two interesting pieces that have been added, a URL with an anchor to another XMDP profile and a rev attribute. The rev value in<br />
this example is 'extends'. These means that the page this is refering too, is extended by the property SELF. So you could make an XMDP that<br />
lists all the possible rev attributes, 'extends', 'inverse', 'equivalent', etc. Then you could 'alias' one microformat property to another.<br />
<br />
A universal XMDP validator/parser/etc could extract data across two or more XMDP profiles and potentially reason between them. This could create a small ontology.<br />
<br />
It is not clear if this idea actually has utility or is simply a solution looking for a problem.<br />
<br />
=== XMDP XML Schema ===<br />
* [http://www.redantdesign.com/hcard/ XSD and XMDP for Microformats]<br />
The link shows a bad example of creating XMDP from an XSD schema. The big question I guess is why?<br />
Having XMDP defined in XSD should make it easier for machines to read Microformats, rules and strict data typing will allow Microformats to be validated when contained within an XML/XHTML document. If a document is using microformats with and XSD behind simple XPath queries can be used to harvest the information, this can then be rendered to straight XML for translation to RDF or other XML transport formats.<br />
<br />
XSD behind XMDP also has distinct advantages for CMS authors, the XSD sitting behind xforms or sxforms to allow data entry into a CMS can be used to generate XMDP and valid Microformats when rendering content. This in theory should make it easier for CMS authors to develop a semantic core around data before exporting to XHTML + Microformats, RDF etc. and/or make data querying via web services a little more straightforward.<br />
<br />
==== Follow up ====<br />
Having looked into Microformats a little more I realise how bad that example is; however I still feel that placing a schema behind XMDP is a worthwhile exercise. I don't mind spending a little time on this if anyone feels it's a worthwhile exercise, but I'd propose the following:<br />
* Define a loose set of microformat conventions (i.e. a meta property will be bound to an attribute etc.), and have these defined in a microformat namespace (mf:?).<br />
* Create a XSD for common microformat fields without structures (dtStart etc.), with XSD typing and mf: rules (i.e. mf:optional-html-attribute-binding="title" or mf:html-attribute-binding="href" - names were never my strong point )<br />
* Start working towards creating XSD schema including the common schema for agreed specifications<br />
<br />
There would still need to be some form of link between the XMDP and the defining XSD (profile attribute or link element?). With these in place it should be possible for an application like tails, or new apps to pick up on any Microformat in a page and display the data, without the application having to be aware of the specific Microformat standard.<br />
<br />
Microformats are cool, especially the fact that you don't have to be a rocket scientist to start using them. However if there can be a way of interleaving grassroots microformat adoption into the more complex semantic forms (RDF etc.), through XML then that's got to be a bonus?<br />
<br />
[http://www.redantdesign.com/hcard/take2.asp more here]<br />
<br />
== ID Attribute ==<br />
<div class="discussion"><br />
* A problem that I've had using XDMP is that it requires the use of the ID attribute (e.g. &lt;dt id="foo">foo&lt;/dt>) to define the term "foo". As (X)HTML only allows one element with any given ID, this raises problems if you need to define the same term multiple times -- e.g. to define "category" as a class within both hcard and hcalendar, or to define "copyright" as both a class value and a rel value. [[User:TobyInk|TobyInk]] 06:26, 18 Feb 2008 (PST)<br />
** Two things. First, "category" MUST NOT be different between hCard and hCalendar, and thus it is a feature, not a problem, that there can only be one id="category" between the two of them. Second, for the rel case, this is solved by using ID values prefixed with "rel-" for rel values. E.g. in http://gmpg.org/xmdp/1, rel-profile is defined with id="rel-profile", and the class name "profile" is defined with id="profile". [[User:Tantek|Tantek]] 17:48, 4 October 2009 (UTC)<br />
</div><br />
== automatic parsability enabling ==<br />
<br />
The current XMDP is useful for people to read and learn about a microformat, but of very limited utility to automate parsing microformats/[[poshformats]] (simply identification of vocabulary to parse for, and what attributes to parse for them). It would be nice if people could design their own poshformats, create an XMDP profile, and for the poshformat to be thus instantly parsable by machines. Here is the information that I think would need to be added to XMDP for this to be possible:<br />
<br />
For each profile defined:<br />
<br />
* What is/are the root class name(s) (as previous brainstormed above: [[xmdp-brainstorming#root_class_name_identification|root class name identification]]) of the microformats being defined by the XMDP (required)<br />
* What are the properties of each microformat? Or alternatively (and preferably), which microformat(s) may a property be used with? (to handle the common and encouraged case of vocabulary re-use across microformats) (required)<br />
<br />
For each property defined:<br />
<br />
* A human-readable description of what the property means (XMDP already has this)<br />
* Is it a class/rel/id (or rev, but deprecated) value (XMDP already has this)<br />
* Is it singular or plural? (default: plural)<br />
* What datatype is it? (e.g. text, URI, email, datetime, duration. default:text)<br />
* Might it contain a nested poshformat/microformat? If so, then this profile should link to the profile of the nested poshformat /microformat. (Multiple formats could be defined in the same XMDP profile, using ID attributes to link from one to the other.)<br />
* What nested subproperties might be found within it? Or alternatively (and preferably), whether a property is actually a subproperty, and if so, which properties may it be used inside? (again, to handle the common and encouraged case of vocabulary re-use) (Perhaps this could be indicated using a nested profile.)<br />
<br />
We must expect that there will always be some parsing rules (e.g. hAtom's [http://microformats.org/wiki/hatom#Entry_Author "hunt the author" game]) which will not be expressible in a machine readable profile format, but it may be possible to cover 90% of the information a parser should need for most microformats.<br />
<br />
Indeed experience has shown that any "real world" semantic markup languages that get significant use requires LOTS of special custom parsing rules (e.g. HTML is not fully parseable simply from the DTD, nor is RSS from the RSS DTD).<br />
<br />
Thus while it may make sense to take incremental steps towards capturing more about a microformat in XMDP, full enabling of machine parsability should not be a short-term (nor even medium-term) goal, as others have tried (DTD, RelaxNG, XML Schema) and failed to achieve this.<br />
<br />
== See Also ==<br />
* [[xmdp]]<br />
* [[xmdp-faq]]<br />
* [[xmdp-issues]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xmdp&diff=70205xmdp2020-07-18T16:35:33Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:XMDP}}<br />
<abbr title="XHTML Meta Data Profiles">XMDP</abbr> are XHTML Meta Data Profiles and the specification is documented externally at http://gmpg.org/xmdp/<br />
<br />
== See Also ==<br />
* [[xmdp-origins]]<br />
* [[xmdp-examples]]<br />
* [[xmdp-faq]]<br />
* [[xmdp-issues]]<br />
* [[xmdp-brainstorming]]<br />
* [[xmdp-profile]]<br />
* [[html5-profile]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xhtml-syndication-fr&diff=70204xhtml-syndication-fr2020-07-18T16:35:33Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:XHTML Syndication History}}<br />
<br />
L'idée d'utiliser la syndication XHTML n'est en aucun cas neuve.<br />
<br />
Quand l'idée à commencé à émerger sur la [http://microformats.org/discuss/ liste microformats-discuss], cela semblait comme une nouvelle idée. Ce ne l'est pas. Bien sûr, je ([[User:RyanKing|Ryan King]] n'étais pas un citoyen du [http://en.wikipedia.org/wiki/Blogosphere Blogistan] quand cela avait été précédemment discuté, aussi j'ai décidé de faire quelque recherche. Voici une brève histoire de l'idée :<br />
<br />
Mark Pilgrim [http://diveintomark.org/archives/2002/11/26/syndication_is_not_publication déclare] précisément que "Every few months, somebody floats the idea of doing away with RSS and replacing it with HTML or XHTML, 'because semantic markup is all we need'."<br />
<br />
Il avait apparemment raison parce que le sujet continue à émerger.<br />
<br />
Mark dit aussi :<br />
<br />
<blockquote><br />
I’ve talked about application posture before; it seems to me that this latest movement adopts the wrong posture. The entire success of RSS is predicated on the principle that you can keep doing whatever messed up stuff you’ve always done on your web pages… oh, and do this other thing too. Look, it’s simple, you can code it up in an hour with a few print statements and an escape function. By contrast, this latest XHTML-as-syndication movement seems to be based on the principle that syndication is so incredibly important that you must immediately stop whatever you’re doing with your web pages, upgrade to XHTML, validate your markup, restructure your home page to include all and only the content you’re willing to syndicate, and by the way, would you please unlearn that ugly nasty presentational page layout language you’ve been using for years and learn this wonderful happy structured semantic markup language instead?<br />
</blockquote><br />
In response, in seems that people are already *unlearning their crappy presentational markup shit.* Could it be that, given the move towards a separation of presentation and structure, we may now be able to create a syndication format in XHTML (at least for blogs)?<br />
<br />
--[[User:RyanKing|RyanKing]] 14:34, 27 Oct 2005 (PDT)<br />
<br />
== Chantier en cours ==<br />
Ce document est un chantier en cours. Si vous souhaitez contribuer, sentez-vous libre pour prendre l'un des liens à partir de la queue en bas de la page, analysez-le, écrivez un court résumé de la proposition et enregistrez toute problématique dans la section "Problématiques Soulevées".<br />
<br />
Référence : [http://diveintomark.org/archives/2002/11/26/syndication_is_not_publication]<br />
<br />
== Problématiques Soulevées ==<br />
Cette section est là pour documenter les problématiques rencontrées dans les premiers efforts pour utiliser XHTML comme un format de syndication.<br />
<br />
* Comment représentons-nous les dates en XHTML ? (voir au-dessus) [http://diveintomark.org/archives/2002/11/26/syndication_is_not_publication]<br />
* Requérir des éléments spécifiques de structure ne fait aucun sens [http://www.scottandrew.com/blog/archives/2002/11/semantic_overloading.html]<br />
<br />
== Profils proposés, etc ==<br />
=== Résumés de Sites en XHTML ===<br />
[http://w3.org/People/DanC Dan Connoly] du [http://w3.org W3C] a un "Site Summaries in XHTML" pour exprimer les canaux RDF 1.0 en XHTML. <br />
<br />
http://www.w3.org/2000/08/w3c-synd/<br />
<br />
Une interprétation vague de la spec : <br />
<br />
* the title of the channel is taken from the title of the page<br />
* each <code>&lt;div class="item"&gt;</code> on the page indicates an RSS item<br />
** each such div element should contain an h2 or h3 element; this serves as the item's title.<br />
** it should also contain a p element that serves as the item's description.<br />
**the p element should contain an <code>&lt;a rel="details" href="...ref..."&gt;...&lt;/a&gt;</code> which is taken as the URI of the item.<br />
**the div should contain some element with <code>class="date"</code>; its content should be a date in DD Month YYYY format; this is taken as the Dublin Core date of the item.<br />
<br />
=== Module Syndication XHTML ===<br />
19 juillet 2002 <br />
Joe Gregorio a publié un Module de Syndication XHTML.<br />
<br />
<blockquote><br />
The motivation for this document is to do away with RSS as a seperate file format. If web publishers and CMSs want to participate in content syndication then they have to produce two versions of their front page, the HTML version and the RSS version. A careful inspection of XHTML and common web practice shows that most of the information need to do syndication already exists in web pages published today. What is needed is a little extra information to make syndication possible.<br />
</blockquote><br />
Its done by way of an xml namespace which adds attributes to the XHTML. Example:<br />
<br />
<blockquote><pre><nowiki><br />
&lt;div class="singleItem" syn:item=""&gt;<br />
&lt;h4&gt;&lt;a syn:title="" syn:link="href" href="http://bitworking.org/2002/07/18.html#a245" <br />
class="weblogItemTitle"&gt;Bye-bye BurningBird&lt;/a&gt;&lt;/h4&gt;<br />
&lt;p class="firstItemParagraph" syn:description=""&gt;<br />
Hard to believe but &lt;a href="http://weblog.burningbird.net/archives/000370.php"&gt;BurningBird&lt;/a&gt;<br />
is closing down her blog. Best of wishes Shelly.&lt;/p&gt;<br />
&lt;div class="singleItemFooter"&gt;<br />
&lt;span class="itemPermaLinkTime"&gt;12:21:21 AM <br />
&lt;span class="itemPermaLink"&gt;&lt;a href="2002/07/18.html#a245"&gt;#&lt;/a&gt;<br />
&lt;/span&gt;&amp;nbsp;&amp;nbsp;<br />
&lt;/span&gt;<br />
&lt;/div&gt;<br />
&lt;/div&gt;<br />
</nowiki></pre></blockquote><br />
Reference: [http://bitworking.org/XHTML-Syndication-20020719.html]<br />
<br />
=== RSS : Profil XHTML ===<br />
Aaron Swartz a un profil XHTML. Description :<br />
<br />
<blockquote><br />
* the value of the <title> is the title of your site<br />
* (optional)the element with class="description" contains a short description<br />
* each element with class="item" on your page is an item, inside which:<br />
** the element with class="title" is the item's title<br />
** everything else is the content of the item<br />
** the link with rel="bookmark" is the URI of the item<br />
** (optional) the element with class="date" is the date<br />
</blockquote><br />
<br />
Référence : [http://www.aaronsw.com/2002/rssXP]<br />
<br />
== Discussion ==<br />
Cette section est pour rassembler des liens vers des trucs qui discutent de l'idée d'utiliser XHTML pour la syndication. Personnellement je ne suis pas intéressé par les propositions/idées qui ne décollent pas. Je veux apprendre des erreurs précédentes. Sentez-vous libre d'ajouter à cette liste avec un résumé, si vous le souhaitez. --[[User:RyanKing|RyanKing]] 14:34, 27 Oct 2005 (PDT)<br />
<br />
* http://www.dashes.com/anil/2002/11/22/syndication_for<br />
* http://www.actsofvolition.com/archives/2002/march/blogmltheweblog<br />
* http://weblog.burningbird.net/archives/2002/11/26/rss-push-back<br />
* http://www.intertwingly.net/blog/977.html<br />
<br />
= Queue =<br />
Le fait que ce document soit un chantier en cours, cette section est simplement une liste de liens qui ont besoin d'être analysés.<br />
* http://ln.hixie.ch/?start=1038263537&count=1<br />
* http://www.aaronsw.com/weblog/000738<br />
* http://www.kryogenix.org/days/2002/11/24/instead<br />
* http://tantek.com/log/2002/11.html#L20021124t1454<br />
* http://tantek.com/log/2002/11.html#L20021124t0620<br />
* http://www.scottandrew.com/weblog/2002_11#a000469<br />
* http://bitworking.org/2002/07/19.html#a251<br />
* http://bitworking.org/2002/07/15.html#a244<br />
* http://diveintomark.org/archives/2002/11/26/the_rebellion_will_be_syndicated<br />
* http://diveintomark.org/archives/2002/11/26#syndication_is_not_publication<br />
* http://www.yetanothercommunitysystem.com/yacs/articles/view.php/438<br />
* http://diveintomark.org/archives/2002/11/26/syndication_is_not_publication<br />
* http://www.dellah.com/orient/2002/11/26/the-xhtml-syndication-debate<br />
* http://nilesh.org/weblog/2002/11/xhtml-syndication/<br />
* http://dannyayers.com/archives/2003/04/30/xhtml-syndication-module/<br />
* http://dannyayers.com/archives/2005/08/27/hatom-no-seriously/<br />
* http://www.dashes.com/anil/2002/11/22/syndication_for<br />
<br />
(tidy me ;-)<br />
Dan Brickley, commentaire sur http://dannyayers.com/archives/2005/11/26/history/ :<br />
Eric van der Vlist had an implementation of this back in 2000 http://groups.yahoo.com/group/XHTML-L/message/683. We made a version available on the ILRT site http://www.ilrt.bris.ac.uk/discovery/2000/08/hss/sw.html, which fed into the more widely used W3C version http://www.w3.org/2000/08/w3c-synd/ of this idea. I still think this is the way to go, ultimately. The use cases just aren’t different enough to justify having completely different document formats, solely on basis of their dissemination mechanism. But I tried raising this in early Atom days and got told it was a silly idea. Maybe as the XML doc formats mature (XHTML2, CDF) it’ll be time to revisit again.</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xfolk-to-rdf&diff=70203xfolk-to-rdf2020-07-18T16:35:32Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:xFolk/hReview → RDF}}<br />
<br />
Only a rough sketch on a piece of paper so far. "X" is the review, "Y" is the item being reviewed.<br />
<br />
[http://buzzword.org.uk/2008/hReview/to-rdf.png http://buzzword.org.uk/2008/hReview/to-rdf.jpeg]<br />
<br />
RDF prefixes used in above diagramme:<br />
<br />
; <code>rev</code><br />
: http://www.purl.org/stuff/rev#<br />
; <code>tag</code><br />
: http://www.holygoat.co.uk/owl/redwood/0.1/tags/<br />
; <code>dc</code><br />
: http://purl.org/dc/terms/<br />
; <code>foaf</code><br />
: http://xmlns.com/foaf/0.1/<br />
<br />
== xFolk / hReview Equivalence ==<br />
<br />
xFolk can be thought of as a minimal version of hReview.<br />
<br />
{| border="1"<br />
|-<br />
! hReview Term<br />
! xFolk Term<br />
|-<br />
| hreview<br />
| xfolkentry<br />
|-<br />
| version<br />
| /<br />
|-<br />
| summary<br />
| /<br />
|-<br />
| type<br />
| type is always "url"<br />
|-<br />
| item fn<br />
| taggedlink (link text)<br />
|-<br />
| item url<br />
| taggedlink (href)<br />
|-<br />
| item photo<br />
| /<br />
|-<br />
| reviewer<br />
| /<br />
|-<br />
| dtreviewed<br />
| /<br />
|-<br />
| rating (best, worst)<br />
| /<br />
|-<br />
| description<br />
| description<br />
|-<br />
| tag<br />
| tag<br />
|-<br />
| permalink<br />
| /<br />
|-<br />
| license<br />
| /<br />
|}<br />
<br />
With this in mind, an xFolk entry can be treated as simply a funny-looking hReview and the hReview to RDF mapping then applied to xFolk.</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xfolk-profile-ja&diff=70202xfolk-profile-ja2020-07-18T16:35:31Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:xFolk メタデータプロファイル}}<br />
<!-- 2009-08-06T13:22:07 --><br />
以下は [[xfolk-ja|xFolk]] 仕様のための [http://gmpg.org/xmdp/ XMDP] プロファイルです。<br />
<br />
== 作者==<br />
<ul id="author"><br />
<li>[[User:Tantek|Tantek Çelik]]<br />
<li>[http://thecommunityengine.com/home Bud Gibson]</li><br />
</ul><br />
<br />
== URL ==<br />
このプロファイルは microformats.org 上で、独立した XMDP ファイルとして管理します。<br />
* http://microformats.org/profile/xfolk<br />
* 短縮URL: http://ufs.cc/x/xfolk<br />
<br />
== 使用法 ==<br />
&lt;HEAD&gt;タグ内で次のように (X)HTML ファイルを参照します。<br />
<source lang=html4strict><br />
<head profile='http://microformats.org/profile/xfolk'><br />
</source><br />
<br />
== プロファイル==<br />
<p>(メタデータプロファイルについては)[http://www.w3.org/TR/html401/struct/global.html#h-7.4.4.3 HTML4 Meta data profiles] で述べられ、また [http://gmpg.org/xmdp/ Xhmtl Meta Data Profiles] では特に [http://gmpg.org/xfn/11 XFN 1.1 relationships meta data profile] と [[xoxo-ja|XOXO Profile]] に関連することがさらに詳しく説明されています。</p><br />
<br />
<p>このプロファイルには、機能している xFolk の実装で使うのに充分なだけの class 属性の値のセットがあると作者は信じています。このプロファイルは不完全で、xFolk が発展するに伴い変更の対象となる可能性があります。</p><br />
<br />
<p>xFolk は重要なな構成要素として [[rel-tag-ja|rel-tag]] を使っているため、どの xFolk プロファイルにも rel-tag を含めるのが理にかなっているということに注意してください。</p><br />
<br />
<source lang=html4strict><br />
<dl class="profile"><br />
<dt id="class">class</dt><br />
<dd><br />
<p>[http://www.w3.org/TR/html401/struct/global.html#adef-class HTML4 definition of the 'class' attribute]。このメタデータプロファイルでは、'class' 属性の値とその意味が[http://www.w3.org/TR/WD-htmllink-970328#profile "Hypertext Links in HTML"のドラフト]の提案に従って定義されています。</p><br />
<dl><br />
<dt id="xfolkentry">xfolkentry</dt><br />
<dd>xFolk エントリーのコンテナ要素であることを示します。xFolk エントリーとは、収集されてフォークソノミーになってほしいメタデータ付きのブックマークを意味しています。class 属性の値 xfolkentry は、普通 &lt;div&gt;,、&lt;ul&gt;,、&lt;ol&gt;,、&lt;dt&gt;,、&lt;p&gt;,、&lt;span&gt;, 要素に割り当てられます。xFolk の xfolkentry を持つ要素は任意の深さにネストすることができます。</dd><br />
<dt id="taggedlink">taggedlink</dt><br />
<dd>taggedlink の class を持つ &lt;a&gt;, タグは xFolk エントリーがブックマークする項目の URL を示しています。taggedlink class の &lt;a&gt;, 要素は xfolkentry class を持つ各要素の中にただ一つだけ現れなければなりません。ブックマークの題名は次の順で見ていき、利用できる物に決まります。(1) 任意の title 属性。(2) &lt;a&gt;, 要素自身の値。</dd><br />
<dt id="description">description</dt><br />
<dd>xFolk エントリーのより詳しい説明。普通、 &lt;dd&gt;,、&lt;li&gt;,、&lt;p&gt;,、&lt;span&gt;, 要素に割り当てられます。<code>description</code> の class を持つ要素は任意で、複数あってもかまいません。<code>description</code> class の要素が複数ある時には、文書に現れる順と同じと看做されます。</dd><br />
<dt id="extended">extended</dt><br />
<dd><code>description</code> と同じ意味を持つ class の値で、廃止予定です。</dd><br />
</dl><br />
</dd><br />
</dl><br />
</source><br />
<br />
== 関連ページ ==<br />
{{template:xfolk-related-pages}}<br />
* [[xfolk-0.5-XMDP]]<br />
* [[xfolk-ja|xFolk]](日本語)<br />
* [[xfolk-issues-ja|xFolk の問題]](日本語)</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xfolk-profile&diff=70201xfolk-profile2020-07-18T16:35:29Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:xFolk meta data profile}}<br />
The following is an [http://gmpg.org/xmdp/ XMDP] profile for the [[xfolk|xFolk]] specification.<br />
<br />
== Authors ==<br />
<ul id="author"><br />
<li>[[User:Tantek|Tantek Çelik]]<br />
<li>[http://thecommunityengine.com/home Bud Gibson]</li><br />
</ul><br />
<br />
== URLs ==<br />
This profile is hosted as a separate XMDP file on microformats.org:<br />
* http://microformats.org/profile/xfolk<br />
* shortURL: http://ufs.cc/x/xfolk<br />
<br />
== Usage ==<br />
Profiles are referenced in (X)HTML files in the &lt;HEAD&gt; tag, e.g.:<br />
<source lang=html4strict><br />
<head profile='http://microformats.org/profile/xfolk'><br />
</source><br />
<br />
== Profile ==<br />
<p>As described in [http://www.w3.org/TR/html401/struct/global.html#h-7.4.4.3 HTML4 Meta data profiles] and further elaborated on in [http://gmpg.org/xmdp/ XHTML Meta Data Profiles] with specific reference to the [http://gmpg.org/xfn/11 XFN 1.1 relationships meta data profile] and <br />
[[xoxo|XOXO Profile]].</p><br />
<br />
<p>The author Bud believes this profile provides a set of class attribute values sufficient to be used in working implementations of xFolk. The profile may be incomplete and is subject to change as xFolk evolves.</p><br />
<br />
<p>Note that in practice it makes sense to include the [[rel-tag]] profile in any profile of xFolk, since xFolk makes critical use of rel-tag as a building block.</p><br />
<br />
<source lang=html4strict><br />
<dl class="profile"><br />
<dt id="class">class</dt><br />
<dd><br />
<p>[http://www.w3.org/TR/html401/struct/global.html#adef-class HTML4 definition of the 'class' attribute]. This meta data profile defines some 'class' attribute values (class names) and their meanings as suggested by a [http://www.w3.org/TR/WD-htmllink-970328#profile" draft of "Hypertext Links in HTML"]:</p><br />
<dl><br />
<dt id="xfolkentry">xfolkentry</dt><br />
<dd>Indicates a container element for an xFolk entry. An xFolk entry indicates one bookmark with supporting metadata that the user wants to have aggregated into a folksonomy. The xfolkentry class attribute value is usually applied to &lt;div&gt;, &lt;ul&gt;, &lt;ol&gt;, &lt;dt&gt;, &lt;p&gt; or &lt;span&gt; elements. xFolk elements contained in an xfolkentry may be nested at an arbitrary depth.</dd><br />
<dt id="taggedlink">taggedlink</dt><br />
<dd>An &lt;a&gt; tag of class taggedlink indicates the URL of the item the xFolk entry bookmarks. One and only one &lt;a&gt; element of class taggedlink must occur within each element of class xfolkentry. The title of the bookmark is in order of availability: (1) the value of an optional title attribute; (2) The value of the &lt;a&gt; element itself.</dd><br />
<dt id="description">description</dt><br />
<dd>A further description of the xFolk entry. Typically applied to &lt;dd&gt;, &lt;li&gt;, &lt;p&gt;, and &lt;span&gt; elements. Elements of class <code>description</code> are optional and may occur multiply. When multiple elements of class <code>description</code> are present, they are assumed to be in document order.</dd><br />
<dt id="extended">extended</dt><br />
<dd>A deprecated class value that is equivalent to <code>description</code>.</dd><br />
</dl><br />
</dd><br />
</dl><br />
</source><br />
<br />
== FAQ ==<br />
<br />
<div class="issues"><br />
* Does the above snippet need fixing? I am not sure whether it's supposed to be displayed as "HTML source code" - or is this meant to be the actual HTML. - [[User:Drozzy]]<br />
** Yes it is meant to be displayed as HTML source, hence the <code>&lt;source&gt;</code> tags surrounding it. If you want to view the profile as a page, see http://microformats.org/profile/xfolk (also linked from the top of this page) - [[User:Tantek|Tantek]] 17:07, 22 March 2010 (UTC)<br />
</div><br />
<br />
==Related pages==<br />
{{template:xfolk-related-pages}}<br />
* [[xfolk-0.5-XMDP]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xfolk-ja&diff=70200xfolk-ja2020-07-18T16:35:28Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:xFolk RC1}}<br />
<!-- english: 2010-05-28T05:34:41 --><br />
{{DraftSpecification-ja}}<br />
<br />
'''xFolk'''("xFolksonomy"に由来)は、ブックマークのコレクションを公開するための簡単でオープンなフォーマットです。これによって、サービスがウェブベースのブックマークソフトウェアでのユーザー体験の向上とデータの共有をよりうまくできるようになります。xFolk は HTML または XHTML、Atom、RSS、任意の XML に埋め込むことができます。これはオープンな[[microformats-ja|マイクロフォーマット]]標準の一つです。<br />
<br />
__TOC__<br />
<br />
== 仕様ドラフト ==<br />
<br />
=== 編者/作者 ===<br />
[http://thecommunityengine.com/ Bud Gibson] ([http://thecommunityengine.com The Community Engine])<br />
<br />
=== 著作権 ===<br />
{{MicroFormatCopyrightStatement2005}}<br />
<br />
=== 特許 ===<br />
{{MicroFormatPatentStatement-ja}}<br />
<br />
=== 謝辞 ===<br />
各項目が、部分的に、一度にたくさんのカテゴリーに属していてもかまわないというアイディアをもたらしてくれた [http://www.cnbc.cmu.edu/~plaut/ David Plaut] に感謝します。また、より最近ですが、思慮深い批評と推進で xFolk の開発に貢献してくれた [http://tantek.com/ Tantek Celik]、[http://epeus.blogspot.com/ Kevin Marks]、[http://steve.osdir.com/ Steve Mallet]、[http://hybernaut.com/ Brian DelVecchio]、[http://blogmarks.net Francois Hodierne]に感謝します。<br />
<br />
== はじめに ==<br />
ソーシャルブックマークサービスでは、ユーザーはブックマークを保存し、タグを付け、ほかのユーザーと共有します。ここ数年でこういったサービスの数は[http://en.wikipedia.org/wiki/Social_bookmarking 20を超え]、その中には[http://del.icio.us del.icio.us]、[http://furl.net furl]、[http://de.lirio.us de.lirio.us](訳注:現在は [http://www.simpy.com/ Simpy] に引き継がれたようです)、jots(訳注:現在はサービス終了)、[http://blogmarks.net blogmarks]という人気サービス例も含まれます。 <br />
<br />
相互運用可能なデータのオープンスタンダードがないことは、ソーシャルブックマークサービスを使う上での大きな問題です。オープンスタンダードがあればソーシャルブックマークデータを簡単に集めて再構築し、gataga(訳注:現在はサービス終了)による実験的なブックマーク検索エンジンのような方向性の、新しいサービスを発明することが可能になるのです。また、[http://johnvey.com/features/deliciousdirector/ 目下は del.icio.us で行われている]ような、サービスをまたがって機能する JavaScript を書いてユーザー体験を全面的に向上させることもできるようになります。<br />
<br />
xFolk は両方の利点を持つことを目標にした、ソーシャルブックマークのオープンスタンダードです。xFolk を取り入れたソーシャルブックマークサービスは、データサービスの一歩先を歩くことになるでしょう。ですが、データ自体はサードパーティのスクリプトが操作したり、共有したりすることが簡単な物になります。その結果、ブックマークサービスは低コストでユーザーに幅広い選択肢を提供し、本質的な差別化に力を注ぐことができるようになります。独立したブックマーク保管サービスを運営する個人やグループは、自分で作れる以上の幅広い機能を選べるようになります。<br />
<br />
== セマンティック XHTML デザイン指針 ==<br />
{{semantic-xhtml-design-principles-ja}}<br />
<br />
== フォーマット ==<br />
ソーシャルブックマークサービス、リンクブログ(訳注:リンクとそれに対するコメントからなるブログ)、[http://thecommunityengine.com/home/archives/xfolk 他所]でのリポートを幅広く分析した結果、ブックマークサービスと'''たくさんの'''異なるリンクブログで公開されているデータは暗黙的に次のスキーマに従って書かれていることが分かりました。<br />
<br />
* ブックマークしたりタグを付けるリンク<br />
* エントリーの題名<br />
* リンクに付けるタグ<br />
* リンクの追加説明や概要<br />
<br />
初期の xFolk 標準が繰り返し使われたおかげで、この一般的なスキーマは次のようにしてマークアップへと変換できることが実証されています。<br />
<br />
# 各エントリーに <code>xfolkentry</code> という class を持つコンテナ要素を作る<br />
# ブックマークしたりタグを付けるリンクには <code>taggedlink</code> という class を持つ &lt;a&gt; 要素を使う<br />
# エントリーの題名には、もしあれば &lt;a&gt; 要素の title 属性を、なければその値を使う<br />
# タグには [[rel-tag-ja|rel-tag]] を使う<br />
# 追加説明や概要には、<code>description</code> という class を持つコンテナ要素(&lt;p&gt; など)を使う<br />
<br />
xFolk エントリーでは、題名を伴ったタグを付けるリンクが必須で、他の要素は全て省略できます。エントリーには複数のタグあってもかまいませんし、<code>description</code> class の要素が複数あってもかまいません。<code>description</code> class を持つ複数の要素の順序は、文書に現れるままの順です。xFolk エントリー内の意味的な要素は任意の深さにネストできます。<br />
<br />
たくさんのソーシャルブックマークシステムが存在して、それぞれが独自のマークアップの慣例を持っています。さらに、たくさんの人が既に個人のリンクブログを公表しています。xFolk の第一の目標は、こうした現在の慣例に適合させるのが簡単であるようデザインすることなので、xFolk エントリーで使う要素の種類には厳密な前提条件がほとんどありません。意味を決める機能は、要素よりも class 属性や([[rel-tag-ja|rel-tag]] の場合は)rel 属性の値に与えられるのです。<br />
<br />
開発者は [http://www.w3.org/TR/xpath XPath] か相当する文法を使って xFolk エントリーの要素にアクセスすることが期待されます。XPath を使うための条件は、HTML 文書が整形式であることです。妥当な文書ではなくてもかまいません。このため、最善ではないかもしれませんが、妥当性検証をしていない HTML 文書の中で xFolk が使えるようになるのです。<br />
<br />
=== XMDP プロファイル ===<br />
xFolk の [http://gmpg.org/xmdp XMDP] プロファイルは、[[xfolk-profile-ja|xFolk profile]] を参照してください。<br />
<br />
== 例 ==<br />
<br />
下に [http://del.icio.us del.icio.us] の標準マークアップに見られるブックマークの例を示します。要素の class 属性の値を変更して xFolk に適合させる必要のある場所は、行の末尾にコメントで印を付けています。<br />
<pre>&lt;div class="post"&gt; <!--変更する箇所--><br />
&lt;div&gt;<br />
&lt;a class="delLink" href="http://www.sifry.com/alerts/archives/000306.html"&gt; <!--変更する箇所--><br />
Sifry's Alerts: Technorati launches Related Tags<br />
&lt;/a&gt; <br />
&lt;/div&gt;<br />
&lt;div class="extended"&gt; <!--変更する箇所--><br />
Ever wanted to see what posts are related to other posts, what tags <br />
are related to others? Now you can! Just check under the Tag <br />
description on most tag pages, like this one, or this one, and you'll<br />
see the patterns. Can you smell the emergence?<br />
どの投稿がどの投稿と関係あるのか、どのタグがどのタグと関係あるのか、<br />
分かるようになってほしいとずっと思ってた。ようやくなった!<br />
こことかこことか、ほとんどのタグページでタグを記述した部分の下をチェックしてほしい。<br />
何かが起きそうなにおいがするだろ?<br />
(訳注:『Emergence』は書名。邦題は『創発―蟻・脳・都市・ソフトウェアの自己組織化ネットワーク』。<br />
個の局所的な働きが全体の組織だった働きを生むという現象を解説)<br />
&lt;/div&gt;<br />
&lt;div class="meta"&gt;<br />
to<br />
&lt;a class="delNav" href="/fpgibson/folksonomy"&gt;folksonomy&lt;/a&gt; <!--変更する箇所--><br />
&lt;a class="delNav" href="/fpgibson/technorati"&gt;technorati&lt;/a&gt; <!--変更する箇所--><br />
... &lt;a class="delNav" href="/url/cbcabf7de070fdb46598ee679367be49"&gt;<br />
and 1 other person<br />
&lt;/a&gt;<br />
... on 2005-04-09<br />
&lt;/div&gt;<br />
&lt;/div&gt;</pre><br />
<br />
これに相当する xFolk は以下の通りです。class 属性の変更が必要だった行の末尾にコメントを付けています。<br />
<pre><nowiki><br />
&lt;div class="xfolkentry"&gt; <!-- 変更した箇所 --><br />
&lt;div&gt;<br />
&lt;a class="taggedlink" href="http://www.sifry.com/alerts/archives/000306.html"&gt; <!-- 変更した箇所 --><br />
Sifry's Alerts: Technorati launches Related Tags<br />
&lt;/a&gt; <br />
&lt;/div&gt;<br />
&lt;div class="description"&gt; <!-- 変更した箇所 --><br />
Ever wanted to see what posts are related to other posts, what tags <br />
are related to others? Now you can! Just check under the Tag <br />
description on most tag pages, like this one, or this one, and you'll<br />
see the patterns. Can you smell the emergence?<br />
どの投稿がどの投稿と関係あるのか、どのタグがどのタグと関係あるのか、<br />
分かるようになってほしいとずっと思ってた。ようやくなった!<br />
こことかこことか、ほとんどのタグページでタグを記述した部分の下をチェックしてほしい。<br />
何かが起きそうなにおいがするだろ?<br />
&lt;/div&gt;<br />
&lt;div class="meta"&gt;<br />
to<br />
&lt;a rel="tag" href="/fpgibson/folksonomy"&gt;folksonomy&lt;/a&gt; <!-- 変更した箇所 --><br />
&lt;a rel="tag" href="/fpgibson/technorati"&gt;technorati&lt;/a&gt; <!-- 変更した箇所 --><br />
... &lt;a class="delNav" href="/url/cbcabf7de070fdb46598ee679367be49"&gt;<br />
and 1 other person<br />
&lt;/a&gt;<br />
... on 2005-04-09<br />
&lt;/div&gt;<br />
&lt;/div&gt;<br />
</nowiki></pre><br />
<br />
マークアップを xFolk に従う物に変換するのは、ほとんどの場合簡単です。xFolk の長所は、<br />
全てのサービスやリンクブログにまたがって、精度を失うことの無いまま使い回せる class 属性のセットを提供していることです。<br />
次の節ではこの点を説明する例をさらに多く提示します。<br />
<br />
下は(リストのマークアップを使った)別の簡単な例です。<br />
<pre><br />
<nowiki><br />
<ul><!--xFolk はブックマークの *コレクション* に関する物なのです--><br />
<li><br />
<ul class="xfolkentry"> <br />
<li><a class="taggedlink" href="http://microformats.org/wiki/Main_Page">microformats wiki</a></li><br />
<li class="description">マイクロフォーマットを勉強して実践する主な場所で……</li><br />
<li class="description">コミュニティ駆動の Wiki</li><br />
<li class="meta"><br />
Tags :<br />
<a rel="tag" href="http://del.icio.us/tag/microformats">microformats</a><br />
<a rel="tag" href="http://del.icio.us/tag/websocial">websocial</a><br />
<a rel="tag" href="http://del.icio.us/tag/semantics">semantics</a><br />
</li><br />
</ul><br />
</li><br />
<br />
<li><br />
<!--上と同様の xfolkentryなど……--><br />
</li><br />
<br />
</ul><br />
</nowiki><br />
</pre><br />
<br />
<br />
== より多くの例 ==<br />
<br />
開発者がサイトに xFolk を取り入れるのに役立つ例がたくさんあります。<br />
<br />
=== 実世界での例 ===<br />
<br />
実際に機能中の、xFolk でブックマークを公開しているシステムの例です。パース、索引作成、整理などを試せる「実際に利用されている」例を探し始めるには絶好でしょう。自分が xFolk を使ってブックマークを公表しているなら、遠慮せずそのサイトをこのリストの一番上に加えてください。リストが大きくなり過ぎたら、別の Wiki ページを作ります。<br />
<br />
* [http://greenvoice.com Greenvoice] はユーザーが作る環境ニュースのリンクリストで、xFolk でマークアップされています。<br />
* [http://www.idoneos.com Idoneos.com] はコンセプトごとに繋がった情報ページ(多くはスペイン語)のコレクションで、xFolk を使ってブックマークにタグ付けしています。<br />
* [http://ashaszin.lautre.net/ Ashaszin] - [http://spip.net SPIP] を使って運営されている小さなブログ。xFolk でタグ付けした del.icio.us リンクとウェブフィードがあります。<br />
* [http://www.rolandinsh.lv/blog/ Rolands Umbrovskis - blog] ブログの記事は全て xFolk でマークアップされています。<br />
* [http://www.bbc.co.uk/worldservice/bangladeshboat BBC World Service Bangladesh River Journey] はソーシャルネットワークマッシュアップで、hAtom エントリーのブックマークに、基本的な xFolk を使っています。[http://dharmafly.com/blog/bangladeshboat Dharmafly のブログでの議論] を参照。<br />
* [http://waferbaby.com/hussy waferbaby の Hussy] は、現在 xFolk を使ってリンクを公開しています(訳注:2008 年 11 月現在、確認できません)。<br />
* [http://smarking.com/ Smarking] は、現在 xFolk を使って(検索結果を含む)共有リンクを公開しています。<br />
* [http://unalog.com unalog] は、現在 xFolk を使って(検索結果を含む)共有リンクを公開しています(訳注:現在終了)。<br />
* [http://de.lirio.us de.lirio.us] は、現在 xFolk を使ってブックマークを公開しています(<code>description</code> の代わりに、廃止予定の <code>extended</code> という class 属性を使っています。[[xfolk-profile-ja |XMDP]] を参照)(訳注:現在は [http://www.simpy.com/ Simpy] に引き継がれ、そちらでは xFolk は使用されていないようです)。<br />
* [http://blogmarks.net/my/tools,export blogmarks] は現在、ブログへのブックマークを xFolk でエクスポートします(訳注:アカウント未所持のため、未確認。通常ページでは xFolk を使用しています)。<br />
* [http://thecommunityengine.com The Community Engine] は、[http://thecommunityengine.com/home メインエントリー]と[http://thecommunityengine.com/webcites 公開ブックマーク]で xFolk を使っています(<code>description</code> の代わりに、廃止予定の <code>extended</code> という class 属性を使っています。[[xfolk-profile-ja |XMDP]] を参照)。<br />
* [http://groovymother.com/links/ Groovy Links] は xFolk でマークアップされているリンクブログです(訳注:現在はこのページは無く、[http://groovymother.com/ ホームページ]が対応)。<br />
* [http://tommorris.org/blog/ Tom Morris] - 日々の del.icio.us リンクが xFolk、[[hcard-ja|hCard]]、[[vote-links-ja|Vote Links]] でマークアップされています。<br />
<br />
=== <div id=".E3.81.95.E3.82.89.E3.81.AA.E3.82.8B.E3.82.BD.E3.83.BC.E3.82.B7.E3.83.A3.E3.83.AB.E3.83.96.E3.83.83.E3.82.AF.E3.83.9E.E3.83.BC.E3.82.AF.E3.82.B5.E3.83.BC.E3.83.93.E3.82.B9" name=".E3.81.95.E3.82.89.E3.81.AA.E3.82.8B.E3.82.BD.E3.83.BC.E3.82.B7.E3.83.A3.E3.83.AB.E3.83.96.E3.83.83.E3.82.AF.E3.83.9E.E3.83.BC.E3.82.AF.E3.82.B5.E3.83.BC.E3.83.93.E3.82.B9">ソーシャルブックマークサービスへの付加</div> ===<br />
<br />
<br />
次の例では、一つのサービスに、どのようにして xFolk を適用できるのかが説明されています(訳注:現在の scuttle 0.7.4 では xFolk を使ってリンクがマークアップされています)。<br />
<br />
* [[xfolk-scuttle | scuttle]]<br />
<br />
=== リンクブログ ===<br />
<br />
ソーシャルブックマークサービスは、人々がリンクを公開する最近の例と言うに過ぎません。リンクブログは、ほとんどブログの初期の頃からありました。これはその発端から、あまり意味的でないマークアップをされる傾向があったため、xFolk にするにはもう少し労力を使う必要があります。次の例は、個別の作業説明し、それぞれがどのようにしてうまくいくのかを描いています。<br />
<br />
* [[xfolk-kottke | kottke]]<br />
* [[xfolk-pollas | pollas]]<br />
* [[xfolk-jacobian | jacobian]]<br />
* [[xfolk-julian-bez | julian-bez]]<br />
<br />
=== スパム ===<br />
スパム業者には、リンクファームにタグを付けるのに xFolk を利用している所もあります。(恐らく、実際にそのサイトにリンクさせるには、悪いアイディアでしょう。)例えば、<br />
* phontron.info<br />
<br />
== 実装 ==<br />
<br />
次の実装は、xFolk を作ったり使ったりして開発されました。もし xFolk の実装を持っていたらこのリストの一番上に自由に加えてください。リストが大きくなり過ぎた時には、別の Wiki ページを作ります。<br />
<br />
* [http://sourceforge.jp/projects/sfnet_semanticscuttle/ SemanticScuttle] は自分で扱えるソーシャルブックマークソフトウェアで、xFolk をネイティブサポートしています。<br />
* [http://buzka.com Buzka]はソーシャルブックマークサービスで、現在は xFolk をサポートしています(訳注:2008年11月現在はサポートされていないようです)。<br />
* [http://blip.tv Blip.tv]は動画ホスティングサイトで、現在は [http://blog.blip.tv/blog/2006/08/19/blip-supports-xfolk/ xFolk をサポートしています](訳注:2008年11月現在はサポートされていないようです)。<br />
* [http://www.s9y.org/ Serendipity] は PHP によるフレキシブルなブログ/CMS アプリケーションです。現在、xFolk をサポートする[http://www.numblog.de/archives/241-Social-Bookmarks-Plugin-for-Serendipity.html ソーシャルブックマークプラグイン](ダウンロードは Serendipity の [http://spartacus.s9y.org/index.php?mode=bygroups_sidebar_en Plugin/Template ページ]からできます)があります。<br />
* [http://claimid.com claimID] は各人のリンクを xFolk で実装しています。<br />
* [http://ma.gnolia.com ma.gnolia] は、現在 xFolk をサポートしています。<br />
* [http://smarking.com/ Smarking.com](ソーシャルブックマークサービス)はタグ付けされたリンクを xFolk でマークアップしています!豆知識:[http://3spots.blogspot.com/2006/05/social-bookmarking-smarking.html 3spots: Social + bookMARKING = Smarking]。このページ自体は [[hreview-ja|hReview]] です。<br />
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - Tails エクステンションの Flock 0.5.12 移植版。hCard、hCalendar、xFolk、hReview を探して便利なツールバーに表示します(訳注:現在のバージョンの Flock には未対応のため、未確認)。<br />
* [http://blog.codeeg.com/tails-firefox-extension/ Tails] は、ウェブページにマイクロフォーマット([[hcard-ja|hCard]]、[[hcalendar-ja|hCalendar]]、[[hreview-ja|hReview]]、[[xfolk-ja|xFolk]])ががあれば教えてくれる Firefox エクステンションです(訳注:Firefox 2 では動作しますが、Firefox 3 ではインストールできません)。<br />
* Bud Gibson と Mike Migurski は、xFolk reblog ツールでありサービスである [http://thecommunityengine.com/veg-o-matic veg-o-matic] を [http://thecommunityengine.com/home/archives/2005/09/vegomatic_an_al.html 書きました]。<br />
* [http://inside.glnetworks.de/ Martin Rehfeld] は [http://blogmatrix.blogmatrix.com/ David Janes] の仕事を改良して、xFolk を含む多くのマイクロフォーマット要素を見つけてポップアップメニューによって提供する [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ スクリプト] を作りました。''これは現在、Firefox 1.5+/Greasemonkey 0.6.4+ で動作します。<br />
* [http://www.midgard-project.org/midcom-permalink-6416db7e1f0e297b4cf3dcc285702a8d net.nemein.bookmarks] は [http://www.midgard-project.org/ Midgard CMS] 中のブックマーク管理プログラムで、書き出しのネイティブフォーマットとして xFolk を使用します。[http://bergie.iki.fi/links/ 例] 参照(2008年11月現在、確認できません)。<br />
* [http://de.lirio.us de.lirio.us] は現在、xFolk 0.4(説明箇所で <code>extended</code> class 属性を使用)を使ってブックマークを公表しています(訳注:現在は Simpy に引き継がれ、そちらでは xFolk は使われていないようです)。<br />
* [http://dev.blogmarks.net/wiki/BlogSync blogmarks] は現在、ブックマークをブログへ xFolk 0.4 を使ってエクスポートします(ページを下へスクロールしてのエクスポート例を見てください。<code>description</code> の代わりに <code>extended</code> class 属性を使っています)。<br />
* [http://pokkari.com/microformat/javadoc/ Sivitols] は Java のマイクロフォーマット用ライブラリです(現在リンク切れ)。現在は xFolk RC1 標準しか実装されていませんが、より多くのマイクロフォーマットのサポートが予定されています。(出典は [http://blog.blip.tv/blog/microformats/])<br />
* [http://bildu.net Bildu] は xFolk(rel-tag も)をサポートするバスク語のソーシャルブックマークサービスです(訳注:サービスというより、使っているオープンソースソフトウェア [http://sourceforge.net/projects/scuttle/ scuttle] が xFolk をサポート)。<br />
* [http://bookmarks.excite.co.uk/ Excite Bookmarks] は xFolk と rel-tag をサポートするソーシャルブックマークサービスです(訳注:2008年11月現在、rel-tag のみサポート)。<br />
<br />
== 参照 ==<br />
=== 規範的な参考文献 ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]<br />
* [[rel-tag-ja|rel-tag]]<br />
<br />
=== その他の参考文献 ===<br />
* [http://thecommunityengine.com/home/archives/xfolk xFolk に関する記事](リンク切れ)<br />
* [http://thecommunityengine.com/home/archives/tags/microformats マイクロフォーマットのビジネス上の価値](リンク切れ)<br />
* [http://gataga.com gataga ソーシャルブックマーク検索エンジン](ドメイン失効)<br />
* [http://johnvey.com/features/deliciousdirector/ del.icio.us の ajax ベースのインターフェイス]<br />
* [http://en.wikipedia.org/wiki/Social_bookmarking ウィキペディアでのソーシャルブックマークの定義]([http://ja.wikipedia.org/wiki/ソーシャルブックマーク 日本語])<br />
<br />
=== 関連作業 ===<br />
* [[hreview-ja | hReview]]<br />
<br />
== 現在の進行状況 ==<br />
この仕様は最近バージョン RC1 のように安定し始めましたが、いまだ現在進行中です。望まれれば、ブックマークエントリーをできるだけ軽量にしてもっと広くアクセスできるようにするという目標のためには、リリース候補(release candidate)のバージョンを重ねる準備があります。前のバージョンからの変更は、開発者がこの狙いに限定して実装した経験を動機として行いました。以降の変更もおおむね実装上の関心を動機として行われるでしょう。このマイクロフォーマットの更なる可能性については下の「今後の方向性」をご覧ください。<br />
<br />
=== xFolk 0.4 からの変更点 ===<br />
もっと他のマイクロフォーマットの使用法と実装中に出てきたいくらかの要請に沿うため、class 属性の <code>extended</code> という値は廃止予定となり、<code>description</code> が推奨されています。また、実装上の使用例で見受けられたため、複数の要素で <code>extended</code> class を使ってもよいという変更もされました。<br />
<br />
=== <div id=".E4.B8.BB.E3.81.AA.E6.96.B9.E5.90.91.E6.80.A7">今後の方向性</div> ===<br />
xFolk の拡張はいくつか考えられます。そういった拡張には、たいていの場合 xFolk を他のマイクロフォーマットと組み合わせるのが一番の方法です。たとえば、ブックマークしたアイテムに関する自分の評価を表したいと思うかもしれません。これは xFolk と一緒に [[vote-links-ja | Vote Links]] か [[hreview-ja | hReview]] を使うことでできます。<br />
<br />
また、全てのブックマークをタグ付きで提供するなど、xFolk を拡張して整合データに様々なソーシャルブックマークサービスの API を付けて提供することを考えるかもしれません。現在、どの標準でもこういった API の仕様はあまりに流動的です。API とそれが提供する機能は、ソーシャルブックマークサービスとメタサービスが自分を差別化する一つの方法を表しています。<br />
<br />
"xFolk definition" という関係の深いフォーマットが開発中です。xFolk definition ではソーシャルブックマークで使われるタグを厳密に定義する手段を提供することになるでしょう。<br />
<br />
=== ブレインストーミング ===<br />
* [[xfolk-brainstorming|xFolk brainstorming]]<br />
<br />
== 議論 ==<br />
<br />
=== Q&A ===<br />
* xFolk に関する疑問がある時には、[[xfolk-faq|xFolk FAQ]] をチェックしてください。もし答えが見つからなければ、質問してください!<br />
<br />
=== 問題 ===<br />
* この仕様の問題提起は、別ページの [[xfolk-issues|xFolk issues]] の文書に追加してください。<br />
<br />
== 関連ページ ==<br />
{{template:xfolk-related-pages}}<br />
* [[xfolk-profile-ja|xFolk メタデータプロファイル]](日本語)<br />
* [[xfolk-issues-ja|xFolk の問題]](日本語)<br />
<br />
[[Category:xFolk]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xfolk-fr&diff=70199xfolk-fr2020-07-18T16:35:27Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:xFolk RC1}}<br />
{{DraftSpecification}}<br />
<br />
'''xFolk''' (de "xFolksonomie) 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 signets basé sur le web. xFolk peut être embarqué dans HTML ou XHTML, Atom, RSS et le XML arbitraire. C'est l'un des nombreux [[microformats-fr|microformats]] standards ouverts.<br />
<br />
== Spécification Brouillon ==<br />
=== Editeur/Auteur ===<br />
[http://thecommunityengine.com/ Bud Gibson], ([http://thecommunityengine.com The Community Engine])<br />
<br />
(traduction [[Christophe Ducamp]])<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2005-fr}}<br />
<br />
=== Brevets ===<br />
{{MicroFormatPatentStatement-fr}}<br />
<br />
=== Inspiration et Reconnaissances ===<br />
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. <br />
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.<br />
<br />
== Introduction ==<br />
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, <br />
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]. <br />
<br />
Le manque d'un standard ouvert et interopérable de données est une problématique majeure pour 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 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.<br />
<br />
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 en 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.<br />
<br />
== Principes de Design XHTML Sémantique ==<br />
{{semantic-xhtml-design-principles-fr}}<br />
<br />
== Format ==<br />
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 : <br />
<br />
* Un lien bookmarké ou tagué.<br />
* Un titre pour l'entrée.<br />
* Les tags pour le lien.<br />
* Une description étendue ou un résumé du lien.<br />
<br />
Comme démontré dans les premières itérations du standard xFolk, ce schéma général peut être traduit en balisage par : <br />
# créer un élément conteneur pour chaque entrée de la classe <code>xfolkentry</code>, <br />
# utiliser un élément <a> pour le lien bookmarké ou tagué de la classe <code>taggedlink</code>, <br />
# utiliser l'attribut title pour l'élément lien tagué <a>, s'il existe, comme l'entry title, autrement utiliser la valeur de l'élément,<br />
# utiliser [[rel-tag-fr|RelTag]] pour les tags, et <br />
# utiliser un élément conteneur de classe <code>description</code>, tel que &lt;p>, pour toute autre description étendue ou résumé.<br />
<br />
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.<br />
<br />
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]]).<br />
<br />
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 HTML soit bien formé mais pas nécessairement <br />
valide. Par conséquent, bien que non désirable, il est possible d'utiliser xFolk dans un document HTML qui ne valide pas.<br />
<br />
=== XMDP Profile ===<br />
<br />
Voir le [[xfolk-profile-fr|xFolk profile]] pour le profil [http://gmpg.org/xmdp XMDP] de xFolk.<br />
<br />
== Exemple ==<br />
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.<br />
<pre>&lt;div class="post"&gt; <!--changera--><br />
&lt;div&gt;<br />
&lt;a class="delLink" href="http://www.sifry.com/alerts/archives/000306.html"&gt; <!--changera--><br />
Sifry's Alerts: Technorati launches Related Tags<br />
&lt;/a&gt; <br />
&lt;/div&gt;<br />
&lt;div class="extended"&gt; <!--will change--><br />
Ever wanted to see what posts are related to other posts, what tags <br />
are related to others? Now you can! Just check under the Tag <br />
description on most tag pages, like this one, or this one, and you'll<br />
see the patterns. Can you smell the emergence?<br />
&lt;/div&gt;<br />
&lt;div class="meta"&gt;<br />
to<br />
&lt;a class="delNav" href="/fpgibson/folksonomy"&gt;folksonomy&lt;/a&gt; <!--changera--><br />
&lt;a class="delNav" href="/fpgibson/technorati"&gt;technorati&lt;/a&gt; <!--changera--><br />
... &lt;a class="delNav" href="/url/cbcabf7de070fdb46598ee679367be49"&gt;<br />
and 1 other person<br />
&lt;/a&gt;<br />
... on 2005-04-09<br />
&lt;/div&gt;<br />
&lt;/div&gt;</pre><br />
<br />
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<br />
<pre><nowiki><br />
&lt;div class="xfolkentry"&gt; <!-- changé --><br />
&lt;div&gt;<br />
&lt;a class="taggedlink" href="http://www.sifry.com/alerts/archives/000306.html"&gt; <!-- changé --><br />
Sifry's Alerts: Technorati launches Related Tags<br />
&lt;/a&gt; <br />
&lt;/div&gt;<br />
&lt;div class="description"&gt; <!-- changed --><br />
Ever wanted to see what posts are related to other posts, what tags <br />
are related to others? Now you can! Just check under the Tag <br />
description on most tag pages, like this one, or this one, and you'll<br />
see the patterns. Can you smell the emergence?<br />
&lt;/div&gt;<br />
&lt;div class="meta"&gt;<br />
to<br />
&lt;a rel="tag" href="/fpgibson/folksonomy"&gt;folksonomy&lt;/a&gt; <!-- changé --><br />
&lt;a rel="tag" href="/fpgibson/technorati"&gt;technorati&lt;/a&gt; <!-- changé --><br />
... &lt;a class="delNav" href="/url/cbcabf7de070fdb46598ee679367be49"&gt;<br />
and 1 other person<br />
&lt;/a&gt;<br />
... on 2005-04-09<br />
&lt;/div&gt;<br />
&lt;/div&gt;<br />
</nowiki></pre><br />
<br />
<br />
<br />
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.<br />
<br />
Un autre exemple simple (utilisant le marquage listes) :<br />
<source lang=html4strict><br />
<ul><!--xfolk traite de *collections* de bookmarks--><br />
<li><br />
<ul class="xfolkentry"> <br />
<li><a class="taggedlink" href="http://microformats.org/wiki/Main_Page-fr">microformats wiki</a></li><br />
<li class="description">L'endroit principal pour comprendre les microformats et jouer avec...</li><br />
<li class="description">Wiki piloté par une communauté</li><br />
<li class="meta"><br />
Tags :<br />
<a rel="tag" href="http://del.icio.us/tag/microformats">microformats</a><br />
<a rel="tag" href="http://del.icio.us/tag/websocial">websocial</a><br />
<a rel="tag" href="http://del.icio.us/tag/semantics">semantics</a><br />
</li><br />
</ul><br />
</li><br />
<br />
<li><br />
<!--Une autre xfolkentry comme ci-dessus, et ainsi de suite ...--><br />
</li><br />
<br />
</ul><br />
</source><br />
== Beaucoup plus d'exemples ==<br />
<br />
Nous avons de nombreux exemples pour aider les développeurs à incorporer xFolk dans leurs sites.<br />
<br />
=== Dans la jungle ===<br />
<br />
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.<br />
<br />
* [http://greenvoice.com Greenvoice] a une liste de liens environnementaux générée par les utilisateurs, qui est marquée avec xFolk.<br />
* [http://www.idoneos.com Idoneos.com], une collection conceptuellement en réseau de pages d'informations (essentiellement en espagnol), tague les signets avec xFolk.<br />
* [http://ashaszin.lautre.net/ Ashaszin] - Petit blog tournant sous [http://spip.net SPIP] : les liens del.icio.us et fils web sont tagués avec xFolk .<br />
* [http://www.rolandinsh.lv/blog/ Rolands Umbrovskis - blog] tous les billets sont marqués avec xFolk.<br />
* [http://www.bbc.co.uk/worldservice/bangladeshboat BBC World Service Bangladesh River Journey] et un mashup de réseau social, il utilise xFolk pour les entrées de signets hAtom. voir la [http://dharmafly.com/blog/bangladeshboat discussision blog Dharmafly].<br />
* [http://waferbaby.com/hussy waferbaby's Hussy] publie actuellement les liens en utilisant xFolk.<br />
* [http://unalog.com unalog] publie actuellement tous les liens partagés (y compris les résultats de recherche) en utilisant xFolk.<br />
* [http://smarking.com/ Smarking] publie actuellement tous les liens partagés (y compris les résultats de recherche) en utilisant xFolk.<br />
* [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]]).<br />
* [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]]).<br />
* [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].<br />
* [http://groovymother.com/links/ Groovy Links] est un blog de liens qui est balisé avec xFolk.<br />
* [http://tommorris.org/blog/ Tom Morris] - les liens quotidiens del.icio.us sont marqués avec xFolk, [[hcard-fr|hCard]] et [[vote-links-fr|vote-links]].<br />
<br />
=== Services de signets sociaux supplémentaires ===<br />
Cet exemple illustre comment xFolk peut être appliqué à un service additionnel : <br />
<br />
* [[xfolk-scuttle-fr| scuttle]]<br />
<br />
=== Blogs de liens ===<br />
<br />
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.<br />
<br />
* [[xfolk-kottke | kottke]]<br />
* [[xfolk-pollas | pollas]]<br />
* [[xfolk-jacobian | jacobian]]<br />
* [[xfolk-julian-bez | julian-bez]]<br />
<br />
=== Spam === <br />
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 : <br />
* phontron.info<br />
<br />
== Implémentations ==<br />
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.<br />
* [http://bildu.net Bildu] un service de bookmarking social en Basque qui supporte xFolk (et aussi rel-tag).<br />
* [http://bookmarks.excite.co.uk/ Excite Bookmarks] un service de bookmarking social qui supporte xFolk et rel-tag.<br />
* [http://buzka.com Buzka], un service de signet social supporte maintenant xFolk<br />
* [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].<br />
* [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.<br />
* [http://claimid.com claimID] a implémenté xFolk pour les liens vers les personnes.<br />
* [http://ma.gnolia.com ma.gnolia] supporte maintenant xFolk.<br />
* [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]].<br />
* [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.<br />
* [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.<br />
* 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.<br />
* [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+.''<br />
* [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]<br />
* [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>).<br />
* [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>).<br />
* [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/])<br />
<br />
== Références ==<br />
=== Références Normatives ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]<br />
* [[rel-tag-fr|rel-tag]]<br />
<br />
=== Références Informatives ===<br />
* [http://thecommunityengine.com/home/archives/xfolk articles about xFolk]<br />
* [http://thecommunityengine.com/home/archives/tags/microformats articles about the business value of microformats]<br />
* [http://gataga.com gataga social bookmark search engine]<br />
* [http://johnvey.com/features/deliciousdirector/ an ajax based interface for del.icio.us]<br />
* [http://en.wikipedia.org/wiki/Social_bookmarking social bookmarking defined at wikipedia]<br />
<br />
=== Travaux similaires ===<br />
* [[hreview-fr| hReview]]<br />
<br />
== Chantier en cours ==<br />
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.<br />
<br />
=== Changements depuis xFolk 0.4 ===<br />
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.<br />
<br />
=== Directions futures ===<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Brainstorming ===<br />
* [[xfolk-brainstorming-fr|xFolk brainstorming]]<br />
<br />
== Discussions ==<br />
<br />
=== Q&R ===<br />
* 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 !<br />
<br />
=== Problématiques ===<br />
* SVP, ajoutez toute problématique avec la spécification au document séparé [[xfolk-issues-fr| xFolk issues]].<br />
<br />
==Pages apparentées== <br />
{{template:xfolk-related-pages-fr}}<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:xFolk]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xfolk&diff=70198xfolk2020-07-18T16:35:25Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:xFolk RC1}}<br />
{{DraftSpecification}}<br />
<br />
'''xFolk''' (from "xFolksomony") is a simple and open format for publishing collections of bookmarks. It better enables services for improving user experience and sharing data in web-based bookmarking software. xFolk may be embedded in HTML or XHTML, Atom, RSS, and arbitrary XML. It is one of several open [[microformats|microformat]] standards.<br />
<br />
__TOC__<br />
<br />
== Draft Specification ==<br />
<br />
=== Editor/Author ===<br />
[http://thecommunityengine.com/ Bud Gibson] ([http://thecommunityengine.com The Community Engine])<br />
<br />
=== Copyright ===<br />
{{MicroFormatCopyrightStatement2005}}<br />
<br />
=== Patents ===<br />
{{MicroFormatPatentStatement}}<br />
<br />
=== Inspiration and Acknowledgments ===<br />
Thanks to: [http://www.cnbc.cmu.edu/~plaut/ David Plaut] who introduced me to the idea that items may partially belong to many categories at once. More recently, thanks to: [http://tantek.com/ Tantek Çelik], [http://epeus.blogspot.com/ Kevin Marks], [http://steve.osdir.com/ Steve Mallet], [http://hybernaut.com/ Brian DelVecchio], and [http://blogmarks.net François Hodierne] who have contributed to the development of xFolk with thoughtful critiques and implementations.<br />
<br />
== Introduction ==<br />
Social bookmarking services let users save and tag bookmarks to share with other users. Over the past year, the number of these services has mushroomed to [http://en.wikipedia.org/wiki/Social_bookmarking over 20], with popular examples including: [http://del.icio.us del.icio.us], [http://furl.net furl], [http://de.lirio.us de.lirio.us], [http://jots.com jots], and [http://blogmarks.net blogmarks]. <br />
<br />
Lack of an open, interoperable data standard is a major issue in using social bookmarking services. An open standard would make it possible to easily collect social bookmark data and remix it to invent new services along the lines of [http://gataga.com gataga]'s experimental bookmark search engine. An open standard would also make it possible to write javascripts that work across services [http://johnvey.com/features/deliciousdirector/ as some currently do for del.icio.us], enabling across-the-board improvements in user experience.<br />
<br />
xFolk is an open social bookmarking standard that aims to achieve both benefits. Social bookmarking services that adopt xFolk will continue to differentiate themselves with data services. But, the data itself will be easy to manipulate by third party scripts and easy to share. As a result, bookmarking services will be able to offer a wider array of options to their users at low cost and focus on what truly differentiates them. Individuals or groups operating standalone bookmark repositories will have access to a wider array of functionality than they can produce on their own.<br />
<br />
== Semantic XHTML Design Principles ==<br />
{{semantic-xhtml-design-principles}}<br />
<br />
== Format ==<br />
Extensive analysis of social bookmarking services and linkblogs, reported on [http://thecommunityengine.com/home/archives/xfolk elsewhere], reveals that the data published by both bookmarking services and '''many''' different linkblogs are described by the following implied schema:<br />
<br />
* A bookmarked or tagged link.<br />
* A title for the entry.<br />
* Tags for the link.<br />
* An extended description or summary of the link.<br />
<br />
As demonstrated in early iterations of the xFolk standard, this general schema can be translated into markup by:<br />
<br />
# creating a container element for each entry of class <code>xfolkentry</code>, <br />
# using an <a> element for the bookmarked or tagged link of class <code>taggedlink</code>, <br />
# using title attribute for the tagged link <a> element, if it exists, as the entry title, otherwise using the element value,<br />
# using [[rel-tag]] for the tags, and<br />
# using a container element of class <code>description</code>, such as &lt;p>, for any extended description or summary.<br />
<br />
A given xFolk entry will always contain a tagged link including a title with all other elements optional. Entries may have more than one tag as well as more than one element of class <code>description</code>. Multiple elements of class <code>description</code> are ordered by default document order. Semantic elements within xFolk entries may be nested at arbitray depths.<br />
<br />
Many social bookmarking systems exist, each with its own markup conventions. Further, many people are already publishing personal link blogs. xFolk is designed with ease of adapting to these current practices as a primary goal. Therefore, few assumptions are made as to the exact kinds of elements used for an xFolk entry. Rather, the work of defining semantics is left entirely to the class and rel (in the case of [[rel-tag]]) attribute values.<br />
<br />
It is expected that developers will use [http://www.w3.org/TR/xpath XPath] or equivalent syntax in accessing xFolk entry elements. a requirement for XPath is that the HTML document be well-formed but not necessarily valid. Thus, while not optimal, it is possible to serviceably use xFolk in an HTML document that does not validate.<br />
<br />
=== XMDP Profile ===<br />
<br />
See the [[xfolk-profile|xFolk profile]] for the [http://gmpg.org/xmdp XMDP] profile of xFolk.<br />
<br />
== Example ==<br />
Here is a sample bookmark as displayed in [http://del.icio.us del.icio.us]'s standard markup. Lines where the value of elements' class attributes must change to conform to xFolk are marked with a comment at the end.<br />
<pre>&lt;div class="post"&gt; <!--will change--><br />
&lt;div&gt;<br />
&lt;a class="delLink" href="http://www.sifry.com/alerts/archives/000306.html"&gt; <!--will change--><br />
Sifry's Alerts: Technorati launches Related Tags<br />
&lt;/a&gt; <br />
&lt;/div&gt;<br />
&lt;div class="extended"&gt; <!--will change--><br />
Ever wanted to see what posts are related to other posts, what tags <br />
are related to others? Now you can! Just check under the Tag <br />
description on most tag pages, like this one, or this one, and you'll<br />
see the patterns. Can you smell the emergence?<br />
&lt;/div&gt;<br />
&lt;div class="meta"&gt;<br />
to<br />
&lt;a class="delNav" href="/fpgibson/folksonomy"&gt;folksonomy&lt;/a&gt; <!--will change--><br />
&lt;a class="delNav" href="/fpgibson/technorati"&gt;technorati&lt;/a&gt; <!--will change--><br />
... &lt;a class="delNav" href="/url/cbcabf7de070fdb46598ee679367be49"&gt;<br />
and 1 other person<br />
&lt;/a&gt;<br />
... on 2005-04-09<br />
&lt;/div&gt;<br />
&lt;/div&gt;</pre><br />
<br />
The equivalent in xFolk is as follows. Comments are placed at the end of lines where class attribute changes were required. <br />
<pre><nowiki><br />
&lt;div class="xfolkentry"&gt; <!-- changed --><br />
&lt;div&gt;<br />
&lt;a class="taggedlink" href="http://www.sifry.com/alerts/archives/000306.html"&gt; <!-- changed --><br />
Sifry's Alerts: Technorati launches Related Tags<br />
&lt;/a&gt; <br />
&lt;/div&gt;<br />
&lt;div class="description"&gt; <!-- changed --><br />
Ever wanted to see what posts are related to other posts, what tags <br />
are related to others? Now you can! Just check under the Tag <br />
description on most tag pages, like this one, or this one, and you'll<br />
see the patterns. Can you smell the emergence?<br />
&lt;/div&gt;<br />
&lt;div class="meta"&gt;<br />
to<br />
&lt;a rel="tag" href="/fpgibson/folksonomy"&gt;folksonomy&lt;/a&gt; <!-- changed --><br />
&lt;a rel="tag" href="/fpgibson/technorati"&gt;technorati&lt;/a&gt; <!-- changed --><br />
... &lt;a class="delNav" href="/url/cbcabf7de070fdb46598ee679367be49"&gt;<br />
and 1 other person<br />
&lt;/a&gt;<br />
... on 2005-04-09<br />
&lt;/div&gt;<br />
&lt;/div&gt;<br />
</nowiki></pre><br />
<br />
Converting markup to be conformant with xFolk is almost always this easy. The advantage of xFolk is that it provides one set of class attributes that can be reused across all services and link blogs, almost always with no loss of granularity. The next section presents several more examples to illustrate this point.<br />
<br />
Another simple example (using lists markup) :<br />
<pre><br />
<nowiki><br />
<ul><!--xfolk is about *collections* of bookmarks--><br />
<li><br />
<ul class="xfolkentry"> <br />
<li><a class="taggedlink" href="http://microformats.org/wiki/Main_Page">microformats wiki</a></li><br />
<li class="description">The main place for understanding microformats and playing with...</li><br />
<li class="description">Community driven wiki</li><br />
<li class="meta"><br />
Tags :<br />
<a rel="tag" href="http://del.icio.us/tag/microformats">microformats</a><br />
<a rel="tag" href="http://del.icio.us/tag/websocial">websocial</a><br />
<a rel="tag" href="http://del.icio.us/tag/semantics">semantics</a><br />
</li><br />
</ul><br />
</li><br />
<br />
<li><br />
<!--Another xfolkentry as above, and so on...--><br />
</li><br />
<br />
</ul><br />
</nowiki><br />
</pre><br />
<br />
== Many more examples ==<br />
<br />
We have numerous examples to help developers incorporate xFolk into their sites.<br />
<br />
=== In the wild ===<br />
<br />
These are real live examples of functioning systems that publish bookmarks in xFolk. These are a great place to start for anyone looking for examples "in the wild" to try parsing, indexing, organizing etc. If you publish using xFolk, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.<br />
<br />
* [http://greenvoice.com Greenvoice] has a user-generated environmental news link list, which is marked up with xFolk.<br />
* [http://www.idoneos.com Idoneos.com] , a conceptually networked collection of information pages (mostly spanish), is tagging bookmarks with xFolk.<br />
* [http://ashaszin.lautre.net/ Ashaszin] - Small blog running with [http://spip.net SPIP] : del.icio.us links and web feeds tagged with xFolk .<br />
* [http://www.rolandinsh.lv/blog/ Rolands Umbrovskis - blog] all blog posts are marked up with xFolk.<br />
* [http://www.bbc.co.uk/worldservice/bangladeshboat BBC World Service Bangladesh River Journey] a social network mashup, uses basic xFolk for bookmarking hAtom entries. See [http://dharmafly.com/blog/bangladeshboat Dharmafly blog discussion].<br />
* [http://waferbaby.com/hussy waferbaby's Hussy] currently publishes links using xFolk.<br />
* [http://smarking.com/ Smarking] currently publishes all shared links (including search results) using xFolk.<br />
* [http://unalog.com unalog] currently publishes all shared links (including search results) using xFolk.<br />
* [http://de.lirio.us de.lirio.us] currently publishes its bookmarks using xFolk (with the deprecated class attribute <code>extended</code> in place of <code>description</code>, see [[xfolk-profile | the XMDP]]).<br />
* [http://dev.blogmarks.net/wiki/BlogSync blogmarks] currently exports bookmarks to blogs in xFolk (scroll down to the export example on the page; the deprecated class attribute <code>extended</code> is used in place of <code>description</code>, see [[xfolk-profile | the XMDP]]).<br />
* [http://thecommunityengine.com The Community Engine] uses xFolk (with the deprecated class attribute <code>extended</code> in place of <code>description</code>, see [[xfolk-profile | the XMDP]]) for its [http://thecommunityengine.com/home main entries] and for its [http://thecommunityengine.com/webcites republished bookmarks].<br />
* [http://groovymother.com/links/ Groovy Links] is a link blog which is marked up with xFolk.<br />
* [http://tommorris.org/blog/ Tom Morris] - daily del.icio.us links are marked up with xFolk, [[hCard]] and [[vote-links]].<br />
<br />
=== Additional social bookmarking services ===<br />
<br />
This example illustrates how xFolk may be applied to one additional service:<br />
<br />
* [[xfolk-scuttle | scuttle]]<br />
<br />
=== Link blogs ===<br />
<br />
Social bookmarking services are only the most recent examples of people publishing links. Link blogs have been around almost since the beginning of blogging. They represent somewhat more of a challenge for xFolk because their markup tends to be less semantic from the outset. The following examples illustrate some particular challenges and how they can be overcome.<br />
<br />
* [[xfolk-kottke | kottke]]<br />
* [[xfolk-pollas | pollas]]<br />
* [[xfolk-jacobian | jacobian]]<br />
* [[xfolk-julian-bez | julian-bez]]<br />
<br />
=== Spam ===<br />
Some spammers are adding xFolk tags to their link farms. (It's probably a bad idea to actually link to these sites.) For example,<br />
* phontron.info<br />
<br />
== Implementations ==<br />
<br />
The following implementations have been developed which generate or use xFolk. If you have an xFolk implementation, feel free to add it to the top of this list. Once the list grows too big, we'll make a separate wiki page.<br />
<br />
* [http://sourceforge.net/projects/semanticscuttle SemanticScuttle], your own social bookmarking software, supports xfolk natively<br />
* [http://buzka.com Buzka], a social bookmarking service, now supports xFolk<br />
* [http://blip.tv Blip.tv], a video hosting site, now [http://blog.blip.tv/blog/2006/08/19/blip-supports-xfolk/ supports xFolk].<br />
* [http://www.s9y.org/ Serendipity], a PHP-powered, flexible Blogging/CMS application, now has a [http://www.numblog.de/archives/241-Social-Bookmarks-Plugin-for-Serendipity.html social bookmarks plugin] that supports xFolk.<br />
* [http://claimid.com claimID] has implemented xFolk for people's links.<br />
* [http://ma.gnolia.com ma.gnolia] now supports xFolk.<br />
* [http://smarking.com/ Smarking.com] (a social bookmarking service) marks up their tagged links with xFolk! Hat tip: [http://3spots.blogspot.com/2006/05/social-bookmarking-smarking.html 3spots: Social + bookMARKING = Smarking] which itself is an [[hreview|hReview]].<br />
* [http://blog.codeeg.com/2006/03/20/flock-tails-flocktails/ Flocktails] - port of Tails extension for Flock 0.5.12 that looks for hCards, hCalendar, xFolk and hReview and tosses them into a handy topbar<br />
* [http://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.<br />
* Bud Gibson and Mike Migurski [http://thecommunityengine.com/home/archives/2005/09/vegomatic_an_al.html have written] [http://thecommunityengine.com/veg-o-matic veg-o-matic], an xFolk reblogging tool and service.<br />
* [http://inside.glnetworks.de/ Martin Rehfeld] has updated the work of [http://blogmatrix.blogmatrix.com/ David Janes] and produced a [[Greasemonkey]] [http://inside.glnetworks.de/2006/06/05/microformats-have-arrived-in-firefox-15-greasemonkey-06/ script] that finds many microformat elements, including xFolk and [http://blog.davidjanes.com/mtarchives/2005_08.html#003379 provides a popup menu of actions]. ''This will work with FireFox 1.5+/GreaseMonkey 0.6.4+ now.''<br />
* [http://www.midgard-project.org/midcom-permalink-6416db7e1f0e297b4cf3dcc285702a8d net.nemein.bookmarks], the bookmark manager in [http://www.midgard-project.org/ Midgard CMS] uses xFolk as the native output format, with added <code>abbr class=posted</code> for publication date and <code>abbr class=poster</code> for user who added the bookmark. See [http://bergie.iki.fi/links/ example]<br />
* [http://de.lirio.us de.lirio.us] currently publishes its bookmarks using xFolk 0.4 (the class attribute <code>extended</code> is used in place of description).<br />
* [http://dev.blogmarks.net/wiki/BlogSync blogmarks] currently exports bookmarks to blogs in xFolk 0.4 (scroll down to the export example on the page; the class attribute <code>extended</code> is used in place of <code>description</code>).<br />
* [http://pokkari.com/microformat/javadoc/ Sivitols] is a Java library for microformats. Currently only the xFolk RC1 standard is implemented, but additional microformat support is planned. (adapted from [http://blog.blip.tv/blog/microformats/])<br />
* [http://bildu.net Bildu] a social bookmarking service in Basque that supports xFolk (an also rel-tag).<br />
* [http://bookmarks.excite.co.uk/ Excite Bookmarks] a social bookmarking service that supports xFolk and rel-tag.<br />
<br />
== References ==<br />
=== Normative References ===<br />
* [http://www.w3.org/TR/2002/REC-xhtml1-20020801/ XHTML 1.0 SE]<br />
* [[rel-tag]]<br />
<br />
=== Informative References ===<br />
* [http://thecommunityengine.com/home/archives/xfolk articles about xFolk]<br />
* [http://thecommunityengine.com/home/archives/tags/microformats articles about the business value of microformats]<br />
* [http://gataga.com gataga social bookmark search engine]<br />
* [http://johnvey.com/features/deliciousdirector/ an ajax based interface for del.icio.us]<br />
* [http://en.wikipedia.org/wiki/Social_bookmarking social bookmarking defined at wikipedia]<br />
<br />
=== Similar Work ===<br />
* [[hreview | hReview]]<br />
<br />
== Work in progress ==<br />
Although this specification has recently begun to stabilize as indicated by the version RC1, it is still a work in progress. If warranted, I am prepared to go through multiple release candidates to achieve the narrow purpose of making bookmark entries more genrally accessible with as with as light weight a format as possible. All changes since the last iteration have been motivated by the implementation experience of developers attempting to achieve this narrow aim. Further changes will also most likely be motivated by implementation concerns. See "future directions" below for additional microformat possibilities.<br />
<br />
=== Changes since xFolk 0.4 ===<br />
The class attribute value <code>extended</code> was deprecated in favor <code>description</code> to better conform with other microformat usage and some requests during implementation. The other change has been to allow use of multiple elements of class <code>extended</code> based on some use cases discovered in implementation.<br />
<br />
=== Future directions ===<br />
There are several extensions one might imagine for xFolk. Frequently, these extensions are best achieved by combining xFolk with another microformat. For instance, one might want to indicate his or her evaluation of the bookmarked item. This might be achieved by using [[vote-links | Vote Links]] or [[hreview | hReview]] with xFolk.<br />
<br />
One can also imagine extending xFolk to provide data conformant with various social bookmarking service APIs, for instance to provide all bookmarks by tag. These APIs are currently too fluid for specification in any kind of standard. The APIs and the functionality they provide represent one way social bookmarking services and meta services can differentiate themselves.<br />
<br />
A companion format called "xFolk definition" is under development. xFolk definition will provide a means of explicitly defining the tags used in social bookmarks.<br />
<br />
=== Brainstorming ===<br />
* [[xfolk-brainstorming|xFolk brainstorming]]<br />
<br />
== Discussions ==<br />
<br />
=== Q&A ===<br />
* If you have any questions about xFolk, check the [[xfolk-faq|xFolk FAQ]], and if you don't find answers, add your questions!<br />
<br />
=== Issues ===<br />
* Please add any issues with the specification to the separate [[xfolk-issues|xFolk issues]] document.<br />
<br />
==Related pages==<br />
{{template:xfolk-related-pages}}<br />
<br />
[[Category:Draft Specifications]]<br />
[[Category:xFolk]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xfn-to-foaf&diff=70197xfn-to-foaf2020-07-18T16:35:25Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:XFN → FOAF}}<br />
{{TOC-right}}<br />
by [[User:TobyInk|Toby Inkster]]<br />
<br />
(Contributors: Gabriele Renzi)<br />
<br />
<p>&nbsp;</p><br />
<br />
A number of people have expressed an interest in extracting RDF-like data from [[xfn|XFN]] and [[hcard|hCard]]. The problem is that while XFN is interpreted as representing a relationship between two people, it actually encodes a relationship between two URIs. <br />
<br />
This page describes a technique for figuring out which people these URIs represent. It is not an attempt to describe a new specification or standard, but rather, a set of best practices. Two algorithms are described: a "high-bandwidth" version which requires web crawling, and a "low-bandwidth" version which uses only the information found on the initial page.<br />
<br />
For most of the examples on this page, the following XFN link will be used:<br />
<br />
<pre><nowiki><a rel="friend met" href="http://bob.example.net">Bob Smith</a></nowiki></pre><br />
<br />
which has been found on Alice Jones' web page at <nowiki>http://alice.example.net</nowiki>.<br />
<br />
== Determining the subject ==<br />
<br />
# Find the [[representative-hcard|representative hCard]] for the current page.<br />
# In the high-bandwidth situation, parsers {{may}} crawl <code>rel=me</code> links in order to find a "better" representative hCard, where the meaning of "better" is to be defined by the parser itself.<br />
#* (Parsers {{should}} impose a depth limit for crawling.)<br />
# If no hCard for the subject has been found, the subject is a person represented by the following RDF triples:<br />
<pre><nowiki>_:bnode01 a foaf:Person;<br />
foaf:page &lt;http://alice.example.net&gt;.</nowiki></pre><br />
<br />
A parser which understands RDFa or other semantics may use additional techniques to determine the subject of the link, but those are beyond the scope of the Microformats wiki.<br />
<br />
== Determining the predicate ==<br />
<br />
This is the easiest step.<br />
<br />
For <code>rel="me"</code> the predicate is <code>foaf:page</code>.<br />
<br />
For other relationships, the local name of the predicate is the same as the rel value, and the namespace URI is defined as <code><nowiki>http://vocab.sindice.com/xfn#</nowiki></code>. Many non-me XFN values can be considered to be refinements of foaf:knows. As an example, the fully qualified URIs for the predicates associated with <code><nowiki>rel="met friend"</nowiki></code> are:<br />
<br />
* <code><nowiki>http://vocab.sindice.com/xfn#met</nowiki></code><br />
* <code><nowiki>http://vocab.sindice.com/xfn#friend</nowiki></code><br />
* <code><nowiki>http://xmlns.com/foaf/0.1/knows</nowiki></code><br />
<br />
'''Which XFN values are refinements of <code>foaf:knows</code>?''' This is a matter of debate. Although normally, say, a parent and child will have a close relationship, there are instances where they may have never met, and not know each other at all. The current list of XFN values which I treat as refinements of <code>foaf:knows</code> are: acquaintance, friend, met, co-resident, spouse, crush, date and sweetheart. Depending upon your application, you may wish to narrow or broaden your scope.<br />
<br />
== Determining the object ==<br />
<br />
# If the link element is a descendant of an element with <code>class="vcard"</code> which is not the representative hCard for the page, then this hCard is taken to represent the person who is the object of the relationship.<br />
<!-- # If a non-representative hCard exists on the page with a UID property which is identical to the target of the link element, then this hCard is taken to represent the object of the relationship. --><br />
# In the high-bandwidth situation, parsers {{may}} follow the link target to look for a representative hCard for the object.<br />
#* (Parsers {{may}} then further follow rel="me" links from <nowiki>http://bob.example.net</nowiki> in order to find a "better" representative hCard for Bob.)<br />
# If no hCard representing the object of the relationship has been found, then the object is taken to be a <code>foaf:Person</code> with a <code>foaf:name</code> corresponding to the link text and, depending on the kind of link provided in the <code>href</code> attribute, a <code>foaf:mbox</code> (for "mailto:" links), <code>foaf:mbox_sha1sum</code> (for "urn:sha1:" URLs), <code>foaf:img</code> (image links, determined by <code>type</code> attribute or HTTP headers, not by file name) or <code>foaf:page</code> (all other links). Our example would generate the following triples: <br />
<br />
<pre><nowiki>_:bnode02 a foaf:Person;<br />
foaf:page &lt;http://bob.example.net&gt;;<br />
foaf:name "Bob Smith".</nowiki></pre><br />
<br />
A parser which understands RDFa or other semantics may use additional techniques to determine the object of the link, but those are beyond the scope of the Microformats wiki.<br />
<br />
'''Is the link text really a person's name?''' sometimes it will be, sometimes it won't. If the link is part of an hCard which has used <code><nowiki><a class="fn url" ...></nowiki></code>, then it should be safe to suppose that it is a name, but at other times this is more of a risk. Often the link text will be a nickname. This is OK, as the definition of the <code>foaf:name</code> term is sufficiently broad to cover these cases. In other cases, it might not be a name at all. Depending on your application's needs, you may want to consider using <code>rdfs:label</code> instead of <code>foaf:name</code> or simply ignoring the link text completely.<br />
<br />
== Example ==<br />
<br />
The following example is assumed to have been found at <nowiki>http://alice.example.net</nowiki>. For simplicity's sake, we assume the low-bandwidth situation.<br />
<br />
<pre><nowiki><br />
<html lang="en"><br />
<title>Alice Jones</title><br />
<br />
<div class="vcard"><br />
<h1 class="fn">Alice Jones</h1><br />
<p class="adr"><br />
<span class="locality">Sydney</span>, <br />
<span class="country-name">Australia</span>.<br />
</p><br />
<p><br />
<a href="http://alice.example.com/blog/" rel="me" class="url"><br />
Alice's Blog<br />
</a><br />
</p><br />
</div><br />
<br />
<h2>Friends &amp;amp; Contacts</h2><br />
<br />
<ul><br />
<br />
<li class="vcard"><br />
<a class="fn url" href="http://bob.example.net" rel="friend met"><br />
Bob Smith<br />
</a><br />
</li><br />
<br />
<li><br />
<a href="http://carol.example.net" rel="co-worker met"><br />
Carol Brown<br />
</a><br />
</li><br />
<br />
<li><br />
<a href="http://dave.example.net" rel="friend neighbor met"><br />
Dave Wong<br />
</a><br />
</li><br />
<br />
<li><br />
<a href="http://eve.example.net" rel="adversary met"><br />
Eve Ville<br />
</a><br />
</li><br />
<br />
</ul><br />
<br />
<address class="vcard"><br />
Page maintained by <a href="http://eve.example.net" class="url uid"<br />
>Eve Ville</a>. Contact <a class="email" href="mailto:eve@example.net"<br />
>eve@example.net</a> for corrections. (I know I'm not the most trustworthy<br />
of sources.)<br />
</address><br />
<br />
</html><br />
</nowiki></pre><br />
<br />
The subject of all the XFN links on the page is the hCard for Alice Jones at the top of the page. This is determined in [[representative-hcard-parsing|step two of the representative hCard parsing procedure]] because it contains <code>rel="me"</code>.<br />
<br />
The next XFN link is the one labelled "Bob Smith". Because the link is part of an hCard, the person described by the hCard is the object of the link.<br />
<br />
For the next two XFN links, there exist no hCards that represent the objects. We can gather some information about them from the link element itself: their <code>foaf:name</code> and <code>foaf:page</code>. (Note that FOAF defines foaf:name very loosely, so it's OK if the link text is a nickname.)<br />
<br />
Although at first glance the XFN link for Eve Ville looks similar, there is in fact an hCard later on in the page with a UID matching the XFN link target, so using rule #2 for determining the object, we use this hCard as the object of the XFN relationship. Note that "adversary" is not an XFN rel value, so is beyond the scope of this document.<br />
<br />
=== Possible RDF Output ===<br />
<br />
The following is a possible RDF/XML representation of the information in the example above.<br />
<br />
<pre><nowiki><br />
<?xml version="1.0"?><br />
<rdf:RDF xmlns:foaf="http://xmlns.com/foaf/0.1/"<br />
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"<br />
xmlns:xfn="http://vocab.sindice.com/xfn#"<br />
xmlns="http://www.w3.org/2006/vcard/ns#"><br />
<br />
<!-- Alice --><br />
<VCard rdf:nodeID="bnode01"><br />
<br />
<!-- data from Alice's hCard --><br />
<fn>Alice Jones</fn><br />
<adr rdf:parseType="Resource"><br />
<locality>Sydney</locality><br />
<country-name>Australia</country-name><br />
</adr><br />
<url rdf:resource="http://alice.example.com/blog/" /><br />
<br />
<!-- data from Alice's XFN links --><br />
<foaf:page rdf:resource="http://alice.example.com/blog/" /><br />
<foaf:knows rdf:nodeID="bnode02" /><br />
<xfn:met rdf:nodeID="bnode02" /><br />
<xfn:friend rdf:nodeID="bnode02" /><br />
<foaf:knows rdf:nodeID="bnode03" /><br />
<xfn:met rdf:nodeID="bnode03" /><br />
<xfn:co-worker rdf:nodeID="bnode03" /><br />
<foaf:knows rdf:nodeID="bnode04" /><br />
<xfn:met rdf:nodeID="bnode04" /><br />
<xfn:friend rdf:nodeID="bnode04" /><br />
<xfn:neighbor rdf:nodeID="bnode04" /><br />
<foaf:knows rdf:nodeID="bnode05" /><br />
<xfn:met rdf:nodeID="bnode05" /><br />
<br />
</VCard><br />
<br />
<!-- Bob, data from hCard --><br />
<VCard rdf:nodeID="bnode02"><br />
<fn>Bob Smith</fn><br />
<url rdf:resource="http://bob.example.net" /><br />
</VCard><br />
<br />
<!-- Carol, implied data --><br />
<foaf:Person rdf:nodeID="bnode03"><br />
<foaf:name>Carol Brown</foaf:name><br />
<foaf:page rdf:resource="http://carol.example.net" /><br />
</foaf:Person><br />
<br />
<!-- Dave, implied data --><br />
<foaf:Person rdf:nodeID="bnode04"><br />
<foaf:name>Dave Wong</foaf:name><br />
<foaf:page rdf:resource="http://dave.example.net" /><br />
</foaf:Person><br />
<br />
<!-- Eve, data from hCard --><br />
<VCard rdf:nodeID="bnode05"><br />
<fn>Eve Ville</fn><br />
<url rdf:resource="http://eve.example.net" /><br />
<uid>http://eve.example.net"</uid><br />
<email rdf:resource="mailto:eve@example.net" /><br />
</VCard><br />
<br />
</rdf:RDF><br />
</nowiki></pre><br />
<br />
Note that some personal data for contacts is expressed in the FOAF vocabulary, and some information is expressed in vCard/hCard vocabulary. User agents may use OWL or another technique to draw equivalencies between vocabularies, such as taking <code>fn</code> to be equivalent to <code>foaf:name</code>.<br />
<br />
== Organisation hCards and XFN ==<br />
<br />
If either the subject or object hCard represents an organisation (rather than a person), the following relationships are meaningless:<br />
<br />
* acquaintance<br />
* friend<br />
* child<br />
* parent<br />
* sibling<br />
* spouse<br />
* kin<br />
* crush<br />
* date<br />
* sweetheart<br />
<br />
== Reverse Relationships ==<br />
<br />
Explicit reverse relationships may be provided by authors using the <code>rev</code> attribute. These should be interpreted by parsers in exactly the same manner as described above, however subject and object must be swapped.<br />
<br />
The [http://gmpg.org/xfn/11 XFN 1.1 profile] explicitly mentions inverses for some XFN relationships, and lists which relationships are symmetric (i.e. their own inverse). For example, as Alice met Bob, it is implied that Bob met Alice. Parsers may use the information in the profile to make explicit the implicit reverse relationships.<br />
<br />
== Inspiration, References ==<br />
<br />
* [http://microformats.org/discuss/mail/microformats-discuss/2008-March/011760.html Re: XFN is getting smoked by FOAF] — Toby Inkster, 2008-03-11<br />
* [http://microformats.org/discuss/mail/microformats-discuss/2008-March/011772.html Re: XFN + hCard] — Toby Inkster, 2008-03-12<br />
* [http://microformats.org/discuss/mail/microformats-discuss/2008-March/011799.html Re: A (big) problem with XFN: identity of source and target not findable] — Toby Inkster, 2008-03-18<br />
* [http://microformats.org/discuss/mail/microformats-discuss/2008-March/011800.html Re: A (big) problem with XFN: identity of source and target not findable] — David Janes, 2008-03-18<br />
* [http://microformats.org/discuss/mail/microformats-discuss/2008-March/011806.html Re: A (big) problem with XFN: identity of source andtarget not findable] — Toby Inkster, 2008-03-18<br />
* [http://microformats.org/discuss/mail/microformats-discuss/2008-March/011851.html Re: A (big) problem with XFN: identity of source andtarget not findable] — Roger L Costello, 2008-03-20<br />
* [http://microformats.org/discuss/mail/microformats-discuss/2008-April/012010.html Re: Coding mbox_sha1sum in XFN] — Toby Inkster, 2008-04-26<br />
<br />
== Related Pages ==<br />
<br />
* [http://vocab.sindice.com/xfn/guide.html Sindice: Expressing the XFN microformat in RDF] (largely compatible with this page) — Richard Cyganiak, 2008-06-27<br />
<br />
=== XFN ===<br />
<br />
{{xfn-related-pages}}<br />
<br />
=== Microformats to RDF ===<br />
<br />
{{uf-rdf-related-pages}}<br />
<br />
=== Other ===<br />
<br />
* [http://xen.adactio.com/ XHTML Enemies Network] - spoof of XFN. Can be easily implemented using the same algorithm.<br />
** [http://buzzword.org.uk/rdf/xen XHTML Enemies Network in RDF]<br />
* [[xpn|XHTML Professionals Network]] - proposed extension to XFN to deal with corporate relationships. When/if completed, will probably be implementable using the algorithm on this page.</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xfn-implementations-fr&diff=70196xfn-implementations-fr2020-07-18T16:35:24Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>''Cette page a démarré sur [[xfn-implementations-fr]]''<br />
{{DISPLAYTITLE:Implémentations XFN}}<br />
<br />
En plus de la page des [http://gmpg.org/xfn/tools Outils XFN], voici quelques implémentations plus récentes :<br />
<br />
'''Note : nous devrions migrer ici tout ce qui figure sur http://gmpg.org/xfn/tools, (re)vérifier tout, et documenter pour savoir si c'est mis à jour ou obsolète. Peut-être placer une photo de la totalité de la liste (sans les liens) pour une documentation historique d'implémentation. Puis redirigeons gmpg.org/xfn/tools ici.'''<br />
<br />
== nouvelles implémentations ==<br />
Les implémentations suivantes ont été développées et génèrent ou parsent [http://gmpg.org/xfn les liens de relations XFN]. Si vous avez une implémentation XFN, sentez-vous libre de l'ajouter '''en haut''' de cette liste.<br />
<!--<br />
<br />
Placez vos ajouts en *haut* de cette liste<br />
<br />
--><br />
* [http://blog.georgebrock.com/events/open-hack-london-xfn-profile-discovery XFN profile discovery] - Un script Greasemonkey qui suit les liens rel="me" à partir de la page enn cours pour trouver les autres sites et profils d'une personne.<br />
* [http://afrigator.com Afrigator] par [[Stii|Stii Pretorius]] - utilise la data XFN trouvée sur les blogrolls pour trouver des amis sur Afrigator.com (Screen cast - [http://www.vimeo.com/1110175 http://www.vimeo.com/1110175])<br />
* [http://digg.com/ Digg] par [[SteveWilliams|Steve Williams]] (Exemple : [http://digg.com/users/sbwms Profil utilisateur de Steve].)<br />
* [http://donpark.org:3301/ XFN friend finder] par Don Park ([http://twitter.com/donpdonp/statuses/740869022 annonce]).<br />
* [http://www.qmpeople.fr/ qmpeople] - Génère du XFN à partir des propriétés du carnet d'adresses des utilisateurs enregistrés - par exemple http://www.qmpeople.fr/users/laserion<br />
* [http://textcube.org TextCube] L'outil de blogging TextCube version 1.6 (en cours de phase Beta) supportera les blogrolls xfn.<br />
* [http://code.google.com/apis/socialgraph/ Google Social Graph API] utilise la donnée XFN provenant des sites Web publics comme sa principale source de donnée.<br />
<!--<br />
<br />
Ajoutez en *haut* de cette liste<br />
<br />
--><br />
<br />
== flux de mises à jour et pingers==<br />
* [http://updates.elsewhere.im/ SixApart Relationship Update Stream] - lancé le 2007-10-19<br />
<br />
== publication création ==<br />
Les outils suivants, plugins et extensions permettent aux auteurs de créer facilement et publier des liens XFN : <br />
* [http://icite.net/develop/software.html#ll4blojsom LL4blojsom] est le plugin LinkList pour le moteur de blog [http://blojsom.sf.net blojsom]. blojsom, écrit en Java, est l'application open source derrière le Serveur Tiger Weblog qui fait partie du serveur OS X. Le plugin LL4blojsom est utilisé pour créer des blogrolls XFN.<br />
* [http://www.zachinglis.com/projects/xfn-rel-creator/ XFN rel Creator] Ce script remplace n'importe quels liens dans les tags désignés et les remplace par une réprésentation visuelle des liens. Réglé par défaut comme des "abbrevations" mais avec CSS il est facile de les remplacer par des images.<br />
* [http://www.wordpress.org/ WordPress] a un support intégré XFN dans sa fonction Link Manager, qui est utilisée pour générer les blogrolls. Quand on est dans l'interface administrateur, choisissez l'item du menu au niveau le plus haut, puis choisissez Add Link. Le formulaire de lien vous laisse choisir quelles propriétés XFN vous souhaitez pour le lien. Au moment d'afficher les liens sur le site via n'importe quel tags standards de gabarit WordPress, il le formatera automatiquement avec les tags appropriés dans l'attribut rel. (basé sur le [http://gmpg.org/xfn/creator XFN Creator])<br />
* [http://www.communityserver.org/ Community Server] a un support XFN dans sa "blog Link Lists". Il vous permet de sélectionner quel(s) tag(s) XFN utiliser pour chaque lien. <br />
* [http://www.webstandards.org/action/dwtf/microformats/ La suite Dreamweaver Extension] du [http://webstandards.org/ Projet Web Standards] permet la publication de liens XFN dans Dreamweaver 8.<br />
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] est un plugin pour [http://textpattern.com/ Textpattern] qui supporte l'embarquement de XFN et d'autres microformats dans les gabarits et billets de blogs. Ecrit par [http://placenamehere.com/ Chris Casciano].<br />
* [http://www.oddmuse.org/cgi-bin/oddmuse/xfn_Module Le Module OddMuse XFN] permet un marquage wiki dans les wikis OddMuse pour saisir de la donnée concernant les relations xfn.<br />
* [http://blo.gs/ blo.gs] – vous permet d'ajouter de l'information concernant votre relation aux personnes derrière les blogs dans votre liste de favoris. [http://blo.gs/news.php#n56 support XFN 1.1 ajoutée le 2004-08-20].<br />
* [http://www.nvu.com/ Nvu] – éditeur HTML qui intègre la publication de XFN dans son module de dialogue de publciation d'hyperliens.<br />
<br />
=== XFN Creator ===<br />
L'outil [http://gmpg.org/xfn/creator XFN Creator] a été localisé en plusieurs langues (voir les liens [[rel-alternate-fr|rel-aternate]] dans le titre). Des localisations supplémentaires sont fournies en-dessous.<br />
<br />
Si vous êtes un lecteur natif des langues suivantes, révisez SVP les XFN creators suivants et laissez une liste embarquées les évaluant. Une fois qu'un "creator" a été suffissament évalué, il devrait être copié sur gmpg.org (ou de préférence sur http://microformats.org/code/xfn/ et http://microformats.org/code-tools-fr) et avec un lien rel-atlernate corresondant.<br />
<br />
* [http://www.beyondcow.com/creator-ch.html XFN 1.1 生成器] (Chinois), [http://twitter.com/lianxu/status/8961983572 publié le 2010-02-11] par [http://twitter.com/lianxu/status/8961804821 twitter.com/lianxu].<br />
* ...<br />
<br />
== Listes d'amis ==<br />
Bon nombre de services supportent à la fois les listes d'amis et même mieux des listes d'amis XFN + [[hcard-fr|hCard]].<br />
* voir [[hcard-xfn-friends-lists-fr|listes d'amis hCard+XFN]].<br />
<br />
== équivalence identité rel me ==<br />
* Le [http://wordpress.org/extend/plugins/yadis/ plugin YADIS] supporte les liens de délégation OpenID qui sont aussi des liens compatibles XFN rel-me.<br />
* [http://wink.com Wink] supporte rel-me (voir [http://wink.com/beach--profile])<br />
** '''sous-optimal''' : utilise "nofollow me" là où il devrait simplement utiliser "me". L'information de profil saisie par l'utilisateur est la première partie, pas une partie tiers, et de ce fait ne devrait pas être étiquetée avec [[rel-nofollow-fr|rel-nofollow]].<br />
<br />
== validateurs ==<br />
* [http://tools.microformatic.com/help/xhtml/rel-lint/ rel-lint] par [[User:DrewMcLellan|Drew McLellan]] validera l'existence d'attributs XFN.<br />
<br />
== visualiseurs et navigateurs ==<br />
* Exemple de [http://services.alphaworks.ibm.com/manyeyes/view/SNnqRHsOtha6i5-m6iGTH2- visualisation XFN] sur Many Eyes d'IBM<br />
* [http://xfngraph.sourceforge.net XFN Graph] — un outil multi-plateformes basé sur Java qui crée des diagrammes en arbre des relations XFN pour toute URL donnée.<br />
* [http://xfnroll.new-bamboo.co.uk/people/popular XFNRoller] (va devenir lifestalker.com) spider XFN et navigateur concentré sur l'utilisation des blogs pour représenter les individus. Exporte un OPML de fils pour les listes tels que les 10 personnes les plus populaires.<br />
<br />
== recherche ==<br />
* [http://xfnsearch.joshpeek.com/ XFN Search] (semble requérir un login HTTP-authentication)<br />
<br />
== convertisseurs ==<br />
* voir [[xfn-to-foaf-fr|xfn-to-foaf]]<br />
<br />
== semble vieux ou invérifiabme ==<br />
Ce sites semblent trop vieux, et ou peut-être cassés (comme PHP error dump).<br />
* '''[http://tagalag.com Tagalag]''' [http://tagalag.com/tools.html#xfn supporte] un vocabulaire XFN partiel.<br />
<br />
== hors-ligne ==<br />
Les implémentations XFN qui suivent semblent être hors-ligne : <br />
* '''Autoxfn''' – Un module pour Bloxsom qui ajoute les annotations XFN aux liens dans une entrée.<br />
** était sur <nowiki>http://weblog.scifihifi.com/2004/02/08/autoxfn-10/</nowiki> en date du 2004-02-08.<br />
* '''exefen''' – Une interface web qui permet une annotation rapide XFN de tous les liens sur une page. Vous pouvez sauvegarder le résultat et le coller dans votre source HTML.<br />
** était sur <nowiki>http://photomatt.net/tools/exefen/</nowiki> en 2004(?).<br />
== Voir aussi ==<br />
{{xfn-related-pages-fr}}</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xfn-implementations&diff=70195xfn-implementations2020-07-18T16:35:24Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:XFN Implementations }}<br />
<br />
In addition to the [http://gmpg.org/xfn/tools XFN Tools] page, this page contains more more recent implementations.<br />
<br />
'''Note: we should move all of http://gmpg.org/xfn/tools to here, (re)verify each, and document as either up to date, or obsolete. Perhaps snapshot the entire list (without links) for historical implementation documentation. Then let's redirect gmpg.org/xfn/tools to here.'''<br />
<br />
== new implementations ==<br />
The following implementations have been developed which either generate or parse [http://gmpg.org/xfn XFN relationship links]. If you have an XFN implementation, feel free to add it to the '''top''' of this list.<br />
<!--<br />
<br />
Add to the *top* of this list<br />
<br />
--><br />
* [http://blog.georgebrock.com/events/open-hack-london-xfn-profile-discovery XFN profile discovery] - A Greasemonkey script that follows rel="me" links from the current page to find a person's other sites and profiles.<br />
* [http://afrigator.com Afrigator] by [[Stii|Stii Pretorius]] - use XFN data found on blog rolls to find friends on Afrigator.com (Screen cast - [http://www.vimeo.com/1110175 http://www.vimeo.com/1110175])<br />
* [http://digg.com/ Digg] by [[SteveWilliams|Steve Williams]] (Example: [http://digg.com/users/sbwms Steve's Digg user profile].)<br />
* [http://donpark.org:3301/ XFN friend finder] by Don Park ([http://www.donpark.org/blog/articles/2008/03/15/my-rss-reader-just-killed-friendfeed blog explanation]).<br />
* [http://www.qmpeople.com/ qmpeople] - Generates XFN from address book properties of registered users - e.g. http://www.qmpeople.com/users/laserion<br />
* [http://textcube.org TextCube] Blogging tool TextCube version 1.6 and later.<br />
* [http://code.google.com/apis/socialgraph/ Google Social Graph API] uses XFN data from public Web sites as its main data source.<br />
<!--<br />
<br />
Add to the *top* of this list<br />
<br />
--><br />
<br />
== update streams and pingers ==<br />
* [http://updates.elsewhere.im/ SixApart Relationship Update Stream] - launched 2007-10-19<br />
<br />
== authoring publishing ==<br />
The following tools, plugins, and extensions enable authors to eaily create and publish XFN links:<br />
* [http://icite.net/develop/software.html#ll4blojsom LL4blojsom] is the LinkList plugin for the [http://blojsom.sf.net blojsom] blog engine. blojsom, written in Java, is the open source application behind the Tiger Weblog Server that is part of OS X server. The LL4blojsom plugin is used for creating XFN blogrolls.<br />
* [http://www.zachinglis.com/projects/xfn-rel-creator/ XFN rel Creator] This script replaces any links within the designated tags and replaces them with a visual representation of the links. Default set as abbrevations but with CSS it is easy to replace them for images.<br />
* [http://www.wordpress.org/ WordPress] has XFN support built-in to its Link Manager function, which is used for generating blogrolls. When in the administrative interface, choose the Links top-level menu item, then choose Add Link. The link form lets you choose which XFN properties you wish the link to have. When displaying the links on the site via any of the standard WordPress template tags, it will automatically format it with the appropriate tags in the rel attribute. (based on [http://gmpg.org/xfn/creator XFN Creator])<br />
* [http://www.communityserver.org/ Community Server] has XFN support in its blog Link Lists. It allows you to select which XFN tag(s) to use for each link.<br />
* [http://www.webstandards.org/action/dwtf/microformats/ Dreamweaver Extension suite] from the [http://webstandards.org/ Web Standards Project] enables the authoring of XFN links from within Dreamweaver 8.<br />
* [http://placenamehere.com/TXP/pnh_mf/ pnh_mf] is a plugin for [http://textpattern.com/ Textpattern] that supports embedding XFN and other microformats in templates and blog posts. Written by [http://placenamehere.com/ Chris Casciano].<br />
* [http://www.oddmuse.org/cgi-bin/oddmuse/xfn_Module OddMuse XFN Module] allows a wiki markup in OddMuse wikis for entering data about xfn relationships<br />
* [http://blo.gs/ blo.gs] – Allows you to add information regarding your relationship to the people behind the blogs in your favorites list. [http://blo.gs/news.php#n56 XFN 1.1 support added 2004-08-20].<br />
* [http://www.nvu.com/ Nvu] – HTML editor that integrates XFN editing into its hyperlink editing dialogs.<br />
<br />
=== XFN Creators ===<br />
The [http://gmpg.org/xfn/creator XFN Creator] has been localized to numerous languages (see the [[rel-alternate]] links in the head). Additional localizations are provided below. <br />
<br />
If you are a native/fluent reader of the following languages, please review the respective XFN creators and leave a nested list comment evaluating them. Once a creator has been sufficiently well reviewed, it should be copied to gmpg.org (or preferably http://microformats.org/code/xfn/ and http://microformats.org/code-tools) and rel-alternate linked accordingly.<br />
<br />
* [http://www.beyondcow.com/creator-ch.html XFN 1.1 生成器] (Chinese), [http://twitter.com/lianxu/status/8961983572 published 2010-02-11] by [http://twitter.com/lianxu/status/8961804821 twitter.com/lianxu].<br />
* ...<br />
<br />
== friends lists ==<br />
Numerous services support both XFN friends lists, and even better XFN+[[hcard|hCard]] friends lists.<br />
* See [[hcard-xfn-friends-lists|hCard+XFN friends lists]].<br />
<br />
== rel me identity equivalency ==<br />
* [http://wordpress.org/extend/plugins/yadis/ YADIS plugin] supports OpenID delegation links that are also compatible XFN rel-me links.<br />
* [http://wink.com Wink] supports rel-me (see [http://wink.com/beach--profile])<br />
** '''suboptimal''': uses "nofollow me" where it should just use "me". User entered profile information is first party, not 3rd party, and therefore should not be labeled with [[rel-nofollow]].<br />
<br />
== validators ==<br />
* [http://tools.microformatic.com/help/xhtml/rel-lint/ rel-lint] by [[User:DrewMcLellan|Drew McLellan]] will validate existence of XFN attributes.<br />
<br />
== visualizers and browsers ==<br />
* [http://manyeyes.alphaworks.ibm.com/manyeyes/visualizations/xhtml-friends-network-with-twitter XFN visualization] example at IBM's Many Eyes made with [http://sphinx.net.ru/hg/xfn-spider xfn-spider] — simple crawler extracting microformats with XSLT ([http://sphinx.net.ru/blog/entry/simple-microformat-xslt-extraction/ Original article in Russian] circa summer 2007) and exporting information to OPML feedlist, [http://manyeyes.alphaworks.ibm.com/manyeyes/visualizations/tags-from-a-bigger-xhtml-friend-netw tag cloud] etc.<br />
* [http://xfngraph.sourceforge.net XFN Graph] — a multi-platform Java-based tool which creates spider diagrams of XFN relationships from any given starting URL.<br />
* [http://xfnroll.new-bamboo.co.uk/people/popular XFNRoller] (to be lifestalker.com) XFN spider and browser focused on using blogs to represent individuals. Exports OPML of feeds for lists such as top 10 most popular people.<br />
<br />
== search ==<br />
* [http://xfnsearch.joshpeek.com/ XFN Search] (appears to require HTTP-authentication login)<br />
<br />
== converters ==<br />
* see [[xfn-to-foaf]]<br />
<br />
== appear old or unverifiable ==<br />
These sites appear to be too old, and or perhaps broken (like PHP error dump).<br />
* '''[http://tagalag.com Tagalag]''' [http://tagalag.com/tools.html#xfn supports] a partial XFN vocabulary.<br />
<br />
== offline ==<br />
The following XFN implementations appear to be offline:<br />
* '''Autoxfn''' – A module for Bloxsom that adds XFN annotations to links in an entry.<br />
** was at <nowiki>http://weblog.scifihifi.com/2004/02/08/autoxfn-10/</nowiki> as of 2004-02-08.<br />
* '''exefen''' – A Web-based interface that allows quick XFN annotation of all the links on a page. You can save the result and paste it back into your HTML source.<br />
** was at <nowiki>http://photomatt.net/tools/exefen/</nowiki> as of 2004(?).<br />
<br />
== See Also ==<br />
{{xfn-related-pages}}</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xfn-fr&diff=70194xfn-fr2020-07-18T16:35:24Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:XFN - The XHTML Friends Network}}<br />
<p class="entry-summary"><abbr title="XHTML Friends Network">XFN</abbr> est un moyen simple de représenter les relations humaines en utilisant les hyperliens.</p><br />
<br />
La spécification XFN et plus d'informations peuvent être trouvés sur [http://www.gmpg.org/xfn/ GMPG.org].<br />
<br />
* [http://gmpg.org/xfn/ XFN page d'accueil]<br />
* [http://gmpg.org/xfn/intro introduction à XFN]<br />
* [http://gmpg.org/xfn/and/#idconsolidation XFN et consolidation d'identité avec rel="me"]<br />
<br />
<br />
== articles ==<br />
Cette section est "informative".<br />
<br />
Voir [[xfn-articles-fr|articles-xfn]].<br />
<br />
== en rapport ==<br />
Quelques pages discutant de XFN peuvent être trouvées sur ce wiki :<br />
<br />
{{xfn-related-pages-fr}}<br />
<br />
<br />
[[Category:Specifications]]<br />
[[Category:XFN]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xfn-faq-fr&diff=70193xfn-faq-fr2020-07-18T16:35:23Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE: XFN FAQ }}<br />
<br />
Cette page est destinée à documenter les Q&R sur [[xfn-fr|XFN]] en plus des [http://gmpg.org/xfn/faq XFN FAQ officielles]. Il est probable que les items ici seront incorporés là-bas. Ou peut-être que GMPG peut choisir de rediriger la FAQ ici - ceci doit être déterminé. A cette heure, si vous avez une nouvelle question à poser à propos de XFN, considérez SVP de la poser d'abord sur la liste de discussion [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss].<br />
<br />
SVP, lisez d'abord la page officielle des [http://gmpg.org/xfn/faq XFN FAQ].<br />
<br />
<br />
== clarifications sur les valeurs ==<br />
<br />
=== Pourquoi est-ce que "muse" est dans la catégorie "romantic" ===<br />
''Selon la [http://gmpg.org/xfn/11 spec XFN], rel="muse" est un lien vers quelqu'un qui vous inspire, et est listé comme une relation "romantique". Est-ce toujours sous-tendu par une relation romantique, parce qu'on pourrait trouver certainement quelqu'un d'autre d'inspirant sans être intéressé/impliqué émotionnellement ?''<br />
<br />
* Bien sûr, "muse" n'était pas destiné à être purement romantique dans le sens romantique littéral de "relation romantique" (bien qu'il soit clair sur la façon dont cela pourrait être mal interprété), et bien sûr ce sens est inclus. La catégorisation sous "romantic" est dans un sens plus large, similaire au [http://fr.wikipedia.org/wiki/Romantisme romantisme] tout comme en permettant l'élévation de : <blockquote>"the achievements of what it [Romanticism] perceived as misunderstood heroic individuals and artists that altered society."</blockquote> ou [http://en.wikipedia.org/wiki/Romance_%28genre%29 romance the genre].<br />
* La [http://gmpg.org/xfn/11 spec XFN] définit ''muse'' tout comme ''crush'', et on devrait ne pas la confondre avec l'autre. Quoi qu'il en soit, romantiquement ou au sens figuré, la muse inspire.<br />
* Remarquez aussi : [http://en.wiktionary.org/wiki/muse la définition du Wiktionary de ''muse'']<br />
<br />
=== Comment je marque ma relation avec les entreprises dans lesquelles j'ai travaillé ===<br />
'Comment je marque ma relation avec les entreprises dans lesquelles j'ai travaillé ?''<br />
<br />
* Marquez les sociétés dans lesquelles vous avez travaillé sur votre page de résumé/CV avec [[hresume-fr|hResume]]. Dedans chacun de vos jobs est marqué avec un événement [[hcalendar-fr|hCalendar]] avec une [[hcard-fr|hCard]] embarquée qui représente votre identité (title, url, org-unit etc) pendant que vous étiez dans cette société.<br />
<br />
* Pour les organisations et sociétés dont vous faites partie actuellement, jetez un oeil à la proposition de microformat en brainstorming sur [[rel-group]]<br />
<br />
=== Comment je marque les personnes avec lesquelles j'ai travaillé===<br />
''Comment je marque les personnes avec lesquelles j'ai travaillé ?''<br />
<br />
* Utilisez la relation XFN 'colleague' pour marquer votre relation actuelle avec vos précédents collègues.<br />
* En outre, vous pouvez utiliser XFN sur les liens vers les personnes dans un billet de blog pour régler un contexte de date et horaire quand cette relation était vraie. Ainsi au fil du temps, il est possible d'utiliser différentes valeurs XFN reflétant la nature évoluante de vos relations. Voir [http://gmpg.org/xfn/background#timeless XFN: Background: Out of time] pour en savoir plus.<br />
=== Comment marquer l'information de lieu comme mon bureau ===<br />
''Is there anything in there for locative info, like 'my office,' etc.? [http://twitter.com/chrisbrogan/statuses/680669842 1]'' <br /><br />
''We have "rel" tags for humans. Is there an equivalent for location and place? [http://twitter.com/chrisbrogan/statuses/680135072 2]'' <br />
<br />
Marquez les lieux en rapport avec votre bureau comme une partie de votre <code>type</code> <code>work</code> adresse (<code>adr</code>) dans votre [[hcard-fr|hCard]].<br />
<br />
=== Pourquoi XFN omet les valeurs négatives===<br />
''Wondering why XFN definitions do not include "fool", "enemy", "jerk", "pedant", and so forth. [http://twitter.com/Vaguery/statuses/673040272 1]''<br />
<br />
<blockquote><p>Negative relationship terms have been omitted from XFN by design. The authors think that such values would not serve a positive ends and thus made the deliberate decision to leave them out.</p></blockquote><br />
<br />
Extrait de "[http://gmpg.org/xfn/background#positive XFN Background: Positive or neutral relationships only]" - plus de raisons et explications ici.<br />
<br />
=== Existe-t'il des relations asymétriques XFN ? ===<br />
''Is there such a thing as an asymmetric xfn relationship?''<br />
<br />
La plupart des relations XFN ne doivent pas être symétriques et sont par conséquent asymétriques dans l'usage du vrai monde. Les seules relations XFN qui sont "en fait toujours symétriques" (selon le profil [http://gmpg.org/xfn/11 XFN 1.1 profile]) sont :<br />
* [[rel-co-worker]]<br />
* [[rel-colleague]]<br />
* [[rel-co-resident]]<br />
* [[rel-date]]<br />
**en pratique, il a été pointé dans les différentes définitions de 'date' utilisées dans le discours commun que celles ci mènent souvent à des asymétries de compréhension entre un individu et une personne, qu'elles aient une relation rel-date. Ceci pourrait probablement utiliser plus d'analyse en provenance du vrai monde.<br />
* [[rel-kin]]<br />
* [[rel-met]]<br />
* [[rel-neighbor]]<br />
* [[rel-sibling]]<br />
* [[rel-spouse]]<br />
* [[rel-sweetheart]]<br />
<br />
Une relation XFN '''obligatoirement symétrique''', a moins que la relation ne soit revendiquée dans les deux directions (par ex. avec un hyperlien, voir définitions pour les détails), la relation ne peut pas être affirmée :<br />
* [[rel-me]]<br />
<br />
Toutes les autres relations XFN 1.1 ne sont pas obligatoirement symétriques, elles ne peuvent non plus être nécessaires ou attendues.<br />
<br />
=== Y'a-t'il une relation fan===<br />
''Is there a 'fans' or 'fan of' type of XFN relationship?''<br />
<br />
Voir [[xfn-brainstorming#fans_and_followers|XFN Brainstorming: fans and followers]].<br />
<br />
=== Si je suis fan de quelqu'un quelle relation devrais-je utiliser au moment de faire un lien===<br />
''If I'm a fan of someone, what XFN rel value should I use when linking to them?''<br />
<br />
A cette heure, il n'existe pas de bon terme inverse pour déclarer que vous êtes fan de quelqu'un. Vous pouvez déclarer l'inverse, ce qui veut dire, vous pouvez essayer de lier vers quelqu'un le fait que vous déclarez être un fan de vous avec rel="fan" selon le [[xfn-brainstorming#fans_and_followers|fans and followers brainstorming]], mais il n'existe à cette heure [http://twitter.com/t/statuses/746089852 pas de bon inverse de fan] pour lier vers des personnes dont vous êtes fan.<br />
<br />
==== Devrais-je déclarer cette personne comme une connaissance ====<br />
Follow-up: ''Would I identify as an acquaintance of that person?''<br />
<br />
Pas nécessairement. [[rel-acquaintance]] déclare plus que ça, ce qui veut dire, que vous avez au moins eu une conversation ou quelque sorte d'interaction avec elle. Vous n'avez pas besoin de quelque interaction avec les personnes dont vous êtes fan.<br />
<br />
A cette heure, vous pourriez utiliser [[rel-contact]] pour déclarer au moins que vous avez quelque information de contact avec cette personne (son URL) ou considérez cette personne comme un contact, et ce même si cela même si ça ne charrie pas le sens que vous en êtes fan.<br />
<br />
== aide sur la publication ==<br />
=== validation ===<br />
''Wondering how people intend to validate xfn… [http://twitter.com/lmjabreu/statuses/667894392 1]''<br />
<br />
* Utilisez le validateur [http://tools.microformatic.com/help/xhtml/rel-lint/ rel-lint] de [[User:DrewMcLellan|Drew McLellan]]qui vérifie une page sur les [[rel values|valeurs rel]] standards extraites du HTML 4.01 et XFN 1.1, et affiche des avertissements pour les valeurs non reconnues.<br />
<br />
Voir [[xfn-implementations-fr#validateurs| XFN Implementations: validateurs]] pour en savoir plus.<br />
<br />
== autres possibilités ==<br />
=== Pourquoi ne pas utiliser rev au lieu d'un mot-clé pour indiquer l'inverse===<br />
''Why not exploit the rev property to avoid having to use a different keyword to denote the reverse? --[[User:WizardIsHungry|Jon Williams]] 14:41, 8 Jan 2007 (PST)''<br />
<br />
* Pour faire vite, <code>rev</code> ne devrait pas être utilisé. Pour plus de détails, voir [[rel-faq-fr|rel FAQ]] en particulier [[rel-faq-fr#Est-ce_rev_devrait_.C3.AAtre_utilis.C3.A9|'rev' devrait-il être utilisé]].<br />
<br />
=== Est-ce que les liens XFN utilisent des protocoles autres que http ===<br />
''Pouvez-vous utiliser rel="me" pour d'autres protocoles que HTTP ? tels que mailto: ou aim:? --[[User:BrianSuda|Brian Suda]] [http://rbach.priv.at/Microformats-IRC/2006-05-12#T033706 03:37, 2006-05-12] (PST)''<br />
<br />
* La réponse actuelle est "oui" tout particulièrement parce que XFN ne fait que décrire la relation entre deux choses, plutôt que le protocole avec lequel l'une ou l'autre des choses est adressée.<br />
<br />
== développement ==<br />
<br />
=== Comment vous auto-découvrez XFN ===<br />
''I am interested in the autodiscovery of microformats in html especially xfn. What would that look like? [http://twitter.com/rmarkwhite/statuses/677103472 1]''<br />
<br />
* Sur toute page web qui représente une personne, parsez le HTML, tout spécialement les attributs des liens <code>rel</code> séparés par des espaces (éléments <code>a</code> et <code>link</code>), et jetez un oeil aux [http://gmpg.org/xfn/11 18 valeurs XFN 1.1] parmi les [[rel values-fr|valeurs rel]]. Répétez pour les pages que pointent ces liens avec des valeurs XFN rel. Pour en savoir plus sur la façon de crawler les liens (ou un sous ensemble déterminé par des valeurs rel) sur le Web, consultez n'importe lequel des ouvrages sur la façon de crawler le web.<br />
<br />
=== Does consolidating a paginated friends list scale ===<br />
Note : Ceci est une FAQ "implémentation".<br />
<br />
''How do services that publish [[hcard-xfn-supporting-friends-lists|hCard+XFN supporting friends lists]] and use the <code>rel="me next"</code> and <code>rel="me prev"</code> [[hcard-xfn-supporting-friends-lists#Implement_hCard_XFN_supporting_friends_lists|method for consolidating paginated friends lists]] scale?''<br />
<br />
The short answer is: it is pagination that actually scales and publishing complete lists that does not.<br />
<br />
In real world practical experience, [http://twitter.com Twitter]'s live-on-the-web implementation right now has demonstrated not only that the pagination approach already scales, <strong style="text-transform:uppercase">but</strong> more importantly:<br />
<br />
"publishing all your friends on one resource" <strong style="text-transform:uppercase">does not</strong> scale.[[xfn-faq#not-scale-explanation|*]]<br />
<br />
Twitter employee Blaine said as much at the [[events/2007-08-28-social-network-portability-today|Social Network Portability Today meetup at the Satisfactory]], due primarily to database load.<br />
<br />
Note that because this is a <em>backend</em> issues, this is true regardless of the format sent to the front end client (whether HTML, random XML, or CSV). And whether you call it an "API call" or "HTTP GET request" or "page load", on the Web they are all the same thing.<br />
<br />
Note also that this isn't uncommon. Twitter isn't the only interface (whether user or programmatic) that requires clients (whether browsers or spiders) to retrieve paginated results. Most search engine APIs for example require clients to make paginated requests.<br />
<br />
<div id="not-scale-explanation"><br />
* Any such absolute statement ("does not scale") is obviously meant to summarize a measured result rather than be dogmatic in nature because obviously in the literal sense such an unqualified absolute statement can be disproven with carefully chosen examples. In this instance, it has been pointed out that there are services (namely LiveJournal) that can return hundreds of contacts in a single request without any difficulty. Problems have been noted by implementers (e.g. Twitter) when a friends list has more than about <strong>1500</strong> contacts, especially trending into the 10,000 range. With modern (as of 2007) servers and backend software stacks, returning simple datasets this size can take over a second if not cached, which is too long.<br />
</div><br />
<br />
== Voir aussi ==<br />
{{xfn-related-pages-fr}}</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xfn-faq&diff=70192xfn-faq2020-07-18T16:35:22Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE: XFN FAQ }}<br />
<br />
This page is for documenting Q&A about [[xfn|XFN]] in addition to the [http://gmpg.org/xfn/faq official XFN FAQ]. It is likely that items here will be incorporated there. Or perhaps GMPG may choose to redirect the FAQ here - this is to be determined. For now, if you have a new question to ask about XFN, please consider first asking your question on the [http://microformats.org/mailman/listinfo/microformats-discuss/ microformats-discuss] mailing list.<br />
<br />
Please first read the [http://gmpg.org/xfn/faq official XFN FAQ].<br />
<br />
== How do I reference the XFN profile in HTML5 ==<br />
''How do I reference the XFN profile in HTML5?''<br />
<br />
AKA the obsolete profile attribute problem.<br />
<br />
When validating an [[HTML5]] document, you may get a warning or error for using the profile attribute, like: <blockquote>The profile attribute on the head element is obsolete.</blockquote><br />
<br />
In HTML5 documents, instead of:<br />
<source lang=html4strict><br />
<head profile="http://gmpg.org/xfn/11"><br />
</source><br />
Use:<br />
<source lang=html4strict><br />
<head><br />
<link rel="profile" href="http://gmpg.org/xfn/11"/><br />
</source><br />
<br />
== value clarifications ==<br />
<br />
=== Why is muse in the romantic category ===<br />
''According to the [http://gmpg.org/xfn/11 XFN spec], rel="muse" is a link to someone who inspires you, and is listed as being a "romantic" relationship. Does it is always implied as a romantic relationship, since one could certainly find someone else inspiring without being romantically involved/interested?''<br />
<br />
* Certainly "muse" was not intended to only be purely romantic in the literal "romantic relationship" sense (though it is clear how that could easily be misconstrued), and of course that meaning is included. The categorization as "romantic" is in a broader sense, similar to [http://en.wikipedia.org/wiki/Romanticism romanticism] as in enabling the elevation of: <blockquote>"the achievements of what it [Romanticism] perceived as misunderstood heroic individuals and artists that altered society."</blockquote> or [http://en.wikipedia.org/wiki/Romance_%28genre%29 romance the genre].<br />
* The [http://gmpg.org/xfn/11 XFN spec] defines ''muse'' as well as ''crush'', and one ought not to be confused with the other. Either way, romantically or figuratively, the muse inspires.<br />
* Note also: [http://en.wiktionary.org/wiki/muse The Wiktionary definition of ''muse'']<br />
<br />
=== How do I markup my relationship to companies I used to work for ===<br />
''How do I markup my relationship to companies I used to work for?''<br />
<br />
* Markup companies that you used to work for on your resume page with [[hresume|hResume]]. In it each job is captured as an [[hcalendar|hCalendar]] event with a nested [[hcard|hCard]] that represents your identity (title, url, org-unit etc) while you were at that company.<br />
<br />
* For current companies and organizations that you are a part of, take a look at the [[rel-group]] microformat brainstorm proposal.<br />
<br />
=== How do I markup people that I used to work with ===<br />
''How do I markup people that I used to work with?''<br />
<br />
* Use the XFN 'colleague' relationship to markup your current relationship to your former co-workers.<br />
* In addition, you can use XFN on links to people within a blog post set a date and time context for when that relationship was true. Thus over time, it is possible to use different XFN values to reflect the evolving nature of your relationships. See [http://gmpg.org/xfn/background#timeless XFN: Background: Out of time] for more.<br />
<br />
=== How do I markup location info like my office ===<br />
''Is there anything in there for locative info, like 'my office,' etc.? [http://twitter.com/chrisbrogan/statuses/680669842 1]'' <br /><br />
''We have "rel" tags for humans. Is there an equivalent for location and place? [http://twitter.com/chrisbrogan/statuses/680135072 2]'' <br />
<br />
Markup location info related to your office as part of your <code>type</code> <code>work</code> address (<code>adr</code>) in your [[hCard]].<br />
<br />
=== Why does XFN omit negative values ===<br />
''Wondering why XFN definitions do not include "fool", "enemy", "jerk", "pedant", and so forth. [http://twitter.com/Vaguery/statuses/673040272 1]''<br />
<br />
<blockquote><p>Negative relationship terms have been omitted from XFN by design. The authors think that such values would not serve a positive ends and thus made the deliberate decision to leave them out.</p></blockquote><br />
<br />
From "[http://gmpg.org/xfn/background#positive XFN Background: Positive or neutral relationships only]" - more reasons and explanation provided there.<br />
<br />
=== Are there any asymmetric XFN relationships ===<br />
''Is there such a thing as an asymmetric xfn relationship?''<br />
<br />
Most XFN relationships are not required to be symmetric and are therefore often asymmetric in real world use. The only XFN relationships that are '''effectively always symmetric''' (per the [http://gmpg.org/xfn/11 XFN 1.1 profile]) are:<br />
* [[rel-co-worker]]<br />
* [[rel-colleague]]<br />
* [[rel-co-resident]]<br />
* [[rel-date]]<br />
**in practice it has been pointed out that the broadly varying definitions of 'date' used in common discourse often lead to asymmetries of understanding between one individual and a person they have a rel-date relationship with. This could probably use more real world analysis.<br />
* [[rel-kin]]<br />
* [[rel-met]]<br />
* [[rel-neighbor]]<br />
* [[rel-sibling]]<br />
* [[rel-spouse]]<br />
* [[rel-sweetheart]]<br />
<br />
One XFN relationship is '''required symmetric''', that is, unless the relationship is asserted in both directions (e.g. with a hyperlink, see value definitions for details), the relationship cannot be asserted:<br />
* [[rel-me]]<br />
<br />
All other XFN 1.1 relationships are not required to be symmetric, nor can they necessarily or should be expected to be.<br />
<br />
=== Is there a fan or fan of relationship ===<br />
''Is there a 'fans' or 'fan of' type of XFN relationship?''<br />
<br />
See [[xfn-brainstorming#fans_and_followers|XFN Brainstorming: fans and followers]].<br />
<br />
=== If I am a fan of someone what rel should I use when linking to them ===<br />
''If I'm a fan of someone, what XFN rel value should I use when linking to them?''<br />
<br />
Right now there is no good inverse term for stating that you are a fan of someone. You can assert the inverse, that is, you can try linking to someone who you are asserting is a fan of you with rel="fan" per the [[xfn-brainstorming#fans_and_followers|fans and followers brainstorming]], but currently there is [http://twitter.com/t/statuses/746089852 no good inverse of fan] to link to people that you are a fan of.<br />
<br />
==== follow up would I identify as an acquaintance of that person ====<br />
Follow-up: ''Would I identify as an acquaintance of that person?''<br />
<br />
Not necessarily. [[rel-acquaintance]] asserts more than that, that is, that you have at least had a conversation or some sort of interaction with them. You don't necessarily have any interaction with people that you are a fan of.<br />
<br />
For now, you could use [[rel-contact]] to at least assert that you have some contact information for that person (their URL presmably) or consider that person to be a contact, but even that doesn't convey the meaning that you are a fan of theirs.<br />
<br />
== authoring and publishing help ==<br />
=== validation ===<br />
''Wondering how people intend to validate xfn… [http://twitter.com/lmjabreu/statuses/667894392 1]''<br />
<br />
* Use the [http://tools.microformatic.com/help/xhtml/rel-lint/ rel-lint] validator by [[User:DrewMcLellan|Drew McLellan]] which checks a page for standard [[rel values]] from HTML 4.01 and XFN 1.1, and shows warnings for any unrecognized values.<br />
<br />
See [[xfn-implementations#validators| XFN Implementations: validators]] for more.<br />
<br />
== other possibilities ==<br />
=== Why not use rev instead of a keyword to denote the reverse ===<br />
''Why not exploit the rev property to avoid having to use a different keyword to denote the reverse? --[[User:WizardIsHungry|Jon Williams]] 14:41, 8 Jan 2007 (PST)''<br />
<br />
* In short, <code>rev</code> should not be used. For more details see the [[rel-faq|rel FAQ]] in particular [[rel-faq#Should_.27rev.27_even_be_used|Should 'rev' even be used]].<br />
<br />
=== Can XFN links use protocols other than http ===<br />
''Can you use rel="me" for other protocols besides HTTP? such as mailto: or aim:? --[[User:BrianSuda|Brian Suda]] [http://rbach.priv.at/Microformats-IRC/2006-05-12#T033706 03:37, 2006-05-12] (PST)''<br />
<br />
* The current answer is "yes" particular because XFN only described the relationship between two things, rather than the protocol with which either thing is addressed.<br />
<br />
== development ==<br />
<br />
=== How do you do autodiscovery of XFN ===<br />
''I am interested in the autodiscovery of microformats in html especially xfn. What would that look like? [http://twitter.com/rmarkwhite/statuses/677103472 1]''<br />
<br />
* On any webpage that represents a person, parse the HTML, especially the space-separated <code>rel</code> attributes of the links (<code>a</code> and <code>link</code> elements), and look for [http://gmpg.org/xfn/11 18 XFN 1.1 values] among the [[rel values]]. Repeat for the pages that those links with XFN rel values point to. For more on how to crawl links (or a subset thereof determined by rel values) on the Web, see any number of books on how to spider and crawl the web.<br />
<br />
=== Does consolidating a paginated friends list scale ===<br />
Note: this is an ''implementation'' FAQ.<br />
<br />
''How do services that publish [[hcard-xfn-supporting-friends-lists|hCard+XFN supporting friends lists]] and use the <code>rel="me next"</code> and <code>rel="me prev"</code> [[hcard-xfn-supporting-friends-lists#Implement_hCard_XFN_supporting_friends_lists|method for consolidating paginated friends lists]] scale?''<br />
<br />
The short answer is: it is pagination that actually scales and publishing complete lists that does not.<br />
<br />
In real world practical experience, [http://twitter.com Twitter]'s live-on-the-web implementation right now has demonstrated not only that the pagination approach already scales, <strong style="text-transform:uppercase">but</strong> more importantly:<br />
<br />
"publishing all your friends on one resource" <strong style="text-transform:uppercase">does not</strong> scale.[[xfn-faq#not-scale-explanation|*]]<br />
<br />
Twitter employee Blaine said as much at the [[events/2007-08-28-social-network-portability-today|Social Network Portability Today meetup at the Satisfactory]], due primarily to database load.<br />
<br />
Note that because this is a <em>backend</em> issues, this is true regardless of the format sent to the front end client (whether HTML, random XML, or CSV). And whether you call it an "API call" or "HTTP GET request" or "page load", on the Web they are all the same thing.<br />
<br />
Note also that this isn't uncommon. Twitter isn't the only interface (whether user or programmatic) that requires clients (whether browsers or spiders) to retrieve paginated results. Most search engine APIs for example require clients to make paginated requests.<br />
<br />
<div id="not-scale-explanation"><br />
* Any such absolute statement ("does not scale") is obviously meant to summarize a measured result rather than be dogmatic in nature because obviously in the literal sense such an unqualified absolute statement can be disproven with carefully chosen examples. In this instance, it has been pointed out that there are services (namely LiveJournal) that can return hundreds of contacts in a single request without any difficulty. Problems have been noted by implementers (e.g. Twitter) when a friends list has more than about <strong>1500</strong> contacts, especially trending into the 10,000 range. With modern (as of 2007) servers and backend software stacks, returning simple datasets this size can take over a second if not cached, which is too long.<br />
</div><br />
<br />
== See Also ==<br />
{{xfn-related-pages}}<br />
adde</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xfn-brainstorming&diff=70191xfn-brainstorming2020-07-18T16:35:19Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE: XFN Brainstorming }}<br />
{{TOC-right}}<br />
This page is for brainstorming about various uses and details of [[XFN]], as well as collecting input for potential extensions.<br />
<br />
== Required Reading ==<br />
Before participating in any XFN brainstorming please read and understand the following:<br />
* [http://gmpg.org/xfn/intro XFN intro]<br />
* [http://gmpg.org/xfn/background XFN background]<br />
* [[xfn-faq|XFN FAQ]] <br />
* [http://gmpg.org/xfn/and XFN and other services]<br />
* [[rel-faq]]<br />
<br />
Note that all existing XFN values were based on research that showed real world sites that indicated such relationships explicitly via text and hyperlinks to other sites. Thus any new semantics or values will be more seriously considered if URLs demonstrating existing text labeling and hyperlinking behavior are provided.<br />
<br />
== Contributors ==<br />
* [http://tantek.com/ Tantek Çelik]<br />
* [[User:CiaranMc |CiaranMc ]]<br />
* [http://factoryjoe.com/ Chris Messina]<br />
* [http://kevinmarks.com/ Kevin Marks]<br />
<br />
== general ==<br />
* [[xfn-wants]]<br />
<br />
== Identity Consolidation ==<br />
See [[rel-me]] and [[identity-consolidation]]. <span id="Frames">&nbsp;</span><br />
<br />
=== Indicating non-identity ===<br />
I think we need a way to indicate that another page should not be consolidated into your identity. - KevinMarks<br />
<br />
==== common name disambiguation ====<br />
If you have a common name, creating a disambiguation page or pages to indicate which ones aren't you is useful for indexers and people alike. In fact there are examples of people already creating such a page and linking to pages that are not them. Real world use cases that would benefit:<br />
* Kevin Kelly (the former Wired editor) has put together a page to indicate [http://kevinkelly.name|other people also called "Kevin Kelly"].<br />
* [http://vadim.com Vadim Akslerod] has created a page of [http://vadim.com/vadim/ Vadims on the Net] that link to other people called Vadim.<br />
<br />
==== accidental or malicious rel-me links ====<br />
If someone accidentally or maliciously links to one of my pages with rel="me" it would be good to be able to actually deny the connection, rather than just passively not link back. See [http://socialgraph-resources.googlecode.com/svn/trunk/samples/findyours.html?q=kevinmarks.com | the social graph API results for kevinmarks.com] for examples. - KevinMarks<br />
<br />
This appears to be more of a theoretical use case (as compared to the common name disambiguation) because the real world use ''is'' to simply '''not''' link back, and I don't think we should encourage people to add links to things that are not them, nor are they likely to, especially if it is a spammer/stalker/griefer that is linking to them. - [[User:Tantek|Tantek]]<br />
<br />
==== notme proposal ====<br />
initial proposal: <code>rel="notme"</code>, though very open to better suggestions.<br />
<br />
== Extending family relationships ==<br />
<br />
=== grandparent ===<br />
<cite>[http://www.gmpg.org/xfn/background The XFN: Background page]</cite> says:<br />
<blockquote><br />
We considered adding "grandparent," but in the end dropped the term because it seemed unlikely to be used in the near future. It may appear in future versions of XFN.<br />
</blockquote><br />
<br />
Presumably the assumption is that a grandparent won't have a website, but:<br />
<div class="discussion"><br />
* I think it's important in some situations to capture the age difference in a relationship in a way that rel="kin" doesn't seem to.<br />
** Additional XFN rel values is the wrong way to represent age information (even relative). Instead, mark up each person's page with an hCard for them that has a <code>bday</code> property, with even just the year if you want - that could then be used to determine an approximate age difference, which is presumably all that is desired. [[User:Tantek|Tantek]]<br />
* ''rel=kin'' with an age difference of, say, 45 years, might represent any of parent, grandparent, uncle, sibling, cousin or more.<br />
** Again, age (and thus differences) should be represented by use of the [[hCard]] 'bday' property, not rel. [[User:Tantek|Tantek]] 19:27, 15 June 2009 (UTC)<br />
</div><br />
<br />
==== grandparent examples ====<br />
If people actually find and document non-trivial examples of links to grandparent sites and this section gets too big, perhaps we can move it to [[grandparent-examples]].<br />
<br />
To date, no real world examples have been documented of URLs of grandchildren linking to their grandparents, thus, per the microformats [[process]], we should not complicate a format for a ''theoretical'' need. <br />
<br />
Anyone that cares to pursue this may find some real world examples to document in the following web searches (note that search links themselves are not examples, but merely a step towards finding real world examples which still need to be individually analyzed, checked against being false positives etc.) <br />
* [http://www.google.co.uk/search?&q=%22my+grandpa%27s+website%22 search for "my grandpa's website"]<br />
* [http://www.google.co.uk/search?&q=%22my+grandfather%27s+website%22 search for "my grandfather's website"]<br />
* [http://www.google.co.uk/search?&q=%22my+grandma%27s+website%22 search for "my grandma's website"]<br />
* [http://www.google.co.uk/search?&q=%22my+grandmother%27s+website%22 search for "my grandmother's website"]. <br />
<br />
See also [[genealogy-examples]].<br />
<br />
=== ancestor descendant ===<br />
Even if they don't maintain it themselves (or are deceased) there might be a URL that does a good job of representing a person.<br />
<br />
Consider a site about one's family tree. It might have something like:<br />
<source lang="html4strict"><br />
I can trace my family back to <a href="http://en.wikipedia.org/wiki/William_I_of_England">William the conqueror.</a><br />
</source><br />
In these cases it would be useful to have <code>rel="ancestor"</code>, and perhaps a corresponding <code>rel="descendant"</code>.<br />
-CiaranMc<br />
<br />
See also: [[genealogy-brainstorming#Relationships]]<br />
<br />
* rel="kin" can be considered sufficient until at least some number of non-trivial real world examples are provided.<br />
<br />
==== ancestor descendant examples ====<br />
If this section gets too big, perhaps we can move it to [[ancestor-descendant-examples]].<br />
* Wikipedia examples<br />
** [http://en.wikipedia.org/wiki/Winston_Churchill#Family_and_early_life Winston Churchill, with list if ancestors]<br />
** [http://en.wikipedia.org/wiki/Elizabeth_II_of_the_United_Kingdom#Marriage Queen Elizabeth II]: refers to "Queen Victoria as [her] great-great-grandmother". <br />
* See also [[genealogy-examples]].<br />
<br />
So far only a couple of (representative) real world examples (from just one site, Wikipedia) have been provided, thus, per the microformats [[process]], we should not complicate a format for a need clearly outside of the 80/20.<br />
<br />
== Simple Groups and Members ==<br />
A very simple extension to XFN could enable decentralized group membership. E.g.<br />
* rel="group". A person could link from their page to the page of a group that they belong to (e.g. their company, school, DJ collective etc.) and thus assert that they belong to that group.<br />
* rel="member". The web pages of groups could link to who they consider members and thus assert that person's membership.<br />
<br />
The relationships could be required bi-directional in order to confirm group membership, that is, both the individual must link to the group with rel="group" and the group must link to the individiual with rel="member" in order for the membership to be considered "true".<br />
<br />
See also [[group-brainstorming]] for more on this including documentation of examples.<br />
<br />
== fans and followers ==<br />
It's becoming a common aspect of many social networks (see list below) that you have unreciprocated and non-friend-based connections to people. These connections are particularly noteworthy where you don't really ever expect to have your connections reciprocated, but instead are similar to the idea of "rel-muse". <br />
<br />
=== follower and following ===<br />
The brainstorming on fans and followers and inverses thereof has appeared to settle (for many months - over a year(?)) on "follower" and "following" as mutual inverse relationship terms.<br />
<br />
Current summary:<br />
<br />
* rel="follower" - links to someone who is a follower, that is they are following you.<br />
* rel="following" - links to someone who is one of your "followings", i.e. someone you are following.<br />
<br />
Summary discussion:<br />
<div class="discussion"><br />
* I'd say they're ready for experimentation on websites in the wild. Once we have examples in the wild, we can promote this to a draft of [[rel-follower]]. [[User:Tantek|Tantek]] 00:13, 21 October 2010 (UTC)<br />
* We've had consensus on this for a while now - consider this an invitation for anyone to start stubbing out minimal descriptions for [[rel-follower]] and [[rel-following]], and then we can add them as brainstorming values as well as register them for use in HTML5 in the [[existing-rel-values]] page. [[User:Tantek|Tantek]] 16:55, 30 June 2011 (UTC)<br />
</div><br />
<br />
FAQ:<br />
<div class="discussion"><br />
* Q: Does <code>rel=following</code> mean that I read all their content daily/hourly/in real time?[http://indiewebcamp.com/irc/2013-08-28/line/1377706665]<br />
** A: <code>rel=following</code> just means reading some amount, no implications about timeliness, nor comprehensiveness.[http://indiewebcamp.com/irc/2013-08-28/line/1377706765]<br />
</div><br />
<br />
See below for the analysis and brainstorming that led to this outcome and for specific discussions.<br />
<br />
=== fan follower examples ===<br />
Sites that have the semantic / implied-schema of "fan" or "follower")<br />
* http://crowdvine.com/ (has fans and mutual fans and want to meet)<br />
* http://twitter.com/ (has followers vs friends)<br />
* http://upcoming.org/ (has fans vs friends)<br />
* http://www.sugarloot.com (has Fans vs Favorites)<br />
<br />
==== IndieWeb ====<br />
* http://hmans.io/following<br />
<br />
=== possible inverse of fan terms ===<br />
Brainstorm list of possible terms (for an inverse of fan/follower):<br />
<div class="discussion"><br />
* source<br />
** +1 I like this as a neutral term, <s>except that it would be better kept as a rel value for atom:source in [[hAtom]]</s> (on re-reading the Atom spec, atom:source should be a class on a containing element) [[User:Kevin Marks|Kevin Marks]]<br />
* influence<br />
* influencer<br />
** 0 [[User:Tantek|Tantek]] - I like this one, it seems to represent the implied semantics. If I follow someone, then they are an "influencer" to me. However, the point made by [[User:Donohoe]] below is a good one thus I've changed my opinion from +1 to +0 on this option.<br />
** -1 Sounds like "influenza", and just because I follow someone, doesn't mean they influence me. [[User:Gazza|Gazza]]<br />
** -1 - influence can be negative as well as positive: "The child only shoplifted because he was under the influence of older boys". [[User:AndyMabbett|Andy Mabbett]] 01:04, 26 Jan 2008 (PST)<br />
*** -1 Argument from theoretical example. [[User:Tantek|Tantek]] 21:46, 15 June 2009 (UTC)<br />
** -1 This seems too strong; the relationship is not meant to imply an endorsement; we have [[vote-links]] for that [[User:Kevin Marks|Kevin Marks]] Donohoe's reasoning below is good and I prefer 'following'<br />
** -1 This value is assigned one of 2 ways; arbitrarily by app, or by the user. I don't trust an app to make a decision on what constitutes an ''influencer'' and I don't see a user choosing that in its current wording --[[User:Donohoe|Donohoe]] 19:55, 5 Aug 2008 (PDT)<br />
*** I tend to agree with [[User:Donohoe|Donohoe]]'s reasoning. [[User:Tantek|Tantek]] 21:46, 15 June 2009 (UTC)<br />
* leader<br />
* star<br />
* hero<br />
* favorite<br />
* guider<br />
* role-model<br />
* idol<br />
** -1 [[User:Tantek|Tantek]] These all seem too strong and sometimes imply more subordination than most people want.<br />
* subscription<br />
** +1 Tony Stubblebine<br />
** +1 this one seems most neutral to me (a good thing) [[User:STHayden|STHayden]] 08:35, 3 Mar 2008 (PST)<br />
** -1 this makes sense in a feed-reader context, but not necessarily in a blogroll one; it implies the content rather than the person [[User:Kevin Marks|Kevin Marks]] 14:30, 24 Mar 2008 (PDT)<br />
** +1 Was neutral, now in favor --[[User:Donohoe|Donohoe]] 19:11, 6 Aug 2008 (PDT)<br />
** -1 against for same reasons as Kevin Marks. And "subscription" doesn't sound like a term for a person. -- [[User:Tantek|Tantek]]<br />
* of-interest<br />
* interest<br />
* followee<br />
* focus<br />
* <span id="following">following</span> - as the singular of "followings". If someone is one of your "followings", then you are following that someone, as opposed to if someone is one of your "followers", then that someone is following you! It may sound a bit clumsy/awkward as a term at first, but I think that's actually a sign of novel usage, which has some appeal because then it means the term may be available for us to fill it with this meaning - or I should say, amplify this meaning as it [http://search.twitter.com/search?q=followings has been given by existing Twitter users].<br />
** +1 [[User:Tantek|Tantek]] '''following''' is the best term I have seen for the inverse of fan/follower, and paired with '''follower''', provides a good enough complementary pair of relationships to express both directions.<br />
** Note that Google has now [http://buzz.blogger.com/2008/08/show-off-your-followers.html adopted the "follow" terminology]. -- [http://factoryjoe.com/ Chris Messina]<br />
** +1 'following'is widely adopted. Lets just decide on this and get it implemented. <br />
** +1 I think 'following' is now well understood thanks to both Twitter and Blogger using it, and worth codifying here [[User:Kevin Marks|Kevin Marks]]<br />
* follows<br />
** proposed by [http://schema.org/Person unknown authors at schema.org] I assume this meant to be a verb (like 'knows' ) rather than a plural adjective.<br />
</div><br />
<br />
=== rejected fan follower terms ===<br />
==== rel-fan ====<br />
<div class="discussion"><br />
I would propose adding "rel-fan" or "rel-follower" to the collection of XFN values -- as being something like a "contact" or a "muse" but having a different purpose within the realm of social networking. Again, given that this is showing up in social networks like Pownce (fan), Twitter (follower), and that these words are becoming common, I wonder if it wouldn't make sense to even ditch rel-muse in favor of rel-follower and rel-fan (the former implying some kind of positive social stalking and the latter a kind of amiable appreciation for someone's work). <br />
<br />
This fan/follower designation seems sorely lacking from Flickr where not everyone falls into either contact, friend or family... but in many cases, you just like someone's photos and want to be able to check in on them every now and again, similar to the way that people "follow" or "subscribe" to blog feeds... Someone who reads my blog feed could be considered a "follower" -- as in, "someone who follows my blog".<br />
<br />
- Chris Messina<br />
<br />
Chris, rel-fan or rel-follower would work for you to point to people who follow you, but the converse case is probably more useful, saying who you follow (eg blogroll case too). We need a good noun for that relationship that describes how you view them, that is less coloured than 'muse' currently is by being classified as romantic. rel-source or rel-influence maybe? Very hard to come up with a good noun. <br />
<br />
[[User:Kevin Marks|Kevin Marks]] 12:57, 17 Aug 2007 (PDT)<br />
<br />
* Hence the existence of the HTML "rev" attribute. [[User:TobyInk|TobyInk]] 00:12, 25 Feb 2008 (PST)<br />
** The [[rel-faq#Should_rev_even_be_used|use of rev has been deprecated]] since authors nearly always get it wrong. [[User:Tantek|Tantek]] 10:32, 6 Aug 2008 (PDT)<br />
*** I'm not suggesting that we create a new microformat using rev — I'm pointing out that if we define <code>rel=fan</code> (for linking to your fans) then <code>rev=fan</code> "automatically pops into meaning". (Besides which the usually quoted evidence of rev being "confusing" to authors (i.e. Google's analysis) is flaky at best.) [[User:TobyInk|TobyInk]] 15:26, 6 Aug 2008 (PDT)<br />
**** Suggesting the use of <code>rev=fan</code> (as you just did) *is* creating a new microformat using rev, so yes, you are suggesting it. And Google's analysis backed up many years of my (and others') personal anecdotal experience with web developers where &gt;90% did not understand the difference between rel and rev. [[User:Tantek|Tantek]] 17:53, 6 Aug 2008 (PDT)<br />
***** My point is that as per the [http://www.w3.org/TR/REC-html40/struct/links.html#adef-rev HTML 4 definition of <code>rev</code>] any time anyone defines a new link type <code>rel=''X''</code>, the meaning of <code>rev=''X''</code> becomes defined too. This is unavoidable. We should define new link types in terms of <code>rel</code> rather than <code>rev</code> for clarity, but we can't prevent people from taking advantage of the facilities inherent in (X)HTML to mark up the inverse meaning. (e.g. [http://changelog.ca/log/2005/09/12/proposed-microformats-for-reputation-and-trust-metrics <code>rev=tag</code> mention], [http://singpolyma.net/2007/05/the-state-of-distributed-social-networking/ and again], [http://styrheim.weblogg.no/311005201154_revtags.html and again]) [[User:TobyInk|TobyInk]] 01:17, 7 Aug 2008 (PDT)<br />
****** We can avoid use of 'rev' by (1) specifically recommending against use of it as the [[rel-faq#Should_rev_even_be_used|rel FAQ does]], and (2) by providing an inverse term that can be used with 'rel' so there is no need to use 'rev'. [[User:Tantek|Tantek]] 19:27, 15 June 2009 (UTC)<br />
</div><br />
<br />
==== rel-reader ====<br />
For blogrolls at least, what about rel-read / rel-reader? -- [[User:SteveIvy|Steve Ivy]]<br />
<br />
Steve, "read" is still a verb (and [[rel-values]] need to be nouns), and "reader" would still imply that they are a "reader" of yours, rather than vice versa. -- [[User:Tantek|Tantek]]<br />
<br />
How about "rel-reader" instead of "rel-follower" and "rel-reading" instead of "rel-following" ? It has the more 'neutral' and 'real world' connotation of actually reading and not 'following' people around. Also refers to the traditional word for such things in the book-world as in "Neil Gaiman's readers" and "I am reading Neil Gaiman" -- [[User:KP|Kartik]]<br />
<br />
On further thought and discussion with [[User:Tantek|Tantek]] (see: [http://logs.glob.uno/?c=freenode%23microformats&s=1+Jul+2014&e=1+Jul+2014#c72761 IRC logs reference] ), reader/reading denote textual content which seems too narrow for the Web.-- [[User:KP|Kartik]]<br />
<br />
==== rel-subscriber ====<br />
What about ''subscriber'' instead - also very neutral and more akin to others in the list? --[[User:Donohoe|Donohoe]] 19:55, 5 Aug 2008 (PDT)<br />
<br />
"subscriber" is no different from "reader" in this respect, and means the *opposite* of what we are looking for. I.e. a rel="subscriber" link to someone would mean that someone is a subscriber of my content/feed. -- [[User:Tantek|Tantek]]<br />
<br />
=== past examples ===<br />
Sites that previously provided real world examples of fans vs friends:<br />
* http://pownce.com/ (has fans vs friends) - until 2008-12-15 when the site moved to read-only mode.<br />
<br />
== favorites ==<br />
Another possibility is perhaps 'favorite', that is, people do link to favorite bands for example, which is similar to saying they are a fan of the band. Thus you could add <code>rel="favorite"</code> to such hyperlinks to indicate that that music band over there is a favorite of yours. [[User:Tantek|Tantek]] 17:57, 2 Oct 2007 (PDT) based on a question raised by DanBri.<br />
<br />
== mentors and mentees ==<br />
Though seemingly rare, I personally have found use for <code>rel="mentor"</code> and inverse <code>rel="mentee"</code> (see Wiktionary definitions: [http://en.wiktionary.org/wiki/mentor mentor], [http://en.wiktionary.org/wiki/mentee mentee]). I don't have sufficient evidence to even consider proposing adding these to XFN, but I wanted to capture them here as a brainstorm while I look into using them personally and research examples in the wild. I may just use them as [[POSH]] myself.<br />
<br />
[[User:Tantek|Tantek]] 02:34, 8 Jul 2007 (PDT)<br />
<br />
* +1 Erica OGrady<br />
* +1 needed by [https://github.com/open-app/core Enspiral] in their [http://www.enspiral.com/ Open App Ecosystem] as explained in [https://github.com/hackers4peace/plp-docs/issues/12#issuecomment-78043877 this github issue] &mdash [[User:Elf Pavlik|Elf Pavlik]] 22:49, 3 May 2015 (UTC)<br />
<br />
== advisor and advisee ==<br />
Similarly, I have seen folks reference someone as an advisor, or note that they are advising someone. We could consider <code>rel="advisor"</code> and <code>rel="advisee"</code> to capture and represent these semantics.<br />
<br />
Note that the relationship of advising a company or organization would be much better captured by noting "advisor" as a "role" property value in an hCard listing that organization, e.g.:<br />
<pre><nowiki><br />
<span class="vcard"><br />
<span class="fn">Tantek Çelik</span><br />
<span class="org">Citizen Agency</span><br />
<span class="role">advisor</span><br />
</span><br />
</nowiki></pre><br />
<br />
Again, I think [[POSH]] usage of these terms would make a good experiment to see if there is sufficient use to formalize them.<br />
<br />
[[User:Tantek|Tantek]] 07:45, 29 Dec 2007 (PST)<br />
<br />
== Influence out and influenced in ==<br />
<br />
Needing to provide more options to describe the flow of influence I've been considering the following relationship terms that fall into two predicate groups, influence out(applied) and influence in(received).<br />
<br />
Influence out: <br />
* 'follower'<br />
* 'student'<br />
* 'subscriber'<br />
* 'listener'<br />
* 'reader'<br />
* 'viewer'<br />
* 'supporter'<br />
* 'collaborator'<br />
<br />
Influence in: <br />
* 'inspiration'<br />
* 'favorite'<br />
* 'teacher'<br />
* 'mentor'<br />
* 'adviser'<br />
* 'influence'<br />
* 'source'<br />
* 'collaborator'<br />
<br />
Inline with xfn convention the terms are all nouns and refer to the far side of the link they are used in.<br />
<br />
[[User:James Tindall|James Tindall]] 14:23, 31 Aug 2008 (BST)<br />
<br />
== scholarly ==<br />
A possibility that might be added is scholarly definitions. For example:<br />
* <code>rel="mentor"</code>[Student's Teacher] (similar to above)<br />
** or perhaps <code>rel="teacher"</code> to indicate the distinct scholarly semantic. - [[User:Tantek|Tantek]]<br />
* <code>rel="student"</code>[Teacher's Student] (inverse of mentor)<br />
* <code>rel="classmate"</code>[Student's classmate]. <br />
Possible uses in Social Networking sites that involve adding your school, grading your teachers, etc. Teacher &lt;-&gt; Teacher would be specified in with the existing XFN <code>rel="co-worker"</code> or <code>rel="colleague"</code> values.<br />
<br />
[[User:Navarr|Navarr]] 05:56, 13 Dec 2007 (CST)<br />
<br />
== professional ==<br />
* [[xpn]] / [[xpn-examples]] - proposal to extend (or replicate) XFN for business (or professional - hence X'''P'''N) relationships<br />
<br />
== business to business ==<br />
There has been some discussion (on the microformats-discuss mailing list) about wanting to markup business to business relationships.<br />
<br />
While this is out of scope for XFN's person to person links, if a page/site does represent a company (e.g. if the [[representative hCard]] of the page was an organization) and links to other company sites, it could be useful.<br />
<br />
In particular <code>rel</code> values of:<br />
* <code>subsidiary</code>. designates a link to a subsidiary company of a controlling/parent company<br />
* <code>controlling</code>. designates a link to the controlling/parent company of a subsidiary company<br />
* ...<br />
<br />
Currently this is a theoretical example as no real world example pages of companies linking to other such company pages have been provided, and as such, there is insufficient research/usage/experience to merit consideration as a microformat.<br />
<br />
Those wishing to experiment with these rel values, should consider doing so as [[POSH]] and document their experience here so that we have some real world examples!<br />
<br />
[[User:Tantek|Tantek]] 19:27, 15 June 2009 (UTC)<br />
<br />
== met and wants to meet ==<br />
<br />
[http://lanyrd.com/ Lanyrd] allows to mark people as "Want to meet". Also some people like to keep track on who they have met. Based on [http://indiewebcamp.com/irc/2015-05-03/line/1430691481869 discussion on #indiewebcamp IRC]<br />
<br />
[[User:Elf Pavlik|Elf Pavlik]] 23:01, 3 May 2015 (UTC)<br />
<br />
<div class="discussion"><br />
* Note: [[XFN]] 1.1 already has [[rel-met|rel=met]]. [[User:Tantek|Tantek]] 23:01, 25 August 2015 (UTC)<br />
</div><br />
<br />
== see also ==<br />
{{xfn-related-pages}}<br />
* [[hcard|hCard]]<br />
* [[hcard-brainstorming|hCard brainstorming]]<br />
* [[social-network-portability]]<br />
* [http://xmlns.com/foaf/spec/ FOAF Vocabulary]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xfn-articles-fr&diff=70190xfn-articles-fr2020-07-18T16:35:18Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:Articles XFN}}<br />
<br />
{{stub-fr}}<br />
<br />
Les articles à propos de [[xfn-fr|XFN]] en particulier <br />
<br />
<br />
Ajoutez vos articles et billets de blog à propos de hCalendar, les plus récents en premier, groupés par années, en ajoutant des sections pour les années si nécessaire.<br />
<!--<br />
Gabarit : <br />
*<span class="hentry"><span class="published">AAAA-MM-JJ</span>: <span class="entry-summary"><cite class="entry-title">TITRE</cite> par <span class="author vcard"><span class="fn">AUTEUR</span></span>: <span class="url">http://exemple.com</span></span></span><br />
<br />
--><br />
<br />
== 2008 ==<br />
*<span class="hentry"><span class="published">2008-09-17</span>: <span class="entry-summary"><cite class="entry-title">Getting Semantic With Microformats, Part 2: XFN</cite> by <span class="author vcard"><span class="fn">Emily Lewis</span></span>: <span class="url">http://ablognotlimited.com/articles/getting-semantic-with-microformats-part-2-xfn/</span></span></span> - [http://christopheducamp.com/ProjetBlog/2008/09/21/emily-lewis-parvenir-a-la-semantique-avec-les-microformats-2eme-partie-xfn/ Parvenir au Sémantique avec les Microformats, 2ème partie – XFN]<br />
<br />
== non daté ==<br />
* [http://reference.sitepoint.com/html/xfn SitePoint reference: XFN] par Ian Lloyd<br />
<br />
== brisé ==<br />
Ces articles ont des liens brisés - voir peut-être si vous pouvez les retrouver dans http://archive.org et fournir un lien archive.org ici : <br />
* <nowiki>http://www.centralityjournal.com/archives/xfn_bottomup_social_networks.html</nowiki> - XFN:bottom-up Social Networks by Stowe Boyd]<br />
<br />
== voir aussi ==<br />
* [[hcalendar-fr|hCalendar]]<br />
* [[articles-fr|articles]]<br />
* [[hcard-articles-fr|hCard-articles]]<br />
* [[hcalendar-articles-fr|hCalendar-articles]]<br />
* [[hreview-articles-fr|hReview-articles]]<br />
* [[xfn-articles-fr|XFN-articles]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xfn-articles&diff=70189xfn-articles2020-07-18T16:35:18Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:XFN articles}}<br />
<br />
{{stub}}<br />
<br />
Articles about [[XFN]] in particular.<br />
<br />
Add articles and blog posts specifically about XFN, most recent first, grouped by year, adding sections for years as necessary.<br />
<!--<br />
Template:<br />
<br />
*<span class="hentry"><span class="published">YYYY-MM-DD</span>: <span class="entry-summary"><cite class="entry-title">TITLE</cite> by <span class="author vcard"><span class="fn">AUTHOR</span></span>: <span class="url">http://example.com</span></span></span><br />
<br />
--><br />
<br />
== 2008 ==<br />
*<span class="hentry"><span class="published">2008-09-17</span>: <span class="entry-summary"><cite class="entry-title">Getting Semantic With Microformats, Part 2: XFN</cite> by <span class="author vcard"><span class="fn">Emily Lewis</span></span>: <span class="url">http://ablognotlimited.com/articles/getting-semantic-with-microformats-part-2-xfn/</span></span></span><br />
<br />
== undated ==<br />
* [http://reference.sitepoint.com/html/xfn SitePoint reference: XFN] by Ian Lloyd<br />
<br />
== broken ==<br />
These articles have broken links - perhaps see if you can find them in http://archive.org and provide an archive.org link for them here:<br />
* <nowiki>http://www.centralityjournal.com/archives/xfn_bottomup_social_networks.html</nowiki> - XFN:bottom-up Social Networks by Stowe Boyd]<br />
<br />
== see also ==<br />
* [[hCalendar]]<br />
* [[articles]]<br />
* [[hcard-articles]]<br />
* [[hcalendar-articles]]<br />
* [[hreview-articles]]<br />
* [[xfn-articles]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=xfn&diff=70188xfn2020-07-18T16:35:17Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:XFN - The XHTML Friends Network}}<br />
<p class="entry-summary"><abbr title="XHTML Friends Network">XFN</abbr> is a simple way to represent human relationships using hyperlinks.</p><br />
<br />
The XFN specification and more information can be found at [http://www.gmpg.org/xfn/ GMPG.org].<br />
<br />
* [http://gmpg.org/xfn/ XFN home page]<br />
* [http://gmpg.org/xfn/intro introduction to XFN]<br />
* [http://gmpg.org/xfn/and/#idconsolidation XFN and identity consolidation with rel="me"]<br />
<br />
== articles ==<br />
This section is informative.<br />
<br />
See [[xfn-articles]].<br />
<br />
== related ==<br />
Some pages discussing XFN can be found on this wiki:<br />
<br />
{{xfn-related-pages}}<br />
<br />
[[Category:Specifications]]<br />
[[Category:XFN]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=x2v-fr&diff=70187x2v-fr2020-07-18T16:35:16Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:X2V}}<br />
[http://suda.co.uk/projects/X2V/ X2V] est une [[implementation-fr|implémentation]] [[microformats]] XSLT de [[User:Brian|Brian Suda]] qui [[parsers-fr|parse]] [[hcard-fr|hCard]] ou les événements [[hcalendar-fr|hCalendar]] dans le (X)HTML et les transforme respectivement dans des fichiers correspondants vCard (.vcf) ou iCalendar (.ics).<br />
<br />
Les dernières versions de développement en beta peuvent être testées sur <br />
* http://suda.co.uk/projects/X2V/<br />
** version 0.9.7 est la dernière version et elle supporte :<br />
** [[hcard-fr|hCard]] vers [[vcard-fr|vCard]]<br />
** [[hcalendar-fr|hCalendar]] vers [[icalendar-fr|iCalendar]]<br />
** [[value-class-pattern-fr|modèle de classe value]] (support presque complet de la séparation dates horaire, voir [[value-class-date-time-tests]])<br />
<br />
== feedback ==<br />
Demandes de fonctionnalités et autre feedback général.<br />
Quand cette section grossira, nous la migrerons sur [[x2v-feedback]].<br />
<br />
== problèmes ==<br />
Bugs ou autres problèmes apparents. Voir [[x2v-issues]].<br />
<br />
==instances hébergées==<br />
<br />
Si vous voulez simplement utiliser X2V hébergé sur le web, les sites suivants le font fonctionner : <br />
<br />
* [http://h2vx.com h2vx] est un service de transformation motorisé par X2V<br />
** http://h2vx.com/vcf/<br />
** http://h2vx.com/ics/<br />
** '''Statut :''' En ligne.<br />
* [[implementors-fr#Technorati|Technorati]] héberge un déploiement de X2V pour convertir les contacts hCard ou événements hCalendar sur <br />
** http://feeds.technorati.com/contacts/<br />
** http://feeds.technorati.com/events/<br />
** '''Statut :''' Interface utilisateur hors d'usage/404 depuis le redesign récent 2009-10 <br />
* La page de développement de Brian Suda dispose aussi d'une copie fonctionnelle : <br />
** http://suda.co.uk/projects/X2V/<br />
** '''Statut :''' les formulaires de transformation sont non fonctionnels à cette heure du fait d'une migration serveur 2009-09.<br />
<br />
== installation ==<br />
Si vous souhaitez faire tourner votre propre convertisseur X2V, soit pour vos propres contenus, ou comme service web général, vous devez d'abord récupérer : <br />
* les fichiers X2V XSLT (besoin de lien vers le téléchargement le plus récent)<br />
* le code X2V PHP (besoin de lien vers le téléchargement le plus récent)<br />
<br />
Puis de suivre ces instructions pour l'installer : <br />
# ... (à documenter)<br />
# ...<br />
<br />
== migré ==<br />
Un <span id="Test">test</span> dans la ligne a migré : [[value-dt-test-YYYY-MM-DD--HH-MM]], et s'est épanché dans un cas de test général pour le [[value-class-pattern-fr|modèle-de-classe-value]], l'un des nombreux [[value-class-date-time-tests|tests-value-class-date-time]].<br />
<br />
== voir aussi ==<br />
* [[hcard-fr|hCard]]<br />
* [[hcard-implementations-fr|hcard-implementations]]<br />
* [[vcard-implementations-fr|vcard-implementations]]<br />
* [[hcalendar-fr|hCalendar]]<br />
* [[hcalendar-implementations-fr|hcalendar-implementations]]<br />
* [[icalendar-implementations-fr|icalendar-implementations]]<br />
* [[implementations-fr|implementations]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=x2v&diff=70186x2v2020-07-18T16:35:15Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:X2V}}<br />
[http://suda.co.uk/projects/X2V/ X2V] is an open source [[microformats]] XSLT [[implementation]] by [[User:Brian|Brian Suda]] that [[parsers|parses]] [[hCard]] or [[hCalendar]] events in (X)HTML and transforms them into the corresponding vCard (.vcf) or iCalendar (.ics) file respectively.<br />
<br />
The latest beta and development versions of X2V can be tested at:<br />
* http://suda.co.uk/projects/X2V/<br />
** version 0.9.7 is the latest version, and it supports:<br />
** [[hCard]] to [[vCard]]<br />
** [[hCalendar]] to [[iCalendar]]<br />
** [[value-class-pattern]] (nearly complete support of dates time separation, see [[value-class-date-time-tests]])<br />
<br />
== feedback ==<br />
Feature requests and other general feedback.<br />
When this section grows to big we can move it to [[x2v-feedback]].<br />
<br />
== issues ==<br />
Bugs or other apparent problems. See [[x2v-issues]].<br />
<br />
==hosted instances==<br />
<br />
If you want to just use X2V hosted on the web, the following sites are running it:<br />
<br />
* [[H2VX]] is a transformer service powered by X2V<br />
** http://h2vx.com/vcf/ &amp; http://h2vx.com/ics/<br />
** beta/dev version: http://dev.h2vx.com/vcf/ &amp; http://dev.h2vx.com/ics/<br />
** '''Status:''' Up.<br />
* Brian Suda's development page has a running copy, too:<br />
** http://suda.co.uk/projects/X2V/<br />
** '''Status:''' transformation forms are non-functional currently due to a 2009-09 server move. No ETA on return.<br />
<br />
== install ==<br />
If you wish to run your own X2V converter, either for your own content, or as a general web service, you should fork and customize the [[h2vx]] service, which contains all necessary X2V XSLT files, PHP code, as well as H2VX web UI HTML+CSS+JS.<br />
* See [[h2vx]] for more.<br />
<br />
== moved ==<br />
One inline <span id="Test">test</span> moved to: [[value-dt-test-YYYY-MM-DD--HH-MM]], and expanded into a general test case for the [[value-class-pattern]], one of several [[value-class-date-time-tests]].<br />
<br />
== past instances ==<br />
The following instances of X2V used to exist but are no longer supported:<br />
* [[implementors#Technorati|Technorati]] hosted a deployment of X2V for converting hCard contacts or hCalendar events at:<br />
** <nowiki>http://feeds.technorati.com/contacts/</nowiki><br />
** <nowiki>http://feeds.technorati.com/events/</nowiki><br />
** '''Status:''' UI is down/404 since recent 2009-10 Technorati redesign - no ETA nor expected return. 2010-11: feeds.technorati.com conversion URLs themselves simple redirect to H2VX. 2012: feeds.technorati.com URLs 404.<br />
<br />
If you were using Technorati URLs for conversions, you should switch to [[H2VX]] URLs.<br />
<br />
== see also ==<br />
* [[H2VX]]<br />
* [[hCard]]<br />
* [[hcard-implementations]]<br />
* [[vcard-implementations]]<br />
* [[hCalendar]]<br />
* [[hcalendar-implementations]]<br />
* [[icalendar-implementations]]<br />
* [[implementations]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=work-of-art&diff=70185work-of-art2020-07-18T16:35:14Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:Work of Art}}<br />
<br />
Many art museums use metadata to describe the works of art in their collections. However, the presentation of works of art on the web often does not benefit from that formalized categorization work. We'd like to develop an xhtml markup standard for the presentation of works of art on the web.<br />
<br />
This page is an index for a community effort to create a work of art microformat.<br />
<br />
Per the microformats [[process]]:<br />
<br />
* [[workofart-examples]] (A list of existing (x)html markup examples for works of art.)<br />
* [[workofart-formats]] (A list of existing metadata formats works of art.)<br />
* [[workofart-brainstorming]] (A place to propose and discuss xhtml markup standards for works of art.)<br />
<br />
Please take a look, and contribute your thoughts and ideas.</div>Aaronpkhttp://microformats.org/wiki/index.php?title=wordpress-themes-fr&diff=70184wordpress-themes-fr2020-07-18T16:35:13Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:Thèmes WordPress Themes}}<br />
<br />
Ces thèmes intègrent la fonctionnalité microformat à [[WordPress-fr|WordPress]], une des nombreuses [[implementations-fr|implémentations]] microformats. Pour une liste toujours changeante des thèmes WordPress utilisant les microformats, voir les [http://wordpress.org/extend/themes/tags/microformats thèmes tagués microformats] sur WordPress.org.<br />
<br />
== K2 Theme ==<br />
<br />
* [http://www.getk2.com K2] utilise [[hatom-fr|hAtom]]+[[value-class-pattern-fr|modèle de classe value]], [[hcard-fr|hCard]], [[xfn-fr|XFN]], [[rel-tag-fr|Tag]] et [[xoxo-fr|XOXO]].<br />
<br />
== Thèmes Plaintxt.org ==<br />
* Tous les [http://www.plaintxt.org/themes/ plaintxt.org thèmes] ont le support intégré de [[hatom-fr|hAtom]], [[hcard-fr|hCard]] et [[xoxo-fr|XOXO]] : [http://www.plaintxt.org/themes/barthelme/ Barthelme], [http://www.plaintxt.org/themes/blogtxt/ blog.txt], [http://www.plaintxt.org/themes/plaintxtBlog/ plaintxtBlog], [http://www.plaintxt.org/themes/simplr/ Simplr], et [http://www.plaintxt.org/themes/veryplaintxt/ veryplaintxt]. Par [[implementors#Scott_Allan_Wallick|Scott Allan Wallick]].<br />
<br />
== PrimePress ==<br />
* [http://www.techtrot.com/primepress/ PrimePress] est un thème SEO qui implémente les microformats<br />
<br />
== Sandbox ==<br />
* [http://www.plaintxt.org/themes/sandbox/ Sandbox] est un thème Wordpress qui utilise [[hatom-fr|hAtom]], [[hcard-fr|hCard]] et [[xoxo-fr|XOXO]]. par [[implementors#Scott_Allan_Wallick|Scott Allan Wallick]].<br />
** Sandbox est aussi disponible pour les comptes hébergés sur le service d'hébergement <nomutilisateur>.wordpress.com.<br />
<br />
== StartPoint ==<br />
* [http://www.jesuscarrera.info/proyectos/startpoint/ StartPoint] est un thème pour les développeurs de thèmes. Un bon point de départ pour produire vos propres thèmes WordPress. Il supporte de nombreux langages et widgets, contient le microformat sémantique [[hatom-fr|hAtom]] et bien plus encore.<br />
<br />
== Strangelove ==<br />
* [http://www.whump.com/dropbox/Strangelove.zip Strangelove] est une modification du thème par défaut de WordPress (Kubrick) avec un support intégré de [[hatom-fr|hAtom]]. <br />
** Strangelove pointe vers le service de proxy hAtom2Atom comme lien pour les fils de syndication.<br />
<br />
== Thematic ==<br />
* [http://themeshaper.com/thematic-for-wordpress/ Thematic] est un thème de développement [[hatom-fr|hAtom]], optimisé pour utilisation avec des thèmes enfants et partiellement basé sur le thème Sandbox.<br />
<br />
== en rapport ==<br />
* Voir aussi les [http://wordpress.org/extend/themes/tags/microformats thèmes tagués microformats] sur WordPress.org.<br />
* [[wordpress-fr|wordpress]]<br />
* [[wordpress-plugins-fr|extensions wordpress]]<br />
* [[cms-fr|cms]]<br />
* [[implementations-fr|implémentations]]<br />
<br />
<br />
<br />
<br />
== Thèmes WP ==<br />
* [http://www.plaintxt.org/themes/barthelme/ Barthelme] est un thème pour Wordpress qui utilise [[hatom-fr|hAtom]] et [[hcard|hCard]]. <br />
* [http://www.plaintxt.org/themes/sandbox/ Sandbox] est un thème pour Wordpress qui utilise [[hatom-fr|hAtom]]. <br />
** Le thème est aussi disponible pour les comptes sur le service d'hébergement <nomutilisateur>.wordpress.com.<br />
* [http://www.jesuscarrera.info/proyectos/startpoint/ StartPoint] Un thème pour les développeurs de thèmes. Un bon point de départ pour produire vos propres gabarits. Il supporte plusieurs langues, les widgets, contient les microformats sémantiques hAtom, et plus encore.<br />
* [http://www.whump.com/dropbox/Strangelove.zip Strangelove] est une modification du thème Wordpress par défaut (Kubrick) avec le support [[hatom-fr|hAtom]]. <br />
** Il pointe vers le service proxy hAtom2Atom comme le lien pour les fils de syndication.</div>Aaronpkhttp://microformats.org/wiki/index.php?title=wordpress-plugins-fr&diff=70183wordpress-plugins-fr2020-07-18T16:35:13Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:Extensions WordPress}}<br />
<br />
Ces extensions ajoutent la fonctionnalité [[microformats-fr|microformats]] à [[WordPress-fr|WordPress]], une des nombreuses [[implementations-fr|implémentations]] microformats. Pour une liste toujours changeante des extensions Wordpress utilisant les microformats, voir [http://wordpress.org/extend/plugins/tags/microformats les extensions taguées microformats] sur WordPress.org.<br />
<br />
==Blog Summary==<br />
L'extension [http://www.plaintxt.org/experiments/blog-summary/ Blog Summary] produit une liste personnalisable [[hatom-fr|hAtom]] [[xoxo-fr|XOXO]] des derniers billets via code raccourci <code>[</code><code>blog-summary</code><code>]</code>. Par [[implementors#Scott_Allan_Wallick|Scott Allan Wallick]].<br />
<br />
===GigPress===<br />
[http://gigpress.com/ GigPress] est une extension WordPress qui gère et affice les concerts et tournées pour les groupes ou autres opérations de tours, et les affiche avec un marquage [[hcalendar-fr|hCalendar]]. Par [[implementors-fr#Derek_Hogue|Derek Hogue]].<br />
<br />
===hAvatar===<br />
Affiche les avatars pour les commentateurs en se fondant sur les hCards sur l'URL qu'ils laissent derrière.<br />
<br />
Essayez la [http://wordpresstest.aardverschuiving.com/2_3_1/?p=1 page Test] ou [http://files.fourstarters.com/havatar-0.3.zip téléchargez la version: 0.3] (dernière en date au 2008-02-09).<br />
<br />
Vérifiez en saisissant : <code>hg clone static-http://alper.nl/hg/havatar/</code><br />
<br />
Regardez [http://fourstarters.com/2008/01/20/havatar-wordpress-plugin/ l'annonce initiale] et [http://fourstarters.com/2008/02/09/havatar-updated-version-03/ l'annonce de mise à jour], et les problèmes connus dans le [http://alper.nl/hg/havatar/README README].<br />
<br />
=== Boîte hCard About ===<br />
* Le widget [http://redmonk.net/projects/widget_hcard_about/ hCard About Box] par [[implementors-fr#Steve_Ivy|Steve Ivy]] supporte [[hcard-fr|hCard]].<br />
<br />
== hCard Commenting ==<br />
* L'extension WP [http://notizblog.org/projects/wp-hcard-commenting/ hCard Commenting] par [[implementors#Matthias_Pfefferle|Matthias Pfefferle]] permet aux visiteurs de remplir facilement les formulaires de commentaires en utilisant une hCard.<br />
<br />
=== Microformatted Blogroll ===<br />
* L'extension Wordpress [http://factorycity.net/projects/wp-microformatted-blogroll/ WP Microformatted Blogroll 0.2] par [[implementors-fr#Chris_Messina|Chris Messina]] supporte [[hcard-fr|hCard]] et [http://gmpg.org/xfn/ XFN].<br />
<br />
=== Save Microformats Plugin ===<br />
* [http://notizblog.org/projects/save-microformats/ Extension Save Microformats pour Wordpress] - une extension pour sauvegarder les Microformats postés en utilisant les fils technorati. par [[implementors-fr#Matthias_Pfefferle|Matthias Pfefferle]]<br />
<br />
=== VoteBack ===<br />
* L'[http://redmonk.net/archives/2006/12/21/voteback/ extension VoteBack pour Wordpress] par [[implementors-fr#Steve_Ivy|Steve Ivy]] vérifie les pingbacks entrants et trackbacks pour les [[votelinks-fr|votelinks]].<br />
<br />
== rel-me publishing ==<br />
Les extensions qui implémentent la publication de liens [[rel-me-fr|rel-me]] vers d'autres services et profils :<br />
* [http://blog.maybe5.com/?page_id=94 Extension WordPress Social Links] - supporte les liens rel-me vers d'autres services<br />
* [http://code.l0g.in/about-me/ About Me plugin] (on github) - supporte la création d'une page "About Me" avec des liens rel-me vers d'autres profils.<br />
<br />
== Extensions TinyMCE ==<br />
Si vous utilisez l'extension TinyMCE, envisagez aussi d'installer ce qui suit : <br />
* '''TinyMCE hCard''' (was at <nowiki>http://www.undergroundwebdesigns.com/tinyMCE-hcard-plugin.html</nowiki>) - ajoute une icône [http://www.undergroundwebdesigns.com/assets/images/hcard_button.gif] dans votre barre d'outils tinyMCE qui fournit un formulaire pour créer un contact hCard.<br />
* '''TinyMCE hCalendar''' (was at <nowiki>http://www.undergroundwebdesigns.com/tinyMCE-hcalendar-plugin.html</nowiki>) - ajoute une nouvelle icône [http://www.undergroundwebdesigns.com/assets/images/calendar_button.gif] dans votre barre d'outils tinyMCE qui fournit un formulaire pour créer un événement hCalendar.<br />
Voir aussi [http://undergroundwebdesigns.com/blog/how-to-use-the-tinymce-hcalendar-and-hcard-plugins-with-modx les instructions pour installer ces extensions TinyMCE en modx] ([http://twitter.com/alx4god17/statuses/856692032 tweeted]).<br />
<br />
== en rapport==<br />
* Voir les [http://wordpress.org/extend/plugins/tags/microformats extensions taguées '''microformats'''] sur le répertoire officiel WordPress pour en avoir plus.<br />
* [[wordpress-fr|wordpress]]<br />
* [[wordpress-themes-fr|wordpress-themes]]<br />
* [[cms-fr|cms]]<br />
* [[implementations-fr|implémentations]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=wordpress-plugins&diff=70182wordpress-plugins2020-07-18T16:35:12Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:WordPress Plugins}}<br />
<br />
These plugins add [[microformats]] functionality to [[WordPress]], one of several microformats [[implementations]]. For an ever-changing list of WordPress plugins utilizing microformats, [http://wordpress.org/extend/plugins/tags/microformats see plugins tagged microformats] on WordPress.org.<br />
<br />
==Blog Summary==<br />
The [http://www.plaintxt.org/experiments/blog-summary/ Blog Summary] plugin produces a customizable, [[hatom|hAtom]]-enabled [[xoxo|XOXO]]-friendly list of recent posts via the shortcode <code>[</code><code>blog-summary</code><code>]</code>. By [[implementors#Scott_Allan_Wallick|Scott Allan Wallick]].<br />
<br />
==GigPress==<br />
[http://gigpress.com/ GigPress] is a WordPress plugin that manages and displays concerts and tours for bands or other touring acts, and outputs them with [[hcalendar|hCalendar]] markup. By [[implementors#Derek_Hogue|Derek Hogue]]<br />
<br />
==hAvatar==<br />
Displays avatars for commenters based on the hCards on the URL they leave behind.<br />
<br />
Try the [http://wordpresstest.aardverschuiving.com/2_3_1/?p=1 Test page] or [http://files.fourstarters.com/havatar-0.3.zip download version: 0.3] (latest at 2008-02-09).<br />
<br />
Test hAvatar by typing: <code>hg clone static-http://alper.nl/hg/havatar/</code><br />
<br />
See the [http://fourstarters.com/2008/01/20/havatar-wordpress-plugin/ initial announcement] and [http://fourstarters.com/2008/02/09/havatar-updated-version-03/ update announcement], and the known issues in the [http://alper.nl/hg/havatar/README README].<br />
<br />
== hCard About Box ==<br />
* The [http://redmonk.net/projects/widget_hcard_about/ hCard About Box] widget by [[implementors#Steve_Ivy|Steve Ivy]] supports [[hcard|hCard]].<br />
<br />
== hCard Addressbook ==<br />
* [http://wordpress.org/extend/plugins/addressbook/ Wordpress Addressbook plugin] - Display list of addresses from the blog owner's address book, each marked up as an hCard. Maintained by [http://samwilson.id.au Sam Wilson].<br />
<br />
== hCard Commenting ==<br />
* The [http://notizblog.org/projects/wp-hcard-commenting/ hCard Commenting] WordPress plugin by [[implementors#Matthias_Pfefferle|Matthias Pfefferle]] allows visitors to easily fill out the comment forms using an hCard.<br />
<br />
== hCard vCard Generator ==<br />
* [http://www.codemyownroad.com/products/hcard-vcard-generator-wordpress-plugin/ hCard & vCard Generator plugin for WordPress] - Generate microformat compatible hCards and vCards for WordPress users - great for use on staff pages and for user bio's.<br />
<br />
== hReview Support for Editor ==<br />
* The [http://wordpress.org/extend/plugins/hreview-support-for-editor/ hReview Support for Editor] plugin by Andrew E Scott allows bloggers to easily publish hReview enabled reviews.<br />
<br />
== Microformatted Blogroll ==<br />
* The [http://factorycity.net/projects/wp-microformatted-blogroll/ WP Microformatted Blogroll 0.2] Wordpress plugin by [[implementors#Chris_Messina|Chris Messina]] supports [[hcard|hCard]] and [http://gmpg.org/xfn/ XFN].<br />
<br />
== Save Microformats Plugin ==<br />
* [http://notizblog.org/projects/save-microformats/ Save Microformats plugin for Wordpress] - a plugin by [[implementors#Matthias_Pfefferle|Matthias Pfefferle]] to save posted Microformats using technorati feeds.<br />
<br />
== VoteBack ==<br />
* The [http://redmonk.net/archives/2006/12/21/voteback/ VoteBack plugin for Wordpress] by [[implementors#Steve_Ivy|Steve Ivy]] checks incoming pingbacks and trackbacks for [[votelinks]].<br />
<br />
== rel-me publishing ==<br />
Plugins that implement publishing [[rel-me]] links to other services and profiles:<br />
* [http://blog.maybe5.com/?page_id=94 Social Links Wordpress plugin] - supports rel-me links to other services<br />
* [http://code.l0g.in/about-me/ About Me plugin] (on github) - supports creation of an About Me page with rel-me links to other profiles.<br />
<br />
== MicroAnywhere ==<br />
Adds two buttons to the TinyMCE editor in wordpress that allow for the creation of hCard and hCalendar objects embeded in posts, pages etc. <br />
* [http://wordpress.org/plugins/micro-anywhere/ MicroAnywhere on Wordpress.org]<br />
* [https://github.com/undergroundwebdesigns/microanywhere Open sourced on GitHub]<br />
<br />
== hNews ==<br />
<br />
* The [http://wordpress.org/extend/plugins/hnews-for-wordpress/ hnews-for-wordpress] plugin by themattharris and Ben Campbell. And a basic [http://valueaddednews.org/technical/hnews-for-wordpress HOWTO].<br />
<br />
== hCard Widget ==<br />
* The [http://lautman.ca/hcard-wordpress-widget/ hCard Wordpress Widget] plugin adds a widget to display contact information in accordance with hCard microformats standard. Ideal for use in a widgetized footer. Plugin by [http://twitter.com/michaellautman @michaellautman]<br />
<br />
== related ==<br />
* See [http://wordpress.org/extend/plugins/tags/microformats plugins tagged '''microformats'''] on the official WordPress plugin repository for more.<br />
* [[wordpress]]<br />
* [[wordpress-themes]]<br />
* [[cms]]<br />
* [[implementations]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=wordpress&diff=70181wordpress2020-07-18T16:35:12Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:WordPress}}<br />
<br />
One of several microformats [[implementations]].<br />
WordPress is an [http://wordpress.org/ open source blogging tool], that has been more broadly described as a "state-of-the-art publishing platform" and a content management system ([[cms]]).<br />
<br />
== Adding Microformats Support to WordPress ==<br />
<br />
===builtin===<br />
Become familiar with existing WordPress support for microformats.<br />
* [http://wordpress.org WordPress] supports [[xfn|XFN]] blogrolls through a built-in user interface. (cf. [[xfn-implementations]]) <br />
** by [[implementors#Matt_Mullenweg|Matt Mullenweg]] and friends<br />
<br />
=== themes ===<br />
Use one of the numerous a microformats-powered [[wordpress-themes]], such as:<br />
* '''[http://www.plaintxt.org/themes/sandbox/ Sandbox theme]''' and Sandbox-based themes include [[hatom|hAtom]], [[hcard|hCard]], and [[xoxo|XOXO]]. By [[implementors#Scott_Allan_Wallick|Scott Allan Wallick]].<br />
See [[wordpress-themes]] for more.<br />
<br />
=== plugins ===<br />
{{main|wordpress-plugins}}<br />
Use microformats-enabling [[wordpress-plugins]], such as:<br />
* '''[http://wordpress.org/extend/plugins/hreview-support-for-editor/ hReview Support for Editor]''' to easily publish hReview enabled reviews. By Andrew E Scott.<br />
* '''[http://www.plaintxt.org/experiments/blog-summary/ Blog Summary]''' to produce an hAtom-enabled list of recent entries via shortcode. By [[implementors#Scott_Allan_Wallick|Scott Allan Wallick]].<br />
See [[wordpress-plugins]] for more.<br />
<br />
=== blog posts ===<br />
* 2006-09-12 [http://microformats.org/blog/2006/09/12/publishing-microformats-in-wordpress/ microformats blog: Publishing Microformats in Wordpress]<br />
<br />
== related ==<br />
* [[wordpress-themes]]<br />
* [[wordpress-plugins]]<br />
* [[cms]] ([[movable-type]])<br />
* [[implementations]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=wiki-better-than-email-fr&diff=70180wiki-better-than-email-fr2020-07-18T16:35:09Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:Wiki is better than email}} <br />
<br />
Le wiki fonctionne mieux que l'e-mail pour le contenu (exemples, problématiques, brainstorm, etc.) pour bon nombre de raisons.<br />
<br />
<br />
== wikis en langage clair (anglais) ==<br />
Voici une vidéo courte résumant comment les wikis fonctionnent mieux que l'e-mail pour la collaboration, même pour quelque chose d'aussi simple que d'organiser un voyage en camping.<br />
<br />
[http://www.youtube.com/watch?v=-dnL00TdmLY http://i2.ytimg.com/vi/-dnL00TdmLY/default.jpg][http://www.youtube.com/watch?v=-dnL00TdmLY YouTube: Wikis in Plain English]<br />
<br />
== raisons ==<br />
Voici quelques raisons pour lesquelles les wikis fonctionnent mieux que l'e-mail pour les microformats en particulier, et en fait, pour tout type de développement de standards ouverts.<br />
<br />
* <span id="scaling-fr">'''rapport signal bruit.'''</span> Tout le monde n'est pas intéressé par chaque problématique sur chaque format.<br />
* <span id="efficiency-fr">'''efficacité : lire l'état actuel vs deltas.'''</span> Vous pouvez lire une page wiki pour avoir le statut/fil de discussion sur une problématique tandis qu'avec les emails, vous devez souvent lire de nombreux emails (et fils de discussions) et les appliquer comme des deltas/diffs dans votre tête pour comprendre où s'est terminée la problématique, etc.<br />
* <span id="search-fr">'''recherche.'''</span> la recherche sur le web/wikis fonctionne bien mieux en pratique que la recherche dans les listes de discussions (la recherche web sur les archives d'emails n'a par exemple pas de recherche sur les fils).<br />
* <span id="pd">'''domaine public.'''</span> les contributions wiki sont requises pour être dans le domaine public, alors que dans l'email il n'existe pas d'interface-utilisateur pour renforcer ça, de ce fait l'email devrait être utilisé uniquement "informaivement" pour les notifications et jamais pour le contenus à comprendre de quelque substance.<br />
* <span id="tradition">'''tradition.'''</span> les microformats ont été documentés sur un wiki depuis leur inception, en tant que résultat le wiki est la ressource définitive pour tout ce qui concerne les microforamts ; pas du tout sur les listes de discussion. La communauté a une tradition de longue date préférant l'utilisation du wiki pour le contenu. Nous réalisons que c'est tout à fait nouveau pour une communauté de standards, du fait que la plupart des communautés de standards sont centrées sur l'email (par ex. W3C, IETF). Néanmoins pour toutes les raisons présentées au-dessus, nous croyons qu'utiliser les wikis pour le contenu est bien supérieur à l'email et de ce fait, espérons que les autres communautés de standards basculeront plus leurs activités pour être basées sur web/wiki plutôt que sur des listes de discussion.<br />
<br />
<div class="discussion"><br />
* note historique : les microformats ont toujours été développés via IRC public + wiki depuis 2004 quand Kevin Marks et Tantek Çelik ont commencé initialement à chercher/brainstormer/ébaucher les microformats tels que [[rel-license-fr|rel-license]], [[vote-links-fr|vote-links]], [[xoxo-fr|XOXO]], [[hcard-fr|hCard]], [[hcalendar-fr|hCalendar]] sur le Wiki des Développeurs de Technorati. et le réseau IRC Freenode. Brian Suda a découvert en quelque sorte la page hCard sur le wiki des développeurs de Technorati, a commencé à la modifier, et c'est comme ça qu'ils se sont rencontrés avec Tantek Çelik. Les [[mailing-lists-fr|listes de discussion]] n'étaient pas créées jusqu'à ce que le site microformats.org se lance mi 2005 et elles ont toujours été considérées comme secondaires au wiki et au canal IRC.<br />
** exception : hAudio fût développé essentiellement à travers des éditions via e-mail et wiki. -- [[User:ManuSporny|ManuSporny]] 03:37, 28 février 2009 (UTC)<br />
*** Avec du recul, autoriser cela était probablement une erreur, parce qu'il y a eu bien trop d'emails sur le sujet de hAudio de ma part et de bien d'autres pour le hisser, et beaucoup de questions ont été résolues avec peu de profondeur de discussion (seulement 1-2 participants, typiquement Manu et Martin). A l'avenir en tant que communauté, nous devrions insister que toutes les problématiques soient enregistrées sur le wiki, et que toutes les opinions sur les problématiques spécifiques soient saisies sur le wiki, de manière à ce que cette information ne soit pas perdue dans l'e-mail.[[User:Tantek|Tantek]] 21:23, 15 June 2009 (UTC)<br />
</div><br />
<br />
== documentation supplémentaire ==<br />
* Voir le livre http://www.wikinomics.com/ pour plus de détails et explications sur les raisons pour lesquelles les wikis sont plus efficaces que l'e-mail pour une variété de workflows.<br />
* Cette image aide à illustrer un des nombreux scénarios - et même si nous n'envoyons pas de documents word, le point est que le contenu itéré à travers l'email est bien moins efficace qu'itérer du contenu sur un wiki : <br /> [http://www.wikinomics.com/blog/index.php/2008/03/26/wiki-collaboration-leads-to-happiness/ http://www.wikinomics.com/blog/uploads/wiki_collaboration2.jpg]<br />
<br />
== FAQ ==<br />
=== quel est le meilleur moyen de comprendre et résoudre les problématiques ===<br />
''What is the best way to capture and resolve issues through broad consensus?''<br />
<br />
# First check the relevant *-issues page, and if available, the corresponding *-issues-resolved page.<br />
# [[IRC]] can be useful for quickly discovering whether something is an issue or not.<br />
# If you cannot find the answer to an issue by searching, and asking in IRC, then ask a short message on the microformats-discuss list, and mention specifically the relevant *-issues wiki page where you didn't find the issue.<br />
# If it appears you have a new issue, capture it on the appropriate *-issues page.<br />
# If you have an opinion about an existing issue, add a nested list item to the existing issue and a "+1" or "0" or "-1" signifying your approval/ambivalence/disapproval, sign your name with <nowiki>~~~~</nowiki>, and optionally provide reasons for your opinion.<br />
<br />
The wiki, being on the Web and much more easily discoverable, reaches far more people than any email list or the IRC channel. Wiki pages are also much more readable as a summary of opinions, than having to wade through email threads trying to determine who is for/neutral/against any particular issue.<br />
<br />
<div class="discussion"><br />
* Thus the wiki is the best choice for documenting a range of opinions, and archiving discussions that lead to consensus.<br />
** -1 I'm not arguing for an all-or-nothing approach. I think we should discuss on IRC/e-mail, form a consensus of some kind, and then record that consensus on the wiki. The community should allow people to use whatever method works for them, rather than forcing a method of communication and issue resolution onto the community. -- [[User:ManuSporny|ManuSporny]] 03:22, 28 February 2009 (UTC)<br />
*** This reasoning is flawed for multiple reasons: [[User:Tantek|Tantek]] 21:23, 15 June 2009 (UTC)<br />
**** '''Different opinions should be captured on the wiki, not just consensus.''' If you only capture consensus, then others with different opinions that come along later will simply restate those different opinions and then the community will waste time arguing the same arguments again. IRC/Email is insufficient for discussion.<br />
**** '''Consensus should arise from expression of opinions on the wiki via +1/0/-1 subpoints.''' If you only capture +1/0/-1 opinions in email, those discussions are inevitably lost in email archives, difficult to find, and difficult to show that consensus actually occured.<br />
**** '''People can communicate informally using whatever method works for them.''' Formal issue capturing/discussion/resolution takes place on the wiki.<br />
**** '''In order to actually keep a community a ''community'', we have to converge on certain methods and practices.''' Issue capturing, discussion, and resolution is one such practice.<br />
</div><br />
<br />
=== et si je ne peux pas trouver les problématiques sur le wiki ===<br />
''What should I do if I cannot find issues on the wiki?''<br />
<br />
''I find it difficult to understand the arguments behind a large number of the items on the Microformats wiki.'' -- [[User:ManuSporny|ManuSporny]] 03:22, 28 February 2009 (UTC)''<br />
<br />
* If a simple search of the wiki fails to quickly reveal an answer to an issue, then ask in the [[IRC]] channel or on an email list as noted in the previous FAQ. <br />
* Responses to such queries should include URLs to answers on the wiki, hopefully with improved discoverability to increase findability of similar issues in the future.<br />
<br />
=== pourquoi l'IRC est mieux que l'email ===<br />
''Why is IRC okay, but e-mail not okay? [[User:ManuSporny|ManuSporny]] 03:22, 28 February 2009 (UTC)''<br />
<br />
# People can easily choose to be on IRC or not when it is convenient for them to participate in discussions or not and that aspect of easy in/out control is very important. Email on the other hand, is much more cumbersome to subscribe/unsubscribe when you have time to handle discussions or don't. <br />
# In IRC, if a participant has a misconception, others in the channel can quickly correct that participant, rather than the participant waste a lot of time with writing something up that is based on that misconception. In email OTOH, a mistaken assumption in the start of an email can lead to the author wasting time writing paragraphs upon paragraphs dependent on that bad assumption.<br />
<br />
=== et si je n'ai pas le temps d'être sur l'IRC ===<br />
''What if I don't have time to be on IRC?''<br />
<br />
''I do not have the time to sit around in an IRC channel. -- [[User:ManuSporny|ManuSporny]] 03:22, 28 February 2009 (UTC)''<br />
<br />
''I need an asynchronous method of communication and IRC doesn't work for me. -- [[User:ManuSporny|ManuSporny]] 03:22, 28 February 2009 (UTC)''<br />
<br />
* If you do not have time to be on IRC or want an asynchronous method of communication, you may check the [[IRC]] archives at your convenience.<br />
<br />
=== et si je préfère faire ma communication dans des batches ===<br />
''What if I prefer to do my communication in batches?''<br />
<br />
''I do my communication in batches because that is most efficient for me. -- [[User:ManuSporny|ManuSporny]] 03:22, 28 February 2009 (UTC)''<br />
<br />
* If you prefer to do your communication in batches, simply check the [[IRC]] archives, write up simple short follow-ups with references to specific IRC archive permalinks, and paste them into IRC at your convenience.<br />
<br />
=== comment m'assurer que je ne rate rien sur l'IRC ===<br />
''How do I make sure that I don't miss something in IRC?''<br />
<br />
''I can shut off my e-mail client and not worry that I've missed something, I can't necessarily do the same with IRC. -- [[User:ManuSporny|ManuSporny]] 03:22, 28 February 2009 (UTC)''<br />
<br />
* You can check the [[IRC]] archives, since the last time you checked the IRC archives, and thus make sure that you don't miss anything without having to be on IRC at all times.<br />
<br />
=== et si quelqu'un démarre une guerre de modifications sur une question ===<br />
''What if someone starts an edit war on an issue?''<br />
<br />
''Edit wars lead to subsequent banning of individuals, as this community has experienced. -- [[User:ManuSporny|ManuSporny]] 03:22, 28 February 2009 (UTC)''<br />
<br />
If someone:<br />
* does a revert without any explanation or follow-up explanatory edit, or<br />
* undoes a revert without any follow-up to an explanation, or<br />
* simply repeats an edit, ignoring previous edit explanations<br />
<br />
Please contact one or more of the [[admins]] either on IRC (preferably) or via email, alerting them and providing URL(s) to the problematic edits on the wiki.<br />
<br />
The admins will follow-up by correcting the wiki.<br />
<br />
Such behavior that is disruptive to the community will not be tolerated.<br />
<br />
If the individual persists in an edit war, especially after one of the admins have stepped in, the admins will warn and then ban the individual for progressively longer ban times as necessary.<br />
<br />
=== de quelle façon le wiki est mieux pour les questions à controverse ===<br />
''How is the wiki better for controversial issues?''<br />
<br />
* All issues, whether controversial or not, are better captured on a wiki for future documentation, with permalinks to reduce the probability that the same issue is re-raised (since the previous issue and resolution can be easily referenced by permalink, and often better discovered by search.)<br />
<br />
* If it seems like differences of opinion on an issue are unresolvable, then a wiki can serve to summarize opinions one way or the other (via +1 / -1 / 0 {username} surveys) so that at least the controversy can be recorded rather than incessant "email-ping-pong" where emails simply just go back and forth and no progress is made.<br />
<br />
* In comparison, e-mail does not allow for broad consensus, only the illusion thereof. The problem is that the overwhelming amount of email noise (on issues or formats they may not be interested in) typically results in people simply paying less attention and eventually leaving the mailing lists. [[logical-flaws#Absence_of_objections_is_not_approval|Absence of response is not an indicator of agreement]] or certainly not consensus. Much better to capture the actual issues/responses/opinions on the wiki and not flood the mailing lists.<br />
<br />
=== qu'est-ce qui différencie la communauté microformats des communautés précédentes des standards ===<br />
<br />
''How is the microformats community different from previous standards communities?''<br />
<br />
* The microformats community started with the wiki as central practice, and other methods (including IRC) as merely notification or for very brief discussions that if meaningful were captured on the wiki. <br />
* In comparison the email-centric discussions in other standards communities (e.g. W3C, IETF) has long been overwhelmed by trolls and other bad actors (e.g. www-style and www-html mailing lists) thus significantly reducing both the utility of such lists, and the desire for people of any level of expertise to actually attempt to participate.<br />
<br />
As [http://www.paulgraham.com/trolls.html Paul Graham wrote]:<br />
<blockquote><p>There's a sort of Gresham's Law of trolls: trolls are willing to use a forum with a lot of thoughtful people in it, but thoughtful people aren't willing to use a forum with a lot of trolls in it. Which means that once trolling takes hold, it tends to become the dominant culture.</p></blockquote><br />
<br />
<br />
=== comment le wiki peut améliorer l'objectivité et le sentiment de camaraderie ===<br />
''How can the wiki improve objectivity and friendliness?'''<br />
<br />
<div class="discussion"><br />
* The wiki is a vital documentation tool, and we should strive that it be written as a quality piece of documentation of issues and specs. --[[User:BenWard|BenWard]] 23:32, 28 February 2009 (UTC)<br />
** +1 [[User:Tantek|Tantek]] 21:23, 15 June 2009 (UTC)<br />
* In forcing discussion into this format, discussion is blunted, becomes harsh and naturally gravitates toward polarized discussion. This is important for documenting the issue; to distill issues to their core, but this is bad for building friendly, amicable relationships between people trying to work together on microformats. --[[User:BenWard|BenWard]] 23:32, 28 February 2009 (UTC)<br />
** We should encourage neutral/objective documentation of issues, and editing of issues to remove emotional content that could be interpreted as hostile or unfriendly. [[User:Tantek|Tantek]] 21:23, 15 June 2009 (UTC)<br />
** In addition, as [[admins]] we should act quickly to warn and ban individuals who are abusive on the wiki (see above about edit wars). [[User:Tantek|Tantek]] 21:23, 15 June 2009 (UTC)<br />
** On the side of friendliness, we should reach out to and contact new editors over IRC and email as necessary to help familiarize them with [[how-to-play]] and the [[mailing-list]] guidelines. [[User:Tantek|Tantek]] 21:23, 15 June 2009 (UTC)<br />
</div><br />
<br />
== en rapport ==<br />
* [[mailing-lists-fr|listes de discussion]]<br />
* [[how-to-play-fr|comment jouer]]<br />
* [[put-it-on-the-wiki-fr|posez-le-sur-wiki]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=wiki-better-than-email&diff=70179wiki-better-than-email2020-07-18T16:35:08Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:Wiki is better than email}} <br />
<br />
The wiki works better than email for content (examples, issues, brainstorms etc.) for numerous reasons. <br />
<br />
;short URL<br />
:http://ufs.cc/w/wikibetter<br />
<br />
== wikis in plain english ==<br />
Here is a short video explaining how wikis work much better than email for collaboration, even for something as simple as planning a camping trip.<br />
<br />
[http://www.youtube.com/watch?v=-dnL00TdmLY http://i2.ytimg.com/vi/-dnL00TdmLY/default.jpg][http://www.youtube.com/watch?v=-dnL00TdmLY YouTube: Wikis in Plain English]<br />
<br />
== reasons ==<br />
Here are some reasons why wikis work better than email for microformats in particular, and in fact, for any kind of open standards development.<br />
<br />
* <span id="scaling">'''signal-to-noise scaling.'''</span> Not everyone is interested in every issue on every format (feature, topic, etc.).<br />
* <span id="efficiency">'''efficiency: reading current state vs deltas.'''</span> You can read one wiki page to get the status/thread of an issue whereas with emails you often have to read thru numerous emails (and threads) and apply them like deltas/diffs in your head to understand where an issue etc. ended up.<br />
* <span id="search">'''search/discoverability.'''</span> search for the web/wikis works much better in practice than searching mailing lists (web search of email archives has no thread-smarts for example).<br />
* <span id="pd">'''public domain.'''</span> Wiki contributions are required public domain, while in email there is no UI to enforce this, thus email should be use only "informatively" for notifications and never for capturing material of any substance.<br />
* <span id="tradition">'''tradition.'''</span> microformats have been documented on a wiki since their inception, as a result the wiki is the definitive resource for all matters microformats; not any of the mailing lists. The community has had a longstanding tradition preferring use of the wiki for content over email. We realize this is fairly novel for a standards community, as most standards communities are email-centric (e.g. W3C, IETF). However, for all the above reasons we believe using wikis for content is far superior to email and thus hope that other standards communities shift more of their activities to being web/wiki-based rather than email lists. See [[#historical_note]] for more on this.<br />
<br />
== additional documentation ==<br />
* See the book http://www.wikinomics.com/ for more details and explanations on how wikis are more efficient than email for a variety of workflows.<br />
* This picture helps illustrate one of many scenarios - and though we are not sending word documents, the point is, that iterating content through email is far less efficient than iterating content on a wiki: <br /> [http://www.wikinomics.com/blog/index.php/2008/03/26/wiki-collaboration-leads-to-happiness/ http://www.wikinomics.com/blog/uploads/wiki_collaboration2.jpg]<br />
<br />
== FAQ ==<br />
=== what is the best way to capture and resolve issues ===<br />
''What is the best way to capture and resolve issues through broad consensus?''<br />
<br />
# First check the relevant *-issues page, and if available, the corresponding *-issues-resolved page.<br />
# [[IRC]] can be useful for quickly discovering whether something is an issue or not.<br />
# If you cannot find the answer to an issue by searching, and asking in IRC, then ask a short message on the microformats-discuss list, and mention specifically the relevant *-issues wiki page where you didn't find the issue.<br />
# If it appears you have a new issue, capture it on the appropriate *-issues page.<br />
# If you have an opinion about an existing issue, add a nested list item to the existing issue and a "+1" or "0" or "-1" signifying your approval/ambivalence/disapproval, sign your name with <nowiki>~~~~</nowiki>, and optionally provide reasons for your opinion.<br />
<br />
The wiki, being on the Web and much more easily discoverable, reaches far more people than any email list or the IRC channel. Wiki pages are also much more readable as a summary of opinions, than having to wade through email threads trying to determine who is for/neutral/against any particular issue.<br />
<br />
Thus the wiki is the best choice for documenting a range of opinions, and archiving discussions that lead to consensus.<br />
<br />
<br />
=== should we only capture consensus on the wiki ===<br />
''Should we first discuss on IRC/e-mail, form a consensus of some kind, and then record that consensus on the wiki?''<br />
<br />
No. It is important to capture more than just consensus on the wiki (in appropriately structured ways).<br />
<br />
* '''Different opinions should be captured on the wiki, not just consensus.''' If you only capture consensus, then others with different opinions that come along later will simply restate those different opinions and then the community will waste time arguing the same arguments again. IRC/Email is insufficient for discussion.<br />
* '''Consensus should arise from expression of opinions on the wiki via +1/0/-1 subpoints.''' If you only capture +1/0/-1 opinions in email, those discussions are inevitably lost in email archives, difficult to find, and difficult to show that consensus actually occured.<br />
* '''People can communicate informally using whatever method works for them.''' Formal issue capturing/discussion/resolution takes place on the wiki.<br />
* '''In order to actually keep a community a ''community'', we have to converge on certain methods and practices.''' Issue capturing, discussion, and resolution is one such practice, and doing so on the wiki provides better community memory and continuity.<br />
<br />
<br />
=== what if I cannot find issues on the wiki ===<br />
''What should I do if I cannot find issues on the wiki?''<br />
<br />
''I find it difficult to understand the arguments behind a large number of the items on the Microformats wiki.'' -- [[User:ManuSporny|ManuSporny]] 03:22, 28 February 2009 (UTC)''<br />
<br />
* If a simple search of the wiki fails to quickly reveal an answer to an issue, then ask in the [[IRC]] channel or on an email list as noted in the previous FAQ. <br />
* Responses to such queries should include URLs to answers on the wiki, hopefully with improved discoverability to increase findability of similar issues in the future.<br />
<br />
<br />
=== why do IRC and email lists repeat conversations ===<br />
''Why do IRC channels and email lists repeat conversations, e.g. conversations about wikis and emails?''<br />
<br />
The very mediums of IRC and email tend to cause forgetting the past (preferring brief summary statements to actual search/citation) and thus inevitably repeating conversations, including repeating errant statements (see: every email list), unless briefly (and repeatedly) corrected with URLs to answers (like this one).<br />
<br />
<br />
=== how do wikis reduce duplication of discussions ===<br />
''How can we, and why do we use the wiki to reduce duplication of discussions?''<br />
<br />
If a community uses only or primarily email for discussions, then discussions are duplicated/repeated over and over because new folks show up and are unable to search/find previous discussions. Or sometimes even folks on a list for a long time will repeat themselves because they'll forget the past.<br />
<br />
By putting substantial content (problem statements, use-cases, research, discussions thereabout) on the wiki, we can reduce and hopefully minimize duplication by using URLs to the wiki instead.<br />
<br />
Even if content is first sent or found in email, by copying / simplifying it to a place on the wiki, citing it by URL provides a much more discoverable (and updateable) place for discussion and avoids (or at least reduces) subsequent duplication of discussions.<br />
<br />
<br />
=== will anyone see stuff on the wiki ===<br />
''Will anyone see stuff on the wiki?''<br />
<br />
The short answer is yes, people will see stuff on the wiki because:<br />
* Wikis show-up ''much'' better in web searches than email (or IRC) archives, and web searching is how most people find and see most things on the web.<br />
<br />
Problems with other methods:<br />
* Very few see content on email lists (or even IRC or Twitter) after a week. Due to poor search indexing, (or in the case of Twitter, none after 5 days), such discussion content is effectively dead and unfindable.<br />
<br />
Sometimes this FAQ is rephrased as an errant assertion: "nobody will ever see stuff on the wiki", perhaps said in an attempt to support a process of "step 1 is mailing list". See the next FAQ.<br />
<br />
<br />
=== when is it better to IRC or email first ===<br />
''Is it ever better to IRC or email first?''<br />
<br />
Literally no. You should do a web search first.<br />
<br />
However, once you've tried to do a web search to answer whatever question you have, [[IRC]] and email are good for asking questions. In particular, they're good for questions of were/are there any existing discussions of a use-case / topic / feature (since humans can still often find things better conceptually than search engines).<br />
<br />
Thus it may be ''better'' to first ask a '''short''' question in IRC or email (e.g. regarding a specific desired feature or format), '''before''' starting a wiki page.<br />
<br />
If your question is long, [[simplify]] it first.<br />
<br />
<br />
=== why is IRC better than email ===<br />
''Why is IRC okay, but e-mail not okay? [[User:ManuSporny|ManuSporny]] 03:22, 28 February 2009 (UTC)''<br />
<br />
# People can easily choose to be on IRC or not when it is convenient for them to participate in discussions or not and that aspect of easy in/out control is very important. Email on the other hand, is much more cumbersome to subscribe/unsubscribe when you have time to handle discussions or don't. <br />
# In IRC, if a participant has a misconception, others in the channel can quickly correct that participant, rather than the participant waste a lot of time with writing something up that is based on that misconception. In email OTOH, a mistaken assumption in the start of an email can lead to the author wasting time writing paragraphs upon paragraphs dependent on that bad assumption.<br />
<br />
<br />
=== what if I do not have time to be on IRC ===<br />
''What if I don't have time to be on IRC?''<br />
<br />
''I do not have the time to sit around in an IRC channel. -- [[User:ManuSporny|ManuSporny]] 03:22, 28 February 2009 (UTC)''<br />
<br />
''I need an asynchronous method of communication and IRC doesn't work for me. -- [[User:ManuSporny|ManuSporny]] 03:22, 28 February 2009 (UTC)''<br />
<br />
* If you do not have time to be on IRC or want an asynchronous method of communication, you may check the [[IRC]] archives at your convenience.<br />
<br />
<br />
=== what if I prefer to do my communication in batches ===<br />
''What if I prefer to do my communication in batches?''<br />
<br />
''I do my communication in batches because that is most efficient for me. -- [[User:ManuSporny|ManuSporny]] 03:22, 28 February 2009 (UTC)''<br />
<br />
* If you prefer to do your communication in batches, simply check the [[IRC]] archives, write up simple short follow-ups with references to specific IRC archive permalinks, and paste them into IRC at your convenience.<br />
<br />
<br />
=== how do I make sure I do not miss something in IRC ===<br />
''How do I make sure that I don't miss something in IRC?''<br />
<br />
''I can shut off my e-mail client and not worry that I've missed something, I can't necessarily do the same with IRC. -- [[User:ManuSporny|ManuSporny]] 03:22, 28 February 2009 (UTC)''<br />
<br />
* You can check the [[IRC]] archives, since the last time you checked the IRC archives, and thus make sure that you don't miss anything without having to be on IRC at all times.<br />
<br />
<br />
=== what if someone starts an edit war on an issue ===<br />
''What if someone starts an edit war on an issue?''<br />
<br />
''Edit wars lead to subsequent banning of individuals, as this community has experienced. -- [[User:ManuSporny|ManuSporny]] 03:22, 28 February 2009 (UTC)''<br />
<br />
If someone:<br />
* does a revert without any explanation or follow-up explanatory edit, or<br />
* undoes a revert without any follow-up to an explanation, or<br />
* simply repeats an edit, ignoring previous edit explanations<br />
<br />
Please contact one or more of the [[admins]] either on IRC (preferably) or via email, alerting them and providing URL(s) to the problematic edits on the wiki.<br />
<br />
The admins will follow-up by correcting the wiki.<br />
<br />
Such behavior that is disruptive to the community will not be tolerated.<br />
<br />
If the individual persists in an edit war, especially after one of the admins have stepped in, the admins will warn and then ban the individual for progressively longer ban times as necessary.<br />
<br />
<div class="discussion"><br />
* On Wikipedia, there is a principle called the [https://en.wikipedia.org/wiki/Wikipedia:BOLD,_revert,_discuss_cycle BOLD, revert, discuss cycle] (or "BRD" for short). The idea is that you initially make a ''bold'' change to a page without having to have a lot of discussion up-front, and thus avoiding the feeling that one must seek permission from the "owner" of the page. If others disagree with the change, they then revert the change, and then a discussion is conducted to seek consensus. The point of the BRD cycle is to encourage people to engage in reasoned and evidence-based discussion about their disagreements rather than rather than starting an edit war. —[[User:TomMorris|Tom Morris]] 17:43, 23 July 2014 (UTC)<br />
</div><br />
<br />
=== how is the wiki better for controversial issues ===<br />
''How is the wiki better for controversial issues?''<br />
<br />
* All issues, whether controversial or not, are better captured on a wiki for future documentation, with permalinks to reduce the probability that the same issue is re-raised (since the previous issue and resolution can be easily referenced by permalink, and often better discovered by search.)<br />
<br />
* If it seems like differences of opinion on an issue are unresolvable, then a wiki can serve to summarize opinions one way or the other (via +1 / -1 / 0 {username} surveys) so that at least the controversy can be recorded rather than incessant "email-ping-pong" where emails simply just go back and forth and no progress is made.<br />
<br />
* In comparison, e-mail does not allow for broad consensus, only the illusion thereof. The problem is that the overwhelming amount of email noise (on issues or formats they may not be interested in) typically results in people simply paying less attention and eventually leaving the mailing lists. [[logical-flaws#Absence_of_objections_is_not_approval|Absence of response is not an indicator of agreement]] or certainly not consensus. Much better to capture the actual issues/responses/opinions on the wiki and not flood the mailing lists.<br />
<br />
<br />
=== how is the microformats community different from previous standards communities ===<br />
<br />
''How is the microformats community different from previous standards communities?''<br />
<br />
* The microformats community started with the wiki as central practice, and other methods (including IRC) as merely notification or for very brief discussions that if meaningful were captured on the wiki. <br />
* In comparison the email-centric discussions in other standards communities (e.g. W3C, IETF) has long been overwhelmed by trolls and other bad actors (e.g. www-style and www-html mailing lists) thus significantly reducing both the utility of such lists, and the desire for people of any level of expertise to actually attempt to participate.<br />
<br />
As [http://www.paulgraham.com/trolls.html Paul Graham wrote]:<br />
<blockquote><p>There's a sort of Gresham's Law of trolls: trolls are willing to use a forum with a lot of thoughtful people in it, but thoughtful people aren't willing to use a forum with a lot of trolls in it. Which means that once trolling takes hold, it tends to become the dominant culture.</p></blockquote><br />
<br />
<br />
=== how can the wiki improve objectivity and friendliness ===<br />
''How can the wiki improve objectivity and friendliness?'''<br />
<br />
<div class="discussion"><br />
* The wiki is a vital documentation tool, and we should strive that it be written as a quality piece of documentation of issues and specs. --[[User:BenWard|BenWard]] 23:32, 28 February 2009 (UTC)<br />
** +1 [[User:Tantek|Tantek]] 21:23, 15 June 2009 (UTC)<br />
* In forcing discussion into this format, discussion is blunted, becomes harsh and naturally gravitates toward polarized discussion. This is important for documenting the issue; to distill issues to their core, but this is bad for building friendly, amicable relationships between people trying to work together on microformats. --[[User:BenWard|BenWard]] 23:32, 28 February 2009 (UTC)<br />
** We should encourage neutral/objective documentation of issues, and editing of issues to remove emotional content that could be interpreted as hostile or unfriendly. [[User:Tantek|Tantek]] 21:23, 15 June 2009 (UTC)<br />
** In addition, as [[admins]] we should act quickly to warn and ban individuals who are abusive on the wiki (see above about edit wars). [[User:Tantek|Tantek]] 21:23, 15 June 2009 (UTC)<br />
** On the side of friendliness, we should reach out to and contact new editors over IRC and email as necessary to help familiarize them with [[how-to-play]] and the [[mailing-list]] guidelines. [[User:Tantek|Tantek]] 21:23, 15 June 2009 (UTC)<br />
</div><br />
<br />
== historical note ==<br />
<div class="discussion"><br />
* historical note: microformats have always been developed via public IRC + wiki since 2004 when Kevin Marks and Tantek Çelik first started researching/brainstorming/drafting microformats such as [[rel-license]], [[vote-links]], [[XOXO]], [[hCard]], [[hCalendar]] on the public Technorati Developer's Wiki and the Freenode IRC network. Brian Suda somehow discovered the Technorati Developer's wiki page for hCard, started editing it, and that's how he and Tantek Çelik met. The [[mailing-lists]] were not created until the microformats.org site was launched in mid 2005 and have always been considered secondary to the wiki and IRC channel.<br />
** exception: hAudio was developed almost entirely through e-mail and wiki edits. -- [[User:ManuSporny|ManuSporny]] 03:37, 28 February 2009 (UTC)<br />
*** In retrospect, allowing that was probably a mistake, as there were far too many emails on the subject of hAudio for I and many others to keep up with, and many issues were resolved with little breadth of discussion (only 1-2 participants, typically Manu and Martin). In the future as a community we should insist that all issues be captured on the wiki, and that all opinions on specific issues be captured on the wiki, so that this information is not lost in email.[[User:Tantek|Tantek]] 21:23, 15 June 2009 (UTC)<br />
</div><br />
<br />
== related ==<br />
* [[mailing-lists]]<br />
* [[how-to-play]]<br />
* [[put-it-on-the-wiki]]<br />
== see also ==<br />
* [http://www.pbworks.com/7-deadly-sins-block-team-collaboration/ 7 Deadly Sins That Block Team Collaboration (And How To Overcome Them)]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=wiki-2-ja&diff=70178wiki-2-ja2020-07-18T16:35:07Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:Microformats.org Wiki 2.0}}<br />
<!-- english: 2008-11-19T02:33:59 --><br />
<p class="entry-summary">Microformats.org は、2005 年に生まれた最初の時以来、ほぼデフォルトの MediaWiki テーマで運営されてきました。数年を経て、wiki で公開される記事の種類は定まり、コミュニティでの編集の慣例もよく分かってきました。‘Wiki 2.0’ プロジェクトは、コミュニティが必要としていることに対応するべく wiki ソフトをアップデートし、これを機会に見た目も良くすることにしました。</p><br />
__TOC__<br />
<br />
==変更の概要==<br />
<br />
* MediaWiki をバージョン 1.4 からバージョン 1.13.2 にアップデートしました。<br />
* wiki の見た目を、Dan Cederholm による microformats.org の最初のデザインをベースにした、完全なカスタムスキンにアップグレードしました。<br />
* 検索機能の場所をページの右上にしました。ページのずっと下に埋もれているのはばかばかしいことだからです。<br />
* ヘッダーを microformats サイトの他の大事な所――ブログとメーリングリストのアーカイブ――へのリンクにしました。<br />
* いくつか拡張機能を付け加えて MediaWiki をインストールしました。<br />
** HTML の phrase 要素を全てサポートしました。<br />
** コードの構文強調機能を付けました。<br />
** ページタイトルでマークアップし直したものがあります(例えば ‘hcard’ を ‘hCard’ にしたり、もっと大掛かりなものもあります)。<br />
* ‘Talk’ ページは、単に ‘hidden’ にしたのではなく、機能を<strong>完全に</strong>なくしました。<br />
* wiki の全ページを [[hAtom]] と [[hcalendar-ja|hCalendar]] でマークアップしました。<br />
* 記事をもっと体系的にするため、MediaWiki のカテゴリー機能を使っています。<br />
** Specifications(仕様)カテゴリーのページは、特別な「仕様」スタイルにしました([[hCard]] 参照)。<br />
** Draft Specifications(仕様ドラフト)カテゴリーのページは、また別の特別な「仕様」スタイルにしました([[hResume]] 参照)。<br />
** どちらかの仕様カテゴリーのページには、個別の -issues(~の問題)ページへのリンクを作ります。<br />
* TOC――table of contents(目次)――はテーマにあったスタイルにしました。もう TOC を右寄せにするのにインラインスタイルを使う必要はありません。<br />
* インライン表示の issues tracking(問題追跡)とネスト形式の議論一覧表示をサポートしています。以前は、提示された記事から議論が書かれている所を見付け出すのも、スレッドを追いかけるのも難しいことでした。これをもっと適切に表示するマークアップをサポートしました。<br />
* ブログのコメントと同様、ユーザー名の横に [http://gravatar.com Gravatar] が表示されます。<br />
* 投稿前にもう少し我慢してプレビューを見てもらうため、編集画面の ‘Save’ ボタンと ‘Preview’ ボタンを入れ替えました。<br />
<br />
==Wiki 2.0 の使い方==<br />
<br />
以下で Wiki 2.0 の新機能をうまく使う方法を説明したいと思います。<br />
<br />
===ページタイトル===<br />
<br />
MediaWiki がバージョン 1.4 から 1.13 になって、heading(見出し)としてマークアップされた HTML 要素がページの Table of Contents(目次)生成から排除されるというバグが修正されました。今までは <code>H1</code> 要素を使っても目次の番号が1.1、1.2、1.3、etc と小さくはならなかったので、ページの見出しを上書きするにはこれを使ってきました。このバグは修正されたので、上のようなハックはもっときちんとしたメカニズムに置き換わりました。<br />
<br />
ページにタイトルを付けるには、<code>H1</code> 要素を使うのではなく、代わりに <code>entry-title</code> 要素を使ってください。これを MediaWiki の追加機能が解析して、ページ上部に表示されるエントリーのタイトルを目次には含めずに上書きします。この要素を使うのは、それが各ページをマークアップして土台を作っている hAtom の entory-title 要素に相当するからです。<br />
<br />
===仕様ページの書き方===<br />
<br />
新しい wiki では仕様文書を普通のページとは違う特別な表示にする機能をサポートしています。仕様ページは、W3C や WHATWG、その他の団体の文書のように、よりプレーンな外見になって、幅がページいっぱいに広がっています。ページのフッターを拡張してサイドバーはそこに配置したので、機能は全部残っています。<br />
<br />
表示をこのようにするには、ページに特定のカテゴリーを付け加える必要があります。<br />
<br />
* 仕様には <nowiki>[[Category:Specifications]]</nowiki> を付け加えて、‘Specifications’ カテゴリーに追加します。<br />
* 仕様ドラフトには<nowiki>[[Category:Draft Specifications]]</nowiki>を付け加えて、‘Draft Specifications’ カテゴリーに追加します。また、ドラフトは、仕様と区別する文章を載せるために <nowiki>{{DraftSpecification}}</nowiki> テンプレートを文書の冒頭に付け加え'''なければなりません'''。<br />
<br />
問題ページ、ブレインストーミングページやたたき台その他のページは、厳密には仕様ドラフトや仕様ではないので、それらのカテゴリーには追加せず、普通の wiki ページとして表示しておくべきだということに注意してください。<br />
<br />
カテゴリーは記事の一番下で宣言するようにしてください。<br />
<br />
===議論と問題===<br />
<br />
議論はよく、文書中にネストされた一覧として表示されますが、それだと議論を追い、文書の動きのある部分を見分けるのが難しくなります。今度はもっと適切に、そして願わくばもっとはっきりと表示されるようにマークアップできます。<br />
<br />
* <em>議論</em> : <code>&lt;div class="discussion">&lt;/div></code>で囲む。<br />
* <em>問題</em>提起 : <code>&lt;div class="discussion issues">&lt;/div></code>で囲む。<br />
<br />
下は表示例です。<br />
<br />
<div class="discussion"><br />
* 上の表現には不満です。--[[User:BenWard|BenWard]] 09:50, 17 November 2008 (UTC)<br />
** そうかな。いいと思いますよ。--[[User:BenWard|BenWard]] 09:50, 17 November 2008 (UTC)<br />
</div><br />
<br />
<div class="discussion issues"><br />
* '''新しい wiki ではプロフィールページでのアニメーション GIF の宣言による作成機能(declarative creation。訳注:未確認)をサポートしていない。'''これはおおごとだ!--[[User:BenWard|BenWard]] 09:50, 17 November 2008 (UTC)<br />
** いや。ええと……とにかく違う!--[[User:BenWard|BenWard]] 09:50, 17 November 2008 (UTC)<br />
</div><br />
<br />
議論への書き込みには、'''常に'''、文章の終わりで<nowiki>--~~~~</nowiki>を使って署名を入れてください。<br />
<br />
===コードの構文強調===<br />
<br />
[http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi/ja 構文強調の拡張機能]をインストールしました。これで、例とコードの抜粋で使われているたくさんの言語の構文を強調して見やすくすることができます。<br />
<br />
* ソースのブロックに構文強調を適用するには、新たな <code>&lt;source></code> という要素を使ってください。例:<br />
<br />
<pre><nowiki><br />
<source lang=html4strict><br />
<div class="vcard"><br />
<a class="fn org" href="http://microformats.org">Microformats.org</a><br />
</div><br />
</source><br />
</nowiki></pre><br />
<br />
表示結果:<br />
<br />
<source lang=html4strict><br />
<div class="vcard"><br />
<a class="fn org" href="http://microformats.org">Microformats.org</a><br />
</div><br />
</source><br />
<br />
HTML 用の言語名はただの ‘HTML’ ではなくて<code>html4strict</code> になることに注意してください。サポートされている全言語の一覧は構文強調拡張機能ページで見ることができます: http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi/ja#.E3.82.B5.E3.83.9D.E3.83.BC.E3.83.88.E3.81.95.E3.82.8C.E3.82.8B.E8.A8.80.E8.AA.9E]<br />
<br />
==クレジット==<br />
<br />
Wiki 2.0 プロジェクトは [[User:BenWard]] が遂行しました。見た目は [http://simplebits.com Dan Cederholm] による最初の microformats.org のテーマを引き継ぎました。また、Mark James による素晴らしく使いやすい [http://famfamfam.com/lab/icons/silk/ Fam Fam Fam の Silk icon] を使っています。<br />
<br />
==問題==<br />
<br />
バグの問題やリクエストは [[wiki-2-issues]] ページで報告してください。<br />
<br />
[[Category:Microformats.org]]<br />
[[Category:Wiki]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=wiki-2-issues&diff=70177wiki-2-issues2020-07-18T16:35:06Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:Wiki 2.0 Issues}}<br />
The following documents issues and bugs with the new wiki 2.0 launch.<br />
__TOC__<br />
==Known Issues==<br />
<br />
===Syntax Highlighting is Ugly===<br />
<div class="discussion issues"><br />
* '''The default syntax highlighting stylesheet does not match the look and feel of microformats.org'''. This is because the extension has been installed as is, and a custom stylesheet hasn't been produced for languages.<br />
</div><br />
<br />
===Many pages have duplicate headings===<br />
<div class="discussion issues"><br />
* '''Some pages are displayed with two titles'''. These are pages which haven't been updated to use the <code><nowiki><entry-title></nowiki></code> mark-up for page headings yet. They are currently displaying the MediaWiki default heading, as well as the heading from the previous wiki install. The page needs to be updated to use the new mark-up.<br />
* '''Default <code>my-page</code> headings could be dynamically reformatted'''. To save manual overrides of every page on the wiki, add reformatting rules to convert ‘wiki-2-issues- into ‘Wiki 2 Issues’ and so on. --[[User:BenWard|BenWard]] 00:00, 12 January 2009 (UTC)<br />
** It be necessary to have special handling for ‘hcard-issues’ to ‘hCard issues’ for capitalization, but can handle most cases. Just keep a little list of known microformats? --[[User:BenWard|BenWard]] 00:00, 12 January 2009 (UTC)<br />
</div><br />
<br />
===User Preferences have been reset===<br />
<div class="discussion issues"><br />
* '''All user preferences have been reset to defaults.''' To switch to the new theme, user preferences had to be overwritten. Sensible defaults have been applied, but apologies to those who had customised their profiles. You need to adjust your setting again from the [[Special:Preferences]] page.<br />
</div><br />
<br />
===IRC Bot===<br />
<div class="discussion issues"><br />
* '''The #microformats IRC bot is nolonger reporting page edits'''. Edits of either major or minor type are nolonger echoed into #microformats IRC<br />
** Need to check with Ryan King or Tantek regarding how to reconfigure that. --[[User:BenWard|BenWard]] 10:16, 17 November 2008 (UTC)<br />
*** I just [http://krijnhoetmer.nl/irc-logs/microformats/20081117#l-70 checked with Ryan on irc], maintainer of [[mfbot]], and according to him it needs to be rewritten [probably due to the database schema change]. Since the bot was originally derived from a bot from the Wikipedia community, it may be possible to upgrade mfbot using their latest bot code. Ryan does not have time to look into this now, so we need to add this to the wiki-2 upgrade fix-up [[to-do]] list. --[[User:Tantek|Tantek]] 18:05, 17 November 2008 (UTC)<br />
</div><br />
<br />
===Top Navigation Bar===<br />
<div class="discussion issues"><br />
* Absolutely beautiful upgrade, Ben. But because the wiki is now ''so'' integrated with the uf look and feel, people are going to wonder where the About/Code+Tools/Get Started links have gone. [[Special:Contributions/91.84.42.38|91.84.42.38]] 17:12, 17 November 2008 (UTC)<br />
</div><br />
<br />
===Categories===<br />
<div class="discussion issues"><br />
* As well as "Specifications" and "Draft Specifications", I'd suggest "Pre-Draft Specifications" for efforts like haudio, figure, hproduct, and hrecipe, which seem to be converging on relatively stable specs, but haven't got there quite yet; and "Exploratory Discussions" for efforts which are still in the early stages. (But no custom style sheets for those categories.) [[User:TobyInk|TobyInk]] 17:37, 17 November 2008 (UTC)<br />
** I have created a [[category-suggestions]] page to collect such suggestions, and updated the respective [[how-to-play]] guideline accordingly. --[[User:Tantek|Tantek]] 18:15, 17 November 2008 (UTC)<br />
</div><br />
<br />
===New Users cannot edit their own User: page===<br />
<div class="discussion issues"><br />
* Newly registered users are able to edit pages in the global wiki namespace, but not within <code>User:</code>. --Reported by Rob Manson, November 29th<br />
** This is presumably a configuration issue concerning default user-group permissions. Likely overwritten, or the format changed, when we upgraded to MediaWiki 1.13 --[[User:BenWard|BenWard]] 21:25, 30 November 2008 (UTC)<br />
</div><br />
<br />
===Generate front-page content from categories===<br />
<div class="discussion issues"><br />
* Also, would be nice if the Main_Page listings of drafts and specifications could be auto-generated from the categories, but that's probably unlikely. [[User:TobyInk|TobyInk]] 17:37, 17 November 2008 (UTC)<br />
** Agreed, that would be neat. I'll take a look into doing that with an extension. --[[User:BenWard|BenWard]] 22:49, 17 November 2008 (UTC)<br />
</div><br />
<br />
===Spam===<br />
<div class="discussion issues"><br />
* Surely it's possible to create a plugin which looks at edits from users with no edit history, and blocks the edit if and only if it seems to create a one-word paragraph at the top of the page? [[User:TobyInk|TobyInk]] January 5th 2009<br />
* I recommend the [http://www.mediawiki.org/wiki/Extension:ReCAPTCHA ReCAPTCHA plugin] for MediaWiki as a way of preventing spambots from signing up. It's one of the least annoying CAPTCHAs I've seen: the words presented are part of the Project Gutenberg book scanning, and it has an audio version - but there is some dispute regarding accessibility - see [http://www.accessifyforum.com/viewtopic.php?t=10686 here]. The [http://www.mediawiki.org/wiki/Extension:ConfirmEdit ConfirmEdit extension] allows you to trigger a CAPTCHA on a variety of events. If someone can come up with some regular expressions which match the spam problem, you can always use [http://www.mediawiki.org/wiki/Extension:SpamRegex the SpamRegex extension]. I'll have a little think about possible anti-spam regexes, but it could be something of a tough problem as spam is subject to Darwinian principles... --[[User:TomMorris|TomMorris]] 20:49, 5 January 2009 (UTC)<br />
</div><br />
<br />
===CAPTCHA loop problem===<br />
<div class="discussion issues"><br />
* If you edit a page and add some external links, then save without an edit summary, you get the CAPTCHA which pops up. You fill in the CAPTCHA, and then it goes to a page which tells you that if you hit save again, it'll post your edit without an edit summary. But if you try to do so, it then brings up the CAPTCHA again. The only way that the user can post edits with external links is to post an edit summary. Of course, every edit should have an edit summary. But I was being lazy. Dunno what the right way to resolve this is. –[[User:TomMorris|TomMorris]] 10:14, 15 August 2009 (UTC)<br />
</div><br />
<br />
==Fixed Issues==<br />
<br />
===TOC overlaps preceding text===<br />
<div class="discussion issues"><br />
* '''The TOC overlaps preceding paragraphs of text'''. This is an error in the stylesheet. For visual effect the TOC gets pulled upward to overlap titles, but does not account for being preceded by a paragraph, rather than the page heading.<br />
** Fixed 2008-11-17 by [[User:BenWard]]<br />
</div><br />
<br />
==Related Pages==<br />
<br />
* [[wiki-2]]<br />
<br />
[[Category:Wiki]]<br />
[[Category:Issues Tracking]]</div>Aaronpkhttp://microformats.org/wiki/index.php?title=wiki-2-fr&diff=70176wiki-2-fr2020-07-18T16:35:05Z<p>Aaronpk: Replace <entry-title> with {{DISPLAYTITLE:}}</p>
<hr />
<div>{{DISPLAYTITLE:Wiki Microformats.org 2.0}}<br />
<p class="entry-summary">Microformats.org a été servi par un moteur MediaWiki avec un thème proche du défaut depuis sa création en 2005. Au fil des années, le type de contenu publié sur le wiki s'est établi, et les pratiques d'édition de notre communauté mieux comprises. Le projet 'Wiki 2.0' est une entreprise pour mettre à jour notre logiciel wiki afin de mieux coller aux besoins de la communauté, et de saisir l'opportunité d'ajouter aussi quelque scintillement visuel.</p><br />
__TOC__<br />
<br />
==Résumé des Modifications==<br />
<br />
* MediaWiki a été mis à jour de la version 1.4 vers la version 1.13.2.<br />
* Le stylisme visuel du wiki a été mis à jour sur une skin complètement personnalisée, fondée sur le design original de Dan Cederholm sur microformats.org.<br />
* La fonctionnalité de recherche est désormais localisée tout en haut et à droite de la page, parce que la voir enterrée plus bas était idiot.<br />
* L'en-tête lie maintenant vers d'autres parties vitales du site microformats — le blog et les archives de la liste de discussion.<br />
* Quelques nouvelles extensions ont été ajoutée à l'installation MediaWiki<br />
** les éléments phrase HTML sont désormais complètement supportés<br />
** Ajout de la mise en valeur de la syntaxe pour le Code<br />
** Les titres de pages peuvent maintenant être récrits dans le marquage (par ex. 'hcard' peut devenir 'hCard', ou des transformations plus ambitieuses)<br />
* Les pages de ‘Discussion’ ont été <strong>complètement</strong> désactivées, plutôt que simplement ‘cachées’.<br />
* Toutes les pages wiki sont marquées avec [[hatom-fr|hAtom]] et [[hcalendar-fr|hCalendar]]<br />
* Nous utiliserons désormais la fonctionnalité des catégories de MediaWiki pour mieux organiser notre contenu.<br />
** Les pages placées à l'intérieur de la catégorie Specifications reçoivent un style spécial ‘spec-like’ (voir [[hcard|hCard]]).<br />
** Les pages placées dans la catégorie Draft Specification reçoivent un style spécial ‘spec-like’ (voir [[hResume]])<br />
** Les pages placées dans quelque catégorie de spécification que ce soit génèreront des liens vers leurs pages respectives de problématiques.<br />
* TOC — table des matières — est maintenant proprement stylisé dans le thème. Plus besoin d'utiliser les styles dans la ligne pour aligner la table des matières sur la droite.<br />
* Il y a désormais un support de stylisme pour à la fois les problématiques de suivi dans la ligne et les discussions dans l'imbricage de liste. Avant il était difficile d'identifier la documentation de discussion à partir du contenu proposé, et difficile de suivre les fils de discussion. Le marquage est maintenant supporté pour styliser cela de façon plus approprié.<br />
* Votre nom d'utilisateur a maintenant un [http://gravatar.com Gravatar] qui s'affiche, comme dans les commentaires de blog.<br />
* Au moment de modifier une page, les boutons 'Publier' et 'Prévisualiser' ont été inversés pour essayer d'encourager les personnes à prévisualiser avant de publier.<br />
<br />
==Comment Utiliser Wiki 2.0==<br />
<br />
Ce qui suit essaye d'expliquer comment mieux utiliser les nouvelles fonctionnalités de Wiki 2.0.<br />
<br />
===Titres des Pages===<br />
<br />
Entre la 1.4 et 1.13 MediaWiki a réparé un bug où les titres marqués avec des éléments HTML étaient exclus de la Table des Matières sur les pages. Nous utilisions alors les éléments <code>H1</code> pour neutraliser les titres des pages tout en conservant la numérotation de la Table des Matières en 1.1, 1.2, 1.3, etc. Depuis que ce bug est réparé, ce hack a été remplacé par un mécanisme plus robuste.<br />
<br />
<em>Plutôt que d'utiliser les éléments <code>H1</code> pour titrer vos pages, utilisez à la place le nouvel élément <code>entry-title</code></em>. Ceci est analysé par une extension MediaWiki et passe outre le titre de l'entrée tel qu'affiché sur la page, tout en l'excluant de la Table des Matières. C'est ainsi nommé, parce que cela correspond à l'élément entry-title dans le hAtom inclus dans chaque entrée.<br />
<br />
===Ecriture des Spécifications===<br />
<br />
Le nouveau wiki supporte l'affichage spécial des documents de spécifications, différent des pages normales. Les pages sont stylisés plus clairement et le contenu occupe la totalité de la largeur de la page, proche de la documentation provenant du W3C, WHATWG et d'autres corps. La barre latérale est poussée en bas dans un pied de page étendue, de façon à ce que toutes les fonctionnalités demeurent.<br />
<br />
Pour permettre ces vues, vous devez ajouter votre page à une catégorie particulière.<br />
<br />
* Les spécifications devraient être ajoutées à la catégorie ‘Specifications’, en ajoutant <nowiki>[[Category:Specifications]]</nowiki> à la base du document.<br />
* Les 'Draft Specifications' devraient être ajoutée à la catégorie ‘Draft Specifications’ en ajoutant <nowiki>[[Category:Draft Specifications]]</nowiki> à la base du document. Vous '''devez''' aussi inclure le modèle <nowiki>{{DraftSpecification}}</nowiki> dans l'en-tête de votre document, afin de fournir une différenciation textuelle du brouillon.<br />
<br />
Remarquez S.V.P. que les pages de problématiques, les pages de brainstorming, les straw-men et tout ce qu'il y a d'autres non explicitement Spécification Draft ou Documentation de Spécification ne devraient pas être ajoutés à ces catégories et devraient continuer à être présenté comme des pages wiki normales.ar wiki pages.<br />
<br />
Les catégories devraient être déclarées à la base des articles, svp.<br />
<br />
===Discussions et Problématiques===<br />
<br />
Dans les documents, les discussions sont souvent représentées à travers des listes imbriquées. Elles sont difficiles à suivre et à différencier du véritable contenu du document. Vous pouvez maintenant les marquer et faire qu'elles soient présentées judicieusement, et nous l'espérons plus clairement.<br />
<br />
* Pour les <em>discussions</em> : entourez le fil avec <code>&lt;div class="discussion">&lt;/div></code>.<br />
* Pour valoriser les <em>problématiques</em> : entourez le fil avec <code>&lt;div class="discussion issues">&lt;/div></code>.<br />
<br />
Voici des exemples pour présenter le rendu :<br />
<br />
<div class="discussion"><br />
* Je ne suis pas très satisfait de la traduction ci-dessus. --[[User:ChristopheDucamp|ChristopheDucamp]] 05:25, 19 May 2009 (UTC)<br />
** Pas d'accord. Je pense que ça pourra suffire pour aujourd'hui ! --[[User:ChristopheDucamp|ChristopheDucamp]] 05:25, 19 May 2009 (UTC)<br />
</div><br />
<br />
<div class="discussion issues"><br />
* '''Le nouveau wiki ne supporte pas la création déclarative de GIFs animés sur les pages de profil.'''. Parfait pour moi, belle évolution ! --[[User:BenWard|BenWard]] 09:50, 17 November 2008 (UTC)<br />
** Non. Juste… non ! --[[User:BenWard|BenWard]] 09:50, 17 November 2008 (UTC)<br />
</div><br />
<br />
Signez '''toujours''' vos contributions aux discussions en utilisant la chaîne <nowiki>--~~~~</nowiki> à la fin de votre texte.<br />
<br />
===Mise en Valeur du Code===<br />
<br />
Nous avons installé une [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi extension Syntax Highlighting]. Ceci vous permet d'avoir une mise en valeur plus élégante de bon nombre de langages dans les exemples et de fragments de codes sur le wiki.<br />
<br />
* Pour utiliser des blocs de source mis en valeur, utilisez le nouvel élément <code>&lt;source></code>. Par exemple : <br />
<br />
<pre><nowiki><br />
<source lang=html4strict><br />
<div class="vcard"><br />
<a class="fn org" href="http://microformats.org">Microformats.org</a><br />
</div><br />
</source><br />
</nowiki></pre><br />
<br />
Produit <br />
<br />
<source lang=html4strict><br />
<div class="vcard"><br />
<a class="fn org" href="http://microformats.org">Microformats.org</a><br />
</div><br />
</source><br />
<br />
Notez que le nom du langage pour le HTML est <code>html4strict</code>, pas juste ‘HTML’. Vous pouvez trouver la liste complète de tous les langages supportés sur la page d'extension Syntax Highlighter : http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi#Supported_languages<br />
<br />
==Crédits==<br />
<br />
Le projet Wiki 2.0 a été implémenté par [[User:BenWard]]. Le style visuel est dérivé du thème original microformats.org de [http://simplebits.com Dan Cederholm]. Le wiki utilise aussi les icônes merveilleusement utiles [http://famfamfam.com/lab/icons/silk/ Fam Fam Fam Silk] de Mark James.<br />
<br />
==Problématiques==<br />
<br />
Rendez compte svp des problématiques de bugs et demandes de fonctionnalités sur la page [[wiki-2-issues]].<br />
<br />
== En rapport ==<br />
* [[mediawiki-customization]]<br />
<br />
[[Category:Microformats.org]]</div>Aaronpk