<?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/data">
<title>Public marks with search data</title>
<description>Public marks with search data</description>
<link>http://blogmarks.net/marks/search/data</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/RETFU/mark/1058617364"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058617035"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058616463"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058615807"/>
<rdf:li resource="http://blogmarks.net/api/user/olafael/mark/1058613496"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058612995"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058609747"/>
<rdf:li resource="http://blogmarks.net/api/user/marco/mark/1058609472"/>
<rdf:li resource="http://blogmarks.net/api/user/marco/mark/1058609469"/>
<rdf:li resource="http://blogmarks.net/api/user/fotopol/mark/1058607358"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058605211"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058604772"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058601927"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058594201"/>
<rdf:li resource="http://blogmarks.net/api/user/parmentierf/mark/1058593703"/>
<rdf:li resource="http://blogmarks.net/api/user/ycc2106/mark/1058596128"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058593365"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058592075"/>
<rdf:li resource="http://blogmarks.net/api/user/marco/mark/1058592040"/>
<rdf:li resource="http://blogmarks.net/api/user/ycc2106/mark/1058596142"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058590583"/>
<rdf:li resource="http://blogmarks.net/api/user/vrossign/mark/1058590224"/>
<rdf:li resource="http://blogmarks.net/api/user/ycc2106/mark/1058596150"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058589148"/>
<rdf:li resource="http://blogmarks.net/api/user/parmentierf/mark/1058586329"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/RETFU/mark/1058617364">
<title>Axiis : Data Visualization Framework</title>
<link>http://www.axiis.org/index.html</link>
<description></description>
<dc:date>2009-12-11T09:22:15Z</dc:date>
<dc:author>RETFU</dc:author>
<dc:subject>statistique, as3</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.axiis.org/index.html"><img border="0" src="http://blogmarks.net/screenshots/2009/12/11/c515be046f2e6e0ac8deabc3c4f9f3ec.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.axiis.org/index.html">Axiis : Data Visualization Framework</a></h4>
 
