<?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/holyver/marks">
<title>Public marks from user holyver</title>
<description>Public marks from user holyver</description>
<link>http://blogmarks.net/user/holyver/marks</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058592199"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058570495"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058524400"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058458344"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058420517"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058397050"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058389190"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058389038"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058379955"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058379897"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058374231"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058374224"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058368860"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058360169"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058360167"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058353877"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058353873"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058353872"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058353828"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058340062"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058299683"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058271040"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058271038"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058271032"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058269680"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058592199">
<title>LinkedIn Developer Network</title>
<link>http://developer.linkedin.com/index.jspa</link>
<description>LinkedIn APIs

Let your users bring LinkedIn profiles and networks with them to your site or application. You gain better awareness of your users, increase productive engagement, and gain reach through the 52 million professionals on LinkedIn.</description>
<dc:date>2009-11-25T21:07:19Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>social network, api, development, widget</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://developer.linkedin.com/index.jspa"><img border="0" src="http://blogmarks.net/screenshots/2009/11/25/397cd9e86336e93707f863cee4a09b44.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://developer.linkedin.com/index.jspa">LinkedIn Developer Network</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">LinkedIn APIs

Let your users bring LinkedIn profiles and networks with them to your site or application. You gain better awareness of your users, increase productive engagement, and gain reach through the 52 million professionals on LinkedIn.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/social%2Bnetwork">social network</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/api">api</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/development">development</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/widget">widget</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058592199">Copy</a> | 
<a href="http://blogmarks.net/link/3416260">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058570495">
<title>The Complete Guide to Google Wave: How to Use Google Wave</title>
<link>http://completewaveguide.com/</link>
<description>Google Wave is a new web-based collaboration tool that's notoriously difficult to understand. This guide will help. Here you'll learn how to use Google Wave to get things done with your group. Because Wave is such a new product that's evolving quickly, this guidebook is a work in progress that will update in concert with Wave as it grows and changes. Read more about The Complete Guide to Google Wave. </description>
<dc:date>2009-11-02T21:51:13Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>google wave, book, guide, collaboratif</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://completewaveguide.com/"><img border="0" src="http://blogmarks.net/screenshots/2009/11/15/af99505dea7be32bc73a6937c02d6cd1.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://completewaveguide.com/">The Complete Guide to Google Wave: How to Use Google Wave</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3399302">1 other(s)</a> 
<p class="description">Google Wave is a new web-based collaboration tool that's notoriously difficult to understand. This guide will help. Here you'll learn how to use Google Wave to get things done with your group. Because Wave is such a new product that's evolving quickly, this guidebook is a work in progress that will update in concert with Wave as it grows and changes. Read more about The Complete Guide to Google Wave. </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google%2Bwave">google wave</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/book">book</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/guide">guide</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/collaboratif">collaboratif</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058570495">Copy</a> | 
<a href="http://blogmarks.net/link/3399302">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058524400">
<title>Gilbane SF: Content Integration Standards -- CMIS, JSR-170, JSR-283</title>
<link>http://www.cmswire.com/cms/enterprise-cms/gilbane-sf-content-integration-standards-cmis-jsr170-jsr283-004762.php</link>
<description>One of the final sessions at Gilbane SF yesterday was around content standards: CMIS, JSR-170 and JSR-283.

Many realize there are several challenges with CMIS in particular and efficiently working with content from disparate content repositories in general.

The session aimed at shedding light on some of these challenges and possible solutions in the standards space. </description>
<dc:date>2009-09-30T19:18:23Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>JSR-170, jsr-283, cmis, repository, ecm, clevermarks</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.cmswire.com/cms/enterprise-cms/gilbane-sf-content-integration-standards-cmis-jsr170-jsr283-004762.php"><img border="0" src="http://blogmarks.net/screenshots/2009/09/30/56d4cc0bc3d361e1c1906ad49c01160b.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.cmswire.com/cms/enterprise-cms/gilbane-sf-content-integration-standards-cmis-jsr170-jsr283-004762.php">Gilbane SF: Content Integration Standards -- CMIS, JSR-170, JSR-283</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">One of the final sessions at Gilbane SF yesterday was around content standards: CMIS, JSR-170 and JSR-283.

Many realize there are several challenges with CMIS in particular and efficiently working with content from disparate content repositories in general.

