• ... (Array) 30 elements
    • 0 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) links for 2007-06-14
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div> <ul> <li> <div><a href="http://www.sigmaphoto.com/lenses/lenses_all_details.asp?id=3301&amp;navigator=6"> Sigma 10-20mm Wide Angle Lens</a></div> <div>Wide angle lens, recently recommended.</div> <div>(tags: <a href="http://del.icio.us/sethladd/photography">photography</a>)</div> </li> </ul> </div> </div>
        • description (String) Sigma 10-20mm Wide Angle Lens Wide angle len...
          • Sigma 10-20mm Wide Angle Lens Wide angle lens, recently recommended. (tags: photography )
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://www.semergence.com/2007/06/13/links-for-...
              • http://www.semergence.com/2007/06/13/links-for-2007-06-14/
        • dc:date (Integer) 1181795305
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Seth Ladd
            • link (NULL)
            • email (NULL)
    • 1 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) A brief history of Consensus, 2PC and Transacti...
          • A brief history of Consensus, 2PC and Transaction Commit.
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div> <p><a href="http://betathoughts.blogspot.com/2007/06/brief-history-of-consensus-2pc-and.html"> A brief history of Consensus, 2PC and Transaction Commit</a>, in which Mark Mc Keown attempts to keep us all in sync with the history of consensus across processes in a distributed system.</p> <p>Excellent read. Thanks Mark!</p> </div> </div>
        • description (String) A brief history of Consensus, 2PC and Transacti...
          • A brief history of Consensus, 2PC and Transaction Commit , in which Mark Mc Keown attempts to keep us all in sync with the history of consensus across processes in a distributed system. Excellent read. Thanks Mark!
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://www.semergence.com/2007/06/13/a-brief-hi...
              • http://www.semergence.com/2007/06/13/a-brief-history-of-consensus-2pc-and-transaction-commit/
        • dc:date (Integer) 1181784938
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Seth Ladd
            • link (NULL)
            • email (NULL)
    • 2 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) developerWorks article on XHTML 2
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div>Why I like XHTML 2.</div> </div>
        • description (String) Why I like XHTML 2.
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://www.snee.com/bobdc.blog/2007/06/develope...
              • http://www.snee.com/bobdc.blog/2007/06/developerworks_article_on_xhtm.html
        • dc:date (Integer) 1181773464
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Bob DuCharme
            • link (NULL)
            • email (NULL)
    • 3 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) Going wide
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div>Decision made.</div> </div>
        • description (String) Decision made.
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://norman.walsh.name/2007/06/13/sigma
        • dc:date (Integer) 1181763539
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Norm Walsh
            • link (NULL)
            • email (NULL)
    • 4 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) Implementing XProc, VI
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div>Part the sixth, in which we consider options and parameters.</div> </div>
        • description (String) Part the sixth, in which we consider options an...
          • Part the sixth, in which we consider options and parameters.
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://norman.walsh.name/2007/06/13/implXProcVI
        • dc:date (Integer) 1181759713
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Norm Walsh
            • link (NULL)
            • email (NULL)
    • 5 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) XProc parameters
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div>Dealing with command line options and parameters turns out to be trickier than it looks.</div> </div>
        • description (String) Dealing with command line options and parameter...
          • Dealing with command line options and parameters turns out to be trickier than it looks.
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://norman.walsh.name/2007/06/13/xprocParame...
              • http://norman.walsh.name/2007/06/13/xprocParameters
        • dc:date (Integer) 1181757613
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Norm Walsh
            • link (NULL)
            • email (NULL)
    • 6 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) SIOC and other RDF from Apache Forrest in Googl...
          • SIOC and other RDF from Apache Forrest in Google SOC
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div> <p>Saw <a href="http://code.google.com/soc/asf/appinfo.html?csaid=5B17CB63EC1B0C7B"> this snippet</a> in a current project description from <a href="http://code.google.com/soc/asf/about.html">Apache for the Google Summer of Code</a>:</p> <blockquote> <p><strong>Creating plugins for embedding/producing RDF/XML and microformats in Forrest content objects</strong></p> <p><em>Student: Oshani Wasana Seneviratne<br /> Mentor: Gavin McDonald</em></p> <p>Community focused data representation schemas such as RDF and Microformats are gaining in popularity in many socially-oriented web sites. Such RDF schemas include FOAF (Friend Of A Friend), DOAP (Description Of A Project), DOAC (Description Of A Career), SIOC (Semantically Interlinked Online Communities), etc., and various Microformats include hAtom, hCalendar, hCard, adr, geo, hReview, hResume, rel-directory, rel-nofollow, rel-tag, xFolk, XFN, XOXO, etc.</p> <p>This project aims to create plugins in order to facilitate embedding of such formats in the Forrest content objects.</p> </blockquote> <p>Forrest is “a publishing framework that transforms input from various sources into a unified presentation in one or more output formats”… Looking forward to seeing this!</p> No Tags</div> </div>
        • description (String) Saw this snippet in a current project descripti...
          • Saw this snippet in a current project description from Apache for the Google Summer of Code : Creating plugins for embedding/producing RDF/XML and microformats in Forrest content objects Student: Oshani Wasana Seneviratne Mentor: Gavin McDonald Community focused data representation schemas such as RDF and Microformats are gaining in popularity in many socially-oriented web sites. Such RDF schemas include FOAF (Friend Of A Friend), DOAP (Description Of A Project), DOAC (Description Of A Career), SIOC (Semantically Interlinked Online Communities), etc., and various Microformats include hAtom, hCalendar, hCard, adr, geo, hReview, hResume, rel-directory, rel-nofollow, rel-tag, xFolk, XFN, XOXO, etc. This project aims ...
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://www.johnbreslin.com/blog/2007/06/13/sioc...
              • http://www.johnbreslin.com/blog/2007/06/13/sioc-and-other-rdf-from-apache-forrest-in-google-soc/
        • dc:date (Integer) 1181734330
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) John Breslin
            • link (NULL)
            • email (NULL)
    • 7 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) links for 2007-06-13
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div> <ul> <li> <div><a href="http://blog.lostlake.org/index.php?/archives/46-Some-more-Rails-to-lift-code-examples.html"> Some more Rails to lift code examples</a></div> <div>Converting a Rails application to a Scala on lift application.</div> <div>(tags: <a href="http://del.icio.us/sethladd/scala">scala</a> <a href="http://del.icio.us/sethladd/rubyonrails">rubyonrails</a>)</div> </li> <li> <div><a href="http://video.google.com/videoplay?docid=6204903272262158881">Super Mario Bros: Frustration</a></div> <div>A hilarious soundtrack to the hardest levels of Super Mario Brothers. Warning, not for virgin ears.</div> <div>(tags: <a href="http://del.icio.us/sethladd/humor">humor</a> <a href="http://del.icio.us/sethladd/video">video</a>)</div> </li> </ul> </div> </div>
        • description (String) Some more Rails to lift code examples Conver...
          • Some more Rails to lift code examples Converting a Rails application to a Scala on lift application. (tags: scala rubyonrails ) Super Mario Bros: Frustration A hilarious soundtrack to the hardest levels of Super Mario Brothers. Warning, not for virgin ears. (tags: humor video )
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://www.semergence.com/2007/06/12/links-for-...
              • http://www.semergence.com/2007/06/12/links-for-2007-06-13/
        • dc:date (Integer) 1181708766
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Seth Ladd
            • link (NULL)
            • email (NULL)
    • 8 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) Google's Song and Dance
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div> <p>Google <a href="http://googleblog.blogspot.com/2007/06/how-long-should-google-remember.html"> responded</a> to the European Union's privacy concerns with a response that includes a decision to begin to 'anonymize' search results at 18 months. Rather than allay concerns, the company's response only raises more questions.</p> <p>Let's leave aside, for a moment, <a href="http://searchengineland.com/070612-041042.php">what other companies do and do not do</a>. Whatever ends up happening with Google in regards to data storage will probably greatly impact on other companies. Google, in this case, becomes the bellwether when it comes to storing 'incidental data' such as searches, ad clicks, map uses, emails, and so on.</p> <p>Google's reasoning for storing data, and the fact that it is vague responding to questions about use of cookies, how long personal information is kept once original data is deleted, and whether and how profiling is happening–not to mention what kind of data is stored relating to Reader, Analytics, and so on, don't really address the concerns about privacy.</p> <p>For instance, Google uses its spell checker as one example of the 'further' research necessary for storing data for such longer periods of time. This makes no sense, though, because if a person uses one spelling at one time, chances are they'll use alternative spellings within a short time afterwards because the original spelling won't return what they need. Do people really do multiple searches using different spellings 18 months apart?</p> <p>In regards to the efficiency of the search, yes, clicking on the first item would show the search worked. But does a person make a search, keep the results up on their screen for 18 months, and then click through?</p> <p>I was also surprised that preparations for a DoS (Denial of Service) occurs through search engine results for months before an attack. Leads to another question: does this happen a lot? And what do the search result patterns show? A lot of people looking up "How do I create a Denial of Service Attack" or "DoS for Dummies"? I'm neither a search engine wiz, or a security expert. I guess this is all beyond my abilities and understandings.</p> <p>In regards to detecting click fraud, again, I would assume something like this would be apparent at some point, and storing information related to such an event makes sense — but what about the world of data completely outside such patterns?</p> <p>As for having to maintain this data for 18 months because of 'government' regulations: which ones? Google keeps mentioning these, but the ones the company references in Europe have to do ISPs, not search engines. The US laws mentioned in the response are focused on financial transactions, and the data storage needs here have to do with storing data until invoices are paid–exactly how long does it take Google to pay people?</p> <p>That the Justice Department and others in the US talk about storing data for years is just that: talk. Until and unless laws are enacted, we have to remember that the current Justice Department in this country is still acting under the shotgun reactions of a paranoid idiot who isn't smart enough to be hired to clean Google's floors. Times are changing: we won't always live in this constant state of generated fear.</p> <p>What was fascinating was Google's claim that it can only support one global privacy standard. Does that mean that if Tuvalu passes a law that search engine companies must retain raw search results and other personal data for two years (or five or ten), Google is then going to use this to establish its privacy requirements for, say, the US, Japan, Europe, and all points from there?</p> <p>"Well, there we go. It's out of our hands now. Time to build another dam for another data center. Say, the Mississippi looks like it would really drive some turbine–what do you people in Missouri feel about being known as 'Lake Google'?</p> <p>Search results, cookies, unknown data collection patterns, amount of profiling, types of profiling, persisting data even when accounts are deleted–instead of accusing people of 'wearing tin hats' for asking legitimate questions about data retention, it's time for Google to put away its PR and its team of lawyers and have a honest discussion with the people who helped it become the multi-billion dollar success it is. This is not asking the company to give away corporate secrets and unveil it's deepest, darkest algorithms. This is asking for specifics, when all we have been given in the past is vague generalities. Better yet, this is asking to let us have <a href="http://informationatrix.wordpress.com/2007/06/12/google-responds-to-privacy-nay-sayerssort-of/"> some say in all of this</a>.</p> <p>These questions and concerns raised this week are not going away. They are going to persist. Probably about as long as the data Google stores.</p> </div> </div>
        • description (String) Google responded to the European Union's privac...
          • Google responded to the European Union's privacy concerns with a response that includes a decision to begin to 'anonymize' search results at 18 months. Rather than allay concerns, the company's response only raises more questions. Let's leave aside, for a moment, what other companies do and do not do . Whatever ends up happening with Google in regards to data storage will probably greatly impact on other companies. Google, in this case, becomes the bellwether when it comes to storing 'incidental data' such as searches, ad clicks, map uses, emails, and so on. Google's reasoning for storing data, and the ...
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://burningbird.net/technology/googles-song-...
              • http://burningbird.net/technology/googles-song-and-dance/
        • dc:date (Integer) 1181688420
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Shelley Powers
            • link (NULL)
            • email (NULL)
    • 9 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) The Aftermath of (Almost) Everything
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div> <p>Just a quick update post <a href="http://www.eswc2007.org/">ESWC</a> (SPARQL <a href="http://platon.escet.urjc.es/~axel/sparqltutorial/">tutorial</a>), <a href="http://webont.org/owled/2007/">OWLED</a> (organizing and…everything), and <a href="http://www.inf.unibz.it/krdb/events/dl-2007/">DL</a> (nothing but hanging out; I did jump, fully clothed, into a pool; I expect photos will show up at some point): Lot’s of good and important stuff happened.</p> <p>One of the most interesting things at OWLED was that Sandro Hawke annouced that the W3C team has started work on a charter for a potential W3C working group to extend OWL along the lines of OWL 1.1. While this is not a done deal, by any means, it is an important step. Thanks to everyone who helped including all the wonderful moral support we’ve received. There are still devils and details, as always, but I’m very happy with how things are going.</p> <p>More to come as I unpack.</p> </div> </div>
        • description (String) Just a quick update post ESWC (SPARQL tutorial ...
          • Just a quick update post ESWC (SPARQL tutorial ), OWLED (organizing and…everything), and DL (nothing but hanging out; I did jump, fully clothed, into a pool; I expect photos will show up at some point): Lot’s of good and important stuff happened. One of the most interesting things at OWLED was that Sandro Hawke annouced that the W3C team has started work on a charter for a potential W3C working group to extend OWL along the lines of OWL 1.1. While this is not a done deal, by any means, it is an important step. Thanks to everyone who helped ...
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://clarkparsia.com/weblog/2007/06/12/the-af...
              • http://clarkparsia.com/weblog/2007/06/12/the-aftermath-of-almost-everything/
        • dc:date (Integer) 1181646703
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Clark and Parsia
            • link (NULL)
            • email (NULL)
    • 10 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) OASIS OpenDocument Metadata
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div> <p>Bruce D’Arcus <a href="http://lists.w3.org/Archives/Public/semantic-web/2007Jun/0094.html"> announced in semantic-web@w3.org</a> that the OASIS OpenDocument Metadata Subcommittee works on a <a href="http://www.oasis-open.org/committees/download.php/24327/ODF-Metadata-Proposal.pdf"> proposal for enhanced metadata support</a> in their file format:</p> <blockquote> <p>A quick summary is that we’ve adopted RDF as the model for metadata, which can be:</p> <ul> <li>embedded as RDF/XML in the file package to describe either the document, or embedded content</li> <li>used in an RDFa-like syntax to tag content as triples (where the content is the literal object)</li> <li>hooked up to a new generic field (text:meta-field)</li> </ul> </blockquote> <p>Note: For further discussions on this topic see also <a href="http://lists.oasis-open.org/archives/office/">http://lists.oasis-open.org/archives/office/</a>.</p> </div> </div>
        • description (String) Bruce D’Arcus announced in semantic-web@w3....
          • Bruce D’Arcus announced in semantic-web@w3.org that the OASIS OpenDocument Metadata Subcommittee works on a proposal for enhanced metadata support in their file format: A quick summary is that we’ve adopted RDF as the model for metadata, which can be: embedded as RDF/XML in the file package to describe either the document, or embedded content used in an RDFa-like syntax to tag content as triples (where the content is the literal object) hooked up to a new generic field (text:meta-field) Note: For further discussions on this topic see also http://lists.oasis-open.org/archives/office/ .
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://rdfa.info/2007/06/12/oasis-opendocument-...
              • http://rdfa.info/2007/06/12/oasis-opendocument-metadata/
        • dc:date (Integer) 1181632954
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) RDFa
            • link (NULL)
            • email (NULL)
    • 11 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) Semantic Web Strategies speaker submission form...
          • Semantic Web Strategies speaker submission form back up
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div>Ready for your ideas.</div> </div>
        • description (String) Ready for your ideas.
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://www.snee.com/bobdc.blog/2007/06/semantic...
              • http://www.snee.com/bobdc.blog/2007/06/semantic_web_strategies_speake.html
        • dc:date (Integer) 1181621994
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Bob DuCharme
            • link (NULL)
            • email (NULL)
    • 12 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) iPhone and the Semantic Web
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div> <p>I downloaded Safari, and it works quite nicely on Windows. What an interesting development in the broadest sense of the term.</p> <p>I also followed <a href="http://news.com.com/2100-1016_3-6190159.html">some of the discussion about Ajax development for the iPhone</a>, which again is of interest to an Ajax developer. One problem, though: the iphone costs 500.00 for the low end phone, 600.00 for the higher end.</p> <p>I have a cellphone, I have an iPod. I like new toys as much as the next person, but even if I could afford it, I'd have a hard time shelling out that kind of money for a device which really isn't best of breed for both. Other than the bigger video screen.</p> <p>It would be appropriate to cover in my next book, though, since its focus is on web graphics. Perhaps I can get O'Reilly to shell out for an iPhone I can 'borrow'.</p> <p>I wonder, it supports the web, but can it support a semantic web? Will it have a tiny little RDF engine? Can it do OWL? How much knowledge can fit into 3GB and change?</p> <p>If we can squeeze RDF onto the device in addition to a bitty browser and Ajax, I have dibs on the term <em>iKnow</em>.</p> </div> </div>
        • description (String) I downloaded Safari, and it works quite nicely ...
          • I downloaded Safari, and it works quite nicely on Windows. What an interesting development in the broadest sense of the term. I also followed some of the discussion about Ajax development for the iPhone , which again is of interest to an Ajax developer. One problem, though: the iphone costs 500.00 for the low end phone, 600.00 for the higher end. I have a cellphone, I have an iPod. I like new toys as much as the next person, but even if I could afford it, I'd have a hard time shelling out that kind of money for a device ...
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://burningbird.net/technology/iphone-and-th...
              • http://burningbird.net/technology/iphone-and-the-semantic-web-iknow/
        • dc:date (Integer) 1181610317
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Shelley Powers
            • link (NULL)
            • email (NULL)
    • 13 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) Max Headroom and Joost
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div> <p>Kent Newsome recently <a href="http://www.newsome.org/2007/06/don-you-mean-television-vs-youtube.shtml"> wrote on Joost</a> and doesn't think much of the premise. His story reminded me that I haven't done an update on the service for a time.</p> <p>The company just issued another beta release of the software, and it is getting very stable, at least on Windows XP SP2. I've been looking for new content through the online channel guide. However, it was only when <a href="http://www.onthetoob.com/">this site</a> and its channel and new content feeds was pointed out to me was I able to discover the new Warner Brother's Sci-Fi channel, with two Max Headroom shows, three Time Trax, the Aqua Man pilot, and several shows from the first season of Babylon Five. More new shows are added daily to multiple channels, including several very old and very classic cartoons — featuring Betty Boop and Felix the Cat, as well as classic Looney Tunes.</p> <p>Upside is that the picture is getting quite good and when I sit in my TV watching chair and send the signal from computer to my LCD TV, I get a really nice picture and little hesitation or breakup for most of the shows. Its a nice alternative if you don't want to pay for cable or satellite, but still want to have access to video content outside of your own movies.</p> <p>Downside is that more Max Headroom shows are needed. Oh, and Joost is the most uncommunicative company I have ever seen that's dependent on the beta process and word of mouth. Company personnel never participate in the forum, update the company weblog, or respond to bug submissions. Surprising considering the number of RDF community members associated with the application and company. This is probably the shape of things to come: don't expect interaction to be with anyone other than other service users.</p> <p>I'll have to look for a privacy statement to see if the site stores information about what shows I watch, and whether I'd be embarrassed if my viewing habits became public fodder. However, I'm a weblogger, little embarrasses me.</p> <p>Again, if you want an invite, drop me a comment with your name and email address (emails are not published).</p> </div> </div>
        • description (String) Kent Newsome recently wrote on Joost and doesn'...
          • Kent Newsome recently wrote on Joost and doesn't think much of the premise. His story reminded me that I haven't done an update on the service for a time. The company just issued another beta release of the software, and it is getting very stable, at least on Windows XP SP2. I've been looking for new content through the online channel guide. However, it was only when this site and its channel and new content feeds was pointed out to me was I able to discover the new Warner Brother's Sci-Fi channel, with two Max Headroom shows, three Time Trax, ...
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://burningbird.net/technology/max-headroom-...
              • http://burningbird.net/technology/max-headroom-and-joost/
        • dc:date (Integer) 1181586826
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Shelley Powers
            • link (NULL)
            • email (NULL)
    • 14 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) On Privacy Redux
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div> <p>Matt Cutts of Google <a href="http://www.mattcutts.com/blog/privacy-international-loses-all-credibility/"> responded, informally</a> to the Privacy International report, citing the privacy lapses of AOL and other companies. I'm not going to address these, particularly since <a href="http://blog.insiderchatter.com/2007/06/11/google-is-wrong-on-consumer-privacy/"> Donna Bogatin</a> has done this, so well.</p> <p>Some of Matt's readers assumed PI was motivated by some form of corruption or corporate bias, or that the report was an attempt to garner attention. I doubt the corruption, but it's true that watch dog groups operate almost purely on the attention they can generate about an issue.</p> <p>Regardless of motivation, none of this discounts what the report says, or how people are reacting to it. That's what should be the focus of our discussion now, and that's what the folks of Google should be paying attention to. I wrote the following in comments at Matt's post:</p> <blockquote> <p>Try this on for size:</p> <p>Start from the premise that perhaps this organization’s concerns are a legitimate reflection of how people are going to perceive Google in the years to come. And then think about how this could be a way of ‘kicking’ Google out of its complacent dependence on the goodness of its search for the ultimate algorithms, by reminding those in charge that the internet is more than a set of calculations.</p> <p>This is an opportunity for Google. Unless you see it this way, get used to having your spleen agitated on a regular basis.</p> </blockquote> <p>What's not needed is more PR for Google, or some form of privacy czar. The former will just recommend more paint for the cracked walls; the latter will get caught up in the mechanics of what is Google–which is an organization centering around the push for perfect searches, perfection being determined in a scholarly vacuum.</p> <p>I've never been particularly concerned about Google releasing data outside of the company, or to the government. Well, at least not the US. It's not in the company's interest, from a corporate stand point, or from the personal views of the workers.</p> <p>What I've long been concerned about is what Google does with this data internally. You see, I have a difficult time trying to figure out why having IP addresses associated with specific searches is such an important component of the algorithms for these searches. After all, one doesn't need to know the exact IP address to see which items are clicked through to from searches. One assumes that when creating a generalized search, click through rates would be sufficient.</p> <p>But no, the company specifically stores IP addresses with these searches. I'm not a search engine wiz, but one can assume the company is checking for patterns across a universe of searches. This gives it the ability to take search to the next levels of complexity–and the more information about how individuals approach search as a whole, the better it can fine tune algorithms. In fact, it would be nice if we would search under our names so it wouldn't have to muck around with IP addresses that can change. It will even provide us a history of such searches.</p> <p>However, attempts along this line have not met with universal acceptance, which must be a source of frustration to the company. Why? Because the company really isn't 'evil', and doesn't have 'evil' intentions with its data. If it did, our lives would be so much simpler.</p> <p>I assume the company is storing the IP address with the searches in order to generate a more semantically meaningful search result–exploring search as it relates to other searches; to perhaps even have the engine 'learn' from previous search efforts and adjust results accordingly. Not necessarily a bad thing to do, though people behave based on their unique environment, built of life experiences, that tends to blur the ability to derive any universally useful heuristic from captured patterns.</p> <p>However, add this with the other data that Google can capture–either about a person, specifically, or about a given IP address at a time:</p> <ul> <li>Payments through Google Checkout, which provides valuable information about our buying patterns</li> <li>What weblogs we subscribe to, <em>and</em>, which items in those weblogs a person actually clicks through to. We can assume that 'click through' denotes a heightened level of interest</li> <li>Information stored or maintained through Google applications, such as documents, spreadsheets, software, email, or our calendars–that's a pool of potentially very personal, and therefore richly enticing, data in those applications</li> <li>Where we live, where we're going, how we're getting there, and with calendaring, why we're going</li> <li>What I read. What I read anywhere on the web.</li> <li>What I write. Also anywhere on the web.</li> <li>What groups I participate in, what usenet groups did I participate on in the past</li> <li>What videos do I watch, what images do I work on, which ones do I view</li> <li>Who are my friends? What clubs do I belong to? What political party am I member of?</li> <li>What are my financial investments? What companies am I most interested in right now?</li> </ul> <p>I culled this list from the Google applications I know of, all reflecting the type of data that Google can, and most likely is, collecting about us. That's a lot of data. Why is it collecting such? For better searches? Not likely. In order to personalize the web? There could be something to this, and this is one area where our interpretations of Google's activities can differ, widely, between us.</p> <p>Many people seem to feel 'flattered' or even grateful when software remembers about us. I'm not sure why–perhaps it has something to do with feeling alienated from this large world, or from those around us. Perhaps we're just lazy and anything that promises us simpler access to data is viewed as 'good'.</p> <p>Google also projects this warm feeling of intimacy by the simplicity of the company's interfaces to many of the tools. They are not especially polished or sophisticated. They strike one as being efficient, simple, clean, and straight forward. There's never even a hint, at any time that Google is a multi-billion dollar corporation that's becoming one of the most major influences in both our culture and our lives. A company whose shareholders recently voted to continue doing business with China rather than take a stand against that country's repressive policies.</p> <p>Yet Google gave us satellite views in our maps, and tools and toys we can use as much as we want without once charging us a penny. It gave us Developer Days, and GWT, and Maps; supports open source, and hires some of our favorite people. It is a teddy bear. A really big, really smart teddy bear.</p> <p>Looking beyond the fur, though, we have to remember that Google is a company that can be both ruthless, and single minded in its determination of the course its charted for itself. For all that we may like those members of Google who we know–through weblogs, conferences, or other associations–they are only part of a much bigger whole. Their individual beliefs and personal morals can only influence the company as much as that inner, powerful sanctum that is the heart of Google allows. And the inner heart of Google is one based on a corporate belief in the ultimate righteousness of its algorithms. A belief that over time, as these algorithms are allowed to increase in sophistication, they will filter out bias, bigotry, and ignorance. The company believes passionately in its research–so much so that it can't even comprehend why we're so worried about privacy. What was it <a href="http://www.mattcutts.com/blog/privacy-international-loses-all-credibility/#comment-106282"> one person wrote in Matt's comments</a>? <em>People that aren’t us won’t get it.</em>.</p> <p>Many at Google would most likely agree with me when I say the following: there is a purity of purpose behind such efforts at Google. I have no doubt that Google's efforts really are focused on finding the best results. I also have no doubt that Google sees such as being of benefit to the community. I might even agree with the necessity. Agree until…</p> <p>Until the results of such are used to monetize who we are, and what we do on the web. To know exactly what ads we'd be most vulnerable to at any point in time. To mark who is potentially dangerous, and who is not. To determine what it thinks we really want to see when we come looking for information. Perhaps even to determine who is not worthy of being seen.</p> <p><em>Tell me what job should I take, Google.</em> Anyone remember that?</p> <p>Information is power. I once wrote that Google is one of the most dangerous companies I know and was discounted for making a grandiose claim. Yet there is probably no entity in the world that knows more about us, that has more information on us, then Google. Not even the IRS knows that I like Firefly or that I vote Democrat. The state or a potential employer doesn't know that I'm searching for low cholesterol recipes. The Department of Homeland security isn't aware that I daydream about traveling, and plan secret little vacations that I can't afford. No government on the world is party to my fears, hopes, dreams, and worries as much as the search engines I use.</p> <p>Some would say, correctly, that there is a simple solution: don't use Google products. True, I do switch search engines on a daily basis. But search engines are only the tip. What happens when Google starts tracking through ads? Through page readers? Through Google Analytics and Reader and Books and what all? Through the hundred other little areas that we look at with such fond indulgence because they, you know, <em>have cool APIs</em>?</p> <p>Keeping our data in raw form for up to two years? Why so long? The reasons given make no sense. They never did. How much data is gathered, and will be gathered with new acquisitions, is also unknown. Google has bought a lot of companies, and is associated with still others. We really don't have an idea, at all, how much information is being tracked to us through cookies and IP addresses. We also don't know who in the company has access to it, and how much the data is directly connected to individuals.</p> <p>Google wants to know all about us, but isn't willing to let us know enough about it so that we can make rational assessments of our privacy risks. When, in ignorance of such information, we write based on conjecture, it pooh poohs our fears, and discounts our worries and repeats that it is 'better than other companies'–equivalent to we in the US saying our form of torture isn't as bad as that practiced in other countries, and at least our methods don't leave scars.</p> <p>Most worrisome of all gaps in our knowledge of Google operations is what profiles are generated from the data that Google collects, and exactly how long will such derived information be stored? What was it the folks at Google said once? It wants to eventually store the web? If so, then space is not a concern. I imagine much of me can be compressed into a space less than a Gig in size.</p> <p>Regardless of your opinion of the Privacy International report, isn't it about time Google realized that not everyone shares the same faith in the company's<em>purity of purpose</em>; nor the same belief in the inherent neutrality and fairness of algorithms? Two years. What was I searching for two years ago–I can't remember now, but Google can. Two years. That's longer than my first marriage. Come to think of it, Google probably knows as much about me, or more, than my first husband. Considering my first husband, though, this isn't surprising and one of the many reasons I divorced him.</p> <p>Unfortunately, I don't have the option to divorce Google.</p> </div> </div>
        • description (String) Matt Cutts of Google responded, informally to t...
          • Matt Cutts of Google responded, informally to the Privacy International report, citing the privacy lapses of AOL and other companies. I'm not going to address these, particularly since Donna Bogatin has done this, so well. Some of Matt's readers assumed PI was motivated by some form of corruption or corporate bias, or that the report was an attempt to garner attention. I doubt the corruption, but it's true that watch dog groups operate almost purely on the attention they can generate about an issue. Regardless of motivation, none of this discounts what the report says, or how people are reacting ...
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://burningbird.net/technology/on-privacy-re...
              • http://burningbird.net/technology/on-privacy-redux/
        • dc:date (Integer) 1181580117
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Shelley Powers
            • link (NULL)
            • email (NULL)
    • 15 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) Fun with SIMILE Exhibit
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div><a href="http://simile.mit.edu/exhibit/">SIMILE Exhibit</a> is a really interesting tool. The Simile folks have this to say: <blockquote> <p>Exhibit is a lightweight structured data publishing framework that lets you create web pages with support for sorting, filtering, and rich visualizations by writing only HTML and optionally some CSS and Javascript code.</p> </blockquote> <p>Doesn't that sound like the promises you've heard a thousand times before? Only this time, the tools are genuinely easy and powerful to use. I have a couple of gripes, about documentation (I'll get to these in a bit) but I <a title= "Publications page rendered using Simile Exhibit" href="http://www.hpl.hp.com/personal/Steve_Cayzer/publications2.htm">applied Exhibit to my publications page</a> and not only are the results pleasing, the whole process was fairly painless. And, there's nothing to download. Exhibit works by reading a data file (in JSON format, see later for how to generate), using an HTML template to format this, and calling out to a javascript file (hosted on the simile site) which is the Exhibit API.</p> <p>&nbsp;Here's some general thoughts. If you want a HOWTO -&nbsp; of sorts - keep reading.<br /></p> <ul> <li>&nbsp;Exhibit is a data driven display. The data is in fact RDF (or a restricted subset of RDF) which make it grpah structured, quite expressive, and extensible.</li> <li>The 'download' free nature, as well as ease of use, make it a powerful driver to wider spread adoption. But you still need access to your own website, some decent data, and HTML/CSS skills, so it's for power users.<br /></li> <li>There's quite a lot of UI thought here. For example, you can multiply select from 1 facet (papers written by Steve OR Paul) and click on the author of a paper to get a pop up of related reports (others papers written by Paul). Exhibit deliberately doesn't try fancy mechanisms for large amounts of data, either within facets (think tag clouds) or results (number of publications).</li> <li>The data model can be extended - for example, a free text value (brand="General Mills") can become a resources (brand="General Mills" and "General Mills" has HQ in Minnesota). The mechanism for doing this feels slightly fragile - linking by free text label. But it's an interesting approach (see fig 9 in <a title= "Simile Exhibit (paper)" href="http://people.csail.mit.edu/dfhuynh/research/papers/www2007-exhibit.pdf"> their paper</a> for more details).<br /></li> </ul> <p>I'm not really a hacker. I mean, I <i>can</i> program, but I don't relish the prospect of spending hours grovelling around in someone else's code to get something to work. But I do like experimenting, when I get the time. If this sounds like you, then you might want to try out Exhibit too. Here's how I did it, with some hints which you might find useful.</p> <ol> <li>I already have a publications file in Bibtex, so that bit was easy. Simile needs data in JSON format but <a href="http://simile.mit.edu/babel/">the Babel converter</a> will do this task for you.</li> <li>Doing the Babel conversion creates a template HTML file which you can download and tweak. My tweaked file can be found by doing 'view source' on my <a title= "Publications page rendered using Simile Exhibit" href="http://www.hpl.hp.com/personal/Steve_Cayzer/publications2.htm">Exhibit publications page.</a> It's not very big!</li> <li>I wanted to display the papers by descending year, but the exhibit default is ascending (It's probably lexical by the way but since I use 4 digit dates and intend to retired before 9999 I don't anticipate a problem...) The <a href="http://simile.mit.edu/wiki/Exhibit/For_Authors">Simile documentation</a> is not very exensive as yet - I'm sure this will improve as time goes on - but <a title="sortable views in Exhibit" href="http://simile.mit.edu/wiki/Exhibit/API/Sortable_Views">I found what I was looking for here</a>. You need to use the ex:directions tab as follows:</li> </ol> <pre> &lt;<span"start-tag">div</span><span"attribute-name"> ex:role</span>=<span"attribute-value">"exhibit-view" </span><span"attribute-value"> </span><span"attribute-name">ex:orders</span>=<span"attribute-value">".year" </span><span"attribute-name">ex:directions</span>=<span"attribute-value">"descending" </span><span"attribute-name">ex:possibleOrders</span>=<span"attribute-value">".pub-type, .author, .year, .label, .tags" </span><span"attribute-name">ex:possibleDirections</span>=<span"attribute-value">"ascending,descending"</span> </pre> <ol> <li>I also wanted to make use of the 'keywords' in the technical reports (that's the '.tags' bit at the end) - but I am not yet sure how to do this. For example, the authors are treated separately ("Steve Cayzer and Paul Shabajee" is parsed as 2 entities) and moreover each entity (of type Author) is available to do a search on. To take an example: <pre> <span> { "items" : [ { "url" : "http://www.hpl.hp.com/techreports/2007/HPL-2007-72.html", "pub-type" : "techreport", "uri" : "urn:d4cedad9e3e0d6dcc6147e0970e37cb5", "author" : [ "Michlmayr,-Elke", "Cayzer,-Steve", "Shabajee,-Paul" ], "label" : "Adaptive User Profiles for Enterprise Information Access", },</span> </pre> and <pre> <span> { "label" : "Michlmayr, Elke", "type" : "Author", }, </span> </pre> and <pre> <span> "types" : { "Author" : { "uri" : "http://simile.mit.edu/2006/11/bibtex#Author" }, }, "properties" : { "author" : { "label" : "author", "uri" : "http://simile.mit.edu/2006/11/bibtex#author", </span> </pre> Hopefully it's clear what's going on here. The JSON file can be tweaked to give this sort of behaviour, but of course such tweaks get lost next time a bibtex-&gt;JSON conversion gets done. Making the changes at the bibtex level is clearly better; but the appropriate changes do not suggest themselves. I shall keep experimenting. <p>There's a <a title="Simile Exhibit (paper)" href="http://people.csail.mit.edu/dfhuynh/research/papers/www2007-exhibit.pdf"> pretty good academic paper out</a>, which is well worth reading and, for me, filled in a couple of the gaps on the documentation.</p> </li> </ol> </div> </div>
        • description (String) SIMILE Exhibit is a really interesting tool. Th...
          • SIMILE Exhibit is a really interesting tool. The Simile folks have this to say: Exhibit is a lightweight structured data publishing framework that lets you create web pages with support for sorting, filtering, and rich visualizations by writing only HTML and optionally some CSS and Javascript code. Doesn't that sound like the promises you've heard a thousand times before? Only this time, the tools are genuinely easy and powerful to use. I have a couple of gripes, about documentation (I'll get to these in a bit) but I applied Exhibit to my publications page and not only are the results ...
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://www.semanticblogging.org/semblog/blog/de...
              • http://www.semanticblogging.org/semblog/blog/default/?permalink=D6D0E3701EE05BBB4085CB338D27D354.html
        • dc:date (Integer) 1181578515
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Steve Cayzer
            • link (NULL)
            • email (NULL)
    • 16 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) “Friendly talks”, a.k.a. I had some fun wit...
          • “Friendly talks”, a.k.a. I had some fun with SPARQL and Exhibit…
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div> <div> <p><a href="http://people.csail.mit.edu/dfhuynh/">David Huynh</a> sent me a mail on a cool feature he has just added to <a href="http://simile.mit.edu/exhibit/">Exhibit 2.0</a>: he’s put a shortcut to the <a href="http://simile.mit.edu/babel/">Babel</a> service. What this means is that one can refer to an RDF/XML, Excel, or a BibTex file instead of the JSON code, and Exhibit will convert it to RDF on the fly. So, to try it out, I put together a small example: the list of the <a href="http://www.ivan-herman.net/Misc/2007/friendlyTalks.html">W3C related talks</a> of my buddies, ie, people whose name appear in <a href="http://www.ivan-herman.net/foaf.rdf">my foaf file</a>. And the remarkable thing is that this needed around 20-25 minutes (including chasing some stupid misspelling in the SPARQL query:-). And here is how it works:</p> <p>First of all, the <a href="http://www.w3.org/Talks/">W3C Talks’ system</a> is based on RDF: all data are stored in (public) RDF files and the interface, the query, etc, is just a front-end to the data. (The links to the relevant RDF files can be found at the bottom of the <a href="http://www.w3.org/Talks/">Talks’ page</a>). I could therefore come up with a SPARQL query which looks more or less as follows (I omitted the namespace declarations from here):</p> <pre> CONSTRUCT { [] rdf:type talk:Talk; dc:date ?date; foaf:name ?name; talk:event ?event; vcard:Locality ?city; vcard:Country ?country; dc:title ?title. } FROM &lt;http://www.w3.org/2004/08/TalkFiles/2006/Talks.rdf&gt; FROM &lt;http://www.w3.org/2004/08/TalkFiles/2006/WWW2006.rdf&gt; FROM &lt;http://www.w3.org/2004/08/TalkFiles/2006/BeijingEvent.rdf&gt; FROM &lt;http://www.w3.org/2004/08/TalkFiles/2007/Talks.rdf&gt; FROM &lt;http://www.w3.org/2004/08/TalkFiles/2007/WWW2007.rdf&gt; FROM NAMED &lt;http://www.ivan-herman.net/foaf.rdf&gt; WHERE { GRAPH &lt;http://www.ivan-herman.net/foaf.rdf&gt; { [] foaf:knows [ foaf:name ?name ]. } ?talk dc:title ?title; dc:date ?date; talk:presenter ?person; talk:event [ ical:description ?event; vcard:Locality ?city; vcard:Country ?country ]. ?person contact:fullName ?name. } </pre> <p>This query can be run on a SPARQL endpoint (I used <a href="http://sparql.org/">SPARQLer</a> for this one) via the <a href="http://www.w3.org/TR/rdf-sparql-protocol/">SPARQL Protocol</a>, using a suitable URI. The URI is actually pretty ugly, so I made a tiny url out of it, and I simply plugged this <a href="http://tinyurl.com/2g78e3">tiny uri</a> as a data source for Exhibit in the HTML header. And, voilà!, the data displays. A bit of tweaks on the Exhibit lenses to make it a little bit nicer, define the facets, that sort of things, and put it on the Web. And the beauty is the typical mashup effect: if I add a new person to my foaf file or a new entry is added to the W3C Talks’ data, the display remains up-to-date… All data used here are pure RDF/XML files but, if the SPARQL endpoint understood, say, GRDDL on the fly, then I could have used my W3C Homepage as a datasource, too…</p> <p>One issue that I find interesting/important here is the crucial role of the CONSTRUCT facility of SPARQL, which adapts the output of the Query to Exhibit. I have the impression that, when talking about SPARQL, we do not emphasize enough what a great feature this CONSTRUCT is. A SPARQL endpoint acts as an <em>RDF transformation engine</em> which is really powerful.</p> </div> </div> </div>
        • description (String) David Huynh sent me a mail on a cool feature he...
          • David Huynh sent me a mail on a cool feature he has just added to Exhibit 2.0 : he’s put a shortcut to the Babel service. What this means is that one can refer to an RDF/XML, Excel, or a BibTex file instead of the JSON code, and Exhibit will convert it to RDF on the fly. So, to try it out, I put together a small example: the list of the W3C related talks of my buddies, ie, people whose name appear in my foaf file . And the remarkable thing is that this needed around 20-25 minutes (including ...
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://ivanherman.wordpress.com/2007/06/11/%e2%...
              • http://ivanherman.wordpress.com/2007/06/11/%e2%80%9cfriendly-talks%e2%80%9d-aka-i-had-some-fun-with-sparql-and-exhibit%e2%80%a6/
        • dc:date (Integer) 1181564700
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Ivan Herman
            • link (NULL)
            • email (NULL)
    • 17 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) More on RDF and Vertical Storage
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div>We actually did the experiment I mentioned a couple of posts back, about storing RDF triples column-wise.<br /> <br /> The test loads 4.8 million triples of LUBM data and reads the whole set on one index and then checks if it finds the same row on another index.<br /> <br /> Reading GSPO and checking OGPS takes 27 seconds.<span>&nbsp;</span> Doing the same with column wise bitmap indices on S, G, P and O takes 86 seconds.<span>&nbsp;&nbsp;</span> The latter checks the existence of the row by AND'ing 4 bitmap indices and the former checks its existence by a single lookup in a multi-part index whose last part is a bitmap.<span>&nbsp;</span> The result is approximately what one would expect.<span>&nbsp;</span> The bitmap AND could be optimized a bit, dropping the time to maybe 70 seconds.<span>&nbsp;</span><br /> <br /> Now speaking of compression, it is true that column storage will work better.<span>&nbsp;</span> For example the G and P columns will compress to pretty much nothing.<span>&nbsp;</span> On a row layout they compress too but not to nothing since even if a value is not unique you have to store the place where the value is if you want to read rows in constant time per row.<br /> <br /> What is nice with the 4 bitmaps is that no combination of search conditions is penalized.<span>&nbsp;</span> But the trick of using bitmaps for self-join is lost:<span>&nbsp;</span> You can't evaluate {?s a Person . ?s name "Mary"} by and'ing the S bitmaps for persons and for subjects named "Mary".<br /> <br /> The 4 bitmap indices are remarkably compact, though. 8840 pages all together.<br /> We could probably get the G, S, P, O columns in 3000 pages or so, using very little<span>&nbsp;</span> compression.<br /> The OGPS index is <span>&nbsp;&nbsp;</span>5169 pages and the GSPO index is 21243 pages.<br /> <br /> None of the figures have any compression, except what a bitmap naturally produces.<br /> <br /> Now we have figured out a modified row layout which will about double working set with the same memory and keep things in rows.<span>&nbsp;</span> We will try that.<span>&nbsp;</span> The GSPO index will be about<span>&nbsp;</span> 10000 pages and OGPS will be about 4500.<span>&nbsp;</span> We do not expect much impact on search or insert times.<br /> <br /> We looked at using gzip for database pages.<span>&nbsp;</span> They go to between 1/4 to 1/3 page.<span>&nbsp;&nbsp;</span> But this does not improve working set and having variable length pages generates all kinds of special cases you don’tt want.<span>&nbsp;</span> So we will improve working set first and deal with somewhat compressed data in the execution engine.<br /> After that, maybe gzip will cut the size to 1/2 or so but<span>&nbsp;</span> that will be good for disk only.<span>&nbsp;</span> And it does not so much matter how much you transfer but how many seeks you do.<br /> <br /> Still, column-wise storage will likely win for size.<span>&nbsp;</span> So if the working set is much larger than memory this may have an edge.<span>&nbsp;</span> To keep all bases covered we will eventually add this as an option.<br /></div> </div>
        • description (String) We actually did the experiment I mentioned a co...
          • We actually did the experiment I mentioned a couple of posts back, about storing RDF triples column-wise. The test loads 4.8 million triples of LUBM data and reads the whole set on one index and then checks if it finds the same row on another index. Reading GSPO and checking OGPS takes 27 seconds. &#160; Doing the same with column wise bitmap indices on S, G, P and O takes 86 seconds. &#160;&#160; The latter checks the existence of the row by AND'ing 4 bitmap indices and the former checks its existence by a single lookup in a multi-part index ...
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://www.openlinksw.com/weblog/oerling/?id=1222
        • dc:date (Integer) 1181550792
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Orri Erling
            • link (NULL)
            • email (NULL)
    • 18 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) Hostile to Privacy
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div> <p>I'll have more to say on this later in the week, but the <a href="http://www.privacyinternational.org/article.shtml?cmd[347]=x-347-553961"> Privacy International ratings of companies and their privacy policy</a> is very interesting reading–particularly the part about Google being hostile to privacy.</p> <p>I downloaded code checked into Google today, have received emails from people using Google, checked if my web settings are correct with Google's WebMaster tools (which ended up changing my username to the GMail account when I signed up for one in order to look at Google's use of Ajax), which then tracks me, as I surf about if I don't remember to log out.</p> <p>People use the tools for office work, for mapping, for reading feeds, subscribing to feeds, to cover their every movement–even who they're subscribed to, and who they read.</p> <p>What's particularly scary, and I think the report mentions this, is that Google can't understand why we're concerned. After all, this information will enable them to 'customize' our experiences. And, as comments have mentioned: Google gives us all this for free.</p> <p>Custom search results (filtering), custom recommendations (lack of diversity), even custom ads — all the better to cleverly trigger our impulse buying. These are not the equivalent of a government's demands for this information, but neither are they a 'good' thing.</p> <p>Generally, the folks in <a href="http://www.techcrunch.com/2007/06/10/google-rated-bottom-for-privacy/"> Duncan Riley's post</a> see no harm, and in fact, they love it when Google 'personalizes' everything. But what cost personalization? At what point can we no longer trust what we'll be receiving on the internet? At what point, will the discordant voices be screened?</p> <p>That's the original purpose of the internet, wasn't it? To provide a place for us to find new information and different views? New sources? New ways of looking at things?</p> <p>The wonder of serendipity?</p> <p>One thing I disagree with on the report: I don't see Google as 'hostile' to privacy. I think the company just doesn't understand it, or why any of us would be concerned about it. I think this overall puzzlement reflects the company's inward view, and lack of diversity on the staff–and by diversity, in this instance, I don't mean race or sex. I mean the company lacks the ability to see outside of its own algorithms.</p> <p>It is this 'corporate confusion' over privacy and our concerns that's actually more intimidating than if the company was willfully deceptive.</p> <p>More on this later.</p> <div> <p><b>update</b></p> <p>Danny Sullivan has the most <a href="http://searchengineland.com/070610-100246.php">detailed look and pushback against the report</a> at this time. I think he's missing a major aspect of the report: it's from our viewpoint, based on what we can see. Now what an insider knows. Not what a search engine expert understands.</p> </div> <p>Continued <a href="http://burningbird.net/technology/on-privacy-redux/">here</a></p> </div> </div>
        • description (String) I'll have more to say on this later in the week...
          • I'll have more to say on this later in the week, but the Privacy International ratings of companies and their privacy policy is very interesting reading–particularly the part about Google being hostile to privacy. I downloaded code checked into Google today, have received emails from people using Google, checked if my web settings are correct with Google's WebMaster tools (which ended up changing my username to the GMail account when I signed up for one in order to look at Google's use of Ajax), which then tracks me, as I surf about if I don't remember to log out. People ...
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://burningbird.net/technology/hostile-to-pr...
              • http://burningbird.net/technology/hostile-to-privacy/
        • dc:date (Integer) 1181534333
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Shelley Powers
            • link (NULL)
            • email (NULL)
    • 19 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) Ajaxy Comments
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div> <p>I've incorporated editing into the site–both traditional, link-based, and Ajax. I still need to tweak, and I imagine as people use the comments, things will break.</p> <p>Both types of edits are available for each item, using the philosophy that a person may want to use a traditional edit page over an Ajax editing approach. The hypertext link for editing takes you to the full edit page, where you can also delete the comment. The Ajax approach is accessible through a 'button' added to the post using script.</p> <p>I had planned on pulling my simple custom library for the background functionality, and either using JQuery, or <a href="http://dean.edwards.name/weblog/2007/05/miniweb/">Dean Edwards</a> Base.dom on which to build. However, I'm concerned about the Safari problem with Dean's library, and I'm not sure that JQuery fits all my needs. What I may end up doing is pulling in Edwards' library, and creating my own custom intermediate library.</p> <p>All I've done for now is create a singleton where before I had several global functions. The original approach doesn't impact on performance or cross-browser compatibility, but lots of global variables can cause problems with merged libraries. I've also made some attempts at eliminating IE memory links related to removeChild used with elements with assigned event handlers, but this still needs work.</p> <p>I have one polling operation that checks to see if there are new comments after the page is loaded, and then pulls these in if found. The new comment(s) are added to the end of the list of comments in the page, with a yellow 'fade' to signal the addition. I've also added an Ajax preview, but not a non-scripted preview. Lots of real issues doing the latter with Wordpress. Mayhap someone else has a plugin for it.</p> <p>Finally, I didn't incorporate OpenID. I thought about doing this, and had incorporated OpenID for comments via an existing plug-in at one point. However, OpenID is identity, not necessarily trust or ownership. My main interest is identifying the person who just made a comment and perhaps wants to edit typos–that's it. For now, I'm using a combination of cookies and IP address. It's not perfect, but it should be relatively safe, and relatively open.</p> <p>If I had used OpenID, those people who did not want to get one of these, or who write anonymously wouldn't have been able to edit their comments. Contrary to popular criticism, anonymous comments do have value, at least in this space.</p> <p>One big problem I ran into, and perhaps I don't understand XHTML, is that when I created the URL to edit a comment, which uses a traditional GET with two parameters, ala ?action=http://planetrdf.com//editcomment&amp;comment=3333, I received a mal-formed XML error with Firefox. The page validated, and also pulled up in every other browser. Did I miss something related to XHTML with this one?</p> <p>I have a lot more to do with the site, and the underlying libraries, but I'm starting the book this next week, and will have to finish the bits off as I can. I still have my graphics and photo library, and some meta/RDF stuff I want to incorporate. Once the work I've published here gets a chance to be decently tested, I'll look at packaging for other use. It's not going to be a simple plug-in, but should be able to be packaged.</p> <div> <p><b>update</b></p> <p>I had forgotten to encode the ampersand in the URL for the link. The validator did not pick it up, because I also forgot that the link wouldn't show unless the application accessed it with my logged in cookie.</p> <p>Yes, it was a particularly stupid error on my part. That's what's nice about XHTML: it doesn't hesitate to let you know when you've been stupid. Same as anonymous commenters. &lt;smiley /&gt;</p> </div> </div> </div>
        • description (String) I've incorporated editing into the site–both ...
          • I've incorporated editing into the site–both traditional, link-based, and Ajax. I still need to tweak, and I imagine as people use the comments, things will break. Both types of edits are available for each item, using the philosophy that a person may want to use a traditional edit page over an Ajax editing approach. The hypertext link for editing takes you to the full edit page, where you can also delete the comment. The Ajax approach is accessible through a 'button' added to the post using script. I had planned on pulling my simple custom library for the background functionality, ...
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://burningbird.net/technology/ajaxy-comments/
        • dc:date (Integer) 1181532222
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Shelley Powers
            • link (NULL)
            • email (NULL)
    • 20 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) More on Word's mediocre XML
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div>It's not just the index tag markup, but most of the "Insert Field" parts.</div> </div>
        • description (String) It's not just the index tag markup, but most of...
          • It's not just the index tag markup, but most of the "Insert Field" parts.
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://www.snee.com/bobdc.blog/2007/06/more_on_...
              • http://www.snee.com/bobdc.blog/2007/06/more_on_words_mediocre_xml.html
        • dc:date (Integer) 1181487311
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Bob DuCharme
            • link (NULL)
            • email (NULL)
    • 21 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) Reification (the other meaning)
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div>"<b>Reification is the soul of the Semantic Web</b>" is a good example of reification in the Marxist interpretation. Don't believe me? <b>Then stumble yourself accross the wikipedia article on <a href="http://en.wikipedia.org/wiki/Reification_%28Marxism%29">reification (marxism)</a>.</b><br /> <br /> <cite>Reification (German: Verdinglichung, literally: "thing-ification") is the consideration of an abstraction or an object as if it had human (pathetic fallacy) or living (reification fallacy) existence and abilities; at the same time it implies the thingification of social relations.</cite><br /> <br /> More:<br /> <cite>Ordinary examples of Reification<br /> <br /> Reification occurs when specifically human creations are misconceived as “facts of nature, results of cosmic laws, or manifestations of divine will”. [3]<br /> <br /> Reification is very visible in advertising when the advertiser or designer deliberately tries to associate a commercial product with all kinds of desirable qualities or contexts, with the suggestion that if you buy the product, that you will have access to or experience those desirable qualities. The product thus acquires an deliberately contrived imaginary status in addition to its real status.<br /> <br /> A very graphic visual example of reification is pornography in which sexual acts are separated out from the total human context in which they occur.<br /> <br /> Reification also frequently occurs in language and any form of communication which involves the representation of things or relationships by symbols. For example, the sentence "Make your money work for you" contains a reification, because money does not do any work at all, people do. The power to do work is falsely attributed to money.<br /> <br /> A characteristic of mental illness can be that the mentally-ill person reifies himself or parts of the world around him, misplacing the true context of things, or attributing powers to himself and to objects in the world which they do not really have.</cite><br /> <br /> Because of heavily copy/pasted from wikipedia, this blog post is under available under the terms of the <a href="http://en.wikipedia.org/wiki/Wikipedia:Text_of_the_GNU_Free_Documentation_License"> GNU Free Documentation License</a>.</div> </div>
        • description (String) " Reification is the soul of the Semantic Web "...
          • " Reification is the soul of the Semantic Web " is a good example of reification in the Marxist interpretation. Don't believe me? Then stumble yourself accross the wikipedia article on reification (marxism) . Reification (German: Verdinglichung, literally: "thing-ification") is the consideration of an abstraction or an object as if it had human (pathetic fallacy) or living (reification fallacy) existence and abilities; at the same time it implies the thingification of social relations. More: Ordinary examples of Reification Reification occurs when specifically human creations are misconceived as “facts of nature, results of cosmic laws, or manifestations of divine will”. [3] ...
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://leobard.twoday.net/stories/3820915/
        • dc:date (Integer) 1181473320
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Leo Sauermann
            • link (NULL)
            • email (NULL)
    • 22 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) Brief Outage
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div> <p>Our hosting provider, Joyent, apparently took some kind of hardware hit today; they haven’t said, yet, whether it was a disk or controller or something else, but we stopped being able to SSH into our container last night. So I filed a ticket. (I forgot that we have 24-hr emergency tech support. Doh!)</p> <p>Then today HTTP stopped and we couldn’t ping the sites, etc. Doh!!</p> <p>After a call to the now-remembered emergency line, we get the container rebooted (it must really be bad, then, since, generally, you don’t fix things in Unix by rebooting), but there was no /home volume mounted. Ouch!</p> <p>After the RAID was rebuilt, apparently, we got /home, and things got a lot better here today. Joyent has been pretty solid (modulo some weird Java bug we can’t track down), but we just launched the new <a href="http://pellet.owldl.com/">Pellet</a> site yesterday, so it being down today is a real bummer.</p> <p>Computers suck! Okay, shit breaks, and that’s the reason for ZFS, RAID, etc. (I think this part of the outage was only about 30 minutes, which is good, but not great.)</p> <p>But it would be nice if Joyent would give us some more info about what was wrong. I’m not sure why, but more info would make me feel better…</p> </div> </div>
        • description (String) Our hosting provider, Joyent, apparently took s...
          • Our hosting provider, Joyent, apparently took some kind of hardware hit today; they haven’t said, yet, whether it was a disk or controller or something else, but we stopped being able to SSH into our container last night. So I filed a ticket. (I forgot that we have 24-hr emergency tech support. Doh!) Then today HTTP stopped and we couldn’t ping the sites, etc. Doh!! After a call to the now-remembered emergency line, we get the container rebooted (it must really be bad, then, since, generally, you don’t fix things in Unix by rebooting), but there was no /home volume ...
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://clarkparsia.com/weblog/2007/06/08/brief-...
              • http://clarkparsia.com/weblog/2007/06/08/brief-outage/
        • dc:date (Integer) 1181324957
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Clark and Parsia
            • link (NULL)
            • email (NULL)
    • 23 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) Reconnected
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div> <p>I think the last thunderstorm fried my wireless card - quite frustrating, because the places I was staying in had decent connections. Very good people at ESWC, btw.<br /></p> <p>Now at Talis, slightly freaked that I made the absolutely the right decision when I jumped on board (some motivations were questionable, blame Royal Bank of Scotland for that one). <strike>They</strike> We know what <strike>they're</strike> we're doing, and it's about as hot as it gets. The infrastructure is sorted, which is a total novelty to me.</p> <p>Stuff to do, party later.&nbsp;</p> <p>Slides from last week here - trying to answer "<a href="http://dannyayers.com/sfsw2007/slides">where are the agents?</a>" (behind you Jim ;-)<br /></p> </div> </div>
        • description (String) I think the last thunderstorm fried my wireless...
          • I think the last thunderstorm fried my wireless card - quite frustrating, because the places I was staying in had decent connections. Very good people at ESWC, btw. Now at Talis, slightly freaked that I made the absolutely the right decision when I jumped on board (some motivations were questionable, blame Royal Bank of Scotland for that one). They We know what they're we're doing, and it's about as hot as it gets. The infrastructure is sorted, which is a total novelty to me. Stuff to do, party later.&#160; Slides from last week here - trying to answer " where ...
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://dannyayers.com/2007/06/08/reconnected
        • dc:date (Integer) 1181312427
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Danny Ayers
            • link (NULL)
            • email (NULL)
    • 24 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) Talis Summer Ball
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div> <p>Just packing a bag for tonight’s Talis party. This is our annual staff and friends event and an opportunity to let our hair down. This year especially because the theme is the 70’s in the Caribbean!! No, I’m not entirely sure what that means either. But everyone has been busy pulling together costumes by scouring ebay, charity shops and raiding parents’ wardrobes. I’m taking my camera…!</p> </div> </div>
        • description (String) Just packing a bag for tonight’s Talis party....
          • Just packing a bag for tonight’s Talis party. This is our annual staff and friends event and an opportunity to let our hair down. This year especially because the theme is the 70’s in the Caribbean!! No, I’m not entirely sure what that means either. But everyone has been busy pulling together costumes by scouring ebay, charity shops and raiding parents’ wardrobes. I’m taking my camera…!
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://iandavis.com/blog/2007/06/talis-summer-ball
        • dc:date (Integer) 1181311611
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Ian Davis
            • link (NULL)
            • email (NULL)
    • 25 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) Java SemWeb developers wanted
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div><a href="http://www.aduna-software.com/">Aduna</a>, the company behind <a href="http://www.openrdf.org/">Sesame</a>, <a href="http://www.aduna-software.com/home/careers/overview.view">is hiring</a>. We have several open positions in our development team (we're looking for a <a href="http://www.aduna-software.com/home/careers/java_software_engineer_junior.view"> Junior Java Software Engineer</a> and a <a href="http://www.aduna-software.com/home/careers/java_software_engineer_senior.view"> Senior Java Software Engineer</a>) and are looking for talented people who are interested in helping us develop the building blocks of the Semantic Web. If you are interested, have a look at the job descriptions, and <a href="http://www.aduna-software.com/contact/overview.view">contact us</a>.</div> </div>
        • description (String) Aduna , the company behind Sesame , is hiring...
          • Aduna , the company behind Sesame , is hiring . We have several open positions in our development team (we're looking for a Junior Java Software Engineer and a Senior Java Software Engineer ) and are looking for talented people who are interested in helping us develop the building blocks of the Semantic Web. If you are interested, have a look at the job descriptions, and contact us .
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://feeds.feedburner.com/~r/TheSeer/~3/12320...
              • http://feeds.feedburner.com/~r/TheSeer/~3/123206636/java-semweb-developers-wanted.html
        • dc:date (Integer) 1181305745
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Jeen Broekstra
            • link (NULL)
            • email (NULL)
    • 26 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) Photographic metadata and digiKam
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div>I'm still trying to find a good way to manage photographic metadata.</div> </div>
        • description (String) I'm still trying to find a good way to manage p...
          • I'm still trying to find a good way to manage photographic metadata.
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://norman.walsh.name/2007/06/08/digikam
        • dc:date (Integer) 1181302840
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Norm Walsh
            • link (NULL)
            • email (NULL)
    • 27 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) QOTD
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div> <p><a href="http://gizmodo.com/gadgets/sssh/thankos-silent-keyboard-only-makes-6db-266953.php"> We seriously don’t know how you IBM keyboard lovers get any work done when it sounds like Optimus Prime pleasuring himself with a jackhammer.</a></p> </div> </div>
        • description (String) We seriously don’t know how you IBM keyboard ...
          • We seriously don’t know how you IBM keyboard lovers get any work done when it sounds like Optimus Prime pleasuring himself with a jackhammer.
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://www.semergence.com/2007/06/07/qotd/
        • dc:date (Integer) 1181257820
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Seth Ladd
            • link (NULL)
            • email (NULL)
    • 28 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) Pellet 1.5 Release Candidate #1
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div> <p>The first release candidate in the Pellet 1.5 series is <a href="http://pellet.owldl.com/download">available for download</a>. Notable enhancements since the 1.4 release (in March) include significant optimizations within the concept classifier (which <a href=http://planetrdf.com//"/weblog/2007/04/10/pellet-classification-improvements/">we’ve mentioned before</a>), axiom tracing to provide justification for arbitrary inferences, and preliminary support for incremental reasoning. We’ve also been able to resolve a collection of miscellaneous bugs. For more details on the release, you can see <a href="http://lists.owldl.com/pipermail/pellet-users/2007-June/001605.html"> the announcement in the pellet-users list archives</a>.</p> <p>Also of note, if you take a look at the <a href="http://pellet.owldl.com/">new Pellet site</a> you’ll notice we’ve done quite a bit of work expanding the <a href="http://pellet.owldl.com/faq">Pellet FAQ</a> content. Maybe we finally got to that question that you’ve always wondered about but never asked.</p> <p>Finally, remember, this is a release <i>candidate</i> for a reason. We think it’s great, but we’re looking for feedback and bug reports. Pellet is successful as a software project because we get high quality feedback from its users. If you find an issue, browse <a href="http://cvsdude.com/trac/clark-parsia/pellet-devel/report">the public issue tracker</a> for more information and let us know about it on the <a href="http://lists.owldl.com/mailman/listinfo/pellet-users">pellet-users list</a>.</p> </div> </div>
        • description (String) The first release candidate in the Pellet 1.5 s...
          • The first release candidate in the Pellet 1.5 series is available for download . Notable enhancements since the 1.4 release (in March) include significant optimizations within the concept classifier (which we’ve mentioned before ), axiom tracing to provide justification for arbitrary inferences, and preliminary support for incremental reasoning. We’ve also been able to resolve a collection of miscellaneous bugs. For more details on the release, you can see the announcement in the pellet-users list archives . Also of note, if you take a look at the new Pellet site you’ll notice we’ve done quite a bit of work expanding the ...
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://clarkparsia.com/weblog/2007/06/07/pellet...
              • http://clarkparsia.com/weblog/2007/06/07/pellet-15-release-candidate-1/
        • dc:date (Integer) 1181244450
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Clark and Parsia
            • link (NULL)
            • email (NULL)
    • 29 (Object) SimplePie_Item
      • data (Array) 6 elements
        • title (String) RESTful Web Services: the book
        • encoded (String) <div xmlns='http://www.w3.org/1999/xhtml'> <div...
          • <div xmlns='http://www.w3.org/1999/xhtml'> <div><a href="http://www.oreilly.com/catalog/9780596529260/"><img align="right" src="http://blogs.sun.com/bblfish/resource/RESTfulWebServicesTheBook.jpg" alt="" /></a> <p><a href="http://www.oreilly.com/catalog/9780596529260/">RESTful Web Services</a> is a newly published book that should be a great help in giving people an overview of how to build web services that work with the architecture of the Web. The authors of the book are I believe serious RESTafarians. They hang out (virtually) on the yahoo <a href="http://tech.groups.yahoo.com/group/rest-discuss/">REST discuss</a> newsgroup. So I know ahead of time that they will most likely never fail on the REST side of things. Such a book should therefore be a great help for people desiring to develop web services.</p> <p>As an aside, I am currently reading it online via <a href="http://safaribooksonline.com/">Safari Books</a>, which is a really useful service, especially for people like me who are always traveling and don't have space to carry wads of paper around the world. As I have been intimately involved in this area for a while - <a href="http://bblfish.net/blog/page1.html#10">I read Roy Fielding's thesis</a> in 2004, and it immediately made sense of my intuitions - I am skipping through the book from chapter to chapter as my interests guide me, using the search tool when needed. As this is an important book, I will write up my comments here in a number of posts as I work my way through it.</p> <p>What of course is missing in Roy's thesis, which is a high level abstract description of an architectural style, are practical examples, which is what this book sets out to provide. The advantage of Roy's level of abstraction is that it permitted him to make some very important points without loosing himself in arbitrary implementation debates. Many implementations can fit his architectural style. That is the power of speaking at the right level of abstraction: it permits one to say something well, in such a way that it can withstand the test of time. Developers of course want to see how an abstract theory applies to their everyday work, and so a cook book such as "RESTful Web Services" is going to appeal to them. The danger is that by stepping closer to implementation details, certain choices are made that turn out to be in fact arbitrary, ill conceived, non optimal or incomplete. The risk is well worth taking if it can help people find their way around more easily in a sea of standards. This is where the rubber hits the road.</p> <p>Right from the beginning the authors, <a href="http://intertwingly.net/blog/">Sam Ruby</a> and <a href="http://www.crummy.com/">Leonard Richardson</a> coin the phrase "Resource Oriented Architecture".</p> <blockquote> <p>Why come up with a new term, Resource-Oriented Architecture? Why not just say REST? Well, I do say REST, on the cover of this book, and I hold that everything in the Resource-Oriented Architecture is also RESTful. But REST is not an architecture: it's a set of design criteria. You can say that one architecture meets those criteria better than another, but there is no one "REST architecture."</p> </blockquote> <p>The emphasis on Resources is I agree with them fundamental. Their chapter 4 does a very good job of showing why. URIs name Resources. URLs in particular name Resources that can return representations in well defined ways. REST stands for "Representation of State Transfer", and the representations transferred are the representations of resources identified by URLs. The whole thing fits like a glove.</p> <p>Except that where there is a glove, there are two, one for each hand. And they are missing the other glove, so to speak. And the lack is glaringly obvious. Just as important as Roy Fielding's work, just as abstract, and developed by some of the best minds on the web, even in the world, is <a href="http://www.w3.org/RDF/">RDF</a>, which stands for <b>Resource</b> Description Framework. I emphasize the "Resource" in RDF because for someone writing a book on Resource Oriented Architecture, to have only three short mentions of the framework for describing resources standardized by non less that the <a href="http://w3.org/">World Wide Web Consortium</a> is just ... flabbergasting. Ignoring this work is like trying to walk around on one leg. It is possible. But it is difficult. And certainly a big waste of energy, time and money. Of course since what they are proposing is so much better than what may have gone on previously, which seems akin to trying to walk around on a gloveless hand, it may not immediately be obvious what is missing. I shall try to make this clear in the series of notes.</p> <p>Just as REST is very simple, so is RDF. It is easiest to describe something on the web if you have a URL for it. If you want to say something about it, that it relates to something else for example, or that it has a certain property, you need to specify which property it has. Since a property is a thing, it too is easiest to speak about if it has a URL. So once you have identified the property in the global namespace you want to say what its value is, you need to specify what the value of that property is, which can be a string or another object. That's RDF for you. It's so simple I am able to explain it to people in bars within a minute. Here is an example, which says that my name is Henry:</p> <code>&lt;<a href="http://bblfish.net/people/henry/card#me">http://bblfish.net/people/henry/card#me</a>&gt; &lt;<a href="http://xmlns.com/foaf/0.1/name">http://xmlns.com/foaf/0.1/name</a>&gt; "Henry Story" .</code> <p>Click on the URLs and you will <a href="http://blogs.sun.com/bblfish/entry/get_my_meaning">GET their meaning</a>. Since resources can return any number of representations, different user agents can get the representation they prefer. For the <a href="http://xmlns.com/foaf/0.1/name">name</a> relation you will get an html representation back if you are requesting it from a browser. With this system you can describe the world. We know this since it is simply a generalization of the system found in relational databases, where instead of identifying things with table dependent primary keys, we identify them with URIs.</p> <p>So RDF, just as REST, is at its base very easy to understand and furthermore the two are complementary. Even though REST is simple, it nevertheless needs a book such as "RESTful web services" to help make it practical. There are many dispersed standards out there which this books helps bring together. It would have been a great book if it had not missed out the other half of the equation. Luckily this should be easy to fix. And I will do so in the following notes, showing how RDF can help you become even more efficient in establishing your web services. Can it really be even easier? Yes. And furthermore without contradicting what this book says.</p> </div> </div>
        • description (String) RESTful Web Services is a newly published book ...
          • RESTful Web Services is a newly published book that should be a great help in giving people an overview of how to build web services that work with the architecture of the Web. The authors of the book are I believe serious RESTafarians. They hang out (virtually) on the yahoo REST discuss newsgroup. So I know ahead of time that they will most likely never fail on the REST side of things. Such a book should therefore be a great help for people desiring to develop web services. As an aside, I am currently reading it online via Safari Books ...
        • link (Array) 1 element
          • alternate (Array) 1 element
            • 0 (String) http://blogs.sun.com/bblfish/entry/restful_web_...
              • http://blogs.sun.com/bblfish/entry/restful_web_services_the_book
        • dc:date (Integer) 1181191093
        • creator (Array) 1 element
          • 0 (Object) SimplePie_Author
            • name (String) Henry Story
            • link (NULL)
            • email (NULL)
  • Krumo version 0.1a
    | http://krumo.sourceforge.net
    Called from /home/aaron/summer_of_code/soc_aggregation/parser_test.php, line 96