Comments on: rest, the semantic web and my feeble brain http://inkdroid.org/journal/2009/05/14/rest-the-semantic-web-and-my-feeble-brain/ $pithy_personal_mission_statement Wed, 10 Mar 2010 02:04:23 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: inkdroid › web documents and axioms for linked data http://inkdroid.org/journal/2009/05/14/rest-the-semantic-web-and-my-feeble-brain/comment-page-1/#comment-81887 inkdroid › web documents and axioms for linked data Tue, 23 Feb 2010 02:06:53 +0000 http://inkdroid.org/journal/?p=974#comment-81887 [...] email exchange with Richard Cyganiak (one of the architects of the Linked Data pattern) about some trouble I’ve had understanding what Information Resources and Documents are in the context of [...] [...] email exchange with Richard Cyganiak (one of the architects of the Linked Data pattern) about some trouble I’ve had understanding what Information Resources and Documents are in the context of [...]

]]> By: ed http://inkdroid.org/journal/2009/05/14/rest-the-semantic-web-and-my-feeble-brain/comment-page-1/#comment-81536 ed Fri, 22 May 2009 16:02:15 +0000 http://inkdroid.org/journal/?p=974#comment-81536 @herbert yes, in fact we were playing around w/ ore. I just sent a <a href="http://groups.google.com/group/oai-ore/browse_thread/thread/4a71d09b6b5a6feb" rel="nofollow">message</a> to the oai-ore discussion list about the use of the oai-ore vocabulary in the linked data views at chronicling america. @herbert yes, in fact we were playing around w/ ore. I just sent a message to the oai-ore discussion list about the use of the oai-ore vocabulary in the linked data views at chronicling america.

]]> By: hvdsomp http://inkdroid.org/journal/2009/05/14/rest-the-semantic-web-and-my-feeble-brain/comment-page-1/#comment-81533 hvdsomp Tue, 19 May 2009 18:58:44 +0000 http://inkdroid.org/journal/?p=974#comment-81533 @ed thanks for your kind words. regarding your above question, I was wondering whether you had actually considered an ORE approach? I see the following resources: (*) Splash page that gives access to scanned image of newspaper - document resource (*) Scanned image - one or more document resources depending on whether you give each format the same (conneg) or different (non conneg) URI (*) Analog newspaper - non-document resource The above 3 could be aggregated in an ORE Aggregation, itself a non-document resource. Now the URI of the ORE Aggregation is the one to ship around ;-) Anyhow, this is interesting because at a workshop a few months ago at the National Library of Sweden a related issue came up: the library there has the need to glue together the analog newspaper (issue of a day) and all its related digital products, such as the newspaper's website pages, the blog, the blog's comments, the videos, etc. In that context, ORE was also mentioned as a possible solution. @ed thanks for your kind words.

regarding your above question, I was wondering whether you had actually considered an ORE approach? I see the following resources:

(*) Splash page that gives access to scanned image of newspaper – document resource
(*) Scanned image – one or more document resources depending on whether you give each format the same (conneg) or different (non conneg) URI
(*) Analog newspaper – non-document resource

The above 3 could be aggregated in an ORE Aggregation, itself a non-document resource. Now the URI of the ORE Aggregation is the one to ship around ;-)

Anyhow, this is interesting because at a workshop a few months ago at the National Library of Sweden a related issue came up: the library there has the need to glue together the analog newspaper (issue of a day) and all its related digital products, such as the newspaper’s website pages, the blog, the blog’s comments, the videos, etc. In that context, ORE was also mentioned as a possible solution.

]]> By: ed http://inkdroid.org/journal/2009/05/14/rest-the-semantic-web-and-my-feeble-brain/comment-page-1/#comment-81532 ed Tue, 19 May 2009 16:10:11 +0000 http://inkdroid.org/journal/?p=974#comment-81532 @hvdsomp thanks so much, I had seen your ldow2009 ore paper, but not this one on resources! I've been really pleased to see you and the rest of the OAI-ORE folks cross-fertilizing the digital-library/repository and linked-data/semweb crowds. @hvdsomp thanks so much, I had seen your ldow2009 ore paper, but not this one on resources!

I’ve been really pleased to see you and the rest of the OAI-ORE folks cross-fertilizing the digital-library/repository and linked-data/semweb crowds.

]]> By: hvdsomp http://inkdroid.org/journal/2009/05/14/rest-the-semantic-web-and-my-feeble-brain/comment-page-1/#comment-81531 hvdsomp Tue, 19 May 2009 15:46:28 +0000 http://inkdroid.org/journal/?p=974#comment-81531 Ed: Regarding the vocab issue, you might be interested in this paper that was presented at LDOW2009 (where I presented on ORE): An Ontology of Resources for Linked Data (Harry Halpin, Valentina Presutti) - http://events.linkeddata.org/ldow2009/papers/ldow2009_paper19.pdf Ed: Regarding the vocab issue, you might be interested in this paper that was presented at LDOW2009 (where I presented on ORE):

