<?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/marks/search/case">
<title>Public marks with search case</title>
<description>Public marks with search case</description>
<link>http://blogmarks.net/marks/search/case</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058575597"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058560162"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058553989"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058550404"/>
<rdf:li resource="http://blogmarks.net/api/user/ms_michel/mark/1058544516"/>
<rdf:li resource="http://blogmarks.net/api/user/srcmax/mark/1058539527"/>
<rdf:li resource="http://blogmarks.net/api/user/gregg/mark/1058539506"/>
<rdf:li resource="http://blogmarks.net/api/user/srcmax/mark/1058528305"/>
<rdf:li resource="http://blogmarks.net/api/user/alamat/mark/1058522168"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058512194"/>
<rdf:li resource="http://blogmarks.net/api/user/vrossign/mark/1058511732"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058504723"/>
<rdf:li resource="http://blogmarks.net/api/user/tadeufilippini/mark/1058501395"/>
<rdf:li resource="http://blogmarks.net/api/user/marco/mark/1058499274"/>
<rdf:li resource="http://blogmarks.net/api/user/decembre/mark/1058547795"/>
<rdf:li resource="http://blogmarks.net/api/user/tadeufilippini/mark/1058492882"/>
<rdf:li resource="http://blogmarks.net/api/user/ericpaul/mark/1058481229"/>
<rdf:li resource="http://blogmarks.net/api/user/bamthomas/mark/1058477163"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058475331"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058471279"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058469200"/>
<rdf:li resource="http://blogmarks.net/api/user/bs_pepper/mark/1058467297"/>
<rdf:li resource="http://blogmarks.net/api/user/paulantoinem/mark/1058470261"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058435430"/>
<rdf:li resource="http://blogmarks.net/api/user/decembre/mark/1058547970"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058575597">
<title>BBC - Digital Revolution Blog: Rushes Sequences - Biz Stone and Evan Williams interview - USA (Video)</title>
<link>http://www.bbc.co.uk/blogs/digitalrevolution/2009/11/rushes-sequences-biz-stone-and.shtml</link>
<description>&lt;blockquote&gt;&lt;p&gt;there was a popular blogger and he also had a Twitter account and he was complaining that his cable was out, and he was I'm going to write about this cable company, Compass and how terrible they are and its going to be the number one search result in, in search engines for year to come.  And they were monitoring Twitter search for any mentions of they're brand name.  And they saw that within a few minutes and they replied to him on Twitter, and they said what seems to be the problem, they were going to send a van out to your house.  And they had his cable fixed in like 30 minutes, so the next day the blog post was, Compass has great customer service, and it was like a, you know a complete reversal and we were like wow, they're really smart about it,&lt;/p&gt;&lt;/blockquote&gt;

*soupir* Ce que la marque a fait est un coup médiatique pas une réponse qui est « scalable » Un compte twitter pour une marque ne va pas remplacer le service SAV (avec des centaines de personnes derrière le téléphone). La qualité du service et la réponse de la marque étaient bonnes car elles étaient un coup unique, et réalisées par une personne du service Communications de l'entreprise.

Imaginons maintenant les milliers d'appels quotidiens pour une grande marque. Twitter ? Des centaines de comptes twitter ? Des centaines de gens pour y répondre. Baisse de la qualité et du service, baisse de la croyance en l'opération marketing, retour à la case départ. Qu'est-ce qui manque ? La communauté !

Un social media n'existe que si la communauté devient autonome.</description>
<dc:date>2009-11-08T12:31:37Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>societé, socialnetwork</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.bbc.co.uk/blogs/digitalrevolution/2009/11/rushes-sequences-biz-stone-and.shtml"><img border="0" src="http://blogmarks.net/screenshots/2009/11/08/f5459f0c355bbed290e4c3b71f3e20b0.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.bbc.co.uk/blogs/digitalrevolution/2009/11/rushes-sequences-biz-stone-and.shtml">BBC - Digital Revolution Blog: Rushes Sequences - Biz Stone and Evan Williams interview - USA (Video)</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>there was a popular blogger and he also had a Twitter account and he was complaining that his cable was out, and he was I'm going to write about this cable company, Compass and how terrible they are and its going to be the number one search result in, in search engines for year to come.  And they were monitoring Twitter search for any mentions of they're brand name.  And they saw that within a few minutes and they replied to him on Twitter, and they said what seems to be the problem, they were going to send a van out to your house.  And they had his cable fixed in like 30 minutes, so the next day the blog post was, Compass has great customer service, and it was like a, you know a complete reversal and we were like wow, they're really smart about it,</p></blockquote>

*soupir* Ce que la marque a fait est un coup médiatique pas une réponse qui est « scalable » Un compte twitter pour une marque ne va pas remplacer le service SAV (avec des centaines de personnes derrière le téléphone). La qualité du service et la réponse de la marque étaient bonnes car elles étaient un coup unique, et réalisées par une personne du service Communications de l'entreprise.

Imaginons maintenant les milliers d'appels quotidiens pour une grande marque. Twitter ? Des centaines de comptes twitter ? Des centaines de gens pour y répondre. Baisse de la qualité et du service, baisse de la croyance en l'opération marketing, retour à la case départ. Qu'est-ce qui manque ? La communauté !