The session aimed at shedding light on some of these challenges and possible solutions in the standards space. </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/JSR-170">JSR-170</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/jsr-283">jsr-283</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cmis">cmis</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/repository">repository</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ecm">ecm</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/clevermarks">clevermarks</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058524400">Copy</a> | 
<a href="http://blogmarks.net/link/3360176">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058458344">
<title>A Quick Tutorial on JavaScript Bookmarklets</title>
<link>http://www.mattcutts.com/blog/javascript-bookmarklet-basics/</link>
<description>Bookmarklets are very handy pieces of JavaScript code that you can bookmark</description>
<dc:date>2009-08-07T15:17:20Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>tutorial, javascript, code, bookmarklet, clevermarks</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.mattcutts.com/blog/javascript-bookmarklet-basics/"><img border="0" src="http://blogmarks.net/screenshots/2009/08/07/aeee8e22f1b61b0b85edabf3a8c5badb.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.mattcutts.com/blog/javascript-bookmarklet-basics/">A Quick Tutorial on JavaScript Bookmarklets</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">Bookmarklets are very handy pieces of JavaScript code that you can bookmark</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tutorial">tutorial</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/javascript">javascript</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/code">code</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bookmarklet">bookmarklet</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/clevermarks">clevermarks</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058458344">Copy</a> | 
<a href="http://blogmarks.net/link/3309001">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058420517">
<title>Google Gears windows and linux compiled versions compatible with Firefox 3.5</title>
<link>http://code.google.com/p/gears/issues/detail?id=749</link>
<description>In case anyone's interested, here are Firefox 3.5 compatible xpi builds for Windows i386 (compiled on Visual Studio 2008 SP1) and Linux i386 and x86_64 (compiled using gcc 4.3.3 on Ubuntu using my patch posted above): http://gkovacs.xvm.mit.edu/google-gears/gears-win32-opt-0.5.25.0.xpi http://gkovacs.xvm.mit.edu/google-gears/gears-linux-0.5.25.0.xpi http://gkovacs.xvm.mit.edu/google-gears/gears-linux-x86_64-0.5.25.0.xpi </description>
<dc:date>2009-07-07T20:44:35Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>linux, google, windows, code, ubuntu</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://code.google.com/p/gears/issues/detail?id=749"><img border="0" src="http://blogmarks.net/screenshots/2009/07/07/821fe425fbc48db83131788db06756ba.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://code.google.com/p/gears/issues/detail?id=749">Google Gears windows and linux compiled versions compatible with Firefox 3.5</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">In case anyone's interested, here are Firefox 3.5 compatible xpi builds for Windows i386 (compiled on Visual Studio 2008 SP1) and Linux i386 and x86_64 (compiled using gcc 4.3.3 on Ubuntu using my patch posted above): http://gkovacs.xvm.mit.edu/google-gears/gears-win32-opt-0.5.25.0.xpi http://gkovacs.xvm.mit.edu/google-gears/gears-linux-0.5.25.0.xpi http://gkovacs.xvm.mit.edu/google-gears/gears-linux-x86_64-0.5.25.0.xpi </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linux">linux</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/windows">windows</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/code">code</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ubuntu">ubuntu</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058420517">Copy</a> | 
<a href="http://blogmarks.net/link/3279102">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058397050">
<title>Digital Web Magazine - User Interface Implementations of Faceted Browsing</title>
<link>http://www.digital-web.com/articles/user_interface_implementations_of_faceted_browsing/</link>
<description>Just as it is important to choose the proper knife when slicing-n-dicing vegetables, it is critical to prescribe a suitable user interface to support faceted filtering. Faceted filtering allows you to narrow down a large list of objects to a manageable size by applying flexible combinations of attribute filters in any order. Rather than forcing you down fixed paths within a website’s information architecture, faceted filtering allows you to multi-dimensionally slice-n-dice the information in a manner that best accommodates your specific needs. A user interface that optimally supports faceted filtering must expose its robust functionality in a way that expresses affordances, controls complexity, and follows existing standards that have been pre-established across the web.</description>
<dc:date>2009-06-26T22:56:28Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>gui, facet, search engine, web</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.digital-web.com/articles/user_interface_implementations_of_faceted_browsing/"><img border="0" src="http://blogmarks.net/screenshots/2009/06/26/59b4c5a06f1fb0bfcb60020dbcb46ec8.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.digital-web.com/articles/user_interface_implementations_of_faceted_browsing/">Digital Web Magazine - User Interface Implementations of Faceted Browsing</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">Just as it is important to choose the proper knife when slicing-n-dicing vegetables, it is critical to prescribe a suitable user interface to support faceted filtering. Faceted filtering allows you to narrow down a large list of objects to a manageable size by applying flexible combinations of attribute filters in any order. Rather than forcing you down fixed paths within a website’s information architecture, faceted filtering allows you to multi-dimensionally slice-n-dice the information in a manner that best accommodates your specific needs. A user interface that optimally supports faceted filtering must expose its robust functionality in a way that expresses affordances, controls complexity, and follows existing standards that have been pre-established across the web.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/gui">gui</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/facet">facet</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/search%2Bengine">search engine</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058397050">Copy</a> | 
<a href="http://blogmarks.net/link/3258601">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058389190">
<title>google-friend-connect-plugins - Google Code</title>
<link>http://code.google.com/p/google-friend-connect-plugins/</link>
<description>Google Friend Connect provides simple user authentication using any OpenID account, including Google, Yahoo and AIM. Instead of filling in yet another profile form, your users can connect to their existing identities, showing current profile pictures.

By making login easier and connected to existing identity, you'll see increased engagement and comment activity.

The Google Friend Connect plugins are proof-of-concept code to integrate users with external accounts into your site. A user can visit your site and leave a comment with a Google Account, Yahoo Account, any OpenID, or in future other sites that participate in OpenSocial.