by <a href="http://blogmarks.net/user/RETFU">RETFU</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3203155">1 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/statistique">statistique</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/as3">as3</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058617364">Copy</a> | 
<a href="http://blogmarks.net/link/3203155">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058617035">
<title>steve dekorte - projects - open source - vertexdb</title>
<link>http://www.dekorte.com/projects/opensource/vertexdb/</link>
<description>&lt;blockquote&gt;&lt;p&gt;VertexDB is a high performance graph database server that supports automatic garbage collection. It uses the HTTP protocol for requests and JSON for it's response data format and the API is inspired by the FUSE filesystem API plus a few extra methods for queries and queues. It's implementation is currently built on top of TokyoCabinet and libevent.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-12-11T04:11:59Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>http, api, database, tokyocabinet, json, graph</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.dekorte.com/projects/opensource/vertexdb/"><img border="0" src="http://blogmarks.net/screenshots/2009/12/11/ea60bddbf23f494d001fd1dee2bae636.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.dekorte.com/projects/opensource/vertexdb/">steve dekorte - projects - open source - vertexdb</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>VertexDB is a high performance graph database server that supports automatic garbage collection. It uses the HTTP protocol for requests and JSON for it's response data format and the API is inspired by the FUSE filesystem API plus a few extra methods for queries and queues. It's implementation is currently built on top of TokyoCabinet and libevent.</p></blockquote></div>
<p class="tags">
<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>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/database">database</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tokyocabinet">tokyocabinet</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/json">json</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/graph">graph</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058617035">Copy</a> | 
<a href="http://blogmarks.net/link/3436246">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058616463">
<title>Elevation › Ex Nihilo</title>
<link>http://exnihilo.mezzoblue.com/elevation/</link>
<description>&lt;blockquote&gt;&lt;p&gt;Elevation is a free, open source route visualizer that renders personal GPS data in 3D space, built in Processing by Dave Shea.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-12-10T12:00:46Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>data, gps, processing, 3d</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://exnihilo.mezzoblue.com/elevation/"><img border="0" src="http://blogmarks.net/screenshots/2009/12/10/cb013d0a89e5467880b3813b6d636ee3.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://exnihilo.mezzoblue.com/elevation/">Elevation › Ex Nihilo</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>Elevation is a free, open source route visualizer that renders personal GPS data in 3D space, built in Processing by Dave Shea.</p></blockquote></div>
<p class="tags">
<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/gps">gps</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/processing">processing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/3d">3d</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058616463">Copy</a> | 
<a href="http://blogmarks.net/link/3435784">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058615807">
<title>invisible commitment - a set on Flickr</title>
<link>http://www.flickr.com/photos/yesyesnono/sets/72157622825191782/</link>
<description>&lt;blockquote&gt;&lt;p&gt;This series of abstract data visualisation represents the source code structure and work progress of a software collection. The intention was to represent the sheer volume of work put into open source software development and usually by a smal number of people.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-12-09T23:05:48Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>datavisualization</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.flickr.com/photos/yesyesnono/sets/72157622825191782/"><img border="0" src="http://blogmarks.net/screenshots/2009/12/09/d6afdffa11b99c8dc1ea90d7e67cf324.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.flickr.com/photos/yesyesnono/sets/72157622825191782/">invisible commitment - a set on Flickr</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>This series of abstract data visualisation represents the source code structure and work progress of a software collection. The intention was to represent the sheer volume of work put into open source software development and usually by a smal number of people.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/datavisualization">datavisualization</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058615807">Copy</a> | 
<a href="http://blogmarks.net/link/3435237">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/olafael/mark/1058613496">
<title>Data Feed Explorer API Google Analytics</title>
<link>http://analyseweb.fr/api-google-analytics/data-feed-explorer-api-google-analytics/</link>
<description></description>
<dc:date>2009-12-07T14:32:31Z</dc:date>
<dc:author>olafael</dc:author>
<dc:subject>google, analytics</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://analyseweb.fr/api-google-analytics/data-feed-explorer-api-google-analytics/"><img border="0" src="http://blogmarks.net/screenshots/2009/12/07/b02c443441fe9622583b2d76c4181d96.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://analyseweb.fr/api-google-analytics/data-feed-explorer-api-google-analytics/">Data Feed Explorer API Google Analytics</a></h4>
 
by <a href="http://blogmarks.net/user/olafael">olafael</a> 
<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/analytics">analytics</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058613496">Copy</a> | 
<a href="http://blogmarks.net/link/3433282">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058612995">
<title>Zero Geography: Mapping the Geographies of Wikipedia Content</title>
<link>http://zerogeography.blogspot.com/2009/11/mapping-geographies-of-wikipedia.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;The following maps represent the first stage of a project I am embarking on to map out some of the spatial contours of Wikipedia. Data were obtained from the August 2009 Wikipedia geodata dump organised by user Kolossos. The information was then ported over to a GIS. There are almost half a million geotagged Wikipedia articles (i.e. Wikipedia articles about a place or an event that occurred in a distinct place), so the preparation time alone for the files needed to create these maps was almost a week.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-12-07T01:40:12Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>wikipedia, cartographie</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://zerogeography.blogspot.com/2009/11/mapping-geographies-of-wikipedia.html"><img border="0" src="http://blogmarks.net/screenshots/2009/12/07/22881ce66c13d3bebe9e377f14e9b4e3.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://zerogeography.blogspot.com/2009/11/mapping-geographies-of-wikipedia.html">Zero Geography: Mapping the Geographies of Wikipedia Content</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>The following maps represent the first stage of a project I am embarking on to map out some of the spatial contours of Wikipedia. Data were obtained from the August 2009 Wikipedia geodata dump organised by user Kolossos. The information was then ported over to a GIS. There are almost half a million geotagged Wikipedia articles (i.e. Wikipedia articles about a place or an event that occurred in a distinct place), so the preparation time alone for the files needed to create these maps was almost a week.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/wikipedia">wikipedia</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=1058612995">Copy</a> | 
<a href="http://blogmarks.net/link/3432848">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058609747">
<title>Natural Earth</title>
<link>http://www.naturalearthdata.com/</link>
<description>&lt;blockquote&gt;&lt;p&gt;Natural Earth is a public domain map dataset available at 1:10m, 1:50m, and 1:110m scales. Featuring tightly integrated vector and raster data, with Natural Earth you can make a variety of visually pleasing, well-crafted maps with cartography or GIS software.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-12-04T23:54:17Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>cartographie, opensource</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.naturalearthdata.com/"><img border="0" src="http://blogmarks.net/screenshots/2009/12/04/5d15683b6e5d73497f5474439dac52d8.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.naturalearthdata.com/">Natural Earth</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>Natural Earth is a public domain map dataset available at 1:10m, 1:50m, and 1:110m scales. Featuring tightly integrated vector and raster data, with Natural Earth you can make a variety of visually pleasing, well-crafted maps with cartography or GIS software.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cartographie">cartographie</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opensource">opensource</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058609747">Copy</a> | 
<a href="http://blogmarks.net/link/3429871">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/marco/mark/1058609472">
<title>Google Launch of DNS Service and OpenDNS Reply</title>
<link>http://www.circleid.com/posts/20091203_google_launch_of_dns_service_and_opendns_reply/</link>
<description>Access to end user DNS data is pure gold.</description>
<dc:date>2009-12-04T14:40:11Z</dc:date>
<dc:author>marco</dc:author>
<dc:subject>google, dns</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.circleid.com/posts/20091203_google_launch_of_dns_service_and_opendns_reply/"><img border="0" src="http://blogmarks.net/screenshots/2009/12/04/829e5865fda045d0521254665f9305fa.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.circleid.com/posts/20091203_google_launch_of_dns_service_and_opendns_reply/">Google Launch of DNS Service and OpenDNS Reply</a></h4>
 
