@prefix rdfs: . @prefix ns1: . ns1:this rdfs:label "Kingsley Idehen" . @prefix rdf: . @prefix ns3: . @prefix foaf: . ns3:this rdf:type foaf:Person . @prefix sioct: . rdf:type sioct:Weblog . @prefix atom: . rdf:type atom:Feed ; rdfs:label "kidehen@openlinksw.com's BLOG [127] description" . rdf:type atom:Entry , sioct:BlogPost ; rdfs:label "So, What Does \"HREF\" Stand For, Anyway" . rdf:type sioct:BlogPost , atom:Entry ; rdfs:label "Linked Data & Identity" . rdf:type atom:Entry , sioct:BlogPost ; rdfs:label "Linked Data Rules Simplified" . rdf:type sioct:BlogPost , atom:Entry ; rdfs:label "Exploring the Value Proposition of Linked Data" . rdf:type atom:Entry , sioct:BlogPost . @prefix dc: . dc:title "The URI, URL, and Linked Data Meme's Generic HTTP URI (Updated)" ; foaf:maker ns3:this ; rdfs:label "The URI, URL, and Linked Data Meme's Generic HTTP URI (Updated)" . @prefix dt: . @prefix dcterms: . dcterms:created "2009-08-07T14:34:50-04:00"^^dt:dateTime ; dcterms:modified "2010-03-28T12:19:00-04:00"^^dt:dateTime . @prefix sioc: . sioc:id "3238064d1ff52eafbea3498ddb8af936" ; sioc:link ; sioc:content "\n\tSituation Analysis\n\n\tAs the "Linked Data" meme has gained momentum you've more than likely been on the receiving end of dialog with Linked Open Data community members (myself included) that goes something like this:\n\n\t"Do you have a URI", "Get yourself a URI", "Give me a de-referencable URI" etc..\n\n\n\tAnd each time, you respond with a URL -- which to the best of your Web knowledge is a bona fide URI. But to your utter confusion you are told: Nah! You gave me a Document URI instead of the URI of a real-world thing or object etc..\n\n\tWhat's up with that?\n\n\tWell our everyday use of the Web is an unfortunate conflation of two distinct things, which have Identity: Real World Objects (RWOs) & Address/Location of Documents (Information bearing Resources).\n\n\tThe "Linked Data" meme is about enhancing the Web by unobtrusively reintroducing its core essence: the generic HTTP URI, a vital piece of Web Architecture DNA. Basically, its about so realizing the full capabilities of the Web as a platform for Open Data Identification, Definition, Access, Storage, Representation, Presentation, and Integration.\n\n\tWhat is a Real World Object?\n\n\tPeople, Places, Music, Books, Cars, Ideas, Emotions etc..\n\n\tWhat is a URI?\n\n\tA Uniform Resource Identifier. A global identifier mechanism for network addressable data items. Its sole function is Name oriented Identification.\n\n\tURI Generic Syntax\n\n\tThe constituent parts of a URI (from URI Generic Syntax RFC) are depicted below: \n\n\n\tWhat is a URL?\n\n\tA location oriented HTTP scheme based URI. The HTTP scheme introduces a powerful and inherent duality that delivers:\n\n\t\n\t\tResource Address/Location Identifier\n\t\n\t\tData Access mechanism for an Information bearing Resource (Document, File etc..)\n\n\n\tSo far so good!\n\n\tWhat is an HTTP based URI?\n\n\tThe kind of URI Linked Data aficionados mean when they use the term: URI.\n\n\tAn HTTP URI is an HTTP scheme based URI. Unlike a URL, this kind of HTTP scheme URI is devoid of any Web Location orientation or specificity. Thus, Its inherent duality provides a more powerful level of abstraction. Hence, you can use this form of URI to assign Names/Identifiers to Real World Objects (RWO). Even better, courtesy of the Identity/Address duality of the HTTP scheme, a single URI can deliver the following:\n\n\t\n\t\tRWO Identfier/Name\n\t\n\t\tRWO Metadata document Locator (courtesy of URL aspect)\n\t\n\t\tNegotiable Representation of the Located Document (courtesy of HTTP's content negotiation feature).\n\n\n\tWhat is Metadata?\n\n\tData about Data. Put differently, data that describes other data in a structured manner.\n\n\tHow Do we Model Metadata?\n\n\tThe predominant model for metadata is the Entity-Attribute-Value + Classes & Relationships model (EAV/CR). A model that's been with us since the inception of modern computing (long before the Web).\n\n\tWhat about RDF?\n\n\tThe Resource Description Framework (RDF) is a framework for describing Web addressable resources. In a nutshell, its a framework for adding Metadata bearing Information Resources to the current Web. Its comprised of:\n\n\t\n\t\tEntity-Attribute-Value (aka. Subject-Predictate-Object) plus Classes & Relationships (Data Dictionaries e.g., OWL) metadata model\n\t\n\t\tA plethora of instance data representation formats that include: RDFa (when doing so within (X)HTML docs), Turtle, N3, TriX, RDF/XML etc.\n\n\n\tWhat's the Problem Today?\n\n\tThe ubiquitous use of the Web is primarily focused on a Linked Mesh of Information bearing Documents. URLs rather than generic HTTP URIs are the prime mechanism for Web tapestry; basically, we use URLs to conduct Information -- which is inherently subjective -- instead of using HTTP URIs to conduct "Raw Data" -- which is inherently objective.\n\n\tNote: Information is "data in context", it isn't the same thing as "Raw Data". Thus, if we can link to Information via the Web, why shouldn't we be able to do the same for "Raw Data"?\n\n\tHow Does the Link Data meme solve the problem?\n\n\tThe meme simply provides a set of guidelines (best practices) for producing Web architecture friendly metadata. Meaning: when producing EAV/CR model based metadata, endow Subjects, their Attributes, and Attribute Values (optionally) with HTTP URIs. By doing so, a new level of Link Abstraction on the Web is possible i.e., "Data Item to Data Item" level links (aka hyperdata links). Even better, when you de-reference a RWO hyperdata link you end up with a negotiated representations of its metadata.\n\n\tConclusion\n\n\tLinked Data is ultimately about an HTTP URI for each item in the Data Organization Hierarchy :-)\n\n\tRelated\n\n\t\n\t\tHistory of how "Resource" became part of URI - historic account by TimBL\n\n\t\n\t\tLinked Data Design Issues Document - TimBL's initial Linked Data Guide\n\t\n\t\tLinked Data Rules Simplified - My attempt at simplifying the Linked Data Meme without SPARQL & RDF distraction\n\t\n\t\tLinked Data & Identity - another related post\n\t\n\t\tThe Linked Data Meme's Value Proposition\n\n\t\n\t\tSo What Does "HREF" stand for anyway?\n\n\t\n\t\tMy Del.icio.us hosted Bookmark Data Space for Identity Schemes\n\n\t\n\t\tTimBL's Ted Talk re. "Raw Linked Data"\n\n\t\n\t\tResource Oriented Architecture\n\n\t\n\t\tMore Famous Than Simon Cowell .\n\n" ; atom:title "The URI, URL, and Linked Data Meme's Generic HTTP URI (Updated)" . @prefix ns11: . sioc:has_creator ns11:this ; sioc:has_container ; sioc:links_to , , ns1:this . @prefix dbpedia: . sioc:links_to dbpedia:Entity-attribute-value_model . @prefix ns13: . sioc:links_to ns13:identifier_scheme , dbpedia:Uniform_Resource_Locator , dbpedia:Uniform_Resource_Identifier , dbpedia:Web_Ontology_Language , , . @prefix ns14: . sioc:links_to ns14:roa-rest-of-rest , dbpedia:Information , dbpedia:RDFa , dbpedia:SPARQL , . @prefix ns15: . sioc:links_to ns15:i , , dbpedia:Data_hierarchy , , dbpedia:Meme , dbpedia:Data_dictionary , , , dbpedia:Knowledge , , dbpedia:Linked_Data ; atom:source ; atom:author ns3:this ; atom:published "2009-08-07T18:34:50Z" ; atom:updated "2010-03-28T16:19:00Z" ; sioc:has_reply , , , . @prefix opl: . opl:isDescribedUsing . rdf:type atom:Entry , sioct:Comment ; rdfs:label "Re:The URI, URL, and Linked Data Meme's Generic HTTP URI" . rdf:type atom:Entry , sioct:Comment ; rdfs:label "Re:The URI, URL, and Linked Data Meme's Generic HTTP URI" . ns11:this rdf:type sioc:User . rdf:type atom:Entry , sioct:Comment . rdf:type sioct:Comment , atom:Entry . @prefix rdf: . @prefix atom: . rdf:type atom:Entry . @prefix sioct: . rdf:type sioct:BlogPost . @prefix rdfs: . rdfs:label "Data 3.0 (a Manifesto for Platform Agnostic Structured Data) Update 5" . @prefix sioc: . sioc:links_to . rdf:type sioct:BlogPost , atom:Entry ; rdfs:label "SPARQL Guide for the Javascript Developer " ; sioc:links_to . rdf:type sioct:BlogPost , atom:Entry ; rdfs:label "SPARQL Guide for the PHP Developer" ; sioc:links_to . @prefix ns5: . @prefix foaf: . ns5:this rdf:type foaf:Person ; foaf:made . rdf:type sioct:Weblog , atom:Feed ; rdfs:label "kidehen@openlinksw.com's BLOG [127] description" ; sioc:container_of ; atom:entry ; atom:contains . rdf:type atom:Entry , sioct:Comment ; rdfs:label "Re:The URI, URL, and Linked Data Meme's Generic HTTP URI" ; sioc:reply_of . rdf:type atom:Entry , sioct:Comment ; rdfs:label "Re:The URI, URL, and Linked Data Meme's Generic HTTP URI" ; sioc:reply_of . @prefix ns7: . ns7:this rdf:type sioc:User ; sioc:creator_of . rdf:type sioct:BlogPost , atom:Entry ; rdfs:label "SPARQL for the Ruby Developer" ; sioc:links_to . rdf:type sioct:BlogPost , atom:Entry ; rdfs:label "SPARQL Guide for the Perl Developer" ; sioc:links_to . rdf:type sioct:BlogPost , atom:Entry ; rdfs:label "One Technology That Will Rock 2010 (Update 1)" ; sioc:links_to . rdf:type atom:Entry , sioct:Comment ; sioc:reply_of . rdf:type sioct:Comment , atom:Entry ; sioc:reply_of . rdf:type sioct:BlogPost , atom:Entry ; rdfs:label "SPARQL Guide for Python Developer" ; sioc:links_to .