See separate instructions for the WordPressPlugin, DrupalPlugin and PhpbbPlugin</description>
<dc:date>2009-06-24T00:39:22Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>google, openid, authentication, OpenSocial, drupal, plugin, clevermarks, google friend connect</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://code.google.com/p/google-friend-connect-plugins/"><img border="0" src="http://blogmarks.net/screenshots/2009/06/24/2032686f22298c8c9c336f30e5c4e9ff.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://code.google.com/p/google-friend-connect-plugins/">google-friend-connect-plugins - Google Code</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">Google Friend Connect provides simple user authentication using any OpenID account, including Google, Yahoo and AIM. Instead of filling in yet another profile form, your users can connect to their existing identities, showing current profile pictures.

By making login easier and connected to existing identity, you'll see increased engagement and comment activity.

The Google Friend Connect plugins are proof-of-concept code to integrate users with external accounts into your site. A user can visit your site and leave a comment with a Google Account, Yahoo Account, any OpenID, or in future other sites that participate in OpenSocial.

See separate instructions for the WordPressPlugin, DrupalPlugin and PhpbbPlugin</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/openid">openid</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/authentication">authentication</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/OpenSocial">OpenSocial</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/drupal">drupal</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/plugin">plugin</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/clevermarks">clevermarks</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google%2Bfriend%2Bconnect">google friend connect</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058389190">Copy</a> | 
<a href="http://blogmarks.net/link/3253044">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058389038">
<title>OAuth-OpenID: You’re Barking Up the Wrong Tree if you Think They’re the Same Thing</title>
<link>http://softwareas.com/oauth-openid-youre-barking-up-the-wrong-tree-if-you-think-theyre-the-same-thing</link>
<description>OAuth, OpenID…they sound like the same thing and they kind of do vaguely similar things But I’m here to tell you, OAuth is not Open ID. They have a different purpose. I’ve been playing around with OAuth a bit in the past couple weeks and have a grip on what it’s aiming to do and what it’s not aiming to do.

To start with, here’s what OAuth does have in common with Open ID</description>
<dc:date>2009-06-23T20:42:59Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>oAuth, openid, faq, authentication, security, clevermarks</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://softwareas.com/oauth-openid-youre-barking-up-the-wrong-tree-if-you-think-theyre-the-same-thing"><img border="0" src="http://blogmarks.net/screenshots/2009/06/23/b36484a4f10cba29bbf53e55188f5df3.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://softwareas.com/oauth-openid-youre-barking-up-the-wrong-tree-if-you-think-theyre-the-same-thing">OAuth-OpenID: You’re Barking Up the Wrong Tree if you Think They’re the Same Thing</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">OAuth, OpenID…they sound like the same thing and they kind of do vaguely similar things But I’m here to tell you, OAuth is not Open ID. They have a different purpose. I’ve been playing around with OAuth a bit in the past couple weeks and have a grip on what it’s aiming to do and what it’s not aiming to do.

To start with, here’s what OAuth does have in common with Open ID</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/oAuth">oAuth</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/openid">openid</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/faq">faq</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/authentication">authentication</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/security">security</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/clevermarks">clevermarks</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058389038">Copy</a> | 
<a href="http://blogmarks.net/link/3252914">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058379955">
<title>Google I/O - OpenSocial in the Enterprise</title>
<link>http://code.google.com/intl/fr/events/io/sessions/OpenSocialEnterprise.html</link>
<description>In the year and half since OpenSocial's public launch, there are now over 700 million end users of OpenSocial applications across numerous social sites (containers) around the world. With OpenSocial's proven global success in traditional social applications, the enterprise software community has now begun to realize its potential and build innovative solutions that cater to the enterprise. Join us for a session centered on how the enterprise software development community is successfully bringing social concepts and technology into the enterprise. Key enterprise players will present and demonstrate how they've successfully used OpenSocial software to build new social solutions.</description>
<dc:date>2009-06-19T23:11:32Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>google, development, OpenSocial, enterprise, video, talk, clevermarks</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://code.google.com/intl/fr/events/io/sessions/OpenSocialEnterprise.html"><img border="0" src="http://blogmarks.net/screenshots/2009/06/19/3e7aaadaa0cd31359887662e5949b555.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://code.google.com/intl/fr/events/io/sessions/OpenSocialEnterprise.html">Google I/O - OpenSocial in the Enterprise</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">In the year and half since OpenSocial's public launch, there are now over 700 million end users of OpenSocial applications across numerous social sites (containers) around the world. With OpenSocial's proven global success in traditional social applications, the enterprise software community has now begun to realize its potential and build innovative solutions that cater to the enterprise. Join us for a session centered on how the enterprise software development community is successfully bringing social concepts and technology into the enterprise. Key enterprise players will present and demonstrate how they've successfully used OpenSocial software to build new social solutions.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/development">development</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/OpenSocial">OpenSocial</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/enterprise">enterprise</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/video">video</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/talk">talk</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/clevermarks">clevermarks</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058379955">Copy</a> | 
<a href="http://blogmarks.net/link/3244643">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058379897">
<title>Shindig - Welcome To Shindig!</title>
<link>http://incubator.apache.org/shindig/</link>
<description>What is Shindig?
Shindig is a container for hosting social application consisting of four parts:

    * Gadget Container JavaScript: core JavaScript foundation for general gadget functionality (read more about gadget functionality). This JavaScript manages security, communication, UI layout, and feature extensions, such as the OpenSocial API.
    * Gadget Rendering Server: used to render the gadget XML into JavaScript and HTML for the container to expose via the container JavaScript.
    * OpenSocial Container JavaScript: JavaScript environment that sits on top of the Gadget Container JavaScript and provides OpenSocial specific functionality (profiles, friends, activities, datastore).
    * OpenSocial Data Server: an implementation of the server interface to container-specific information, including the OpenSocial REST APIs, with clear extension points so others can connect it to their own backends.