by <a href="http://blogmarks.net/user/marco">marco</a> 
<p class="description">Access to end user DNS data is pure gold.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dns">dns</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058609472">Copy</a> | 
<a href="http://blogmarks.net/link/3429649">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/marco/mark/1058609469">
<title>Google's New Public DNS Service - and Data Retention Issues</title>
<link>http://www.circleid.com/posts/20091203_google_public_dns_service_and_data_retention_issues/</link>
<description>Their separate privacy policy for the Google Public DNS strikes me as utterly reasonable, particularly given its very rapid (24-48 hours) deletion of what I would consider to be the key privacy-sensitive data.</description>
<dc:date>2009-12-04T14:34:44Z</dc:date>
<dc:author>marco</dc:author>
<dc:subject>google, dns</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.circleid.com/posts/20091203_google_public_dns_service_and_data_retention_issues/"><img border="0" src="http://blogmarks.net/screenshots/2009/12/04/1d9750e089603b20f0396bc6894d8093.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.circleid.com/posts/20091203_google_public_dns_service_and_data_retention_issues/">Google's New Public DNS Service - and Data Retention Issues</a></h4>
 
by <a href="http://blogmarks.net/user/marco">marco</a> 
<p class="description">Their separate privacy policy for the Google Public DNS strikes me as utterly reasonable, particularly given its very rapid (24-48 hours) deletion of what I would consider to be the key privacy-sensitive data.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dns">dns</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058609469">Copy</a> | 
<a href="http://blogmarks.net/link/3429646">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/fotopol/mark/1058607358">
<title>Mineralogy Database - Mineral Collecting, Localities, Mineral Photos and Data</title>
<link>http://www.mindat.org/index.php</link>
<description>site en anglais consacré aux minéraux. Nombreuses photographies avec possibilités de recherches </description>
<dc:date>2009-12-02T18:56:57Z</dc:date>
<dc:author>fotopol</dc:author>
<dc:subject>photos, minéraux</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.mindat.org/index.php"><img border="0" src="http://blogmarks.net/screenshots/2009/12/02/d8fd3415bc236d0728421b16362d509b.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.mindat.org/index.php">Mineralogy Database - Mineral Collecting, Localities, Mineral Photos and Data</a></h4>
 
