« Trying Chromium OS | Main | Corporate VIAF »

Comments

Ryan Shaw

http://viaf.org/viaf/99366184 is the 'real world object', a concept. On resolution it does a 303 redirect to http://viaf.org/viaf/99366184/ the generic document.

That seems extremely error-prone. Why not URIs that are more clearly distinguishable, something like http://viaf.org/viaf/99366184 and http://viaf.org/viaf/99366184/document?

Response: We've gone back and forth on this. Granted, the difference between viaf/123 and viaf/123/ is subtle, but since the only clients that care are probably those interested in the RDF, we decided there wouldn't be much confusion. People are used to similar sorts of redirection happening on URLs in their browsers all the time.
--Th

Metazool

Thanks for your writing about VIAF.

Checking out the RDF representation of the links above - e.g. by doing this:

curl -H "Accept: application/rdf+xml" http://viaf.org/viaf/99366184/

The RDF/XML returned has relative links in some of the rdf:about statements - e.g. "viaf/99366184/#etcetc"

Shouldn't the links be qualified / absolute - e.g. "/viaf/99366184/#etcetc" or "http://viaf.org/viaf/etc" ?

Response: We like relative URIs. It keeps everything shorter and more portable. The xml:base ( of http://viaf.org/) in the rdf:RDF should take care of making everything work.
--Th

Metazool

The same problem with relative links also appears on the HTML view of the record, in the "Record Views" section with links to other XML formats.

Response: You are correct, the HTML is wrong. We'll fix that right away. Thanks!
--Th

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment

Comments are moderated, and will not appear until the author has approved them.

Your Information

(Name is required. Email address will not be displayed with the comment.)

My Photo

April 2018

Sun Mon Tue Wed Thu Fri Sat
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30          
https://outgoing.typepad.com/outgoing/2010/05/viafs-new-linked-data.html?cid=6a00d83459bf2269e20133ef05e4be970b
outgoing.typepad.com
crawl=CC-MAIN-2019-26
41009
application/http; msgtype=response
sha1:A4O55474KUFMBORUGLHSJKSGUWBGNRZT
<urn:uuid:904c6290-3b83-457f-9495-74402bebd7a3>
2019-06-17T16:44:28Z
104.18.137.190
application/xhtml+xml
sha1:JDYZ6M5PLX4KC3QS7ATUXBDUGHOQIGWH
<urn:uuid:55b65c6c-5398-4566-b2ad-e8aa221e30a7>
https://outgoing.typepad.com/outgoing/2010/05/viafs-new-linked-data.html?cid=6a00d83459bf2269e20133ef05e4be970b
response
<urn:uuid:e53abdc3-6264-4f3a-a69f-267b57d90c81>
isPartOf: CC-MAIN-2019-26
publisher: Common Crawl
description: Wide crawl of the web for June 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-123-210-107.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/