<?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/results">
<title>Public marks with search results</title>
<description>Public marks with search results</description>
<link>http://blogmarks.net/marks/search/results</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/tlaporte/mark/1058578150"/>
<rdf:li resource="http://blogmarks.net/api/user/Fabrice.bonny/mark/1058574160"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058562239"/>
<rdf:li resource="http://blogmarks.net/api/user/srcmax/mark/1058560022"/>
<rdf:li resource="http://blogmarks.net/api/user/dzc/mark/1058558964"/>
<rdf:li resource="http://blogmarks.net/api/user/parmentierf/mark/1058555066"/>
<rdf:li resource="http://blogmarks.net/api/user/br1o/mark/1058556400"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058550483"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058550425"/>
<rdf:li resource="http://blogmarks.net/api/user/eledo34/mark/1058548917"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058546662"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058524122"/>
<rdf:li resource="http://blogmarks.net/api/user/parmentierf/mark/1058522385"/>
<rdf:li resource="http://blogmarks.net/api/user/srcmax/mark/1058520177"/>
<rdf:li resource="http://blogmarks.net/api/user/Fiber_Optic/mark/1058519425"/>
<rdf:li resource="http://blogmarks.net/api/user/decembre/mark/1058547762"/>
<rdf:li resource="http://blogmarks.net/api/user/decembre/mark/1058547763"/>
<rdf:li resource="http://blogmarks.net/api/user/decembre/mark/1058547764"/>
<rdf:li resource="http://blogmarks.net/api/user/oseres/mark/1058510531"/>
<rdf:li resource="http://blogmarks.net/api/user/parmentierf/mark/1058502672"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058501868"/>
<rdf:li resource="http://blogmarks.net/api/user/access2/mark/1058499750"/>
<rdf:li resource="http://blogmarks.net/api/user/access2/mark/1058499736"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058499469"/>
<rdf:li resource="http://blogmarks.net/api/user/Neewok/mark/1058497837"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/tlaporte/mark/1058578150">
<title>Results and comments - www.matousec.com</title>
<link>http://www.matousec.com/projects/proactive-security-challenge/results.php</link>
<description></description>
<dc:date>2009-11-10T16:16:24Z</dc:date>
<dc:author>tlaporte</dc:author>
<dc:subject>securite internet</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.matousec.com/projects/proactive-security-challenge/results.php"><img border="0" src="http://blogmarks.net/screenshots/2009/11/10/2683b8fa7e09c365c6a3db0fa159e05f.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.matousec.com/projects/proactive-security-challenge/results.php">Results and comments - www.matousec.com</a></h4>
 
by <a href="http://blogmarks.net/user/tlaporte">tlaporte</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/securite%2Binternet">securite internet</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058578150">Copy</a> | 
<a href="http://blogmarks.net/link/3405044">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Fabrice.bonny/mark/1058574160">
<title>WebAIM: Screen Reader User Survey Results</title>
<link>http://webaim.org/projects/screenreadersurvey2/</link>
<description></description>
<dc:date>2009-11-06T20:22:42Z</dc:date>
<dc:author>Fabrice.bonny</dc:author>
<dc:subject>e-accessibilité, enquête</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://webaim.org/projects/screenreadersurvey2/"><img border="0" src="http://blogmarks.net/screenshots/2009/11/06/5719b680a5226796c804f667095c5f15.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://webaim.org/projects/screenreadersurvey2/">WebAIM: Screen Reader User Survey Results</a></h4>
 