by <a href="http://blogmarks.net/user/fotopol">fotopol</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/993850">1 other(s)</a> 
<p class="description">site en anglais consacré aux minéraux. Nombreuses photographies avec possibilités de recherches </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/photos">photos</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/min%25C3%25A9raux">minéraux</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058607358">Copy</a> | 
<a href="http://blogmarks.net/link/993850">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058605211">
<title>GeoAPI Home</title>
<link>http://geoapi.com/</link>
<description>&lt;blockquote&gt;&lt;p&gt;GeoAPI services include a reverse geocoder; deep data about 16 million businesses and tens of thousands of points of interest; a writable layer for developers to annotate the world and do complex geo-queries; and location-enabled media layers (e.g., Twitter and Flickr). We've also recently added an iPhone SDK to speed up mobile development.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-11-30T11:08:34Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>mobile, api, geolocation</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://geoapi.com/"><img border="0" src="http://blogmarks.net/screenshots/2009/11/30/07f448929147590f89617c567f6a0805.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://geoapi.com/">GeoAPI Home</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3408992">1 other(s)</a> 
<div class="description"><blockquote><p>GeoAPI services include a reverse geocoder; deep data about 16 million businesses and tens of thousands of points of interest; a writable layer for developers to annotate the world and do complex geo-queries; and location-enabled media layers (e.g., Twitter and Flickr). We've also recently added an iPhone SDK to speed up mobile development.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mobile">mobile</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/api">api</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/geolocation">geolocation</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058605211">Copy</a> | 
<a href="http://blogmarks.net/link/3408992">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058604772">
<title>Pragmatic Programming Techniques: NOSQL Patterns</title>
<link>http://horicky.blogspot.com/2009/11/nosql-patterns.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;Over the last couple years, we see an emerging data storage mechanism for storing large scale of data. These storage solution differs quite significantly with the RDBMS model and is also known as the NOSQL. The aim of this blog is to extract the underlying technologies that these solutions have in common, and get a deeper understanding on the implication to your application's design.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-11-29T22:16:20Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>NoSQL, cassandra, bigtable</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://horicky.blogspot.com/2009/11/nosql-patterns.html"><img border="0" src="http://blogmarks.net/screenshots/2009/11/29/5c9ad1ffe22f9dc806cb99542b7253f2.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://horicky.blogspot.com/2009/11/nosql-patterns.html">Pragmatic Programming Techniques: NOSQL Patterns</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3414414">1 other(s)</a> 
<div class="description"><blockquote><p>Over the last couple years, we see an emerging data storage mechanism for storing large scale of data. These storage solution differs quite significantly with the RDBMS model and is also known as the NOSQL. The aim of this blog is to extract the underlying technologies that these solutions have in common, and get a deeper understanding on the implication to your application's design.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/NoSQL">NoSQL</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cassandra">cassandra</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bigtable">bigtable</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058604772">Copy</a> | 
<a href="http://blogmarks.net/link/3414414">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058601927">
<title>Mobile Opportunity: The mobile data apocalypse, and what it means to you</title>
<link>http://mobileopportunity.blogspot.com/2009/11/mobile-data-apocalypse-and-what-it.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;It's also possible to create some APIs that would tell a website how much bandwidth is available to it, so the developer could adjust its features accordingly. This idea is being tossed around between web companies and operators, but I don't know how much is actually being done about it.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-11-29T11:13:10Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>api, webarchitecture, mobile, webservices</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://mobileopportunity.blogspot.com/2009/11/mobile-data-apocalypse-and-what-it.html"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://mobileopportunity.blogspot.com/2009/11/mobile-data-apocalypse-and-what-it.html">Mobile Opportunity: The mobile data apocalypse, and what it means to you</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>It's also possible to create some APIs that would tell a website how much bandwidth is available to it, so the developer could adjust its features accordingly. This idea is being tossed around between web companies and operators, but I don't know how much is actually being done about it.</p></blockquote></div>
<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/webarchitecture">webarchitecture</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mobile">mobile</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webservices">webservices</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058601927">Copy</a> | 
<a href="http://blogmarks.net/link/3423131">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058594201">
<title>BBC News - Information goes out to play</title>
<link>http://news.bbc.co.uk/2/hi/uk_news/magazine/8381597.stm</link>
<description>&lt;blockquote&gt;&lt;p&gt;In this age of information overload, a new solution is emerging that could help us cope with the oceans of data surrounding and swamping us. It's called information visualisation.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-11-28T01:06:40Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>datavisualization</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://news.bbc.co.uk/2/hi/uk_news/magazine/8381597.stm"><img border="0" src="http://blogmarks.net/screenshots/2009/11/28/a223cf10bc07deaacae936b7dab3da95.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://news.bbc.co.uk/2/hi/uk_news/magazine/8381597.stm">BBC News - Information goes out to play</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>In this age of information overload, a new solution is emerging that could help us cope with the oceans of data surrounding and swamping us. It's called information visualisation.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/datavisualization">datavisualization</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058594201">Copy</a> | 
<a href="http://blogmarks.net/link/3417872">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/parmentierf/mark/1058593703">
<title>SHERPA/RoMEO Application Programmers' Interface</title>
<link>http://www.sherpa.ac.uk/romeo/api.html</link>
<description>The SHERPA/RoMEO Application Programmers' Interface (API) is a machine-to-machine interface that lets programmers access SHERPA/RoMEO data from their applications. For instance, you could use the API to incorporate an automatic look-up of a journal or publisher into your repository's deposition process.</description>
<dc:date>2009-11-27T08:40:09Z</dc:date>
<dc:author>parmentierf</dc:author>
<dc:subject>api, dev, open access, web, bibliographie</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.sherpa.ac.uk/romeo/api.html"><img border="0" src="http://blogmarks.net/screenshots/2009/11/27/c16987eff6125b0a26a81c3699cb2f26.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.sherpa.ac.uk/romeo/api.html">SHERPA/RoMEO Application Programmers' Interface</a></h4>
 