Shindig is the reference implementation of OpenSocial API specifications, a standard set of Social Network APIs which includes:

    * Profiles
    * Relationships
    * Activities
    * Shared applications
    * Authentication
    * Authorization</description>
<dc:date>2009-06-19T20:41:01Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>network, application, server, api, xml, social network, apache, OpenSocial, clevermarks</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://incubator.apache.org/shindig/"><img border="0" src="http://blogmarks.net/screenshots/2009/06/19/33b674bef9b2ce6a3924896402e03e23.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://incubator.apache.org/shindig/">Shindig - Welcome To Shindig!</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2660069">4 other(s)</a> 
<p class="description">What is Shindig?
Shindig is a container for hosting social application consisting of four parts:

    * Gadget Container JavaScript: core JavaScript foundation for general gadget functionality (read more about gadget functionality). This JavaScript manages security, communication, UI layout, and feature extensions, such as the OpenSocial API.
    * Gadget Rendering Server: used to render the gadget XML into JavaScript and HTML for the container to expose via the container JavaScript.
    * OpenSocial Container JavaScript: JavaScript environment that sits on top of the Gadget Container JavaScript and provides OpenSocial specific functionality (profiles, friends, activities, datastore).
    * OpenSocial Data Server: an implementation of the server interface to container-specific information, including the OpenSocial REST APIs, with clear extension points so others can connect it to their own backends.

Shindig is the reference implementation of OpenSocial API specifications, a standard set of Social Network APIs which includes:

    * Profiles
    * Relationships
    * Activities
    * Shared applications
    * Authentication
    * Authorization</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/network">network</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/application">application</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/api">api</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xml">xml</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/social%2Bnetwork">social network</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/apache">apache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/OpenSocial">OpenSocial</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/clevermarks">clevermarks</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058379897">Copy</a> | 
<a href="http://blogmarks.net/link/2660069">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058374231">
<title>Powerpoint, Visio, Axure : Les Wireframes selon Superfiction</title>
<link>http://www.blogoergosum.com/247-powerpoint-visio-axure-les-wireframes-selon-superfiction</link>
<description>Les wireframes (ou zonings selon les agences) sont ces schémas fonctionnels qui premettent de présenter une maquette de site (ou autres) au client avant d’amorcer de manière effective la phase de création graphique.

Bien entendu chaque agence a ses recettes internes pour en faire.

Eric de Superfiction (expert es zonings) s’est penché sur le sujet et décortique l’art du Wireframe à travers l’étude de 3 acteurs majeurs : Microsoft Powerpoint, Microsoft Visio et Axure RP pro.</description>
<dc:date>2009-06-19T00:28:21Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>gui, tools, review, comparison, moa, graphical tools, wireframe</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.blogoergosum.com/247-powerpoint-visio-axure-les-wireframes-selon-superfiction"><img border="0" src="http://blogmarks.net/screenshots/2009/06/19/ee9ba576cc9ce415f38e20f4e2a49f93.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.blogoergosum.com/247-powerpoint-visio-axure-les-wireframes-selon-superfiction">Powerpoint, Visio, Axure : Les Wireframes selon Superfiction</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">Les wireframes (ou zonings selon les agences) sont ces schémas fonctionnels qui premettent de présenter une maquette de site (ou autres) au client avant d’amorcer de manière effective la phase de création graphique.

Bien entendu chaque agence a ses recettes internes pour en faire.

