<?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/existing">
<title>Public marks with search existing</title>
<description>Public marks with search existing</description>
<link>http://blogmarks.net/marks/search/existing</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058578855"/>
<rdf:li resource="http://blogmarks.net/api/user/Spone/mark/1058567600"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058563736"/>
<rdf:li resource="http://blogmarks.net/api/user/srcmax/mark/1058561029"/>
<rdf:li resource="http://blogmarks.net/api/user/ms_michel/mark/1058549928"/>
<rdf:li resource="http://blogmarks.net/api/user/marco/mark/1058539994"/>
<rdf:li resource="http://blogmarks.net/api/user/PêUR/mark/1058529027"/>
<rdf:li resource="http://blogmarks.net/api/user/decembre/mark/1058547724"/>
<rdf:li resource="http://blogmarks.net/api/user/sbrothier/mark/1058524927"/>
<rdf:li resource="http://blogmarks.net/api/user/mozkart/mark/1058521551"/>
<rdf:li resource="http://blogmarks.net/api/user/sbrothier/mark/1058508795"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058504936"/>
<rdf:li resource="http://blogmarks.net/api/user/decembre/mark/1058547773"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058496413"/>
<rdf:li resource="http://blogmarks.net/api/user/parmentierf/mark/1058495532"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058490434"/>
<rdf:li resource="http://blogmarks.net/api/user/dzc/mark/1058487355"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058482494"/>
<rdf:li resource="http://blogmarks.net/api/user/Xavier Lacot/mark/1058477329"/>
<rdf:li resource="http://blogmarks.net/api/user/marco/mark/1058448268"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058447485"/>
<rdf:li resource="http://blogmarks.net/api/user/marco/mark/1058436209"/>
<rdf:li resource="http://blogmarks.net/api/user/ms_michel/mark/1058430606"/>
<rdf:li resource="http://blogmarks.net/api/user/znarf/mark/1058422553"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058419739"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058578855">
<title>Google Latitude</title>
<link>http://www.google.com/latitude/apps/history</link>
<description>&lt;blockquote&gt;&lt;p&gt;Privacy Notice&lt;/p&gt;&lt;p&gt;* Your history will not be visible publicly or to your Latitude friends.&lt;/p&gt;&lt;p&gt;* You may delete your entire location history or portions of it whenever you like.&lt;/p&gt;&lt;p&gt;* Disabling the feature will not remove existing history already stored. To delete that, go to History management.&lt;/p&gt;&lt;/blockquote&gt;
upfront</description>
<dc:date>2009-11-11T11:46:12Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>googlelatitude, opacité</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.google.com/latitude/apps/history"><img border="0" src="http://blogmarks.net/screenshots/2009/11/11/079dd0e7d1aabdf8ceb6b47854129b7f.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.google.com/latitude/apps/history">Google Latitude</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>Privacy Notice</p><p>* Your history will not be visible publicly or to your Latitude friends.</p><p>* You may delete your entire location history or portions of it whenever you like.</p><p>* Disabling the feature will not remove existing history already stored. To delete that, go to History management.</p></blockquote>
upfront</div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/googlelatitude">googlelatitude</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opacit%25C3%25A9">opacité</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058578855">Copy</a> | 
<a href="http://blogmarks.net/link/3405572">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Spone/mark/1058567600">
<title>Raindrop Design Development Page</title>
<link>http://blogs.mozillamessaging.com/raindropdesign/</link>
<description>Raindrop is an open design process in building a better, more personal and useful way of participating in your existing communications. Built on a web messaging platform designed to push the limits of browser based applications—we are a Mozilla Labs project.</description>
<dc:date>2009-10-30T10:16:44Z</dc:date>
<dc:author>Spone</dc:author>
<dc:subject>design, mozilla, mozilla labs, projet, prototype, messagerie instantanée, email</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://blogs.mozillamessaging.com/raindropdesign/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/30/fc705822aea425259f691b8b1a4ed3c0.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://blogs.mozillamessaging.com/raindropdesign/">Raindrop Design Development Page</a></h4>
 
