<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/user/night.kame/marks/tag/microformats">
<title>Public marks from user night.kame with tag microformats</title>
<description>Public marks from user night.kame with tag microformats</description>
<link>http://blogmarks.net/user/night.kame/marks/tag/microformats</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/night.kame/mark/1058352231"/>
<rdf:li resource="http://blogmarks.net/api/user/night.kame/mark/1058163633"/>
<rdf:li resource="http://blogmarks.net/api/user/night.kame/mark/1057528326"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/night.kame/mark/1058352231">
<title>Unboxing Web-Oriented Architecture: The 6 Aspects Of An Emergent Architectural Style</title>
<link>http://hinchcliffe.org/archive/2009/06/06/16901.aspx</link>
<description>&lt;blockquote&gt;&lt;p&gt;Transfer Methods. This is at the core of REST and ROA and is the foundation of Web-Oriented Architecture. You can read Roy Fielding's chapter on REST (he conceived of the approach originally) or you can just follow the simple guidelines here. At other times, protocols like BitTorrent can be used if the requirements warrant it, but these are exceptional scenarios that I will cover at some point in the future.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Ne pas citer XMPP dans les &quot;Transfer Methods&quot; quelque jours après l'annonce de Google Wave, et surtout le mettre dans le schéma au niveau des Microformats fait perdre toute crédibilité à l'article.&lt;/p&gt;</description>
<dc:date>2009-06-07T19:29:02Z</dc:date>
<dc:author>night.kame</dc:author>
<dc:subject>soa, rest, xmpp, microformats, gloubi-boulga</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://hinchcliffe.org/archive/2009/06/06/16901.aspx"><img border="0" src="http://blogmarks.net/screenshots/2009/06/07/2bc3b205bc59b5d8c3bd4a6857ce3582.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://hinchcliffe.org/archive/2009/06/06/16901.aspx">Unboxing Web-Oriented Architecture: The 6 Aspects Of An Emergent Architectural Style</a></h4>
 
by <a href="http://blogmarks.net/user/night.kame">night.kame</a> 
<div class="description"><blockquote><p>Transfer Methods. This is at the core of REST and ROA and is the foundation of Web-Oriented Architecture. You can read Roy Fielding's chapter on REST (he conceived of the approach originally) or you can just follow the simple guidelines here. At other times, protocols like BitTorrent can be used if the requirements warrant it, but these are exceptional scenarios that I will cover at some point in the future.</p></blockquote>
<p>Ne pas citer XMPP dans les "Transfer Methods" quelque jours après l'annonce de Google Wave, et surtout le mettre dans le schéma au niveau des Microformats fait perdre toute crédibilité à l'article.</p></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/soa">soa</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/rest">rest</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xmpp">xmpp</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/microformats">microformats</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/gloubi-boulga">gloubi-boulga</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058352231">Copy</a> | 
<a href="http://blogmarks.net/link/3220692">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/night.kame/mark/1058163633">
<title>MetaExtensions - WHATWG Wiki</title>
<link>http://wiki.whatwg.org/wiki/MetaExtensions</link>
<description>&lt;blockquote&gt;&lt;p&gt;For the &quot;Status&quot; section to be changed to &quot;Accepted&quot;, the proposed keyword must either have been through the Microformats process, and been approved by the Microformats community;&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;Oui oui, on est bien en train de parler de HTML 5 là.&lt;/p&gt;</description>
<dc:date>2009-01-17T20:37:45Z</dc:date>
<dc:author>night.kame</dc:author>
<dc:subject>html5, joke, microformats</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://wiki.whatwg.org/wiki/MetaExtensions"><img border="0" src="http://blogmarks.net/screenshots/2009/01/17/3fa5c69fafdccc71c7514c450e4f9529.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://wiki.whatwg.org/wiki/MetaExtensions">MetaExtensions - WHATWG Wiki</a></h4>
 
by <a href="http://blogmarks.net/user/night.kame">night.kame</a> 
<div class="description"><blockquote><p>For the "Status" section to be changed to "Accepted", the proposed keyword must either have been through the Microformats process, and been approved by the Microformats community;</p></blockquote><p>Oui oui, on est bien en train de parler de HTML 5 là.</p></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html5">html5</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/joke">joke</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/microformats">microformats</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058163633">Copy</a> | 
<a href="http://blogmarks.net/link/3060534">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/night.kame/mark/1057528326">
<title>TPAC 2007 - URI-Based Extensibility: Benefits, Deviations, Lessons-Learned - W3C Q&amp;A Weblog</title>
<link>http://www.w3.org/QA/2007/11/tpac-2007-uri-extensibility.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;Ian Hickson stresses out that there is little value to give URI for microformats for example, and that you still need knowledge of the vocabulary to implement it.&lt;/p&gt;&lt;/blockquote&gt;

Next (logical) step: there is little value in microformats.</description>
<dc:date>2007-11-08T00:08:31Z</dc:date>
<dc:author>night.kame</dc:author>
<dc:subject>microformats, bricolage</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.w3.org/QA/2007/11/tpac-2007-uri-extensibility.html"><img border="0" src="http://blogmarks.net/screenshots/2007/11/08/f51e5bf3dad668be33ff07eaf08aa32d.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.w3.org/QA/2007/11/tpac-2007-uri-extensibility.html">TPAC 2007 - URI-Based Extensibility: Benefits, Deviations, Lessons-Learned - W3C Q&amp;A Weblog</a></h4>
 
by <a href="http://blogmarks.net/user/night.kame">night.kame</a> 
<div class="description"><blockquote><p>Ian Hickson stresses out that there is little value to give URI for microformats for example, and that you still need knowledge of the vocabulary to implement it.</p></blockquote>

Next (logical) step: there is little value in microformats.</div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/microformats">microformats</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bricolage">bricolage</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057528326">Copy</a> | 
<a href="http://blogmarks.net/link/2516288">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>