@prefix rdf: . @prefix ns1: . @prefix foaf: . ns1:this rdf:type foaf:Person . @prefix sioct: . rdf:type sioct:Weblog . @prefix atom: . rdf:type atom:Feed . @prefix rdfs: . rdfs:label "kidehen@openlinksw.com's BLOG [127] description" . rdf:type atom:Entry , sioct:BlogPost . @prefix dc: . dc:title "Linked Data in Action: Library of Congress" ; foaf:maker ns1:this ; rdfs:label "Linked Data in Action: Library of Congress" . @prefix dt: . @prefix dcterms: . dcterms:created "2008-06-11T16:36:40Z"^^dt:dateTime ; dcterms:modified "2008-06-11T13:16:31.000010-04:00"^^dt:dateTime . @prefix sioc: . sioc:id "7e5e4894c05acecaa90691e6bcc3c1e6" ; sioc:link ; sioc:content "As I start my countdown to the upcoming Linked Data Planet conference, here is the first of a series of posts geared towards showcasing practical use of the burgeoning Linked Data Web.\nFirst up, the Library of Congress, take a look at the following pages which are "Human" and machine based "User Agent" friendly: \n\n\n Science\n\n\n Humanities\n\n\n Mathematics\n\n\n Cataloging\n\n\n World Wide Web\n\n\n\nKey point: The pages above are served up in line with Linked Data deployment and publishing tenets espoused by the Linking Open Data Community (LOD) which include (in my preferred terminology):\n\n\nGiving "Names" to things you observe (aka Data Source Names or "DSNs" for short)\nUse HTTP URLs in your data source naming scheme so that "access by reference" to your data sources exploits the expanse of the HTTP driven Web i.e make your DSNs "Linked Data Source Names" (LDNS)\nRemember that Documents / Pages are compound in nature, and they aren't the only data sources we would want to name; a document's LDSN must be distinct from the LDSNs used for the subject matter concepts and/or named entities associated with a document\n\n\nUse the RDF Data Model to express structure within your data source(s)\nUse LDSNs when constructing statements/claims/assertions/records (triples) inside your structured data sources \n\nWhen publishing Web Pages related to your data sources; use at least one of the following to methods to guide user agents to data sources associated with your published page; the HTML LINK tag, RDFa, GRDDL, or Content Negotiation.\n\n\nThe items above are features that users and decision makers should start to hone into when seeking, and evaluating, platforms that facilitate cost-effective exploitation of the Linked Data Web. " ; atom:title "Linked Data in Action: Library of Congress" . @prefix ns10: . sioc:has_creator ns10:this ; sioc:has_container . @prefix dbpedia: . sioc:links_to dbpedia:Linked_Data , dbpedia:Named_entity_recognition , . @prefix ns12: . sioc:links_to ns12:this . @prefix ns13: . sioc:links_to ns13:concept . @prefix ns14: . sioc:links_to ns14:concept . @prefix ns15: . sioc:links_to ns15:concept . @prefix ns16: . sioc:links_to ns16:concept . @prefix ns17: . sioc:links_to ns17:concept . @prefix ns18: . sioc:links_to ns18:RPC2 , dbpedia:Content_negotiation , dbpedia:GRDDL , dbpedia:Giant_Global_Graph , dbpedia:RDFa , dbpedia:Topic ; atom:source ; atom:author ns1:this ; atom:published "2008-06-11T16:36:40Z" ; atom:updated "2008-06-11T17:16:31Z" ; sioc:has_reply . @prefix opl: . opl:isDescribedUsing . ns10:this rdf:type sioc:User . rdf:type sioct:Comment , atom:Entry . @prefix rdf: . @prefix ns1: . @prefix foaf: . ns1:this rdf:type foaf:Person ; foaf:made . @prefix atom: . rdf:type atom:Feed . @prefix sioct: . rdf:type sioct:Weblog . @prefix rdfs: . rdfs:label "kidehen@openlinksw.com's BLOG [127] description" . @prefix sioc: . sioc:container_of ; atom:entry ; atom:contains . @prefix ns7: . ns7:this rdf:type sioc:User ; sioc:creator_of . rdf:type atom:Entry , sioct:Comment ; sioc:reply_of .