by <a href="http://blogmarks.net/user/Spone">Spone</a> 
<p class="description">Raindrop is an open design process in building a better, more personal and useful way of participating in your existing communications. Built on a web messaging platform designed to push the limits of browser based applications—we are a Mozilla Labs project.</p>
<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/mozilla">mozilla</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mozilla%2Blabs">mozilla labs</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/projet">projet</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/messagerie%2Binstantan%25C3%25A9e">messagerie instantanée</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/email">email</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058567600">Copy</a> | 
<a href="http://blogmarks.net/link/3396918">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058563736">
<title>Memory and forgetting in the digital age - opinion - 24 October 2009 - New Scientist</title>
<link>http://www.newscientist.com/article/mg20427311.700-memory-and-forgetting-in-the-digital-age.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;And he comes up with an interesting solution: expiration dates in electronic files. This would stop the files from existing forever and flooding us and the next generations with gigantic piles of mostly useless or even potentially harmful details.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-10-26T09:53:50Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>opacité</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.newscientist.com/article/mg20427311.700-memory-and-forgetting-in-the-digital-age.html"><img border="0" src="http://blogmarks.net/screenshots/2009/10/26/e5913c550a5da877d1e87a5e2b4ecdaa.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.newscientist.com/article/mg20427311.700-memory-and-forgetting-in-the-digital-age.html">Memory and forgetting in the digital age - opinion - 24 October 2009 - New Scientist</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>And he comes up with an interesting solution: expiration dates in electronic files. This would stop the files from existing forever and flooding us and the next generations with gigantic piles of mostly useless or even potentially harmful details.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opacit%25C3%25A9">opacité</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058563736">Copy</a> | 
<a href="http://blogmarks.net/link/3393894">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/srcmax/mark/1058561029">
<title>LESS - Leaner CSS</title>
<link>http://lesscss.org/</link>
<description>LESS extends CSS with: variables, mixins, operations and nested rules. Best of all, LESS uses existing CSS syntax. This means you can rename your current .css files to .less and they'll just work.</description>
<dc:date>2009-10-23T08:22:03Z</dc:date>
<dc:author>srcmax</dc:author>
<dc:subject>less, css, intégration</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://lesscss.org/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/23/394b8f945f9d8a14b1f312a4477503e6.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://lesscss.org/">LESS - Leaner CSS</a></h4>
 
by <a href="http://blogmarks.net/user/srcmax">srcmax</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3233933">4 other(s)</a> 
<p class="description">LESS extends CSS with: variables, mixins, operations and nested rules. Best of all, LESS uses existing CSS syntax. This means you can rename your current .css files to .less and they'll just work.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/less">less</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/css">css</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/int%25C3%25A9gration">intégration</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058561029">Copy</a> | 
<a href="http://blogmarks.net/link/3233933">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ms_michel/mark/1058549928">
<title>The IBuySpy Portal architecture (PDF)</title>
<link>http://www.dotnetexperts.com/resources/chapters/asp_dotnet_intra_chap02.pdf</link>
<description>&lt;blockquote&gt;&lt;p&gt;In this book, we'll be using the freely available IBuySpy Portal as a starting point for our intranet development. We'll look at both why we are modifying an existing intranet application rather than creating our own, and why we choose the IBuySpy Portal in particular. Once we have covered the basics, we'll take a tour of its features, looking at the files and types it consists of, how they function and fit together, and general principles behind the site. Finally, we'll take a brief look at how security is handled.&lt;/p&gt;&lt;/blockquote&gt;

</description>
<dc:date>2009-10-14T08:53:44Z</dc:date>
<dc:author>ms_michel</dc:author>
<dc:subject>.net, pour-memoire, cms.net</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.dotnetexperts.com/resources/chapters/asp_dotnet_intra_chap02.pdf"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.dotnetexperts.com/resources/chapters/asp_dotnet_intra_chap02.pdf">The IBuySpy Portal architecture (PDF)</a></h4>
 
by <a href="http://blogmarks.net/user/ms_michel">ms_michel</a> 
<div class="description"><blockquote><p>In this book, we'll be using the freely available IBuySpy Portal as a starting point for our intranet development. We'll look at both why we are modifying an existing intranet application rather than creating our own, and why we choose the IBuySpy Portal in particular. Once we have covered the basics, we'll take a tour of its features, looking at the files and types it consists of, how they function and fit together, and general principles behind the site. Finally, we'll take a brief look at how security is handled.</p></blockquote>

</div>
<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/pour-memoire">pour-memoire</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cms.net">cms.net</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058549928">Copy</a> | 
<a href="http://blogmarks.net/link/3383381">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/marco/mark/1058539994">
<title>Developing for the Apple iPhone using Flash</title>
<link>http://www.adobe.com/devnet/logged_in/abansod_iphone.html</link>
<description>We created a new compiler front end that allowed LLVM to understand ActionScript 3 and used its existing ARM back end to output native ARM assembly code.</description>
<dc:date>2009-10-05T20:27:12Z</dc:date>
<dc:author>marco</dc:author>
<dc:subject>llvm, flash, adobe, iphone</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.adobe.com/devnet/logged_in/abansod_iphone.html"><img border="0" src="http://blogmarks.net/screenshots/2009/10/05/cb862e70f5fb137c7cc30bcbfc5f738a.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.adobe.com/devnet/logged_in/abansod_iphone.html">Developing for the Apple iPhone using Flash</a></h4>
 
by <a href="http://blogmarks.net/user/marco">marco</a> 
<p class="description">We created a new compiler front end that allowed LLVM to understand ActionScript 3 and used its existing ARM back end to output native ARM assembly code.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/llvm">llvm</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/flash">flash</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/iphone">iphone</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058539994">Copy</a> | 
<a href="http://blogmarks.net/link/3375048">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/PêUR/mark/1058529027">
<title>tiltshiftmaker.com - Transform your photos into tilt-shift style miniatures</title>
<link>http://tiltshiftmaker.com/</link>
<description>Tilt-shift miniature style photos are pictures of real-life scenes that are manipulated to look like model photographs.