Eric de Superfiction (expert es zonings) s’est penché sur le sujet et décortique l’art du Wireframe à travers l’étude de 3 acteurs majeurs : Microsoft Powerpoint, Microsoft Visio et Axure RP pro.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/gui">gui</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tools">tools</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/review">review</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/comparison">comparison</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/moa">moa</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/graphical%2Btools">graphical tools</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/wireframe">wireframe</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058374231">Copy</a> | 
<a href="http://blogmarks.net/link/3239303">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058374224">
<title>GUUUI - Visio - the interaction designer's nail gun (3rd edition)</title>
<link>http://www.guuui.com/issues/02_07.php</link>
<description>This is a third edition of my article on using Visio for rapid prototyping for the web. The new edition includes a minor update of the GUUUI Web Prototyping Tool that eliminates a major shortcoming: the inability to create scrolling pages. The update also includes brand new sketchy interface widgets.</description>
<dc:date>2009-06-19T00:18:26Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>gui, specs, moa, tools, prototype, graphical tools</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.guuui.com/issues/02_07.php"><img border="0" src="http://blogmarks.net/screenshots/2009/06/19/b4708d22e6f2e51cd4b30a166310413c.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.guuui.com/issues/02_07.php">GUUUI - Visio - the interaction designer's nail gun (3rd edition)</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">This is a third edition of my article on using Visio for rapid prototyping for the web. The new edition includes a minor update of the GUUUI Web Prototyping Tool that eliminates a major shortcoming: the inability to create scrolling pages. The update also includes brand new sketchy interface widgets.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/gui">gui</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/specs">specs</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/moa">moa</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tools">tools</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/prototype">prototype</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/graphical%2Btools">graphical tools</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058374224">Copy</a> | 
<a href="http://blogmarks.net/link/3161013">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058368860">
<title>Un nouveau type de plugin pour Liferay 5 - Architectes IT</title>
<link>http://www.architectes.it/index.php/post/2009/05/03/Un-nouveau-type-de-plugin-pour-Liferay-5-:-les-hooks</link>
<description>Une des nouveautés de liferay 5 est l’ajout d’un nouveau type de plugin, nommé hook, dans le Plugin SDK. Il impacte fortement la façon de customiser liferay car il permet de changer le comportement et l’interface de liferay de manière plus intelligente.</description>
<dc:date>2009-06-17T16:36:57Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>liferay, portal, plugin, java, development</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.architectes.it/index.php/post/2009/05/03/Un-nouveau-type-de-plugin-pour-Liferay-5-:-les-hooks"><img border="0" src="http://blogmarks.net/screenshots/2009/06/17/5f066f1abaf3a4a968faa71d095804ac.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.architectes.it/index.php/post/2009/05/03/Un-nouveau-type-de-plugin-pour-Liferay-5-:-les-hooks">Un nouveau type de plugin pour Liferay 5 - Architectes IT</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">Une des nouveautés de liferay 5 est l’ajout d’un nouveau type de plugin, nommé hook, dans le Plugin SDK. Il impacte fortement la façon de customiser liferay car il permet de changer le comportement et l’interface de liferay de manière plus intelligente.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/liferay">liferay</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/portal">portal</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/plugin">plugin</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/java">java</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/development">development</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058368860">Copy</a> | 
<a href="http://blogmarks.net/link/3234402">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058360169">
<title>TUTO: utiliser son iphone comme modem (avec et sans jailbreak) version pc</title>
<link>http://forum.frenchiphone.com/index.php?topic=25227.0</link>
<description>Salutations, devant la difficulté de certains à utiliser leur précieux en &quot;mode modem&quot; j'ai décidé de regrouper les tutos que j'ai pu trouver sur le web pour en faire un plus compact. Je rapelle que nous utilisons l'iphone comme un proxy et non véritablement comme un modem et que de ce fait c'est sensé ne pas etre détecté, après je suis pas assez callé en informatique désolé^^. Ce tuto est optimisé vista, cependant la méthode sous xp est sensiblement la meme, vous aurez juste à chercher les options.</description>
<dc:date>2009-06-11T15:10:21Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>web, proxy, iphone, 3g, network, tutorial</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://forum.frenchiphone.com/index.php?topic=25227.0"><img border="0" src="http://blogmarks.net/screenshots/2009/06/11/6225047db447240d758b45a2dc532029.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://forum.frenchiphone.com/index.php?topic=25227.0">TUTO: utiliser son iphone comme modem (avec et sans jailbreak) version pc</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">Salutations, devant la difficulté de certains à utiliser leur précieux en "mode modem" j'ai décidé de regrouper les tutos que j'ai pu trouver sur le web pour en faire un plus compact. Je rapelle que nous utilisons l'iphone comme un proxy et non véritablement comme un modem et que de ce fait c'est sensé ne pas etre détecté, après je suis pas assez callé en informatique désolé^^. Ce tuto est optimisé vista, cependant la méthode sous xp est sensiblement la meme, vous aurez juste à chercher les options.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/proxy">proxy</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/iphone">iphone</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/3g">3g</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/network">network</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tutorial">tutorial</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058360169">Copy</a> | 
<a href="http://blogmarks.net/link/3226911">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058360167">
<title>Red Kaffe, C.A. &gt; Blog - Utiliser votre iPhone/Smartphone comme modem 3G/3G ...</title>
<link>http://www.redkaffe.com/Blog/tabid/72/EntryId/170/Utiliser-votre-iPhone-Smartphone-comme-modem-3G-3G.aspx</link>
<description>Bonsoir à tous, je fais juste un petit post pour dire que je viens de trouver un logiciel très utile et très simple à utiliser. Il permet de connecter en WiFi votre  iPhone3G ou votre smartphone équipé de connectique 3G/3G+ et WIFI, avec votre netbook/laptop et de bénéficier ainsi de la connectivité 3G/3G+. Cela peut paraître anodin, mais avec un iPhone 3G, muni d' un plan illimité d' Internet via la 3G, cela permet tout simplement de se connecter au net en l' absence d' autre connexion...</description>
<dc:date>2009-06-11T15:08:44Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>iphone, 3g, network, tutorial</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.redkaffe.com/Blog/tabid/72/EntryId/170/Utiliser-votre-iPhone-Smartphone-comme-modem-3G-3G.aspx"><img border="0" src="http://blogmarks.net/screenshots/2009/06/11/4e8c99b247e3448dce6f2141c7b3c015.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.redkaffe.com/Blog/tabid/72/EntryId/170/Utiliser-votre-iPhone-Smartphone-comme-modem-3G-3G.aspx">Red Kaffe, C.A. &gt; Blog - Utiliser votre iPhone/Smartphone comme modem 3G/3G ...</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">Bonsoir à tous, je fais juste un petit post pour dire que je viens de trouver un logiciel très utile et très simple à utiliser. Il permet de connecter en WiFi votre  iPhone3G ou votre smartphone équipé de connectique 3G/3G+ et WIFI, avec votre netbook/laptop et de bénéficier ainsi de la connectivité 3G/3G+. Cela peut paraître anodin, mais avec un iPhone 3G, muni d' un plan illimité d' Internet via la 3G, cela permet tout simplement de se connecter au net en l' absence d' autre connexion...</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/iphone">iphone</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/3g">3g</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/network">network</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tutorial">tutorial</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058360167">Copy</a> | 
<a href="http://blogmarks.net/link/3226909">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058353877">
<title>Protocol Reference - Google Data APIs - Google Code</title>
<link>http://code.google.com/intl/fr/apis/gdata/docs/2.0/reference.html</link>
<description>This document describes the protocol used by the Google Data APIs, including information about what a query looks like, what results look like, and so on.</description>
<dc:date>2009-06-08T20:29:12Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>google, atom, protocol, Atom Publishing Protocol, rest, architecture</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://code.google.com/intl/fr/apis/gdata/docs/2.0/reference.html"><img border="0" src="http://blogmarks.net/screenshots/2009/06/08/8d786ef31999487b694691c2bed34e38.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://code.google.com/intl/fr/apis/gdata/docs/2.0/reference.html">Protocol Reference - Google Data APIs - Google Code</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">This document describes the protocol used by the Google Data APIs, including information about what a query looks like, what results look like, and so on.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/atom">atom</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/protocol">protocol</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Atom%2BPublishing%2BProtocol">Atom Publishing Protocol</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/architecture">architecture</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058353877">Copy</a> | 
<a href="http://blogmarks.net/link/3222056">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058353873">
<title>Google Data APIs - Google Code</title>
<link>http://code.google.com/intl/fr/apis/gdata/</link>
<description>The Google Data APIs provide a simple standard protocol for reading and writing data on the web.