by <a href="http://blogmarks.net/user/parmentierf">parmentierf</a> 
<p class="description">The SHERPA/RoMEO Application Programmers' Interface (API) is a machine-to-machine interface that lets programmers access SHERPA/RoMEO data from their applications. For instance, you could use the API to incorporate an automatic look-up of a journal or publisher into your repository's deposition process.</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/open%2Baccess">open access</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/bibliographie">bibliographie</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058593703">Copy</a> | 
<a href="http://blogmarks.net/link/3417500">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ycc2106/mark/1058596128">
<title>Fiddler Web Debugger - A free web debugging tool</title>
<link>http://www.fiddler2.com/fiddler2</link>
<description>Fiddler is a Web Debugging Proxy which logs all HTTP(S) traffic between your computer and the Internet. Fiddler allows you to inspect all HTTP(S) traffic, set breakpoints, and &quot;fiddle&quot; with incoming or outgoing data. Fiddler includes a powerful event-based scripting subsystem, and can be extended using any .NET language.  Fiddler is freeware and can debug traffic from virtually any application, including Internet Explorer, Mozilla Firefox, Opera, and thousands more.</description>
<dc:date>2009-11-27T08:13:30Z</dc:date>
<dc:author>ycc2106</dc:author>
<dc:subject>debugger, proxy, software, mswindows, log, traffic</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.fiddler2.com/fiddler2"><img border="0" src="http://blogmarks.net/screenshots/2009/11/28/e025eb9924c02ffd9623e4f0c8f40140.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.fiddler2.com/fiddler2">Fiddler Web Debugger - A free web debugging tool</a></h4>
 
