<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: google-base</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/google-base.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2005-11-16T12:34:46+00:00</updated><author><name>Simon Willison</name></author><entry><title>Google Base is interesting</title><link href="https://simonwillison.net/2005/Nov/16/base/#atom-tag" rel="alternate"/><published>2005-11-16T12:34:46+00:00</published><updated>2005-11-16T12:34:46+00:00</updated><id>https://simonwillison.net/2005/Nov/16/base/#atom-tag</id><summary type="html">
    &lt;p id="p-0"&gt;I'm still trying to get my head around &lt;a href="http://base.google.com/"&gt;Google Base&lt;/a&gt;. Here's a brain-dump of my thinking so far. First, some links.&lt;/p&gt;

&lt;ul&gt;
 &lt;li&gt;&lt;a href="http://base.google.com/base/about.html"&gt;Google Base FAQ&lt;/a&gt;&lt;/li&gt;
 &lt;li&gt;&lt;a href="http://googleblog.blogspot.com/2005/11/first-base.html"&gt;Google Base introduction&lt;/a&gt; on the Google Blog (includes testimonials)&lt;/li&gt;
 &lt;li&gt;&lt;a href="http://www.plasticbag.org/archives/2005/11/in_which_google_base_launches.shtml"&gt;Tom's first impressions&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p id="p-1"&gt;Base is a very interesting product for a whole bunch of reasons. The data model is surprisingly simple on the surface: all items have a title, description, (optional) external URL, a "type" and a set of labels (a.k.a. tags) and "attributes". Attributes are something for tag enthusiasts to get excited by - they're name/value pairs that are kind of like tags in that you can apply them to anything, but more structured and with a greater level of implied meaning.&lt;/p&gt;

&lt;p id="p-2"&gt;Attributes instantly made me think of geotagging on &lt;a href="http://www.flickr.com/"&gt;Flickr&lt;/a&gt;, where tags are overloaded to store latitude and longitude values (example &lt;a href="http://www.flickr.com/photos/clagnut/60936865/"&gt;here&lt;/a&gt;). Having first class support for this kind of extensible data is a very powerful concept.&lt;/p&gt;

&lt;p id="p-3"&gt;Another interesting problem that the Google Base data model could be used to tackle is Wikipedia's &lt;a href="http://en.wikipedia.org/wiki/Wikipedia:Wikiproject"&gt;WikiProjects&lt;/a&gt;. If you look at any US Navy ship entry on Wikipedia (&lt;a href="http://en.wikipedia.org/wiki/USS_Iwo_Jima_%28LHD-7%29"&gt;example&lt;/a&gt;) you'll see a table on the right hand side of standard attributes relating to that ship - things like Length, Displacement, Armament and so on. This data isn't really structured - it's just a wiki table, manually maintained by participants of the &lt;a href="http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Ships"&gt;Ships WikiProject&lt;/a&gt;.&lt;/p&gt;

&lt;p id="p-4"&gt;Obviously this data would be more valuable if it was structured in a way that allowed queries to be made against it. Base-like attributes provide a way of doing this.&lt;/p&gt;

&lt;p id="p-5"&gt;There's definitely a trend towards this kind of loose data model at the moment. JotSpot allows all pages within a wiki to have as many extra name/value attribute pairs as you like (even the wiki body itself is internally implemented as a special attribute), and Ning works along similar lines.&lt;/p&gt;

&lt;p id="p-6"&gt;Base currently allows bulk importing of data using tab delimited files, RSS or Atom. There are no outward bound APIs which is a notable omission - I wouldn't be at all surprised to see them added in the next few weeks.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/google"&gt;google&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/google-base"&gt;google-base&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="google"/><category term="google-base"/></entry></feed>