These REST-style APIs are based on the Atom Publishing Protocol (AtomPub), using the standard Atom syndication format to represent data and HTTP to handle communication. The Google Data API protocol also extends AtomPub for processing queries, authentication, batch requests, and providing alternate output formats (JSON, RSS).

Many Google services support the Google Data API protocol</description>
<dc:date>2009-06-08T20:27:14Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>google, atom, protocol, Atom Publishing Protocol, rest, architecture</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://code.google.com/intl/fr/apis/gdata/"><img border="0" src="http://blogmarks.net/screenshots/2009/06/08/afe134986ac15704b4ff4802a887f4aa.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://code.google.com/intl/fr/apis/gdata/">Google Data APIs - Google Code</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">The Google Data APIs provide a simple standard protocol for reading and writing data on the web.

These REST-style APIs are based on the Atom Publishing Protocol (AtomPub), using the standard Atom syndication format to represent data and HTTP to handle communication. The Google Data API protocol also extends AtomPub for processing queries, authentication, batch requests, and providing alternate output formats (JSON, RSS).

Many Google services support the Google Data API protocol</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/atom">atom</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/protocol">protocol</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Atom%2BPublishing%2BProtocol">Atom Publishing Protocol</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/architecture">architecture</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058353873">Copy</a> | 
<a href="http://blogmarks.net/link/3222053">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058353872">
<title>Google Data APIs Overview - Google Data APIs - Google Code</title>
<link>http://code.google.com/intl/fr/apis/gdata/overview.html</link>
<description>The Google Data APIs provide a simple standard protocol for reading and writing data on the web.