An Ontology of Resources for Linked Data (Harry Halpin, Valentina Presutti) – http://events.linkeddata.org/ldow2009/papers/ldow2009_paper19.pdf

]]> By: ed http://inkdroid.org/journal/2009/05/14/rest-the-semantic-web-and-my-feeble-brain/comment-page-1/#comment-81530 ed Sat, 16 May 2009 12:26:17 +0000 http://inkdroid.org/journal/?p=974#comment-81530 John: interesting, so would it be appropriate to say Topic Maps are more in line with Xiaoshu’s point about the confusion being a vocabulary issue rather than an identity issue? Will need to review Topic Maps again. John: interesting, so would it be appropriate to say Topic Maps are more in line with Xiaoshu’s point about the confusion being a vocabulary issue rather than an identity issue? Will need to review Topic Maps again.

]]> By: ed http://inkdroid.org/journal/2009/05/14/rest-the-semantic-web-and-my-feeble-brain/comment-page-1/#comment-81529 ed Sat, 16 May 2009 12:18:30 +0000 http://inkdroid.org/journal/?p=974#comment-81529 Jeff, yes ... but I thought you were talking about the link rel="alternate" type="text/plain" in the html ... which really does lead you to a text/plain representation. I am already aware of Topic Maps yes, but thanks for the link to your blog post. I am interested in exploring how linked data works in practice primarily at the moment. Jeff, yes … but I thought you were talking about the link rel=”alternate” type=”text/plain” in the html … which really does lead you to a text/plain representation.

I am already aware of Topic Maps yes, but thanks for the link to your blog post. I am interested in exploring how linked data works in practice primarily at the moment.

]]> By: Jeff Young http://inkdroid.org/journal/2009/05/14/rest-the-semantic-web-and-my-feeble-brain/comment-page-1/#comment-81528 Jeff Young Sat, 16 May 2009 02:08:22 +0000 http://inkdroid.org/journal/?p=974#comment-81528 Ed, Look closer at the "View: Text" link at http://chroniclingamerica.loc.gov/lccn/sn85066387/1898-01-01/ed-1/seq-1/. It leads to a text/html representation. If you plan to buy into the Linked Data principles, you should be beware that Topic Maps seem to have a competing philosophy. This blog entry may help you decide which URIs are appropriate for use in the RDF you produce: http://q6.oclc.org/2009/05/linked_datahttp.html. Jeff Ed,

Look closer at the “View: Text” link at http://chroniclingamerica.loc.gov/lccn/sn85066387/1898-01-01/ed-1/seq-1/. It leads to a text/html representation.

If you plan to buy into the Linked Data principles, you should be beware that Topic Maps seem to have a competing philosophy. This blog entry may help you decide which URIs are appropriate for use in the RDF you produce: http://q6.oclc.org/2009/05/linked_datahttp.html.

Jeff

]]> By: jenitennison.com/ http://inkdroid.org/journal/2009/05/14/rest-the-semantic-web-and-my-feeble-brain/comment-page-1/#comment-81525 jenitennison.com/ Fri, 15 May 2009 19:33:57 +0000 http://inkdroid.org/journal/?p=974#comment-81525 I can tell you what we did in a similar situation with the London Gazette. We gave the notices (and issues, and editions) identifier URLs which 303 to an abstract document URL, which content negotiate to a number of different representation URLs. I think that there is a difference between "page 1 of edition 1 of The Call dated 1st Jan 1898" and "a web page that provides information about page 1 of edition 1 of The Call dated 1st Jan 1898". The two items have different publishers and creation dates, for example. Therefore I'd give them separate URIs. If someone requests "page 1 of edition 1 of The Call dated 1st Jan 1898" you redirect them to the "web page about ...". I can tell you what we did in a similar situation with the London Gazette. We gave the notices (and issues, and editions) identifier URLs which 303 to an abstract document URL, which content negotiate to a number of different representation URLs.

I think that there is a difference between “page 1 of edition 1 of The Call dated 1st Jan 1898″ and “a web page that provides information about page 1 of edition 1 of The Call dated 1st Jan 1898″. The two items have different publishers and creation dates, for example. Therefore I’d give them separate URIs. If someone requests “page 1 of edition 1 of The Call dated 1st Jan 1898″ you redirect them to the “web page about …”.

]]> By: johnwcowan http://inkdroid.org/journal/2009/05/14/rest-the-semantic-web-and-my-feeble-brain/comment-page-1/#comment-81524 johnwcowan Fri, 15 May 2009 19:24:18 +0000 http://inkdroid.org/journal/?p=974#comment-81524 Topic Maps gets this right: it distinguishes *in the links* between the use of URIs as subject indicators and their use as information resources. Topic Maps gets this right: it distinguishes *in the links* between the use of URIs as subject indicators and their use as information resources.

]]>