by <a href="http://blogmarks.net/user/ycc2106">ycc2106</a> 
<p class="description">Fiddler is a Web Debugging Proxy which logs all HTTP(S) traffic between your computer and the Internet. Fiddler allows you to inspect all HTTP(S) traffic, set breakpoints, and "fiddle" with incoming or outgoing data. Fiddler includes a powerful event-based scripting subsystem, and can be extended using any .NET language.  Fiddler is freeware and can debug traffic from virtually any application, including Internet Explorer, Mozilla Firefox, Opera, and thousands more.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/debugger">debugger</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/proxy">proxy</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/software">software</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mswindows">mswindows</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/log">log</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/traffic">traffic</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058596128">Copy</a> | 
<a href="http://blogmarks.net/link/3419704">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058593365">
<title>ry's http-parser at master - GitHub</title>
<link>http://github.com/ry/http-parser</link>
<description>&lt;blockquote&gt;&lt;p&gt;This is a parser for HTTP messages written in C. It parses both requests and responses. The parser is designed to be used in performance HTTP applications. It does not make any allocations, it does not buffer data, and it can be interrupted at anytime. It only requires about 128 bytes of data per message stream (in a web server that is per connection).&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-11-27T04:13:24Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>http, parser</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://github.com/ry/http-parser"><img border="0" src="http://blogmarks.net/screenshots/2009/11/27/1c42b51e7de1f1892d28240e17f4eee8.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://github.com/ry/http-parser">ry's http-parser at master - GitHub</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>This is a parser for HTTP messages written in C. It parses both requests and responses. The parser is designed to be used in performance HTTP applications. It does not make any allocations, it does not buffer data, and it can be interrupted at anytime. It only requires about 128 bytes of data per message stream (in a web server that is per connection).</p></blockquote></div>
<p class="tags">
<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/parser">parser</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058593365">Copy</a> | 
<a href="http://blogmarks.net/link/3417203">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058592075">
<title>9/11 Pager data</title>
<link>http://911.wikileaks.org/files/index.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;9/11 tragedy pager intercepts.&lt;/p&gt;&lt;p&gt;The following are national US pager intercepts that cover the September 11 tragedy from 3am on the same day (Tuesday) until 3am the following day.&lt;/p&gt;&lt;p&gt;Due to popular demand we provide a new block of pager data every 5 minutes, synchronized to the actual time of day the message was sent.&lt;/p&gt;&lt;p&gt;This way the world has a chance to objectively see how the tragedy progressed.&lt;/p&gt;&lt;p&gt;A full archive containing all the messages will be released on Thursday November 26 at the conclusion.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-11-25T17:04:04Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>911, sms, opacity</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://911.wikileaks.org/files/index.html"><img border="0" src="http://blogmarks.net/screenshots/2009/11/25/6efa3a502a36641c831080c1dfee9c8b.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://911.wikileaks.org/files/index.html">9/11 Pager data</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>9/11 tragedy pager intercepts.</p><p>The following are national US pager intercepts that cover the September 11 tragedy from 3am on the same day (Tuesday) until 3am the following day.</p><p>Due to popular demand we provide a new block of pager data every 5 minutes, synchronized to the actual time of day the message was sent.</p><p>This way the world has a chance to objectively see how the tragedy progressed.</p><p>A full archive containing all the messages will be released on Thursday November 26 at the conclusion.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/911">911</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sms">sms</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opacity">opacity</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058592075">Copy</a> | 
<a href="http://blogmarks.net/link/3416157">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/marco/mark/1058592040">
<title>Enabling gzip on apache to send compressed data</title>
<link>http://www.neeraj.name/blog/articles/874-enabling-gzip-on-apache-to-send-compressed-data</link>
<description></description>
<dc:date>2009-11-25T15:59:36Z</dc:date>
<dc:author>marco</dc:author>
<dc:subject>apache, apache2, gzip</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.neeraj.name/blog/articles/874-enabling-gzip-on-apache-to-send-compressed-data"><img border="0" src="http://blogmarks.net/screenshots/2009/11/25/f61caec33ab3eeada29d85573eb29c37.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.neeraj.name/blog/articles/874-enabling-gzip-on-apache-to-send-compressed-data">Enabling gzip on apache to send compressed data</a></h4>
 