Now you can easily transform your existing digital camera photos into tilt-shift style miniatures using tiltshiftmaker.com. Our online photo editing tool is fun and requires no registration or signup.</description>
<dc:date>2009-10-03T09:23:16Z</dc:date>
<dc:author>PêUR</dc:author>
<dc:subject>fun, photo, generator, tiltshift</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://tiltshiftmaker.com/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/03/24267abb44eef05549044e188c510039.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://tiltshiftmaker.com/">tiltshiftmaker.com - Transform your photos into tilt-shift style miniatures</a></h4>
 
by <a href="http://blogmarks.net/user/PêUR">PêUR</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3053078">4 other(s)</a> 
<p class="description">Tilt-shift miniature style photos are pictures of real-life scenes that are manipulated to look like model photographs.

Now you can easily transform your existing digital camera photos into tilt-shift style miniatures using tiltshiftmaker.com. Our online photo editing tool is fun and requires no registration or signup.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/fun">fun</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/photo">photo</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/generator">generator</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tiltshift">tiltshift</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058529027">Copy</a> | 
<a href="http://blogmarks.net/link/3053078">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/decembre/mark/1058547724">
<title>The URI microformat, OpenURL and COIns,  will be very interesting to library application - in &quot;Programming&quot; (Tricks/tips learned in daily programming work)</title>
<link>http://lxming.blogspot.com/2006/02/make-case-for-uri-microformat-uri.html</link>
<description>The URI microformat takes advantage of OpenURL and existing link resolver solution.It defines a convention of plugging URI metadata in HTML page. If it is adopted and widely used,now a microformat-aware application (be a greasemonkey script, or a web service) can grab the identifier and point to your local OpenURL resolver, you immediately get the copy from local library.It is very similar to COINS, but it's much simpler and cleaner, anyone can understand and use it, and its aplication can be beyond traditional research library. e.g. in a public library, you can use amazon as catalog and immediately check if it's available in local collection.------- COinS provides a great number of additional capabilities that URI microformat can't support. Since COinS can't be dismissed for this reason, it doesn't make sense to me to create yet another standard that does the same thing with so little savings.I will grant that the COinS is less intuitive.....</description>
<dc:date>2009-10-02T01:32:28Z</dc:date>
<dc:author>decembre</dc:author>
<dc:subject>openurl, coins, uri, microformat, bib, bibliotheque2.0, library2.0, opac, opac2.0, service, amazon, catalogue, dev, metadonnée, metadata, web-service, greasemonkey</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://lxming.blogspot.com/2006/02/make-case-for-uri-microformat-uri.html"><img border="0" src="http://www.blogmarks.net/screenshots/2006/04/06/784f554d5905ad70ddf5d21e535477ad.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://lxming.blogspot.com/2006/02/make-case-for-uri-microformat-uri.html">The URI microformat, OpenURL and COIns,  will be very interesting to library application - in &quot;Programming&quot; (Tricks/tips learned in daily programming work)</a></h4>
 
by <a href="http://blogmarks.net/user/decembre">decembre</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/706259">1 other(s)</a> 
<p class="description">The URI microformat takes advantage of OpenURL and existing link resolver solution.It defines a convention of plugging URI metadata in HTML page. If it is adopted and widely used,now a microformat-aware application (be a greasemonkey script, or a web service) can grab the identifier and point to your local OpenURL resolver, you immediately get the copy from local library.It is very similar to COINS, but it's much simpler and cleaner, anyone can understand and use it, and its aplication can be beyond traditional research library. e.g. in a public library, you can use amazon as catalog and immediately check if it's available in local collection.------- COinS provides a great number of additional capabilities that URI microformat can't support. Since COinS can't be dismissed for this reason, it doesn't make sense to me to create yet another standard that does the same thing with so little savings.I will grant that the COinS is less intuitive.....</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/openurl">openurl</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/coins">coins</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/uri">uri</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/microformat">microformat</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bib">bib</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bibliotheque2.0">bibliotheque2.0</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/library2.0">library2.0</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opac">opac</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opac2.0">opac2.0</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/service">service</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/amazon">amazon</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/catalogue">catalogue</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/metadonn%25C3%25A9e">metadonnée</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/metadata">metadata</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web-service">web-service</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/greasemonkey">greasemonkey</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058547724">Copy</a> | 
<a href="http://blogmarks.net/link/706259">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/sbrothier/mark/1058524927">
<title>Marshall Alexander - Paper Engineer</title>
<link>http://www.marshallalexander.net/</link>
<description>
	I am a Dutch paper engineer, based in Arnhem, and my work mainly focuses on the creation of papertoys. I either create completely new characters from scratch or I transform existing characters into papermodels. My speciality is one-piece papertoys, models that consist of a single flat piece of paper, which by intricate folding is transformed into a 3-dimensional model. I also create more complex templates consisting of several parts that are glued together to construct the final model. I've have done commissioned work for the toy industry, for promotional purposes and for books and magazines. Growing up in the seventies and eighties, my personal work is heavily inspired by retro design, videogames, movies, bright plastic toys and TV cartoons. Most of this work can be downloaded for free from my site. So get your knives and glue out, download some of the models and start building. Enjoy! </description>