The Data APIs use either of two standard XML-based syndication formats: Atom or RSS. They also have a feed-publishing system that consists of the Atom publishing protocol plus some extensions (using Atom's standard extension model) for handling queries.</description>
<dc:date>2009-06-08T20:26:42Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>google, atom, protocol, Atom Publishing Protocol, rest, architecture</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://code.google.com/intl/fr/apis/gdata/overview.html"><img border="0" src="http://blogmarks.net/screenshots/2009/06/08/8d3533f8467521aa2c13977b70eef268.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://code.google.com/intl/fr/apis/gdata/overview.html">Google Data APIs Overview - Google Data APIs - Google Code</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">The Google Data APIs provide a simple standard protocol for reading and writing data on the web.

The Data APIs use either of two standard XML-based syndication formats: Atom or RSS. They also have a feed-publishing system that consists of the Atom publishing protocol plus some extensions (using Atom's standard extension model) for handling queries.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/atom">atom</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/protocol">protocol</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Atom%2BPublishing%2BProtocol">Atom Publishing Protocol</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/architecture">architecture</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058353872">Copy</a> | 
<a href="http://blogmarks.net/link/3222052">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058353828">
<title>Getting to know the Atom Publishing Protocol, Part 1: Create and edit Web resources with the Atom Publishing Protocol</title>
<link>http://www.ibm.com/developerworks/library/x-atompp1/</link>
<description>The Atom Publishing Protocol is an important new standard for content publishing and management. In this article, explore a high-level overview of the protocol and its basic operation and capabilities.</description>
<dc:date>2009-06-08T20:03:55Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>atom, protocol, rest, clevermarks, architecture, Atom Publishing Protocol</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ibm.com/developerworks/library/x-atompp1/"><img border="0" src="http://blogmarks.net/screenshots/2009/06/08/95079c819c6f69a180dd3a40986a2b2d.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ibm.com/developerworks/library/x-atompp1/">Getting to know the Atom Publishing Protocol, Part 1: Create and edit Web resources with the Atom Publishing Protocol</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">The Atom Publishing Protocol is an important new standard for content publishing and management. In this article, explore a high-level overview of the protocol and its basic operation and capabilities.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/atom">atom</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/protocol">protocol</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/clevermarks">clevermarks</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/architecture">architecture</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Atom%2BPublishing%2BProtocol">Atom Publishing Protocol</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058353828">Copy</a> | 
<a href="http://blogmarks.net/link/3222014">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058340062">
<title>Google Wave : Plateforme de communication centralisée</title>
<link>http://www.zorgloob.com/2009/05/google-wave-platteforme-de.asp</link>
<description>Aujourd'hui à la conférence Google I/O (celle ou les participants se sont vu offrir un téléphone HTC Magic, aussi nommé Google Ion, gratuitement), une annonce de Google n'est pas passée inaperçue. Google veut avec Wave (vague en anglais) révolutionner la façon dont on communique sur le net. L'ambition est immense, le projet également, mais l'enthousiasme généré par les développeurs suite à cette annonce donne de grand espoirs. Plus une communauté est active sur un projet, plus celui-ci peut réussir. Google a testé cet effet avec Android, et veut maintenant reproduire le schéma.</description>
<dc:date>2009-05-29T02:29:02Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>google, collab, clevermarks, social network</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.zorgloob.com/2009/05/google-wave-platteforme-de.asp"><img border="0" src="http://blogmarks.net/screenshots/2009/05/29/9777b71634e51644223126edb88f941e.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.zorgloob.com/2009/05/google-wave-platteforme-de.asp">Google Wave : Plateforme de communication centralisée</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3210200">1 other(s)</a> 
<p class="description">Aujourd'hui à la conférence Google I/O (celle ou les participants se sont vu offrir un téléphone HTC Magic, aussi nommé Google Ion, gratuitement), une annonce de Google n'est pas passée inaperçue. Google veut avec Wave (vague en anglais) révolutionner la façon dont on communique sur le net. L'ambition est immense, le projet également, mais l'enthousiasme généré par les développeurs suite à cette annonce donne de grand espoirs. Plus une communauté est active sur un projet, plus celui-ci peut réussir. Google a testé cet effet avec Android, et veut maintenant reproduire le schéma.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/collab">collab</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/clevermarks">clevermarks</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/social%2Bnetwork">social network</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058340062">Copy</a> | 
<a href="http://blogmarks.net/link/3210200">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058299683">
<title>Apache CouchDB: Introduction</title>
<link>http://couchdb.apache.org/docs/intro.html</link>
<description>What CouchDB is

    * A document database server, accessible via a RESTful JSON API.
    * Ad-hoc and schema-free with a flat address space.
    * Distributed, featuring robust, incremental replication with bi-directional conflict detection and management.
    * Query-able and index-able, featuring a table oriented reporting engine that uses Javascript as a query language.

What it is Not

    * A relational database.
    * A replacement for relational databases.
    * An object-oriented database. Or more specifically, meant to function as a seamless persistence layer for an OO programming language.</description>
<dc:date>2009-04-26T23:28:41Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>apache, database, xml, document, rest, api, json</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://couchdb.apache.org/docs/intro.html"><img border="0" src="http://blogmarks.net/screenshots/2009/04/26/5f5f745bd802675ec60c562daca63939.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://couchdb.apache.org/docs/intro.html">Apache CouchDB: Introduction</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">What CouchDB is

    * A document database server, accessible via a RESTful JSON API.
    * Ad-hoc and schema-free with a flat address space.
    * Distributed, featuring robust, incremental replication with bi-directional conflict detection and management.
    * Query-able and index-able, featuring a table oriented reporting engine that uses Javascript as a query language.

What it is Not

    * A relational database.
    * A replacement for relational databases.
    * An object-oriented database. Or more specifically, meant to function as a seamless persistence layer for an OO programming language.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/apache">apache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/database">database</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xml">xml</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/document">document</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/api">api</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/json">json</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058299683">Copy</a> | 
<a href="http://blogmarks.net/link/3175852">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058271040">
<title>Facebook PHP Tutorial</title>
<link>http://www.merchantos.com/makebeta/facebook/facebook-php-tutorial/</link>
<description>I will cover the basics of using the Facebook PHP library and how to get your application started, including:

   1. Installing The Facebook Developer Application
   2. Downloading The Facebook PHP Client Library
   3. Creating Your Application
   4. Hello Facebook! Example
   5. FBML - Facebook Markup Language
   6. Using the Facebook API</description>
<dc:date>2009-04-11T18:43:16Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>tutorial, library, api, facebook, php, social network, development</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.merchantos.com/makebeta/facebook/facebook-php-tutorial/"><img border="0" src="http://blogmarks.net/screenshots/2009/04/11/81716f85d55f009221b8c338b19ab9a6.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.merchantos.com/makebeta/facebook/facebook-php-tutorial/">Facebook PHP Tutorial</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">I will cover the basics of using the Facebook PHP library and how to get your application started, including:

   1. Installing The Facebook Developer Application
   2. Downloading The Facebook PHP Client Library
   3. Creating Your Application
   4. Hello Facebook! Example
   5. FBML - Facebook Markup Language
   6. Using the Facebook API</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tutorial">tutorial</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/library">library</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/api">api</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/facebook">facebook</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/php">php</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/social%2Bnetwork">social network</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/development">development</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058271040">Copy</a> | 
<a href="http://blogmarks.net/link/2806577">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058271038">
<title>Write your first FaceBook App!</title>
<link>http://www.theliveweb.net/blog/2007/10/28/write-your-first-facebook-app/</link>
<description>I recently tried to get my hands dirty with Facebook application development platform. I know there are a bunch of resources available on the web to help you in the process, but when I was trying get my tiny app to work, I realized there were a few things which aren’t explained too well on http://developer.facebook.com/. I am writing down the step-by-step guide that you can use to create your first Facebook application and join the club!</description>
<dc:date>2009-04-11T18:43:33Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>web, facebook, development, php, social network, tutorial</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.theliveweb.net/blog/2007/10/28/write-your-first-facebook-app/"><img border="0" src="http://blogmarks.net/screenshots/2009/04/11/5bdf06ef684e49a42ac9794e6d93c266.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.theliveweb.net/blog/2007/10/28/write-your-first-facebook-app/">Write your first FaceBook App!</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">I recently tried to get my hands dirty with Facebook application development platform. I know there are a bunch of resources available on the web to help you in the process, but when I was trying get my tiny app to work, I realized there were a few things which aren’t explained too well on http://developer.facebook.com/. I am writing down the step-by-step guide that you can use to create your first Facebook application and join the club!</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/facebook">facebook</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/development">development</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/php">php</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/social%2Bnetwork">social network</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tutorial">tutorial</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058271038">Copy</a> | 
<a href="http://blogmarks.net/link/3153250">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058271032">
<title>10 Things That Would Have Been Nice to Know When Starting My Facebook Application: An Entry in padrenel's Journal and Blog at the Experience Project</title>
<link>http://padrenel.blogs.experienceproject.com/3459.html</link>
<description>Alright, just finished my first Facebook app.  Some pretty cool functionality they've built there, and it's mostly pretty straightforward to work with, but the documentation is lagging in some areas.  Here's a few things I learned along the way, in no particular order - most may seem like no-brainers, but I know I lost some time to most of these!</description>
<dc:date>2009-04-11T18:30:32Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>facebook, development, social network, mashup</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://padrenel.blogs.experienceproject.com/3459.html"><img border="0" src="http://blogmarks.net/screenshots/2009/04/11/187c407f35f246169fd19e7228820e9f.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://padrenel.blogs.experienceproject.com/3459.html">10 Things That Would Have Been Nice to Know When Starting My Facebook Application: An Entry in padrenel's Journal and Blog at the Experience Project</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">Alright, just finished my first Facebook app.  Some pretty cool functionality they've built there, and it's mostly pretty straightforward to work with, but the documentation is lagging in some areas.  Here's a few things I learned along the way, in no particular order - most may seem like no-brainers, but I know I lost some time to most of these!</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/facebook">facebook</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/development">development</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/social%2Bnetwork">social network</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mashup">mashup</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058271032">Copy</a> | 
<a href="http://blogmarks.net/link/3153245">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058269680">
<title>Main Page - Facebook Developers Wiki</title>
<link>http://wiki.developers.facebook.com/index.php/Main_Page</link>
<description>The Facebook Developer wiki is a reference for developers interested in Facebook Platform. Facebook Platform is a standards-based Web service with methods for accessing and contributing Facebook data. We've made the methods as easy to understand as possible, and this wiki includes full documentation to help you learn more. </description>
<dc:date>2009-04-10T20:16:31Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>web services, facebook, development, howto, web 2.0, social network</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://wiki.developers.facebook.com/index.php/Main_Page"><img border="0" src="http://blogmarks.net/screenshots/2009/04/10/97d86de74fa443662d4277a8c3d912d5.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://wiki.developers.facebook.com/index.php/Main_Page">Main Page - Facebook Developers Wiki</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2295725">1 other(s)</a> 
<p class="description">The Facebook Developer wiki is a reference for developers interested in Facebook Platform. Facebook Platform is a standards-based Web service with methods for accessing and contributing Facebook data. We've made the methods as easy to understand as possible, and this wiki includes full documentation to help you learn more. </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web%2Bservices">web services</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/facebook">facebook</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/development">development</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/howto">howto</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web%2B2.0">web 2.0</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/social%2Bnetwork">social network</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058269680">Copy</a> | 
<a href="http://blogmarks.net/link/2295725">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>