by <a href="http://blogmarks.net/user/marco">marco</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/apache">apache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/apache2">apache2</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/gzip">gzip</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058592040">Copy</a> | 
<a href="http://blogmarks.net/link/3416131">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ycc2106/mark/1058596142">
<title>Compete | Compete</title>
<link>http://www.compete.com/</link>
<description>Site Profiles  Analyze traffic/engagement data Category Profiles  Benchmark vs. a Category Tag Profiles  Explore crowdsourced tagging Analytics Tools Search Analytics  Find keywords driving traffic Referral Analytics  Uncover sources of traffic Ranked Lists  Get lists of site rankings</description>
<dc:date>2009-11-24T21:09:50Z</dc:date>
<dc:author>ycc2106</dc:author>
<dc:subject>analytics, keywords, domain, compare</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.compete.com/"><img border="0" src="http://blogmarks.net/screenshots/2009/08/29/ed3727c206d77e2f0be4db71f25bbd29.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.compete.com/">Compete | Compete</a></h4>
 
by <a href="http://blogmarks.net/user/ycc2106">ycc2106</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1055519">5 other(s)</a> 
<p class="description">Site Profiles  Analyze traffic/engagement data Category Profiles  Benchmark vs. a Category Tag Profiles  Explore crowdsourced tagging Analytics Tools Search Analytics  Find keywords driving traffic Referral Analytics  Uncover sources of traffic Ranked Lists  Get lists of site rankings</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/analytics">analytics</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/keywords">keywords</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/domain">domain</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/compare">compare</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058596142">Copy</a> | 
<a href="http://blogmarks.net/link/1055519">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058590583">
<title>Humanising data: introducing “Chernoff Schools” for Ashdown – Blog – BERG</title>
<link>http://berglondon.com/blog/2009/11/23/chernoff-schools/</link>
<description>&lt;blockquote&gt;&lt;p&gt;For a little while I had been taking pictures of objects, furniture, buildings and other things in my environment where I recognised, however abstract, a face.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-11-24T04:49:19Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>photographie, reality</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://berglondon.com/blog/2009/11/23/chernoff-schools/"><img border="0" src="http://blogmarks.net/screenshots/2009/11/24/0eec3e1c28525fc6138d77a7fc3b5f3f.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://berglondon.com/blog/2009/11/23/chernoff-schools/">Humanising data: introducing “Chernoff Schools” for Ashdown – Blog – BERG</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>For a little while I had been taking pictures of objects, furniture, buildings and other things in my environment where I recognised, however abstract, a face.</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/reality">reality</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058590583">Copy</a> | 
<a href="http://blogmarks.net/link/3414946">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/vrossign/mark/1058590224">
<title>jQSlickWrap - Slick text wrapping for jQuery</title>
<link>http://jwf.us/projects/jQSlickWrap/#examples</link>
<description>To do this, it needs to have access to the individual pixels of the images it's operating on -- which is why for jQSlickWrap to work, you need to have a browser that supports HTML 5's new canvas element.
Here's an overview of the algorithm:

   1. If necessary, pre-load the image.
   2. Determine the CSS styles for the image (float and padding).
   3. Create a canvas element and set its dimensions to the size of the image plus its padding.
   4. Draw the image onto the canvas in the top-left location.
   5. Figure out the &quot;background&quot; color of the image by examining the pixel data at the top-left corner of the image.
   6. Fill the canvas with this background color.</description>
<dc:date>2009-11-23T16:15:50Z</dc:date>
<dc:author>vrossign</dc:author>
<dc:subject>css, images, html, colo, canvas, wrap</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://jwf.us/projects/jQSlickWrap/#examples"><img border="0" src="http://blogmarks.net/screenshots/2009/11/23/938c9f45accfede15cf7ec2bb4670242.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://jwf.us/projects/jQSlickWrap/#examples">jQSlickWrap - Slick text wrapping for jQuery</a></h4>
 
by <a href="http://blogmarks.net/user/vrossign">vrossign</a> 
<p class="description">To do this, it needs to have access to the individual pixels of the images it's operating on -- which is why for jQSlickWrap to work, you need to have a browser that supports HTML 5's new canvas element.
Here's an overview of the algorithm:

   1. If necessary, pre-load the image.
   2. Determine the CSS styles for the image (float and padding).
   3. Create a canvas element and set its dimensions to the size of the image plus its padding.
   4. Draw the image onto the canvas in the top-left location.
   5. Figure out the "background" color of the image by examining the pixel data at the top-left corner of the image.
   6. Fill the canvas with this background color.</p>