<dc:date>2009-10-01T10:32:13Z</dc:date>
<dc:author>sbrothier</dc:author>
<dc:subject>paper, papercut, toys</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.marshallalexander.net/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/01/4782232d30b0cbedac7f7595fb854828.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.marshallalexander.net/">Marshall Alexander - Paper Engineer</a></h4>
 
by <a href="http://blogmarks.net/user/sbrothier">sbrothier</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2512071">4 other(s)</a> 
<p class="description">
	I am a Dutch paper engineer, based in Arnhem, and my work mainly focuses on the creation of papertoys. I either create completely new characters from scratch or I transform existing characters into papermodels. My speciality is one-piece papertoys, models that consist of a single flat piece of paper, which by intricate folding is transformed into a 3-dimensional model. I also create more complex templates consisting of several parts that are glued together to construct the final model. I've have done commissioned work for the toy industry, for promotional purposes and for books and magazines. Growing up in the seventies and eighties, my personal work is heavily inspired by retro design, videogames, movies, bright plastic toys and TV cartoons. Most of this work can be downloaded for free from my site. So get your knives and glue out, download some of the models and start building. Enjoy! </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/paper">paper</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/papercut">papercut</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/toys">toys</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058524927">Copy</a> | 
<a href="http://blogmarks.net/link/2512071">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/mozkart/mark/1058521551">
<title>BBM</title>
<link>http://www.broadbandmechanics.com/</link>
<description>Social Networking, blogging, ID Hub, content management and an aggregation engine are all available in source code form or we'll host it for you - via a SaaS deal.  We can customize to your needs, whether it be a stand alone network or by - &quot;bringing social to software&quot; - into your existing legacy app or web site</description>
<dc:date>2009-09-27T16:57:35Z</dc:date>
<dc:author>mozkart</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.broadbandmechanics.com/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/27/5e1d406288d3bfb3d56db9114ce1c0ab.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.broadbandmechanics.com/">BBM</a></h4>
 
by <a href="http://blogmarks.net/user/mozkart">mozkart</a> 
<p class="description">Social Networking, blogging, ID Hub, content management and an aggregation engine are all available in source code form or we'll host it for you - via a SaaS deal.  We can customize to your needs, whether it be a stand alone network or by - "bringing social to software" - into your existing legacy app or web site</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058521551">Copy</a> | 
<a href="http://blogmarks.net/link/3357775">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/sbrothier/mark/1058508795">
<title>WOFF File Format</title>
<link>http://people.mozilla.com/~jkew/woff/woff-2009-09-16.html</link>
<description>This document specifies a simple compressed file format for fonts, designed primarily for use on the web. The WOFF format is directly based on the table-based sfnt structure used in TrueType[1], OpenType[2] and Open Font Format[3] fonts, which are collectively referred to as sfnt-based fonts. A WOFF font file is simply a repackaged version of a sfnt-based font in compressed form. The format also allows font metadata and private-use data to be included separately from the font data. WOFF encoding tools convert an existing sfnt-based font into a WOFF formatted file, and user agents restore the original sfnt-based font data for use with a webpage.

In general, the structure and contents of decompressed font data should match that of the original font file. Tools producing WOFF font files may provide other font editing features such as glyph subsetting, validation or font feature additions but these are considered outside the scope of this format. Independent of these features, both tools and user agents must assure that the validity of the underlying font data is preserved.</description>
<dc:date>2009-09-18T16:17:44Z</dc:date>
<dc:author>sbrothier</dc:author>
<dc:subject>typography, fonts</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://people.mozilla.com/~jkew/woff/woff-2009-09-16.html"><img border="0" src="http://blogmarks.net/screenshots/2009/09/18/2527113cf894d3f08e0ebd719d38c493.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://people.mozilla.com/~jkew/woff/woff-2009-09-16.html">WOFF File Format</a></h4>
 
by <a href="http://blogmarks.net/user/sbrothier">sbrothier</a> 
<p class="description">This document specifies a simple compressed file format for fonts, designed primarily for use on the web. The WOFF format is directly based on the table-based sfnt structure used in TrueType[1], OpenType[2] and Open Font Format[3] fonts, which are collectively referred to as sfnt-based fonts. A WOFF font file is simply a repackaged version of a sfnt-based font in compressed form. The format also allows font metadata and private-use data to be included separately from the font data. WOFF encoding tools convert an existing sfnt-based font into a WOFF formatted file, and user agents restore the original sfnt-based font data for use with a webpage.