Un social media n'existe que si la communauté devient autonome.</div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/societ%25C3%25A9">societé</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/socialnetwork">socialnetwork</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058575597">Copy</a> | 
<a href="http://blogmarks.net/link/3403445">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058560162">
<title>John Nack on Adobe: Lightroom 3.0 public beta arrives!</title>
<link>http://blogs.adobe.com/jnack/2009/10/lightroom_30_public_beta_arrives.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;karl — 4:14 AM on October 22, 2009 Reply to this comment&lt;/p&gt;&lt;p&gt;Hmmm…&lt;/p&gt;&lt;p&gt;In the available doc, I have not seen any geolocation UI for the photos by picking up a location on a map. See Flickr system and/or HoudahGeo http://www.houdah.com/houdahGeo/&lt;/p&gt;&lt;p&gt;Is it really the case?&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-10-22T11:16:20Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>flickr, geolocation, photographie, adobe, lightroom</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://blogs.adobe.com/jnack/2009/10/lightroom_30_public_beta_arrives.html"><img border="0" src="http://blogmarks.net/screenshots/2009/10/22/9309db4e8b90244e2a9ccc6475edd2f7.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://blogs.adobe.com/jnack/2009/10/lightroom_30_public_beta_arrives.html">John Nack on Adobe: Lightroom 3.0 public beta arrives!</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>karl — 4:14 AM on October 22, 2009 Reply to this comment</p><p>Hmmm…</p><p>In the available doc, I have not seen any geolocation UI for the photos by picking up a location on a map. See Flickr system and/or HoudahGeo http://www.houdah.com/houdahGeo/</p><p>Is it really the case?</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/flickr">flickr</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/geolocation">geolocation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/photographie">photographie</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/adobe">adobe</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/lightroom">lightroom</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058560162">Copy</a> | 
<a href="http://blogmarks.net/link/3390907">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058553989">
<title>lxml vs. ElementTree « michael schurter</title>
<link>http://michael.susens-schurter.com/blog/2009/10/14/lxml-vs-elementtree/</link>
<description>&lt;blockquote&gt;&lt;p&gt;While lxml has some excellent benchmarks about the speed of lxml.etree vs. ElementTree, I wanted to run some tests that were as close as possible to my own use case (fairly simple multi-megabyte XML files).&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-10-18T18:36:05Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>lxml, elementtree, benchmark</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://michael.susens-schurter.com/blog/2009/10/14/lxml-vs-elementtree/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/18/5f5223d38667e99b0042331de89298db.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://michael.susens-schurter.com/blog/2009/10/14/lxml-vs-elementtree/">lxml vs. ElementTree « michael schurter</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>While lxml has some excellent benchmarks about the speed of lxml.etree vs. ElementTree, I wanted to run some tests that were as close as possible to my own use case (fairly simple multi-megabyte XML files).</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/lxml">lxml</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/elementtree">elementtree</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/benchmark">benchmark</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058553989">Copy</a> | 
<a href="http://blogmarks.net/link/3386812">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058550404">
<title>Implementers' Draft: Portable Contacts 1.0 Draft C</title>
<link>http://portablecontacts.net/draft-spec.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;This API defines a language- and platform- neutral protocol for Consumers to request address book, profile, and friends-list information from Service Providers. As a protocol, it is intended to be easy to understand and implement, either as a Service Provider or Consumer, using any language or platform of choice. It is also intended to be implemented by both individuals and small services as well as large providers, in any case where a service contains data about who a user knows and wishes to make that information portable, under the user's control.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-10-15T01:06:30Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>addressbook, api, FreeData</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://portablecontacts.net/draft-spec.html"><img border="0" src="http://blogmarks.net/screenshots/2009/10/15/fafee23ed86fec3cdbe705707815e215.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://portablecontacts.net/draft-spec.html">Implementers' Draft: Portable Contacts 1.0 Draft C</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>This API defines a language- and platform- neutral protocol for Consumers to request address book, profile, and friends-list information from Service Providers. As a protocol, it is intended to be easy to understand and implement, either as a Service Provider or Consumer, using any language or platform of choice. It is also intended to be implemented by both individuals and small services as well as large providers, in any case where a service contains data about who a user knows and wishes to make that information portable, under the user's control.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/addressbook">addressbook</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/FreeData">FreeData</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058550404">Copy</a> | 
<a href="http://blogmarks.net/link/3383748">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ms_michel/mark/1058544516">
<title>A S#arp Project Case Study </title>
<link>http://groups.google.com/group/sharp-architecture/browse_thread/thread/9df324a3dc36decb</link>
<description>Un ensemble de billets qui relatent les problèmes rencontrés, les solutions et les leçons apprises tout au long de la réalisation du site de e-commerce Francy Dress Outfitters (http://www.fancydressoutfitters.co.uk/) avec le framework S#arp Architecture</description>
<dc:date>2009-10-10T12:30:01Z</dc:date>
<dc:author>ms_michel</dc:author>
<dc:subject>.net, mvc</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://groups.google.com/group/sharp-architecture/browse_thread/thread/9df324a3dc36decb"><img border="0" src="http://blogmarks.net/screenshots/2009/10/10/605ef96827798b491414d1681fcc3653.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://groups.google.com/group/sharp-architecture/browse_thread/thread/9df324a3dc36decb">A S#arp Project Case Study </a></h4>
 
by <a href="http://blogmarks.net/user/ms_michel">ms_michel</a> 
<p class="description">Un ensemble de billets qui relatent les problèmes rencontrés, les solutions et les leçons apprises tout au long de la réalisation du site de e-commerce Francy Dress Outfitters (http://www.fancydressoutfitters.co.uk/) avec le framework S#arp Architecture</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/.net">.net</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mvc">mvc</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058544516">Copy</a> | 
<a href="http://blogmarks.net/link/3378792">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/srcmax/mark/1058539527">
<title>Viral Test - Viral Case</title>
<link>http://viral-test.com/</link>
<description>Bienvenue sur le premier film viral ouvert à tous les annonceurs : le Viral Test</description>
<dc:date>2009-10-05T09:55:45Z</dc:date>
<dc:author>srcmax</dc:author>
<dc:subject>marketing viral</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://viral-test.com/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://viral-test.com/">Viral Test - Viral Case</a></h4>
 
by <a href="http://blogmarks.net/user/srcmax">srcmax</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3374686">1 other(s)</a> 
<p class="description">Bienvenue sur le premier film viral ouvert à tous les annonceurs : le Viral Test</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/marketing%2Bviral">marketing viral</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058539527">Copy</a> | 
<a href="http://blogmarks.net/link/3374686">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/gregg/mark/1058539506">
<title>Viral Test - Viral Case</title>
<link>http://viral-test.com/</link>
<description></description>
<dc:date>2009-10-05T09:31:22Z</dc:date>
<dc:author>gregg</dc:author>
<dc:subject>viral</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://viral-test.com/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://viral-test.com/">Viral Test - Viral Case</a></h4>
 
by <a href="http://blogmarks.net/user/gregg">gregg</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3374686">1 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/viral">viral</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058539506">Copy</a> | 
<a href="http://blogmarks.net/link/3374686">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/srcmax/mark/1058528305">
<title>In Case You Forgot: IE6 Still Holds 25% of the Browser Market</title>
<link>http://mashable.com/2009/10/02/ie6-market-share/</link>
<description>&lt;blockquote&gt;
&lt;p&gt;All of this makes it easy to forget what browser is still dominating the market. According to Net Application’s Market Share data, that browser is Internet Explorer 6 (Internet Explorer 6.0), released in August 2001.&lt;/p&gt;
&lt;/blockquote&gt;</description>
<dc:date>2009-10-02T14:25:35Z</dc:date>
<dc:author>srcmax</dc:author>
<dc:subject>browser, ie6, standards</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://mashable.com/2009/10/02/ie6-market-share/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/02/c591195f3af72f844531c0b70497b579.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://mashable.com/2009/10/02/ie6-market-share/">In Case You Forgot: IE6 Still Holds 25% of the Browser Market</a></h4>
 
by <a href="http://blogmarks.net/user/srcmax">srcmax</a> 
<div class="description"><blockquote>
<p>All of this makes it easy to forget what browser is still dominating the market. According to Net Application’s Market Share data, that browser is Internet Explorer 6 (Internet Explorer 6.0), released in August 2001.</p>
</blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/browser">browser</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ie6">ie6</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/standards">standards</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058528305">Copy</a> | 
<a href="http://blogmarks.net/link/3363864">React (1)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/alamat/mark/1058522168">
<title>Help Flood Victims in the Philippines </title>
<link>http://paniwala.com/help-flood-victims/</link>
<description>This will be short.

I’m sending out an appeal to the world.

As I write this article, thousands of people are still trapped in the floodwaters of typhoon Ondoy—or in relocation sites that have no food and drinking water. (Just in case you don’t know anything about what’s happening in Metro Manila and Rizal </description>
<dc:date>2009-09-28T08:07:16Z</dc:date>
<dc:author>alamat</dc:author>
<dc:subject>flood, help, prayers, victims</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://paniwala.com/help-flood-victims/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/28/5c74f971e2e3813871bb2ff1fc31581d.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://paniwala.com/help-flood-victims/">Help Flood Victims in the Philippines </a></h4>
 
by <a href="http://blogmarks.net/user/alamat">alamat</a> 
<p class="description">This will be short.

I’m sending out an appeal to the world.

As I write this article, thousands of people are still trapped in the floodwaters of typhoon Ondoy—or in relocation sites that have no food and drinking water. (Just in case you don’t know anything about what’s happening in Metro Manila and Rizal </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/flood">flood</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/help">help</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/prayers">prayers</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/victims">victims</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058522168">Copy</a> | 
<a href="http://blogmarks.net/link/3358286">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058512194">
<title>Cocoa with Love: WhereIsMyMac, a Snow Leopard CoreLocation project</title>
<link>http://cocoawithlove.com/2009/09/whereismymac-snow-leopard-corelocation.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;In Snow Leopard, you can ask for the computer's location. Without a GPS, how accurate could that be? The answer in my case is: very accurate. In this post, I'll show you how to write a CoreLocation app for the Mac that shows the current location in Google Maps, so you can see exactly where your computer thinks it is.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-09-21T23:11:48Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>opacite, corelocation, cocoa, macosx, geolocation</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://cocoawithlove.com/2009/09/whereismymac-snow-leopard-corelocation.html"><img border="0" src="http://blogmarks.net/screenshots/2009/09/21/75d5e96cdf8ef363a69c0e1fda7b6a11.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://cocoawithlove.com/2009/09/whereismymac-snow-leopard-corelocation.html">Cocoa with Love: WhereIsMyMac, a Snow Leopard CoreLocation project</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>In Snow Leopard, you can ask for the computer's location. Without a GPS, how accurate could that be? The answer in my case is: very accurate. In this post, I'll show you how to write a CoreLocation app for the Mac that shows the current location in Google Maps, so you can see exactly where your computer thinks it is.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opacite">opacite</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/corelocation">corelocation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cocoa">cocoa</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/macosx">macosx</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/geolocation">geolocation</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058512194">Copy</a> | 
<a href="http://blogmarks.net/link/3349506">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/vrossign/mark/1058511732">
<title>Showcase of Case Studies in Design Portfolios « Smashing Magazine</title>
<link>http://www.smashingmagazine.com/2009/09/20/showcase-of-case-studies-in-design-portfolios/</link>
<description></description>
<dc:date>2009-09-21T11:22:30Z</dc:date>
<dc:author>vrossign</dc:author>
<dc:subject>design, showcase, portfolios, case, stuides, case studies</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.smashingmagazine.com/2009/09/20/showcase-of-case-studies-in-design-portfolios/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/21/2f64b6802ac0c0aa7d385b0e04c11e63.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.smashingmagazine.com/2009/09/20/showcase-of-case-studies-in-design-portfolios/">Showcase of Case Studies in Design Portfolios « Smashing Magazine</a></h4>
 
by <a href="http://blogmarks.net/user/vrossign">vrossign</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/design">design</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/showcase">showcase</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/portfolios">portfolios</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/case">case</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/stuides">stuides</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/case%2Bstudies">case studies</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058511732">Copy</a> | 
<a href="http://blogmarks.net/link/3349148">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058504723">
<title>Case Study: NPR.org — AIGA | the professional association for design</title>
<link>http://www.aiga.org/content.cfm/case-study-npr-org</link>
<description>&lt;blockquote&gt;&lt;p&gt;We learned a lot through experimentation with a working prototype; we had a staging server set up that mirrored the actual site and was pulling from live databases. This enabled editors to publish actual content via the prototype, allowing us to identify bugs in the design and editorial workflows before launch.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-09-16T03:52:53Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>design, prototype</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.aiga.org/content.cfm/case-study-npr-org"><img border="0" src="http://blogmarks.net/screenshots/2009/09/21/9ce1a66fe96cdf8bca3f04141679e69a.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.aiga.org/content.cfm/case-study-npr-org">Case Study: NPR.org — AIGA | the professional association for design</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>We learned a lot through experimentation with a working prototype; we had a staging server set up that mirrored the actual site and was pulling from live databases. This enabled editors to publish actual content via the prototype, allowing us to identify bugs in the design and editorial workflows before launch.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/design">design</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/prototype">prototype</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058504723">Copy</a> | 
<a href="http://blogmarks.net/link/3343540">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/tadeufilippini/mark/1058501395">
<title>Cambridge Grammar for First Certificate (book audio)</title>
<link>http://www.ingilizcepratik.net/cambridge-grammar-for-first-certificate-book-audio-t-18386.html</link>
<description>Cambridge Grammar for First Certificate (book audio)

Intermediate to Upper-intermediate

This book provides complete coverage of the grammar needed for the Cambridge FCE exam, and develops listening skills at the same time. It includes the full range of FCE exam tasks from the Reading, Writing, Listening, and Use of English papers, and contains helpful grammar explanations and a grammar glossary.

Contents
1. Present tenses: Present simple, present continuous, state verbs;
2. Past tenses: Past simple, past continuous, used to (and to be used to), would;
3. Present perfect simple and past simple: Present perfect and past simple, present perfect simple and continuous;
4. Past perfect: Past perfect simple and continuous;
5. Future 1: Present tenses, will, future continuous;
6. Future 2: Going to, future in the past, present after time adverbs, future perfect, to be about to;
7. Adjectives: Comparative and superlative adjectives, position, order, adjectives ending in -ing and -ed;
8. Adverbs: Formation, adverbs and adjectives easily confused, comparative and superlative adverbs, modifiers, position;
9. Questions: Yes / no questions, short answers, question words, question tags, agreeing;
10. Countable and uncountable nouns, articles: Countable and uncountable nouns, a, the and no article, special uses articles;
11. Pronouns and determiners: Possessives, reflexive pronouns, each other etc, there and it, someone etc, all, most and some, each and every, both, neither etc;
12. Modals 1: Use of modals, obligation, necessity;
13. Modals 2: Permission, requests, offers, suggestions, orders, advice;
14. Modals 3: Ability, deduction: certainty, probability and possibility;
15. Passive: Passive, to have something done;
16. Reported speech: Reporting about the past, reporting about the present, verbs used for reporting, questions;
17. Verbs followed by to-infinitive or -ing: Verb + to-infinitive, verb + infinitive without to, verb + -ing, verb + object + to-infinitive, verb + that, adjectives;
18. Phrasal verbs: Meaning and form, verb + preposition, verb + adverb, verb + preposition + adverb;
19. Conditionals 1: Zero, first, second and third conditionals, mixed conditionals;
20. Conditionals 2: Unless, in case, as / so long as, provided that, I wish / if only, it’s time, I’d rather, otherwise / or else; 21. Prepositions 1: Prepositions of place and time;
22. Prepositions 2: Prepositions which follow verbs and adjectives, prepositions to express who, how and why, expressions with prepositions;
23. Relative clauses: Defining and non-defining relative clauses, relative pronouns and prepositions;
24. Linking words 1: Because, as and since, so and therefore, in order to, to + infinitive and so (that), so and such, enough and too;
25. Linking words 2: In spite of and despite, but, although and though, even though and even if, participle clauses, before and after + -ing, when, while and since + -ing.
</description>
<dc:date>2009-09-13T00:45:37Z</dc:date>
<dc:author>tadeufilippini</dc:author>
<dc:subject>cambridge firstcertificate, cambridge grammar, grammar cambridge, ingilizcepratik english, ingilizcepratik, english ingilizcepratik, certificate, first certificate, certificate first, firstcertificate, firstcertificate cambridge</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ingilizcepratik.net/cambridge-grammar-for-first-certificate-book-audio-t-18386.html"><img border="0" src="http://blogmarks.net/screenshots/2009/09/13/ddeb5a6bef512650236b8b650352f038.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ingilizcepratik.net/cambridge-grammar-for-first-certificate-book-audio-t-18386.html">Cambridge Grammar for First Certificate (book audio)</a></h4>
 
by <a href="http://blogmarks.net/user/tadeufilippini">tadeufilippini</a> 
<p class="description">Cambridge Grammar for First Certificate (book audio)

Intermediate to Upper-intermediate

This book provides complete coverage of the grammar needed for the Cambridge FCE exam, and develops listening skills at the same time. It includes the full range of FCE exam tasks from the Reading, Writing, Listening, and Use of English papers, and contains helpful grammar explanations and a grammar glossary.

Contents
1. Present tenses: Present simple, present continuous, state verbs;
2. Past tenses: Past simple, past continuous, used to (and to be used to), would;
3. Present perfect simple and past simple: Present perfect and past simple, present perfect simple and continuous;
4. Past perfect: Past perfect simple and continuous;
5. Future 1: Present tenses, will, future continuous;
6. Future 2: Going to, future in the past, present after time adverbs, future perfect, to be about to;
7. Adjectives: Comparative and superlative adjectives, position, order, adjectives ending in -ing and -ed;
8. Adverbs: Formation, adverbs and adjectives easily confused, comparative and superlative adverbs, modifiers, position;
9. Questions: Yes / no questions, short answers, question words, question tags, agreeing;
10. Countable and uncountable nouns, articles: Countable and uncountable nouns, a, the and no article, special uses articles;
11. Pronouns and determiners: Possessives, reflexive pronouns, each other etc, there and it, someone etc, all, most and some, each and every, both, neither etc;
12. Modals 1: Use of modals, obligation, necessity;
13. Modals 2: Permission, requests, offers, suggestions, orders, advice;
14. Modals 3: Ability, deduction: certainty, probability and possibility;
15. Passive: Passive, to have something done;
16. Reported speech: Reporting about the past, reporting about the present, verbs used for reporting, questions;
17. Verbs followed by to-infinitive or -ing: Verb + to-infinitive, verb + infinitive without to, verb + -ing, verb + object + to-infinitive, verb + that, adjectives;
18. Phrasal verbs: Meaning and form, verb + preposition, verb + adverb, verb + preposition + adverb;
19. Conditionals 1: Zero, first, second and third conditionals, mixed conditionals;
20. Conditionals 2: Unless, in case, as / so long as, provided that, I wish / if only, it’s time, I’d rather, otherwise / or else; 21. Prepositions 1: Prepositions of place and time;
22. Prepositions 2: Prepositions which follow verbs and adjectives, prepositions to express who, how and why, expressions with prepositions;
23. Relative clauses: Defining and non-defining relative clauses, relative pronouns and prepositions;
24. Linking words 1: Because, as and since, so and therefore, in order to, to + infinitive and so (that), so and such, enough and too;
25. Linking words 2: In spite of and despite, but, although and though, even though and even if, participle clauses, before and after + -ing, when, while and since + -ing.
</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cambridge%2Bfirstcertificate">cambridge firstcertificate</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cambridge%2Bgrammar">cambridge grammar</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/grammar%2Bcambridge">grammar cambridge</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ingilizcepratik%2Benglish">ingilizcepratik english</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ingilizcepratik">ingilizcepratik</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/english%2Bingilizcepratik">english ingilizcepratik</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/certificate">certificate</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/first%2Bcertificate">first certificate</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/certificate%2Bfirst">certificate first</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/firstcertificate">firstcertificate</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/firstcertificate%2Bcambridge">firstcertificate cambridge</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058501395">Copy</a> | 
<a href="http://blogmarks.net/link/3341046">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/marco/mark/1058499274">
<title>IE6/IE7 Implicit Label Bug</title>
<link>http://www.evotech.net/blog/2009/09/ie6ie7-implicit-label-bug/</link>
<description>I assume this is such an esoteric bug that I don't need to create recommendations on fixing it. I just wanted to document it in case someone else comes across this bug</description>
<dc:date>2009-09-10T20:43:56Z</dc:date>
<dc:author>marco</dc:author>
<dc:subject>bug, label, form, ie7, ie6</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.evotech.net/blog/2009/09/ie6ie7-implicit-label-bug/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/10/b7ff315c606990a9b364213f282d94b4.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.evotech.net/blog/2009/09/ie6ie7-implicit-label-bug/">IE6/IE7 Implicit Label Bug</a></h4>
 
by <a href="http://blogmarks.net/user/marco">marco</a> 
<p class="description">I assume this is such an esoteric bug that I don't need to create recommendations on fixing it. I just wanted to document it in case someone else comes across this bug</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bug">bug</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/label">label</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/form">form</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ie7">ie7</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ie6">ie6</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058499274">Copy</a> | 
<a href="http://blogmarks.net/link/3339326">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/decembre/mark/1058547795">
<title>UserScript Writing 101 – Manuel of Things to learn - Userscripts.org</title>
<link>http://userscripts.org/guides/22</link>
<description>The Order of Things to Learn Look to the &quot;Resources&quot; section for places to learn about these.     1. HTML. Hypertext Markup Language. Not the same &quot;language&quot; as JavaScript. This is a markup language, meaning it's a bunch of text that is meant to represent some type of structure, in this case, a web page.    2. XML. Extensible Markup Language. In case you didn't realize, HTML itself is a type of &quot;XML&quot;. Learning XML is important because many popular websites (YouTube, Facebook, Last.fm) use XML to interact with data. Since you already know HTML by this point, understanding XML should be cake.    3. CSS. Cascading Style Sheets. This is the way HTML (should be) stylized. You'll want to learn this.    4. JavaScript. Learn all the basics: data types, functions, JavaScript's native functions like prompt, alert, etc.    5. The Greasemonkey Extras. Like I said, Greasmonkey == JavaScript, with a lot of extras. A specific page listing the API's can be found here.</description>
<dc:date>2009-09-05T03:02:18Z</dc:date>
<dc:author>decembre</dc:author>
<dc:subject>greasemonkey, userscript, manuel, documentation, script, extension, reference, dev, javascript, html, xml</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://userscripts.org/guides/22"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://userscripts.org/guides/22">UserScript Writing 101 – Manuel of Things to learn - Userscripts.org</a></h4>
 
by <a href="http://blogmarks.net/user/decembre">decembre</a> 
<p class="description">The Order of Things to Learn Look to the "Resources" section for places to learn about these.     1. HTML. Hypertext Markup Language. Not the same "language" as JavaScript. This is a markup language, meaning it's a bunch of text that is meant to represent some type of structure, in this case, a web page.    2. XML. Extensible Markup Language. In case you didn't realize, HTML itself is a type of "XML". Learning XML is important because many popular websites (YouTube, Facebook, Last.fm) use XML to interact with data. Since you already know HTML by this point, understanding XML should be cake.    3. CSS. Cascading Style Sheets. This is the way HTML (should be) stylized. You'll want to learn this.    4. JavaScript. Learn all the basics: data types, functions, JavaScript's native functions like prompt, alert, etc.    5. The Greasemonkey Extras. Like I said, Greasmonkey == JavaScript, with a lot of extras. A specific page listing the API's can be found here.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/greasemonkey">greasemonkey</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/userscript">userscript</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/manuel">manuel</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/documentation">documentation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/script">script</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/extension">extension</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/reference">reference</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dev">dev</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/html">html</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xml">xml</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058547795">Copy</a> | 
<a href="http://blogmarks.net/link/3381534">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/tadeufilippini/mark/1058492882">
<title>Installation/FromImgFiles - Community Ubuntu Documentation</title>
<link>https://help.ubuntu.com/community/Installation/FromImgFiles</link>
<description># Download the desired .img file
# Install the usb-imagewriter package

    *

      If your release does not include this, download it from Oliver's PPA
    *

      If imagewriter fails to launch, you may need to install python glade2 support. Install the python-glade2 package or Run sudo apt-get install python-glade2
    * If your release does not include it and you are running 9.04 Jaunty Jackalope then run this command from the console:
          o

            sudo apt-get install usb-imagewriter 

#

Open Applications -&gt; Accessories -&gt; Image Writer

    *

      KDE users will find this in Applications -&gt; Utilities -&gt; Image Writer
    *

      on some usb-imagewriter versions (console command: imagewriter) the application fails to write if the image path contains blank spaces, exiting with &quot;IndexError: list index out of range&quot;. Also, in case you prefer to launch it from the command line, don't forget to sudo it, otherwise it will give a permission error. 

# Insert your flash media
# Select the downloaded file and flash device, and click &quot;Write to Device&quot;
# Remove your device when the operation is complete </description>
<dc:date>2009-09-04T08:05:43Z</dc:date>
<dc:author>tadeufilippini</dc:author>
<dc:subject>pendrive ubuntu, Imager, disk, usb, ubuntu community, community ubuntu, ubuntu help, help ubuntu, writer, image, image writer, imagewriter, usb ubuntu, ubuntu usb, disk imager, ubuntu pendrive</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="https://help.ubuntu.com/community/Installation/FromImgFiles"><img border="0" src="http://blogmarks.net/screenshots/2009/09/04/0b58fb82db2f0f67a63c1a579142fb28.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="https://help.ubuntu.com/community/Installation/FromImgFiles">Installation/FromImgFiles - Community Ubuntu Documentation</a></h4>
 
by <a href="http://blogmarks.net/user/tadeufilippini">tadeufilippini</a> 
<p class="description"># Download the desired .img file
# Install the usb-imagewriter package

    *

      If your release does not include this, download it from Oliver's PPA
    *

      If imagewriter fails to launch, you may need to install python glade2 support. Install the python-glade2 package or Run sudo apt-get install python-glade2
    * If your release does not include it and you are running 9.04 Jaunty Jackalope then run this command from the console:
          o

            sudo apt-get install usb-imagewriter 

#

Open Applications -> Accessories -> Image Writer

    *

      KDE users will find this in Applications -> Utilities -> Image Writer
    *

      on some usb-imagewriter versions (console command: imagewriter) the application fails to write if the image path contains blank spaces, exiting with "IndexError: list index out of range". Also, in case you prefer to launch it from the command line, don't forget to sudo it, otherwise it will give a permission error. 

# Insert your flash media
# Select the downloaded file and flash device, and click "Write to Device"
# Remove your device when the operation is complete </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/pendrive%2Bubuntu">pendrive ubuntu</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Imager">Imager</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/disk">disk</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/usb">usb</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ubuntu%2Bcommunity">ubuntu community</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/community%2Bubuntu">community ubuntu</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ubuntu%2Bhelp">ubuntu help</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/help%2Bubuntu">help ubuntu</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/writer">writer</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/image">image</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/image%2Bwriter">image writer</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/imagewriter">imagewriter</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/usb%2Bubuntu">usb ubuntu</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ubuntu%2Busb">ubuntu usb</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/disk%2Bimager">disk imager</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ubuntu%2Bpendrive">ubuntu pendrive</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058492882">Copy</a> | 
<a href="http://blogmarks.net/link/3334277">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ericpaul/mark/1058481229">
<title>The Curious Case of Flash on the iPhone | Popular Science</title>
<link>http://www.popsci.com/gear-amp-gadgets/article/2009-06/curious-case-flash-iphone</link>
<description></description>
<dc:date>2009-08-25T15:23:02Z</dc:date>
<dc:author>ericpaul</dc:author>
<dc:subject>iphone</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.popsci.com/gear-amp-gadgets/article/2009-06/curious-case-flash-iphone"><img border="0" src="http://blogmarks.net/screenshots/2009/08/25/769370ffdbaec1e10000316523a7d40f.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.popsci.com/gear-amp-gadgets/article/2009-06/curious-case-flash-iphone">The Curious Case of Flash on the iPhone | Popular Science</a></h4>
 
by <a href="http://blogmarks.net/user/ericpaul">ericpaul</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/iphone">iphone</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058481229">Copy</a> | 
<a href="http://blogmarks.net/link/3324437">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/bamthomas/mark/1058477163">
<title>The Case Against Apple–in Five Parts « The Jason Calacanis Weblog</title>
<link>http://calacanis.com/2009/08/08/the-case-against-apple-in-five-parts/</link>
<description></description>
<dc:date>2009-08-24T08:09:45Z</dc:date>
<dc:author>bamthomas</dc:author>
<dc:subject>informatique, apple</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://calacanis.com/2009/08/08/the-case-against-apple-in-five-parts/"><img border="0" src="http://blogmarks.net/screenshots/2009/08/24/305ad1a38cdb24b1bbba8b73e20420fd.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://calacanis.com/2009/08/08/the-case-against-apple-in-five-parts/">The Case Against Apple–in Five Parts « The Jason Calacanis Weblog</a></h4>
 
by <a href="http://blogmarks.net/user/bamthomas">bamthomas</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/informatique">informatique</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/apple">apple</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058477163">Copy</a> | 
<a href="http://blogmarks.net/link/3323256">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058475331">
<title>Creative Review - We are open</title>
<link>http://www.creativereview.co.uk/back-issues/creative-review/2009/july-2009/we-are-open</link>
<description>Pete Hellicar and Joel Gethin Lewis set up their business formally earlier this year, though have worked together on projects over the last couple of years and known each other for longer. At the centre of their business strategy is open source, with all works they create being placed online for others to download and use or adapt after they are finished. You might imagine that this approach would cause anxiety in some of the advertising agencies or brands they have been talking to, but surprisingly this is not the case. “We say everything upfront,” says Lewis. “A lot of people said to me ‘no-one will want to open source their projects, you’re crazy’, but no-one’s had a problem with it so far.”</description>
<dc:date>2009-08-22T10:16:02Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>opensource</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.creativereview.co.uk/back-issues/creative-review/2009/july-2009/we-are-open"><img border="0" src="http://blogmarks.net/screenshots/2009/08/22/1ff4a135da3574a0e6645ddcc3e9467f.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.creativereview.co.uk/back-issues/creative-review/2009/july-2009/we-are-open">Creative Review - We are open</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3321952">1 other(s)</a> 
<p class="description">Pete Hellicar and Joel Gethin Lewis set up their business formally earlier this year, though have worked together on projects over the last couple of years and known each other for longer. At the centre of their business strategy is open source, with all works they create being placed online for others to download and use or adapt after they are finished. You might imagine that this approach would cause anxiety in some of the advertising agencies or brands they have been talking to, but surprisingly this is not the case. “We say everything upfront,” says Lewis. “A lot of people said to me ‘no-one will want to open source their projects, you’re crazy’, but no-one’s had a problem with it so far.”</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opensource">opensource</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058475331">Copy</a> | 
<a href="http://blogmarks.net/link/3321952">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058471279">
<title>Up-conversion using XSLT 2.0</title>
<link>http://www.saxonica.com/papers/ideadb-1.1/mhk-paper.xml</link>
<description>&lt;blockquote&gt;&lt;p&gt;The paper shows case study of a multi-phase transformation taking data from a legacy ASCII-based interchange format, to XML based on a standardized vocabulary. The transformations illustrate the power of new features including regular expression handling, grouping, recursive functions, and schema-aware processing.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-08-18T00:32:35Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>xslt</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.saxonica.com/papers/ideadb-1.1/mhk-paper.xml"><img border="0" src="http://blogmarks.net/screenshots/2009/08/18/f529b5186f05bb6fa24a82b979a5f452.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.saxonica.com/papers/ideadb-1.1/mhk-paper.xml">Up-conversion using XSLT 2.0</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>The paper shows case study of a multi-phase transformation taking data from a legacy ASCII-based interchange format, to XML based on a standardized vocabulary. The transformations illustrate the power of new features including regular expression handling, grouping, recursive functions, and schema-aware processing.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xslt">xslt</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058471279">Copy</a> | 
<a href="http://blogmarks.net/link/3318702">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058469200">
<title>Re: POST from Julian Reschke on 2009-08-16 (www-tag@w3.org from August 2009)</title>
<link>http://lists.w3.org/Archives/Public/www-tag/2009Aug/0049.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;No, using POST to add to a collection is the right thing to do. An alternative is PUT, in case you want to allow the client to specify the name of the new sub resource.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-08-16T21:02:12Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>http</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://lists.w3.org/Archives/Public/www-tag/2009Aug/0049.html"><img border="0" src="http://blogmarks.net/screenshots/2009/08/16/7947e3d60868b6ab3fec6340a75f59f8.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://lists.w3.org/Archives/Public/www-tag/2009Aug/0049.html">Re: POST from Julian Reschke on 2009-08-16 (www-tag@w3.org from August 2009)</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>No, using POST to add to a collection is the right thing to do. An alternative is PUT, in case you want to allow the client to specify the name of the new sub resource.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/http">http</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058469200">Copy</a> | 
<a href="http://blogmarks.net/link/3316850">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/bs_pepper/mark/1058467297">
<title>Case study : la stratégie Web de Terminator Salvation | Marketing 2.0 - Le blog de l'agence You to You</title>
<link>http://www.marketing20.fr/buzz-marketing/case-study-la-strategie-web-de-terminator-salvation/</link>
<description></description>
<dc:date>2009-08-14T11:03:56Z</dc:date>
<dc:author>bs_pepper</dc:author>
<dc:subject>marketing, viral, terminator</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.marketing20.fr/buzz-marketing/case-study-la-strategie-web-de-terminator-salvation/"><img border="0" src="http://blogmarks.net/screenshots/2009/08/14/00b572b6939dce0b8ea68b74be7d8fdb.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.marketing20.fr/buzz-marketing/case-study-la-strategie-web-de-terminator-salvation/">Case study : la stratégie Web de Terminator Salvation | Marketing 2.0 - Le blog de l'agence You to You</a></h4>
 
by <a href="http://blogmarks.net/user/bs_pepper">bs_pepper</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/marketing">marketing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/viral">viral</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/terminator">terminator</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058467297">Copy</a> | 
<a href="http://blogmarks.net/link/3315322">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/paulantoinem/mark/1058470261">
<title>Criminal case against “extremist” Siberian artist ongoing - Artem Loskutov was jailed for his role in a political art groupThe Art Newspaper</title>
<link>http://envrac.posterous.com/criminal-case-against-extremist-siberian-arti</link>
<description>The Center for Extremism Prevention, formed from Interior Ministry units previously charged with combating organised crime, has to justify its existence,” says a statement on kissmybabushka.co ...</description>
<dc:date>2009-08-13T12:04:48Z</dc:date>
<dc:author>paulantoinem</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://envrac.posterous.com/criminal-case-against-extremist-siberian-arti"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://envrac.posterous.com/criminal-case-against-extremist-siberian-arti">Criminal case against “extremist” Siberian artist ongoing - Artem Loskutov was jailed for his role in a political art groupThe Art Newspaper</a></h4>
 
by <a href="http://blogmarks.net/user/paulantoinem">paulantoinem</a> 
<p class="description">The Center for Extremism Prevention, formed from Interior Ministry units previously charged with combating organised crime, has to justify its existence,” says a statement on kissmybabushka.co ...</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058470261">Copy</a> | 
<a href="http://blogmarks.net/link/3317808">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058435430">
<title>Tokyo Tyrant: network interface of Tokyo Cabinet</title>
<link>http://tokyocabinet.sourceforge.net/tyrantdoc/</link>
<description>&lt;blockquote&gt;&lt;p&gt;Tokyo Tyrant is a package of network interface to the DBM called Tokyo Cabinet. Though the DBM has high performance, you might bother in case that multiple processes share the same database, or remote processes access the database. Thus, Tokyo Tyrant is provided for concurrent and remote connections to Tokyo Cabinet. It is composed of the server process managing a database and its access library for client applications.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-07-20T03:33:44Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>tokyo, database</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://tokyocabinet.sourceforge.net/tyrantdoc/"><img border="0" src="http://blogmarks.net/screenshots/2009/07/20/002217fc4e779611113ee0087a7ab0df.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://tokyocabinet.sourceforge.net/tyrantdoc/">Tokyo Tyrant: network interface of Tokyo Cabinet</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>Tokyo Tyrant is a package of network interface to the DBM called Tokyo Cabinet. Though the DBM has high performance, you might bother in case that multiple processes share the same database, or remote processes access the database. Thus, Tokyo Tyrant is provided for concurrent and remote connections to Tokyo Cabinet. It is composed of the server process managing a database and its access library for client applications.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tokyo">tokyo</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/database">database</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058435430">Copy</a> | 
<a href="http://blogmarks.net/link/3290201">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/decembre/mark/1058547970">
<title>Creative Commons - Quelques scripts GreaseMonkey pour Flickr</title>
<link>http://bydorian.com/quelques-scripts-greasemonkey-pour-flickr/</link>
<description>Du fait que je recherche beaucoup d’images sur Flickr, pour gagner du temps j’ai fait quelques scripts. Ces scripts agissent par GreaseMonkey, une extension de Firefox qui permet d’executer du Javascript.  Le premier me permet d’avoir une phrase toute faite contenant l’auteur de l’image et la licence, avec des liens pour soutenir l’auteur et les Creative Commons. La phrase ressemblera à : « Image par &amp;lt;auteur&amp;gt; sous &amp;lt;licence&amp;gt;. ».  Le second permet de cocher par defaut la case de recherche Creative Commons lors d’une recherche avancée avec Flickr.  Les scripts ne sont pas particulièrement soignés mais fonctionnels tant que Flickr ne change pas la structure de son site. Je les met dans le domaine public vu le peu de code.</description>
<dc:date>2009-07-19T17:01:44Z</dc:date>
<dc:author>decembre</dc:author>
<dc:subject>extension, creative-commons, creativecommons, libre, image, illustration, dev, site</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://bydorian.com/quelques-scripts-greasemonkey-pour-flickr/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://bydorian.com/quelques-scripts-greasemonkey-pour-flickr/">Creative Commons - Quelques scripts GreaseMonkey pour Flickr</a></h4>
 
by <a href="http://blogmarks.net/user/decembre">decembre</a> 
<p class="description">Du fait que je recherche beaucoup d’images sur Flickr, pour gagner du temps j’ai fait quelques scripts. Ces scripts agissent par GreaseMonkey, une extension de Firefox qui permet d’executer du Javascript.  Le premier me permet d’avoir une phrase toute faite contenant l’auteur de l’image et la licence, avec des liens pour soutenir l’auteur et les Creative Commons. La phrase ressemblera à : « Image par &lt;auteur&gt; sous &lt;licence&gt;. ».  Le second permet de cocher par defaut la case de recherche Creative Commons lors d’une recherche avancée avec Flickr.  Les scripts ne sont pas particulièrement soignés mais fonctionnels tant que Flickr ne change pas la structure de son site. Je les met dans le domaine public vu le peu de code.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/extension">extension</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/creative-commons">creative-commons</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/creativecommons">creativecommons</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/libre">libre</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/image">image</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/illustration">illustration</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dev">dev</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/site">site</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058547970">Copy</a> | 
<a href="http://blogmarks.net/link/3381672">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>