<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/images">images</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/colo">colo</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/canvas">canvas</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/wrap">wrap</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058590224">Copy</a> | 
<a href="http://blogmarks.net/link/3414665">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ycc2106/mark/1058596150">
<title>Big Huge Thesaurus: Synonyms, antonyms, and rhymes (oh my!)</title>
<link>http://words.bighugelabs.com/</link>
<description>Big Huge Thesaurus Synonyms, antonyms, and rhymes (oh my!) (Also blog post ideas and story plot/logline resources for writers.) This site is based on source data from the Princeton University WordNet database, the Carnegie Mellon Pronouncing Dictionary, and suggestions from thousands of people on the internet just like you.</description>
<dc:date>2009-11-22T21:00:15Z</dc:date>
<dc:author>ycc2106</dc:author>
<dc:subject>generator, story, synonym, rhyme, antonym, search, language, tools</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://words.bighugelabs.com/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://words.bighugelabs.com/">Big Huge Thesaurus: Synonyms, antonyms, and rhymes (oh my!)</a></h4>
 
by <a href="http://blogmarks.net/user/ycc2106">ycc2106</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2514522">1 other(s)</a> 
<p class="description">Big Huge Thesaurus Synonyms, antonyms, and rhymes (oh my!) (Also blog post ideas and story plot/logline resources for writers.) This site is based on source data from the Princeton University WordNet database, the Carnegie Mellon Pronouncing Dictionary, and suggestions from thousands of people on the internet just like you.</p>
<p class="tags">
<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/story">story</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/synonym">synonym</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/rhyme">rhyme</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/antonym">antonym</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/language">language</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=1058596150">Copy</a> | 
<a href="http://blogmarks.net/link/2514522">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058589148">
<title>map butcher » Finding Reality</title>
<link>http://mapbutcher.com/blog/?p=439</link>
<description>&lt;blockquote&gt;&lt;p&gt;Recently I’ve been doing some ‘gardening’.  You can see this clearly from these images on NearMap…. What’s really special about NearMap apart from the fact they are updating imagery more often than I am at home is that they have integrated OSM into their viewer and you can use their data to update OSM:&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-11-22T12:22:29Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>cartographie, opacité</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://mapbutcher.com/blog/?p=439"><img border="0" src="http://blogmarks.net/screenshots/2009/11/22/90978c8cd12279bedeb67e6497b6e1b2.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://mapbutcher.com/blog/?p=439">map butcher » Finding Reality</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>Recently I’ve been doing some ‘gardening’.  You can see this clearly from these images on NearMap…. What’s really special about NearMap apart from the fact they are updating imagery more often than I am at home is that they have integrated OSM into their viewer and you can use their data to update OSM:</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cartographie">cartographie</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=1058589148">Copy</a> | 
<a href="http://blogmarks.net/link/3413846">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/parmentierf/mark/1058586329">
<title>Handle System 5.3: Using a SQL Database for Storage</title>
<link>http://www.handle.net/hs_manual/server_manual_13.html</link>
<description>Using a SQL database as storage for as handle server allows greater control over data deposits as well as permitting complex data query. </description>
<dc:date>2009-11-19T08:58:28Z</dc:date>
<dc:author>parmentierf</dc:author>
<dc:subject>handle, sgbd, institutional repository</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.handle.net/hs_manual/server_manual_13.html"><img border="0" src="http://blogmarks.net/screenshots/2009/11/19/4d72974bab4ed84751eeaba2b41c6c35.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.handle.net/hs_manual/server_manual_13.html">Handle System 5.3: Using a SQL Database for Storage</a></h4>
 
by <a href="http://blogmarks.net/user/parmentierf">parmentierf</a> 
<p class="description">Using a SQL database as storage for as handle server allows greater control over data deposits as well as permitting complex data query. </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/handle">handle</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sgbd">sgbd</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=1058586329">Copy</a> | 
<a href="http://blogmarks.net/link/3411580">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>