In general, the structure and contents of decompressed font data should match that of the original font file. Tools producing WOFF font files may provide other font editing features such as glyph subsetting, validation or font feature additions but these are considered outside the scope of this format. Independent of these features, both tools and user agents must assure that the validity of the underlying font data is preserved.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/typography">typography</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/fonts">fonts</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058508795">Copy</a> | 
<a href="http://blogmarks.net/link/3346875">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058504936">
<title>User:Gerv/BugzillaAPIDesign - MozillaWiki</title>
<link>https://wiki.mozilla.org/User:Gerv/BugzillaAPIDesign</link>
<description>&lt;blockquote&gt;&lt;p&gt;This is a design scratchpad for an HTTP RESTful API for Bugzilla. It will be implemented as a proxy, using a variety of methods (the existing API, web scraping) on the back end and with a clean interface as defined here on the front end.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-09-16T04:59:28Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>Bugzilla, restful, http, api</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="https://wiki.mozilla.org/User:Gerv/BugzillaAPIDesign"><img border="0" src="http://blogmarks.net/screenshots/2009/09/16/a31392654bc3eebabce58919dd2d0e89.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="https://wiki.mozilla.org/User:Gerv/BugzillaAPIDesign">User:Gerv/BugzillaAPIDesign - MozillaWiki</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>This is a design scratchpad for an HTTP RESTful API for Bugzilla. It will be implemented as a proxy, using a variety of methods (the existing API, web scraping) on the back end and with a clean interface as defined here on the front end.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Bugzilla">Bugzilla</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/restful">restful</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/http">http</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/api">api</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058504936">Copy</a> | 
<a href="http://blogmarks.net/link/3343725">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/decembre/mark/1058547773">
<title>Hardware interrupt  - IDE ATA and ATAPI disks use PIO mode after multiple time-out or CRC errors occur    * In Windows XP and Windows Server 2003, this time-out value is always 10 seconds.</title>
<link>http://support.microsoft.com/default.aspx?scid=kb;en-us;817472</link>
<description>* An alternate, less-aggressive policy is implemented to reduce the transfer mode (from faster to slower DMA modes, and then eventually to PIO mode) on time-out and CRC errors. The existing behavior is that the IDE/ATAPI Port driver (Atapi.sys) reduces the transfer mode after any 6 cumulative time-out or CRC errors. When the new policy is implemented by this fix, Atapi.sys reduces the transfer mode only after 6 consecutive time-out or CRC errors. This new policy is implemented only if the registry value that is described later in this article is present.  To implement the alternate behavior (reducing the transfer mode after six consecutive time-out or CRC errors instead of after six cumulative time-out or CRC errors), you must modify the registry as described below after you apply the hotfix..</description>
<dc:date>2009-09-12T14:03:19Z</dc:date>
<dc:author>decembre</dc:author>
<dc:subject>windows, xp, hardware, interrupt, microsoft, officiel, disk, ide, dma, pio, atapi, reparer</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;817472"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://support.microsoft.com/default.aspx?scid=kb;en-us;817472">Hardware interrupt  - IDE ATA and ATAPI disks use PIO mode after multiple time-out or CRC errors occur    * In Windows XP and Windows Server 2003, this time-out value is always 10 seconds.</a></h4>
 
by <a href="http://blogmarks.net/user/decembre">decembre</a> 
<p class="description">* An alternate, less-aggressive policy is implemented to reduce the transfer mode (from faster to slower DMA modes, and then eventually to PIO mode) on time-out and CRC errors. The existing behavior is that the IDE/ATAPI Port driver (Atapi.sys) reduces the transfer mode after any 6 cumulative time-out or CRC errors. When the new policy is implemented by this fix, Atapi.sys reduces the transfer mode only after 6 consecutive time-out or CRC errors. This new policy is implemented only if the registry value that is described later in this article is present.  To implement the alternate behavior (reducing the transfer mode after six consecutive time-out or CRC errors instead of after six cumulative time-out or CRC errors), you must modify the registry as described below after you apply the hotfix..</p>
<p class="tags">
<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/xp">xp</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/hardware">hardware</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/interrupt">interrupt</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/microsoft">microsoft</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/officiel">officiel</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/ide">ide</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dma">dma</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/pio">pio</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/atapi">atapi</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/reparer">reparer</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058547773">Copy</a> | 
<a href="http://blogmarks.net/link/3381516">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058496413">
<title>About | Mapdiva, LLC</title>
<link>http://www.mapdiva.com/about-2/</link>
<description>&lt;blockquote&gt;&lt;p&gt;You know how powerful maps are – to communicate, to convince, to plan, to dream. But existing mapping tools make hard work of a good map. General-purpose graphics programs know nothing about mapping and can be an exercise in frustration. And GIS» geographic information systems (GIS) are used to manage and analyze geospatial data; though powerful for those purposes they often produce unattractive “GIS-looking” maps!have a steep learning curve, are expensive, and lack high-quality presentation graphics.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-09-08T01:41:42Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>macosx, cartographie</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.mapdiva.com/about-2/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/08/aa5f4f003ef4059a68d6d4302552db67.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.mapdiva.com/about-2/">About | Mapdiva, LLC</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>You know how powerful maps are – to communicate, to convince, to plan, to dream. But existing mapping tools make hard work of a good map. General-purpose graphics programs know nothing about mapping and can be an exercise in frustration. And GIS» geographic information systems (GIS) are used to manage and analyze geospatial data; though powerful for those purposes they often produce unattractive “GIS-looking” maps!have a steep learning curve, are expensive, and lack high-quality presentation graphics.</p></blockquote></div>
<p class="tags">
<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/cartographie">cartographie</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058496413">Copy</a> | 
<a href="http://blogmarks.net/link/3337131">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/parmentierf/mark/1058495532">
<title>DuraSpace</title>
<link>http://duraspace.org/index.php</link>
<description>The joined organization, named &quot;DuraSpace,&quot; will sustain and grow its flagship repository platforms - Fedora and DSpace. DuraSpace will also expand its portfolio by offering new technologies and services that respond to the dynamic environment of the Web and to new requirements from existing and future users.</description>
<dc:date>2009-09-07T08:01:08Z</dc:date>
<dc:author>parmentierf</dc:author>
<dc:subject>dspace, fedora commons, institutional repository</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://duraspace.org/index.php"><img border="0" src="http://blogmarks.net/screenshots/2009/09/07/8a09a56145f352ab1ca96ddf8c34e26c.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://duraspace.org/index.php">DuraSpace</a></h4>
 
