http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/
Kingsley Idehen's Blog Data Space
I have seen the future and it's full of Linked Data! :-)
kidehen@openlinksw.com
kidehen@openlinksw.com
2024-03-28T10:38:22Z
Virtuoso Universal Server 08.03.3327
http://www.openlinksw.com/weblog/public/images/vbloglogo.gif
Simple Virtuoso Installation & Utilization Guide for SPARQL Users (Update 5)
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2011-01-16#1647
2011-01-16T07:06:21Z
2011-01-19T10:43:35-05:00
<h3>What is <a class="auto-href" href="http://dbpedia.org/resource/SPARQL" id="link-id0x1ab60ac0">SPARQL</a>?</h3> <p>A declarative query language from the W3C for querying structured propositional <a href="http://dbpedia.org/resource/Data">data</a> (in the form of 3-<a href="http://en.wikipedia.org/wiki/Tuple" id="link-id0x1b1e0010">tuple</a> [triples] or 4-tuple [quads] records) stored in a <a href="http://en.wikipedia.org/wiki/Deductive_database" id="link-id0x1cf8af98">deductive database</a> (colloquially referred to as triple or quad stores in <a class="auto-href" href="http://dbpedia.org/resource/Semantic_Web" id="link-id0x1caf5050">Semantic Web</a> and <a class="auto-href" href="http://dbpedia.org/resource/Linked_Data" id="link-id0x19d781b8">Linked Data</a> parlance).</p> <p>SPARQL is inherently platform independent. Like <a class="auto-href" href="http://dbpedia.org/resource/SQL" id="link-id0x1b879140">SQL</a>, the query language and the backend database engine are distinct. Database clients capture SPARQL queries which are then passed on to compliant backend databases.</p> <h3>Why is it important?</h3> <p>Like SQL for relational databases, it provides a powerful mechanism for accessing and joining data across one or more data partitions (named graphs identified by IRIs). The aforementioned capability also enables the construction of sophisticated Views, Reports (HTML or those produced in native form by desktop productivity tools), and data streams for other services.</p> <p>Unlike SQL, SPARQL includes result serialization formats and an HTTP based wire protocol. Thus, the ubiquity and sophistication of HTTP is integral to SPARQL i.e., client side applications (user agents) only need to be able to perform an HTTP GET against a <a class="auto-href" href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id0x1ba287e8">URL</a> en route to exploiting the power of SPARQL.</p> <h3>How do I use it, generally?</h3> <ol> <li>Locate a SPARQL endpoint (<a href="http://dbpedia.org/sparql" id="link-id0x1d7436b0">DBpedia</a>, <a href="http://lod.openlinksw.com/sparql" id="link-id0x1bf20690">LOD Cloud Cache</a>, <a href="http://semantic.data.gov" id="link-id0x1a8ebc28">Data.Gov</a>, <a href="http://linkeddata.uriburner.com/sparql" id="link-id0x1be93070">URIBurner</a>, <a href="http://www.delicious.com/kidehen/sparql_endpoint" id="link-id0x1cce9b40">others</a>), or;</li> <li>Install a SPARQL compliant database server (quad or triple store) on your desktop, workgroup server, data center, or cloud (e.g., <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtuosoEC2AMI" id="link-id0x1cd697a0">Amazon EC2 AMI</a>)</li> <li>Start the database server</li> <li>Execute SPARQL Queries via the <a href="http://lod.openlinksw.com/sparql" id="link-id0x1b99d790">SPARQL endpoint.</a> </li> </ol> <h3>How do I use SPARQL with <a class="auto-href" href="http://virtuoso.openlinksw.com" id="link-id0x1c9adc80">Virtuoso</a>?</h3> <p>What follows is a very simple guide for using SPARQL against your own instance of Virtuoso:</p> <ol> <li>Software Download and Installation</li> <li>Data Loading from Data Sources exposed at Network Addresses (e.g. HTTP URLs) using very simple methods</li> <li>Actual SPARQL query execution via SPARQL endpoint.</li> </ol> <h3>Installation Steps</h3> <ol> <li> Download <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VOSDownload" id="link-id0x1b795100">Virtuoso Open Source</a> or <a href="http://download.openlinksw.com/virtwiz/virtuoso.php" id="link-id0x1cce46f0">Virtuoso Commercial</a> Editions </li> <li> Run installer (if using Commercial edition of Windows Open Source Edition, otherwise follow build guide) </li> <li> Follow post-installation guide and verify installation by typing in the command: virtuoso -? (if this fails check you've followed installation and setup steps, then verify environment variables have been set) </li> <li> Start the Virtuoso server using the command: virtuoso-start.sh </li> <li> Verify you have a connection to the Virtuoso Server via the command: isql localhost (assuming you're using default DB settings) or the command: isql localhost:1112 (assuming demo database) or goto your browser and type in: http://<virtuoso-server-host-name>:[port]/conductor (e.g. http://localhost:8889/conductor for default DB or http://localhost:8890/conductor if using Demo DB) </li> <li> Go to SPARQL endpoint which is typically -- http://<virtuoso-server-host-name>:[port]/sparql </li> <li> Run a quick sample query (since the database always has system data in place): select distinct * where {?s ?p ?o} limit 50 .</li> </ol> <h3>Troubleshooting</h3> <ol> <li>Ensure environment settings are set and functional -- if using Mac OS X or Windows, so you don't have to worry about this, just start and stop your Virtuoso server using native OS services applets</li> <li>If using the Open Source Edition, follow the <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VOSMake#Getting%20Started" id="link-id0x1bfa7548">getting started guide</a> -- it covers PATH and startup directory location re. starting and stopping Virtuoso servers.</li> <li>Sponging (HTTP GETs against external Data Sources) within SPARQL queries is disabled by default. You can enable this feature by assigning "<a href="http://docs.openlinksw.com/virtuoso/rdfsparql.html#rdfsupportedprotocolendpointuri" id="link-id0x1d566270">SPARQL_SPONGE</a>" privileges to user "SPARQL". Note, more sophisticated security exists via <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtAuthPolicyFOAFSSL" id="link-id0x1a3c9eb8">WebID based ACLs</a>. </li> </ol> <h3>Data Loading Steps</h3> <ol> <li> Identify an RDF based structured data source of interest -- a file that contains 3-tuple / triples available at an address on a public or private HTTP based network </li> <li>Determine the Address (URL) of the RDF data source</li> <li>Go to your Virtuoso SPARQL endpoint and type in the following SPARQL query: DEFINE GET:SOFT "replace" SELECT DISTINCT * FROM <RDFDataSourceURL> WHERE {?s ?p ?o} </li> <li> All the triples in the RDF resource (data source accessed via URL) will be loaded into the Virtuoso Quad Store (using RDF Data Source URL as the internal quad store Named Graph IRI) as part of the SPARQL query processing pipeline. </li> </ol> <p> Note: the data source URL doesn't even have to be RDF based -- which is where the Virtuoso <a class="auto-href" href="http://virtuoso.openlinksw.com/Whitepapers/html/VirtSpongerWhitePaper.html" id="link-id0x1d1a0978">Sponger</a> Middleware comes into play (download and install the <a href="http://s3.amazonaws.com/opldownload/uda/vad-packages/6.1/virtuoso/rdf_mappers_dav.vad" id="link-id0x1d0e1530">VAD installer package</a> first) since it delivers the following features to Virtuoso's SPARQL engine: </p> <ol> <li> Transformation of data from non RDF data sources (file content, hypermedia resources, <a href="http://dbpedia.org/resource/World_Wide_Web">web</a> services output etc..) into RDF based 3-tuples (triples)</li> <li> Cache Invalidation Scheme Construction -- thus, subsequent queries (without the define get:soft "replace" pragma will not be required bar when you forcefully want to override cache).</li> <li> If you have very large data sources like DBpedia etc. from CKAN, simply use our <a href="http://www.openlinksw.com/dataspace/dav/wiki/Main/VirtBulkRDFLoader" id="link-id0x1d19b4b0">bulk loader</a> . </li> </ol> <h3>SPARQL Endpoint Discovery</h3> <p>Public SPARQL endpoints are emerging at an ever increasing rate. Thus, we've setup up a DNS lookup service that provides access to a large number of SPARQL endpoints. Of course, this doesn't cover all existing endpoints, so if our endpoint is missing please ping <a class="auto-href" href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id0x1d634848">me</a>.</p> <p>Here are a collection of commands for using DNS-SD to discover SPARQL endpoints:</p> <ol> <li>dns-sd -B _sparql._tcp sparql.openlinksw.com -- browse for services instances</li> <li>dns-sd -Z _sparql._tcp sparql.openlinksw.com -- output results in Zone File format</li> <li></li> </ol> <h3>Related</h3> <ol> <li> <a href="http://www.ensta.fr/~diam/ruby/online/ruby-doc-stdlib/libdoc/net/http/rdoc/index.html" id="link-id0x1b156610">Using HTTP from Ruby</a> -- you can just make <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VOSSparqlProtocol" id="link-id0x1d024d60">SPARQL Protocol URLs</a> re. SPARQL</li> <li> <a href="http://sparql.rubyforge.org/client/" id="link-id0x1cd43a48">Using SPARQL Endpoints via Ruby</a> -- Ruby example using DBpedia endpoint</li> <li> <a href="http://wikis.openlinksw.com/dataspace/owiki/wiki/OATWikiWeb/InteractiveSparqlQueryBuilder" id="link-id0x1b9d2190">Interactive SPARQL Query By Example (QBE) tool</a> -- provides a graphical user interface (as is common in SQL realm re. query building against <a class="auto-href" href="http://dbpedia.org/resource/Relational_database_management_system" id="link-id0x1bfffb70">RDBMS</a> engines) that works with any SPARQL endpoint </li> <li> <a href="http://www.openlinksw.com/dataspace/dav/wiki/Main/VirtRDFInsert" id="link-id0x1ab63de0">Other methods of loading RDF data into Virtuoso</a> </li> <li> <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtSponger" id="link-id0x1ca248e0">Virtuoso Sponger</a> -- architecture and how it turns a wide variety of non RDF data sources into SPARQL accessible data </li> <li> <a href="http://ode.openlinksw.com/example.html" id="link-id0x1be34758">Using OpenLink Data Explorer</a> (ODE) to populate Virtuoso -- locate a resource of interest; click on a bookmarklet or use <a class="auto-href" href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id0x1ca84af0">context</a> menus (if using ODE extensions for Firefox, Safari, or Chrome); and you'll have SPARQL accessible data automatically inserted into your Virtuoso instance. </li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1295" id="link-id0x1c9060f0">W3C's SPARQLing Data Access Ingenuity</a> -- an older generic SPARQL introduction post </li> <li> <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtSPARQLRef" id="link-id0x1cf1e298">Collection of SPARQL Query Examples </a>-- GoodRelations (Product Offers), <a class="auto-href" href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id0x1c0445d0">FOAF</a> (Profiles), <a class="auto-href" href="http://dbpedia.org/resource/SIOC" id="link-id0x1b785e48">SIOC</a> (Data Spaces -- <a href="http://ods.openlinksw.com/dataspace/dav/wiki/ODS/ODSAtomOWLRefExampleBlog" id="link-id0x1b6c9f78">Blogs</a>, <a href="http://ods.openlinksw.com/dataspace/dav/wiki/ODS/ODSAtomOWLRefExampleWiki" id="link-id0x1c188280">Wikis</a>, <a href="http://ods.openlinksw.com/dataspace/dav/wiki/ODS/ODSAtomOWLRefExampleBookmarks" id="link-id0x1a9a8f98">Bookmarks</a>, <a href="http://ods.openlinksw.com/dataspace/dav/wiki/ODS/ODSAtomOWLRefExampleFeeds" id="link-id0x1720c658">Feed Collections</a>, <a href="http://ods.openlinksw.com/dataspace/dav/wiki/ODS/ODSAtomOWLRefExampleGallery" id="link-id0x1cdba348">Photo Galleries</a>, <a href="http://ods.openlinksw.com/dataspace/dav/wiki/ODS/ODSAtomOWLRefExampleBriefcase" id="link-id0x1c8f1148">Briefcase/DropBox</a>, <a href="http://ods.openlinksw.com/dataspace/dav/wiki/ODS/ODSAtomOWLRefExampleAddressbook" id="link-id0x1b5eb7e0">AddressBook</a>, <a href="http://ods.openlinksw.com/dataspace/dav/wiki/ODS/ODSAtomOWLRefExampleCalendar" id="link-id0x1c575120">Calendars</a>, <a href="http://ods.openlinksw.com/dataspace/dav/wiki/ODS/ODSAtomOWLRefExampleDiscussions" id="link-id0x1c73be98">Discussion Forums</a>) </li> <li> <a href="http://lod.openlinksw.com/demo_queries/" id="link-id0x1b08aa00">Collection of Live SPARQL Queries against LOD Cloud Cache</a> -- simple and advanced queries. </li> </ol>
7 Things Brought to You by HTTP-based Hypermedia
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2010-11-08#1644
2010-11-08T21:43:28Z
2010-11-08T15:29:43-05:00
<p>There are some very powerful benefits that accrue from the use of <a href="http://dbpedia.org/resource/Hypertext_Transfer_Protocol" id="link-id0x1b498648">HTTP</a> based <a href="http://dbpedia.org/resource/Hypermedia" id="link-id0x1be1e208">Hypermedia</a>. 7 that come to mind immediately include: </p> <ol> <li>Structured & Platform Independent Enterprise <a class="auto-href" href="http://dbpedia.org/resource/Federated_database_system" id="link-id0x1ab5d6c8">Data Virtualization</a> -- concrete conceptual level access and provisioning of abstract domain entities such as Customers, Orders, Employees, Products, Countries, Competitors etc.</li> <li>Distributed Application State (<a href="http://dbpedia.org/resource/Representational_State_Transfer" id="link-id0x1a8a0e38">REST</a>) -- application state transitions via links</li> <li> Structured Data Representation (<a class="auto-href" href="http://dbpedia.org/resource/Linked_Data" id="link-id0x1acf1aa0">Linked Data</a>) -- whole data data representation via links </li> <li> Structured Identity (<a href="http://esw.w3.org/WebID" id="link-id0x1a484548">WebID</a>) -- verifiable distributed identity </li> <li> Structured Profiles (<a class="auto-href" href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id0xa00bca8">FOAF</a>) -- platform independent profiles for people and organizations </li> <li> Articulation of Structured Value Propositions (<a href="http://www.heppnetz.de/projects/goodrelations/" id="link-id0x1a4793d0">GoodRelations</a>) -- Product & Service Offers, Business Entities, Locations, Business Hours, etc. </li> <li> Structured Collaboration Spaces (<a href="http://rdfs.org/sioc/spec/" id="link-id0x1afb8b40">SIOC</a>) -- Blogs, Wikis, File Sharing, Discussion Forums, Aggregated Feeds, Statuses, Photo Galleries, Polls etc.</li> </ol>
Solving Real Problems by Leveraging Linked Data: Unambiguous & Verifiable Identity for HTTP Networks
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2010-07-11#1625
2010-07-12T03:25:03Z
2010-07-12T07:22:02.000018-04:00
<h3>Problem: Unambiguous Verifiable Network Identity.</h3> <p>How Does <a href="http://dbpedia.org/resource/Linked_Data" id="link-id0x1b1ad1d0">Linked Data</a> Address This Problem? It provides critical infrastructure for the WebID Protocol that enables an innovative tweak of SSL/TLS. </p> <p>What about OpenID? The WebID Protocol embraces and extends OpenID (<strong><em>in an open and positive way</em></strong>) via the WebID + OpenID Hybrid variant of the protocol -- basic effect is that OpenID calls are re-routed to the WebID aspect which simply removes Username and Password Authentication from the authentication challenge interaction pattern.</p> <h3>WebID Components</h3> <ol> <li> X.509 Certificate and Private Key Generator </li> <li> Structured Profile Document (e.g. a <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id0x1a301338">FOAF</a> based Profile) published to an HTTP Network (e.g. <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id0x1ba50e10">World Wide Web</a>) and accessible at an Address (<a href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id0x12ded2e0">URL</a>) </li> <li> An Agent Identifier aka. WebID (an HTTP Name Reference re. <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id0x1b197378">URI</a> variant) that's the Subject of a Structured Profile Document (actually a Descriptor Resource)</li> <li> Mechanism for persisting Public Key data from X.509 Certificate to Structured Profile Document and associating it with Subject WebID (e.g. SPARUL or other HTTP based methods) </li> <li> Mechanism for de-referencing Public Key data associated with a WebID (from its Structured Profile Document) for comparison against Public Key data following successful standard SSL/TLS protocol handshake (e.g. via <a href="http://dbpedia.org/resource/SPARQL" id="link-id0x16d26ec8">SPARQL</a> Query). </li> </ol> <h3>Demo</h3> <ul> <li> <a href="http://www.youtube.com/watch?v=mjgXsjd8PDE" id="link-id0x1b9cc4d8">WebID + OpenID Hybrid Protocol Demo using ODS, Stackoverflow.com, and identi.ca.</a> - YouTube Screencast Demo Part 1 using Firefox</li> <li> <a href="http://www.youtube.com/watch?v=eXoxUo7Py4M " id="link-id0x1a2db140">WebID + OpenID Hybrid Protocol Demo using ODS, Stackoverflow.com, and identi.ca.</a> - YouTube Screencast Demo Part 2 using Safari </li> </ul> <h3>Related</h3> <ul> <li> <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=webid&type=text&output=html" id="link-id0x1bc37a58">Prior Posts about WebIDs</a> </li> <li> <a href="http://payswarm.com/webid/drafts/ED-webid-20100711/" id="link-id0x1a0eecb8">Draft WebID Spec</a> </li> </ul>
Data 3.0 (a Manifesto for Platform Agnostic Structured Data) Update 5
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2010-04-16#1624
2010-04-16T21:09:05Z
2010-05-25T17:10:28.000001-04:00
<p>After a long period of trying to demystify and unravel the wonders of standards compliant structured <a href="http://dbpedia.org/resource/Data">data</a> access, combined with protocols (e.g., HTTP) that separate: </p> <ol> <li>Identity,</li> <li>Access,</li> <li>Storage,</li> <li>Representation, and</li> <li>Presentation.</li> </ol> <p>I ended up with what I can best describe as the Data 3.0 Manifesto. A manifesto for standards complaint access to structured data object (or <a href="http://dbpedia.org/resource/Entity" id="link-id0x1a0bc238">entity</a>) descriptors.</p> <h3>Some Related Work</h3> <p> <a href="http://blogs.msdn.com/alexj/" id="link-id0x1a3c5b70">Alex James</a> (Program Manager <a href="http://blogs.msdn.com/efdesign/" id="link-id0x1a3c5bd8">Entity Frameworks</a> at Microsoft), put together something quite similar to this via his Base4 <a href="http://dbpedia.org/resource/Blog" id="link-id0x13c374c8">blog</a> (around the <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> 2.0 bootstrap time), sadly -- quoting Alex -- that post has gone where discontinued blogs and their host platforms go (deep deep irony here). </p> <p>It's also important to note that this manifesto is also a variant of the <a href="http://www.w3.org/People/Berners-Lee/card#i" id="link-id0x1a29f338">TimBL</a>'s <a href="http://www.w3.org/DesignIssues/LinkedData.html" id="link-id0x1a4e8580">Linked Data Design Issues</a> <a href="http://dbpedia.org/resource/Meme" id="link-id0x199efc30">meme</a> re. Linked Data, but totally decoupled from RDF (data representation formats aspect) and <a href="http://dbpedia.org/resource/SPARQL" id="link-id0x199efc58">SPARQL</a> which -- in my world view -- remain implementation details.</p> <h3>Data 3.0 manifesto</h3> <ul> <li>An "Entity" is the "Referent" of an "Identifier."</li> <li>An "Identifier" SHOULD provide a global, unambiguous, and unchanging (though it MAY be opaque!) "Name" for its "Referent".</li> <li>A "Referent" MAY have many "Identifiers" (Names), but each "Identifier" MUST have only one "Referent".</li> <li>Structured Entity Descriptions SHOULD be based on the <a href="http://dbpedia.org/resource/Entity-attribute-value_model" id="link-id0x1a2a15c0">Entity-Attribute-Value (EAV) Data Model</a>, and SHOULD therefore take the form of one or more 3-tuples (triples), each comprised of: <ul> <li>an "Identifier" that names an "Entity" (i.e., Entity Name),</li> <li>an "Identifier" that names an "Attribute" (i.e., Attribute Name), and</li> <li>an "Attribute Value", which may be an "Identifier" or a "Literal".</li> </ul> </li> <li>Structured Descriptions SHOULD be CARRIED by "Descriptor Documents" (i.e., purpose specific documents where Entity Identifiers, Attribute Identifiers, and Attribute Values are clearly discernible by the document's intended consumers, e.g., humans or machines).</li> <li>Structured Descriptor Documents can contain (carry) several Structured Entity Descriptions</li> <li>Stuctured Descriptor Documents SHOULD be network accessible via network addresses (e.g., HTTP URLs when dealing with HTTP-based Networks).</li> <li>An Identifier SHOULD resolve (de-reference) to a Structured Representation of the Referent's Structured Description.</li> </ul> <h3>Related</h3> <ul> <li> <a href="http://twitpic.com/1g02q8/full" id="link-id0x1a3d1428">Referent, Identifier, and Descriptor/Sense (The Data Perception Trinity)</a> illustration</li> <li> <a href="http://twitpic.com/1g03vo/full" id="link-id0x1a353a20">Referent, Identifier, and Descriptor/Sense Trinity</a> (as exploited in <a href="http://esw.w3.org/Foaf%2Bssl" id="link-id0x135ed828">FOAF+SSL</a> based Secure WebIDs) illustration</li> <li> <a href="http://www.slideshare.net/kidehen/understanding-linked-data-via-eav-model-based-structured-descriptions" id="link-id0x1961ae30">Demystifying Linked Data via EAV Model based Structured Descriptions</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1388" id="link-id0x1a28db38">What do people have against URIs and URLs?</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1567" id="link-id0x1a4cedc8">The URI, URL, and Linked Data Meme's Generic HTTP URI</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1543" id="link-id0x19ac04c8">Simple Explanation of RDF and Linked Data Dynamics</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1547" id="link-id0x13c24748">Linked Data and Identity</a> </li> <li> <a href="http://esw.w3.org/Foaf%2Bssl/FAQ" id="link-id0x199ef720">FOAF+SSL FAQ</a> </li> <li> <a href="http://lists.w3.org/Archives/Public/public-lod/2010Apr/0278.html" id="link-id0x1a361640">LOD Community Thread</a> (showing evolution of this manifesto based on feedback from members such as <a href="http://richard.cyganiak.de/foaf.rdf#cygri" id="link-id0x1a361668">Richard Cyganiak</a>).</li> <li> <a href="http://code.google.com/apis/base/starting-out.html#terms" id="link-id0x18e0b578">Googlebase Data API Docs</a> </li> <li> <a href="http://code.google.com/apis/gdata/docs/2.0/basics.html" id="link-id0x199c77b0">Google Data Protocol</a> (GData)</li> <li> <a href="http://odata.org" id="link-id0x19d1e578">Microsoft's OData Protocol</a> </li> <li> <a href="http://www.youtube.com/watch?v=6pmWojisM_E" id="link-id0x1a40a998">Magic of De-referencable Names and actual Data via Binky Video</a> </li> <li> <a href="http://www.slideshare.net/jyri/building-sites-around-social-objects-web-20-expo-sf-2009" id="link-id0x19ad7e70">Social Objects Presentation</a> (aka. Social Linked Data Objects) - by <a href="http://www.slideshare.net/jyri" id="link-id0x19e71700">Jyri Engeström</a> </li> <li> <a href="http://en.wikipedia.org/wiki/Reference_%28computer_science%29" id="link-id0x199c6178">What's a Reference?</a> </li> </ul>
Linked Data & Socially Enhanced Collaboration (Enterprise or Individual) -- Update 1
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2010-03-02#1610
2010-03-02T20:47:54Z
2010-03-03T19:50:37-05:00
<p>Socially enhanced enterprise and invididual collaboration is becoming a focal point for a variety of solutions that offer erswhile distinct content managment features across the realms of Blogging, Wikis, Shared Bookmarks, Discussion Forums etc.. as part of an integrated platform suite. Recently, <a href="http://www.socialtext.com/" id="link-id112be850">Socialtext</a> has caught my attention courtesy of its nice <a href="http://www.socialtext.com/products/socialnetworking.php" id="link-id145d9850">features and benefits page</a> . In addition, I've also found the <a href="http://mike2.openmethodology.org/" id="link-id14103cc8">Mike 2.0 portal</a> immensely interesting and valuable, for those with an enterprise collaboration bent.</p> <p>Anyway, Socialtext and Mike 2.0 (they aren't identical and juxtaposition isn't seeking to imply this) provide nice demonstrations of socially enhanced collaboration for individuals and/or enterprises is all about:</p> <ol> <li>Identifying Yourself</li> <li>Identifying Others (key contributors, peers, collaborators)</li> <li>Serendipitous Discovery of key contributors, peers, and collaborators</li> <li>Serendipitous Discovery by key contributors, peers, and collaborators</li> <li>Develop and sustain relationships via socially enhanced professional network hybrid</li> <li>Utilize your new "trusted network" (which you've personally indexed) when seeking help or propagating a <a href="http://dbpedia.org/resource/Meme" id="link-id13ad00d0">meme</a>.</li> </ol> <p>As is typically the case in this emerging realm, the critical issue of discrete "identifiers" (record keys in sense) for <a href="http://dbpedia.org/resource/Data">data</a> items, data containers, and data creators (individuals and groups) is overlooked albeit unintentionally. </p> <h3>How HTTP based <a href="http://dbpedia.org/resource/Linked_Data" id="link-id112e1ba8">Linked Data</a> Addresses the Identifier Issue</h3> <p>Rather than using platform constrained identifiers such as: </p> <ul> <li>email address (a "mailto" scheme identifier), </li> <li>a dbms user account, </li> <li>application specific account, or</li> <li>OpenID.</li> </ul> <p>It enables you to leverage the platform independence of HTTP scheme Identifiers (Generic URIs) such that Identifiers for: </p> <ol> <li>You, </li> <li>Your Peers, </li> <li>Your Groups, and </li> <li>Your Activity Generated Data, </li> </ol> <p>simply become conduits into a mesh of <a href="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/images/My_Data_Spaces.png" id="link-id13fe1168">HTTP -- referencable and accessible -- Linked Data Objects</a> endowed with High SDQ (Serendipitious Discovery Quotient). For example my <a href="http://kingsley.idehen.name/dataspace/person/kidehen#this" id="link-id13bdcc80">Personal WebID </a>is all anyone needs to know if they want to explore:</p> <ol> <li>My Profile (which includes references to data objects associated with my interests, social-network, calendar, bookmarks etc.)</li> <li>Data generated by my activities across various data spaces (via data objects associated with my online accounts e.g. <a href="http://linkeddata.uriburner.com/about/id/entity/http/feeds.delicious.com/v2/rss/kidehen?count=15" id="link-id141cce38">Del.icio.us</a>, <a href="http://linkeddata.uriburner.com/about/id/entity/http/twitter.com/kidehen" id="link-id11802ce8">Twitter</a>, <a href="http://linkeddata.uriburner.com/about/id/entity/http/www.last.fm/user/kidehen" id="link-id118bf470">Last.FM</a>)</li> <li> <a href="http://uriburner.com/fct/rdfdesc/usage.vsp?g=http%3A%2F%2Fkingsley.idehen.name%2Fdataspace%2Fperson%2Fkidehen%23this&tp=4" id="link-id13c0f528">Linked Data Meshups via URIBurner</a> (or any other <a href="http://virtuoso.openlinksw.com" id="link-id11334f00">Virtuoso</a> instance) that provide an extend view of my profile</li> </ol> <h3>How <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id14324eb0">FOAF</a>+SSL adds Socially aware Security </h3> <p>Even when you reach a point of equilibrium where: your daily activities trigger orchestratestration of CRUD (Create, Read, Update, Delete) operations against Linked Data Objects within your socially enhanced collaboration network, you still have to deal with the thorny issues of security, that includes the following: </p> <ol> <li>Single Sign On, </li> <li>Authentication, and </li> <li>Data Access Policies.</li> </ol> <p>FOAF+SSL, an application of HTTP based Linked Data, enables you to enhance your Personal HTTP scheme based Identifer (or WebID) via the following steps (peformed by a FOAF+SSL compliant platform):</p> <ol> <li>Imprint WebID within a self-signed x.509 based public key (certificate) associated with your private key (generated by FOAF+SSL platform or manually via OpenSSL)</li> <li>Store public key components (modulous and exponent) into your FOAF based profile document which references your Personal HTTP Identifier as its primary topic</li> <li>Leverage HTTP <a href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id141f8b30">URL</a> component of WebID for making public key components (modulous and exponent) available for x.509 certificate based authentication challenges posed by systems secured by FOAF+SSL (directly) or OpenID (indirectly via FOAF+SSL to OpenID proxy services).</li> </ol> <p>Contrary to conventional experiences with all things PKI (Public Key Infrastructure) related, FOAF+SSL compliant platforms typically handle the PKI issues as part of the protocol implementation; thereby protecting you from any administrative tedium without compromising security.</p> <h3>Conclusions</h3> <p>Understanding how new technology innovations address long standing problems, or understanding how new solutions inadvertently fail to address old problems, provides time tested mechanisms for product selection and value proposition comprehension that ultimately save scarce resources such as time and money. </p> <p>If you want to understand real world problem solution #1 with regards to HTTP based Linked Data look no further than the issues of secure, socially aware, and platform independent identifiers for data objects, that build bridges across erstwhile data silos.</p> <p>If you want to cost-effectively experience what I've outlined in this post, take a look at <a href="http://ods.openlinksw.com/wiki/ODS/" id="link-id13c21220">OpenLink Data Spaces</a> (<a href="http://ods.openlinksw.com/wiki/ODS/" id="link-id1422cdd8">ODS</a>) which is a distributed collaboration engine (enterprise of individual) built around the <a href="http://virtuoso.openlinksw.com" id="link-id14211c98">Virtuoso</a> database engines. It simply enhances existing collaboration tools via the following capabilities:</p> <p>Addition of Social Dimensions via HTTP based <a href="http://dbpedia.org/resource/Identity_(object-oriented_programming)" id="link-id116ecd88">Data Object Identifiers</a> for all Data Items (if missing)</p> <ol> <li>Ability to integrate across a myriad of Data Source Types rather than a select few across RDBM Engines, LDAP, <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> Services, and various HTTP accessible Resources (Hypermedia or Non Hypermedia content types)</li> <li>Addition of FOAF+SSL based authentication</li> <li>Addition of FOAF+SSL based Access Control Lists (ACLs) for policy based data access.</li> </ol> <h3>Related:</h3> <ul> <li> <a href="http://ods.openlinksw.com/dataspace/dav/wiki/ODS/GetAPersonalURIIn5MinutesOrLess" id="link-id117b2610">Get Yourself A WebID in 5 Minutes or Less</a> via OpenLink Data Spaces (an application layer built atop Virtuoso)</li> <li> <a href="http://ods.openlinksw.com/dataspace/dav/wiki/ODS/ODSBriefcaseFOAFSSL" id="link-id140311a0">How To Share Resources Securely Using FOAF+SSL</a> </li> <li> <a href="http://www.youtube.com/watch?v=CRbdeNMPCug" id="link-id11ad5448">FOAF+SSL & WebID Demonstration</a> </li> <li> <a href="http://www.slideshare.net/kidehen/linked-data-spaces-data-portability-access" id="link-id141f43a8">OpenLink Data Spaces & Data Portability</a>.</li> </ul>
5 Game Changing Things about the OpenLink Virtuoso + AWS Cloud Combo
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2010-01-31#1590
2010-01-31T22:29:34Z
2010-02-01T08:59:36-05:00
<p> Here are 5 powerful benefits you can immediately derive from the combination of <a href="http://virtuoso.openlinksw.com" id="link-id17eb8988">Virtuoso</a> and Amazon's AWS services (specifically the EC2 and EBS components): <br /> </p> <ol> <li> Acquire your own personal or service specific <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id1423e520">data space</a> in the Cloud. Think DBase, Paradox, FoxPRO, Access of yore, but with the power of <a href="http://dbpedia.org/resource/Oracle_Database" id="link-id136c6290">Oracle</a>, <a href="http://dbpedia.org/resource/IBM_Informix" id="link-id11b269b8">Informix</a>, <a href="http://dbpedia.org/resource/Microsoft_SQL_Server" id="link-id138084b8">Microsoft SQL Server</a> etc.. using a Conceptual, as opposed to solely Logical, model based DBMS (i.e., a Hybrid DBMS Engine for: <a href="http://dbpedia.org/resource/SQL" id="link-id132a7938">SQL</a>, RDF, XML, and Full Text) </li> <li> Ability to share and control access to your resources using innovations like <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id17ee9d28">FOAF</a>+SSL, OpenID, and OAuth, all from one place </li> <li> Construction of personal or organization based FOAF profiles in a matter of minutes; by simply creating a basic DBMS (or <a href="http://dbpedia.org/resource/OpenLink_Data_Spaces" id="link-id14784ae0">ODS</a> application layer) account; and then using this profile to create strong links (references) to all your Data silos (esp. those from the <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> 2.0 realm) </li> <li> Load data sets from the <a href="http://community.linkeddata.org/dataspace/organization/lod#this" id="link-id17e6ac98">LOD</a> cloud or Sponge existing Web resources (i.e., on the fly data transformation to RDF model based <a href="http://dbpedia.org/resource/Linked_Data" id="link-id17e65d38">Linked Data</a>) and then use the combination to build powerful lookup services that enrich the value of URLs (think: Web addressable reports holding query results) that you publish </li> <li> Bind all of the above to a domain that you own (e.g. a .Name domain) so that you have an attribution-friendly "authority" component for resource URLs and <a href="http://dbpedia.org/resource/Entity" id="link-id118a08d8">Entity</a> URIs published from your Personal Linked Data Space on the Web (or private HTTP network). </li> </ol> <p> In a nutshell, the AWS Cloud infrastructure simplifies the process of generating Federated presence on the <a href="http://dbpedia.org/resource/Internet" id="link-id1380af38">Internet</a> and/or <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id11633b10">World Wide Web</a>. Remember, centralized networking models always end up creating data silos, in some <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id142006f0">context</a>, ultimately! :-) </p>
One Technology That Will Rock 2010 (Update 1)
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2010-01-02#1601
2010-01-02T17:30:38Z
2010-02-01T09:02:41-05:00
<p>Thanks to the <a href="http://www.techcrunch.com/" id="link-id114eb070">TechCrunch</a> post titled: <a href="http://www.techcrunch.com/2010/01/01/ten-technologies-2010/" id="link-id1146e550">Ten Technologies That Will Rock 2010</a>, I've been able to quickly construct a derivative post that condenses the ten item list down to a Single Technology That Will Rock 2010 :-)</p> <p>Sticking with the TechCrunch layout, here is why all roads simply lead to <a href="http://dbpedia.org/resource/Linked_Data" id="link-id11141d50">Linked Data</a> come 2010 and beyond: </p> <ol> <li> <strong>The Tablet: </strong>a new form factor addition re. <a href="http://dbpedia.org/resource/Internet" id="link-id13f09418">Internet</a> and <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> application hosts which is just another way of saying: Linked Data will be accessible from Tablet applications.</li> <li> <strong>Geo:</strong> GPS chips are now standard features of mobile phones, so <a href="http://www.techcrunch.com/2009/12/23/location-2010/" id="link-id112cfdd0">geolocation</a> is increasingly becoming a necessary feature for any killer app. Thus, GeoSpatial Linked Data and GeopSpatial Queries are going to be a critical success factor for any endeavor that seeks to engage mobile applications developers and ultimately their end-users. Basiacally, you want to be able to perform Esoteric Search from these devices of the form: Find Vendors of a Camcorder (e.g., with a Zoom Factor: Weight Ratio of X) within a 2km Radius of my current location. Or how many items from my WishList are available from a Vendor within a 2km radius of my current location. Conversely, provide Vendors with the ability to spot potential Customers within a 2km of a given "clicks & mortar" location (e.g. BestBuy store).</li> <li> <strong>Realtime Search: </strong>Rich Structured Profiles that leverage standards such as <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id140ece38">FOAF</a> and <a href="http://blogs.sun.com/bblfish/entry/foaf_ssl_creating_a_global" id="link-id11856318">FOAF+SSL</a> will enable Highly Personalized Realtime Search (HPRS) without compromisng privacy. Tecnically, this is about <a href="http://esw.w3.org/topic/WebID" id="link-id13ec6260">WebID</a>s securely bound to X.509 Certificates, providing access to verifiable and highly navigable Personal Profile <a href="http://dbpedia.org/resource/Data">Data</a> Spaces that also double as personal search index entry points.</li> <li> <strong>Chrome OS: </strong>Just another operating system for exploiting the burgeoning Web of Linked Data</li> <li> <strong>HTML5: </strong>Courtesy of <a href="http://dbpedia.org/resource/RDFa" id="link-id115b08f0">RDFa</a>, just another mechanism for exposing Linked Data by making HTML+RDFa a bona fide markup for <a href="http://dbpedia.org/resource/Metadata" id="link-id1195b070">metadata</a> (i.e., format for describing real world objects via their attribute-value graphs)</li> <li> <strong>Mobile Video:</strong> Simplifies the production and sharing of Video annotations (comments, reviews etc.) en route to creating rich Linked Discourse Data Spaces.</li> <li> <strong>Augmented Reality:</strong> Ditto</li> <li> <strong>Mobile Transactions:</strong> As per points 1&2 above, Vendor Discovery and Transaction Conusmation will increasingly be driven by high SDQ applications. The "Funnel Effect" (more choices based on individual preferences) will be a critical success factor for any one operating in the Mobile Transaction realm. Note, without Linked Data you cannot deliver scalable solutions that handle the combined requirements of: SDQ, "Funnel Effect", and Mobile Device form factor, will simply maginify the importance of Web accessible Linked Data.</li> <li> <strong>Android:</strong> An additional platform for items 1-8; basically, 2010 isn't going to be an iPhone only zone. Personally, this reminds <a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id111ab5e8">me</a> of a battle from the past i.e., Microsoft vs Apple, re. desktop computing dominance. Google has studied history very well :-)</li> <li> <strong>Social CRM:</strong> this is simply about applying points 1-9 alongide the construction of Linked Data from eCRM Data Spaces.</li> </ol> <p>As I've stated in the past (across a variety of mediums), you cannot build applications that have long term value without addressing the following issues:</p> <ol> <li>Data Item or Object Identity</li> <li>Data Structure -- Data Models</li> <li>Data Representation -- Data Model <a href="http://dbpedia.org/resource/Entity" id="link-id1148eaf8">Entity</a> & Relationships Representation mechanism (as delivered by metadata oriented markup)</li> <li>Data Storage -- Database Management Systems</li> <li>Data Access -- Data Access Protocols </li> <li>Data Presentation -- How you present Views and Reports from Structured Data Sources</li> <li>Data Security -- Data Access Policies</li> </ol> <p>The items above basically showcase the very essence of the HTTP <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id1239af68">URI</a> abstraction that drives HTTP based Linked Data; which is also the basic payload unit that underlies <a href="http://dbpedia.org/resource/Representational_State_Transfer" id="link-id11489a98">REST</a>.</p> <h3>Conclusion</h3> <p>I simply hope that the next decade marks a period of broad appreciation and comprehension of Data Access, Integration, and Management issues on the parts of: application developers, integrators, analysts, end-users, and decision makers. Remember, without structured Data we cannot produce or share <a href="http://dbpedia.org/resource/Information" id="link-id13cb5040">Information</a>, and without Information, we cannot produce of share <a href="http://dbpedia.org/resource/Knowledge" id="link-id647abb0">Knowledge</a>.</p> <h3>Related</h3> <ul> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1567" id="link-id13fa3a20">HTTP URI Abstraction and Linked Data</a> </li> <li> <a href="http://www.dataflux.com/dfblog/?p=1458," id="link-id138f3ea8">First Law of Data Quality</a> </li> <li> <a href="http://walkingoncoals.blogspot.com/2009/12/whos-data-is-it-part-1.html" id="link-id13efccb8">Who's Data Is It?</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1442" id="link-id1355df68">Serendipitous Discovery Quotient</a> (SDQ)</li> <li> <a href="http://www.seangolliher.com/2009/linked-data/serendipitous-discovery-quotient-sdq-the-future-of-seo-or-an-abstract-concept/" id="link-id11217cb8">SDQ: The Future of SEO or an Abstract Concept?</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/oerling/weblog/Orri%20Erling%27s%20Blog/1587" id="link-id139cfbe0">SPARQL & GeoSpatial Indexing</a> (implications of <a href="http://dbpedia.org/resource/SPARQL" id="link-id13f51b78">SPARQL</a>-GEO)</li> <li> <a href="http://blog.jonudell.net/2009/09/09/talking-with-kingsley-idehen-about-mastering-your-own-search-index/" id="link-id13c5c248">Mastering Your Own Search Index</a> </li> <li> <a href="http://blog.jonudell.net/2009/11/23/talking-with-martin-hepp-about-solving-the-paradox-of-choice/" id="link-id135ba4d0">Solving the Paradox of Choice</a>.</li> </ul>
Exploring the Value Proposition of Linked Data
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2009-07-23#1565
2009-07-24T00:17:19Z
2009-07-24T08:20:01-04:00
<h3>What is <a href="http://dbpedia.org/resource/Linked_Data" id="link-id138c9aa8">Linked Data</a>?</h3> <p> The primary topic of a <a href="http://dbpedia.org/resource/Meme" id="link-id12f86100">meme</a> penned by <a href="http://www.w3.org/People/Berners-Lee/card#i" id="link-id115b4c98">TimBL</a> in the form of a <a href="http://www.w3.org/DesignIssues/LinkedData.html" id="link-id1333f300">Design Issues Doc</a> (note: this is how TimBL has shared his thoughts since the <a href="http://www.w3.org/DesignIssues/" id="link-id1128a1d0">Beginning of the Web</a>). </p> <p> There are a number of dimensions to the meme, but its primary purpose is the reintroduction of the HTTP <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id13c43cb8">URI</a> -- a vital component of the Web's core architecture. </p> <h3> What's Special about HTTP URIs?</h3> <p> They possess an intrinsic duality that combines persistent and unambiguous <a href="http://dbpedia.org/resource/Data">Data</a> Identity with platform & representation format independent Data Access. Thus, you can use a string of characters that look like a contemporary Web <a href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id119cd8a0">URL</a> to unambiguously achieve the following: </p> <ol> <li>Identity or Name Anything of Interest</li> <li>Describe Anything of Interest by associating the Description Subject's Identity with a constellation of Attribute and Value pairs (technically: an <a href="http://dbpedia.org/resource/Entity-attribute-value_model" id="link-id1133e8a8">Entity</a>-Attribute-Value or Subject-Predicate-Object graph)</li> <li>Make the Description of Named Things of Interest discoverable on the Web by implicitly binding the aforementioned to Documents that hold their descriptions (technically: metadata documents or <a href="http://dbpedia.org/resource/Information" id="link-id1391da40">information</a> resources)</li> </ol> <h3>What's the basic value proposition of the <a href="http://www.w3.org/DesignIssues/LinkedData.html" id="link-id113bb690">Linked Data meme</a>?</h3> <p>Enabling more productive use of the Web by users and developers alike. All of which is achieved by tweaking the Web's Hyperlinking feature such that it now includes Hypertext and <a href="http://dbpedia.org/resource/Linked_Data" id="link-id1337a3f0">Hyperdata</a> as link types.</p> <p>Note: Hyperdata Linking is simply what an HTTP URI facilitates.</p> <p>Examples problems solved by injecting Linked Data into the Web:</p> <ol> <li>Federated Identity by enabling Individuals to unambiguously Identify themselves (Profiles++) courtesy of existing <a href="http://dbpedia.org/resource/Internet" id="link-id13926e28">Internet</a> and Web protocols (e.g., <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id13646ec8">FOAF</a>+SSL's WebIDs which combine Personal Identity with X.509 certificates and HTTPs based client side certification)</li> <li>Security and Privacy challenge alleviation by delivering a mechanism for policy based data access that feeds off federated individual identity and social network (graph) traversal</li> <li>Spam Busting via the above</li>. <li> Increasing the Serendipitous Discovery Quotient (SDQ) of Web accessible resources by embedding Rich Metadata into (X)HTML Documents e.g., structured descriptions of your "WishLists" and "OfferLists" via a common set of terms offered by vocabularies such as <a href="http://www.heppnetz.de/projects/goodrelations/" id="link-id1199b4d0">GoodRelations</a> and <a href="http://dbpedia.org/resource/SIOC" id="link-id1334cfb0">SIOC</a> </li> <li>Coherent integration of disparate data across the Web and/or within the Enterprise via "Data Meshing" rather than "Data Mashing"</li> <li>Moving beyond imprecise statistically driven "Keyword Search" (e.g. Page Rank) to "Precision Find" driven by typed link based <a href="http://dbpedia.org/resource/Entity" id="link-id135f6fe8">Entity</a> Rank plus Entity Type and Entity Property filters.</li> </ol> <h3>Conclusion</h3> <p>If all of the above still falls into the technical mumbo-jumbo realm, then simply consider Linked Data as delivering Open Data Access in granular form to Web accessible data -- that goes beyond data containers (documents or files).</p> <p>The value proposition of Linked Data is inextricably linked to the value proposition of the <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id1356f5c0">World Wide Web</a>. This is true, because the Linked Data meme is ultimately about an enhancement of the current Web; achieved by reintroducing its architectural essence -- in new <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id11300828">context</a> -- via a new level of link abstraction, courtesy of the Identity and Access duality of HTTP URIs.</p> <p>As a result of Linked Data, you can now have Links on the Web for a Person, Document, Music, Consumer Electronics, Products & Services, Business Opening & Closing Hours, Personal "WishLists" and "OfferList", an Idea, etc.. in addition to links for Properties (Attributes & Values) of the aforementioned. Ultimately, all of these links will be indexed in a myriad of ways providing the substrate for the next major period of Internet & Web driven innovation, within our larger human-ingenuity driven innovation continuum.</p> <h3>Related</h3> <ul> <li> <a href="http://www.ebusiness-unibw.org/wiki/GoodRelations#Recipes_and_Examples" id="link-id11386648">Recipes for Describing Your Business and its Offerings using the GoodRelations Vocabulary / Schema</a> </li> <li> <a href="http://slidesix.com/view/SolvingRealProblemsUsingLinkedData" id="link-id13658ee0">Solving Real Problems with RDF based Linked Data</a> </li> <li> <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=linked%20data&type=text&output=html" id="link-id1175a650">Other Linked Data Posts from this Blog oriented Linked Data Space</a> (goes back a few years!)</li> <li>Various practical <a href="http://delicious.com/kidehen/linked_data_demo" id="link-id13390cf8">Linked Data demo links from my Del.icio.us Bookmark oriented Data Space</a> </li> <li> <a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id132cda80">My personal WebID</a> which is conduit to a Linked Data mesh covering vast variety of things I've opted to share with others via the Web (best viewed using a Linked Data aware User Agent like ODE).</li> </ul>
Take N: Yet Another OpenLink Data Spaces Introduction
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2009-04-22#1542
2009-04-22T18:46:18Z
2009-04-22T15:32:06.000020-04:00
<h3>Problem:</h3> <p>Your Life, Profession, <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a>, and <a href="http://dbpedia.org/resource/Internet" id="link-id0x1c6687f8">Internet</a> do not need to become mutually exclusive due to "<a href="http://dbpedia.org/resource/Information" id="link-id0x1c6696e8">information</a> overload".</p> <h3>Solution:</h3> <p> A platform or service that delivers a point of online presence that embodies the fundamental separation of: Identity, <a href="http://dbpedia.org/resource/Data">Data</a> Access, Data Representation, Data Presentation, by adhering to Web and Internet protocols.</p> <h3>How:</h3> <p> Typical post installation (Local or Cloud) task sequence:</p> <ol> <li> Identify myself (happens automatically by way of registration)</li> <li>If in an LDAP environment, import accounts or associate system with LDAP for account lookup and authentication</li> <li> Identify Online Accounts (by fleshing out profile) which also connects system to online accounts and their data</li> <li>Use Profile for granular description (Biography, Interests, WishList, OfferList, etc.)</li> <li>Optionally upstream or downstream data to and from my online accounts</li> <li>Create content Tagging Rules</li> <li>Create rules for associating Tags with formal URIs</li> <li>Create automatic Hyperlinking Rules for reuse when new content is created (e.g. <a href="http://dbpedia.org/resource/Blog" id="link-id11a7c660">Blog</a> posts)</li> <li>Exploit Data Portability virtues of RSS, Atom, OPML, <a href="http://dbpedia.org/resource/RDFa" id="link-id13f54d50">RDFa</a>, RDF/XML, and other formats for imports and exports</li> <li>Automatically <a href="http://dbpedia.org/resource/Tag" id="link-id121ddff0">tag</a> imported content</li> <li>Use function-specific helper application UIs for domain specific data generation e.g. AddressBook (optionally use vCard import), Calendar (optionally use iCalendar import), Email, File Storage (use WebDAV mount with copy and paste or HTTP GET), Feed Subscriptions (optionally import RSS/Atom/OPML feeds), Bookmarking (optionally import bookmark.html or XBEL) etc..</li> <li>Optionally enable "Conversation" feature (today: Social Media feature) across the relevant application domains (manage conversations under covers using NNTP, the standard for this functionality realm) </li> <li>Generate HTTP based <a href="http://dbpedia.org/resource/Entity" id="link-id13d5d378">Entity</a> IDs (URIs) for every piece of data in this burgeoning <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id11a69670">data space</a> </li> <li>Use REST based APIs to perform CRUD tasks against my data (local and remote) (<a href="http://dbpedia.org/resource/SPARQL" id="link-id11a76e10">SPARQL</a>, GData, Ubiquity Commands, Atom Publishing)</li> <li>Use OpenID, OAuth, <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id11c9b3e0">FOAF</a>+SSL, FOAF+SSL+OpenID for accessing data elsewhere</li> <li>Use OpenID, OAuth, FOAF+SSL, FOAF+SSL+OpenID for Controlling access to my data (Self Signed Certificate Generation, Browser Import of said Certificate & associated Private Key, plus persistence of Certificate to FOAF based profile data space in "one click")</li> <li>Have a simple UI for <a href="http://dbpedia.org/resource/Entity-attribute-value_model" id="link-id14015bd0">Entity</a>-Attribute-Value or Subject-Predicate-Object arbitrary data annotations and creation since you can't pre model an "<a href="http://dbpedia.org/resource/Open_world_assumption" id="link-id11cd8548">Open World</a>" where the only constant is data flow</li> <li>Have my Personal <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id142beee8">URI</a> (Web ID) as the single entry point for controlled access to my HTTP accessible data space</li> </ol> <p> I've just outlined a snippet of the capabilities of the <a href="http://dbpedia.org/resource/OpenLink_Data_Spaces" id="link-id13d64740">OpenLink Data Spaces</a> platform. A platform built using OpenLink <a href="http://virtuoso.openlinksw.com" id="link-id13d74170">Virtuoso</a>, architected to deliver: open, platform independent, multi-model, data access and data management across heterogeneous data sources. </p> <p> All you need to remember is your URI when seeking to interact with your data space.</p> <h3>Related</h3> <ol> <li> <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/GetAPersonalURIIn5MinutesOrLess" id="link-id13c97948">Get Yourself a URI (Web ID) in 5 Minutes or Less!</a> </li> <li> <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=%22data%20spaces%22&type=text&output=html" id="link-id1431e088">Various posts over the years about Data Spaces</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1415" id="link-id11f837f0">Future of Desktop Post</a> </li> <li> <a href="http://bnode.org/blog/2009/04/22/semantic-web-apps-to-simplify-my-life" id="link-id1393f8a8">Simplify My Life Post</a> by <a href="http://bnode.org/about" id="link-id11da0cc8">Bengee Nowack</a> </li> </ol>
Simple Compare & Contrast of Web 1.0, 2.0, and 3.0 (Update 1)
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2009-03-14#1531
2009-03-14T18:20:00Z
2009-04-29T13:21:25.000004-04:00
<p>Here is a tabulated "compare and contrast" of <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> usage patterns 1.0, 2.0, and 3.0.</p> <table border="1" width="715" height="286"> <tbody> <tr> <td>Â </td> <td><strong>Web 1.0</strong></td> <td><strong>Web 2.0</strong></td> <td><strong>Web 3.0</strong></td> </tr> <tr> <td><strong>Simple Definition</strong></td> <td>Interactive / Visual Web</td> <td>Programmable Web</td> <td><a href="http://dbpedia.org/resource/Linked_Data" id="link-id117a9a98">Linked Data</a> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id146bcdb0">Web</a></td> </tr> <tr> <td><strong>Unit of Presence</strong></td> <td>Web Page</td> <td>Web Service Endpoint</td> <td><a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id11a66c60">Data Space</a> (named structured data enclave)</td> </tr> <tr> <td><strong>Unit of Value Exchange</strong></td> <td>Page <a href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id146083f8">URL</a></td> <td>Endpoint URL for API</td> <td>Resource / <a href="http://dbpedia.org/resource/Entity" id="link-id121b2148">Entity</a> / Object <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id1467ed00">URI</a></td> </tr> <tr> <td><strong>Data Granularity</strong></td> <td>Low (HTML)</td> <td>Medium (XML)</td> <td>High (RDF)</td> </tr> <tr> <td><strong>Defining Services</strong></td> <td>Search </td> <td>Community (Blogs to Social Networks) </td> <td>Find</td> </tr> <tr> <td><strong>Participation Quotient</strong></td> <td>Low</td> <td>Medium</td> <td>High</td> </tr> <tr> <td><strong>Serendipitous Discovery Quotient </strong></td> <td>Low</td> <td>Medium</td> <td>High</td> </tr> <tr> <td><strong>Data Referencability Quotient </strong></td> <td>Low (Documents)</td> <td>Medium (Documents)</td> <td>High (Documents and their constituent Data)</td> </tr> <tr> <td><strong>Subjectivity Quotient</strong></td> <td>High</td> <td>Medium (from A-list bloggers to select source and partner lists)</td> <td>Low (everything is discovered via URIs)</td> </tr> <tr> <td> <strong><a href="http://dbpedia.org/resource/Transclusion" id="link-id155308d8">Transclusence</a> </strong></td> <td>Low</td> <td>Medium (Code driven Mashups)</td> <td>HIgh (Data driven Meshups)</td> </tr> <tr> <td><strong>What You See Is What You Prefer (WYSIWYP)</strong></td> <td>Low</td> <td>Medium </td> <td>High (negotiated representation of resource descriptions)</td> </tr> <tr> <td><strong>Open Data Access (Data Accessibility)</strong></td> <td>Low</td> <td>Medium (Silos)</td> <td>High (no Silos)</td> </tr> <tr> <td><strong>Identity Issues Handling</strong></td> <td>Low</td> <td>Medium (<a href="http://dbpedia.org/resource/OpenID" id="link-id119d77f8">OpenID</a>)</td> <td><p>High (<a href="http://esw.w3.org/topic/foaf+ssl" id="link-id135cc348">FOAF+SSL</a>)</p></td> </tr> <tr> <td><strong>Solution Deployment Model</strong></td> <td>Centralized</td> <td>Centralized with sprinklings of Federation</td> <td>Federated with function specific Centralization (e.g. Lookup hubs like <a href="http://community.linkeddata.org/dataspace/organization/lod#this" id="link-id1496d1d0">LOD</a> Cloud or <a href="http://dbpedia.org/resource/DBpedia" id="link-id1571f690">DBpedia</a>)</td> </tr> <tr> <td><strong>Data Model Orientation</strong></td> <td>Logical (Tree based DOM)</td> <td>Logical (Tree based XML)</td> <td>Conceptual (Graph based RDF)</td> </tr> <tr> <td><strong>User Interface Issues</strong></td> <td>Dynamically generated static interfaces</td> <td>Dyanically generated interafaces with semi-dynamic interfaces (courtesy of XSLT or <a href="http://dbpedia.org/resource/XQuery" id="link-id118399e8">XQuery</a>/<a href="http://dbpedia.org/resource/XPath" id="link-id14b00ba0">XPath</a>)</td> <td>Dynamic Interfaces (pre- and post-generation) courtesy of self-describing nature of RDF</td> </tr> <tr> <td><strong>Data Querying</strong></td> <td><a href="http://dbpedia.org/resource/Full_text_search" id="link-id14fdd948">Full Text Search</a></td> <td>Full Text Search</td> <td>Full Text Search + Structured Graph Pattern Query Language (<a href="http://dbpedia.org/resource/SPARQL" id="link-id154a9368">SPARQL</a>)</td> </tr> <tr> <td><strong>What Each Delivers</strong></td> <td>Democratized Publishing</td> <td>Democratized Journalism & Commentary (Citizen Journalists & Commentators)</td> <td>Democratized Analysis (Citizen Data Analysts)</td> </tr> <tr> <td> <strong><a href="http://dbpedia.org/resource/Star_Wars" id="link-id155ce920">Star Wars Edition Analogy</a> </strong></td> <td>Star Wars (original fight for decentralization via rebellion)</td> <td>Empire Strikes Back (centralization and data silos make comeback)</td> <td>Return of the JEDI (<a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1474" id="link-id11706640">FORCE</a> emerges and facilitates decentralization from "Identity" all the way to "Open Data Access" and "Negotiable Descriptive Data Representation")</td> </tr> </tbody> </table> <p>Naturally, I am not expecting everyone to agree with <a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id15be20c0">me</a>. I am simply making my contribution to what will remain facinating discourse for a long time to come :-)</p> <h3>Related</h3> <ul> <li> <a href="http://novaspivack.typepad.com/nova_spivacks_weblog/2007/10/web-30----the-a.html" id="link-id14a9d738">Web 3.0 The Best Official Definition Imaginable</a> -- Nova Spivack's </li> </ul>
Time for RDBMS Primacy Downgrade is Nigh! (No Embedded Images Edition - Update 1)
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2009-01-27#1520
2009-01-27T19:19:44Z
2009-03-17T11:50:58-04:00
<p> As the world works it way through a "once in a generation" economic crisis, the long overdue downgrade of the <a href="http://dbpedia.org/resource/Relational_database_management_system" id="link-id15750540">RDBMS</a>, from its pivotal position at the apex of the <a href="http://dbpedia.org/resource/Data" id="link-id0x24ea3650">data</a> access and data management pyramid is nigh.</p> <h3>What is the Data Access, and Data Management Value Pyramid?</h3> <p> As depicted below, a top-down view of the data access and data management value chain. The term: apex, simply indicates value primacy, which takes the form of a data access API based entry point into a DBMS realm -- aligned to an underlying data model. Examples of data access APIs include: Native Call Level Interfaces (CLIs), <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id11c254c0">ODBC</a>, <a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id149b16a8">JDBC</a>, <a href="http://dbpedia.org/resource/ADO.NET" id="link-id11451eb0">ADO</a>.NET, <a href="http://dbpedia.org/resource/OLE_DB" id="link-id15b02478">OLE-DB</a>, <a href="http://dbpedia.org/resource/XML_for_Analysis" id="link-id1181fa10">XMLA</a>, and <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id0x1f8394a8">Web</a> Services.</p> See: <a href="http://virtuoso.openlinksw.com/images/Agility_Value_Factors_Pyramid.png" id="link-id146cadd8"> AVF Pyramid Diagram.</a> <p> The degree to which ad-hoc views of data managed by a DBMS can be produced and dispatched to relevant data consumers (e.g. people), without compromising concurrency, data durability, and security, collectively determine the "Agility Value Factor" (AVF) of a given DBMS. Remember, agility as the cornerstone of environmental adaptation is as old as the concept of evolution, and intrinsic to all pursuits of primacy. </p> <p>In simpler business oriented terms, look at AVF as the degree to which DBMS technology affects the ability to effectively implement "Market Leadership Discipline" along the following pathways: innovation, operation excellence, or customer intimacy. </p> <h3>Why has RDBMS Primacy has Endured?</h3> <p> Historically, at least since the late '80s, the RDBMS genre of DBMS has consistently offered the highest AVF relative to other DBMS genres en route to primacy within the value pyramid. The desire to improve on paper reports and spreadsheets is basically what DBMS technology has fundamentally addressed to date, even though conceptual level interaction with data has never been its forte.</p> See: <a href="http://virtuoso.openlinksw.com/images/Old_RDBMS_Primacy_Pyramid.png" id="link-id134dab90"> RDBMS Primacy Diagram.</a> <p> For more then 10 years -- at the very least -- limitations of the traditional RDBMS in the realm of conceptual level interaction with data across diverse data sources and schemas (enterprise, Web, and <a href="http://dbpedia.org/resource/Internet" id="link-id116001c0">Internet</a>) has been crystal clear to many RDBMS technology practitioners, as indicated by some of the quotes excerpted below:</p> <blockquote> <cite> <p> "Future of Database Research is excellent, but what is the future of data?" </p> "..it is hard for <a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id14932398">me</a> to disagree with the conclusions in this report. It captures exactly the right thoughts, and should be a must read for everyone involved in the area of databases and database research in particular." <p>-- <a href="http://jhingran.typepad.com/anant_jhingrans_musings/" id="link-id11334c50">Dr. Anant Jingran</a>, CTO, IBM <a href="http://dbpedia.org/resource/Information" id="link-id150c7970">Information</a> Management Systems, commenting on the <a href="http://db.cs.berkeley.edu/claremont/" id="link-id11c3b408">2007 RDBMS technology retreat</a> attended by a number of key DBMS technology pioneers and researchers.</p> </cite> </blockquote> <blockquote> <cite> <p> "<a href="http://www.databasecolumn.com/2007/09/one-size-fits-all.html" id="link-id15c14f08">One size fits all: A concept whose time has come and gone</a> </p> <p> </p> <ol> <li> They are direct descendants of System R and <a href="http://dbpedia.org/resource/Ingres" id="link-id146da780">Ingres</a> and were architected more than 25 years ago</li> <li> They are advocating "one size fits all"; i.e. a single engine that solves all DBMS needs. </li> </ol> <p>-- Prof. <a href="http://en.wikipedia.org/wiki/Michael_Stonebraker" id="link-id145c4e28">Michael Stonebreaker</a>, one of the founding fathers of the RDBMS industry.</p> </cite> </blockquote> <p>Until this point in time, the requisite confluence of "circumstantial pain" and "open standards" based technology required to enable an objective "compare and contrast" of RDBMS engine virtues and viable alternatives hasn't occurred. Thus, the RDBMS has endured it position of primacy albeit on a "one size fits all basis". </p> <h4>Circumstantial Pain</h4> <p> As mentioned earlier, we are in the midst of an economic crisis that is ultimately about a consistent inability to connect dots across a substrate of interlinked data sources that transcend traditional data access boundaries with high doses of schematic heterogeneity. Ironically, in a era of the dot-com, we haven't been able to make meaningful connections between relevant "real-world things" that extend beyond primitive data hosted database tables and content management style document containers; we've struggled to achieve this in the most basic sense, let alone evolve our ability to connect inline with the <a href="http://www.vldb2007.org/program/slides/s1161-brodie.pdf" id="link-id11a0dcf0">exponential rate at which the Internet & Web are spawning "universes of discourse" (data spaces) that emanate from user activity</a> (within the enterprise and across the Internet & Web). In a nutshell, we haven't been able to upgrade our interaction with data such that "conceptual models" and resulting "<a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id12da4b00">context</a> lenses" (or facets) become concrete; by this I mean: real-world <a href="http://dbpedia.org/resource/Entity" id="link-id146a48a8">entity</a> interaction making its way into the computer realm as opposed to the impedance we all suffer today when we transition from conceptual model interaction (real-world) to logical model interaction (when dealing with RDBMS based data access and data management). </p> <p>Here are some simple examples of what I can only best describe as: "critical dots unconnected", resulting from an inability to interact with data conceptually:</p> <strong>Government (Globally) -</strong> <p> Financial regulatory bodies couldn't effectively discern that a <a href="http://dbpedia.org/resource/Credit_default_swap" id="link-id115ba0e0">Credit Default Swap</a> is an Insurance policy in all but literal name. And in not doing so the cost of an unregulated <a href="http://dbpedia.org/resource/Insurance" id="link-id158d4960">insurance policy</a> laid the foundation for exacerbating the toxicity of fatally flawed mortgage backed securities. Put simply: a flawed insurance policy was the fallback on a toxic security that financiers found exotic based on superficial packaging.</p> <strong>Enterprises - </strong> <p> Banks still don't understand that capital really does exists in tangible and intangible forms; with the intangible being the variant that is inherently dynamic. For example, a tech companies intellectual capital far exceeds the value of fixture, fittings, and buildings, but you be amazed to find that in most cases this vital asset has not significant value when banks get down to the nitty gritty of debt collateral; instead, a buffer of flawed securitization has occurred atop a borderline static asset class covering the aforementioned buildings, fixtures, and fittings. </p> <p> In the general enterprise arena, IT executives continued to "rip and replace" existing technology without ever effectively addressing the timeless inability to connect data across disparate data silos generated by internal enterprise applications, let alone the broader need to mesh data from the inside with external data sources. No correlations made between the growth of buzzwords and the compounding nature of data integration challenges. It's 2009 and only a miniscule number of executives dare fantasize about being anywhere within distance of the: relevant information at your fingertips vision. </p> <p> Looking more holistically at data interaction in general, whether you interact with data in the enterprise space (i.e., at work) or on the Internet or Web, you ultimately are delving into a mishmash of disparate computer systems, applications, service (Web or SOA), and databases (of the RDBMS variety in a majority of cases) associated with a plethora of disparate schemas. Yes, but even today "rip and replace" is still the norm pushed by most vendors; pitting one mono culture against another as exemplified by irrelevances such as: FOSS/LAMP vs Commercial or Web vs. Enterprise, when none of this matters if the data access and integration issues are recognized let alone addressed (see: <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1497?sid=0df0294caee8b37925c6a888bbbca136&realm=wa" id="link-id15c27300">Applications are Like Fish and Data Like Wine</a>). </p> <p> Like the current credit-crunch, exponential growth of data originating from disparate application databases and associated schemas, within shrinking processing time frames, has triggered a rethinking of what defines data access and data management value today en route to an inevitable RDBMS downgrade within the value pyramid.</p> <h3>Technology</h3> <p>There have been many attempts to address real-world modeling requirements across the broader DBMS community from Object Databases to Object-Relational Databases, and more recently the emergence of simple <a href="http://dbpedia.org/resource/Entity-attribute-value_model" id="link-id1128dad0">Entity</a>-Attribute-Value model DBMS engines. In all cases failure has come down to the existence of one or more of the following deficiencies, across each potential alternative:</p> <ol> <li>Query language standardization - nothing close to <a href="http://dbpedia.org/resource/SQL" id="link-id16002d60">SQL</a> standardization</li> <li>Data Access API standardization - nothing close to ODBC, JDBC, OLE-DB, or ADO.NET</li> <li>Wire protocol standardization - nothing close to HTTP</li> <li>Distributed Identity infrastructure - nothing close to the non-repudiatable digital Identity that <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id14926b18">foaf</a>+ssl accords</li> <li>Use of Identifiers as network based pointers to data sources - nothing close to RDF based <a href="http://dbpedia.org/resource/Linked_Data" id="link-id16180a28">Linked Data</a> </li> <li>Negotiable data representation - nothing close to Mime and HTTP based Content Negotiation</li> <li>Scalability especially in the era of Internet & Web scale.</li> </ol> <h4>Entity-Attribute-Value with Classes & Relationships (<a href="http://dbpedia.org/resource/Entity-attribute-value_model" id="link-id13e741b8">EAV</a>/CR) data models</h4> <p>A common characteristic shared by all post-relational DBMS management systems (from Object Relational to pure Object) is an orientation towards variations of EAV/CR based data models. Unfortunately, all efforts in the EAV/CR realm have typically suffered from at least one of the deficiencies listed above. In addition, the same "one DBMS model fits all" approach that lies at the heart of the RDBMS downgrade also exists in the EAV/CR realm.</p> <h3>What Comes Next?</h3> <p>The RDBMS is not going away (ever), but its era of primacy -- by virtue of its placement at the apex of the data access and data management value pyramid -- is over! I make this bold claim for the following reasons: </p> <ol> <li> The Internet aided "Global Village" has brought "<a href="http://en.wikipedia.org/wiki/Open_World_Assumption" id="link-id1148e560">Open World</a>" vs "<a href="http://en.wikipedia.org/wiki/Closed_World_Assumption" id="link-id11967cd0">Closed World</a>" assumption issues to the fore e.g., the current global economic crisis remains centered on the inability to connect dots across "Open World" and "Closed World" data frontiers </li> <li> Entity-Attribute-Value with Classes & Relationships (EAV/CR) based DBMS models are more effective when dealing with disparate data associated with disparate schemas, across disparate DBMS engines, host operating systems, and networks. </li> </ol> <p>Based on the above, it is crystal clear that a different kind of DBMS -- one with higher AVF relative to the RDBMS -- needs to sit atop today's data access and data management value pyramid. The characteristics of this DBMS must include the following:</p> <ol> <li> Every item of data (Datum/Entity/Object/Resource) has Identity</li> <li> Identity is achieved via Identifiers that aren't locked at the DBMS, OS, Network, or Application levels</li> <li> Object Identifiers and Object values are independent (extricably linked by association)</li> <li> Object values should be de-referencable via Object Identifier</li> <li> Representation of de-referenced value graph (entity, attributes, and values mesh) must be negotiable (i.e. content negotiation)</li> <li>Structured query language must provide mechanism for Creation, Deletion, Updates, and Querying of data objects</li> <li> Performance & Scalability across "Closed World" (enterprise) and "Open World" (Internet & Web) realms.</li> </ol> <p>Quick recap, I am not saying that RDBMS engine technology is dead or obsolete. I am simply stating that the era of RDBMS primacy within the data access and data management value pyramid is over. </p> <p>The problem domain (conceptual model views over heterogeneous data sources) at the apex of the aforementioned pyramid has simply evolved beyond the natural capabilities of the RDBMS which is rooted in "Closed World" assumptions re., data definition, access, and management. The need to maintain domain based conceptual interaction with data is now palpable at every echelon within our "Global Village" - Internet, Web, Enterprise, Government etc.</p> <p>It is my personal view that an EAV/CR model based DBMS, with support for the seven items enumerated above, can trigger the long anticipated RDBMS downgrade. Such a DBMS would be inherently multi-model because you would need to the best of RDBMS and EAV/CR model engines in a single product, with in-built support for HTTP and other Internet protocols in order to effectively address data representation and serialization issues.</p> <h4>EAV/CR Oriented Data Access & Management Technology</h4> <p>Examples of contemporary EAV/CR frameworks that provide concrete conceptual layers for data access and data management currently include:</p> <ul> <li> <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id115d1cb0"> Resource Description Framework</a> (RDF) - an EAV/CR based framework</li> <li> <a href="http://dbpedia.org/resource/Linked_Data" id="link-id116cf810">RDF Linked Data </a>- EAV/CR based framework that mandates de-referencable HTTP based Identifiers</li> <li> <a href="http://dbpedia.org/resource/ADO.NET_Entity_Framework" id="link-id13daa160">ADO.NET Entity Frameworks</a> - Microsoft .NET based EAV/CR framework</li> <li> <a href="http://dbpedia.org/page/Core_Data" id="link-id11111838">Core Data Services </a>- Mac OS X based EAV/CR framework that evolved from NeXT's <a href="http://dbpedia.org/resource/Enterprise_Objects_Framework" id="link-id15c27df0">Enterprise Object Frameworks</a> (EOF).</li> </ul> <p>The frameworks above provide the basis for a revised AVF pyramid, as depicted below, that reflects today's data access and management realities i.e., an Internet & Web driven global village comprised of interlinked distributed data objects, compatible with "Open World" assumptions.</p> See: <a href="http://virtuoso.openlinksw.com/images/New_EAV_RDBMS_Pyramid.png" id="link-id158e0760">New EAV/CR Primacy Diagram.</a> <h3>Related</h3> <ul> <li> <a href="http://dynamicorange.com/2009/01/22/blueblog-how-and-why-glue-is-using-amazon-simpledb-instead-of-a-relational-database/" id="link-id15e07c10">How & Why Glue is Using Amazon SimpleDB</a> </li> <li> <a href="http://www.cs.cmu.edu/afs/cs.cmu.edu/user/clamen/OODBMS/Manifesto/htManifesto/node4.html#SECTION00022000000000000000" id="link-id116cf450">Object Database Manifesto (Identity excerpt)</a> </li> <li> <a href="http://www.unixspace.com/context/databases.html" id="link-id150b2c20">Database Models Overview</a> </li> <li> <a href="http://www.youtube.com/watch?v=WEj9vqVvHPc&feature=related" id="link-id0x1135d978">Ted Nelson Explaining Irregularity and Idiosyncrasy of Data Structures</a> - ZigZag Demo </li> </ul>
The Time for RDBMS Primacy Downgrade is Nigh!
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2009-01-24#1519
2009-01-25T00:04:00Z
2009-06-03T18:09:58.000001-04:00
<p> As the world works it way through a "once in a generation" economic crisis, the long overdue downgrade of the <a href="http://dbpedia.org/resource/Relational_database_management_system" id="link-id15750540">RDBMS</a>, from its pivotal position at the apex of the <a href="http://dbpedia.org/resource/Data" id="link-id0x66a74b8">data</a> access and data management pyramid is nigh.</p> <h3>What is the Data Access, and Data Management Value Pyramid?</h3> <p> As depicted below, a top-down view of the data access and data management value chain. The term: apex, simply indicates value primacy, which takes the form of a data access API based entry point into a DBMS realm -- aligned to an underlying data model. Examples of data access APIs include: Native Call Level Interfaces (CLIs), <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id11c254c0">ODBC</a>, <a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id149b16a8">JDBC</a>, <a href="http://dbpedia.org/resource/ADO.NET" id="link-id11451eb0">ADO</a>.NET, <a href="http://dbpedia.org/resource/OLE_DB" id="link-id15b02478">OLE-DB</a>, <a href="http://dbpedia.org/resource/XML_for_Analysis" id="link-id1181fa10">XMLA</a>, and <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id0x2fef498">Web</a> Services.</p> <div> <img alt="Image" src="http://virtuoso.openlinksw.com/images/Agility_Value_Factors_Pyramid.png" /> </div> <p> The degree to which ad-hoc views of data managed by a DBMS can be produced and dispatched to relevant data consumers (e.g. people), without compromising concurrency, data durability, and security, collectively determine the "Agility Value Factor" (AVF) of a given DBMS. Remember, agility as the cornerstone of environmental adaptation is as old as the concept of evolution, and intrinsic to all pursuits of primacy. </p> <p>In simpler business oriented terms, look at AVF as the degree to which DBMS technology affects the ability to effectively implement "Market Leadership Discipline" along the following pathways: innovation, operation excellence, or customer intimacy. </p> <h3>Why has RDBMS Primacy has Endured?</h3> <p> Historically, at least since the late '80s, the RDBMS genre of DBMS has consistently offered the highest AVF relative to other DBMS genres en route to primacy within the value pyramid. The desire to improve on paper reports and spreadsheets is basically what DBMS technology has fundamentally addressed to date, even though conceptual level interaction with data has never been its forte.</p> <div> <img alt="Image" src="http://virtuoso.openlinksw.com/images/Old_RDBMS_Primacy_Pyramid.png" /> </div> <p> For more then 10 years -- at the very least -- limitations of the traditional RDBMS in the realm of conceptual level interaction with data across diverse data sources and schemas (enterprise, Web, and <a href="http://dbpedia.org/resource/Internet" id="link-id116001c0">Internet</a>) has been crystal clear to many RDBMS technology practitioners, as indicated by some of the quotes excerpted below:</p> <blockquote> <cite> <p> "Future of Database Research is excellent, but what is the future of data?" </p> "..it is hard for <a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id14932398">me</a> to disagree with the conclusions in this report. It captures exactly the right thoughts, and should be a must read for everyone involved in the area of databases and database research in particular." <p>-- <a href="http://jhingran.typepad.com/anant_jhingrans_musings/" id="link-id11334c50">Dr. Anant Jingran</a>, CTO, IBM <a href="http://dbpedia.org/resource/Information" id="link-id150c7970">Information</a> Management Systems, commenting on the <a href="http://db.cs.berkeley.edu/claremont/" id="link-id11c3b408">2007 RDBMS technology retreat</a> attended by a number of key DBMS technology pioneers and researchers.</p> </cite> </blockquote> <blockquote> <cite> <p> "<a href="http://www.databasecolumn.com/2007/09/one-size-fits-all.html" id="link-id15c14f08">One size fits all: A concept whose time has come and gone</a> </p> <p> </p> <ol> <li> They are direct descendants of System R and <a href="http://dbpedia.org/resource/Ingres" id="link-id146da780">Ingres</a> and were architected more than 25 years ago</li> <li> They are advocating "one size fits all"; i.e. a single engine that solves all DBMS needs. </li> </ol> <p>-- Prof. <a href="http://en.wikipedia.org/wiki/Michael_Stonebraker" id="link-id145c4e28">Michael Stonebreaker</a>, one of the founding fathers of the RDBMS industry.</p> </cite> </blockquote> <p>Until this point in time, the requisite confluence of "circumstantial pain" and "open standards" based technology required to enable an objective "compare and contrast" of RDBMS engine virtues and viable alternatives hasn't occurred. Thus, the RDBMS has endured it position of primacy albeit on a "one size fits all basis". </p> <h4>Circumstantial Pain</h4> <p> As mentioned earlier, we are in the midst of an economic crisis that is ultimately about a consistent inability to connect dots across a substrate of interlinked data sources that transcend traditional data access boundaries with high doses of schematic heterogeneity. Ironically, in a era of the dot-com, we haven't been able to make meaningful connections between relevant "real-world things" that extend beyond primitive data hosted database tables and content management style document containers; we've struggled to achieve this in the most basic sense, let alone evolve our ability to connect inline with the <a href="http://www.vldb2007.org/program/slides/s1161-brodie.pdf" id="link-id11a0dcf0">exponential rate at which the Internet & Web are spawning "universes of discourse" (data spaces) that emanate from user activity</a> (within the enterprise and across the Internet & Web). In a nutshell, we haven't been able to upgrade our interaction with data such that "conceptual models" and resulting "<a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id12da4b00">context</a> lenses" (or facets) become concrete; by this I mean: real-world <a href="http://dbpedia.org/resource/Entity" id="link-id146a48a8">entity</a> interaction making its way into the computer realm as opposed to the impedance we all suffer today when we transition from conceptual model interaction (real-world) to logical model interaction (when dealing with RDBMS based data access and data management). </p> <p>Here are some simple examples of what I can only best describe as: "critical dots unconnected", resulting from an inability to interact with data conceptually:</p> <strong>Government (Globally) -</strong> <p> Financial regulatory bodies couldn't effectively discern that a <a href="http://dbpedia.org/resource/Credit_default_swap" id="link-id115ba0e0">Credit Default Swap</a> is an Insurance policy in all but literal name. And in not doing so the cost of an unregulated <a href="http://dbpedia.org/resource/Insurance" id="link-id158d4960">insurance policy</a> laid the foundation for exacerbating the toxicity of fatally flawed mortgage backed securities. Put simply: a flawed insurance policy was the fallback on a toxic security that financiers found exotic based on superficial packaging.</p> <strong>Enterprises - </strong> <p> Banks still don't understand that capital really does exists in tangible and intangible forms; with the intangible being the variant that is inherently dynamic. For example, a tech companies intellectual capital far exceeds the value of fixture, fittings, and buildings, but you be amazed to find that in most cases this vital asset has not significant value when banks get down to the nitty gritty of debt collateral; instead, a buffer of flawed securitization has occurred atop a borderline static asset class covering the aforementioned buildings, fixtures, and fittings. </p> <p> In the general enterprise arena, IT executives continued to "rip and replace" existing technology without ever effectively addressing the timeless inability to connect data across disparate data silos generated by internal enterprise applications, let alone the broader need to mesh data from the inside with external data sources. No correlations made between the growth of buzzwords and the compounding nature of data integration challenges. It's 2009 and only a miniscule number of executives dare fantasize about being anywhere within distance of the: relevant information at your fingertips vision. </p> <p> Looking more holistically at data interaction in general, whether you interact with data in the enterprise space (i.e., at work) or on the Internet or Web, you ultimately are delving into a mishmash of disparate computer systems, applications, service (Web or SOA), and databases (of the RDBMS variety in a majority of cases) associated with a plethora of disparate schemas. Yes, but even today "rip and replace" is still the norm pushed by most vendors; pitting one mono culture against another as exemplified by irrelevances such as: FOSS/LAMP vs Commercial or Web vs. Enterprise, when none of this matters if the data access and integration issues are recognized let alone addressed (see: <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1497?sid=0df0294caee8b37925c6a888bbbca136&realm=wa" id="link-id15c27300">Applications are Like Fish and Data Like Wine</a>). </p> <p> Like the current credit-crunch, exponential growth of data originating from disparate application databases and associated schemas, within shrinking processing time frames, has triggered a rethinking of what defines data access and data management value today en route to an inevitable RDBMS downgrade within the value pyramid.</p> <h3>Technology</h3> <p>There have been many attempts to address real-world modeling requirements across the broader DBMS community from Object Databases to Object-Relational Databases, and more recently the emergence of simple <a href="http://dbpedia.org/resource/Entity-attribute-value_model" id="link-id1128dad0">Entity</a>-Attribute-Value model DBMS engines. In all cases failure has come down to the existence of one or more of the following deficiencies, across each potential alternative:</p> <ol> <li>Query language standardization - nothing close to <a href="http://dbpedia.org/resource/SQL" id="link-id16002d60">SQL</a> standardization</li> <li>Data Access API standardization - nothing close to ODBC, JDBC, OLE-DB, or ADO.NET</li> <li>Wire protocol standardization - nothing close to HTTP</li> <li>Distributed Identity infrastructure - nothing close to the non-repudiatable digital Identity that <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id14926b18">foaf</a>+ssl accords</li> <li>Use of Identifiers as network based pointers to data sources - nothing close to RDF based <a href="http://dbpedia.org/resource/Linked_Data" id="link-id16180a28">Linked Data</a> </li> <li>Negotiable data representation - nothing close to Mime and HTTP based Content Negotiation</li> <li>Scalability especially in the era of Internet & Web scale.</li> </ol> <h4>Entity-Attribute-Value with Classes & Relationships (<a href="http://dbpedia.org/resource/Entity-attribute-value_model" id="link-id13e741b8">EAV</a>/CR) data models</h4> <p>A common characteristic shared by all post-relational DBMS management systems (from Object Relational to pure Object) is an orientation towards variations of EAV/CR based data models. Unfortunately, all efforts in the EAV/CR realm have typically suffered from at least one of the deficiencies listed above. In addition, the same "one DBMS model fits all" approach that lies at the heart of the RDBMS downgrade also exists in the EAV/CR realm.</p> <h3>What Comes Next?</h3> <p>The RDBMS is not going away (ever), but its era of primacy -- by virtue of its placement at the apex of the data access and data management value pyramid -- is over! I make this bold claim for the following reasons: </p> <ol> <li> The Internet aided "Global Village" has brought "<a href="http://en.wikipedia.org/wiki/Open_World_Assumption" id="link-id1148e560">Open World</a>" vs "<a href="http://en.wikipedia.org/wiki/Closed_World_Assumption" id="link-id11967cd0">Closed World</a>" assumption issues to the fore e.g., the current global economic crisis remains centered on the inability to connect dots across "Open World" and "Closed World" data frontiers </li> <li> Entity-Attribute-Value with Classes & Relationships (EAV/CR) based DBMS models are more effective when dealing with disparate data associated with disparate schemas, across disparate DBMS engines, host operating systems, and networks. </li> </ol> <p>Based on the above, it is crystal clear that a different kind of DBMS -- one with higher AVF relative to the RDBMS -- needs to sit atop today's data access and data management value pyramid. The characteristics of this DBMS must include the following:</p> <ol> <li> Every item of data (Datum/Entity/Object/Resource) has Identity</li> <li> Identity is achieved via Identifiers that aren't locked at the DBMS, OS, Network, or Application levels</li> <li> Object Identifiers and Object values are independent (extricably linked by association)</li> <li> Object values should be de-referencable via Object Identifier</li> <li> Representation of de-referenced value graph (entity, attributes, and values mesh) must be negotiable (i.e. content negotiation)</li> <li>Structured query language must provide mechanism for Creation, Deletion, Updates, and Querying of data objects</li> <li> Performance & Scalability across "Closed World" (enterprise) and "Open World" (Internet & Web) realms.</li> </ol> <p>Quick recap, I am not saying that RDBMS engine technology is dead or obsolete. I am simply stating that the era of RDBMS primacy within the data access and data management value pyramid is over. </p> <p>The problem domain (conceptual model views over heterogeneous data sources) at the apex of the aforementioned pyramid has simply evolved beyond the natural capabilities of the RDBMS which is rooted in "Closed World" assumptions re., data definition, access, and management. The need to maintain domain based conceptual interaction with data is now palpable at every echelon within our "Global Village" - Internet, Web, Enterprise, Government etc.</p> <p>It is my personal view that an EAV/CR model based DBMS, with support for the seven items enumerated above, can trigger the long anticipated RDBMS downgrade. Such a DBMS would be inherently multi-model because you would need to the best of RDBMS and EAV/CR model engines in a single product, with in-built support for HTTP and other Internet protocols in order to effectively address data representation and serialization issues.</p> <h4>EAV/CR Oriented Data Access & Management Technology</h4> <p>Examples of contemporary EAV/CR frameworks that provide concrete conceptual layers for data access and data management currently include:</p> <ul> <li> <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id115d1cb0"> Resource Description Framework</a> (RDF) - an EAV/CR based framework</li> <li> <a href="http://dbpedia.org/resource/Linked_Data" id="link-id116cf810">RDF Linked Data </a>- EAV/CR based framework that mandates de-referencable HTTP based Identifiers</li> <li> <a href="http://dbpedia.org/resource/ADO.NET_Entity_Framework" id="link-id13daa160">ADO.NET Entity Frameworks</a> - Microsoft .NET based EAV/CR framework</li> <li> <a href="http://dbpedia.org/page/Core_Data" id="link-id11111838">Core Data Services </a>- Mac OS X based EAV/CR framework that evolved from NeXT's <a href="http://dbpedia.org/resource/Enterprise_Objects_Framework" id="link-id15c27df0">Enterprise Object Frameworks</a> (EOF).</li> </ul> <p>The frameworks above provide the basis for a revised AVF pyramid, as depicted below, that reflects today's data access and management realities i.e., an Internet & Web driven global village comprised of interlinked distributed data objects, compatible with "Open World" assumptions.</p> <div> <image src="http://virtuoso.openlinksw.com/images/New_EAV_RDBMS_Pyramid.png"></image> </div> <h3>Related</h3> <ul> <li> <a href="http://allanslibrary.blogspot.com/2009/06/semantic-way.html" id="link-id0xb8c5e498">The Semantic Way</a> - Alan Cho's Summary of <a href="http://www.pwc.com/extweb/home.nsf/docid/1308AF8EA7929CCA852575BA00720F26" id="link-id0xb80f5e10">PwC 2009 tech forecast report on the Semantic Web</a> </li> <li> <a href="http://www.readwriteweb.com/archives/is_the_relational_database_doomed.php" id="link-id0xb8c20658">Is the RDBMS Doomed</a> - <a href="http://www.readwriteweb.com">ReadWriteWeb</a> Article</li> <li> <a href="http://www.metabrew.com/article/anti-rdbms-a-list-of-distributed-key-value-stores/" id="link-id0x1ab4778">Anti-RDBMS: a list of Distributed Key-Value Stores</a> - by <a href="http://www.last.fm/user/RJ" id="link-id0x5a968060">Richard Jones</a> (CTO Last.FM)</li> <li> <a href="http://dynamicorange.com/2009/01/22/blueblog-how-and-why-glue-is-using-amazon-simpledb-instead-of-a-relational-database/" id="link-id15e07c10">How & Why Glue is Using Amazon SimpleDB</a> </li> <li> <a href="http://www.cs.cmu.edu/afs/cs.cmu.edu/user/clamen/OODBMS/Manifesto/htManifesto/node4.html#SECTION00022000000000000000" id="link-id116cf450">Object Database Manifesto (Identity excerpt)</a> </li> <li> <a href="http://www.unixspace.com/context/databases.html" id="link-id150b2c20">Database Models Overview</a> </li> <li> <a href="http://www.youtube.com/watch?v=WEj9vqVvHPc&feature=related" id="link-id0x66b0850">Ted Nelson Explaining Irregularity and Idiosyncrasy of Data Structures</a> - ZigZag Demo </li> </ul>
A Linked Data Web Approach To Semantic "Search" & "Find" (Updated)
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2009-01-09#1517
2009-01-09T23:34:50Z
2009-01-10T13:55:56.000001-05:00
<p>The first salvo of what we've been hinting about re. server side faceted browsing over Unlimited <a href="http://dbpedia.org/resource/Data">Data</a> within configurable Interactive Time-frames is now available for experimentation at: <a href="http://b3s.openlinksw.com/fct/facet.vsp" id="link-ide41d210">http://b3s.openlinksw.com/fct/facet.vsp</a>.</p> <h3>Simple example / demo:</h3> <p>Enter search pattern: Microsoft</p> <p>You will get the usual result from a full text pattern search i.e., hits and text excerpts with matching patterns in boldface. This first step is akin to throwing your net out to sea while fishing.</p> <p> Now you have your catch, what next? Basically, this is where traditional text search value ends since <a href="http://dbpedia.org/resource/regular_expression" id="link-id113b6840">regex</a> or <a href="http://dbpedia.org/resource/XPath" id="link-id1151c140">xpath</a>/<a href="http://dbpedia.org/resource/XQuery" id="link-id14565db8">xquery</a> offer little when the structure of literal text is the key to filtering or categorization based analysis of real-world entities. Naturally, this is where the value of structured querying of <a href="http://dbpedia.org/resource/Linked_Data" id="link-id11bc8208">linked data</a> starts, as you seek to use <a href="http://dbpedia.org/resource/Entity" id="link-id150e7298">entity</a> descriptions (combination of attribute and relationship properties) to "Find relevant things".</p> <p>Continuing with the demo.</p> <p>Click on "Properties" link within the Navigation section of the browser page which results in a distillation and aggregation of the properties of the entities associated with the search results. Then use the "Next" link to page through the properties until to find the properties that best match what you seek. Note, this particular step is akin to using the properties of the catch (using fishing analogy) for query filtering, with each subsequent property link click narrowing your selection further.</p> <p>Using property based filtering is just one perspective on the data corpus associated with the text search pattern; thus, you can alter perspectives by clicking on the "Class" link so that you can filter you search results by entity type. Of course, in a number of scenarios you would use a combination of entity types and entity properties filters to locate the entities of interest to you. </p> <h3>A Few Notes about this demo instance of <a href="http://virtuoso.openlinksw.com" id="link-id14453088">Virtuoso</a>:</h3> <ul> <li> Lookup Data Size (Local Linked Data Corpus): 2 Billion+ Triples (<a href="http://dbpedia.org/page/Entity-attribute-value_model" id="link-id13447558">entity-attribute-value</a> tuples)</li> <li> This is a *temporary* teaser / precursor to the <a href="http://community.linkeddata.org/dataspace/organization/lod#this" id="link-id14e3bfc8">LOD</a> (Linking Open Data Cloud) variant of our Linked Data driven "Search" & "Find" service; we decided to implement this functionality prior to commissioning a larger and more up to date instance based on the entire LOD Cloud</li> <li> The browser is simply using a <a href="http://virtuoso.openlinksw.com" id="link-id138b5688">Virtuoso</a> PL function that also exists in <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> Service form for loose binding by 3rd parties that have a UI orientation and focus (our UI is deliberately bare boned).</li> <li>The properties and entity types (classes) links expose formal definitions and dictionary provenance <a href="http://dbpedia.org/resource/Information" id="link-id10ecc8e0">information</a> materialized in an HTML page (of course your browser or any other HTTP user agent can negotiation alternative representations of this descriptive information)</li> <li> <a href="http://umbel.org/about/" id="link-id117b95e0">UMBEL</a> based inference rules are enabled, giving you a live and simple demonstration of the virtues of Linked Data Dictionaries for example: click on the description link of any property or class from the <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id1595dd88">foaf</a> (friend-of-a-friend vocabulary), <a href="http://dbpedia.org/resource/SIOC" id="link-id151315e8">sioc</a> (semantically-interlinked-online-communities ontology), <a href="http://musicontology.com/" id="link-id15b9d6e8">mo</a> (music ontology), <a href="http://bibliontology.com/" id="link-id114257e8">bibo</a> (bibliographic data ontology) namespaces to see how the data between these lower level vocabularies or ontologies are meshed with <a href="http://dbpedia.org/resource/Cyc" id="link-id15b9be80">OpenCyc</a>'s upper level ontology. </li> </ul> <h3>Related</h3> <ul> <li> <a href="http://www.openlinksw.com/dataspace/oerling/weblog/Orri%20Erling%27s%20Blog/1515" id="link-id14694eb8">Faceted Search: Unlimited Data in Interactive Time</a> </li> <li> <a href="http://blogs.usnet.private:8893/Virtuoso Anytime: No Query Is Too Complex (updated)" id="link-id1356c630">Virtuoso Anytime: No Query Is Too Complex</a> </li> </ul>
Introducing Virtuoso Universal Server (Cloud Edition) for Amazon EC2
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2008-11-28#1489
2008-11-28T19:27:12Z
2008-11-28T16:06:02.000006-05:00
<h3>What is it?</h3> <p>A pre-installed edition of <a href="http://virtuoso.openlinksw.com" id="link-id14bea838">Virtuoso</a> for Amazon's EC2 Cloud platform.</p> <h3>What does it offer?</h3> From a <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> Entrepreneur perspective it offers: <ol> <li> Low cost entry point to a game-changing Web 3.0+ (and beyond) platform that combines <a href="http://dbpedia.org/resource/SQL" id="link-id11309b38">SQL</a>, <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id135f7988">RDF</a>, XML, and Web Services functionality</li> <li> Flexible variable cost model (courtesy of <a href="http://aws.amazon.com/devpay/" id="link-id17941018">EC2 DevPay</a>) tightly bound to revenue generated by your services</li> <li> Delivers federated and/or centralized model flexibility for you SaaS based solutions</li> <li> Simple entry point for developing and deploying sophisticated database driven applications (SQL or RDF <a href="http://dbpedia.org/resource/Linked_Data" id="link-id14ea6b10">Linked Data Web</a> oriented)</li> <li> Complete framework for exploiting OpenID, OAuth (including Role enhancements) that simplifies exploitation of these vital Identity and <a href="http://dbpedia.org/resource/Data">Data</a> Access technologies</li> <li>Easily implement RDF Linked Data based Mail, Blogging, Wikis, Bookmarks, Calendaring, Discussion Forums, Tagging, Social-Networking as <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id11519928">Data Space</a> (data containers) features of your application or service offering</li> <li>Instant alleviation of challenges (e.g. service costs and agility) associated with <a href="http://dbpedia.org/resource/DataPortability" id="link-id111cb610">Data Portability</a> and Open Data Access across Web 2.0 data silos</li> <li> LDAP integration for <a href="http://dbpedia.org/resource/Intranet" id="link-id114a8270">Intranet</a> / <a href="http://dbpedia.org/resource/Extranet" id="link-id10fe4f08">Extranet</a> style applications.</li> </ol> <p>From the DBMS engine perspective it provides you with one or more pre-configured instances of Virtuoso that enable immediate exploitation of the following services:</p> <ol> <li> RDF Database (a Quad Store with <a href="http://dbpedia.org/resource/SPARQL" id="link-id11911bf8">SPARQL</a> & SPARUL Language & Protocol support)</li> <li> <a href="http://dbpedia.org/resource/SQL" id="link-id110544c8">SQL</a> Database (with <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id1524c7d0">ODBC</a>, <a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id14cfb658">JDBC</a>, OLE-DB, <a href="http://dbpedia.org/resource/ADO.NET" id="link-id110ec6c8">ADO</a>.NET, and XMLA driver access)</li> <li>XML Database (XML Schema, <a href="http://dbpedia.org/resource/XQuery" id="link-id10ebf218">XQuery</a>/<a href="http://dbpedia.org/resource/XPath" id="link-id142a7898">Xpath</a>, XSLT, Full Text Indexing)</li> <li>Full Text Indexing.</li> </ol> <p>From a Middleware perspective it provides:</p> <ol> <li> RDF Views (Wrappers / Semantic Covers) over SQL, XML, and other data sources accessible via SOAP or REST style Web Services</li> <li> Sponger Service for converting non RDF <a href="http://dbpedia.org/resource/Information" id="link-id11931c60">information</a> resources into RDF <a href="http://dbpedia.org/resource/Linked_Data" id="link-id118f7168">Linked Data</a> "on the fly" via a large collection of pre-installed RDFizer Cartridges.</li> </ol> <p>From the Web Server Platform perspective it provides an alternative to LAMP stack components such as <a href="http://dbpedia.org/resource/MySQL" id="link-id10f7b780">MySQL</a> and Apace by offering</p> <ol> <li> HTTP Web Server</li> <li> WebDAV Server</li> <li> Web <a href="http://dbpedia.org/resource/Application_server" id="link-id1268daa8">Application Server</a> (includes <a href="http://dbpedia.org/resource/PHP" id="link-id1585d238">PHP</a> runtime hosting)</li> <li> SOAP or REST style Web Services Deployment</li> <li> RDF Linked Data Deployment</li> <li> SPARQL (SPARQL Query Language) and SPARUL (SPARQL Update Language) endpoints</li> <li>Virtuoso Hosted PHP packages for <a href="http://dbpedia.org/resource/MediaWiki" id="link-id15568818">MediaWiki</a>, <a href="http://dbpedia.org/resource/Drupal" id="link-id110bd7a8">Drupal</a>, <a href="http://dbpedia.org/resource/WordPress" id="link-id10f66918">Wordpress</a>, and <a href="http://dbpedia.org/resource/PhpBB" id="link-id13fda4d0">phpBB3</a> (just install the relevant Virtuoso Distro. Package). </li> </ol> <p>From the general System Administrator's perspective it provides:</p> <ol> <li> Online Backups (Backup Set dispatched to S3 buckets, FTP, or HTTP/WebDAV server locations)</li> <li>Synchronized Incremental Backups to Backup Set locations</li> <li>Backup Restore from Backup Set location (without exiting to EC2 shell).</li> </ol> <p>Higher level user oriented offerings include:</p> <ol> <li>OpenLink Data Explorer front-end for exploring the burgeoning Linked Data <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id11646dc8">Web</a> </li> <li> Ajax based SPARQL Query Builder (iSPARQL) that enables SPARQL Query construction by Example</li> <li>Ajax based SQL Query Builder (QBE) that enables SQL Query construction by Example.</li> </ol> <p>For Web 2.0 / 3.0 users, developers, and entrepreneurs it offers it includes Distributed Collaboration Tools & Social Media realm functionality courtesy of <a href="http://dbpedia.org/resource/OpenLink_Data_Spaces" id="link-id11009930">ODS</a> that includes:</p> <ol> <li> Point of presence on the Linked Data Web that meshes your Identity and your Data via URIs</li> <li> System generated Social Network Profile & Contact Data via <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id1185a1c0">FOAF</a>?</li> <li> System generated <a href="http://dbpedia.org/resource/SIOC" id="link-id14791890">SIOC</a> (Semantically Interconnected Online Community) <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id1577cad8">Data Space</a> (that includes a Social Graph) exposing all your Web data in RDF Linked Data form</li> <li> System generated OpenID and automatic integration with FOAF</li> <li> Transparent Data Integration across Facebook, Digg, LinkedIn, FriendFeed, Twitter, and any other Web 2.0 data space equipped with RSS / Atom support and/or REST style Web Services</li> <li> In-built support for SyncML which enables data synchronization with Mobile Phones.</li> </ol> <h3>How Do I Get Going with It?</h3> <ul> <li> <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/ODSInstallationEC2" id="link-id114e1600">Standard Installation Guide</a> </li> <li> <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtEC2AMIDBpediaInstall" id="link-id110a98e8">Personal or Service Specific DBpedia Installation Guide</a> </li> </ul>
Where Are All the RDF-based Semantic Web Applications?
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2008-10-01#1447
2008-10-01T23:09:00Z
2008-10-02T15:27:41-04:00
<p> In response to the "<a href="http://dbpedia.org/resource/Semantic_Web" id="link-id15971040">Semantic Web</a> Technology" application classification scheme espoused by <a href="http://www.readwriteweb.com" id="link-id16391540">ReadWriteWeb</a> (RWW), emphasized in the post titled: <a href="http://www.readwriteweb.com/archives/rdf_semantic_web_apps.php" id="link-id1157eaa0">Where are all the RDF-based Semantic Web Apps?</a>, here is my attempt to clarify and reintroduce what <a href="http://www.openlinksw.com/dataspace/organization/openlink#this" id="link-id15a43758">OpenLink Software</a> offers (today) in relation to Semantic Web technology. </p> <p> From the RWW Top-Down category, which I interpret as: technologies that produce RDF from non RDF <a href="http://dbpedia.org/resource/Data">data</a> sources. Our product portfolio is comprised of the following; <a href="http://virtuoso.openlinksw.com" id="link-id14f05818">Virtuoso Universal Server</a>, <a href="http://dbpedia.org/resource/OpenLink_Data_Spaces" id="link-id162c8630">OpenLink Data Spaces</a>, <a href="http://oat.openlinksw.com" id="link-id134e1a00">OpenLink Ajax Toolkit</a>, and <a href="http://ode.openlinksw.com" id="link-id160b3bf8">OpenLink Data Explorer</a> (which includes ubiquity commands).</p> <h3>Virtuoso Universal Server functionality summary:</h3> <ol> <li>Generation of RDF <a href="http://dbpedia.org/resource/Linked_Data" id="link-id161d5f50">Linked Data</a> Views of <a href="http://dbpedia.org/resource/SQL" id="link-id161d5978">SQL</a>, XML, and <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> Services in general </li> <li>Deployment of RDF Linked Data </li> <li>"On the Fly" generation of RDF Linked Data from Document Web <a href="http://www.w3.org/TR/webarch/" id="link-id178bbc08">information resources</a> (i.e. distillation of entities from their containers e.g. Web pages) via Cartridges / Drivers</li> <li> <a href="http://dbpedia.org/resource/SPARQL" id="link-id162c2118">SPARQL</a> query language support </li> <li>SPARQL extensions that bring SPARQL closer to SQL e.g Aggregates, Update, Insert, Delete Named Graph support (i.e. use of logical names to partition RDF data within Virtuoso's multi-model dbms engine) </li> <li>Inference Engine (currently in use re. <a href="http://dbpedia.org/resource/DBpedia" id="link-id14f563c0">DBpedia</a> via Yago and <a href="http://umbel.org/about/" id="link-id113273b8">UMBEL</a>)</li> <li>Host and exposes data from <a href="http://dbpedia.org/resource/Drupal" id="link-id123d3bd8">Drupal</a>, <a href="http://dbpedia.org/resource/WordPress" id="link-id141adf40">Wordpress</a>, <a href="http://dbpedia.org/resource/MediaWiki" id="link-id1604b450">MediaWiki</a>, <a href="http://dbpedia.org/resource/PhpBB" id="link-id141013a8">phpBB3</a> as RDF Linked Data via in-built support for <a href="http://dbpedia.org/resource/PHP" id="link-id14661e58">PHP</a> runtime</li> <li> <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/ODSInstallationEC2" id="link-id146c84d0">Available as an EC2 AMI</a> </li> <li>etc..</li> </ol> <h3>OpenLink Data Spaces functionality summary:</h3> <ol> <li>Simple mechanism for Linked Data <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id15473770">Web</a> enabling yourself by giving you an <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/GetAPersonalURIIn5MinutesOrLess" id="link-id15f6d278">HTTP based User ID</a> (a de-referencable <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id15aaeb68">URI</a>) that is linked to a <a href="http://myopenlink.net/dataspace/person/kidehen" id="link-id15a7a840">FOAF based Profile page</a> and OpenID</li> <li>Binds all your data sources (blogs, wikis, bookmarks, photos, calendar items etc. ) to your URI so can "Find" things by only remembering your URI</li> <li>Makes your profile page and personal URI the focal point of Linked Data Web presence</li> <li>Delivers Data Portability (using data access by value or <a href="http://dbpedia.org/resource/Reference_(computer_science)" id="link-id16212838">data access by reference</a>) across data silos (e.g. Web 2.0 style social networks)</li> <li>Allows you make annotations about anything in your own <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id14668010">Data Space</a>(s) on the Web without exposure to RDF markup</li> <li>A Briefcase feature that provides a WebDAV driven RDF Linked Data variant of functionality seen in Mac OS X Spotlight and WinFS with the addition of SPARQL compliance</li> <li>Automatically generates <a href="http://dbpedia.org/resource/RDFa" id="link-id14691440">RDFa</a> in its (X)HTML pages</li> <li> <a href="http://dbpedia.org/resource/Blog" id="link-id14fae7b8">Blog</a>, Wiki, WebDAV File Server, Shared Bookmarks, Calendar, and other applications that look and feel like Web 2.0 counterparts but emitt RDF Linked Data amongst a plethora of data exchange formats</li> <li>Available as an EC2 AMI</li> <li>etc..</li> </ol> <h3>OpenLink Ajax Toolkit functionality summary:</h3> <ol> <li>Provides binding to SQL, RDF, XML, and Web Services via Ajax Database Connectivity Layer (you only need an <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id11550548">ODBC</a>, <a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id13ae5f68">JDBC</a>, OLE-DB, <a href="http://dbpedia.org/resource/ADO.NET" id="link-id162803e8">ADO</a>.NET, XMLA Driver, or Web Service on the backend for dynamic data access from Javascript)</li> <li>All controls are Ajax Database Connectivity bound (widgets get their data from Ajax Database Connectivity data sources)</li> <li>Bundled with Virtuoso and <a href="http://dbpedia.org/resource/OpenLink_Data_Spaces" id="link-id161dfe90">ODS</a> installations.</li> <li>etc.</li> </ol> <h3>OpenLink Data Explorer functionality summary</h3> <ol> <li>Distills entities associated with information resource style containers (e.g. Web Pages or files) as RDF Linked Data</li> <li>Exposes the RDF based <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id12a42ed8">Linked Data graph</a> associated with information resources (see the Linked Data behind Web pages)</li> <li>Ubiquity commands for invoking the above</li> <li>Available as a <a href="http://linkeddata.uriburner.com/ode" id="link-id15a0d2b0">Hosted Service</a> or <a href="http://ode.openlinksw.com" id="link-id138b9fa8">Firefox Extension</a> </li> <li>Bundled with Virtuoso and ODS installations</li> <li>etc.</li> </ol> <h3>Note:</h3> <p>Of course you could have simply looked up <a href="http://www.openlinksw.com/dataspace/organization/openlink" id="link-id14ef2c10">OpenLink Software's FOAF based Profile page</a> (*note the Linked Data Explorer tab*), or simply passed the <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id14cbf5c8">FOAF</a> profile page <a href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id16453e28">URL</a> to a Linked Data aware client application such as: <a href="http://linkeddata.uriburner.com/ode" id="link-id15a80500">OpenLink Data Explorer</a>, <a href="http://zitgist.com/about/" id="link-id1586a360">Zitgist</a> <a href="http://dataviewer.zitgist.com" id="link-id16249f60">Data Viewer</a>, <a href="http://beckr.org/marbles" id="link-id15993fb0">Marbles</a>, and <a href="http://dig.csail.mit.edu/2005/ajar/release/tabulator/0.8/tab.html" id="link-id14d63048">Tabulator</a>, and obtained information. Remember, <a href="http://www.openlinksw.com/dataspace/organization/openlink#this" id="link-id138ba838">OpenLink Software</a> is an <a href="http://dbpedia.org/resource/Entity" id="link-id1173e120">Entity</a> of Type: <a href="http://xmlns.com/foaf/0.1/Organization" id="link-id138b87b8">foaf:Organization</a>, on the burgeoning Linked Data Web :-)</p> <h3>Related</h3> <ul> <li> <a href="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Creating_Deploying_Exploiting_Linked_Data2_TimBL_v3.html" id="link-id163a0c88">Linked Data Planet Keynote</a> (RDFa based remix edition)</li> <li> <a href="http://semanticbusiness.blogspot.com/2008/09/report-on-cusp-global-review-of.html" id="link-id11471a40">On The Cusp: A Global Review of the Semantic Web Industry.</a> </li> </ul>
Business Value of Linked Data (Enterprise Angle)?
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2008-09-11#1437
2008-09-11T18:59:24Z
2008-09-11T15:52:48.000050-04:00
<p>All enterprises run IS/MIS/EIS systems that are supposed to enable optimized exploitation of <a href="http://dbpedia.org/resource/Data">data</a>, <a href="http://dbpedia.org/resource/Information" id="link-id1408bee8">information</a>, and <a href="http://dbpedia.org/resource/Knowledge" id="link-id14c429a8">knowledge</a>. Unfortunately, applications, services (SOAP or REST), database engines, middleware, operating systems, programming languages, development frameworks, network protocols, network topologies, or some other piece of infrastructure, eventually lay claim (possessively) to the data.</p> <p>Courtesy of <a href="http://dbpedia.org/resource/Linked_Data" id="link-id10f98db8">Linked Data</a>, we are now able to extend the "document to document" linking mechanism of the <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> (Hypertext Linking) to more granular "<a href="http://dbpedia.org/resource/Entity" id="link-id14410810">entity</a> to <a href="http://dbpedia.org/resource/Entity" id="link-id10dbb420">entity</a>" level linking. And in doing so, we have a layer of abstraction that in one swoop alleviates all of the infrastructure oriented data access impediments of yore. I know this sounds simplistic, but be rest assured, imbibing <a href="http://dbpedia.org/resource/Linked_Data" id="link-id14b6af20">Linked Data</a>'s value proposition is really just that simple, once you engage solutions (e.g. <a href="http://virtuoso.openlinksw.com" id="link-id14ce6a20">Virtuoso</a>) that enable you to deploy <a href="http://dbpedia.org/resource/Linked_Data" id="link-id1151c718">Linked Data</a> across your enterprise.</p> <h3>Example: </h3> <p>Microsoft ACCESS, <a href="http://dbpedia.org/resource/SQL" id="link-id14ef3b08">SQL</a> Server, and <a href="http://virtuoso.openlinksw.com" id="link-id10d865b8">Virtuoso</a> all use the Northwind <a href="http://dbpedia.org/resource/SQL" id="link-id10b04250">SQL</a> DB Schema as the basis of the demonstration database shipped with each DBMS product. This schema is comprised of common IS/MIS entities that include: Customers, Contacts, Orders, Products, Employees etc.</p> <p>What we all really want to do as data, <a href="http://dbpedia.org/resource/Information" id="link-id110dd7a0">information</a>, and <a href="http://dbpedia.org/resource/Knowledge" id="link-id11484408">knowledge</a> consumers and/or dispatchers, is be no more than a single "mouse click" away from relevant data/<a href="http://dbpedia.org/resource/Information" id="link-id10c755c8">information</a>/<a href="http://dbpedia.org/resource/Knowledge" id="link-id1464ac88">knowledge</a> data access and/or exploration. Even better (but not always so obvious), we also want anyone in our network (company, division, department, cube-cluster) to inherit these data access efficiencies.</p> <p>In this example, the <a href="http://demo.openlinksw.com/Northwind/Customer/ALFKI" id="link-id14ab8ed0">Web Page about the Customer "ALKI"</a> provides <a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id14bdb360">me</a> with a myriad of exploration and data access paths e.g., when I click on the <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id10c388e0">foaf</a>:primarytopic property value link.</p> <p>This simple example, via a single Web Page, should put to rest any doubts about the utility of <a href="http://dbpedia.org/resource/Linked_Data" id="link-id0xb042fd8">Linked Data</a>. Of course this is <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=alfki&type=text&output=html" id="link-id10ccccf0">an old demo</a>, but this time around the UI is minimalist as my prior attempts skipped a few steps i.e., starting from within a <a href="http://ode.openlinksw.com" id="link-id10f8a530">Linked Data explorer/browser</a>.</p> <p>Important note: I haven't exported <a href="http://dbpedia.org/resource/SQL" id="link-id0x16dfc2a0">SQL</a> into an RDF data warehouse, I am converting the SQL into RDF <a href="http://dbpedia.org/resource/Linked_Data">Linked Data</a> on the fly which has two fundamental benefits:</p> <ol> <li>No vulnerability to changes in the source DBMS</li> <li>Superior performance over the RDF warehouse since the source schema is SQL based and I can leverage the optimization of the underlying SQL engine when translating between <a href="http://dbpedia.org/resource/SPARQL" id="link-id0xd9a4030">SPARQL</a> and SQL.</li> </ol> <p>Enjoy!</p> <h3>Related</h3> <ol> <li> <a href="http://www.openlinksw.com/dataspace/oerling/weblog/Orri%20Erling%27s%20Blog/1434" id="link-id11338a48">Requirements for Relational to RDF Mapping</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/oerling/weblog/Orri%20Erling%27s%20Blog/1433" id="link-id10d84278">Handling Graph Transitivity in a SQL/RDF Hybrid Engine</a> </li> <li> <a href="http://www.openlinksw.com/dataspace/oerling/weblog/Orri%20Erling%27s%20Blog/1431" id="link-id10c762e8">How Virtuoso handles the Web Aspects of Linked Data Queries</a>.</li> </ol>
Response to: Whole Data Post (Update 3)
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2008-08-15#1413
2008-08-15T13:06:12Z
2008-08-15T18:31:48-04:00
<p>This post is in response to <a href="http://www.furia.com" id="link-id107907b8">Glenn McDonald</a>'s post titled: <a href="http://www.furia.com/page.cgi?type=log&id=308" id="link-id13dcf2d0">Whole Data</a>, where he highlights a number of issues relating to "<a href="http://dbpedia.org/resource/Semantic_Web" id="link-id1016c1f0">Semantic Web</a>" marketing communications and overall messaging, from his perspective.</p> <p> By coincidence, Glenn and I presented at this month's Cambridge <a href="http://dbpedia.org/resource/Semantic_Web" id="link-idd526f48">Semantic Web</a> Gathering.</p> <p>I've provided a dump of Glenn's issues and my responses below:</p> <h3>Issue - RDF</h3> <ul> <li>Ingenious <a href="http://dbpedia.org/resource/Data">data</a> decomposition idea, but: </li> <li>too low-level; the assembly language of data, where we need Java or <a href="http://dbpedia.org/resource/Ruby_programming_language" id="link-id103f3dd0">Ruby</a> </li> <li>"resource" is not the issue; there's no such thing as "metadata", it's all data; "meta" is a perspective </li> <li>lists need to be effortless, not painful and obscure </li> <li>nodes need to be represented, not just implied; they need types and literals in a more pervasive, integrated way. </li> </ul> <h4>Response:</h4> <p>RDF is a Graph based Data Model it stands for Resource Description Framework. The Metadata data angle comes from it's <a href="http://dbpedia.org/resource/Meta_Content_Framework" id="link-id1690df60">Meta Content Framework (MCF)</a> origins. You can express and serialize data based on the RDF Data Model using: Turtle, N3, TriX, N-Triples, and RDF/XML.</p> <h3>Issue - <a href="http://dbpedia.org/resource/SPARQL" id="link-id10234b38">SPARQL</a> (and Freebase's MQL)</h3> <p>These are just appeasement: <br />- old query paradigm: fishing in dark water with superstitiously tied lures; only works well in carefully stocked lakes <br />- we don't ask questions by defining answer shapes and then hoping they're dredged up whole.</p> <h4>Response:</h4> <p> <a href="http://dbpedia.org/resource/SPARQL" id="link-id16e45e50">SPARQL</a>, <a href="http://www.freebase.com/view/freebase/api" id="link-id13e7d468">MQL</a>, and <a href="http://msdn.microsoft.com/en-us/library/bb387145.aspx" id="link-id1516fbd8">Entity-SQL</a> are Graph Model oriented Query Languages. Query Languages always accompany Database Engines. <a href="http://dbpedia.org/resource/SQL" id="link-id13f8c100">SQL</a> is the Relational Model equivalent. </p> <h3>Issue - <a href="http://dbpedia.org/resource/Linked_Data" id="link-id171dee68">Linked Data</a> </h3> <p>Noble attempt to ground the abstract, but: <br />- <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id1576d5f8">URI</a> dereferencing/namespace/<a href="http://dbpedia.org/resource/Open_world_assumption" id="link-id15f50180">open-world</a> issues focus too much technical attention on cross-source cases where the human issues dwarf the technical ones anyway <br />- <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id105df458">FOAF</a> query over the people in this room? forget it. <br />- link asymmetry doesn't scale <br />- identity doesn't scale <br />- generating RDF from non-graph sources: more appeasement, right where the win from actually converting could be biggest! </p> <h4>Response:</h4> <p>Innovative use of HTTP to deliver "<a href="http://dbpedia.org/resource/Reference_%28computer_science%29" id="link-id13eeab20">Data Access by Reference</a>" to the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id13492610">Linked Data</a> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id105dfc10">Web</a>.</p> <p>When you have a Data Model, Database Engine, and Query Language, the next thing you need is a Data Access mechanism that provides "<a href="http://dbpedia.org/resource/Reference_(computer_science)" id="link-id100ef2c0">Data Access by Reference</a>". <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id16692e88">ODBC</a> and <a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id1699b970">JDBC</a> (amongst others) provide "<a href="http://dbpedia.org/resource/Reference_(computer_science)" id="link-id16034b48">Data Access by Reference</a>" via Data Source Names. <a href="http://dbpedia.org/resource/Linked_Data" id="link-id16690118">Linked Data</a> is about the same thing (URIs are Data Source Names) with the following differences:</p> <ul> <li>Naming is scoped to the <a href="http://dbpedia.org/resource/Entity" id="link-id1195dc48">entity</a> level rather than container level</li> <li>HTTP's use within the data source naming scheme expands the referencability of the Named <a href="http://dbpedia.org/resource/Entity" id="link-id10485760">Entity</a> Descriptions beyond traditional confines such as applications, operating systems, and database engines. </li> </ul> <h3> Issue - <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id104684d0">Giant Global Graph</a> </h3> <p>Hugely motivating and powerful idea, worthy of a superhero (Graphius!), but: <br />- giant and global parts are too hard, and starting global makes every problem harder <br />- local projects become unmanageable in global <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id12497088">context</a> (Cyc, Freebase data-modeling lists...). And my thus my plea, again. Forget "semantic" and "<a href="http://dbpedia.org/resource/World_Wide_Web">web</a>", let's fix the database tech first: <br />- node/arc data-model, path-based exploratory query-model <br />- data-graph applications built easily on top of this common model; building them has to be easy, because if it's hard, they'll be bad <br />- given good database tech, good web data-publishing tech will be trivial! <br />- given good tools for graphs, the problems of uniting them will be only as hard as they have to be.</p> <h4>Response:</h4> <p> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id144466d8">Giant Global Graph</a> is just another moniker for a "Web of <a href="http://dbpedia.org/resource/Linked_Data" id="link-id15c2c738">Linked Data</a>" or "<a href="http://dbpedia.org/resource/Linked_Data" id="link-id14e73520">Linked Data</a> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id10aef200">Web</a>".</p> <p>Multi-Model Database technology that meshes the best of the Graph & Relational Models exist. In a nutshell, this is what <a href="http://virtuoso.openlinksw.com" id="link-id13492e10">Virtuoso</a> is all about and it's existed for a very long time :-)</p> <p> <a href="http://virtuoso.openlinksw.com" id="link-id105a4f58">Virtuoso</a> is also a Virtual DBMS engine (so you can see Heterogeneous Relational Data via Graph Model <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id15845110">Context</a> Lenses). Naturally, it is also a <a href="http://dbpedia.org/resource/Linked_Data" id="link-id109e2c78">Linked Data</a> Deployment platform (or <a href="http://dbpedia.org/resource/Linked_Data" id="link-id1086d650">Linked Data</a> Sever). </p> <p>The issue isn't the "<a href="http://dbpedia.org/resource/Semantic_Web" id="link-id107f1ba8">Semantic Web</a>" moniker per se., it's about how <a href="http://dbpedia.org/resource/Linked_Data" id="link-id0xba72818">Linked Data</a> (foundation layer of <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id101dbf50">Semantic Web</a>) gets introduced to users. As I said during the MIT Gathering: "The Web is experienced via Web Browsers primarily, so any enhancement to the Web must be exposed via traditional Web Browsers", which is why we've opted to simply add "View <a href="http://dbpedia.org/resource/Linked_Data">Linked Data</a> Sources" to the existing set of common Browser options that includes:</p> <ol> <li>View page in rendered form (default)</li> <li>View page source (i.e., how you see the markup behind the page)</li> </ol> <p>By exposing the Linked Data <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id15a04b70">Web</a> option as described above, you enable the Web user to knowingly transition from the traditional Rendered (X)HTML page view to the Linked Data View (i.e., structured data behind the page). This simple "User Interaction" tweak makes the notion of exploiting a Structured Web becomes somewhat clearer.</p> <p>The Linked Data <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id10a187d0">Web</a> isn't a panacea. It's just an addition to the existing Web that enrichens the things you can do with the Web. It's predominance, like any application feature, will be subject to the degrees to which it delivers tangible value or matrializes internal and external opportunity costs.</p> <p>Note: The Web isn't ubiquitous today becuase all it's users groked HTML Markup. It's ubquitity is a function of opportunity costs: there simply came a point in the Web boostrap when nobody could afford the opportunity costs associated with being off the Web. The same thing will play out with Linked Data and the broader <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id10a97330">Semantic Web</a> vision.</p> <b>Links:</b> <ol> <li> <a href="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Creating_Deploying_Exploiting_Linked_Data2_TimBL_v3.html(15)" id="link-id137fc560">Linked Data Journey part of my Linked Data Planet Presentation Remix</a>(from slides 15 to 22 - which include bits from <a href="http://www.w3.org/People/Berners-Lee/card#i" id="link-id1048a968">TimBL</a>'s presentation)</li> <li> <a href="http://ode.openlinksw.com" id="link-id1667df98">OpenLink Data Explorer</a> </li> <li> <a href="http://ode.openlinksw.com/example.html" id="link-id137ee860">OpenLink Data Explorer Screenshots and examples</a>.</li> </ol>
ODBC & WODBC Comparison
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2008-05-20#1364
2008-05-20T19:37:53Z
2008-05-20T15:46:11-04:00
<p> <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id100eb550">ODBC</a> delivers open <a href="http://dbpedia.org/resource/Data" id="link-idffd2338">data</a> access (by reference) to a broad range of enterprise databases via a '<a href="http://dbpedia.org/resource/C_(programming_language)" id="link-id104fd1d8">C</a>' based API. Thanks to the <a href="http://www.iodbc.org" id="link-id104721b0">iODBC</a> and <a href="http://www.unixodbc.org" id="link-id10954990">unixODBC</a> projects, <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id10494670">ODBC</a> is available across broad range of platforms beyond Windows.</p> <p> <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id0xc900928">ODBC</a> identifies <a href="http://dbpedia.org/resource/Data" id="link-id10f82200">data</a> sources using <a href="http://dbpedia.org/resource/Data" id="link-id0xcaad080">Data</a> Source Names (DSNs). </p> <p> WODBC (<a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> Open Database Connectivity) delivers open <a href="http://dbpedia.org/resource/Data">data</a> access to Web Databases / Data Spaces. The Data Source Naming scheme: <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id1009ce40">URI</a> or IRI, is <a href="http://dbpedia.org/resource/Hypertext_Transfer_Protocol" id="link-id101fc1b0">HTTP</a> based thereby enabling data access by reference via the Web. </p> <p><a href="http://dbpedia.org/resource/Open_Database_Connectivity">ODBC</a> DSNs bind ODBC client applications to Tables, Views, Stored Procedures. </p> <p>WODBC DSNs bind you to a Data <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id10182a88">Space</a> (e.g. my <a href="http://myopenlink.net/dataspace/person/kidehen" id="link-id105a7858">FOAF based Profile Page</a> where you can use the "Explore Data Tab" to look around if you are a human visitor) or a specific <a href="http://dbpedia.org/resource/Entity" id="link-id10bd8578">Entity</a> within a Data <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id10780dc0">Space</a> (i.e <a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id10848e08">Person Entity Me</a>).</p> <p>ODBC Drivers are built using APIs (DBMS Call Level Interfaces) provided by DBMS vendors. Thus, a DBMS vendor can chose not to release an API, or do so selectivity, for competitive advantage or market disruption purposes (it's happened!).</p> <p>WODBC Drivers are also built using APIs (Web Services associated with a Web Data <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id0xcbe6348">Space</a>). These drivers are also referred to as <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=rdf%20middleware&type=text&output=html" id="link-id16564058">RDF Middleware</a> or RDFizers. The "Web" component of WODBC ensures openness, you publish Data with URIs from your <a href="http://dbpedia.org/resource/Linked_Data" id="link-id1064a768">Linked Data</a> Server and that's it; your data <a href="http://en.wikipedia.org/wiki/Data_Spaces">space</a> or specific data entities are live and accessible (by reference) over the Web!</p> <p>So we have come full circle (or cycle), the Web is becoming more of a structured database everyday! What's new is old, and what's old is new! </p> <p>Data Access is everything, without "Data" there is no <a href="http://dbpedia.org/resource/Information" id="link-id100a9de8">information</a> or <a href="http://dbpedia.org/resource/Knowledge" id="link-id10bb67e8">knowledge</a>. Without "Data" there's not notion of vitality, purpose, or value.</p> <p>URIs make or break everything in the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id10a71638">Linked Data</a> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id10494400">Web</a> just as ODBC DSNs do within the enterprise. </p> <p>I've deliberately left <a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id10a05280">JDBC</a>, <a href="http://dbpedia.org/resource/ADO.NET" id="link-id104e4a70">ADO</a>.<a href="http://dbpedia.org/resource/ADO.NET" id="link-id10215668">NET</a>, and OLE-DB out of this piece due to their respective programming languages and frameworks specificity. None of these mechanisms match the platform availability breadth of ODBC.</p> <p>The Web as a true <a href="http://dbpedia.org/resource/Model-view-controller" id="link-id108ee598">M</a>-<a href="http://dbpedia.org/resource/Model-view-controller" id="link-id0xcda5e90">V</a>-C pattern is now crystalizing. The "M" (Model) component of M-V-C is finally rising to the realm of broad attention courtesy of the "<a href="http://www.w3.org/DesignIssues/LinkedData.html" id="link-id1024ff08">Linked Data" meme</a> and "<a href="http://dbpedia.org/resource/Semantic_Web" id="link-id1831b418">Semantic Web</a>" vision.</p> <p>By the way, M-V-C lines up nicely with Web 1.0 (Web Forms / Pages), Web 2.0 (Web Services based APIs), and Web 3.0 (Data Web, Web of Data, or <a href="http://dbpedia.org/resource/Linked_Data" id="link-id0xb6d0e90">Linked Data</a> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id0xb22a158">Web</a>) :-)</p>
Commercializing the Semantic Web
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2008-05-16#1362
2008-05-16T20:02:45Z
2008-05-16T16:15:29.000001-04:00
<p>Unfortunately, I could only spend 4 days at the recent <a href="http://www2008.org/" id="link-id196acf60">WWW2008</a> event in <a href="http://dbpedia.org/resource/Beijing" id="link-id1974fe28">Beijing</a> (I departed the morning following the <a href="http://events.linkeddata.org/ldow2008/" id="link-id1863f858">Linked Data Workshop</a>), so I couldn't take my slot on the "Commercializing the <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id18990f90">Semantic Web</a> panel" etc.. Anyway, thanks to the <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> I can still inject my points of view in the broad Web based discourse. Well so I hoped, when I attempted to post a comment to Paul Miller's ZDNet domain hosted <a href="http://dbpedia.org/resource/Blog" id="link-id180d6750">blog</a> thread titled: <a href="http://blogs.zdnet.com/semantic-web/?p=132" id="link-id12d206c0">Commercialising the Semantic Web</a>.</p> <p>Unfortunately, the cost of completing ZDNet's unwieldy signup process simply exceeded the benefits of dropping my comments in their particular space :-( Thus, I'll settle for a trackback ping instead.</p> <p>What follows is the cut and paste of my intended comment contributions to Paul's post.</p> <p>Paul,</p> <p> As discussed earlier this week during <a href="http://blogs.talis.com/nodalities/2008/05/kingsley-idehen-talks-about-openlink-software-linked-data-and-the-semantic-web.php" id="link-id1332fb48">our podcast session</a>, commercialization of <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id17382338">Semantic Web</a> technology shouldn't be a mercurial matter at this stage in the game :-) It's all about looking at how it provides value :-)</p> <p>From the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id10d4f4a8">Linked Data</a> angle, the ability to produce, dispatch, and exploit "<a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id13bed160">Context</a>" across an array of "Perspectives" from a plethora of disparate <a href="http://dbpedia.org/resource/Data" id="link-id1731e5f0">data</a> sources on the Web and/or behind corporate firewalls, offers immense commercial value.</p> <p> <a href="http://developer.yahoo.com/searchmonkey/" id="link-id1975d248">Yahoo's Searchmonkey</a> effort will certainly bring clarity to some of the points I made during the podcast re. the role of URIs as "value consumption tickets" (<a href="http://dbpedia.org/resource/Data" id="link-id173eb7b0">Data</a> Services are exposed via URIs). There has to be a trigger (in user space) that compels Web users to seek broader, or simply varied, perspectives as a response to <a href="http://dbpedia.org/resource/Data" id="link-id0x1c7e7f60">data</a> encountered on the Web. Yahoo! is about to put this light on in a big way (imho).</p> <p>The "self annotating" nature of the Web is what ultimately drives the manifestation of the long awaited <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id0xa18a83e8">Semantic Web</a>. I believe I postulated about <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=self%20annotation&type=text&output=html" id="link-id173d7458">"Self Annotation & the Semantic Web" in a number of prior posts</a> which, by the way, should be <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&type=text&kwds=self%20annotation&OpenSearch" id="link-id10b12208">DataRSS compatible right now</a> due to Yahoo's support of OpenSearch <a href="http://dbpedia.org/resource/Data">Data</a> Providers (which this <a href="http://dbpedia.org/resource/Blog" id="link-id170b8df8">Blog</a> Space has been for eons).</p> <p>Today, have many communities adding strucuture to the Web (via their respective tools of preference) without explicitly realizing what they are contributing. Every RSS/Atom feed, <a href="http://dbpedia.org/resource/Tag" id="link-id183d5178">Tag</a>, Weblog, Shared Bookmark, <a href="http://dbpedia.org/resource/WikiWord" id="link-id10c5e758">Wikiword</a>, Microformat, Microformat++ (<a href="http://dbpedia.org/resource/Embedded_RDF" id="link-id16d8ee40">eRDF</a> or <a href="http://dbpedia.org/resource/RDFa" id="link-id1059a688">RDFa</a>), <a href="http://dbpedia.org/resource/GRDDL" id="link-id1090ae10">GRDDL</a> stylesheet, and RDFizer etc.. is a piece of structured data.</p> <p>Finally, the different communities are all finding ways to work together (thank heavens!) and the results are going to be cataclysmic when it all plays out :-)</p> <p>Data, Structure, and Extraction are the keys to the Semantic Life! First you get the Data in a container (<a href="http://dbpedia.org/resource/Information" id="link-id180e5648">information</a> resource), and then you add Structure to the <a href="http://dbpedia.org/resource/Information" id="link-id103801e0">information</a> resource (RSS, Atom, <a href="http://dbpedia.org/resource/Microformats" id="link-id17825e40">microformats</a>, <a href="http://dbpedia.org/resource/RDFa" id="link-id189a8738">RDFa</a>, <a href="http://dbpedia.org/resource/Embedded_RDF" id="link-id1933d5c0">eRDF</a>, SIOC, FOAF, etc.), once you have Structure RDFization (i.e. transformation to <a href="http://dbpedia.org/resource/Linked_Data" id="link-id19744878">Linked Data</a>) is a synch thanks to <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id180dde30">RDF</a> Middleware (as per <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&type=text&kwds=self%20annotation&OpenSearch" id="link-id16dc3130">earlier RDF middleware posts</a>).</p>
Clearing Up RDF misrepresentation once again!
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2008-04-30#1352
2008-04-30T15:51:17Z
2008-04-30T12:07:58.000001-04:00
<p> <a href="http://myopenlink.net/dataspace/person/danieljohnlewis#this" id="link-id12d57690">Daniel Lewis</a> has penned a post titled: <a href="http://vanirsystems.com/danielsblog/2008/04/30/clearing-up-some-misconceptions-again/" id="link-id10c99f18">Clearing up some misconceptions..again</a>, in response to <a href="http://elgg.org/bwerdmuller/foaf#elgg2" id="link-id14fe1bc8">Ben Werdmuller</a>'s post titled: <a href="http://blogs.zdnet.com/social/?p=477" id="link-id141cee58">Introducing the Open Data Definition</a>. </p> <p>The great thing about the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id105991a8">Linked Data</a> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id10a6ec78">Web</a> is that it's much easier to discovery and respond to these points of view before the ink dries :-) Ben certainly needs to take a look at the <a href="http://www.w3.org/RDF/FAQ" id="link-id10f78958">Semantic Web FAQ</a> pre or post assimilation of Daniel's response.</p>
Explaining the Granular Social Network
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2008-04-15#1341
2008-04-15T21:03:54Z
2008-04-15T17:22:42-04:00
<p>Courtesy of <a href="http://www.vimeo.com/user321809/l:embed_898144" id="link-id10c725a8">Thomas Vander Wal</a>'s interesting <a href="http://dbpedia.org/resource/Blog" id="link-id142dfb90">blog</a> post titled: Explaining the Granular Social Network, I found a nice video that highlights the Who + What you know aspect of Social Networking ad the <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id1054bc58">GGG</a> in general. </p> <p>As I can't quite remix Videos on the spur of the moment (yet), I would encourage you to watch the video and then click on the link to <a href="http://myopenlink.net/dataspace/person/kidehen" id="link-id130b7410">my FOAF Profile</a>, then follow the "<a href="http://dbpedia.org/resource/Linked_Data" id="link-id18485a48">Linked Data</a>" tab to see how <a href="http://dbpedia.org/resource/Linked_Data" id="link-id14070380">Linked Data</a> oriented platforms (in my case <a href="http://dbpedia.org/resource/OpenLink_Data_Spaces" id="link-id10a30f60">OpenLink Data Spaces</a>) that exist today actually deliver what's explained in the video. </p> <p>"What You Know" (<a href="http://www.jasonkolb.com/weblog/2008/03/users-as-data-c.html" id="link-id140f4e28">Data & Friend Networks</a>) ultimately trumps "Who You Know" (Friend only Networks). The exploitation power of this reality is enhanced exponentially via the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id0xdcf0460">Linked Data</a> <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id0xa008f990">Web</a> once the implications of beaming <a href="http://dbpedia.org/resource/SPARQL" id="link-idfdfa2f0">SPARQL</a> queries down specific URIs (entry points to <a href="http://dbpedia.org/resource/Linked_Data" id="link-id15ce0dc0">Linked Data</a> graphs) become clearer :-)</p>
Adding Wordpress Blogs into the Linked Data Web using Virtuoso
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2008-04-09#1333
2008-04-09T21:27:34Z
2008-04-10T12:33:05.000003-04:00
<p> <a href="http://dbpedia.org/resource/WordPress" id="link-id101103b0">Wordpress</a> is a Weblog platform comprised of the following: </p> <ol> <li>User Interface - <a href="http://dbpedia.org/resource/PHP" id="link-id107ba368">PHP</a> </li> <li>Application Logic - <a href="http://dbpedia.org/resource/PHP" id="link-id107066b8">PHP</a> </li> <li> <a href="http://dbpedia.org/resource/Data" id="link-id13968340">Data</a> Storage (<a href="http://dbpedia.org/resource/SQL" id="link-id104c5350">SQL</a> <a href="http://dbpedia.org/resource/Relational_database_management_system" id="link-id1076d790">RDBMS</a>) - <a href="http://dbpedia.org/resource/MySQL" id="link-id109c4ea0">MySQL</a> via <a href="http://dbpedia.org/resource/PHP" id="link-id133af570">PHP</a>-<a href="http://dbpedia.org/resource/MySQL" id="link-idf0b03b0">MySQL</a> </li> <li> <a href="http://dbpedia.org/resource/Application_server" id="link-id13217630">Application Server</a> - <a href="http://dbpedia.org/resource/Apache" id="link-id108219d8">Apache</a> </li> </ol> <p>In the form above (the norm), <a href="http://dbpedia.org/resource/WordPress" id="link-id105c6d88">Wordpress</a> <a href="http://dbpedia.org/resource/Data" id="link-id104938f8">data</a> can be injected into the <a href="http://dbpedia.org/resource/Linked_Data" id="link-id107a5f18">Linked Data</a> <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id177329c0">Web</a> via RDFization middleware such as the<a href="http://virtuoso.openlinksw.com/Whitepapers/html/VirtSpongerWhitePaper.html" id="link-id10531b50">Virtuoso Sponger</a> (built into all <a href="http://virtuoso.openlinksw.com" id="link-id10d7e710">Virtuoso</a> instances) and <a href="http://triplr.org/" id="link-id107dcab8">Triplr</a>. The downside of this approach is that the <a href="http://dbpedia.org/resource/Blog" id="link-id1055ab68">blog</a> owner doesn't necessary possess full control over their contributions to the emerging <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-idfed0358">Giant Global Graph</a> or <a href="http://dbpedia.org/resource/Linked_Data" id="link-id10d70668">Linked Data</a>.</p> <p>Another route to <a href="http://dbpedia.org/resource/Linked_Data" id="link-id104c7f68">Linked Data</a> exposure is via <a href="http://virtuoso.openlinksw.com" id="link-id0xa255fb50">Virtuoso</a>'s Metaschema Language for producing <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id10968388">RDF</a> Views over <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id13f594c8">ODBC</a>/<a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id138f69a8">JDBC</a> accessible <a href="http://dbpedia.org/resource/Data" id="link-id1393c068">Data</a> Sources, that enables the following setup:</p> <ol> <li>User Interface - <a href="http://dbpedia.org/resource/PHP" id="link-id0x9fb9c478">PHP</a> </li> <li>Application Logic - PHP </li> <li> <a href="http://dbpedia.org/resource/Data" id="link-id0xc605960">Data</a> Storage (<a href="http://dbpedia.org/resource/SQL" id="link-id0xc2be608">SQL</a> <a href="http://dbpedia.org/resource/Relational_database_management_system" id="link-id0xc7a28a8">RDBMS</a>) - <a href="http://dbpedia.org/resource/MySQL" id="link-id0xc7228f0">MySQL</a> via the PHP-MySQL <a href="http://dbpedia.org/resource/Data">data</a> access interface </li> <li> <a href="http://dbpedia.org/resource/Virtual_Database" id="link-id134b1ee8">Virtual Database</a> linkage of MySQL Tables into Virtuoso </li> <li> <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-idfe31548">RDF</a> View generated over the Virtual SQL Tables </li> <li> <a href="http://dbpedia.org/resource/Application_server" id="link-id0xb8dfa68">Application Server</a> - Virtuoso which provides <a href="http://dbpedia.org/resource/Linked_Data" id="link-id0xc149518">Linked Data</a> Deployment such that <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id10ad9ca0">RDF</a> <a href="http://dbpedia.org/resource/Linked_Data">Linked Data</a> is exposed when requested by <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-idfd352e0">Web</a> User Agents.</li> </ol> <p>Alternatively, you can also exploit Virtuoso as the SQL DBMS, <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id0x9ec4f440">RDF</a> DBMS, Application Server, and Linked Data Deployment platform:</p> <ol> <li>User Interface - PHP </li> <li> Application Logic - PHP </li> <li>Data Storage (SQL RDBMS) - Virtuoso via PHP-<a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id14197218">ODBC</a> data access interface (* <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id103d1a80">ODBC</a> is Virtuoso's native SQL CLI/API *) </li> <li><a href="http://dbpedia.org/resource/Resource_Description_Framework">RDF</a> View generated over the Native SQL Tables </li> <li>Application Server - Virtuoso which provides Linked Data Deployment such that RDF Linked Data is exposed when requested by <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id13918d68">Web</a> User Agents (e.g. <a href="http://demo.openlinksw.com/rdfbrowser" id="link-idff835f0">OpenLink RDF Browser</a>, <a href="http://zitgist.com/about/" id="link-id1372e510">Zitgist</a> <a href="http://dataviewer.zitgist.com" id="link-id109c3048">Data Viewer</a>, <a href="http://www4.wiwiss.fu-berlin.de/rdf_browser" id="link-id105d97f0">DISCO Hyperdata Browser</a>, and <a href="http://dig.csail.mit.edu/2005/ajar/release/tabulator/0.8/tab.html" id="link-id10cc20d8">Tabulator</a>). </li> </ol> <h2 align="left">Benefits?</h2> <ul> <li>Each user account gets a proper Linked Data <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id108c92b0">URI</a> (ID) that can me meshed/smushed with other IDs (so you add data from this new <a href="http://dbpedia.org/resource/Blog" id="link-idfd39648">blog</a> space to other linked data sources associated with you other URIs/IDs) </li> <li>Each post gets a proper <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id10add540">URI</a> All data is now query-able via <a href="http://dbpedia.org/resource/SPARQL" id="link-id101b98f0">SPARQL</a> Discoverability increases exponentially (without drop in relevance in either direction i.e. discovering or being discovered)</li> </ul> <p>How Do I map the <a href="http://dbpedia.org/resource/WordPress" id="link-id12e448c0">WordPress</a> SQL Schema to RDF using Virtuoso? </p> <ul> <li>Determine the RDF Schema or Ontologies that define the Classes for which you will be producing instance data (e.g. SIOC and FOAF) </li> <li>Declare <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-idfaf5c80">URI</a>/IRI generator functions (*special Virtuoso functions*) </li> <li>Use <a href="http://dbpedia.org/resource/SPARQL" id="link-id100436b8">SPARQL</a> Graph patterns to apply <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id0x9de74950">URI</a>/IRI generator functions to Tables, Views, Table Values mode Stored Procedures, Query Resultsets as part of RDBMS to RDF mapping </li> </ul> <p> Read the <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VOSSQL2RDF" id="link-idfaf5d58">Meta Schema Language guide</a> or simply apply our "<a href="http://dbpedia.org/resource/WordPress" id="link-id0x9ef73c78">WordPress</a> SQL Schema to RDF" script to your Virtuoso hosted instance. Of course, there are other mappings that cover other PHP applications deployed via Virtuoso:</p> <ul> <li> <a href="http://dbpedia.org/resource/PhpBB" id="link-id179f4870">phpBB3</a> SQL Schema to RDF </li> <li> <a href="http://dbpedia.org/resource/Drupal" id="link-id10b263d8">Drupal</a> SQL Schema to RDF </li> <li> <a href="http://dbpedia.org/resource/MediaWiki" id="link-id10263a40">MediaWiki</a> SQL Schema to RDF </li> </ul> <h2>Live Demos?</h2> <ul> <li> <a href="http://demo.openlinksw.com/phpBB3" id="link-id17761e88">Virtuoso Hosting phpBB3</a> (<a href="http://demo.openlinksw.com/phpBB3/user/demo#this" id="link-id10087e68">example User URI</a>)</li> <li> <a href="http://demo.openlinksw.com/drupal" id="link-id1091f1d8">Virtuoso Hosting Drupal</a> (<a href="http://demo.openlinksw.com/drupal/user/demo#this" id="link-id13e3d468">example User URI</a>)</li> <li> <a href="http://demo.openlinksw.com/mediawiki" id="link-id10531be0">Virtuoso Hosting MediaWiki</a> (<a href="http://demo.openlinksw.com/mediawiki/user/KingsleyIdehen#this" id="link-id109c5d40">example User URI</a>)</li> </ul>
Recent Data Portability, Linked Data, and Open Data Access Podcasts
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2008-04-09#1332
2008-04-09T17:15:56Z
2008-04-09T13:22:23.000002-04:00
<p>I just listen to, and very much enjoyed (lots of chuckling) <a href="http://www.dajobe.org/" id="link-id177310c8">Dave Beckett</a>'s podcast interview on the <a href="http://talk.talis.com/" id="link-id1056ec98">Talis podcast network</a>. Clearly Dave has a bent for funny project names etc.. He also introduced "Inter-Webs" (<a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> <a href="http://dbpedia.org/resource/Data">Data</a> Spaces in my parlance) towards the end of the interview.</p> <p> <a href="http://www.mediaslate.org/wp/about/" id="link-idfc558f0">Trent Adams</a>, <a href="http://www.linkedin.com/pub/0/49b/4b5" id="link-id107137b0">Steve Greenberg</a>, and I, also had a podcast chat about <a href="http://www.mediaslate.org/wp/2008/03/29/dataportability-in-motion-podcast/" id="link-id10663ec8">Web Data Portability and Accessibility (Linked Data)</a>. I also remixed <a href="http://www.johnbreslin.com/" id="link-id104617f0">Jon Breslin</a>'s "<a href="http://www.slideshare.net/Cloud/dataportability-and-me-introducing-sioc-foaf-and-the-semantic-web/" id="link-id12ca2c70">Data Portability & Me</a>" presentation to produce: "<a href="http://www.slideshare.net/Cloud/data-accessibility-and-me-introducing-sioc-foaf-and-the-linked-data-web/" id="link-idfdf0cd8">Data Accessibility & Me</a>". </p> <p>The podcasts interviews and presentations provide contributions to the broadening discourse about Open Data Access / Connectivity on the Web.</p>
So, What Does "HREF" Stand For, Anyway
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2008-03-12#1323
2008-03-12T16:08:46Z
2008-04-10T16:13:50-04:00
<p>As per usual I am writing this post with the aim of killing a number of <a href="http://dbpedia.org/resource/Meme" id="link-id0x1caa10d8">meme</a>-birds with a single post in relation to the emerging <a href="http://dbpedia.org/resource/Linked_Data" id="link-id156867c8">Linked Data Web</a>.</p> <p>*On* the ubiquitous <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id0x1e5a1a08">Web</a> of "Linked Documents", HREF means (by definition and usage): <a href="http://dbpedia.org/resource/Hypertext" id="link-id16078f10">Hypertext</a> Reference to an <a href="http://dbpedia.org/resource/Hypertext_Transfer_Protocol" id="link-id0x9e840368">HTTP</a> accessible <a href="http://dbpedia.org/resource/Data" id="link-id0x9e570ce8">Data</a> Object of Type: "Document" (an <a href="http://dbpedia.org/resource/Information" id="link-id0xccc6ee8">information</a> resource). Of course we don't make the formal connection of Object Type when dealing with the <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> on a daily basis, but whenever you encounter the "resource not found" condition notice the message: <a href="http://dbpedia.org/resource/HTTP_404" id="link-id153b4d98">HTTP/1.0 404</a> Object Not Found, from the <a href="http://dbpedia.org/resource/Hypertext_Transfer_Protocol">HTTP</a> Server tasked with retrieving and returning the resource. </p> <p>*In* the Web of "<a href="http://dbpedia.org/resource/Linked_Data" id="link-id0x9ed9fb78">Linked Data</a>", a complimentary addition to the current Web of "Linked Documents", HREF is used to reference <a href="http://dbpedia.org/resource/Data">Data</a> Objects that are of a variety of "Types", not just "Documents". And the way this is achieved, is by using <a href="http://dbpedia.org/resource/Surrogate_key" id="link-id153d4438">Data Object Identifiers</a> (URIs / IRIs that are generated by the <a href="http://dbpedia.org/resource/Linked_Data">Linked Data</a> deployment platform) in the strict sense i.e. Data Identity (<a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id0xc9ef280">URI</a>) is separated from Data Address (<a href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id0x1cb62390">URL</a>). Thus, you can reference a Person Data Object (aka an instance of a Person Class) in your HREF and the <a href="http://dbpedia.org/resource/Hypertext_Transfer_Protocol" id="link-id1554e458">HTTP</a> Server returns a Description of the Data Object via a Document (again, an <a href="http://dbpedia.org/resource/Information">information</a> resource). A document containing the Description of a Data Object typically contains HREFs to other Data Objects that expose the Attributes and Relationships of the initial Person Data Object, and it this collection of Data Objects that is technically called a "Graph" -- which is what <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id0xc67a780">RDF</a> models.</p> <blockquote>What I describe above is basic stuff for anyone that's familiar with Object Database or Distributed Objects technology and concepts.</blockquote> <h2><a href="http://dbpedia.org/resource/Uniform_Resource_Identifier">URI</a> and <a href="http://dbpedia.org/resource/Uniform_Resource_Locator">URL</a> confusion</h2> <p>The Linked Document Web is a collection of physical resources that traverse the Web Information Bus in palatable format i.e documents. Thus, Document Object Identity and Document Object Data Address can be the same thing i.e. a <a href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id1525d028">URL</a> can serve as the <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id16e50b50">ID/URI</a> of a Document Data Object.</p> <p>The Linked Data Web on the other hand, is a Distributed Object Database, and each Data Object must be uniquely defined, otherwise we introduce ambiguity that ultimately taints the Database itself (making incomprehensible to reasoning challenged machines). Thus we must have unique Object IDs (URIs / IRIs) for People, Places, Events, and other things that aren't Documents. Once we follow the time tested rules of Identity, People can then be associated with the things they create (<a href="http://dbpedia.org/resource/Blog" id="link-id0xc7c3ce0">blog</a> posts, web pages, bookmarks, wikiwords etc). <a href="http://dbpedia.org/resource/Resource_Description_Framework">RDF</a> is about expressing these graph model relationships while RDF serialization formats enables the information resources to transport these data object link ladden information resources to requesting User Agents.</p> <p>Put in more succinct terms, all documents on the Web are compound documents in reality (e.g. mast contain a least an image these days). The Linked Data Web is about a Web where Data Object IDs (URIs) enable us to distill source data from the information contained in a compound document.</p> <h2>Examples:</h2> <ol> <li><http://community.linkeddata.org/dataspace/person/kidehen2#this> - the ID (URI minted from URL via addition of #this) of a Data Object of Type Person that Identifies me. The Person definition I use comes from the FOAF vocabulary/schema/ontology/data dictionary</li> <li><http://community.linkeddata.org/dataspace/person/kidehen2> - the URI (also a URL) of a FOAF file that contains a description of the Data <a href="http://dbpedia.org/resource/Identity_%28object-oriented_programming%29" id="link-id0xca491e0">Object ID</a>: <http://community.linkeddata.org/dataspace/person/kidehen2#this> (me)</li> <li>As an information resource <http://community.linkeddata.org/dataspace/person/kidehen2> can be dispatched from an HTTP server to a User Agent in (X)HTML, RDF/XML, N3/Turtle representations via HTTP Content Negotiation (<strong>note:</strong> Look at the "Linked Data" tab to see one example of what Data Links facilitate re. Data Discovery and Exploration)</li> <li>If I choose an <a href="http://dbpedia.org/resource/Identity_%28object-oriented_programming%29">Object ID</a> of <http://community.linkeddata.org/dataspace/person/kidehen2/this> instead of <http://community.linkeddata.org/dataspace/person/kidehen2#this> then the HTTP Server should not return an information resource (i.e provide 200 OK response) when a User Agent requests a resource via HTTP using the URI: <http://community.linkeddata.org/dataspace/person/kidehen2/this>, because a Data Object ID (URI) and the Data Object Address (URL) cannot be the same when my Data Object isn't of Type Document; the sever has to use response code 303 to redirect the user agent to the URL of an information resource that matches the Content-type designated in the HTTP Request or determine representation based on it's own quality of service rules for the information resource associated with the Object ID (URI).</li> </ol> <p>The degree of unobtrusiveness of new technology, concepts, or new applications of existing technology, is what ultimately determines eventual uptake and <a href="http://dbpedia.org/resource/Meme">meme</a> virulence (network effects). For a while, the <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id0xc86cda0">Semantic Web</a> meme was mired in confusion and general misunderstanding due to a shortage of practical use case scenario demos. </p> <p>The emergence of the <a href="http://dbpedia.org/resource/SPARQL" id="link-id0xc614158">SPARQL</a> Query Language has provided critical infrastructure for a number of products, projects, and demos, that now make the utility of the <a href="http://dbpedia.org/resource/Semantic_Web">Semantic Web</a> vision mush clearly via the simplicity of Linked Data, as exemplified by the following:</p> <ol> <li> <a href="http://community.linkeddata.org/dataspace/organization/lod#this" id="link-id0xc7c19f0">Linking Open Data Community</a> - collection of People and Linked Data Spaces (across a variety of domains)</li> <li> <a href="http://dbpedia.org/resource/DBpedia" id="link-id0xcb1c398">DBpedia</a> - Ground zero for experiencing and comprehending Linked Data</li> <li> <a href="http://dbpedia.org/resource/OpenLink_Data_Spaces" id="link-id0xc16e458">OpenLink Data Spaces</a> - a simple solution for creating Linked Data Web presence via from existing Web Data Sources (Blogs, Wikis, Shared Bookmarks, <a href="http://dbpedia.org/resource/Tag" id="link-id0xc340200">Tag</a> Spaces, Web Sites, Social Networking Services, Web Services, Discussion Forums etc..)</li> <li>OpenLink <a href="http://virtuoso.openlinksw.com" id="link-id0xca83470">Virtuoso</a> - a Universal Server for generating, managing, and deploying RDF Linked Data from <a href="http://dbpedia.org/resource/SQL" id="link-id0xcce3870">SQL</a>, XML, Web Services based data sources</li> </ol> Why Is This Post a Linked Data Demo, Again? Place the permalink of this post in a Linked Data aware user agent (<a href="http://demo.openlinksw.com/rdfbrowser" id="link-id17b79488">OpenLink RDF Browser1</a>, <a href="http://demo.openlinksw.com/rdfbrowser2" id="link-id15957150">OpenLink RDF Browser2</a>, <a href="http://dataviewer.zitgist.com/" id="link-id15550cf8">Zitgist</a>, <a href="http://www4.wiwiss.fu-berlin.de/rdf_browser" id="link-id1565a680">DISCO</a>, <a href="http://dig.csail.mit.edu/2005/ajar/release/tabulator/0.8/tab.html" id="link-id15700350">Tabulator</a>), and the you can see the universal of interlinked data exposed by this post. The Title of this post should not be the sole mechanism for determining that it is Linked to other posts about the same topic. <h2>Related</h2> <ul> <a href="http://tomayko.com" id="link-id15c56720">Ryan Tomayko</a>'s post titled: <a href="http://tomayko.com/writings/wtf-is-an-href-anyway" id="link-id1514a328">So, What Does "HREF" Stand For, Anyway</a> </ul> <ul> <a href="http://torrez.us/who#elias" id="link-id14eec928">Elias Torre</a>'s post titled: <a href="http://torrez.us/archives/2008/03/10/563/" id="link-id15722c08">The Web FTW</a> </ul> <ul> <a href="http://www.w3.org/TR/cooluris/" id="link-id1576c118">Cool URIs for the Semantic Web.</a> </ul>
10 Reasons to use OpenLink Data Spaces (ODS)
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2008-02-08#1314
2008-02-08T17:33:45Z
2008-02-08T17:08:43-05:00
<p>Via post by <a href="http://vanirsystems.com/danielsblog" id="link-id1480d7c0">Daniel Lewis</a>, titled:<a href="http://vanirsystems.com/danielsblog/2008/02/08/10-reasons-to-use-openlink-data-spaces/#comments" id="link-id1320a618">10 Reasons to use OpenLink Data Spaces</a> </p> <blockquote> <p>There are quite a few reasons to use <a href="http://en.wikipedia.org/wiki/OpenLink_Data_Space" id="link-id103eb060">OpenLink Data Spaces (ODS)</a>. Here are 10 of the reasons why I use ODS:</p> <ol> <li>Its native support of DataPortability Recommendations such as <a href="http://dbpedia.org/resource/RSS" id="link-id18957e88">RSS</a>, <a href="http://dbpedia.org/resource/Atom_%28standard%29" id="link-id1410a9c0">Atom</a>, <a href="http://www.apml.org/" id="link-idfde4b90">APML</a>, <a href="http://dbpedia.org/resource/Yadis" id="link-id1328c260">Yadis</a>, <a href="http://dbpedia.org/resource/OPML" id="link-id10133f70">OPML</a>, <a href="http://dbpedia.org/resource/Microformat" id="link-id16e19be0">Microformats</a>, <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id12deef98">FOAF</a>, <a href="http://dbpedia.org/resource/SIOC" id="link-id15fb99b0">SIOC</a>, <a href="http://dbpedia.org/resource/OpenID" id="link-id1390ae10">OpenID</a> and <a href="http://en.wikipedia.org/wiki/OAuth" id="link-id14dcce70">OAuth</a>.</li> <li>Its native support of Semantic Web Technologies such as: <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id15fc75a0">RDF</a> and <a href="http://dbpedia.org/resource/SPARQL" id="link-id14255238">SPARQL</a>/<a href="http://jena.hpl.hp.com/~afs/SPARQL-Update.html" id="link-id15fe2e40">SPARUL</a> for querying.</li> <li>Everything in ODS is an <a href="http://dbpedia.org/resource/Object_%28computer_science%29" id="link-id11c204a0">Object</a> with its own <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id14812560">URI</a>, this is due to the underlying <a href="http://dbpedia.org/resource/Object-relational_database" id="link-idf663e08">Object-Relational</a> Architecture provided by <a href="http://dbpedia.org/resource/Virtuoso_Universal_Server" id="link-id1484e4c8">Virtuoso</a>.</li> <li>It has all the social media components that you could need, including: <a href="http://dbpedia.org/resource/Blog" id="link-id10120b58">blogs</a>, <a href="http://dbpedia.org/resource/Wiki" id="link-id14d9a608">wikis</a>, <a href="http://dbpedia.org/resource/Social_network_service" id="link-idf0b3a30">social networks</a>, <a href="http://dbpedia.org/resource/Aggregator" id="link-id188d7c78">feed readers</a>, <a href="http://dbpedia.org/resource/Customer_relationship_management" id="link-id134a2c48">CRM</a> and a <a href="http://dbpedia.org/resource/Calendar" id="link-idf66af80">calendar</a>.</li> <li>It is expandable by installing pre-configured components (called VADs), or by re-configuring a <a href="http://dbpedia.org/resource/LAMP_%28software_bundle%29" id="link-id102e8008">LAMP</a> application to use <a href="http://dbpedia.org/resource/Virtuoso_Universal_Server" id="link-id13fe2b68">Virtuoso</a>. Some examples of current VADs include: <a href="http://dbpedia.org/resource/MediaWiki" id="link-id1011d9f0">MediaWiki</a>, <a href="http://dbpedia.org/resource/WordPress" id="link-id13624060">Wordpress</a> and <a href="http://dbpedia.org/resource/Drupal" id="link-id100c4510">Drupal</a>.</li> <li>It works with external webservices such as: <a href="http://dbpedia.org/resource/Facebook" id="link-id131fe6d0">Facebook</a>, <a href="http://dbpedia.org/resource/Del.icio.us" id="link-idfdd1580">del.icio.us</a> and <a href="http://dbpedia.org/resource/Flickr" id="link-id1496aff0">Flickr.</a> </li> <li>Everything within OpenLink Data Spaces is <a href="http://dbpedia.org/resource/Linked_Data" id="link-id17114c00">Linked Data</a>, which provides more meaningful information than just plain structural information. This meaningful information could be used for complex inferencing systems, as ODS can be seen as a <a href="http://dbpedia.org/resource/Expert_system" id="link-id15ea4108">Knowledge Base</a>.</li> <li>ODS builds bridges between the existing static-document based web (aka â<a href="http://dbpedia.org/resource/Web_1.0" id="link-idf08b338">Web 1.0</a>â), the more dynamic, services-oriented, social and/or user-orientated webs (aka â<a href="http://dbpedia.org/resource/Web_2.0" id="link-idfde26e0">Web 2.0</a>â) and the web which we are just going into, which is more data-orientated (aka â<a href="http://dbpedia.org/resource/Web_3.0" id="link-idf9b7328">Web 3.0</a>â or âLinked Data Webâ).</li> <li>It is fully supportive of <a href="http://dbpedia.org/resource/Cloud_computing" id="link-id189480d0">Cloud Computing</a>, and can be installed on <a href="http://dbpedia.org/resource/Amazon_Elastic_Compute_Cloud" id="link-id10026778">Amazon EC2</a>.</li> <li>Its released free under the GNU <a href="http://dbpedia.org/resource/GNU_General_Public_License" id="link-id16002fb0">General Public License (GPL)</a>. [note]However, it is technically dual licensed as it lays on top of the <a href="http://en.wikipedia.org/wiki/Virtuoso_Universal_Server" id="link-id132d4238">Virtuoso Universal Server</a> which has both Commercial and GPL licensing[/note]</li> </ol> </blockquote> <p>The features above collectively provide users with a Linked Data Junction Box that may reside with corporate intranets or "out in the clouds" (Internet). You can consume, share, and publish data in a myriad of formats using a plethora of protocols, without any programming. ODS is simply about exposing the data from your Web 1.0, 2.0, 3.0 application interactions in structured from, with Linking, Sharing, and ultimately Meshing (not Mashing) in mind.</p> <p> <strong>Note:</strong> Although ODS is equipped with a broad array of Web 2.0 style Applications, you do not need to use native ODS apps in order to exploit it's power. It binds to anything that supports the relevant protocols and data formats.</p>
FOAF-ing Linked Data is quite SIOC-ing
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2008-01-31#1306
2008-01-31T02:40:12Z
2008-02-01T18:20:34-05:00
<p>The title of this post is a "Tongue in cheek" expression of euphoria now that I have <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-idfa63488">FOAF</a> and <a href="http://dbpedia.org/resource/SIOC" id="link-idfa976f0">SIOC</a> (pronounced SHOCK) based data spaces exposed via <a href="http://myopenlink.net/dataspace/person/kidehen" id="link-idfde41f8">my FOAF</a> and <a href="http://myopenlink.net/dataspace/kidehen" id="link-idfdca6c8">my SIOC</a> information resource (<a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id16d0b0d8">RDF</a> files) <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-idfa97070">URI</a>s.</p> <p>If you want to explore who I know, what I read, and what I've tagged (amongst other things), all you have to do is:</p> <ol> <li>Beam a <a href="http://dbpedia.org/resource/SPARQL" id="link-idfdca878">SPARQL</a> query down my data space URIs which expose FOAF or SIOC based interconnected <a href="http://dbpedia.org/resource/Linked_Data" id="link-idfa954e8">Linked Data</a> graphs.</li> <li> Walkthrough using an RDF Browser until you reach a beachhead and then beam your SPARQL from there (remember you only need the URI of the RDF Data Source, and while in my Data Space every data item has a proper URI).</li> </ol> <p>Some Tools that help you comprehend what I am saying:</p> <h2>Browsers</h2> <ul> Zitgist Data Viewer (<a href="http://dataviewer.zitgist.com/?uri=http%3A//myopenlink.net/dataspace/kidehen" id="link-id16d410c0">SIOC</a> and <a href="http://dataviewer.zitgist.com/?uri=http%3A//myopenlink.net/dataspace/person/kidehen" id="link-idfa489e8">FOAF</a> data spaces)</ul> <ul>OpenLink RDF Browser (<a href="http://demo.openlinksw.com/rdfbrowser/?uri=http%3A%2F%2Fmyopenlink.net%2Fdataspace%2Fkidehen" id="link-idfa8b0d8">SIOC</a> and <a href="http://demo.openlinksw.com/rdfbrowser/?uri=http%3A%2F%2Fmyopenlink.net%2Fdataspace%2Fperson%2Fkidehen" id="link-idfa974a8">FOAF</a> data spaces)</ul> <ul>DISCO (<a href="http://www4.wiwiss.fu-berlin.de/rdf_browser/?browse_uri=http%3A%2F%2Fmyopenlink.net%2Fdataspace%2Fkidehen%2Fspace%23this" id="link-idfa62288">SIOC</a> and <a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-idf940338">FOAF</a> data spaces)</ul> <ul> <a href="http://dig.csail.mit.edu/2005/ajar/release/tabulator/0.8/tab.html" id="link-id16d6a4b8">Tabulator</a> </ul> <h2>Query Tools</h2> <ul> <a href="http://demo.openlinksw.com/sparql_demo" id="link-idfdd43b8">SPARQL Demo</a> </ul> <ul> <a href="http://demo.openlinksw.com/isparql" id="link-idfa96bd0">iSPARQL QBE</a> </ul>
Semantic Data Web Epiphanies: One Node at a Time
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2008-01-17#1300
2008-01-17T22:59:00Z
2008-01-18T02:27:27.000004-05:00
<p>In 2006, I stumbled across <a href="http://www.jasonkolb.com" id="link-id17165b98">Jason Kolb</a> (online) via a 4-part series of posts titled: <a href="http://www.jasonkolb.com/weblog/2006/08/reinventing_the_1.html" id="link-id14204cf8">Reinventing the Internet</a>. At the time, I realized that Jason was postulating about what is popularly known today as "<a href="http://en.wikipedia.org/wiki/Data_portability" id="link-id1412b280">Data Portability</a>", so I made contact with him (blogosphere style) via a post of my own titled: <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1033" id="link-id13b1cb20">Data Spaces, Internet Reinvention, and the Semantic Web</a>. Naturally, I tried to unveil to Jason the connection between his vision and the essence of the <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id143117f0">Semantic Web</a>. Of course, he was skeptical :-)</p> <p>Jason recently moved to <a href="http://dbpedia.org/resource/Massachusetts" id="link-id13c4a470">Massachusetts</a> which lead to me pinging him about our earlier blogosphere encounter and the emergence of a <a href="http://dataportability.org/" id="link-id17395c60">Data Portability Community</a>. I also informed him about the fact that <a href="http://dbpedia.org/resource/Tim_Berners-Lee" id="link-id105507f0">TimBL</a>, myself, and a number of other Semantic Web technology enthusiasts, frequently meet on the 2nd Tuesday of each month at the <a href="http://dbpedia.org/resource/Massachusetts_Institute_of_Technology" id="link-id1719f798">MIT</a> hosted <a href="http://esw.w3.org/topic/CambridgeSemanticWebGatherings" id="link-id1734d460">Cambridge Semantic Web Gatherings</a>, to discuss, demonstrate, debate all aspects of the Semantic Web. Luckily (for both of us), Jason attended the last event, and we got to meet each other in person.</p> <p>Following our face to face meeting in Cambridge, a number of follow-on conversations ensued covering, Linked Data and practical applications of the Semantic Web vision. Jason writes about our exchanges a recent post titled: <a href="http://www.jasonkolb.com/weblog/2008/01/the-semantic-we.html" id="link-id13be6280">The Semantic Web</a>. His passion for Data Portability enabled me to use <a href="http://esw.w3.org/topic/FoafOpenid" id="link-id141516a8">OpenID and FOAF integration</a> to connect the Semantic Web and Data Portability via the Linked Data concept.</p> <p>During our conversations, Jason also eluded to the fact that he had already encountered <a href="http://en.wikipedia.org/wiki/OpenLink_Software" id="link-id17038218">OpenLink Software</a> while working with our <a href="http://data.openlinksw.com/oplweb/product_category/odbc#this" id="link-id14325f08">ODBC Drivers</a> (part of or <a href="http://data.openlinksw.com/oplweb/product_family/uda#this" id="link-id11ab1008">UDA product family</a>) for <a href="http://dbpedia.org/resource/Informix" id="link-id125858d0">IBM Informix</a> (<a href="http://data.openlinksw.com/oplweb/product/odbc-informix-st#this" id="link-id13b85e30">Single-Tier</a> or <a href="http://data.openlinksw.com/oplweb/product/odbc-informix-mt#this" id="link-id13edceb0">Multi-Tier</a> Editions) a few years ago (interesting random connection).</p> <p>As I've stated in the past, I've always felt that the Semantic Web vision will materialize by way of a global epiphany. The count down to this inevitable event started at the birth of the blogosphere, ironically. And accelerated more recently, through the emergence of <a href="http://dbpedia.org/resource/Web_2.0" id="link-id171d4ec8">Web 2.0</a> and <a href="http://dbpedia.org/page/Social_network" id="link-id140da830">Social Networking</a>, even more ironically :-)</p> <p>The blogosphere started the process of Data Space coalescence via RSS/Atom based semi-strucutured data enclaves, Web 2.0 RDFpropagated Web Service usage en route to creating service provider controlled, data and information silosRDF, Social NetworkingRDF brought attention to the fact that User Generated Data wasn't actually owned or controlled by the Data Creators etc.</p> <p>The emergence of "Data Portability" has created a palatable moniker for a clearly defined, and slightly easier to understand, problem: the meshing of Data and Identity in cyberspace i.e. individual points of presence in cyberspace, in the form of "Personal Data Spaces in the Clouds" (think: doing really powerful stuff with .name domains). In a sense, this is the critical inflection point between the document centric "Web of Linked Documents" and the data centric "Web or Linked Data". There is absolutely no other way solve this problem in a manner that alleviates the imminent challenges presented by information overload -- resulting from the exponential growth of user generated data across the Internet and enterprise Intranets.</p>
W3C's SPARQLing Data Access Ingenuity
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2008-01-15#1295
2008-01-15T22:58:53Z
2008-01-17T15:41:04.000006-05:00
<p>The W3C officially unveiled the SPARQL Query Language today via a press release titled: <a href="http://www.w3.org/2007/12/sparql-pressrelease" id="link-id10074ca8">W3C Opens Data on the Web with SPARQL</a>.</p> <h2>What is <a href="http://dbpedia.org/resource/SPARQL" id="link-id10183f60">SPARQL</a>?</h2> <p>A query language for the burgeoning Structured & <a href="http://dbpedia.org/resource/Linked_Data" id="link-id10426b18">Linked Data</a> Web (aka <a href="http://dbpedia.org/resource/Semantic_Web" id="link-idffde090">Semantic Web</a> / <a href="http://en.wikipedia.org/wiki/Giant_Global_Graph" id="link-id103e3688">Giant Global Graph</a>). Like <a href="http://dbpedia.org/resource/SQL" id="link-id103365f8">SQL</a>, for the Relational Data Model, it provides a query language for the Graph based <a href="http://dbpedia.org/resource/RDF" id="link-id103e33e8">RDF</a> Data Model.</p> <p>It's also a <a href="http://dbpedia.org/resource/Representational_State_Transfer" id="link-id1036a3d0">REST</a> or <a href="http://dbpedia.org/resource/SOAP" id="link-id103b36d8">SOAP</a> based Web Service that exposes SPARQL access to RDF Data via an endpoint. </p> <p>In addition, it's also a Query Results Serialization format that includes <a href="http://dbpedia.org/resource/XML" id="link-id1023bc60">XML</a> and <a href="http://dbpedia.org/resource/JSON" id="link-id102c3f88">JSON</a> support.</p> <h2>Why is it Important?</h2> <p>It brings important clarity to the notion of the "Web as a Database" by transforming existing Web Sites, Portals, and Web Services into bona fide corpus of Mesh-able (rather than Mash-able) Data Sources. For instance, you can perform queries that join one or more of the aforementioned data sources in exactly the same manner (albeit different syntax) as you would one or more SQL Tables. </p> <h3>Example:</h3> <p>-- SPARQL equivalent of SQL SELECT * against my personal data space hosted FOAF file</p> <b><pre> SELECT DISTINCT ?s ?p ?o FROM <http://myopenlink.net/dataspace/person/kidehen> WHERE {?s ?p ?o}</pre></b> <p>-- SPARQL against my social network -- Note: My SPARQL will be beamed across all of contacts in the social networks of my contacts as long as they are all HTTP URI based within each data space</p> <b><pre>PREFIX foaf: <http://xmlns.com/foaf/0.1/> SELECT DISTINCT ?Person FROM <http://myopenlink.net/dataspace/person/kidehen> WHERE {?s a foaf:Person; foaf:knows ?Person}</pre></b> <p>Note: you can use the basic <a href="http://demo.openlinksw.com/sparql" id="link-id1007d9b8">SPARQL Endpoint</a>, <a href="http://demo.openlinksw.com/isparql" id="link-id102c3e08">SPARQL Query By Example</a>, or <a href="http://demo.openlinksw.com/sparql_demo" id="link-id10201f98">SPARQL Query Builder Demo tool</a> to experiment with the demonstration queries above.</p> <h2>How Do I use It?</h2> <p>SPARQL is implemented by RDF Data Management Systems (Triple or Quad Stores) just as SQL is implemented by Relational Database Management Systems. The aforementioned data management systems will typically expose SPARQL access via a SPARQL endpoint.</p> <h2>Where are it's implementations?</h2> <p>A SPARQL implementors Testimonial page accompanies the SPARQL press release. In addition the is a growing collection of implementations on the<a href="http://esw.w3.org/topic/SparqlImplementations" id="link-id10066ca8"> ESW Wiki Page for SPARQL compliant RDF Triple & Quad Stores</a>.</p> <h2>Is this really a big deal?</h2> <p>Yes! SPARQL facilitates an<a href="http://virtuoso.openlinksw.com/presentations/Virtuoso_Sponger_1/Virtuoso_Sponger_1.html" id="link-id101ee5b0"> unobtrusive manifestation of a Linked Data Web</a> by way of natural extension of the existing Document Web i.e these Web enclaves co-exist in symbiotic fashion. </p> <p>As <a href="http://dbpedia.org" id="link-id1037edc0">DBpedia</a> very clearly demonstrates, Linked Data makes the Semantic Web demonstrable and much easier to comprehend. Without SPARQL there would be no mechanism for <a href="http://virtuoso.openlinksw.com/presentations/Virtuoso_Deploying_Linked_Data/Virtuoso_Deploying_Linked_Data.html" id="link-id10455da8">Linked Data deployment</a>, and without Linked Data there is no mechanism for Beaming Queries (directly or indirectly) across the Giant Global Graph of data hosted by Social Networks, Shard Bookmarks Services, Weblogs, Wikis, RSS/Atom/OPML feeds, Photo Galleries and other Web accessible Data Sources (Data Spaces).</p> <h2>Related items</h2> <ul> <a href="http://www.w3.org/TR/cooluris/" id="link-id102021d8">Cool URIs</a> </ul> <ul> <a href="http://sites.wiwiss.fu-berlin.de/suhl/bizer/pub/LinkedDataTutorial/" id="link-id1020d5c0">Publishing Linked Data Tutorial</a> </ul> <ul a="a" href="http://virtuoso.openlinksw.com/wiki/main/Main/ODSSIOCRef"> Detailed SPARQL Query Examples using SIOC Data Spaces</ul> <ul> <a href="http://virtuoso.openlinksw.com/wiki/main/Main/ODSFOAFRef" id="link-id102c4608">Detailed SPARQL Query Examples using FOAF Data Spaces</a> </ul>
OpenOffice.org, SPARQL, and the Linked Data Web
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2008-01-04#1288
2008-01-05T02:50:00Z
2008-02-04T20:42:50.000004-05:00
<p>Question posed by Dan Brickley via a blog post: SQL, OpenOffice: <a href="http://danbri.org/words/2008/01/04/245" id="link-id1689abd8">would a JDBC driver for SPARQL protocol make sense?</a> </p> <p>Writing a <a href="http://dbpedia.org/resource/JDBC_driver" id="link-id16a96580">JDBC Driver</a> for <a href="http://dbpedia.org/resource/SPARQL" id="link-id1a908a70">SPARQL</a> is a little overkill. <a href="http://dbpedia.org/resource/OpenOffice.org" id="link-id16ae69a8">OpenOffice.org</a> simply needs to make <a href="http://dbpedia.org/resource/XML" id="link-id168d3880">XML</a> or Web Data (<a href="http://dbpedia.org/resource/HTML" id="link-id1a7f1f50">HTML</a>, <a href="http://dbpedia.org/resource/XHTML" id="link-id16c1ae60">XHTML</a>, and XML) bonafide data sources within its "<a href="http://dbpedia.org/resource/Pivot_table" id="link-id16665398">Pivot Table</a>" functionality realm. Then all that would then be required is a <a href="http://www.w3.org/TR/rdf-sparql-query/#select" id="link-id168bcbe8">SPARQL SELECT Query</a> transported via the <a href="http://www.w3.org/TR/rdf-sparql-protocol/" id="link-id16c1bbc0">SPARQL Protocol</a> with results sent back using the <a href="http://www.w3.org/TR/rdf-sparql-XMLres/" id="link-id1aa61118">SPARQL XML results serialization</a> format (all part of a single SPARQL Protocol URL).</p> <p>Excel successfully consumes the following information resource URI: http://tinyurl.com/yvoccj (a tiny url for a SPARQL SELECT against my<a href="http://myopenlink.net/dataspace/person/kidehen" id="link-id16702ba8"> FOAF file</a>).</p> <p>Alternatively, and currently achievable, you could simply use <a href="http://esw.w3.org/topic/SPASQL" id="link-id1a1b6b78">SPASQL</a> (SPARQL within SQL) using a <a href="http://dbpedia.org/resource/DBMS" id="link-id1661f240">DBMS</a> engine that supports SQL, SPARQL, and SPARQL e.g. <a href="http://dbpedia.org/resource/Virtuoso_Universal_Server" id="link-id168bba60">Virtuoso</a>. </p> <p> <a href="http://docs.openlinksw.com/virtuoso/rdfapiandsql.html" id="link-id167d9508">Virtuoso SPASQL support</a> is exposed via it's <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id16c62160">ODBC</a> and/or JDBC Drivers. Thus you can do things such as: </p> <ol> <li>Use a SPARQL Query in the FROM CLAUSE of a <a href="http://dbpedia.org/resource/SQL" id="link-id1657a3a8">SQL</a> statement</li> <li>Execute SPARQL via SQL processor by prepending SPARQL query text with the literals "sparql" </li> </ol> <p>BTW - My News Years Resolution: get my act together and shrink the ever increasing list of "simple & practical Virtuoso use case demos" on my todo which now spans all the way back to 2006 :-(</p>
Fourth Platform: Data Spaces in The Cloud (Update)
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2007-09-22#1261
2007-09-22T23:43:00Z
2008-10-26T17:59:33-04:00
<p>I've written extensively on the subject of <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=data%20spaces&type=text&output=html" id="link-id134c2280">Data Spaces</a> in relation to the <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=data%20web%0D%0A&type=text&output=html" id="link-id105aef90">Data Web</a> for while. I've also written sparingly about <a href="http://virtuoso.openlinksw.com/wiki/main/Main/OdsIndex" id="link-id105bd100">OpenLink Data Spaces</a> (a Data Web Platform that build using Virtuoso). On the other hand, I haven't shed much light on installation and deployment of OpenLink Data Spaces.</p> <p> <a href="http://blog.jonudell.net" id="link-id14347f20">Jon Udell</a> recently penned a post titled: <a href="http://blog.jonudell.net/2007/09/21/the-fourth-platform/" id="link-id1439ed48">The Fourth Platform</a>. The post arrives at a spookily coincidental time (this happens quite often between Jon and I as demonstrated last year during our <a href="http://weblog.infoworld.com/udell/gems/ju_idehen.mp3" id="link-id107d17a8">podcast</a>; the "Fourth" in his Innovators Podcast series).</p> <p>The platform that Jon describes is "Cloud Based" and comprised of Storage and Computation. I would like to add Data Access and Management (native and virtual) under the fourth platform banner with the end product called: "Cloud based Data Spaces". </p> <p>As I write, we are releasing a Virtuoso AMI (Amazon Image) labeled: virtuoso-dataspace-server. This edition of<a href="http://virtuoso.openlinksw.com" id="link-id13543210"> Virtuoso</a> includes the OpenLink Data Spaces Layer and all of the OAT applications we've been developing for a while.</p> <h2>What Benefits Does this offer?</h2> <ol> <li>Personal Data Spaces in the Cloud - a place where you can control and consolidate data across your Blogs, Wikis, RSS/Atom Feed Subscriptions, Shared Bookmarks, Shared Calendars, Discussion Threads, Photo Galleries etc</li> <li>All the data in your Data <a href="http://en.wikipedia.org/wiki/Data_Spaces">Space</a> is <a href="http://dbpedia.org/resource/SPARQL" id="link-id1149a4f8">SPARQL</a> or <a href="http://dbpedia.org/resource/GData" id="link-id107a9f28">GData</a> accessible.</li> <li>All of the data in your Personal Data Space is <a href="http://dbpedia.org/resource/Linked_Data">Linked Data</a> from the get go. Each Item of data is <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier">URI</a> addressable</li> <li> <a href="http://dbpedia.org/resource/SIOC" id="link-id104f4160">SIOC</a> support - your Blogs, Wikis, Bookmarks etc.. are based on the SIOC ontology for Semantically Interlinking Online Communities (think: Open social-graph++) </li> <li> <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id105beb78">FOAF</a> support - your FOAF Profile page provides a URI that is an in-road to all Data in your Data Space.</li> <li> <a href="http://dbpedia.org/resource/OpenID" id="link-id1144e138">OpenID</a> support - your Personal Data Space ID is usable wherever OpenID is supported. OpenID and FOAF are integrated as per latest FOAF specs</li> <li>Two Integration with Facebook - You can access your Data Space from Facebook or access Facebook from your Data Space</li> <li>Unified Storage - The WebDAV based filesystem provides Cloud Storage that's integrated with Amazon S3; It also exposes all of your Data Space data via a traditional filesystem UI (think virtual Spotlight); You can also mount this drive to your local filesystem via your native operating system's WebDAV support</li> <li> <a href="http://dbpedia.org/resource/SyncML" id="link-id11128f48">SyncML</a> - you can sync calendar and contact details with your Data Space in the cloud from your Mobile phone.</li> <li>A practical Semantic Data Web solution - based on Web Infrastructure and doesn't require you to do anything beyond exposing URIs for data in your Data Spaces.</li> </ol> <h2> <a href="http://dbpedia.org/resource/Amazon_Elastic_Compute_Cloud" id="link-id115d1920">EC2</a>-AMI Details:</h2> <ul>AMI ID: ami-e2ca2f8b</ul> <ul>Manifest file: virtuoso-images/virtuoso-dataspace-server.manifest.xml</ul> <h2>Installation Guide:</h2> <ol> <li>Get an Amazon Web Services (AWS) account</li> <li>Signup for S3 and EC2 services</li> <li>Install the EC2 plugin for Firefox</li> <li>Start the EC2 plugin</li> <li>Locate the row containing <b>ami-7c31d515  Manifest virtuoso-test/virtuoso-cloud-beta-9-i386.manifest.xml </b>(sort using the AMI ID or Manifest Columns or search on pattern: virtuoso, due to name flux)</li> <li>Start the Virtuoso Data Space Server AMI</li> <li>Wait 4-5 minutes (*take a few minutes to create the pre-configured Linux Image*)</li> <li>Connect to http://<public_dns_name_of_your_instance>http://your-ec2-instance-cname:8890/ Log in with user/password dba/dba</public_dns_name_of_your_instance> </li> <li>Go to the Admin UI (Virtuoso Conductor) and change the PWDs for the 'dba' and 'dav' accounts (*Important!*)</li> <li>Give the "SPARQL" user "SPARQL_UPDATE" privileges (required if you want to exploit the in-built Sponger Middleware)</li> <li>Click on the <a href="http://dbpedia.org/resource/OpenLink_Data_Spaces">ODS</a> (OpenLink Data Spaces) link to start an Personal Editon of OpenLink Data Spaces (or go to: http://your-ec2-instance-cname/dataspace/ods/index.html)</li> <li>Log-in using the username and password credentials for the 'dav' account (or register a new user note: OpenID is an option here also) Create an Data Space Application Instance by clicking on a Data Space App. Tab</li> <li>Import data from your existing Web 2.0 style applications into OpenLink Data Spaces e.g. subscribe to a few RSS/Atom feeds via the "Feeds Manager" application or import some Bookmarks using the "Bookmarks" application</li> <li>Then look at the imported data in Linked Data form via your ODS generated URIs based on the patterns: http://your-ec2-instance-cname/dataspace/person/your-ods-id#this (URI for You the Person), http://your-ec2-instance-cname/dataspace/person/your-ods-id (FOAF File URI), http://your-ec2-instance-cname/dataspace/your-ods-id (SIOC File URI)<br /> </li> </ol> <h2> (OAT) from your Data Space instance</h2>Install the OAT VAD package via the Admin UI and then apply the URI patterns below within your browser:<br /> <ol> <li>http://<public_dns_name_of_your_instance>:8890/oatdemo - Entire OAT Demo Collection</public_dns_name_of_your_instance> </li> <li>http://<public_dns_name_of_your_instance>:8890/rdfbrowser - RDF Browser</public_dns_name_of_your_instance> </li> <li>http://<public_dns_name_of_your_instance>:8890/isparql - SPARQL Query Builder (iSPARQL)</public_dns_name_of_your_instance> </li> <li>http://<public_dns_name_of_your_instance>:8890/qbe - SQL Query Builder (iSQL)</public_dns_name_of_your_instance> </li> <li>http://<public_dns_name_of_your_instance>:8890/formdesigner - Forms Builder (for building Meshups based on RDF, SQL, or Web Servives Data Souces)</public_dns_name_of_your_instance> </li> <li>http://<public_dns_name_of_your_instance>:8890/dbdesigner - SQL DB Schema Designer (note a Visual SQL-RDF Mapper is also on it's way</public_dns_name_of_your_instance> </li> <li>http://<public_dns_name_of_your_instance>:8890/DAV/JS/ - To view the OAT Tree (there are some experimental demos that are missing from the main demo app etc..) </public_dns_name_of_your_instance> </li> </ol> <p>There's more to come!</p>
Yet Another RDFa Demo
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2007-09-03#1249
2007-09-03T17:59:02Z
2008-02-04T20:44:37.000009-05:00
<p> <a href="http://www.ivan-herman.net/Ivan_Herman">Ivan Herman</a> just posted another nice example of practical <a href="http://dbpedia.org/resource/RDFa">RDFa</a> usage in a blog post titled: <a href="http://ivanherman.wordpress.com/2007/09/03/yet-another-rdfa-processor…/">Yet Another RDFa Proccessor</a>. In his post, Ivan exposes a <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier">URI</a> for his<a href="http://www.ivan-herman.net/foaf.html"> FOAF-in-RDFa file</a>.</p> <p>Since I am <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1243">aggressively tracking RDFa developments</a>, I decided to quickly view <a href="http://demo.openlinksw.com/DAV/home/demo/Public/Queries/DataWeb/ivan_herman_foaf_via_rdfa.wqx">Ivan's FOAF-in-RDFa file via the OpenLink RDF Browser</a>. The full implications are best understood when you click on each of the Browser's Tabs -- each providing a different perspective on this interesting addition to the Semantic Data Web (note: the <a href="http://www.w3.org/2005/04/fresnel-info/">Fresnel</a> Tab which demonstrates declarative UI templating using N3).</p> <h3>What's Going on Here?</h3> <p>The <a href="http://demo.openlinksw.com/DAV/JS/rdfbrowser/index.html">OpenLink RDF Browser</a> is a <a href="http://en.wikipedia.org/wiki/Rich_internet_application">Rich Internet Application</a> built using OAT (<a href="http://oat.openlinksw.com">OpenLink Ajax Toolkit</a>). In my case, I am deploying the RDF Browser from a <a href="http://virtuoso.openlinksw.com">Virtuoso</a> instance, which implies that the Browser is able to use the <a href="http://www.openlinksw.com/blog/~kidehen/?id=1172">Virtuoso Sponger</a> Middleware (exposed as a REST Service at the Virtuoso instance endpoint: /proxy); which includes an RDFa Cartridge comprised of a metadata extractor and an <a href="http://dbpedia.org/resource/RDF_Schema">RDF Schema</a> / <a href="http://dbpedia.org/resource/Web_Ontology_Language">OWL Ontology</a> mapper. That's it!</p>
Enterprise 0.0, Linked Data, and Semantic Data Web
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2007-06-14#1224
2007-06-14T15:28:26Z
2008-02-04T23:19:26.000001-05:00
<p>Last week we <a href="http://www.openlinksw.com/press/virt_501.htm">officially released Virtuoso 5.0.1</a> (in Commercial and Open Source Editions). The press release provided us with an official mechanism and timestamp for the current Virtuoso feature set.</p> <p>A vital component of the new Virtuoso release is the finalization of our SQL to RDF mapping functionality -- enabling the declarative mapping of SQL Data to RDF. Additional technical insight covering other new features (delivered and pending) is provided by <a href="http://www.openlinksw.com/weblogs/oerling/">Orri Erling</a>, as part of a series of post-Banff posts.</p> <h2>Why is SQL to RDF Mapping a Big Deal?</h2> <p>A majority of the world's data (especially in the enterprise realm) resides in SQL Databases. In addition, Open Access to the data residing in said databases remains the biggest challenge to enterprises for the following reasons:</p> <ol> <li> SQL Data Sources are inherently heterogeneous because they are acquired with business applications that are in many cases inextricably bound to a particular DBMS engine </li> <li> Data is predictably dirty </li> <li> DBMS vendors ultimately hold the data captive and have traditionally resisted data access standards such as ODBC (*trust me they have, just look at the unprecedented bad press associated with ODBC the only truly platform independent data access API. Then look at how this bad press arose..*) </li> </ol> <p> Enterprises have known from the beginning of modern corporate times that data access, discovery, and manipulation capabilities are inextricably linked to the "Real-time Enterprise" nirvana (hence my use of 0.0 before this becomes 3.0).</p> <p>In my experience, as someone whose operated in the data access and data integration realms since the late '80s, I've painfully observed enterprises pursue, but unsuccessfully attain, full control over enterprise data (the prized asset of any organization) such that data-, information-, knowledge-workers are just a click away from commencing coherent platform and database independent data drill-downs and/or discovery that transcend intranet, internet, and extranet boundaries -- serendipitous interaction with relevant data, without compromise!</p> <p>Okay, situation analysis done, we move on.. </p> <p>At our most recent (<a href="http://esw.w3.org/topic/CambridgeSemanticWebGatherings/Meeting/2007-06-12_Gathering">12th June</a>) monthly <a href="http://esw.w3.org/topic/CambridgeSemanticWebGatherings">Semantic Web Gathering</a>, I unveiled to <a href="http://www.w3.org/People/Berners-Lee/card#i">TimBL</a> and a host of other attendees a simple, but powerful, demonstration of how <a href="http://en.wikipedia.org/wiki/Linked_Data">Linked Data</a>, as an aspect of the <a href="http://www.businessweek.com/technology/content/apr2007/tc20070409_961951.htm">Semantic Data Web</a>, can be applied to enterprise data integration challenges.</p> <h2>Actual SQL to RDF Mapping Demo / Experiment</h2> <h4>Hypothesis</h4> A SQL Schema can be effectively mapped declaratively to RDF such that SQL Rows morph into RDF Instance Data (Entity Sets) based on the Concepts & Properties defined in a Concrete Conceptual Data Model oriented Data Dictionary (<a href="http://www.w3schools.com/rdf/rdf_schema.asp">RDF Schema</a> and/or <a href="http://www.w3schools.com/rdf/rdf_owl.asp">OWL Ontology</a>). In addition, the solution must demonstrate how "Linked Data in the Web" is completely different from "Data on the Web" or "Linked Data on the Web" (btw - <a href="http://kasei.us/people/Tom_Heath/">Tom Heath</a> eloquently unleashed this point in his recent <a href="http://blogs.talis.com/nodalities/2007/06/tom_heath_talks_with_talis_abo.php">podcast interview with Talis</a>). <h4>Apparatus</h4> An Ontology - in this case we simply derived the <a href="http://demo.openlinksw.com/DAV/home/demo/Public/Queries/SQLRDFIntegraton/Explore_Northwind_Ontology.isparql">Northwind Ontology</a> from the XML Schema based CSDL (<a href="http://blogs.msdn.com/adonet/archive/2007/01/30/entity-data-model-part-1.aspx">Conceptual Schema Definition Language</a>) used by Microsoft's public <a href="http://astoria.mslivelabs.com/Default.aspx">Astoria demo</a> (specifically the <a href="http://astoria.mslivelabs.com/termsOfUseNorthwind.aspx?returnURL=Northwind">Northwind Data Services demo</a>). SQL Database Schema - <a href="http://www.microsoft.com/library/media/1033/technet/images/prodtechnol/sql/2000/maintain/sscpop07_big.gif">Northwind</a> (comes bundled with ACCESS, SQL Server, and Virtuoso) comprised of tables such as: <a href="http://www.openlinksw.com/schemas/northwind#Customer">Customer</a>, <a href="http://www.openlinksw.com/schemas/northwind#Employee">Employee</a>, <a href="http://www.openlinksw.com/schemas/northwind#Product">Product</a>, <a href="http://www.openlinksw.com/schemas/northwind#Category">Category</a>, <a href="http://www.openlinksw.com/schemas/northwind#Supplier">Supplier</a>, <a href="http://www.openlinksw.com/schemas/northwind#Shipper">Shipper</a> etc. <a href="http://www.openlinksw.com/virtuoso/">OpenLink Virtuoso</a> - SQL DBMS Engine (although this could have been any <a href="http://en.wikipedia.org/wiki/Open_Database_Connectivity">ODBC</a> or <a href="http://en.wikipedia.org/wiki/Java_Database_Connectivity">JDBC</a> accessible Database), <a href="http://www.openlinksw.com/virtuoso/Whitepapers/pdf/Virtuoso_SQL_to_RDF_Mapping.pdf">SQL-RDF Metaschema Language</a>, HTTP URL-rewriter, WebDAV Engine, and DBMS hosted XSLT processor Client Tools -<a href="http://demo.openlinksw.com/isparql/"> iSPARQL Query Builder</a>, <a href="http://demo.openlinksw.com/DAV/JS/rdfbrowser/index.html">RDF Browser</a> (which could also have been <a href="http://www.w3.org/2005/ajar/tab">Tabulator</a> or<a href="http://sites.wiwiss.fu-berlin.de/suhl/bizer/ng4j/disco/"> DISCO</a> or a standard Web Browser) <h4>Experiment / Demo</h4> <ol> <li> Declaratively map the Northwind SQL Schema to RDF using the Virtuoso Meta Schema Language (see: <a href="http://demo.openlinksw.com/DAV/home/demo/Public/Queries/SQLRDFIntegraton/northwind_sql_rdf.sql">Virtuoso PL based Northwind_SQL_RDF script</a>) </li> <li> Start browsing the data by clicking on the URIs that represent the RDF Data Model Entities resulting from the SQL to RDF Mapping </li> </ol> <h4>Observations</h4> <ol> <li> Via a single Data Link click I was able to obtain specific information about the Customer represented by the URI <a href="http://demo.openlinksw.com/Northwind/Customer/ALFKI">"ALFKI"</a> (act of URI Dereferencing as you would an Object ID in an Object or Object-Relational Database) </li> <li> Via a <a href="http://demo.openlinksw.com/DAV/home/demo/Public/Queries/SQLRDFIntegraton/Explore_Northwind.isparql">Dynamic Data Page </a> I was able to explore all the entity relationships or specific entity data (i.e Exploratory or Entity specific dereferencing) in the Northwind Data Space </li> <li> I was able to perform similar exploration (as per item 2) using our <a href="http://demo.openlinksw.com/DAV/home/demo/Public/Queries/SQLRDFIntegraton/Explore_Northwind_Customer_ALFKI.wqx">OpenLink Browser. </a> </li> </ol> <h4>Conclusions</h4> <p>The vision of data, information, or knowledge at your fingertips is nigh! Thanks to the infrastructure provided by the Semantic Data Web (URIs, <a href="http://en.wikipedia.org/wiki/Resource_Description_Framework">RDF Data Model</a>, variety of RDF Serialization Formats[<a href="http://www.dajobe.org/2004/01/turtle/">1</a>][<a href="http://www.w3.org/DesignIssues/Notation3">2</a>][<a href="http://www.w3.org/TR/2002/WD-rdf-syntax-grammar-20020325/">3</a>], and Shared Data Dictionaries / Schemas / Ontologies [<a href="http://xmlns.com/foaf/spec/">1</a>][<a href="http://rdfs.org/sioc/spec/">2</a>][<a href="http://www.w3.org/TR/swbp-skos-core-guide/">3</a>][<a href="http://musicontology.com/">4</a>][<a href="http://bblfish.net/work/atom-owl/2006-06-06/AtomOwl.html">5</a>]) it's now possible to Virtualize enterprise data from the Physical Storage Level, through the Logical Data Management Levels (Relational), up to a Concrete Conceptual Model (Graph) without operating system, development environment or framework, or database engine lock-in.</p> <h2>Next Steps</h2> <p>We produce a shared ontology for the CRM and Business Reporting Domains. I hope this experiment clarifies how this is quite achievable by converting XML Schemas to RDF Data Dictionaries (RDF Schemas or Ontologies). Stay tuned :-) </p> <p>Also watch <a href="http://news.com.com/1606-2-6189377.html">TimBL amplify and articulate Linked Data value</a> in a recent interview.</p> <h2>Other Related Matters</h2> <p>To deliver a mechanism that facilitates the crystallization of this reality is a contribution of boundless magnitude (as we shall all see in due course). Thus, it is easy to understand why even "her majesty", the queen of England, simply had to get in on the act and <a href="http://www.royal.gov.uk/output/Page1880.asp">appoint TimBL to the "British Order of Merit</a>" :-)</p> <p>Note: All of the demos above now work with IE & Safari (a "remember what Virtuoso is epiphany") by simply putting Virtuoso's DBMS hosted XSLT engine to use :-) This also applies to my earlier collection of demos from the <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=hello%20data%20web&type=text&output=html">Hello Data Web</a> and other <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=.isparql&type=text&output=html">Data Web & Linked Data related demo style posts</a>.</p>
Shared Ontologies Linked Data Style!
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2007-05-25#1203
2007-05-25T21:12:36Z
2007-06-01T19:54:05.000001-04:00
<p>As the <a href="http://blogs.talis.com/nodalities/2007/05/linked_data_the_real_semantic.php">Linked Data meme</a> beams across the Web, it is important to note that Ontology / Schema sharing and reuse is critical to the overall vitality of the burgeoning Semantic Data Web.</p> <p>The items that follow attempt to demonstrate the point by way of SIOC (<a href="http://rdfs.org/sioc/spec/">Semantically-Interlinked Online Communities Ontology</a>) and MO (<a href="http://musicontology.com/">Music Ontology</a>) domain exploration:</p> <p> <b>Linked Data or Dynamic Data Web Pages</b>:</p> <ol> <li> <a href="http://dbpedia.openlinksw.com:8890/DAV/home/demo/dataweb/linked_data_pages/music_ontology_overview.isparql">Music Ontology Overview</a> </li> <li> <a href="http://dbpedia.openlinksw.com:8890/DAV/home/demo/dataweb/linked_data_pages/sioc_ontology_overview.isparql">SIOC Ontology Overview</a> </li> <li> <a href="http://dbpedia.openlinksw.com:8890/DAV/home/demo/dataweb/linked_data_pages/sioc_types_ontology_module.isparql">SIOC Type Ontology Module</a> (how you extend SIOC Concepts unobtrusively)</li> <li> <a href="http://dbpedia.openlinksw.com:8890/DAV/home/demo/dataweb/linked_data_pages/sioc_services_ontology_overview.isparql">SIOC Services Ontology Module</a> (how you extend SIOC in relation to Services Modeling).</li> </ol> <p> <b>Semantic Web Browser Sessions</b>:</p> <ol> <li> <a href="http://dbpedia.openlinksw.com:8890/DAV/home/demo/dataweb/browser_sessions/exploring_music_the_ontology.wqx">Music Ontology Overview via OpenLink RDF Browser</a> </li> <li> <a href="http://dbpedia.openlinksw.com:8890/DAV/home/demo/dataweb/browser_sessions/exploring_sioc.wqx">SIOC Ontology Overview via OpenLink RDF Browser</a> </li> <li> <a href="http://dbpedia.openlinksw.com:8890/DAV/home/demo/dataweb/browser_sessions/exploring_sioc_types_modules.wqx">SIOC Type Ontology Module </a>via OpenLink RDF Browser<br /> </li> <li> <a href="http://dbpedia.openlinksw.com:8890/DAV/home/demo/dataweb/browser_sessions/exploring_sioc_services.wqx">SIOC Services Ontology Module </a>via OpenLink RDF Browser.</li> </ol> <p>Key point, if you are modeling People, Communities, Organizations, Documents, and other entities in the People, Organizations, Documents etc. Data Space, don't forget to : FOAF-FOAF-FOAF it Up! :-)</p>
Exploring FOAF Linked Data Style!
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2007-05-25#1202
2007-05-25T15:41:35Z
2007-05-25T14:36:47-04:00
<p>Over the last few hours the FOAF project received a <a href="http://dannyayers.com/2007/05/25/foaf-0">wakeup call</a> via <a href="http://danbri.org/">Dan Brickley</a>'s <a href="http://xmlns.com/foaf/spec">FOAF 0.9</a> "touch" effort.</p> <p>Naturally, this triggered an obvious opportunity to demonstrate the prowess of <a href="http://en.wikipedia.org/wiki/Linked_Data">Linked Data</a> on the Semantic Web. What follows is a quick dump of what I sent to the <a href="http://lists.foaf-project.org/mailman/listinfo/foaf-dev">foaf-dev</a> mailing list:</p> <p>Here are variety of FOAF Views built using:</p> <ul> - <a href="http://dbpedia.openlinksw.com:8890/DAV/JS/rdfbrowser/index.html">OpenLink RDF Browser</a> </ul> <ul> - <a href="http://dbpedia.openlinksw.com:8890/isparql">Interactive SPARQL QBE </a> </ul> <ul> - <a href="http://dbpedia.openlinksw.com:8890/sparql">Raw SPARQL Endpoint</a> </ul> <p>Enabling you to explore the following lines:</p> <ul> - <a href="http://dbpedia.openlinksw.com:8890/DAV/home/demo/dataweb/linked_data_pages/foaf_overview.isparql">FOAF Overview via a Linked Data Page</a> (same as Dynamic Data Page) </ul> <ul> - <a href="http://dbpedia.openlinksw.com:8890/DAV/home/demo/dataweb/linked_data_pages/foaf_overview_by_status.isparql">FOAF Overview by Term Status via Linked Data Page</a> </ul> <ul> - <a href="http://dbpedia.openlinksw.com:8890/DAV/home/demo/dataweb/queries/foaf_overview.rq">FOAF Overview SPARQL Query (.rq File)</a> </ul> <ul> - <a href="http://dbpedia.openlinksw.com:8890/DAV/home/demo/dataweb/queries/foaf_overview_by_status.rq">FOAF Overview by Term Status</a> </ul> <ul> - <a href="http://tinyurl.com/2hpeau">FOAF Overview via OpenLink RDF Browser</a> </ul>
Data Web, Googlebase, and Yahoo!
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2007-03-22#1165
2007-03-22T23:04:21Z
2007-03-22T19:14:55-04:00
<p>A defining characteristic of the Data Web (Context Oriented Web 3.0) is that it facilitates Meshups rather than Mashups.</p> <p>Quick Definitions:</p> <ul> Mashups - Brute force joining of disparate Web Data</ul> <ul> Meshups - Natural joining of disparate Web Data </ul> <p> Reasons for the distinction:</p> <ul>Mashups are Data Model oblivious.</ul> <ul>Meshups are Data Model driven.</ul> <p>Examples:</p> <ul> Mashups are based on RSS 2.0 most of the time (RSS 2.0 is at best a Tree Structure that contains untyped or meaning challenged links.</ul> <ul> Meshups are RDF based and the data is self describing since the links are typed (posses inherent meaning thereby providing context).</ul> <p>So what? You may be thinking.</p> <p>For starters, I can quite easily Mesh data from Googlebase (which emits RSS 2.0 or Atom) and other data sources with the Mapping Services from Yahoo!</p> <p>I can achieve this in minutes without writing a single line of code. I can do it because of the Data Model prowess of RDF (self-describing instance-data), the data interchange and transformation power of XML and XSLT respectively, the inherent power of XML based Web Services (REST or SOAP), and of course, having a Hybrid Server product like <a href="http://en.wikipedia.org/wiki/Virtuoso_Universal_Server">Virtuoso</a> at my disposal that delivers a cross platform solution for exploiting all of these standards coherently.</p> <p>I can share the self-describing describing data source that serves my Meshup. Try reusing the data presented by a Mashup via the same URL that you used to locate Mashup to get my drift.</p> <p>Demo Links:</p> <ol> <li> <a href="http://demo.openlinksw.com/DAV/JS/rdfbrowser/index.html#http%3A%2F%2Fdemo.openlinksw.com%2FDAV%2Fhome%2Fdemo%2FPublic%2FQueries%2FDataWeb%2Fgoogle_base_jobs_dataspace.isparql">Googlebase Query URL as an RDF Data Source</a> </li> <li>Perform a simple Data Mesh by adding (via link copy and paste) this <a href="http://upcoming.org/search/?q=ajax&scope=allmetros&type=Events">Upcoming.org Query Services URL for Ajax Events</a> to the RDF Browsers list of Data Sources (paste into the Data Source URI input field).</li> </ol> <p>What does this all mean?</p> <p>"Context" is the catalyst of the burgeoning Data Web (Semantic Web Layer - 1). It's the <a href="http://sramanamitra.com/blog/729">emerging appreciation of "Context"</a> that is driving the growing desire to increment Web versions from 2.0 to 3.0. It also the the very same "Context" that has been a preoccupation of <a href="http://www.w3.org/2001/sw/Activity">Semantic Web vision</a> since its inception.</p> <p>The journey towards a more Semantic Web is all inclusive (all "ANDs" and no "ORs" re. participation).</p> <p>The Semantic Web is <a href="http://www.openlinksw.com/blog/~kidehen/?id=887">self-annotating</a>. Web 2.0 has provided a huge contribution to the self annotation effort: on the Web we now have Data Spaces for Bookmarks (e.g del.icio.us), Image Galleries ( e.g Flickr), Discussion Forums (remember those comments associated with blog posts? ditto the pingbacks and trackbacks?), People Profiles (FOAF, XFN, del.icio.us, and those crumbling walled-gardens around many Social Networks), and more..</p> <p>A Web without granular access to Data is simply not a Web worth having (think about the menace of click-fraud and spam).</p>
SPARQL and Full Text Indexing implementations are growing
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2007-03-09#1157
2007-03-09T23:50:29Z
2007-03-13T06:09:43-04:00
<p> <a href="http://en.wikipedia.org/wiki/Virtuoso_Universal_Server">Virtuoso</a> joins <a href="http://wingerz.com/blog/2007/02/06/text-indexing-and-query-in-boca/">Boca</a> and <a href="http://seaborne.blogspot.com/2006/11/larq-lucene-arq.html">ARC 2.0</a> as RDF Quad or Triple Stores with Full Text Index extensions to SPARQL. Here is our example applied to <a href="http://dbpedia.org">DBpedia</a>:</p> <pre><font size="2">PREFIX dbpedia: <http://dbpedia.org/> PREFIX foaf: <http://xmlns.com/foaf/0.1/> PREFIX xsd: <http://www.w3.org/2001/XMLSchema#> SELECT ?name ?birth ?death FROM <http://dbpedia.org> WHERE { ?person dbpedia:birthplace <http://dbpedia.org/resource/Berlin> . ?person dbpedia:birth ?birth . ?person foaf:name ?name . ?person dbpedia:death ?death FILTER (?birth < "1900-01-01"^^xsd:date and bif:contains (?name, 'otto')) . } ORDER BY ?name </font></pre> <p> You can test further using our <a href="http://demo3.openlinksw.com:8890/sparql/">SPARQL Endpoint for DBpedia</a> or via the <a href="http://demo3.openlinksw.com:8890/isparql/">DBPedia bound Interactive SPARQL Query Builder</a> or just click *<a href="http://demo3.openlinksw.com:8890/sparql/?default-graph-uri=&query=PREFIX+dbpedia%3A+%3Chttp%3A%2F%2Fdbpedia.org%2F%3E%0D%0APREFIX+foaf%3A+%3Chttp%3A%2F%2Fxmlns.com%2Ffoaf%2F0.1%2F%3E%0D%0APREFIX+xsd%3A+%3Chttp%3A%2F%2Fwww.w3.org%2F2001%2FXMLSchema%23%3E%0D%0ASELECT+%3Fname+%3Fbirth+%3Fdeath%0D%0AFROM+%3Chttp%3A%2F%2Fdbpedia.org%3E%0D%0AWHERE+%7B%0D%0A++++%3Fperson+dbpedia%3Abirthplace+%3Chttp%3A%2F%2Fdbpedia.org%2Fresource%2FBerlin%3E+.%0D%0A++++%3Fperson+dbpedia%3Abirth+%3Fbirth+.%0D%0A++++%3Fperson+foaf%3Aname+%3Fname+.%0D%0A++++%3Fperson+dbpedia%3Adeath+%3Fdeath%0D%0A++++FILTER+%28%3Fbirth+%3C+%221900-01-01%22%5E%5Exsd%3Adate+and+bif%3Acontains+%28%3Fname%2C+%27otto%27%29%29+.%0D%0A%7D%0D%0AORDER+BY+%3Fname&format=text%2Fhtml">Here</a>* for results courtesy of the <a href="http://www.w3.org/TR/rdf-sparql-protocol/">SPARQL Protocol</a> (REST based Web Service). </p> <p>Note: This is in-built functionality as Virtuoso has possessed <a href="http://en.wikipedia.org/wiki/Full_text_index">Full Text Indexing</a> since 1998-99. This capability applies to physical and virtual graphs managed by Virtuoso.</p> <p>A per usual, there is more to come as we now have a nice intersection point for SPARQL and XQuery/XPath since Triple Objects (the Literal variety) can take the form of XML Schema based Complex Types :-) A point I alluded too in my <a href="http://weblog.infoworld.com/udell/2006/04/28.html">podcast interview with Jon Udell </a>last year (*note: mechanical turk based transcript is bad*). The point I made went something like this: "...you use SPARQL to traverse the typed links and then use XPath/XQuery for further granular access to the data if well-formed..."</p> <p>Anyway, the podcast interview lead to this InfoWorld article titled: <a href="http://www.infoworld.com/article/06/05/03/77873_19OPstrategic_1.html">Unified Data Theory</a>.<br /> </p>
Personal URIs & Data Spaces
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2007-03-01#1148
2007-03-01T19:42:41Z
2007-03-02T09:14:02.000004-05:00
<blockquote> <p> <a href="http://www.johnbreslin.com/blog/2007/03/01/linking-personal-posted-content-across-communities/#comments">Linking personal posted content across communities</a>: "</p> <p>With the help of Kingsley, Uldis and I have been looking at how <a href="http://sioc-project.org/">SIOC</a> can be used to link the content that a single person posts to a number of community sites. The picture below shows an example of stuff that Iâve created on Flickr, YouTube, etc. through my various user identities on those sites (these match some <a href="http://wiki.sioc-project.org/index.php/TypesModule">SIOC types</a> that we want to add to a separate module). We can also say that each Web 2.0 content item is a user-contributed post, with some attached or embedded content (e.g. a file or maybe just some metadata). This is part of a new discussion on the <a href="http://groups.google.com/group/sioc-dev">sioc-dev</a> mailing list, and weâd value your contributions.</p> <p> <img id="image1178" src="http://www.johnbreslin.com/blog/wp-content/uploads/2007/03/20070228a.png" alt="20070228a.png" /> </p> <p>Edit: The inner layer is a person (semantically described in FOAF), the next layer is their user accounts (described in FOAF, SIOC) and the outer layer is the posted content - text, files, associated metadata - on community sites (again described using SIOC). </p> No Tags" <p>(Via <a href="http://www.johnbreslin.com/blog">John Breslin - Cloudlands</a>.)</p> </blockquote> <p>The point that John is making about the Data Web and Interlinked <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q='data%20spaces'&type=text&output=html">Data Spaces</a> exposed via <a href="http://en.wikipedia.org/wiki/Uniform_Resource_Identifier">URI</a>s (e.g Personal URIs), crystallizes a number of very important issues about the Data Web that may remain unclear. I am hoping that by digesting the post excerpt above, in conjunction with the items below, aids the pursuit of clarity and comprehension about the all important Data Web (Semantic Web - Layer 1):</p> <ol> <li> <a href="http://kidehen.idehen.net/dataspace/kidehen">Your OpenID can be Your Personal URI</a> (as noted by <a href="http://blogs.sun.com/bblfish/">Henry Story</a>'s post about: <a href="http://blogs.sun.com/bblfish/entry/openid_for_blogs_sun_com">The Many Uses of OpenID</a>). That that's what I have courtesy of OpenLink Data Spaces (ODS)</li> <li>The above only works unobtrusively (i.e. OpenID and Personal sharing a URI) if Content Negotiation is exploited on the Client and Server sides.</li> <li> <a href="http://www.w3.org/People/Berners-Lee/card.rdf">TimBL</a>'s call out to <a href="http://www.w3.org/DesignIssues/LinkedData.html">Share Your Data and Link to Other Data</a> via URIs via post titled: <a href="http://dig.csail.mit.edu/breadcrumbs/node/71">Give Yourself a URI</a>.</li> <li> <a href="http://www.w3.org/TR/swbp-vocab-pub/">W3C's Best Practice Recipes for Publishing RDF Vocabularies</a> </li> <li> <a href="http://www.w3.org/TR/2004/REC-webarch-20041215/#dereference-uri">W3C's Architecture of the World Wide Web - Vol 1</a> which covers URI Dereferencing (HTTP GET-ing the data that a URI points to)</li> <li> <a href="http://www4.wiwiss.fu-berlin.de/is-group/page/persons/Person6">Richard Cyganiak</a>'s post titled: <a href="http://dowhatimean.net/2007/02/debugging-semantic-web-sites-with-curl">Debugging Semantic Web Sites with Curl</a>.</li> </ol> <p>Examples of some of these principles in practice:</p> <ol> <li>Chris Bizer, Tobias Gaub, and Richard's Javascript based<a href="http://sites.wiwiss.fu-berlin.de/suhl/bizer/ng4j/semwebclient/"> Semantic Web Client Library</a> </li> <li> <a href="http://sites.wiwiss.fu-berlin.de/suhl/bizer/ng4j/disco/">DISCO RDF Browser</a> </li> <li> <a href="http://oat.openlinksw.com">OpenLink Ajax Toolkit</a>'s (OAT) <a href="http://demo.openlinksw.com/DAV/JS/tests/rdfbrowser/index.html">RDF Browser</a> </li> <li>OpenLink <a href="http://demo.openlinksw.com/isparql">Interactive SPARQL Query by Example</a> (iSPARQL QBE)</li> <li>Dynamic Data Web Pages from my prior posts [<a href="http://www.openlinksw.com/blog/~kidehen/?id=1144">1</a>][<a href="http://www.openlinksw.com/blog/~kidehen/index.vspx?page=&id=1145">2</a>][<a href="http://www.openlinksw.com/blog/~kidehen/index.vspx?page=&id=1146">3</a>]</li> <li> <a href="http://dbpedia.org/docs/">dbpedia</a> (Wikipedia as a Data Web oriented Data Source)</li> <li>And of course this blog post's permalink is a bona fide dereferencable URI.</li> </ol> <p>And of course there is more to come such as Grandma's Semantic Web Browser which is coming from <a href="http://fgiasson.com/blog/index.php/2007/02/18/zitgist_a_semantic_web_search_engine">Zitgist LLC</a> (pronounced: Zeitgeist) a joint venture of OpenLink Software and <a href="http://fgiasson.com/blog/">Frederick Giasson</a>.</p>
Our Basic Human Instincts
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2007-02-24#1143
2007-02-24T01:03:38Z
2007-02-23T19:55:49-05:00
<p>I just overheard the following dialog between my six year old son and his play date:</p> <blockquote> <pre> Play Date: What is that thing on the Wall? My Son: Security Alarm Play Date: How does it work My Son: If you click on that top button and then open the door, I will have to enter a code when we come back in or the alarm will go off Play Date: What is the code? My Son: I can't tell you that! Play Date: Why not? My Son: You might come and steal something from our house! Play Date: No I won't! My Son: Well, you might tell someone that might come and steal something from our house! or that person could tell someone who could tell someone that would steal from our house</pre></blockquote> <p>LOL!! of course! At the same time wondering, how come a majority of adults don't quite see the need for granular access to Web Data in a manner that enables computers and humans to collectively arrive at similar decisions? </p> <p>Putting Data in context en route to producing actionable knowledge is a transient endeavor that engages a myriad of human senses. We demonstrate comprehension of this fact in our daily existence as social creatures (at a very early age as depicted above). That said, we seem to forget this fact when engaging the Web: If we can't see it then it can't be valuable.</p> <blockquote> <p>BTW - I just received a ping about the "<a href="http://www.flickr.com/photos/route79/399029535/">Sensory Web</a>" (which is just another way of describing a Data Driven Web experience from my vantage point.)</p> </blockquote> <p>In the popular M-V-C pattern you don't see the "M", but the "M" will kill you if you get it wrong (it is the FORCE)! Coming to think about it, the pattern could have been coined: V-C-M or C-M-V, but isn't for obvious reasons :-)</p> <p>RDF is the vehicle that enables us tap into the Data aspect of the Web. We started off with pages of blurb linked via hypertext (Web 1.0) and then looked to "Keywords" for some kind of data access; we then isolated some "Verbs" and discovered another dimension of Web Interaction (Web 2.0) but looked to these "Verbs" for data access which left us with Mashups; and now we are starting to extract "Nouns" and "Adjectives" from sentences (Subject, Predicate, Object - Triples) associated with resources on the Web (Data Web / Web 3.0 / Semantic Web Layer 1) which provides a natural data access substrate for <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=meshups&type=text&output=html">Meshups</a> (natural joining of disparate data from a plethora of data sources) while providing the foundation layer for the <a href="http://en.wikipedia.org/wiki/Semantic_Web">Semantic Web</a>.</p> <p>For those who need use-cases that demonstrate tangible value re. the Semantic Web, here are some projects to note courtesy of the <a href="http://www.w3.org/2001/sw/sweo/">Semantic Web Education and Outreach</a> (SWEO) interest group: </p> <ol> <li> <a href="http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/FOAFWhitelisting">FOAF based White-lists</a> - Attacking SPAM </li> <li> <a href="http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData">Open Data Access and Linking for the Data Web</a> - Data Integration and Generation effort that creates a cluster of RDF instance data from a myriad of data sources relating to every day things such as: People, Places, Events, Projects, Discussions, Music, Books, and other things </li> <li> <a href="http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/PowderExtension">Content Labeling</a> - Protecting our kids on the Web amongst other matters relating to knowledge about data sources </li> <li> <a href="http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects">Others..</a> </li> </ol> Related posts: <ol> <li> <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=rdf%20data%20integration&type=text&output=html">Data Web and Global Data Integration & Generation Effort</a> </li> <li> <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q='data%20web'&type=text&output=html">Previous Data Web posts</a>.</li> </ol>
Semantic Web Data Generation Activity: FOAF Crawling
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2007-01-22#1123
2007-01-22T15:57:31Z
2007-01-22T14:25:48-05:00
<p> <a href="http://fgiasson.com">Frederick Giasson</a> provides compelling data that supports the view that the <a href="http://www.openlinksw.com/blog/~kidehen/?id=1122">Semantic Web bootstrap is a global Data Integration & Data Generation effort</a> that inevitably involves a variety of Data Sources such as: social networks, blogs, wikis etc.</p> <p> The Data in Fred's post is based on <a href="http://fgiasson.com/blog/index.php/2007/01/21/reaching_at_least_600_000_people_with_19">FOAF Ontology instance data generated from a myriad of Data Sources</a>.</p>
Virtuoso's SQL Schema to RDF Ontology Mapping Language (1.0)
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2006-10-18#1064
2006-10-18T22:18:00Z
2006-11-17T18:24:25-05:00
<p>A new technical white paper about our declarative language for SQL Schema to RDF Ontology Mapping has just been published.</p> <h2>What is this?</h2> <p>A declarative language adapted from SPARQL's graph pattern language (N3/Turtle) for mapping SQL Data to RDF Ontologies. We currently refer to this as a Graph Pattern based RDF VIEW Definition Language.</p> <h2>Why is it important?</h2> <p>It provides an effective mechanism for exposing existing SQL Data as virtual RDF Data Sets (Graphs) negating the data duplication associated with generating physical RDF Graphs from SQL Data en route to persistence in a dedicated Triple Store. </p> <p>Enterprise applications (traditional and web based) and most Web Applications (Web 1.0 and Web 2.0) sit atop relational databases, implying that SQL/RDF model and data integration is an essential element of the burgeoning "Data Web" (Semantic Web - Layer 1) comprehension and adoption process.</p> <p>In a nutshell, this is a quick route for non disruptive exposure of existing SQL Data to SPARQL supporting RDF Tools and Development Environments.</p> <h2>How does it work?</h2> <h3>RDF Side</h3> <ol> <li>locate one or more Ontologies (e.g FOAF, SIOC, AtomOWL, SKOS etc.) that effectively defines the Concepts (Classes) and Terms (Predicates) to be exposed via your RDF Graph</li> <li>Using the Virtuoso's RDF View Definition Language declare a International Resource Identifier (or URI) for your Graph. Example:<pre>CREATE GRAPH IRI("http://myopenlink.net/dataspace")</pre> </li> <li>Then create Classes (Concepts), Class Properties/Predicates (Memb), and Class Instances (Inst) for the new Graph. Example: <pre>CREATE IRI CLASS odsWeblog:feed_iri "http://myopenlink.net/dataspace/kidehen/weblog/MyFeeds" ( in memb varchar not null, in inst varchar not null)</pre> </li> </ol> <h3>SQL Side</h3> <ol> <li>If Virtuoso isn't your SQL Data Store, Identify the ODBC or JDBC SQL data source(s) containing the SQL data to be mapped to RDF and then link the relevant tables into Virtuoso's Virtual DBMS Layer</li> <li>Then use the RDF View Definition Language's graph pattern feature to generate SQL to RDF Mapping Template for your Graph. As shown in this <a href="http://www.usnet.private:8889/wiki/main/Main/VOSSQLRDF#MappingOdsBlogToAtomOwlExample">ODS Weblog -> AtomOWL Mapping example</a>.</li> </ol>
Creating connections between discussion clouds with SIOC
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2006-09-07#1036
2006-09-08T00:56:00Z
2008-02-04T23:22:26.000001-05:00
<p>Another example of <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=%27data%20spaces%27&type=text&output=html">Data Spaces</a> in action by <a href="http://www.johnbreslin.com/blog">John Breslin</a>.. In this case John visualizes the connections that are exploitable by creating SIOC (<a href="http://rdfs.org/sioc/">Semantically-Interlinked Online Communities</a>) instance data from existing Distributed Collaborative Application profiles (<a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=web%202.0&type=text&output=html">Web 2.0</a> in current parlance). Of course, SIOC is an Ontology for RDF data since it describes the Concepts and Terms for a a network mesh of online communities. Which by implication provides another insight into the realization that the Web we know has always been a "Web of Databases" (federation of Graph Model Databases encapsulated in Data Spaces). The emergence of <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=sparql%0D%0A&type=text&output=html">SPARQ</a>L as the standard <a href="http://www.w3.org/TR/rdf-sparql-query/">Query Language for querying RDF Data Sets</a>, alongside the SPARQL Protocol for transmitting SPARQL Queries over HTTP, and the SPARQL Query Results Serialization formats (XML or JSON) Results Serialization Format), basically set the stage truly open and flexible data access across Web Data Space clusters such as: the Blogosphere, Wikispehere, Usenetverse, Linkspaces, Boardscapes, and others.</p> <p> For additional clarity re. my comments above, you can also look at the <a href="http://virtuoso.openlinksw.com/wiki/main/Main/ODSSIOCRef">SPARQL & SIOC Usecase samples document</a> for our <a href="http://virtuoso.openlinksw.com/wiki/main/Main/OdsIndex">OpenLink Data Spaces platform</a>. Bottom line, the Semantic Web and SPARQL aren't <a href="http://morenews.blogspot.com/2006/09/myth-of-web-20.html"> BORING.</a> In fact, quite the contrary, since they are essential ingredients of a more powerful Web than the one we work with today!</p> <p>Enjoy the rest of John's post:</p> <blockquote> <p> <a href="http://www.johnbreslin.com/blog/2006/09/07/creating-connections-between-discussion-clouds-with-sioc/#comments">Creating connections between discussion clouds with SIOC</a>: </p> <p>(Extract from our forthcoming <a href="http://blogtalk.net/Main/Program"> BlogTalk</a> paper about browsers for SIOC.)</p> <p> <a class="imagelink" title="20060907b.png" href="http://www.johnbreslin.com/blog/wp-content/uploads/2006/09/20060907a.png"><img id="image515" alt="20060907b.png" src="http://www.johnbreslin.com/blog/wp-content/uploads/2006/09/20060907b.png" /> </a> </p> <p>SIOC provides a unified vocabulary for content and interaction description: a semantic layer that can co-exist with existing discussion platforms. Using SIOC, various linkages are created between the aforementioned concepts, which allow new methods of accessing this linked data, including:</p> <ul> <li> <strong>Virtual Forums</strong>. These may be a gathering of posts or threads which are distributed across discussion platforms, for example, where a user has found posts from a number of blogs that can be associated with a particular category of interest, or an agent identifies relevant posts across a certain timeframe.</li> <li> <strong>Distributed Conversations</strong>. Trackbacks are commonly used to link blog posts to previous posts on a related topic. By creating links in both directions, not only across blogs but across all types of internet discussions, conversations can be followed regardless of what point or URI fragment a browser enters at.</li> <li> <strong>Unified Communities</strong>. Apart from creating a web page with a number of relevant links to the blogs or forums or people involved in a particular community, there is no standard way to define what makes up an online community (apart from grouping the people who are members of that community using FOAF or OPML). SIOC allows one to simply define what objects are constituent parts of a community, or to say to what community an object belongs (using sioc:has_part / part_of): users, groups, forums, blogs, etc.</li> <li> <strong>Shared Topics</strong>. Technorati (a search engine for blogs) and BoardTracker (for bulletin boards) have been leveraging the free-text tags that people associate with their posts for some time now. SIOC allows the definition of such tags (using the subject property), but also enables hierarchial or non-hierarchial topic definition of posts using sioc:topic when a topic is ambiguous or more information on a topic is required. Combining with other Semantic Web vocabularies, tags and topics can be further described using the SKOS organisation system.</li> <li> <strong>One Person, Many User Accounts</strong>. SIOC also aims to help the issue of multiple identities by allowing users to define that they hold other accounts or that their accounts belong to a particular personal identity (via foaf:holdsOnlineAccount or sioc:account_of). Therefore, all the posts or comments made by a particular person using their various associated user accounts across platforms could be identified.</li> </ul> </blockquote>
Data Spaces and Web of Databases
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2006-08-28#1030
2006-08-28T19:38:00Z
2006-09-04T18:58:56.000001-04:00
<p>Note: An updated version of a previously unpublished blog post:</p> <p> Continuing from <a href="http://weblog.infoworld.com/udell/2006/04/28.html">our recent Podcast conversation</a>, Jon Udell sheds further insight into the essence of our conversation via a âStrategic Developerâ column article titled: <a href="http://www.infoworld.com/cgi-bin/redirect?source=rss&url=http://www.infoworld.com/article/06/05/03/77873_19OPstrategic_1.html">Accessing the web of databases</a>. </p> <p> Below, I present an initial dump of a DataSpace FAQ below that hopefully sheds light on the DataSpace vision espoused during my podcast conversation with Jon. </p> <p> What is a DataSpace? <br /> </p> <p>A moniker for Web-accessible atomic containers that manage and expose Data, Information, Services, Processes, and Knowledge. </p> <p> What would you typically find in a Data Space? Examples include: </p> <ul> <li>Raw Data - SQL, HTML, XML (raw), XHTML, RDF etc.<br /> <br /> </li> <li>Information (Data In Context) - XHTML (various microformats), Blog Posts (in RSS, Atom, RSS-RDF formats), Subscription Lists (OPML, OCS, etc), Social Networks (FOAF, XFN etc.), and many other forms of applied XML.</li> </ul> <ul> <li>Web Services (Application/Service Logic) - REST or SOAP based invocation of application logic for context sensitive and controlled data access and manipulation.</li> </ul> <ul> <li>Persisted Knowledge - Information in actionable context that is also available in transient or persistent forms expressed using a Graph Data Model. A modern knowledgebase would more than likely have RDF as its Data Language, RDFS as its Schema Language, and OWL as its Domain Definition (Ontology) Language. Actual Domain, Schema, and Instance Data would be serialized using formats such as RDF-XML, N3, Turtle etc).</li> </ul> <p> How do Data Spaces and Databases differ? <br />Data Spaces are fundamentally problem-domain-specific database applications. They offer functionality that you would instinctively expect of a database (e.g. AICD data management) with the additonal benefit of being data model and query language agnostic. Data Spaces are for the most part DBMS Engine and Data Access Middleware hybrids in the sense that ownership and control of data is inherently loosely-coupled. </p> <p>How do Data Spaces and Content Management Systems differ?<br />Data Spaces are inherently more flexible, they support multiple data models and data representation formats. Content management systems do not possess the same degree of data model and data representation dexterity. </p> <p>How do Data Spaces and Knowledgebases differ?<br />A Data Space cannot dictate the perception of its content. For instance, what I may consider as knowledge relative to my Data Space may not be the case to a remote client that interacts with it from a distance, Thus, defining my Data Space as Knowledgebase, purely, introduces constraints that reduce its broader effectiveness to third party clients (applications, services, users etc..). A Knowledgebase is based on a Graph Data Model resulting in significant impedance for clients that are built around alternative models. To reiterate, Data Spaces support multiple data models. </p> <p> What Architectural Components make up a Data Space? </p> <ul> <li>ORDBMS Engine - for Data Modeling agility (via complex purpose specific data types and data access methods), Data Atomicity, Data Concurrency, Transaction Isolation, and Durability (aka ACID).<br /> <br /> </li> <li>Virtual Database Engine - for creating a single view of, and access point to, heterogeneous SQL, XML, Free Text, and other data. This is all about Virtualization at the Data Access Level.</li> </ul> <ul> <li>Web Services Platform - enabling controlled access and manipulation (via application, service, or protocol logic) of Virtualized or Disparate Data. This layer handles the decoupling of functionality from monolithic wholes for function specific invocation via Web Services using either the SOAP or REST approach.</li> </ul> <br />Where do Data Spaces fit into the Web's rapid evolution?<br />They are an essential part of the burgeoning Data Web / Semantic Web. In short, they will take us from data âMash-upsâ (combining web accessible data that exists without integration and repurposing in mind) to âMesh-upsâ (combining web accessible data that exists with integration and repurposing in mind).<p> Where can I see a DataSpace along the lines described, in action? </p> <p> Just look at my blog, and take the journey as follows: </p> <ul> <li> <a href="http://www.openlinksw.com/blog/%7Ekidehen/">Front Door</a> (Web 1.0)</li> <li>Lounge (Web 2.0) via <a href="http://www.openlinksw.com/GData/127">GData</a> or <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&type=text&kwds=%27semantic+web%27&OpenSearch">OpenSearch</a> </li> <li>Floor Plan via <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/about.rdf">FOAF</a> or <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/sioc.rdf">SIOC</a> RDF Data Sets (Graphs)</li> <li>Rest of the house (beyond Web 2.0) sending <a href="http://virtuoso.openlinksw.com/wiki/main/Main/VOSODSSparqlSamples">SPARQL Queries</a> to a <a href="http://myopenlink.net:8890/sparql/">SPARQL Endpoint</a>.<br /> </li> </ul> <p> What about other Data Spaces? </p> <p> There are several and I will attempt to categorize along the lines of query method available: <br />Type 1 (Free Text Search over HTTP): <br />Google, MSN, Yahoo!, Amazon, eBay, and most Web 2.0 plays . </p> <p> Type 2 (Free Text Search and XQuery/XPath over HTTP) <br />A few blogs and Wikis (Jon Udell's and a few others)</p>Type 3 (RDF Data Sets and SPARQL Queryable):<br /> <ul> <li>  <a href="http://esw.w3.org/topic/SIOC/EnabledSites">SIOC enabled sites</a> (aka points of semantic web presence)<br /> </li> <li>  <a href="http://pingthesemanticweb.com/">PingTheSemantic</a> <br /> </li> </ul>Type 4 (Generic Free Text Search, OpenSearch, GData, XQuery/XPath, and SPARQL):<br />Points of Semantic Web presence such as the Data Spaces at: <br /> <ul> <li> <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com">My Blog Data Space</a> (as stated earlier in this post)<br /> </li> <li> <a href="http://myopenlink.net:8890/dataspace/kidehen@openlinksw.com">My General Data Space</a> - (ditto; note that this is currently experimental)<br /> </li> </ul> <p>What About Data Space aware tools?<br /> <br /> </p> <ul> <li>  <a href="http://demo.openlinksw.com/DAV/JS/oat/index.html/">OpenLink Ajax Toolkit </a>- provides Javascript Control level binding to Query Services such as XMLA for SQL, GData for Free Text, OpenSearch for Free Text, SPARQL for RDF, in addition to service specific Web Services (Web 2.0 hosted solutions that expose service specific APIs)</li> <li>  <a href="http://rdfs.org/sioc/firefox">Semantic Radar </a>- a Firefox Extension</li> <li>  <a href="http://pingthesemanticweb.com/">PingTheSemantic</a> - the Semantic Webs equivalent of Web 2.0's weblogs.com</li> <li>  <a href="http://simile.mit.edu/piggy-bank/">PiggyBank</a> - a Firefox Extension</li> </ul> <p> </p>
Standards as social contracts
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2006-07-04#995
2006-07-04T17:25:51Z
2006-07-04T14:53:48.000001-04:00
<blockquote> <p> <a href="http://www.tnl.net/blog/2006/06/07/standards-as-social-contracts/#comments">Standards as social contracts</a>: "Looking at Dave Winer's efforts in evangelizing OPML, I try to draw some rough lines into what makes a de-facto standard. De Facto standards are made and seldom happen on their own. In this entry, I look back at the history of HTML, RSS, the open source movement and try to draw some lines as to what makes a standard. </p> <p> <a href="http://feeds.tristanlouis.com/~a/TNLnet?a=nXIQUu"><img src="http://feeds.tristanlouis.com/~a/TNLnet?i=nXIQUu" border="0" /> </a> </p> <div class="feedflare"> <a href="http://feeds.tristanlouis.com/~f/TNLnet?a=dklI2jYY"><img src="http://feeds.tristanlouis.com/~f/TNLnet?i=dklI2jYY" border="0" /> </a> <a href="http://feeds.tristanlouis.com/~f/TNLnet?a=HoauA2Ma"><img src="http://feeds.tristanlouis.com/~f/TNLnet?i=HoauA2Ma" border="0" /></a> <a href="http://feeds.tristanlouis.com/~f/TNLnet?a=DxOLN3Br"><img src="http://feeds.tristanlouis.com/~f/TNLnet?i=DxOLN3Br" border="0" /></a> <a href="http://feeds.tristanlouis.com/~f/TNLnet?a=zU2uLdOm"><img src="http://feeds.tristanlouis.com/~f/TNLnet?i=zU2uLdOm" border="0" /></a> </div>" <p>(Via <a href="http://www.tnl.net/blog">Tristan Louis</a>.)</p> </blockquote> <p>I posted a comment to the Tristan Louis' post along the following lines:</p> <p>Analysis is spot on re. the link between de facto standardization and bootstrapping. Likewise, the clear linkage between boostrapping and connected communities (a variation of the social networking paradigm). </p> <p>Dave built a community around a XML content syndication and subscription usecase demo that we know today as the blogosphere. Superficially, one may conclude that Semantic Web vision has suffered to date from a lack a similar bootstrap effort. Whereas in reality, we are dealing with "time and context" issues that are critical to the base understanding upon which a "Dave Winer" style bootstrap for the Semantic Web would occur.</p> <p>Personally, I see the emergence of Web 2.0 (esp. the mashups phenomenon) as the "time and context" seeds from which the Semantic Web bootstrap will sprout. I see shared ontologies such as <a href="http://oplussol5.usnet.private:8893/foaf">FOAF</a> and <a href="http://rdfs.org/sioc/">SIOC</a> leading the way (they are the RSS 2.0's of the Semantic Web IMHO).</p>
SPARQL Parameterized Queries (Virtuoso using SPARQL in SQL)
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2006-05-11#973
2006-05-11T18:54:47Z
2006-06-22T08:56:58-04:00
<h2>SPARQL with SQL (Inline) </h2> <p>Virtuoso extends its SQL3 implementation with syntax for integrating SPARQL into queries and subqueries.Thus, as part of a SQL SELECT query or subquery, one can write the SPARQL keyword and a SPARQL query as part of query text processed by Virtuoso's SQL Query Processor.</p> <h4>Example 1 (basic) : </h4> <p>Using Virtuoso's Command line or the Web Based ISQL utility type in the following (note: "SQL>" is the command line prompt for the native ISQL utility): </p> <pre>SQL> sparql select distinct ?p where { graph ?g { ?s ?p ?o } };</pre> <p>Which will return the following: </p> <blockquote> <pre> p varchar ---------- http://example.org/ns#b http://example.org/ns#d http://xmlns.com/foaf/0.1/name http://xmlns.com/foaf/0.1/mbox ... </pre> </blockquote> <h4>Example 2 (a subquery variation):</h4> <pre>SQL> select distinct subseq (p, strchr (p, '#')) as fragment from (sparql select distinct ?p where { graph ?g { ?s ?p ?o } } ) as all_predicates where p like '%#%' ;</pre> <blockquote> <pre> fragment varchar ---------- #query #data #name #comment ...</pre> </blockquote> <h3>Parameterized Queries:</h3> <p>You can pass parameters to a SPARQL query using a Virtuoso-specific syntax extension. '??' or '$?' indicates a positional parameter similar to '?' in standard SQL. '??' can be used in graph patterns or anywhere else where a SPARQL variable is accepted. The value of a parameter should be passed in SQL form, i.e. this should be a number or an untyped string. An IRI ID can not be passed, but an absolute IRI can. Using this notation, a dynamic SQL capable client (ODBC, JDBC, ADO.NET, OLEDB, XMLA, or others) can execute parametrized SPARQL queries using parameter binding concepts that are common place in dynamic SQL. Which implies that existing SQL applications and development environments (PHP, Ruby, Python, Perl, VB, C#, Java, etc.) are capable of issuing SPARQL queries via their existing SQL bound data access channels against RDF Data stored in Virtuoso. </p> <p>Note: This is the Virtuoso equivalent of a <a href="http://seaborne.blogspot.com/2006/05/parameterized-queries_07.html">recently published example using Jena </a>(a Java based RDF Triple Store).</p> <h3>Example:</h3> <p>Create a Virtuoso Function by execting the following: </p> <pre>SQL> create function param_passing_demo (); { declare stat, msg varchar; declare mdata, rset any; exec ('sparql select ?s where { graph ?g { ?s ?? ?? }}', stat, msg, vector ('http://www.w3.org/2001/sw/DataAccess/tests/data/Sorting/sort-0#int1', 4 ), -- Vector of two parameters 10, -- Max. result-set rows mdata, -- Variable for handling result-set metadata rset -- Variable for handling query result-set ); return rset[0][0]; } </pre> Test new "param_passing_demo" function by executing the following: <br /> <pre>SQL> select param_passing_demo (); </pre> <p>Which returns: </p> <blockquote> <pre> callret VARCHAR _______________________________________________________________________________</pre> <pre>http://www.w3.org/2001/sw/DataAccess/tests/data/Sorting/sort-0#four</pre> <pre>1 Rows. -- 00000 msec.</pre> </blockquote> <h3>Â </h3> <h3>Using SPARQL in SQL Predicates:</h3> <p>A SPARQL ASK query can be used as an argument of the SQL EXISTS predicate.</p> <pre>create function sparql_ask_demo () returns varchar { if (exists (sparql ask where { graph ?g { ?s ?p 4}})) return 'YES'; else return 'NO'; }; </pre> <p> <br /> Test by executing: </p> <pre>SQL> select sparql_ask_demo (); </pre> <p>Which returns:</p> <pre>_________________________ YES</pre>
Swoogle knows how Semantic Web ontologies are used
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2006-04-05#947
2006-04-05T20:00:36Z
2006-06-22T08:56:58-04:00
<p> <a href="http://ebiquity.umbc.edu/blogger/2006/04/04/swoogle-knows-how-semantic-web-ontologies-are-used/">Swoogle knows how Semantic Web ontologies are used</a>: "</p> <div xmlns="http://www.w3.org/1999/xhtml"> <div> <p> <img src="http://swoogle.umbc.edu/images/logo_mini.png" align="right" alt="" /> </p> <p>The <a href="http://dublincore.org/">Dublin Core Metadata Initiative</a> is updating the RDF expression of DC and might add range restrictions to some properties. Mikael Nilsson wondered if we would use the <a href="http://swoogle.umbc.edu/">Swoogle Semantic Web search engine</a> to see what types of values are being used with DC properties.</p> <p>This kind of query is just the ticket for Swoogle. Well, almost. The current web-based interface supports a limited number of query types. Many more can be asked if you use SQL directly to query Swoogle’s underlying databases. We don’t want to provide a direct SQL query service over the main Swoogle database because it’s easy to ask a query that will take a looooooong time to answer and some could even crash the database server. We are planning to put up a second server with a copy of the database and we give <em>Swoogle Power Users</em> (SPUs) access to it.</p> <p>We ran a simple SQL query to generate some initial data for Mikael showing fall of the DC properties. For each one, we list all of the ranges that values were drawn from and the number of separate documents and triples for each combination. For example</p> <table border="1" align="center" cellpadding="6" bgcolor="#E9E9E9"> <tr bgcolor="#333300"> <td> <div align="center"> <font color="#FFFFFF"><strong>Property</strong> </font> </div> </td> <td> <div align="center"> <font color="#FFFFFF"><strong>Range</strong> </font> </div> </td> <td> <div align="center"> <font color="#FFFFFF"><strong>Documents</strong> </font> </div> </td> <td> <div align="center"> <font color="#FFFFFF"><strong>Triples</strong> </font> </div> </td> </tr> <tr> <td>dc:creater</td> <td>rdfs:Literal</td> <td> <div align="right">32</div> </td> <td> <div align="right">648</div> </td> </tr> <tr> <td>dc:creator</td> <td>rdfs:Literal</td> <td> <div align="right">234655</div> </td> <td> <div align="right">2477665</div> </td> </tr> <tr> <td>dc:creator</td> <td>wn:Person</td> <td> <div align="right">2714</div> </td> <td> <div align="right">1138250</div> </td> </tr> <tr> <td>dc:creator</td> <td>cc:Agent</td> <td> <div align="right">4090</div> </td> <td> <div align="right">6359</div> </td> </tr> <tr> <td>dc:creator</td> <td>foaf:Person</td> <td> <div align="right">2281</div> </td> <td> <div align="right">5969</div> </td> </tr> <tr> <td>dc:creator</td> <td>foaf:Agent</td> <td> <div align="right">1723</div> </td> <td> <div align="right">3234</div> </td> </tr> </table> <p>Notice that the first property in this partial table is an obvious typo. You can see the complete table as <a href="http://www.csee.umbc.edu/~finin/noindex/dc/dcPropertiesRanges.pdf"> pdf</a> file or as an excel <a href="http://www.csee.umbc.edu/~finin/noindex/dc/dcPropertiesRanges.xls"> spreadsheet</a>.</p> <p>[Tim Finin, UMBC ebiquity lab]</p> </div> </div>" <p>(Via <a href="http://planetrdf.com/">Planet RDF</a>.)</p>
This Week’s Semantic Web
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2005-11-14#902
2005-11-14T19:44:03Z
2006-06-22T08:56:58-04:00
<p>(Via <a href="http://dannyayers.com">Danny Ayers</a>.):</p> <p><a href="http://dannyayers.com/archives/2005/11/13/this-weeks-semantic-web/">This Weekâs Semantic Web</a>: </p><p>"Ok, my first attempt at a round-up (in response to Philâs observation of <a href="http://weblog.philringnalda.com/?p=1008">Planetary damage</a>). Thanks to the conference thereâs loads more here than thereâs likely to be subsequent weeks, although itâs still only a fairly random sample and some of the links here are to heaps of other resourcesâ¦<br /> <em>Incidentally, if anyoneâs got a list/links for SemWeb-related blogs that arenât on <a href="http://planetrdf.com">Planet RDF</a>, Iâd be grateful for a pointer. PS. Ok, I forget⦠are there any blogs that arenât on Daveâs <a href="http://journal.dajobe.org/journal/2003/07/semblogs/">list</a> yet..?</em></p> <p>Quote of the week:</p> <blockquote><p> In the Semantic Web, it is not the Semantic which is new, it is the Web which is new. </p></blockquote> <p>- <a href="http://www.research.ibm.com/people/w/welty/">Chris Welty</a>, IBM (lifted from TimBLâs <a href="http://www.w3.org/2005/Talks/1110-iswc-tbl/">slides</a>)</p> <h4>Events</h4> <ul> <li><a href="http://iswc2005.semanticweb.org/">4th International Semantic Web Conference</a> - happened this week, see : <a href="http://simile.mit.edu/conference/iswc2005/">ISWC2005 Semantic Bank</a></li> <li><a href="http://www.gnowsis.org/Events/HackBerlin2005">Semantic Desktop Workshop</a>, 9-13 December 2005, Berlin</li> <li><a href="http://trinity.dit.unitn.it/vikef/swap2005/">Semantic Web Applications and Perspectives/Workshop</a> (SWAP2005), 14-16 December, 2005</li> <li><a href="http://jena.hpl.hp.com/juc2006"> Jena User Conference</a> - May 10-11 2006, Bristol UK</li> </ul> <h4>Docs etc</h4> <ul> <li> Conference highlights on the #swig chump: <a href="http://swig.xmlhack.com/2005/11/06/2005-11-06.html">2005-11-06</a>, <a href="http://swig.xmlhack.com/2005/11/06/2005-11-07.html">-07</a>, <a href="http://swig.xmlhack.com/2005/11/06/2005-11-08.html">-08</a>, <a href="http://swig.xmlhack.com/2005/11/06/2005-11-09.html">-09</a>, <a href="http://swig.xmlhack.com/2005/11/06/2005-11-10.html">-10</a>; Ianâs <a href="http://internetalchemy.org/tag/iswc2005">notes</a>; Johnâs <a href="http://www.johnbreslin.com/blog/2005/11/06/iswc-2005/">resources</a>; Leoâs <a href="http://leobard.twoday.net/topics/SemWeb">stories</a>; Uldisâ <a href="http://captsolo.net/info/blog_a.php/2005/11/12/iswc_2005_do_the_right_thing">call to action</a>; <a href="http://del.icio.us/tag/iswc2005">del.icio.us/iswc2005</a>; <a href="http://www.flickr.com/photos/tags/iswc2005/">flickr/iswc2005</a>; <a href="http://www.foaf-project.org/2004/media/date/2005/11/">foaf-moblog</a>. </li> <li>Slides from Sir TimBLâs conference keynotes: <a href="http://www.w3.org/2005/Talks/1107-iswc-tbl/">Semantic Web for the Industry</a>, <a href="http://www.w3.org/2005/Talks/1110-iswc-tbl/">Putting the Web back in Semantic Web</a></li> <li>Daniel Weitznerâs keynote: <a href="http://www.w3.org/2005/Talks/1110-p4-semweb-iswc/">Privacy, Provenance, Property and Personhood</a></li> <li>Long-time SW researcher <a href="http://www.stefandecker.org">Stefan Decker</a> now has a blog, inspirationally entitled <a href="http://www.stefandecker.org/blog/">Stefan Decker on the Semantic Web</a>. (Stefanâs one of the head honchos at <a href="http://www.deri.ie/">DERI</a>). Sample snippet:<br /> <blockquote><p> I just noticed the article from Dan Zambonini â<a href="http://www.oreillynet.com/pub/wlg/8013?CMP=OTC-TY3388567169">Is Web 2.0 killing the Semantic Web?</a>â. From my perspective the article shows a misconception that people seems to have around the Semantic Web: the Semantic Web effort itself is not provide applications (like the <a href="http://www.oreillynet.com/pub/a/oreilly/tim/news/2005/09/30/what-is-web-20.html">Web 2.0 meme</a> indicates) - it rather provides standards to interlink applications. </p></blockquote> </li> <li>Leigh Dodds has two pieces demonstrating neat facilities offered by <a href="http://jena.sourceforge.net/ARQ">ARQ</a> the SPARQL query API for Java: <a href="http://www.ldodds.com/blog/archives/000251.html">parameterised queries</a> and <a href="http://www.ldodds.com/blog/archives/000252.html">extension functions</a>. </li> <li>A new W3C Working Group has been chartered: <a href="http://www.w3.org/2005/rules/wg/charter">Rule Interchange Format WG</a> - <em>â to produce a core rule language plus extensions which together allow rules to be translated between rule languages and thus transferred between rule systems.â</em>. As noted by <a href="http://journal.dajobe.org/journal/">dajobe</a>, phase 1 includes making a new XML syntax for RDFâ¦</li> <li><a href="http://ebiquity.umbc.edu/resource/html/id/94/">UMBC Semantic Web Reference Card</a> <em>- if you only print one thing this yearâ¦or did you already do the <a href="http://www.dajobe.org/2005/04-sparql/">SPARQL Reference card</a>..?</em></li> <li><a href="http://esw.w3.org/topic/WebDescription">WebDescription</a> - root wiki page for collecting notes on web description languages (ESW Wiki, <a href="http://lists.w3.org/Archives/Public/public-web-http-desc/2005Nov/0000.html">announcement</a>)</li> <li><a href="http://esw.w3.org/topic/Bot">Bot</a> - IRC/Jabber chat bots that are either in use by Semantic Web developers or use Semantic Web technologies (ESW Wiki)</li> <li><a href="http://microformats.org/wiki/faqs-for-rdf">microformat FAQs for RDF fans</a> (ESW Wiki)</li> <li> W3C working draft : <a href="http://www.w3.org/TR/wsdl20-rdf/">WSDL 2.0 - RDF Mapping</a></li> <li>SKOS (Simple Knowledge Organisation System) updated drafts: <a href="http://www.w3.org/TR/swbp-skos-core-spec">SKOS Core Vocabulary Specification</a>, <a href="http://www.w3.org/TR/swbp-skos-core-guide">SKOS Core Guide</a></li> <li>working draft: <a href="http://www.w3.org/TR/sprot11/">SPARQL Protocol for RDF Using WSDL 1.1</a></li> <li><a href="http://www.hpl.hp.com/techreports/2005/HPL-2005-170.html">A relational algebra for SPARQL</a>, <a href="http://www.hpl.hp.com/techreports/2005/HPL-2005-171.html">Note on database layouts for SPARQL datastores</a> (PDFs, Richard Cyganiak, HP)</li> <li><a href="http://eprints.ecs.soton.ac.uk/11042/">Amateur Fiction Online</a> - The Web of Community Trust A Case Study in Community Focused Design for the SemanticWeb (<a href="http://eprints.ecs.soton.ac.uk/11042/01/case_study.pdf">PDF</a>)</li> <li><a href="http://dsonline.computer.org/portal/site/dsonline/menuitem.9ed3d9924aeb0dcd82ccc6716bbe36ec/index.jsp?&pName=dso_level1&path=dsonline/0511&file=x5sem.xml&xsl=article.xsl">Building a Semantic Wiki</a> - IEEE article. See also: <a href="http://m3pe.org/semperwiki/">SemperWiki - Semantic Personal Wiki</a>, <a href="http://wiki.navigable.info/"> WikSAR - Towards a Semantic Wiki Experience</a> <br /> </li> </ul> <h4>Software and stuff</h4> <ul> <li><a href="http://challenge.semanticweb.org/">Semantic Web Challenge</a> applications (winner: <a href="http://www.confoto.org/">CONFOTO</a> - congrats bengee!)</li> <li><a href="http://simile.mit.edu/piggy-bank/">Piggy Bank 2.1.1</a> released.</li> <li> <a href="http://www.openiris.org/">IRIS</a> is a semantic desktop application framework that enables users to create a âpersonal mapâ across their office-related information objects. IRIS includes a machine-learning platform to help automate this process. It provides âdashboardâ views, contextual navigation, and relationship-based structure across an extensible suite of office applications, including a calendar, web and file browser, e-mail client, and instant messaging client.<br /> <em>(open source release due Jan 2006)</em> </li> <li><a href="http://www.mksearch.mkdoc.org/">MKSearch</a> - <em>âA new kind of search engineâ</em> - RDF-backed (Sesame) with Web crawler, extracts and indexes metadata.</li> <li><a href="http://www.foafrealm.org">FOAFRealm</a> - Our goal is to design and implement D-FOAF, a distributed authentication and trust infrastructure without a centralised authority. D-FOAF will be a backbone for trust applications based on social relationships and will establish identity of users similar to the way we establish identify and trust in real life.</li> <li>Perl <a href="http://search.cpan.org/dist/Net-Flickr-RDF-1.1/">Net::Flickr::RDF</a></li> <li>WordPress <a href="http://rdfs.org">SIOC</a> (Semantically-Interlinked Online Communities) plugin updated (just copy <a href="http://sw.deri.org/svn/sw/2005/08/sioc/wordpress/wp-sioc.php">wp-sioc.php</a> into the root of your WP install and it <em>just works</em>)</li> <li><a href="http://ontomedia.ecs.soton.ac.uk/">OntoMedia</a> is intended for the representation of heterogenous media through description of the semantic content of that media. The representation may be limited to the description of some or all of the elements contained within the source or may include information regarding the narrative relationship that these elements have both to the media and to each other.</li> <li><a href="http://mspace.fm/">mSpace</a> is an interaction model to help explore relationships in information - <em>âImagine Google on iTunesâ</em></li> </ul> <p>Blog post title of the week: </p> <blockquote><p> <a href="http://copia.ogbuji.net/blog/2005-11-12/Don_t_give">Donât give me that monkey-ass Web 1.0, either</a> </p></blockquote> <p>- <a href="http://copia.ogbuji.net/blog/">Uche Ogbuji</a></p> <p>Alsoâ¦a new threat to Semantic Web developers has been discovered: <a href="http://planb.nicecupoftea.org/archives/001309.html">typhoid</a>!, and the key to the Webâs full potential isâ¦<a href="http://www.foaf-project.org/2004/media/2005/11/07/3448">Tetris</a>." </p>
Breaking the Web Wide Open!
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2005-10-26#882
2005-10-26T19:28:47Z
2006-06-22T08:56:58-04:00
<p><a href="http://marc.blogs.it/">Marc Canter</a>'s <a href="http://marc.blogs.it/archives/2005/10/breaking_the_we.html">Breaking the Web Wide Open! </a> article is something I found pretty late (by my normal discovery standards). This was partly due to the pre- and post- Web 2.0 event noise levels that have dumped the description of an important industry inflection into the "Bozo Bin" of many. Personally, I think we shouldn't confuse the Web 2.0 traditional-pitch-fest conference with an attempt to identify an important industry inflection).</p><p> Anyway, Marc's article is a very refreshing read because it provides a really good insight into the general landscape of a rapidly evolving Web alongside genuine appreciation of our broader timeless pursuit of "Openness". </p><p>To really help this document provide additional value have scrapped the content of the original post and dumped it below so that we can appreciate the value of the links embedded within the article (note: thanks to Virtuoso I only had to paste the content into my blog, the extraction to my <a href="http://www.openlinksw.com/blog/~kidehen/index.vspx?page=linkblog">Linkblog</a> and <a href="http://www.openlinksw.com/blog/~kidehen/index.vspx?page=summary">Blog Summary</a> Pages are simply features of my <a href="http://www.openlinksw.com/virtuos">Virtuoso </a>based Blog Engine):</p><blockquote><h3 class="hed2" style="padding-bottom: 10px">Breaking the Web Wide Open! (complete story)</h3><p>Even the web giants like AOL, Google, MSN, and Yahoo need to observe these open standards, or they'll risk becoming the "walled gardens" of the new web and be coolio no more.</p><p class="byline"><b><a href="http://community.alwayson-network.com/cgi-bin/WebObjects/AlwaysOn.woa/wa/display?id=9254:Person">Marc Canter</a></b> [<a href="http://community.alwayson-network.com/cgi-bin/WebObjects/AlwaysOn.woa/wa/display?id=9254:Person"><b>Broadband Mechanics, Inc.</b></a>] | POSTED: 09.26.05 @12:00</p><table width="100%" border="0" cellspacing="0" cellpadding="0"><tr><td valign="TOP" class="copy1"><img src="http://community.alwayson-network.com/ao/images/thumb/19433429363e7cd6b1ecfb7.jpg" align="LEFT" border="0" width="80" style="margin: 0px 10px 5px 0px" alt="" /><i><b>Editorial Note:</b> Several months ago, AlwaysOn got a personal invitation from Yahoo founder Jerry Yang "to see and give us feedback on our new social media product, y!360." We were happy to oblige and dutifully showed up, joining a conference room full of hard-core bloggers and new, new media types. The geeks gave Yahoo 360 an overwhelming thumbs down, with comments like, "So the only services I can use within this new network are Yahoo services? What if I don't use Yahoo IM?" In essence, the Yahoo team was booed for being "closed web," and we heartily agreed. With Yahoo 360, Yahoo continues building its own "walled garden" to control its 135 million customersÂan accusation also hurled at AOL in the early 1990s, before AOL migrated its private network service onto the web. As the</i> <a href="http://bernardmoon.blogspot.com/2005/08/yahoos-personality-crisis.html" target="_blank">Economist<i> recently noted</i></a>, "Yahoo, in short, has old media plans for the new-media era."<br /><br />The irony to our view here is, of course, that today's AO Network is also a "closed web." In the end, Mr. Yang's thoughtful invitation and our ensuing disappointment in his new service led to the assignment of this article. It also confirmed our existing plan to completely revamp the AO Network around open standards. To tie it all together, we recruited the chief architect of our new site, <a href="http://www.corante.com/amateur/articles/20030211-3564.html" target="_blank">the notorious Marc Canter</a>, to pen this piece. We look forward to our reader feedback.<br /><br /><b>Breaking the Web Wide Open!</b><br />By Marc Canter<br /><br />For decades, "walled gardens" of proprietary standards and content have been the strategy of dominant players in mainframe computer software, wireless telecommunications services, and the World Wide WebÂit was their successful lock-in strategy of keeping their customers theirs. But like it or not, those walls are tumbling down. Open web standards are being adopted so widely, with such value and impact, that the web giantsÂAmazon, AOL, eBay, Google, Microsoft, and YahooÂare facing the difficult decision of opening up to what they don't control.<br /><br />The online world is evolving into a new open web (sometimes called the Web 2.0), which is all about being personalized and customized for each user. Not only open source software, but <i>open standards</i> are becoming an essential component. <br /><br />Many of the web giants have been using open source software for years. Most of them use at least parts of the <a href="http://www.onlamp.com/pub/a/onlamp/2001/01/25/lamp.html" target="_blank">LAMP</a> (Linux, Apache, MySQL, Perl/Python/PHP) stack, even if they aren't well-known for giving back to the open source community. For these incumbents that grew big on proprietary web services, the methods, practices, and applications of open source software development are difficult to fully adopt. And the next open source movementsÂwhich will be as much about open standards as about codeÂwill be a lot harder for the incumbents to exploit.<br /><br />While the incumbents use cheap open source software to run their back-ends systems, their business models largely depend on proprietary software and algorithms. But our view a new slew of open software, open protocols, and open standards will confront the incumbents with the classic <i><a href="http://www.businessweek.com/chapter/christensen.htm" target="_blank">Innovator's Dilemma</a></i>. Should they adopt these tools and standards, painfully cannibalizing their existing revenue for a new unproven concept, or should they stick with their currently lucrative model with the risk that eventually a bunch of upstarts eat their lunch? <br /><br />Credit should go to several of the web giants who have been making efforts to "open up." Google, Yahoo, eBay, and Amazon all have Open APIs (Application Programming Interfaces) built into their data and systems. Any software developer can access and use them for whatever creative purposes they wish. This means that the API provider becomes an open platform for everyone to use and build on top of. This notion has expanded like wildfire throughout the blogosphere, so nowadays, Open APIs are pretty much required.<br /><br />Other incumbents also have open strategies. AOL has got the RSS religion, <a href="http://www.siliconbeat.com/entries/2005/07/27/aol_gets_rss_religion_with_my_aoland_feedsters_help.html" target="_blank">providing a feedreader and RSS search</a> in order to escape the "walled garden of content" stigma. <a href="http://www.apple.com/podcasting/" target="_blank">Apple now incorporates podcasts</a>, the "personal radio shows" that are latest rage in audio narrowcasting, into iTunes. Even Microsoft is supporting open standards, for example <a href="http://www.microsoft.com/technet/prodtechnol/winxppro/plan/rtcprot.mspx#EKAA" target="_blank">by endorsing SIP (Session Initiation Protocol) for internet telephony and conferencing</a> over Skype's proprietary format or one of its own devising.<br /><br />But new open standards and protocols are in use, under construction, or being proposed every day, pushing the envelope of where we are right now. Many of these standards are coming from startup companies and small groups of developers, not from the giants. Together with the Open APIs, those new standards will contribute to a new, open infrastructure. Tens of thousands of developers will use and improve this open infrastructure to create new kinds of web-based applications and services, to offer web users a highly personalized online experience.<br /><br /><b>A Brief History of Openness</b><br /><br />At this point, I have to admit that I am not just a passive observer, full-time journalist or "just some blogger"Âbut an active evangelist and developer of these standards. It's the vision of "open infrastructure" that's driving <a href="http://www.broadbandmechanics.com/bbm2005.htm" target="_blank">my company </a> and the reason why I'm writing this article. This article will give you some of the background behind on these standards, and what the evolution of the next generation of open standards will look like.<br /><br />Starting back in the 1980s, establishing a software standard was a key strategy for any software company. My former company, MacroMind (which became Macromedia), achieved this goal early on with Director. As <a href="http://webmonkey.wired.com/webmonkey/99/27/index3a_page6.html?tw=multimedia" target="_blank">Director evolved into Flash</a>, the world saw that other companies besides Microsoft, Adobe, and Apple could establish true cross-platform, independent media standards.<br /><br />Then <a href="http://www.w3.org/People/Berners-Lee/" target="_blank">Tim Berners-Lee</a> and <a href="http://www.ibiblio.org/pioneers/andreesen.html" target="_blank">Marc Andreessen</a> came along, and changed the rules of the software business and of entrepreneurialism. No matter how entrenched and "standardized" software was, the rug could still get pulled out from under it. <a href="http://geekphilosopher.com/MainPage/WebBrowserWars.htm?q=Stocks" target="_blank">Netscape did it to Microsoft, and then Microsoft did it <i>back</i> to Netscape</a>. The web evolved, and lots of standards evolved with it. The leading open source standards (such as the LAMP stack) became widely used alternatives to proprietary closed-source offerings. <br /><br />Open standards are more than just technology. Open standards mean sharing, empowering, and community support. Someone floats a new idea (or <a href="http://en.wikipedia.org/wiki/Meme" target="_blank">meme</a>) and the community runs with it â with each person making their own contributions to the standard â evolving it without a moment's hesitation about "giving away their intellectual property."<br /><br />One good example of this was <a href="http://www.sifry.com/alerts/" target="_blank">Dave Sifry</a>, who built the Technorati blog-tracking technology inspired by the <a href="http://www.myelin.co.nz/ecosystem/" target="_blank">Blogging Ecosystem</a>, a weekend project by young hacker <a href="http://marc.blogs.it/archives/2005/07/phil_pearson_jo.html" target="_blank">Phil Pearson</a>. Dave liked what he saw and he ran with itÂturning Technorati into what it is today.<br /><br /><a href="http://en.wikipedia.org/wiki/Dave_Winer" target="_blank">Dave Winer</a> has contributed enormously to this area of open standards. He defined and personally created several open standards and protocolsÂsuch as RSS, OPML, and XML-RPC. Dave has also <a href="http://newhome.weblogs.com/historyOfWeblogs" target="_blank">helped build</a> the blogosphere through his enthusiasm and passion.<br /><br />By 2003, hundreds of programmers were working on creating and establishing new standards for almost everything. The best of these new standards have evolved into compelling web services platforms â such as <a href="http://del.icio.us/" target="_blank">del.icio.us</a>, <a href="http://webjay.org/about" target="_blank">Webjay</a>, or <a href="http://www.flickr.com/photos/tags/ao2005/" target="_blank">Flickr</a>. Some have even spun off formal standards â like XSPF (a standard for playlists) or instant messaging standard XMPP (also known as Jabber).<br /><br />Today's Open APIs are complemented by standardized SchemasÂthe structure of the data itself and its associated meta-data. Take for example a <a href="http://www.ipodder.org/whatIsPodcasting" target="_blank">podcasting feed</a>. It consists of: a) the radio show itself, b) information on who is on the show, what the show is about and how long the show is (the meta-data) and also c) API calls to retrieve a show (a single feed item) and play it from a specified server. <br /><br />The combination of Open APIs, standardized schemas for handling meta-data, and an industry which agrees on these standards are breaking the web wide open right now. So what new open standards should the web incumbentsÂand youÂbe watching? Keep an eye on the following developments:<br /><br /><b>Identity<br />Attention<br />Open Media<br />Microcontent Publishing<br />Open Social Networks<br />Tags<br />Pinging <br />Routing<br />Open Communications<br />Device Management and Control</b><br /><br /><br /><b>1. Identity</b><br /><br />Right now, you don't really control your own online identity. At the core of just about every online piece of software is a membership system. Some systems allow you to browse a site anonymouslyÂbut unless you register with the site you can't do things like search for an article, post a comment, buy something, or review it. The problem is that each and every site has its own membership system. So you constantly have to register with new systems, which cannot share dataÂeven you'd want them to. By establishing a <a href="http://www.wired.com/news/privacy/0,1848,68329-2,00.html?tw=wn_story_page_next1" target="_blank">"single sign-on" standard</a>, disparate sites can allow users to freely move from site to site, and let them control the movement of their personal profile data, as well as any other data they've created. <br /><br />With <a href="http://www.thehindubusinessline.com/2005/01/03/stories/2005010301440200.htm" target="_blank">Passport, Microsoft unsuccessfully attempted</a> to force its proprietary standard on the industry. Instead, a world is evolving where most people assume that users want to control their own data, whether that data is their profile, their blog posts and photos, or some collection of their past interactions, purchases, and recommendations. As long as users can control their digital identity, any kind of service or interaction can be layered on top of it.<br /><br /><a href="http://www.identity20.com/media/OSCON2005/" target="_blank">Identity 2.0</a> is all about users controlling their own profile data and becoming their own agents. This way the users themselves, rather than other intermediaries, will profit from their ID info. Once developers start offering single sign-on to their users, and users have trusted places to store their dataÂwhich respect the limits and provide access controls over that data, users will be able to access personalized services which will understand and use their personal data.<br /><br />Identity 2.0 may seem like some geeky, visionary future standard that isn't defined yet, but by putting each user's digital identity at the core of all their online experiences, Identity 2.0 is becoming the cornerstone of the new open web. <br /><br /><b>The Initiatives:</b><br />Right now, Identity 2.0 is under construction through various efforts from Microsoft (the <a href="http://msdn.microsoft.com/webservices/webservices/understanding/advancedwebservices/default.aspx?pull=/library/en-us/dnwebsrv/html/identitymetasystem.asp" target="_blank">"InfoCard" component built into the Vista operating system</a> and its "<a href="http://garage.docsearls.com/node/605" target="_blank">Identity Metasystem</a>"), <a href="http://sxip.com" target="_blank">Sxip Identity</a>, <a href="http://www.identtycommons.net" target="_blank">Identity Commons</a>, <a href="http://www.projectliberty.org/" target="_blank">Liberty Alliance</a>, <a href="http://lid.netmesh.org/" target="_blank">LID</a> (NetMesh's Lightweight ID), and SixApart's <a href="http://openid.net/" target="_blank">OpenID</a>.<br /><br /><b>More Movers and Shakers:</b><br />Identity Commons and <a href="http://www.identitywoman.net" target="_blank">Kaliya Hamlin</a>, Sxip Identity and <a href="http://blame.ca/dick/" target="_blank">Dick Hardt</a>, the <a href="http://www.identitygang.org/" target="_blank"> Identity Gang</a> and <a href="http://www.searls.com/dochome.html#Bio" target="_blank">Doc Searls</a>, Microsoft's <a href="http://www.identityblog.com/" target="_blank">Kim Cameron</a>, <a href="http://www.craigburton.com/" target="_blank">Craig Burton</a>, <a href="http://phil.windley.org/" target="_blank">Phil Windley</a>, and <a href="http://slashdot.org/article.pl?sid=05/07/05/2020221&from=rss" target="_blank">Brad Fitzpatrick</a>, to name a few.<br /><br /><br /><b>2. Attention</b><br /><br />How many readers know what their online attention is worth? If you don't, Google and Yahoo doÂthey make their living off our attention. They know what we're searching for, happily turn it into a keyword, and sell that keyword to advertisers. They make money off our attention. We don't. <br /><br />Technorati and friends proposed <a href="http://blogs.zdnet.com/Gillmor/index.php?p=74" target="_blank">an attention standard, Attention.xml</a>, designed to "help you keep track of what you've read, what you're spending time on, and what you should be paying attention to." <a href="http://attentiontrust.org/" target="_blank">AttentionTrust</a> is an effort by <a href="http://blogs.zdnet.com/Gillmor/?p=132" target="_blank">Steve Gillmor</a> and <a href="http://majestic.typepad.com/seth/2005/07/attentiontrusto.html" target="_blank">Seth Goldstein </a>to standardize on how captured end-user performance, browsing, and interest data are used. <br /><br />Blogger <a href="http://worcester.typepad.com/pc4media/2005/07/attentiontrusto_1.html" target="_blank">Peter Caputa gives a good summary</a> of AttentionTrust: <blockquote>"As we use the web, we reveal lots of information about ourselves by what we pay attention to. Imagine if all of that information could be stored in a nice neat little xml file. And when we travel around the web, we can optionally share it with websites or other people. We can make them pay for it, lease it ... we get to decide who has access to it, how long they have access to it, and what we want in return. And they have to tell us what they are going to do with our Attention data."</blockquote><br />So when you give your attention to sites that adhere to the AttentionTrust, your attention rights (<i>you own your attention, you can move your attention, you can pay attention and be paid for it</i>, and <i>you can see how your attention is used</i>) are guaranteed. Attention data is crucial to the future of the open web, and Steve and Seth are making sure that no one entity or oligopoly controls it. <br /><br /><b>Movers and Shakers:</b><br /><a href="http://blogs.zdnet.com/Gillmor/" target="_blank">Steve Gillmor</a>, <a href="http://majestic.typepad.com/about.html" target="_blank">Seth Goldstein</a>, <a href="http://www.sifry.com/alerts/" target="_blank">Dave Sifry</a> and the <a href="http://developers.technorati.com/wiki/attentionxml" target="_blank">other Attention.xml folks</a>. <br /><br /><br /><b>3. Open Media</b><br /><br />Proprietary media standardsÂFlash, Windows Media, and QuickTime, to name a few Âhelped liven up the web. But they are proprietary standards that try to keep us locked in, and they weren't created from scratch to handle today's online content. That's why, for many of us, an Open Media standard has been a holy grail. Yahoo's new Media RSS standard brings us one step closer to achieving open media, as do <a href="http://www.vorbis.com/faq/#what" target="_blank">Ogg Vorbis</a> audio codecs, <a href="http://webjay.org/" target="_blank">XSPF playlists</a>, or <a href="http://musicbrainz.org/" target="_blank">MusicBrainz</a>. And several sites offer digital creators not only a place to store their content, but also to sell it. <br /><br /><a href="http://search.yahoo.com/mrss" target="_blank">Media RSS </a>(being developed by Yahoo with help from the community) extends RSS and combines it with "RSS enclosures" Âadds metadata to any media itemÂto create a comprehensive solution for media "narrowcasters." To gain acceptance for Media RSS, Yahoo knows it has to work with the community. As an active member of this community, I can tell you that we'll create Media RSS equivalents for <a href="http://www.xml.com/pub/a/2001/01/24/rdf.html" target="_blank">rdf</a> (an alternative subscription format) and <a href="http://www.atomenabled.org/" target="_blank">Atom</a> (yet <i>another</i> subscription format), so no one will be able to complain that Yahoo is picking sides in format wars.<br /><br />When Yahoo announced the purchase of Flickr, Yahoo founder Jerry Yang insinuated that Yahoo is acquiring "open DNA" to turn Yahoo into <a href="http://www.flickr.com/services/api/" target="_blank">an open standards player</a>. Yahoo is showing what happens when you take a multi-billion dollar company and make openness one of its core valuesÂso Google, beware, even if Google does have more research fellows and Ph.D.s. <br /><br />The open media landscape is far and wide, reaching from game machine hacks and mobile phone downloads to PC-driven bookmarklets, players, and editors, and it includes many other standardization efforts. <a href="http://www.xspf.org/" target="_blank">XSPF</a> is an open standard for playlists, and MusicBrainz is an alternative to the proprietary (and originally effectively stolen) database that <a href="http://en.wikipedia.org/wiki/Gracenote" target="_blank">Gracenote</a> licenses. <br /><br /><a href="http://www.ourmedia.org/" target="_blank">Ourmedia.org</a> is a community front-end to Brewster Kahle's <a href="http://www.archive.org" target="_blank">Internet Archive</a>. Brewster has promised free bandwidth and free storage forever to any content creators who choose to share their content via the Internet Archive. Ourmedia.org is providing an easy-to-use interface and community to get content in and out of the Internet Archive, giving ourmedia.org users the ability to share their media anywhere they wish, without being locked into a particular service or tool. Ourmedia plans to offer open APIs and an open media registry that interconnects other open media repositories into a DNS-like registry (just like the www domain system), so folks can browse and discover open content across many open media services. Systems like <a href="http://www.brightcove.com/" target="_blank">Brightcove</a> and <a href="http://www.evhead.com/2005/02/how-odeo-happened.asp" target="_blank">Odeo</a> support the concept of an open registry, and hope to work with digital creators to sell their work to fulfill the financial aspect of <a href="http://en.wikipedia.org/wiki/The_Long_Tail" target="_blank">the "Long Tail."</a><br /><br /><b>More Movers and Shakers:</b><br /><a href="http://creativecommons.org/about/people" target="_blank">Creative Commons</a>, the <a href="http://www.omn.org/" target="_blank">Open Media Network</a>, <a href="http://www.momentshowing.net/about.html" target="_blank">Jay Dedman</a>, <a href="http://ryanedit.blogspot.com/" target="_blank">Ryanne Hodson</a>, <a href="http://michaelverdi.com/index.php" target="_blank">Michael Verdi</a>, <a href="http://www.chapmanlogic.com/blog/aboutEli.html" target="_blank">Eli Chapman</a>, <a href="http://www.unmediated.org/" target="_blank">Kenyatta Cheese</a>, <a href="http://www.itconversations.com/about.html" target="_blank">Doug Kaye</a>, <a href="http://www.wired.com/wired/archive/13.09/yahoo.html" target="_blank">Brad Horowitz</a>, <a href="http://webjay.org/about#colophon" target="_blank">Lucas Gonze</a>, <a href="http://musicbrainz.org/wd/MusicBrainzBio" target="_blank">Robert Kaye</a>, <a href="http://www.lifewithalacrity.com/" target="_blank">Christopher Allen</a>, <a href="http://en.wikipedia.org/wiki/Brewster_Kahle" target="_blank">Brewster Kahle</a>, <a href="http://www.newmediamusings.com/" target="_blank">JD Lasica</a>, and indeed, <a href="http://www.corante.com/amateur/articles/20030211-3564.html" target="_blank">Marc Canter</a>, among others.<br /><br /><br /><b>4. Microcontent Publishing</b><br /><br />Unstructured content is cheap to create, but hard to search through. Structured content is expensive to create, but easy to search. <a href="http://developers.technorati.com/wiki/MicroFormats" target="_blank">Microformats</a> resolve the dilemma with simple structures that are cheap to use and easy to search.<br /><br />The first kind of widely adopted microcontent is blogging. Every post is an encapsulated idea, addressable via a URL called a permalink. You can syndicate or subscribe to this microcontent using RSS or an RSS equivalent, and news or blog aggregators can then display these feeds in a convenient readable fashion. But a blog post is just a block of unstructured textânot a bad thing, but just a first step for microcontent. When it comes to<i>structured</i> data, such as personal identity profiles, product reviews, or calendar-type event data, RSS was not designed to maintain the integrity of the structures. <br /><br />Right now, blogging doesn't have the underlying structure necessary for full-fledged microcontent publishing. But that will change. Think of local information services (such as movie listings, event guides, or restaurant reviews) that any college kid can access and use in her weekend programming project to create new services and tools.<br /><br />Today's blogging tools will evolve into microcontent publishing systems, and will help spread the notion of structured data across the blogosphere. New ways to store, represent and produce microcontent will create new standards, such as <a href="http://structuredblogging.org/" target="_blank">Structured Blogging</a> and <a href="http://microformats.org/" target="_blank">Microformats</a>. Microformats differ from RSS feeds in that you can't subscribe to them. Instead, Microformats are embedded into webpages and discovered by search engines like Google or Technorati. Microformats are creating common definitions for "What is a review or event? What are the specific fields in the data structure?" They can also specify what we can do with all this information.<a href="http://www.opml.org/spec" target="_blank">OPML (Outline Processor Markup Language)</a> is a hierarchical file format for storing microcontent and structured data. It was developed by <a href="http://en.wikipedia.org/wiki/Dave_Winer" target="_blank">Dave Winer</a> of RSS and podcast fame.<br /><br />Events are one popular type of microcontent. <a href="http://www.openevents.com" target="_blank">OpenEvents</a> is already working to create shared databases of standardized events, which would get used by a new generation of event portalsâsuch as <a href="http://eventful.com/gotevents/" target="_blank">Eventful/EVDB</a>, <a href="http://upcoming.org/" target="_blank">Upcoming.org</a>, and <a href="http://www.whizspark.com/" target="_blank">WhizSpark</a>. The idea of OpenEvents is that event-oriented systems and services can work together to establish shared events databases (and associated APIs) that any developer could then use to create and offer their own new service or application. <a href="http://marc.blogs.it/archives/2005/04/rvw_redux_openr.html" target="_blank">OpenReviews</a> is still in the conceptual stage, but it would make it possible to provide open alternatives to closed systems like Epinions, and establish a shared database of local and global reviews. Its shared open servers would be filled with all sorts of reviews for anyone to access. <br /><br />Why is this important? Because I predict that in the future, 10 times more people will be writing reviews than maintaining their own blog. The list of possible microcontent standards goes on: OpenJobpostings, OpenRecipes, and even OpenLists. Microsoft <a href="http://www.reallysimplesyndication.com/2005/06/22" target="_blank">recently revealed</a> that it has been working on an important new kind of microcontent: Listsâso OpenLists will attempt to establish standards for the <i>kind</i> of lists we all use, such as lists of Links, lists of To Do Items, lists of People, Wish Lists, etc.<br /><br /><b>Movers and Shakers:</b><br /><a href="http://tantek.com/log/2005/09.html" target="_blank">Tantek Ãelik</a> and <a href="http://en.wikipedia.org/wiki/Kevin_Marks" target="_blank">Kevin Marks</a> of <a href="http://developers.technorati.com/wiki/MicroFormats" target="_blank">Technorati</a>, <a href="http://dannyayers.com/" target="_blank">Danny Ayers</a>, <a href="http://www.meyerweb.com/" target="_blank">Eric Meyer</a>, <a href="http://photomatt.net/" target="_blank">Matt Mullenweg</a>, <a href="http://zlab.commerce.net/" target="_blank">Rohit Khare</a>, <a href="http://ifindkarma.typepad.com/relax/" target="_blank">Adam Rifkin</a>, <a href="http://www.sivas.com/aleene/" target="_blank">Arnaud Leene</a>, <a href="http://radio.weblogs.com/0110772/" target="_blank">Seb Paquet</a>, <a href="http://hublog.hubmed.org/" target="_blank">Alf Eaton</a>, <a href="http://www.myelin.co.nz/post/" target="_blank">Phil Pearson</a>, <a href="http://www.joereger.com/" target="_blank">Joe Reger</a>, <a href="http://bobwyman.pubsub.com/" target="_blank">Bob Wyman</a> among others.<br /><br /><br /><b>5. Open Social Networks</b><br /><br />I'll never forget the first time I met <a href="http://www.jabrams.com/" target="_blank">Jonathan Abrams</a>, the founder of Friendster. He was arrogant and brash and he claimed he "<i>owned</i>" all his users, and that he was going to monetize them and make a fortune off them. This attitude robbed Friendster of its momentum, letting MySpace, Facebook, and other social networks take Friendster's place.<br /><br />Jonathan's notion of social networks as a way to control users is typical of the Web 1.0 business model and its attitude towards users in general. Social networks have become one of the battlegrounds between old and new ways of thinking. Open standards for Social Networking will define those sides very clearly. Since meeting Jonathan, I have been working towards finding and establishing open standards for social networks. Instead of closed, centralized social networks with 10 million people in them, the goal is making it possible to have 10 million social networks that each have 10 people in them.<br /><br />FOAF (which stands for Friend Of A Friend, and describes people and relationships in a way that computers can parse) is a schema to represent not only your personal profile's meta-data, but your social network as well. Thousands of researchers use the <a href="http://www.foaf-project.org/" target="_blank">FOAF schema</a> in their "Semantic Web" projects to connect people in all sorts of new ways. <a href="http://gmpg.org/xfn/" target="_blank">XFN</a> is a microformat standard for representing your social network, while <a href="http://www.imc.org/pdi/" target="_blank">vCard</a> (long familiar to users of contact manager programs like Outlook) is a microformat that contains your profile information. Microformats are baked into any xHTML webpage, which means that<i>any</i> blog, social network page, or any webpage in general can "contain" your social network in itÂand be used by<i>any</i> compatible tool, service or application. <br /><br />PeopleAggregator is an earlier project now being integrated into <a href="http://drupal.org/" target="_blank">open content management framework Drupal</a>. The <a href="http://www.broadbandmechanics.com/PeopleAggregator/" target="_blank">PeopleAggregator APIs</a> will make it possible to establish relationships, send messages, create or join groups, and post between different social networks. (Sneak preview: this technology will be available in the upcoming GoingOn Network.) <br /><br />All of these open social networking standards mean that inter-connected social networks will form a mesh that will parallel the blogosphere. This vibrant, distributed, decentralized world will be driven by open standards: personalized online experiences are what the new open web will be all aboutÂand what could be more personalized than people's networks?<br /><br /><b>Movers and Shakers:</b><br /><a href="http://esigler.2nw.net/" target="_blank">Eric Sigler</a>, <a href="http://lucifer.intercosmos.net/index.php?view=about" target="_blank">Joel De Gan</a>, <a href="http://crschmidt.net/" target="_blank">Chris Schmidt</a>, <a href="http://voidstar.com/" target="_blank">Julian Bond</a>, <a href="http://people.tribe.net/paul?_click_path=Application%5Btribe%5D.Person%5Bf2232c95-e123-43a3-b48d-24a5f11f09dc%5D&r=10535" target="_blank">Paul Martino</a>, <a href="http://napsterization.org/stories/archives/000513.html" target="_blank">Mary Hodder</a>, <a href="http://public.2idi.com/=Drummond.Reed" target="_blank">Drummond Reed</a>, <a href="http://danbri.org/" target="_blank">Dan Brickley</a>, <a href="http://360.yahoo.com/profile-9lciejI3aafX1stHPoIRNmkmv4EowQ--" target="_blank">Randy Farmer</a>, and <a href="http://www.kaliyasblogs.net/Iwoman/" target="_blank">Kaliya Hamlin</a>, to name a few.<br /><br /><br /><b>6. Tags</b><br /><br />Nowadays, no self-respecting tool or service can ship without <a href="http://www.salon.com/tech/feature/2005/02/08/tagging/index_np.html" target="_blank">tags</a>. Tags are keywords or phrases attached to photos, blog posts, URLs, or even video clips. These user- and creator-generated tags are an open alternative to what used to be the domain of librarians and information scientists: categorizing information and content using taxonomies. Tags are instead creating <a href="http://www.wired.com/wired/archive/13.04/view.html?pg=4" target="_blank">"folksonomies."</a><br /><br />The recently proposed OpenTags concept would be an open, community-owned version of the popular <a href="http://www.technorati.com/tag/" target="_blank">Technorati Tags service</a>. It would aggregate the usage of tags across a wide range of services, sites, and content tools. In addition to Technorati's current tag features, OpenTags would let groups of people share their tags in "<a href="http://www.zeldman.com/daily/0405d.shtml/" target="_blank">TagClouds</a>." Open tagging is likely to include some of the open identity features discussed above, to create a tag system that is resilient to spam, and yet trustable across sites all over the web.<br /><br />OpenTags owes a debt to earlier versions of shared tagging systems, which include <a href="http://www.topicexchange.com/" target="_blank">Topic Exchange</a> and something called the <a href="http://www.evectors.com/itkcollector/" target="_blank">k-collector</a>Âa knowledge management tag aggregatorÂfrom Italian company eVectors. <br /><br /><b>Movers & Shakers:</b><br /><a href="http://www.myelin.co.nz/notes/" target="_blank">Phil Pearson</a>, <a href="http://matt.blogs.it/" target="_blank">Matt Mower </a>, <a href="http://paolo.evectors.it/" target="_blank">Paolo Valdemarin</a>, and <a href="http://marc.blogs.it/archives/2005/03/opentopics.html" target="_blank">Mary Hodder</a> and <a href="http://www.equalsdrummond.name/index.php?p=39" target="_blank"> Drummond Reed</a> again, among others.<br /><br /><br /><b>7. Pinging</b><br /><br />Websites used to be mostly static. Search engines that <a href="http://en.wikipedia.org/wiki/Web_crawler" target="_blank">crawled</a> (or "spidered") them every so often did a good enough job to show reasonably current versions of your cousin's homepage or even <i>Time</i> magazine's weekly headlines. But when blogging took off, it became hard for search engines to keep up. (Google has only <a href="http://searchenginewatch.com/searchday/article.php/3548411" target="_blank">just managed</a> to offer <a href="http://www.google.com/help/about_blogsearch.html" target="_blank">blog-search functionality</a>, despite <a href="http://www.alwayson-network.com/comments.php?id=325_0_2_0_C" target="_blank">buying Blogger</a> back in early 2003.)<br /><br />To know what was new in the blogosphere, users couldn't depend on services that spidered webpages once in a while. The solution: a way for blogs themselves to automatically notify blog-tracking sites that they'd been updated. <a href="http://weblogs.com/" target="_blank">Weblogs.com</a> was the first blog "ping service": it displayed the name of a blog whenever that blog was updated. Pinging sites helped the blogosphere grow, and <a href="http://blo.gs/" target="_blank">more tools</a>, services, and portals started using pinging in new and different ways. Dozens of pinging services and sitesÂmost of which can't talk to each otherÂsprang up. <br /><br />Matt Mullenweg (the creator of open source blogging software WordPress) decided that a one-stop service for pinging was needed. He created <a href="http://pingomatic.com/" target="_blank">Ping-o-Matic</a>Âwhich aggregates ping services and simplifies the pinging process for bloggers and tool developers. With Ping-o-Matic, any developer can alert all of the industry's blogging tools and tracking sites at once. This new kind of open standard, with shared infrastructure, is a critical to the scalability of Web 2.0 services.<br /><br />As <a href="http://pingomatic.com/about/" target="_blank">Matt said</a>:<br /><blockquote>There are a number of services designed specifically for tracking and connecting blogs. However it would be expensive for all the services to crawl all the blogs in the world all the time. By sending a small ping to each service you let them know you've updated so they can come check you out. They get the freshest data possible, you don't get a thousand robots spidering your site all the time. Everybody wins.</blockquote><br /><b>Movers and Shakers:</b><br /><a href="http://photomatt.net/about/" target="_blank">Matt Mullenweg</a>, <a href="http://trainedmonkey.com/entry/2251" target="_blank">Jim Winstead</a>, <a href="http://newhome.weblogs.com/faq" target="_blank">Dave Winer</a><br /><br /><br /><b>8. Routing</b><br /><br />Bloggers used to have to manually enter the links and content snippets of blog posts or news items they wanted to blog. Today, some RSS aggregators can send a specified post directly into an associated blogging tool: as bloggers browse through the feeds they subscribe to, they can easily specify and send any post they wish to "<a href="http://www.microsoftmonitor.com/archives/010209.html" target="_blank">reblog</a>" from their news aggregator or feed reader into their blogging tool. (This is usually referred to as "<a href="http://help.blogger.com/bin/answer.py?answer=152&topic=17" target="_blank">BlogThis</a>.") As structured blogging comes into its own (see the section on Microcontent Publishing), it will be increasingly important to maintain the structural integrity of these pieces of microcontent when reblogging them. <br /><br />Promising standard <a href="http://redirectthis.com/" target="_blank">RedirectThis</a> will combine a "BlogThis"-like capability while maintaining the integrity of the microcontent. RedirectThis will let bloggers and content developers attach a simple "PostThis" button to their posts. Clicking on that button will send that post to the reader/blogger's favorite <a href="http://ecto.kung-foo.tv/archives/000990.php" target="_blank">blogging tool</a>. This favorite tool is specified at the RedirectThis web service, where users register their blogging tool of choice. RedirectThis also helps maintain the integrity and structure of microcontentÂthen it's just up to the user to prefer a blogging tool that also attains that lofty goal of microcontent integrity. <br /><br />OutputThis is another nascent web services standard, to let bloggers specify what "destinations" they'd like to have as options in their blogging tool. As new destinations are added to the service, more checkboxes would get added to their blogging toolÂallowing them to route their published microcontent to additional destinations.<br /><br /><b>Movers and Shakers:</b><br /><a href="http://reblog.org/" target="_blank">Michael Migurski</a>, <a href="http://www.gonze.com/about" target="_blank">Lucas Gonze</a><br /><br /><br /><b>9. Open Communications</b><br /><br />Likely, you've experienced the joys of finding friends on AIM or Yahoo Messenger, or the convenience of Skyping with someone overseas. Not that you're about to throw away your mobile phone or BlackBerry, but for many, also having access to Instant Messaging (IM) and Voice over IP (VoIP) is crucial. <br /><br />IM and VoIP are mainstream technologies that already enjoy the benefits of open standards. Entire industries are bornÂright this secondÂbased around these open standards. <a href="http://www.jabber.org/" target="_blank">Jabber</a> has been an open IM technology for yearsÂin fact, <a href="http://www.xmpp.org/history.html" target="_blank">as XMPP</a>, it was officially dubbed a standard by <a href="http://www.ietf.org/overview.html" target="_blank">the IETF</a>. Although becoming an <a href="http://en.wikipedia.org/wiki/IETF" target="_blank">official IETF standard</a> is usually the kiss of death, Jabber looks like it'll be around for a while, as entire generations of collaborative, work-group applications and services have been built on top of its messaging protocol. For VoIP, <a href="http://skype.com/helloagain.html" target="_blank">Skype</a> is clearly the leading standard todayÂthough one could <a href="http://socialsoftware.weblogsinc.com/entry/1234000923058521/" target="_blank">argue just how "open" it is</a> (and defenders of the IETF's <a href="http://www.cs.columbia.edu/sip/" target="_blank">SIP standard</a> often do). But it is free and user-friendly, so there won't be much argument from <i>users</i> about it being insufficiently open. Yet there may be a cloud on Skype's horizon: web behemoth Google recently released a beta of <a href="http://www.google.com/talk/developer.html" target="_blank">Google Talk, an IM client committed to open standards</a>. It currently <a href="http://radar.oreilly.com/archives/2005/08/google_talk_rel.html" target="_blank">supports XMPP, and will support SIP</a> for VoIP calls.<br /><br /><b>Movers and Shakers:</b><br /><a href="http://www.jabber.org/people/jer.shtml" target="_blank">Jeremie Miller</a>, <a href="http://www.cs.columbia.edu/~hgs/" target="_blank">Henning Schulzrinne</a>, <a href="http://www.von.com/schedule_eos11114704148.html" target="_blank">Jon Peterson</a>, <a href="http://www.pulver.com/jeff/" target="_blank">Jeff Pulver</a><br /><br /><br /><b>10. Device Management and Control</b><br /><br />To access online content, we're using more and more devices. BlackBerrys, iPods, Treos, you name it. As the web evolves, more and more different devices will have to communicate with each other to give us the content we want when and where we want it. No-one wants to be dependent on one vendor anymoreÂlike, <a href="http://www.alwayson-network.com/comments.php?id=P9409_0_6_0_C" target="_blank">say, Sony</a>Âfor their laptop, phone, MP3 player, PDA, and digital camera, so that it all works together. We need fully interoperable devices, and the standards to make that work. And to fully make use of how content is moving online content and innovative web services, those standards need to be open.<br /><br /><a href="http://en.wikipedia.org/wiki/Midi" target="_blank">MIDI (musical instrument digital interface)</a>, one of the very first open standards in music, connected disparate vendors' instruments, post-production equipment, and recording devices. But MIDI is limited, and <a href="http://www.oreillynet.com/pub/wlg/8015" target="_blank">MIDI II has been very slow to arrive</a>. Now a new standard for controlling musical devices has emerged: <a href="http://www.cnmat.berkeley.edu/OpenSoundControl/" target="_blank">OSC (Open SoundControl)</a>. This protocol is optimized for modern networking technology and inter-connects music, video and controller devices with "other multimedia devices." OSC is used by a wide range of developers, and is being taken up in the mainstream MIDI marketplace.<br /><br />Another open-standards-based device management technology is <a href="http://www.zigbee.org" target="_blank">ZigBee</a>, for building wireless intelligence and network monitoring into all kinds of devices. ZigBee is supported by many networking, consumer electronics, and mobile device companies.<br /><br /><br />   · · · · · ·   <br /><br /><b>The Change to Openness</b><br /><br />The rise of open source software and its "<a href="http://www.oreillynet.com/pub/a/oreilly/tim/articles/architecture_of_participation.html" target="_blank">architecture of participation</a>" are completely shaking up the old proprietary-web-services-and-standards approach. Sun MicrosystemsÂwhose proprietary Java standard helped define the Web 1.0Âis opening its Solaris OS and has even announced the apparent paradox of an <a href="http://blogs.zdnet.com/open-source/?p=418" target="_blank">open-source Digital Rights Management</a> system.<br /><br />Today's incumbents will have to adapt to the new openness of the Web 2.0. If they stick to their <a href="http://www.gartner.com/DisplayDocument?doc_cd=131038" target="_blank">proprietary standards</a>, code, and content, they'll become the new walled gardensÂplaces users visit briefly to retrieve data and content from enclosed data silos, but not where users "live." The incumbents' revenue models will have to change. Instead of "owning" their users, users will know they own themselves, and will expect a return on their valuable identity and attention. Instead of being locked into incompatible media formats, users will expect easy access to digital content across many platforms. <br /><br />Yesterday's web giants and tomorrow's users will need to find a mutually beneficial new balanceÂbetween open and proprietary, developer and user, hierarchical and horizontal, owned and shared, and compatible and closed. <br /><br /><br /><i>Marc Canter is an active evangelist and developer of open standards. Early in his career, Marc founded MacroMind, which became Macromedia. These days, he is CEO of Broadband Mechanics, a founding member of the Identity Gang and of ourmedia.org. Broadband Mechanics is currently developing the <a href="http://www.alwayson-network.com/comments.php?id=11262_0_1_0_C" target="_blank">GoingOn Network</a> (with the AlwaysOn Network), as well as an open platform for social networking called the PeopleAggregator.</i><br /><br />A version of the above post appears in the Fall 2005 issue of AlwaysOn's quarterly print blogozine, and ran as <a href="http://www.alwayson-network.com/comments.php?id=12063_0_1_0_C" target="_blank">a four-part series</a> on the AlwaysOn Network website.</td></tr></table><br /><p>(Via <a href="http://marc.blogs.it/">Marc's Voice</a>.)</p></blockquote>
WebDAV, SQLX, and my Weblog
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2005-04-26#810
2005-04-26T03:54:43Z
2006-06-22T08:56:58-04:00
<p>Uche Ogbuji <a href="http://copia.ogbuji.net/blog/2005/04/24#Posting_to">comments</a> in his <a href="http://copia.ogbuji.net/blog">blog</a> about the use of WebDAV and <a href="http://www.tbradford.org/2005/02/xml-with-virtuoso-and-sqlx_02.html">SQLX </a>in my blog as part of his commentary about <a href="http://egaumer.pagecache.org/PyBlosxom/pyblosxom-webdav.html">Pyblosxom & WebDAV</a>. To provide some clarity about Virtuoso and Blogging I have decided to put out this quick step by guide to the workings of my blog (there is a long overdue technical white paper nearing completion that address this subject in more detail).</p> <p>Here goes:</p> <p><u><strong>Blog Editing</strong></u></p> <p>I can use any editor that supports the following Blog Post APIs:</p> <p>- Moveable Type</p> <p>- Meta Weblog</p> <p>- Blogger</p> <p>Typically I use Virtuoso (which has an unreleased WYSIWYG blog post editor), <a href="http://www.newzcrawler.com/">Newzcrawler</a>, <a href="http://ecto.kung-foo.tv/">ecto</a>, <a href="http://zempt.com/">Zempt</a>, or <a href="http://www.wbloggar.com/">w.bloggar</a> for my posts. If a post is of interest to me, or relevant to our company or customers I tend to perform one of the following tasks:</p> <p>- Generate a post using the "Blog This" feature of my blog editor</p> <p>- Write a new post that was triggered by a previously read post etc.</p> <p>Either way, the posts end up in our company wide blog server that is Virtuoso based (more about this below). The internal blog server automatically categorizes my blog posts, and automagically determines which posts to upstream to other public blogs that I author (e.g <a href="http://kidehen.typepad.com/">http://kidehen.typepad.com</a> ) or co-author (e.g <a href="http://www.openlinksw.com/weblogs/uda">http://www.openlinksw.com/weblogs/uda</a> and <a href="http://www.openlinksw.com/weblogs/virtuoso">http://www.openlinksw.com/weblogs/virtuoso</a> ). I write once and my posts are dispatched conditionally to multiple outlets.</p> <p><strong><u>RSS/Atom/RDF Aggregation & Reading</u></strong></p> <p>I discover, subscribe to, and view blog feeds using <a href="http://www.newzcrawler.com/">Newzcrawler</a> (primarily), and from time to time for experimentation and evaluation purposes I use <a href="http://www.rssbandit.org/">RSS Bandit</a>, <a href="http://www.bradsoft.com/feeddemon/">FeedDemon</a>, and <a href="http://www.bloglines.com/">Bloglines</a>. I am in the process of moving this activity over to Virtuoso completely due to the large number of feeds that I consume on a daily basis (scalability is a bit of a problem with current aggregators).</p> <p><u><strong>Blog Publishing</strong></u></p> <p>When you visit my blog you are experiencing the soon to be released Virtuoso Blog Publishing engine first hand, which is how WebDAV, SQLX, XQuery/XPath, and Free Text etc. come into the mix.</p> <p>Each time I create a post internally, or subscribe to an external feed, the data ends up in Virtuoso's SQL Engine (this is how we handle some of the obvious scalability challenges associated with large subscription counts). This engine is SQL2000N based, which implies that it can transform SQL to XML on the fly using recent extensions to SQL in the form of SQLX (prior to the emergence of this standard we used the FOR XML SQL syntax extensions for the same result). It also has its own in-built XSLT processor (DB Engine resident), and validating XML parser (with support for XML Schema). Thus, my <a href="http://www.openlinksw.com/blog/~kidehen/gems/">RSS/RDF/Atom archives, FOAF, BlogRoll, OPML, and OCS</a> blog syndication gems are all live examples of SQLX documents that leverage Virtuoso's WebDAV engine for exposure to Blog Clients.</p> <p><strong><u>Blog Search</u></strong></p> <p>When you search for blog posts using the basic or <a href="http://www.openlinksw.com/blog/search.vspx?blogid=127">advanced search</a> features of my blog, you end up interacting with one of the following methods of querying data hosted in Virtuoso: Free Text Search, XPath, or XQuery. The <a href="http://www.openlinksw.com/blog/search.vspx?blogid=127&q=virtuoso&type=text&output=html">result sets</a> produced by the search feature uses SQLX to produce subscription gems (<a href="http://www.openlinksw.com/blog/search.vspx?blogid=127&q=virtuoso&type=text&output=xml">RSS</a>/<a href="http://www.openlinksw.com/blog/search.vspx?blogid=127&q=virtuoso&type=text&output=atom">Atom</a>/<a href="http://www.openlinksw.com/blog/search.vspx?blogid=127&q=virtuoso&type=text&output=rdf">RDF</a>/<a href="http://www.openlinksw.com/blog/search.vspx?blogid=127&type=text&kwds=virtuoso&OpenSearch">OpenSearch</a>) and <a href="http://www.openlinksw.com/blog/search.vspx?blogid=127&q=virtuoso&type=text&output=html">URIs</a> that enable dynamic tracking of my posts using your search keywords.</p> <p>BTW - the <a href="http://www.openlinksw.com/blog/~kidehen">http://www.openlinksw.com/blog/~kidehen</a> blog home page exists as a result of Virtuoso's Virtual Domain / Multi-Homing Web Server functionality. The entire site resides in an Object Relational DBMS, and I can take my DB file across Windows, Solaris, Linux, Mac OS X, FreeBSD, AIX, HP-UX, IRIX, and SCO UnixWare without missing a single beat! All I have to do is instantiate my Virtuoso server and my weblog is live.</p>
Back To The Future: Hypermedia
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2005-03-26#766
2005-03-26T20:24:30Z
2006-06-22T08:56:58-04:00
<p>If a picture speaks a thousand words, I sometimes wonder how many words we attribute to a multimedia clip? Especially one that is now openly accessible to many who don't quite understand the high degree of: "Back To The Future" quotient of most of what we see today.</p> <p>The Internet Archive initiative is building up an amazing collection of content that includes this <a href="http://www.archive.org/movies/details-db.php?collection=computerchronicles&collectionid=CC501_hypercard">"must watch" movie</a> about the somewhat forgotten <a href="http://en.wikipedia.org/wiki/Hypercard">hypercard</a> development environment.</p> <p>As I watched the hypercard movie I obtained clear reassurance that my vision of <a href="http://en.wikipedia.org/wiki/Web_2.0">Web 2.0</a> as critical infrastructure for a future Semantic Web isn't unfounded. The solution building methodology espoused by hypercard is exactly how Semantic Web applications will be built, and this will be done by orchestrating the componentary of Web 2.0.</p> <p>When watching this clip make the following mental adjustments:</p> <ol> <li>Swap hypercard stacks for discrete and/or composite services that have published endpoints exposed by Web 2.0 points of presence<br><br></li> <li>Think of information taking the form of XML based content e.g. RSS, Atom, RDF, FOAF, XFN, and other future XML based data contextualization formats; all accessible via URIs<br><br></li> <li>When the Apple Mac operating system is mentioned (or infered) think of the Internet (you don't need Windows, Mac OS, Linux, UNIX etc. to realize the vision, the network provided by the Internet is the Operating System)<br><br></li> <li>When the Apple computer is mentioned simply think about a plethora of function specific devices (computers, mobile phones, PDAs etc.) that overtly or covertly provide conduits to the new operating environment (the Internet)<br><br></li> <li>As you hear term "whole new body of people that are non programmers contributing there ideas" think about yourself and the increasing ease of participation that's beginning to take shape in this emerging frontier!<br><br></li> <li>As for "<a href="http://www.wholeearthmag.com/about.html">Whole Earth Catalog", </a>think <a href="http://en.wikipedia.org">Wikipedia</a> or more recent efforts such as <a href="http://www.answers.com">Answers.com</a>.</li></ol> <p>Web 2.0 is a reflection of the web taking its first major step out of the technology stone age (certainly the case relative to the hypercard movie and "pre web" application development in general). </p> <p> </p>
Is Google Web 2.0's Netscape?
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2004-08-26#611
2004-08-26T21:52:30Z
2006-06-22T08:56:58-04:00
<p>I put this piece together in response to another <a href="http://www.25hoursaday.com/weblog/CommentView.aspx?guid=5ab1ca87-b0df-4dd0-99b6-7730955620ab">stimulating post</a> by Dare Obasanjo titled "Is Google the Next Microsoft or the Next Netscape?". I changed the title of this post to project the fact that Web 2.0 provides the appropriate context (IMHO) for Dare's point re. "Web Site Stickiness". </p> <p>Stickiness is a defining characteristic of Web 1.0 . It's all about eyeballs (site visitors) which implied ultimately that all early Web business models ended up down the advertising route. </p> <p>I always felt that Web 1.0 was akin to having a crowd of people at your reception area seeking a look at your corporate brochures, and then someone realizes that you could start selling AD space in these brochures in response to the growing crowd size and frequency of congregation. The long-term folly of this approach is now obvious, as many organizations forgot their core value propositions (expressed via product offerings) in the process and wandered blindly down the AD model cul-de-sac, and we all know what happened down there.. </p> <p>Web 2.0 is taking shape (the inflection is in its latter stages), and the defining characteristics of Web 2.0 are: </p> <ol> <li>Fabric of Executable Endpoints <br></li> <li>Semantic Content (the RSS/RDF/Atom/FOAF semantic crumbs emerging from the Blogosphere are great examples of things to come re. XQuery queries over HTTP for instance) Migration from the Web Site (defined by static or dynamic HTML page generation) concept, to that of a "Web Point of Presence" (I don't know if this term will catch on, but the conceptual essence here is factual) that enables an organization to achieve the following: <br></li> <ul> <li>Package/catalog value proposition (product and services) using RSS/RDF/Atom <br></li> <li>Provide SOAP compliant Executable Endpoints (Web Services) for consuming value proposition (as opposed to being distracted by the AD model) <br></li> <li>Provide Web Services for consummating contracts associated with core value proposition Identification of internal efficiencies, new products/services that leverage Semantic Content and Web Services, and tangibly exploit: <br></li> <ul> <li>Composite Web Services construction from legacy monolithic application pools <br></li> <li>Standards based (e.g. BPEL) orchestration and integration of disparate composite services (across the Fabric referred to above) </li></ul></ul></ol> <p>When you factor in all of the above, the real question is whether Google and others are equipped to exploit Web 2.0? To some degree, is the best answer at the current time as they have commenced the transition from "content only" web site to web platform (via the many Web Services initiatives that expose SOAP and REST interfaces to various services), but there is much more to this journey, and that's the devil in the "competitive landscape details". </p> <p>From my obviously biased perspective, I think <a href="http://virtuoso.openlinksw.com/">Virtuoso</a> and <a href="http://www.midrangeserver.com/two/two042804-story02.html">Yukon+WinFS</a> provide the server models for driving Web 2.0 points of presence (single server instances that implement multiple protocols). Thus, if Google, Yahoo! et al. aren't exploiting these or similar products, then they will be vulnerable over the long term to the competitve challenges that a Web 2.0 landscape will present. </p>
RSS: The Best Of All Possible Worlds
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-10-02#383
2003-10-03T02:37:52Z
2006-06-22T08:56:58-04:00
<A href="http://www.ventureblog.com/articles/indiv/2003/000192.html">RSS: The Best Of All Possible Worlds</A> <P>The thing that most surprised me today in the <A href="http://www.pulver.com/rvc2003/">SoftEdge</A> panel on Social Software was the reaction to RSS. I should be clear that I am an RSS true believer. It seems to me that metadata as a byproduct of social software engines (be it blogging or social networking or whatever) is not only enviable, it is inevitable. <A href="http://www.oreillynet.com/rss/">RSS</A> and <A href="http://www.foaf-project.org/">FOAF</A> and other yet-to-be-determined social software data protocols will become standards because it simply makes good sense for them to be standardized. Anyone paying attention to the unbelievable development and adoption curve of wireless can appreciate the immense value driven by standards -- and, in particular, standards that are truly standard. So it came as a bit of a shock to me that when I questioned the panelists on the implications of RSS and the Semantic Web, they were less sold on the inevitability of it all. </P> <P>When asked the question of whether the proliferation of RSS and FOAF might make it possible for reader technology to be the next killer application in knowledge management, I got very strong reactions from both Reid Hoffman and Meg Hourihan. Reid stated that he did not believe that RSS was sufficiently robust to provide significant value an any level. Meg followed up with a general indictment of the semantic web, which she views merely as a geek utopia. I will admit that I'm a fan of Candide (particularly at the hands of <A href="http://www.leonardbernstein.com/">Bernstein</A>), but I hardly view myself as Panglos. One need look no further than, for example, the tools that <A href="http://www.oddpost.com/learnmore.html">Oddpost</A> has incorporated into its web email client to allow an integrated email and blog experience. Better yet, through a relatively simple web service, Oddpost can deliver an RSS feed of a particular Google News search so that you can keep track of keywords that are of interest to you without having to visit Google repeatedly to find out if your company or candidate or favorite band has been mentioned in today's news. The same is true of watch lists on <A href="http://www.technorati.com/watchlists/index.html">Technorati</A>. Rather than periodically check to see if someone has linked to your blog, Technorati will do the work for you and deliver the info to your inbox only when there is information to be delivered. These examples are just the tip of the iceberg but the demonstrate the nascent power of RSS and related standards. I'll have to wait for another panel to have that argument with Reid and Meg. </P> <DIV align=right>[via <A href="http://www.ventureblog.com/">VentureBlog</A>] <DIV></DIV></DIV>
Jeff Bezos Comments about Web Services
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-09-25#373
2003-09-25T18:48:00Z
2006-06-22T08:56:58-04:00
The following excerpt from a recent <a href="http://yahoo.businessweek.com/magazine/content/03_39/b3851607.htm">BusinessWeek interview with Jeff Bezos</a> demonstrates how important the "Executable Web" aspect of Web 2.0 (next generation Web comprising two complimentary tracks: Executable Web of Web Services and Syndicated Web or XML based content such as <a href="http://blogs.law.harvard.edu/tech/rss">RSS</a>, <a href="http://www.w3.org/RDF/">RDF</a>, <a href="http://www.opml.org/">OPML</a>, <a href="http://internetalchemy.org/ocs/">OCS</a>, <a href="http://www.foaf-project.org/">FOAF</a> etc.). <blockquote>Q: Amazon.com now runs sites and on-line operations for retailers such as Target and Toys 'R' Us. What's the future for that services business? A: It's a rapidly growing part of our business. And that goes from [large] companies that are customers of that all the way down to individuals using our Web services to tap into the fundamental platform that is Amazon.com. They can build their own applications very effectively. It's almost closer to an ecosystem. Q: So Amazon is becoming a kind of software platform a bit like Microsoft (MSFT )? A: People are building stuff that surprises us. That's what's so interesting about this. We've built this big base of technology to serve ourselves, and now we're opening it up and letting people access it. They're taking these fundamental pieces and building completely new things that not only would we have never gotten around to but in some cases maybe never even have thought of. There are thousands of developers who are building applications using Amazon Web services. The sky's the limit on their creativity. Q: What arises from all those efforts? A: People will be able to build very powerful applications by hooking together a whole bunch of Web services from a whole bunch of different companies. Q: What benefit is Amazon.com getting from this? A: It's too early to say. It's certainly not a major source of revenue for us. But when people use our Web services, they give us credit for that. That turns out to be very helpful. </blockquote> A few years ago the race was on to simply have a Web Site, then this requirement evolved into a requirement for a database driven site. Today we are seeing the final stages of the Web 2.0 inflection which will inevitably change the focus toward the need for a Point of Presence on the Web for exposing or invoking Web Services and/or Syndicating or Subscribing to XML based content.
The Well-Formed Web
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-08-22#245
2003-08-22T18:32:02Z
2006-06-22T08:56:58-04:00
<P>I just came across this article while brainstorming about the <A href="http://wellformedweb.org/story/9/#auto">Comment API</A> and it's potential use (subject of another post as this is being implemented as I write) within Blog Clients (RSS Aggregators and Readers).</P> <P>Back to the article. This is an essay by <A href="http://bitworking.org/foaf.rdf">George Gregorio </A>who is so into auto discovery that he deliberately stuffed his contact details in an FOAF file that you need to auto discover using a FOAF auto discovery aware client (e.g. FOAFnaut or the human brain for instance :-) ) . Anyway, he is an excerpt from his essay (a very good read).</P> <BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"> <P>Over a month ago <A href="http://www.ftrain.com/">Paul Ford</A> published a great essay entitled <A href="http://www.ftrain.com/google_takes_all.html">How Google beat Amazon and Ebay to the Semantic Web</A>. After reading it the first time I thought it was a great introduction to the <A href="http://www.w3.org/2001/sw/">Semantic Web</A>, an idea I had been trying to wrap my head around even since encountering RDF as it is baked into <A title="RDF Site Summary" href="http://www.purl.org/rss/1.0/spec">RSS 1.0</A>. I had seen the light and bought into the promise of the Semantic Web. </P> <P>Time passes...</P> <P><!--StartFragment -->With Dave Winer's floating of the idea of <A href="http://backend.userland.com/rss">RSS 2.0</A> discussions ensue about the RDF in RSS 1.0. After spending some time badgering poor Bill Kearney for a <A href="http://burningbird.net/cgi-bin/mt-comments.cgi?entry_id=528">concrete benefit of having RDF in RSS 1.0</A> and not getting a really satisfactory answer I went back and read Paul Ford's essay again. I wanted to get that old religious feeling back again. It didn't work. The magic was gone. </P></BLOCKQUOTE> <P dir=ltr><A href="http://wellformedweb.org/story/1">Read on...</A></P> <P> </P>
Cool XSL-T Tutorial
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-08-22#244
2003-08-22T04:07:59Z
2006-06-22T08:56:58-04:00
XSLT is one of the most powerful aspects of the entire XML value proposition (this weblog site is an example of what XML and XSLT can deliver), but is also one of the more daunting aspects (both hands-on and getting your brain wrapped around the syntax). Here is a really nice <a href="http://www.zvon.org/xxl/XSLTutorial/Books/Output/example1_ch1.html">XSLT tutorial</a> site. Demystify XSLT, and the world of XML's potential really opens up. It certainly accelerates the comprehension to the concept of <a href="http://jena.hpl.hp.com:3030/blojsom-hp/blog/technologies/blogging/metadata/?">generating RSS from internal data sources</a> - bearing in mind that in the case of <a href="http://www.openlinksw.com/virtuoso">Virtuoso</a> we use our in-built XSLT processor for facilitate XML-RPC to SOAP bridging, SQL-XML, RSS, OPML, RDF, FOAF, Atom|Echo, OCS feed generation amongst other things.
RSS: INJAN (It's not just about news)
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-08-21#241
2003-08-21T15:41:25Z
2006-06-22T08:56:58-04:00
<p><span style="font-size: 10pt; font-family: Arial;">When Virtuoso first unleashed support for XML (in-built XSL, Native XML Storage, Validating XML Parser, XPath, and XQuery) the core message was the delivery of a single server solution that would address the challenges of creating XML data.</span></p><p xmlns="o"></p> <p><span style="font-size: 10pt; font-family: Arial;">In the year 2000 the question of the shape and form of XML data was unclear to many, and reading the article below basically took me back in time to when we released <a href="http://www.it-director.com/article.php?articleid=916">Virtuoso 2.0</a> (we are now at <a href="http://www.openlinksw.com/virtuoso">release 3.0</a> commercially with a <a href="http://www.openlinksw.com/press/virt32_wwdc1.htm">3.2 beta </a>dropping any minute).</span></p><p xmlns="o"></p> <p><span style="font-size: 10pt; font-family: Arial;">RSS is a great XML application, and it does a great job of demonstrating how XML --the new data access foundation layer-- will galvanize the next generation Web (I refer to this as Web 2.0.). </span></p> <blockquote dir="ltr" style="margin-right: 0px;"><span style="font-size: 10pt; font-family: Arial;"> <p><a href="http://jena.hpl.hp.com:3030/blojsom-hp/blog/technologies/blogging/metadata/?permalink=1214847A10C1966396472E816A7A4243.textile">RSS: INJAN (It's not just about news)</a> </p> <p><span class="caps">RSS</span> is not just about news, according to <a href="http://groups.yahoo.com/group/rss-dev/message/5764">Ian Davis on rss-dev</a>.<br />He presents a nice list of alternatives, which I reproduce here (and to which I�d add, of course, bibliography management)</p> <ul> <li>Sitemaps: one of the S�s in <span class="caps">RSS</span> stands for summary. A sitemap is a summary of the content on a site, the items are pages or content areas. This is clearly a non-chronological ordering of items. Is a hierarchy of <span class="caps">RSS</span> sitemaps implied here � how would the linking between them work? How hard would it be to hack a web browser to pick up the <span class="caps">RSS</span> sitemap and display it in a sidebar when you visit the site?</li> <li>Small ads: also known as classifieds. These expire so there�s some kind of dynamic going on here but the ordering of items isn�t necessarily chronological. How to describe the location of the seller, or the condition of the item or even the price. Not every ad is selling something � perhaps it�s to rent out a room.</li> <li>Personals: similar model to the small ads. No prices though (I hope). Comes with a ready made vocabulary of terms that could be converted to an <span class="caps">RDF</span> schema. Probably should do that just for the hell of it anyway � gsoh</li> <li>Weather reports: how about a week�s worth of weather in an <span class="caps">RSS</span> channel. If an item is dated in the future, should an aggregator display it before time? Alternate representations include maps of temperature and pressure etc.</li> <li>Auctions: again, related to small ads, but these are much more time limited since there is a hard cutoff after which the auction is closed. The sequence of bids could be interesting � would it make sense to thread them like a discussion so you can see the tactics?</li> <li>TV listings: this is definitely chronological but with a twist � the items have durations. They also have other metadata such as cast lists, classification ratings, widescreen, stereo, program type. Some types have additional information such as director and production year.</li> <li>Top ten listings: top ten singles, books, dvds, richest people, ugliest, rear of the year etc. Not chronological, but has definate order. May update from day to day or even more often.</li> <li>Sales reporting: imagine if every department of a company reported their sales figures via <span class="caps">RSS</span>. Then the divisions aggregate the departmental figures and republish to the regional offices, who aggregate and add value up the chain. The chairman of the company subscribes to one super-aggregate feed.</li> <li>Membership lists / buddy lists: could I publish my buddy list from Jabber or other instant messengers? Maybe as an interchange format or perhaps could be used to look for shared contacts. Lots of potential overlap with <span class="caps">FOAF</span> here.</li> <li>Mailing lists: or in fact any messaging system such as usenet. There are some efforts at doing this already (e.g. yahoogroups) but we need more information � threads; references; headers; links into archives.</li> <li>Price lists / inventory: the items here are products or services. No particular ordering but it�d be nice to be able to subscribe to a catalog of products and prices from a company. The aggregator should be able to pick out price rises or bargains given enough history.</li> <div align="right">[via <a href="http://jena.hpl.hp.com:3030/blojsom-hp/blog/">Semantic Blogging Demonstrator</a>] </div></ul></span></blockquote> <p><span style="font-size: 10pt; font-family: Arial;">Thus, if we can comprehend RSS (the blog article below does a great job) we should be able to see the fundamental challenges that are before any organization seeking to exploit the potential of the imminent Web 2.0 inflection; how will you cost-effectively create XML data from existing data sources? Without upgrading or switching database engines, operating systems, programming languages? Put differently how can you exploit this phenomenon without losing your ever dwindling technology choices (believe me choices are dwindling fast but most are oblivious to this fact).</span></p><p xmlns="o"></p> <p> </p> <a href="index.vspx?tag=xml" rel="tag" style="display:none;">xml</a><a href="index.vspx?tag=rss" rel="tag" style="display:none;">rss</a><a href="index.vspx?tag=syndication" rel="tag" style="display:none;">syndication</a>
Do We Need the Semantic Web?
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-08-05#231
2003-08-05T15:43:30Z
2006-06-22T08:56:58-04:00
0
Semantic Web Client UI Diagram
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-31#347
2003-05-31T22:08:00Z
2006-06-22T08:56:58-04:00
<a href="http://www.xulplanet.com/cgi-bin/ndeakin/homeN.cgi?ai=136">Semantic Web Client UI Diagram</a> I'm getting really excited by this Semantic Web stuff I'm doing. here's a screenshot / diagram of how it works to display some dynamic UI based on FOAF, RSS, and some movie information. The UI is written using a number of small (less than 1K) XUL and XBL files, although any kind of XML file can theoretically be used. <div align="right">[via <a href="http://www.xulplanet.com/ndeakin/">Neil's Place</a>] <div></div></div><em>This is simply cool!</em>
Semantic Web Client UI Diagram
http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-31#78
2003-05-31T22:08:00Z
2006-06-22T08:56:58-04:00
<A href="http://www.xulplanet.com/cgi-bin/ndeakin/homeN.cgi?ai=136">Semantic Web Client UI Diagram</A> I'm getting really excited by this Semantic Web stuff I'm doing. here's a screenshot / diagram of how it works to display some dynamic UI based on FOAF, RSS, and some movie information. The UI is written using a number of small (less than 1K) XUL and XBL files, although any kind of XML file can theoretically be used. <DIV align=right>[via <A href="http://www.xulplanet.com/ndeakin/">Neil's Place</A>] <DIV></DIV></DIV><EM>This is simply cool!</EM>