by <a href="http://blogmarks.net/user/Fabrice.bonny">Fabrice.bonny</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/e-accessibilit%25C3%25A9">e-accessibilité</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/enqu%25C3%25AAte">enquête</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058574160">Copy</a> | 
<a href="http://blogmarks.net/link/3402254">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058562239">
<title>Time/Weather Desktop on Flickr - Photo Sharing!</title>
<link>http://www.flickr.com/photos/bopuc/4039178260/</link>
<description>&lt;blockquote&gt;&lt;p&gt;Well, most of the work is done by Earthdesk and GeekTool 3.&lt;/p&gt;&lt;p&gt;Earthdesk is set to Natural Color, Equirectangular projection, Natural Color, Real Moonlight, centered on Vienna, Background: Starfield. Zoom 80%, Clouds 80%, Brightness 80%.&lt;/p&gt;&lt;p&gt;In GeekTool, the times and the weathers are all separate Shell &quot;geeklets&quot;.&lt;/p&gt;&lt;p&gt;Times are generated by running shell commands like&lt;/p&gt;&lt;p&gt;env TZ=Asia/Tokyo date &quot; %l:%M %p&quot;&lt;/p&gt;&lt;p&gt;every 20 seconds&lt;/p&gt;&lt;p&gt;The weather is the tricky part. The way I am doing it now, if I am not careful, gets me throttled for too many concurrent requests to the wunderground.com API server. It also fails badly if I am disconnected, so I will need to do it differently.&lt;/p&gt;&lt;p&gt;FWIW: I have a PHP script which I run as separate Shell Geeklets. I invoke it with the name of the city I want. It then hits wunderground and gets back an XML stream of the local weather, which I parse, format and echo. (the way I'd change this is run the script from cron, with a 30 second wait between requests, and cache the results locally, which I would then call from the Shell Geeklets)&lt;/p&gt;&lt;p&gt;From there it's just a question of setting fonts, sizes, colors and moving the little Geeklet boxes around as you want them.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-10-24T15:00:49Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>semanticdesktop, meteo, geek</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.flickr.com/photos/bopuc/4039178260/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/24/5639bd0d870c47d4c396495e456804ec.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.flickr.com/photos/bopuc/4039178260/">Time/Weather Desktop on Flickr - Photo Sharing!</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>Well, most of the work is done by Earthdesk and GeekTool 3.</p><p>Earthdesk is set to Natural Color, Equirectangular projection, Natural Color, Real Moonlight, centered on Vienna, Background: Starfield. Zoom 80%, Clouds 80%, Brightness 80%.</p><p>In GeekTool, the times and the weathers are all separate Shell "geeklets".</p><p>Times are generated by running shell commands like</p><p>env TZ=Asia/Tokyo date " %l:%M %p"</p><p>every 20 seconds</p><p>The weather is the tricky part. The way I am doing it now, if I am not careful, gets me throttled for too many concurrent requests to the wunderground.com API server. It also fails badly if I am disconnected, so I will need to do it differently.</p><p>FWIW: I have a PHP script which I run as separate Shell Geeklets. I invoke it with the name of the city I want. It then hits wunderground and gets back an XML stream of the local weather, which I parse, format and echo. (the way I'd change this is run the script from cron, with a 30 second wait between requests, and cache the results locally, which I would then call from the Shell Geeklets)</p><p>From there it's just a question of setting fonts, sizes, colors and moving the little Geeklet boxes around as you want them.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/semanticdesktop">semanticdesktop</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/meteo">meteo</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/geek">geek</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058562239">Copy</a> | 
<a href="http://blogmarks.net/link/3392654">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/srcmax/mark/1058560022">
<title>Official Google Blog: RT @google: Tweets and updates and search, oh my!</title>
<link>http://googleblog.blogspot.com/2009/10/rt-google-tweets-and-updates-and-search.html</link>
<description>&lt;blockquote&gt;
&lt;p&gt;Given this new type of information and its value to search, we are very excited to announce that we have reached an agreement with Twitter to include their updates in our search results. We believe that our search results and user experience will greatly benefit from the inclusion of this up-to-the-minute data, and we look forward to having a product that showcases how tweets can make search better in the coming months&lt;/p&gt;
&lt;/blockquote&gt;</description>
<dc:date>2009-10-22T08:37:46Z</dc:date>
<dc:author>srcmax</dc:author>
<dc:subject>google, twitter</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://googleblog.blogspot.com/2009/10/rt-google-tweets-and-updates-and-search.html"><img border="0" src="http://blogmarks.net/screenshots/2009/10/22/713572da87995fb3e5ed497fba7478d6.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://googleblog.blogspot.com/2009/10/rt-google-tweets-and-updates-and-search.html">Official Google Blog: RT @google: Tweets and updates and search, oh my!</a></h4>
 
by <a href="http://blogmarks.net/user/srcmax">srcmax</a> 
<div class="description"><blockquote>
<p>Given this new type of information and its value to search, we are very excited to announce that we have reached an agreement with Twitter to include their updates in our search results. We believe that our search results and user experience will greatly benefit from the inclusion of this up-to-the-minute data, and we look forward to having a product that showcases how tweets can make search better in the coming months</p>
</blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/twitter">twitter</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058560022">Copy</a> | 
<a href="http://blogmarks.net/link/3390789">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/dzc/mark/1058558964">
<title>Browser support for CSS3 and HTML5, We've tested all the A-grade browsers for their CSS3 and HTML5 support using FindMeByIP.com. The results have been very interesting. - Deep Blue Sky Digital Ltd - Web design and development in Bath, Bristol &amp; London</title>
<link>http://www.deepbluesky.com/blog/-/browser-support-for-css3-and-html5_72/</link>
<description></description>
<dc:date>2009-10-21T05:04:06Z</dc:date>
<dc:author>dzc</dc:author>
<dc:subject>html5, css3, navigateur, browser compatibility, intégration css/xhtml, conception web, Standard du Web</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.deepbluesky.com/blog/-/browser-support-for-css3-and-html5_72/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/21/51298a15abc56f4f4f8b2fcfb9ac1cd0.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.deepbluesky.com/blog/-/browser-support-for-css3-and-html5_72/">Browser support for CSS3 and HTML5, We've tested all the A-grade browsers for their CSS3 and HTML5 support using FindMeByIP.com. The results have been very interesting. - Deep Blue Sky Digital Ltd - Web design and development in Bath, Bristol &amp; London</a></h4>
 
by <a href="http://blogmarks.net/user/dzc">dzc</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3388894">1 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html5">html5</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/css3">css3</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/navigateur">navigateur</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/browser%2Bcompatibility">browser compatibility</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/int%25C3%25A9gration%2Bcss%252Fxhtml">intégration css/xhtml</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/conception%2Bweb">conception web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Standard%2Bdu%2BWeb">Standard du Web</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058558964">Copy</a> | 
<a href="http://blogmarks.net/link/3388894">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/parmentierf/mark/1058555066">
<title>Wolfram|Alpha Webservice API</title>
<link>http://products.wolframalpha.com/api/webserviceapi.html</link>
<description>The Wolfram|Alpha API gives you access to the Wolfram|Alpha platform at all levels—from individual results to complete Wolfram|Alpha output pages. The API operates as a high-performance REST-style webservice, with convenient bindings for all popular languages and platforms.</description>
<dc:date>2009-10-19T13:49:53Z</dc:date>
<dc:author>parmentierf</dc:author>
<dc:subject>api, dev, web, Wolfram Alpha</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://products.wolframalpha.com/api/webserviceapi.html"><img border="0" src="http://blogmarks.net/screenshots/2009/10/19/5a90701fdaa7f662516684230bf13587.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://products.wolframalpha.com/api/webserviceapi.html">Wolfram|Alpha Webservice API</a></h4>
 
by <a href="http://blogmarks.net/user/parmentierf">parmentierf</a> 
<p class="description">The Wolfram|Alpha API gives you access to the Wolfram|Alpha platform at all levels—from individual results to complete Wolfram|Alpha output pages. The API operates as a high-performance REST-style webservice, with convenient bindings for all popular languages and platforms.</p>
<p class="tags">
<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/dev">dev</a>
<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/Wolfram%2BAlpha">Wolfram Alpha</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058555066">Copy</a> | 
<a href="http://blogmarks.net/link/3387766">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/br1o/mark/1058556400">
<title>Browser support for CSS3 and HTML5, We've tested all the A-grade browsers for their CSS3 and HTML5 support using FindMeByIP.com. The results have been very interesting. : Deep Blue Sky Digital Ltd : Web designers and developers in Bath</title>
<link>http://www.deepbluesky.com/blog/-/browser-support-for-css3-and-html5_72/</link>
<description></description>
<dc:date>2009-10-17T22:23:05Z</dc:date>
<dc:author>br1o</dc:author>
<dc:subject>reference, browser, webstandards, developer, support, web-standards, compatibility, browsers, standards, css, html, firefox, html5, css3</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.deepbluesky.com/blog/-/browser-support-for-css3-and-html5_72/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/21/51298a15abc56f4f4f8b2fcfb9ac1cd0.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.deepbluesky.com/blog/-/browser-support-for-css3-and-html5_72/">Browser support for CSS3 and HTML5, We've tested all the A-grade browsers for their CSS3 and HTML5 support using FindMeByIP.com. The results have been very interesting. : Deep Blue Sky Digital Ltd : Web designers and developers in Bath</a></h4>
 
by <a href="http://blogmarks.net/user/br1o">br1o</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3388894">1 other(s)</a> 
<p class="tags">
<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/browser">browser</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webstandards">webstandards</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/developer">developer</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/support">support</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web-standards">web-standards</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/browsers">browsers</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/standards">standards</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/html">html</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/firefox">firefox</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html5">html5</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/css3">css3</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058556400">Copy</a> | 
<a href="http://blogmarks.net/link/3388894">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058550483">
<title>Adding meaning to your HTTP error pages! - Opera Developer Community</title>
<link>http://dev.opera.com/articles/view/adding-meaning-to-http-error-pages/</link>
<description>&lt;blockquote&gt;&lt;p&gt;When searching for something on the web we’ve all had the experience of clicking on a link in a search engine’s results page only to find that the page no longer exists. If there’s no information on that page other than a default error message, the most likely course of action on the user’s part is to press the back button and try the next search result.&lt;/p&gt;&lt;p&gt;As site authors we can make our error pages more meaningful to our users, so that an error becomes an opportunity to bring the user back into a site and show them content that’s relevant to what they’re looking for. In this article I’ll show you how to do just that.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-10-15T02:40:45Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>http</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://dev.opera.com/articles/view/adding-meaning-to-http-error-pages/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/15/a172019c5c10d0525a98c0ec526fea11.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://dev.opera.com/articles/view/adding-meaning-to-http-error-pages/">Adding meaning to your HTTP error pages! - Opera Developer Community</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>When searching for something on the web we’ve all had the experience of clicking on a link in a search engine’s results page only to find that the page no longer exists. If there’s no information on that page other than a default error message, the most likely course of action on the user’s part is to press the back button and try the next search result.</p><p>As site authors we can make our error pages more meaningful to our users, so that an error becomes an opportunity to bring the user back into a site and show them content that’s relevant to what they’re looking for. In this article I’ll show you how to do just that.</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=1058550483">Copy</a> | 
<a href="http://blogmarks.net/link/3383822">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058550425">
<title>Coding from Scratch: A Conversation with Virtual Reality Pioneer Jaron Lanier, Part One</title>
<link>http://java.sun.com/features/2003/01/lanier_qa1.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;answer Right. And it results in a type of error that doesn't teach you anything. You have chaotic errors where all you can say is, &quot;Boy, this was really screwed up, and I guess I need to go in and go through the whole thing and fix it.&quot; You don't have errors that are proportionate to the source of the error. And that means you can never have any sense of gradual evolution or approximate systems. So, the real difference between the current idea of software, which is protocol adherence, and the idea I'm discussing, pattern recognition, has to do with the kinds of errors we're creating. We need a system in which errors are more often proportional to the source of the error.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-10-15T01:32:31Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>programmation</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://java.sun.com/features/2003/01/lanier_qa1.html"><img border="0" src="http://blogmarks.net/screenshots/2009/10/15/7e110e83e48a38dafce87dbe295b07c7.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://java.sun.com/features/2003/01/lanier_qa1.html">Coding from Scratch: A Conversation with Virtual Reality Pioneer Jaron Lanier, Part One</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1180844">1 other(s)</a> 
<div class="description"><blockquote><p>answer Right. And it results in a type of error that doesn't teach you anything. You have chaotic errors where all you can say is, "Boy, this was really screwed up, and I guess I need to go in and go through the whole thing and fix it." You don't have errors that are proportionate to the source of the error. And that means you can never have any sense of gradual evolution or approximate systems. So, the real difference between the current idea of software, which is protocol adherence, and the idea I'm discussing, pattern recognition, has to do with the kinds of errors we're creating. We need a system in which errors are more often proportional to the source of the error.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/programmation">programmation</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058550425">Copy</a> | 
<a href="http://blogmarks.net/link/1180844">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/eledo34/mark/1058548917">
<title>server icon search results, free download server icons, IconSeeker.com</title>
<link>http://www.iconseeker.com/search/server/</link>
<description></description>
<dc:date>2009-10-13T06:26:20Z</dc:date>
<dc:author>eledo34</dc:author>
<dc:subject>free, icon, icones</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.iconseeker.com/search/server/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/13/453a1cf7ba9c4eddd9e02c83bb72d17f.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.iconseeker.com/search/server/">server icon search results, free download server icons, IconSeeker.com</a></h4>
 
by <a href="http://blogmarks.net/user/eledo34">eledo34</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/free">free</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/icon">icon</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/icones">icones</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058548917">Copy</a> | 
<a href="http://blogmarks.net/link/3382513">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058546662">
<title>PhotoSketch</title>
<link>http://cg.cs.tsinghua.edu.cn/montage/main.htm</link>
<description>&lt;blockquote&gt;&lt;p&gt;We present a system that composes a realistic picture from a simple freehand sketch annotated with text labels. The composed picture is generated by seamlessly stitching several photographs in agreement with the sketch and text labels; these are found by searching the Internet. Although online image search generates many inappropriate results, our system is able to automatically select suitable photographs to generate a high quality composition, using a filtering scheme to exclude undesirable images. We also provide a novel image blending algorithm to allow seamless image composition. Each blending result is given a numeric score, allowing us to find an optimal combination of discovered images. Experimental results show the method is very successful; we also evaluate our system using the results from two user studies.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-10-11T09:15:57Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>photographie, authoringtool</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://cg.cs.tsinghua.edu.cn/montage/main.htm"><img border="0" src="http://blogmarks.net/screenshots/2009/10/11/e21f6ac972cbc4f9c4781ac260c2bd9e.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://cg.cs.tsinghua.edu.cn/montage/main.htm">PhotoSketch</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>We present a system that composes a realistic picture from a simple freehand sketch annotated with text labels. The composed picture is generated by seamlessly stitching several photographs in agreement with the sketch and text labels; these are found by searching the Internet. Although online image search generates many inappropriate results, our system is able to automatically select suitable photographs to generate a high quality composition, using a filtering scheme to exclude undesirable images. We also provide a novel image blending algorithm to allow seamless image composition. Each blending result is given a numeric score, allowing us to find an optimal combination of discovered images. Experimental results show the method is very successful; we also evaluate our system using the results from two user studies.</p></blockquote></div>
<p class="tags">
<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/authoringtool">authoringtool</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058546662">Copy</a> | 
<a href="http://blogmarks.net/link/3380588">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058524122">
<title>Lucid Imagination » Solr’s New Clustering Capabilities</title>
<link>http://www.lucidimagination.com/blog/2009/09/28/solrs-new-clustering-capabilities/</link>
<description>&lt;blockquote&gt;&lt;p&gt;One of the new things in Solr 1.4 that I am particularly excited about is the new document and search results clustering capabilities.  This is an optional module that lives in Solr’s contrib/clustering directory and was added via SOLR-769.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-09-30T10:26:48Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>solr, search-engine</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.lucidimagination.com/blog/2009/09/28/solrs-new-clustering-capabilities/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/30/400c2df20f6af4cec1c1df107662cd85.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.lucidimagination.com/blog/2009/09/28/solrs-new-clustering-capabilities/">Lucid Imagination » Solr’s New Clustering Capabilities</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>One of the new things in Solr 1.4 that I am particularly excited about is the new document and search results clustering capabilities.  This is an optional module that lives in Solr’s contrib/clustering directory and was added via SOLR-769.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/solr">solr</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/search-engine">search-engine</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058524122">Copy</a> | 
<a href="http://blogmarks.net/link/3359938">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/parmentierf/mark/1058522385">
<title>OAI 2.0 Request Results</title>
<link>http://www.numes.fr:8080/numes/oai/public.html?verb=Identify</link>
<description>You are viewing an HTML version of the XML OAI response.</description>
<dc:date>2009-09-28T13:25:36Z</dc:date>
<dc:author>parmentierf</dc:author>
<dc:subject>xml, html, oai, xsl</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.numes.fr:8080/numes/oai/public.html?verb=Identify"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.numes.fr:8080/numes/oai/public.html?verb=Identify">OAI 2.0 Request Results</a></h4>
 
by <a href="http://blogmarks.net/user/parmentierf">parmentierf</a> 
<p class="description">You are viewing an HTML version of the XML OAI response.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xml">xml</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html">html</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/oai">oai</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xsl">xsl</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058522385">Copy</a> | 
<a href="http://blogmarks.net/link/3358472">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/srcmax/mark/1058520177">
<title>Official Google Webmaster Central Blog: Using named anchors to identify sections on your pages</title>
<link>http://googlewebmastercentral.blogspot.com/2009/09/using-named-anchors-to-identify.html</link>
<description>&lt;blockquote&gt;
&lt;p&gt;We generate these deep links completely algorithmically, based on page structure, so they could be displayed for any site (and of course money isn't involved in any way, so you can't pay to get these links). There are a few things you can do to increase the chances that they might appear on your pages. First, ensure that long, multi-topic pages on your site are well-structured and broken into distinct logical sections. Second, ensure that each section has an associated anchor with a descriptive name (i.e., not just &quot;Section 2.1&quot;), and that your page includes a &quot;table of contents&quot; which links to the individual anchors. The new in-snippet links only appear for relevant queries, so you won't see it on the results all the time — only when we think that a link to a section would be highly useful for a particular query.&lt;/p&gt;
&lt;/blockquote&gt;</description>
<dc:date>2009-09-25T20:32:01Z</dc:date>
<dc:author>srcmax</dc:author>
<dc:subject>google, référencement</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://googlewebmastercentral.blogspot.com/2009/09/using-named-anchors-to-identify.html"><img border="0" src="http://blogmarks.net/screenshots/2009/09/25/8cdbc5a5cbbde52ce76ffca47fe1c546.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://googlewebmastercentral.blogspot.com/2009/09/using-named-anchors-to-identify.html">Official Google Webmaster Central Blog: Using named anchors to identify sections on your pages</a></h4>
 
by <a href="http://blogmarks.net/user/srcmax">srcmax</a> 
<div class="description"><blockquote>
<p>We generate these deep links completely algorithmically, based on page structure, so they could be displayed for any site (and of course money isn't involved in any way, so you can't pay to get these links). There are a few things you can do to increase the chances that they might appear on your pages. First, ensure that long, multi-topic pages on your site are well-structured and broken into distinct logical sections. Second, ensure that each section has an associated anchor with a descriptive name (i.e., not just "Section 2.1"), and that your page includes a "table of contents" which links to the individual anchors. The new in-snippet links only appear for relevant queries, so you won't see it on the results all the time — only when we think that a link to a section would be highly useful for a particular query.</p>
</blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/r%25C3%25A9f%25C3%25A9rencement">référencement</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058520177">Copy</a> | 
<a href="http://blogmarks.net/link/3356670">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Fiber_Optic/mark/1058519425">
<title>FitNesse</title>
<link>http://fitnesse.org/</link>
<description>FitNesse is a software testing tool.
From another perspective, FitNesse is a lightweight, open-source framework that makes it easy for software teams to:
Collaboratively define Acceptance Tests -- web pages containing simple tables of inputs and expected outputs.
Run those tests and see the results </description>
<dc:date>2009-09-24T21:50:49Z</dc:date>
<dc:author>Fiber_Optic</dc:author>
<dc:subject>tests</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://fitnesse.org/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/24/eb97fec2ae1bc8f26b454bfd73a77287.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://fitnesse.org/">FitNesse</a></h4>
 
by <a href="http://blogmarks.net/user/Fiber_Optic">Fiber_Optic</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/130712">6 other(s)</a> 
<p class="description">FitNesse is a software testing tool.
From another perspective, FitNesse is a lightweight, open-source framework that makes it easy for software teams to:
Collaboratively define Acceptance Tests -- web pages containing simple tables of inputs and expected outputs.
Run those tests and see the results </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tests">tests</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058519425">Copy</a> | 
<a href="http://blogmarks.net/link/130712">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/decembre/mark/1058547762">
<title>Pipes: flickr image search</title>
<link>http://pipes.yahoo.com/pipes/pipe.info?_id=8be57faa91d19759bef72e8fd8188607</link>
<description>flickr image search This pipe is designed to search images from flickr.com. you can enter the input and see the results as LIST or IMAGES</description>
<dc:date>2009-09-21T08:03:19Z</dc:date>
<dc:author>decembre</dc:author>
<dc:subject>flickr, FlickrSurf+, yahoo, yahoo-pipes, labs, pipes, search, SearchEngine, recherche, rechercher</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://pipes.yahoo.com/pipes/pipe.info?_id=8be57faa91d19759bef72e8fd8188607"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://pipes.yahoo.com/pipes/pipe.info?_id=8be57faa91d19759bef72e8fd8188607">Pipes: flickr image search</a></h4>
 
by <a href="http://blogmarks.net/user/decembre">decembre</a> 
<p class="description">flickr image search This pipe is designed to search images from flickr.com. you can enter the input and see the results as LIST or IMAGES</p>
<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/FlickrSurf%252B">FlickrSurf+</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/yahoo-pipes">yahoo-pipes</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/labs">labs</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/pipes">pipes</a>
<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/SearchEngine">SearchEngine</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/recherche">recherche</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/rechercher">rechercher</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058547762">Copy</a> | 
<a href="http://blogmarks.net/link/3381507">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/decembre/mark/1058547763">
<title>Browse Pipes: Pipes using 'flickr.com' (7428 results)</title>
<link>http://pipes.yahoo.com/pipes/search?r=source%3Aflickr.com</link>
<description>Pipes using 'flickr.com' (7428 results)</description>
<dc:date>2009-09-21T07:58:38Z</dc:date>
<dc:author>decembre</dc:author>
<dc:subject>flickr, FlickrSurf+, pipes, yahoo-pipes, labs, projet, project, online, tool, outil, dev, development, code</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://pipes.yahoo.com/pipes/search?r=source%3Aflickr.com"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://pipes.yahoo.com/pipes/search?r=source%3Aflickr.com">Browse Pipes: Pipes using 'flickr.com' (7428 results)</a></h4>
 
by <a href="http://blogmarks.net/user/decembre">decembre</a> 
<p class="description">Pipes using 'flickr.com' (7428 results)</p>
<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/FlickrSurf%252B">FlickrSurf+</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/pipes">pipes</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/yahoo-pipes">yahoo-pipes</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/labs">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/project">project</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/online">online</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tool">tool</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/outil">outil</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/development">development</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/code">code</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058547763">Copy</a> | 
<a href="http://blogmarks.net/link/3381508">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/decembre/mark/1058547764">
<title>SML Wiki: Interestingness(note: work in progress)</title>
<link>http://wiki.seeminglee.com/interestingness</link>
<description>Interestingness is a media (images, videos, etc) ranking algorithm to provide as an additional metric for search results. The algorithm is based upon an algorithm created by the Flickr team, and is further enhanced by metadata knowledge resulted from the Del.icio.us development.   The algorithm was first unveiled publicly on Flickr on 2005-08-01.1 SML.SML: Interestingness = f(views, faves, comments, tags, time, user, network relationships);  The ranking is based on one or more of the following factors:      * the quantity of user-entered metadata2 (i.e. tags)     * the number of users who have assigned metadata3     * the number of favorites assigned to the photo4     * relationship between the person who uploaded the photo and the people who are commenting5     * access patterns related to the media object6 (i.e. where the clickthroughs are coming from; who comments on it and when)7     * a lapse of time related to the media object8 (i.e. velocity of metadata acquisition)</description>
<dc:date>2009-09-21T07:42:05Z</dc:date>
<dc:author>decembre</dc:author>
<dc:subject>FlickrSurf+, flickr, analyser, application, yahoo, delicious, dev, del.icio.us, code, favoris, user, tag, comment, view, result, ranking, lab, projet, project</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://wiki.seeminglee.com/interestingness"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://wiki.seeminglee.com/interestingness">SML Wiki: Interestingness(note: work in progress)</a></h4>
 
by <a href="http://blogmarks.net/user/decembre">decembre</a> 
<p class="description">Interestingness is a media (images, videos, etc) ranking algorithm to provide as an additional metric for search results. The algorithm is based upon an algorithm created by the Flickr team, and is further enhanced by metadata knowledge resulted from the Del.icio.us development.   The algorithm was first unveiled publicly on Flickr on 2005-08-01.1 SML.SML: Interestingness = f(views, faves, comments, tags, time, user, network relationships);  The ranking is based on one or more of the following factors:      * the quantity of user-entered metadata2 (i.e. tags)     * the number of users who have assigned metadata3     * the number of favorites assigned to the photo4     * relationship between the person who uploaded the photo and the people who are commenting5     * access patterns related to the media object6 (i.e. where the clickthroughs are coming from; who comments on it and when)7     * a lapse of time related to the media object8 (i.e. velocity of metadata acquisition)</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/FlickrSurf%252B">FlickrSurf+</a>
<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/analyser">analyser</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/application">application</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/yahoo">yahoo</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/delicious">delicious</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/del.icio.us">del.icio.us</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/favoris">favoris</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/user">user</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tag">tag</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/comment">comment</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/view">view</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/result">result</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ranking">ranking</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/lab">lab</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/project">project</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058547764">Copy</a> | 
<a href="http://blogmarks.net/link/3381509">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/oseres/mark/1058510531">
<title>The Soulmen | We Got It! › Ulysses 2.0</title>
<link>http://www.the-soulmen.com/ulysses/</link>
<description>// Whether you're a blogger, a poet or a published novelist: Ulysses 2.0 is the *definite* package for all your creative writing needs. Brainstorm, draft, revise, submit; distraction-free and fully focused. No strings nor styles attached.
# A NEW WRITING EXPERIENCE · Forget everything you know about traditional text editors and word processors. Forget about WYSIWYG, formats, rulers and page sizes. Then forget about common means of managing your documents. Forget about the Finder, files &amp; folders, sub-sub-folders and Spotlight search results. Ulysses is not like that. Not at all.</description>
<dc:date>2009-09-20T13:48:24Z</dc:date>
<dc:author>oseres</dc:author>
<dc:subject>writing, mac, tool</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.the-soulmen.com/ulysses/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/20/a966a0fd0ddcbe4869a9d9ac0642a7e8.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.the-soulmen.com/ulysses/">The Soulmen | We Got It! › Ulysses 2.0</a></h4>
 
by <a href="http://blogmarks.net/user/oseres">oseres</a> 
<p class="description">// Whether you're a blogger, a poet or a published novelist: Ulysses 2.0 is the *definite* package for all your creative writing needs. Brainstorm, draft, revise, submit; distraction-free and fully focused. No strings nor styles attached.
# A NEW WRITING EXPERIENCE · Forget everything you know about traditional text editors and word processors. Forget about WYSIWYG, formats, rulers and page sizes. Then forget about common means of managing your documents. Forget about the Finder, files & folders, sub-sub-folders and Spotlight search results. Ulysses is not like that. Not at all.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/writing">writing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mac">mac</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tool">tool</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058510531">Copy</a> | 
<a href="http://blogmarks.net/link/3348169">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/parmentierf/mark/1058502672">
<title>Evaluation of Digital Repository Software at the National Library of Medicine</title>
<link>http://www.dlib.org/dlib/may09/marill/05marill.html</link>
<description>The National Institutes of Health (NIH) National Library of Medicine® (NLM) undertook an 18-month project to evaluate, test and recommend digital repository software and systems to support NLM's collection and preservation of a wide variety of digital objects. This article outlines the methodology NLM used to analyze the landscape of repository software and select three systems for in-depth testing. Finally, the article discusses the evaluation results and next steps for NLM. This project followed an earlier NLM working group, which created functional requirements and identified key policy issues for an NLM digital repository to aid in building NLM's collection in the digital environment. </description>
<dc:date>2009-09-14T09:43:42Z</dc:date>
<dc:author>parmentierf</dc:author>
<dc:subject>institutional repository, dspace, fedora commons, eprints, comparaison</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.dlib.org/dlib/may09/marill/05marill.html"><img border="0" src="http://blogmarks.net/screenshots/2009/09/14/5ce63c05236d8498f5685a208b2eacb3.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.dlib.org/dlib/may09/marill/05marill.html">Evaluation of Digital Repository Software at the National Library of Medicine</a></h4>
 
by <a href="http://blogmarks.net/user/parmentierf">parmentierf</a> 
<p class="description">The National Institutes of Health (NIH) National Library of Medicine® (NLM) undertook an 18-month project to evaluate, test and recommend digital repository software and systems to support NLM's collection and preservation of a wide variety of digital objects. This article outlines the methodology NLM used to analyze the landscape of repository software and select three systems for in-depth testing. Finally, the article discusses the evaluation results and next steps for NLM. This project followed an earlier NLM working group, which created functional requirements and identified key policy issues for an NLM digital repository to aid in building NLM's collection in the digital environment. </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/institutional%2Brepository">institutional repository</a>
<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/eprints">eprints</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/comparaison">comparaison</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058502672">Copy</a> | 
<a href="http://blogmarks.net/link/3342103">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058501868">
<title>Geographic library</title>
<link>http://charles.karney.info/geographic/</link>
<description>&lt;blockquote&gt;&lt;p&gt;GeographicLib is a small set of C   classes for performing conversions between geographic, UTM, UPS, MGRS, geocentric, and local cartesian coordinates and for solving geodesic problems. The emphasis is on returning accurate results with errors close to round-off (about 5–15 nm). In addition, various properties of the Transverse Mercator Projection are described and an accurate algorithm for Geodesics on the Ellipsoid is given.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-09-13T12:29:30Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>geo, library, c++, algoritme</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://charles.karney.info/geographic/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/13/68a2a246298820924b519bb5bcfe462a.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://charles.karney.info/geographic/">Geographic library</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>GeographicLib is a small set of C   classes for performing conversions between geographic, UTM, UPS, MGRS, geocentric, and local cartesian coordinates and for solving geodesic problems. The emphasis is on returning accurate results with errors close to round-off (about 5–15 nm). In addition, various properties of the Transverse Mercator Projection are described and an accurate algorithm for Geodesics on the Ellipsoid is given.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/geo">geo</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/c%252B%252B">c++</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/algoritme">algoritme</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058501868">Copy</a> | 
<a href="http://blogmarks.net/link/3341445">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/access2/mark/1058499750">
<title>Amazon - Constrained Search vs. Random Results</title>
<link>http://www.squidoo.com/amazon</link>
<description>The way to find needles in the immense haystack of Amazon.com is through constrained search.

Amazon's search function, like most others, claims to use a logical AND operator on keywords. That is search results for &quot;Amazon Warriors,&quot; for example, should contain both &quot;Amazon&quot; AND &quot;Warriors.&quot;

In fact, you will find that, all things being equal -- &quot;Amazon&quot; AND &quot;Warriors&quot; results will appear higher than &quot;Amazon&quot; OR &quot;Warriors&quot; results.

You need to &quot;drill down&quot; through the thousands of Amazon Categories to find the results that meet your criteria. I could go on and on (there really are thousands of categories) but I think this small sample will illustrate how different your results can be for a single search term

</description>
<dc:date>2009-09-11T09:16:49Z</dc:date>
<dc:author>access2</dc:author>
<dc:subject>constrained search, search, Searching, categories, amazon categories, amazon</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.squidoo.com/amazon"><img border="0" src="http://blogmarks.net/screenshots/2009/09/11/a55a93466f0eaaedf51903b085998b5c.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.squidoo.com/amazon">Amazon - Constrained Search vs. Random Results</a></h4>
 
by <a href="http://blogmarks.net/user/access2">access2</a> 
<p class="description">The way to find needles in the immense haystack of Amazon.com is through constrained search.

Amazon's search function, like most others, claims to use a logical AND operator on keywords. That is search results for "Amazon Warriors," for example, should contain both "Amazon" AND "Warriors."

In fact, you will find that, all things being equal -- "Amazon" AND "Warriors" results will appear higher than "Amazon" OR "Warriors" results.

You need to "drill down" through the thousands of Amazon Categories to find the results that meet your criteria. I could go on and on (there really are thousands of categories) but I think this small sample will illustrate how different your results can be for a single search term

</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/constrained%2Bsearch">constrained search</a>
<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/Searching">Searching</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/categories">categories</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/amazon%2Bcategories">amazon categories</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/amazon">amazon</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058499750">Copy</a> | 
<a href="http://blogmarks.net/link/3339728">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/access2/mark/1058499736">
<title>Build External Links with Social Bookmarks</title>
<link>http://www.squidoo.com/social-bookmarks</link>
<description>Inbound links -- links from other sites to your page -- are far more important in determining your PageRank and placement in search engine results pages (or SERPs) than keyword density or other artificial means of estimating &quot;quality.&quot;  That is why social media such as online bookmarking sites have become so critical to successful website operation.</description>
<dc:date>2009-09-11T09:03:55Z</dc:date>
<dc:author>access2</dc:author>
<dc:subject>social media, bookmarks, seo, web promotion, advertising, external links, social bookmarks</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.squidoo.com/social-bookmarks"><img border="0" src="http://blogmarks.net/screenshots/2009/09/11/611e3e0093462bf1baf8b3088bbe90dd.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.squidoo.com/social-bookmarks">Build External Links with Social Bookmarks</a></h4>
 
by <a href="http://blogmarks.net/user/access2">access2</a> 
<p class="description">Inbound links -- links from other sites to your page -- are far more important in determining your PageRank and placement in search engine results pages (or SERPs) than keyword density or other artificial means of estimating "quality."  That is why social media such as online bookmarking sites have become so critical to successful website operation.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/social%2Bmedia">social media</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bookmarks">bookmarks</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/seo">seo</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web%2Bpromotion">web promotion</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/advertising">advertising</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/external%2Blinks">external links</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/social%2Bbookmarks">social bookmarks</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058499736">Copy</a> | 
<a href="http://blogmarks.net/link/3339715">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058499469">
<title>browsertests - Project Hosting on Google Code</title>
<link>http://code.google.com/p/browsertests/</link>
<description>&lt;blockquote&gt;&lt;p&gt;This project is about running test cases automatically on several versions of the main Web browsers available today. See the StartPage for more information. Tests and results are visible on http://www.browsertests.org.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-09-11T03:11:49Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>browser, testing, testsuite</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://code.google.com/p/browsertests/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/11/fd918bfc72e2402ee7bca2b2bd774d6a.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://code.google.com/p/browsertests/">browsertests - Project Hosting on Google Code</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>This project is about running test cases automatically on several versions of the main Web browsers available today. See the StartPage for more information. Tests and results are visible on http://www.browsertests.org.</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/testing">testing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/testsuite">testsuite</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058499469">Copy</a> | 
<a href="http://blogmarks.net/link/3339489">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Neewok/mark/1058497837">
<title>Dada Visualization I sur Flickr : partage de photos !</title>
<link>http://www.flickr.com/photos/quasimondo/3892920130/in/set-72157619795179936/</link>
<description>&lt;blockquote&gt;&lt;p&gt;One of the 8 works I created for the Data Art Show at the Pink Hobo Gallery in Minneapolis.&lt;/p&gt;

&lt;p&gt;All these pieces are a pun on the new craze for data visualization. The goals of data visualization as I understand them are to make complicated issues more understandable, to make obscured connections visible and to reveal hidden patterns in the data. After all these tasks have been solved ideally the result should be aesthetically pleasing as well.&lt;/p&gt;

&lt;p&gt;But when I look around what is being done in data visualization today I have the suspicion that in many cases the design is more important than the actual information and that the use of data is more an excuse to justify the use of aesthetics.&lt;/p&gt;

&lt;p&gt;Since I do not have a problem with aesthetics for their own sake in these pieces I deliberately took the opposite direction. Since I wanted to create something visually interesting I made up my own data which would give me the desired results. All these works are the result of generative algorithms, so all the elements and their connections are actually data and not something I assembled manually in Illustrator.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-09-09T11:20:30Z</dc:date>
<dc:author>Neewok</dc:author>
<dc:subject>art, visualization, data mining, ta, dada, data, da, tadada</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.flickr.com/photos/quasimondo/3892920130/in/set-72157619795179936/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/09/7ec52452589dc764c3fcbe9d25dd627e.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.flickr.com/photos/quasimondo/3892920130/in/set-72157619795179936/">Dada Visualization I sur Flickr : partage de photos !</a></h4>
 
by <a href="http://blogmarks.net/user/Neewok">Neewok</a> 
<div class="description"><blockquote><p>One of the 8 works I created for the Data Art Show at the Pink Hobo Gallery in Minneapolis.</p>

<p>All these pieces are a pun on the new craze for data visualization. The goals of data visualization as I understand them are to make complicated issues more understandable, to make obscured connections visible and to reveal hidden patterns in the data. After all these tasks have been solved ideally the result should be aesthetically pleasing as well.</p>

<p>But when I look around what is being done in data visualization today I have the suspicion that in many cases the design is more important than the actual information and that the use of data is more an excuse to justify the use of aesthetics.</p>

<p>Since I do not have a problem with aesthetics for their own sake in these pieces I deliberately took the opposite direction. Since I wanted to create something visually interesting I made up my own data which would give me the desired results. All these works are the result of generative algorithms, so all the elements and their connections are actually data and not something I assembled manually in Illustrator.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/art">art</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/visualization">visualization</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/data%2Bmining">data mining</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ta">ta</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dada">dada</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/data">data</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/da">da</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tadada">tadada</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058497837">Copy</a> | 
<a href="http://blogmarks.net/link/3338233">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>