by <a href="http://blogmarks.net/user/parmentierf">parmentierf</a> 
<p class="description">The joined organization, named "DuraSpace," will sustain and grow its flagship repository platforms - Fedora and DSpace. DuraSpace will also expand its portfolio by offering new technologies and services that respond to the dynamic environment of the Web and to new requirements from existing and future users.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dspace">dspace</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/fedora%2Bcommons">fedora commons</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/institutional%2Brepository">institutional repository</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058495532">Copy</a> | 
<a href="http://blogmarks.net/link/3336395">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058490434">
<title>The joy of webscale identifiers « Jon Udell</title>
<link>http://blog.jonudell.net/2009/08/31/the-joy-of-webscale-identifiers/</link>
<description>&lt;blockquote&gt;&lt;p&gt;Beautifully said. Enormous synergies have gone unrealized because web publishers have chosen to mint new namespaces rather than add value to existing ones.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-09-02T13:36:03Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>uri, identification, http</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://blog.jonudell.net/2009/08/31/the-joy-of-webscale-identifiers/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/02/020eb35a72922a1cc849d25eb340b0a1.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://blog.jonudell.net/2009/08/31/the-joy-of-webscale-identifiers/">The joy of webscale identifiers « Jon Udell</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>Beautifully said. Enormous synergies have gone unrealized because web publishers have chosen to mint new namespaces rather than add value to existing ones.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/uri">uri</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/identification">identification</a>
<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=1058490434">Copy</a> | 
<a href="http://blogmarks.net/link/3332201">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/dzc/mark/1058487355">
<title>Create a video preview as animated GIF with FFmpeg and PHP SPL</title>
<link>http://www.alberton.info/video_preview_as_animated_gif_with_ffmpeg_and_spl.html</link>
<description>create the video preview, we need PHP &gt;= 5.1 with the Imagick extension and FFmpeg. FFmpeg supports most of the existing video formats, has a command line interface, and is available under the LGPL license.</description>
<dc:date>2009-08-31T23:51:11Z</dc:date>
<dc:author>dzc</dc:author>
<dc:subject>prog. Obj, lgpl, php, video, spl, gif</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.alberton.info/video_preview_as_animated_gif_with_ffmpeg_and_spl.html"><img border="0" src="http://blogmarks.net/screenshots/2009/08/31/7c6316ac59f41557bbc133f92bb19f35.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.alberton.info/video_preview_as_animated_gif_with_ffmpeg_and_spl.html">Create a video preview as animated GIF with FFmpeg and PHP SPL</a></h4>
 
by <a href="http://blogmarks.net/user/dzc">dzc</a> 
<p class="description">create the video preview, we need PHP >= 5.1 with the Imagick extension and FFmpeg. FFmpeg supports most of the existing video formats, has a command line interface, and is available under the LGPL license.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/prog.%2BObj">prog. Obj</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/lgpl">lgpl</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/video">video</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/spl">spl</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/gif">gif</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058487355">Copy</a> | 
<a href="http://blogmarks.net/link/3329451">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058482494">
<title>Using RDFa with DITA and DocBook</title>
<link>http://www.devx.com/semantic/Article/42543/1954?pf=true</link>
<description>&lt;blockquote&gt;&lt;p&gt;Adding RDFa to your DocBook or DITA documents has a nice payoff: easier addition of metadata that can be extracted by existing tools that follow an open standard. And it comes at a minimal co&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-08-27T03:41:30Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>rdfa, tools</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.devx.com/semantic/Article/42543/1954?pf=true"><img border="0" src="http://blogmarks.net/screenshots/2009/08/27/b2fbb351c580ba661bc35c59bbf25e02.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.devx.com/semantic/Article/42543/1954?pf=true">Using RDFa with DITA and DocBook</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>Adding RDFa to your DocBook or DITA documents has a nice payoff: easier addition of metadata that can be extracted by existing tools that follow an open standard. And it comes at a minimal co</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/rdfa">rdfa</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tools">tools</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058482494">Copy</a> | 
<a href="http://blogmarks.net/link/3325445">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Xavier Lacot/mark/1058477329">
<title>svgweb - Project Hosting on Google Code</title>
<link>http://code.google.com/p/svgweb/</link>
<description>SVG Web is a JavaScript library which provides SVG support on many browsers, including Internet Explorer, Firefox, and Safari. Using the library plus native SVG support you can instantly target ~95% of the existing installed web base.</description>
<dc:date>2009-08-24T11:33:41Z</dc:date>
<dc:author>Xavier Lacot</dc:author>
<dc:subject>web, javascript, library, code, svg, compatibility, vector, graph, Internet Explorer hack</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://code.google.com/p/svgweb/"><img border="0" src="http://blogmarks.net/screenshots/2009/08/25/9898c544ceca4d0a7b1dec73bb600187.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://code.google.com/p/svgweb/">svgweb - Project Hosting on Google Code</a></h4>
 
