 |
 |
Heya Eric: The main thing you'd want to do would be to make sure URIs like: http://infomotions.com/etexts/literature/english/1500-1599/more-utopia-221 returned something useful for both people and machine agents. The nitty gritty details of how to do this can roughly be found in the Cool URIs for the Semantic Web [1], or How to Publish Linked Data [2]. A slight variation would be to use something like RDFa [3] to embed metadata in your HTML docs, or GRDDL [4] to provide a stylesheet to transform some HTML to RDF. The end goal of linked data, is to provide contextual links from your stuff to other resources on the web, aka timbl's rule #4: Include links to other URIs. so that they can discover more things. [3] So for example you might want to assert that: <http://infomotions.com/etexts/literature/english/1500-1599/more-utopia-221> owl:sameAs <http://dbpedia.org/page/Utopia_(book) . or: <http://infomotions.com/etexts/literature/english/1500-1599/more-utopia-221> dcterms:creator <http://dbpedia.org/resource/Thomas_More> . It's when you link out to other resources on the web that things get interesting, more useful, and potentially more messy :-) For example instead of owl:sameAs perhaps an assertion using FRBR or RDA would be more appropriate. Thanks for asking the question. The public-lod list [4] at the w3c is also a really friendly/helpful group of people making data sets available as linked-data. //Ed [1] http://www.w3.org/TR/cooluris/ [2] http://www4.wiwiss.fu-berlin.de/bizer/pub/LinkedDataTutorial/ [3] http://www.w3.org/TR/xhtml-rdfa-primer/ [4] http://www.w3.org/TR/grddl-primer/ [5] http://www.w3.org/DesignIssues/LinkedData.html [6] http://lists.w3.org/Archives/Public/public-lod/