by <a href="http://blogmarks.net/user/Xavier Lacot">Xavier Lacot</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3300299">3 other(s)</a> 
<p class="description">SVG Web is a JavaScript library which provides SVG support on many browsers, including Internet Explorer, Firefox, and Safari. Using the library plus native SVG support you can instantly target ~95% of the existing installed web base.</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/javascript">javascript</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/code">code</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/svg">svg</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/compatibility">compatibility</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/vector">vector</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/graph">graph</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Internet%2BExplorer%2Bhack">Internet Explorer hack</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058477329">Copy</a> | 
<a href="http://blogmarks.net/link/3300299">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/marco/mark/1058448268">
<title>It's Finally Official, Microsoft &amp; Yahoo Make A Deal, Yahoo Gives Up On Search</title>
<link>http://searchengineland.com/its-finally-official-microsoft-yahoo-make-a-deal-yahoo-gives-up-on-search-23197</link>
<description>Microsoft will acquire an exclusive 10 year license to Yahoo!’s core search technologies, and Microsoft will have the ability to integrate Yahoo! search technologies into its existing web search platforms</description>
<dc:date>2009-07-29T21:14:27Z</dc:date>
<dc:author>marco</dc:author>
<dc:subject>search, microsoft, yahoo, search engine</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://searchengineland.com/its-finally-official-microsoft-yahoo-make-a-deal-yahoo-gives-up-on-search-23197"><img border="0" src="http://blogmarks.net/screenshots/2009/07/29/12b729c37be0bb4fa382560d3d84bdb5.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://searchengineland.com/its-finally-official-microsoft-yahoo-make-a-deal-yahoo-gives-up-on-search-23197">It's Finally Official, Microsoft &amp; Yahoo Make A Deal, Yahoo Gives Up On Search</a></h4>
 
by <a href="http://blogmarks.net/user/marco">marco</a> 
<p class="description">Microsoft will acquire an exclusive 10 year license to Yahoo!’s core search technologies, and Microsoft will have the ability to integrate Yahoo! search technologies into its existing web search platforms</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/search">search</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/microsoft">microsoft</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/yahoo">yahoo</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/search%2Bengine">search engine</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058448268">Copy</a> | 
<a href="http://blogmarks.net/link/3300917">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058447485">
<title>svgweb - Project Hosting on Google Code</title>
<link>http://code.google.com/p/svgweb/</link>
<description>&lt;blockquote&gt;&lt;p&gt;SVG Web is a JavaScript library which provides SVG support on many browsers, including Internet Explorer, Firefox, and Safari. Using the library plus native SVG support you can instantly target ~95% of the existing installed web base.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-07-29T02:19:15Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>javascript, svg</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://code.google.com/p/svgweb/"><img border="0" src="http://blogmarks.net/screenshots/2009/08/25/9898c544ceca4d0a7b1dec73bb600187.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://code.google.com/p/svgweb/">svgweb - Project Hosting on Google Code</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3300299">3 other(s)</a> 
<div class="description"><blockquote><p>SVG Web is a JavaScript library which provides SVG support on many browsers, including Internet Explorer, Firefox, and Safari. Using the library plus native SVG support you can instantly target ~95% of the existing installed web base.</p></blockquote></div>
<p class="tags">
<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/svg">svg</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058447485">Copy</a> | 
<a href="http://blogmarks.net/link/3300299">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/marco/mark/1058436209">
<title>Charging for Access to News Sites</title>
<link>http://daringfireball.net/2009/07/charging_for_access_to_news_sites</link>
<description>The question these companies should be asking is, &quot;How do we keep reporting and publishing good content?&quot; Instead, though, they're asking &quot;How do we keep making enough money to support our existing management and advertising divisions?&quot;</description>
<dc:date>2009-07-20T18:45:05Z</dc:date>
<dc:author>marco</dc:author>
<dc:subject>news, business</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://daringfireball.net/2009/07/charging_for_access_to_news_sites"><img border="0" src="http://blogmarks.net/screenshots/2009/07/20/f237447c1528b27425734c6e517c48f0.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://daringfireball.net/2009/07/charging_for_access_to_news_sites">Charging for Access to News Sites</a></h4>
 
by <a href="http://blogmarks.net/user/marco">marco</a> 
<p class="description">The question these companies should be asking is, "How do we keep reporting and publishing good content?" Instead, though, they're asking "How do we keep making enough money to support our existing management and advertising divisions?"</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/news">news</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/business">business</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058436209">Copy</a> | 
<a href="http://blogmarks.net/link/3290873">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ms_michel/mark/1058430606">
<title>WikiPlex </title>
<link>http://wikiplex.codeplex.com/</link>
<description>A regular expression based wiki engine that allows developers to integrate a wiki experience into an existing .NET application seamlessly and with little effort.</description>
<dc:date>2009-07-17T07:53:46Z</dc:date>
<dc:author>ms_michel</dc:author>
<dc:subject>.net, pour-memoire</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://wikiplex.codeplex.com/"><img border="0" src="http://blogmarks.net/screenshots/2009/07/17/06e7dbecb828da0ec78f59c000b61cb2.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://wikiplex.codeplex.com/">WikiPlex </a></h4>
 
by <a href="http://blogmarks.net/user/ms_michel">ms_michel</a> 
<p class="description">A regular expression based wiki engine that allows developers to integrate a wiki experience into an existing .NET application seamlessly and with little effort.</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/pour-memoire">pour-memoire</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058430606">Copy</a> | 
<a href="http://blogmarks.net/link/3287406">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/znarf/mark/1058422553">
<title>How to create packages? A tutorial with Moonmoon. « La Distribution Blog</title>
<link>http://ladistribution.net/blog/2009/07/how-to-create-a-package-tutorial-with-moonmoon/</link>
<description>&lt;blockquote&gt;
&lt;p&gt;Distributing a new or existing web application on La Distribution is really easy. All we have to do is to embed the application in what we call a package. As of today, La Distribution can theoretically support all PHP web applications, this mean there is tons of potential applications to package.&lt;/p&gt;
&lt;p&gt;Moonmoon logoIn this tutorial we’re going to package Moonmoon a PHP based PlanetPlanet clone. It’s relatively simple, it’s representative of a typical web application, and better, it’s from my friend Maurice! Frankly, I had no clue if the packaging was possible before starting writing this tutorial, so let’s cross our fingers.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Sympa ce tutoriel !&lt;/p&gt;</description>
<dc:date>2009-07-30T09:16:01Z</dc:date>
<dc:author>François Hodierne</dc:author>
<dc:subject>la distribution, web apps, ladistribution, php</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://ladistribution.net/blog/2009/07/how-to-create-a-package-tutorial-with-moonmoon/"><img border="0" src="http://blogmarks.net/screenshots/2009/07/30/e324fffed56aaab84b7b3d092dffb7ae.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://ladistribution.net/blog/2009/07/how-to-create-a-package-tutorial-with-moonmoon/">How to create packages? A tutorial with Moonmoon. « La Distribution Blog</a></h4>
 
by <a href="http://blogmarks.net/user/znarf">François Hodierne</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3280661">2 other(s)</a> 
<div class="description"><blockquote>
<p>Distributing a new or existing web application on La Distribution is really easy. All we have to do is to embed the application in what we call a package. As of today, La Distribution can theoretically support all PHP web applications, this mean there is tons of potential applications to package.</p>
<p>Moonmoon logoIn this tutorial we’re going to package Moonmoon a PHP based PlanetPlanet clone. It’s relatively simple, it’s representative of a typical web application, and better, it’s from my friend Maurice! Frankly, I had no clue if the packaging was possible before starting writing this tutorial, so let’s cross our fingers.</p>
</blockquote>

<p>Sympa ce tutoriel !</p></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/la%2Bdistribution">la distribution</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web%2Bapps">web apps</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ladistribution">ladistribution</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/php">php</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058422553">Copy</a> | 
<a href="http://blogmarks.net/link/3280661">React (1)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058419739">
<title>Print media CSS: The Guardian example : Articles : Mark Boulton</title>
<link>http://www.markboulton.co.uk/articles/detail/print_media_css_the_guardian_example/</link>
<description>&lt;blockquote&gt;&lt;p&gt;Print media stylesheets are rarely used by text-heavy websites to present their content in the best possible way for when users press the print button.&lt;/p&gt;&lt;p&gt;This example of The Guardian uses a rebuilt web standards template to present the existing design for the screen. The print media stylesheet however presents the content more inline with the Guardian newspaper rather than the website.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-07-07T02:37:10Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>css, print</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.markboulton.co.uk/articles/detail/print_media_css_the_guardian_example/"><img border="0" src="http://blogmarks.net/screenshots/2009/07/07/67a7117e1729687767d4eeef5d8e4288.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.markboulton.co.uk/articles/detail/print_media_css_the_guardian_example/">Print media CSS: The Guardian example : Articles : Mark Boulton</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1165151">1 other(s)</a> 
<div class="description"><blockquote><p>Print media stylesheets are rarely used by text-heavy websites to present their content in the best possible way for when users press the print button.</p><p>This example of The Guardian uses a rebuilt web standards template to present the existing design for the screen. The print media stylesheet however presents the content more inline with the Guardian newspaper rather than the website.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/css">css</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/print">print</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058419739">Copy</a> | 
<a href="http://blogmarks.net/link/1165151">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>