Re: How do OBO ontologies work on the LOD?

Hi Kinglsey,

We don't do content negotiation. I've written concerning why, in the past,
to some of the W3C groups.  I don't like the practice because it muddies up
what exactly the URI means. So we use a not uncommon technique of
responding to requests uniformly, with RDF/XML, and providing a stylesheet
for rendering in the browser.

As far as I know this is consistent with the aims of LOD. The underlying
information is in RDF but if you put a URL into your browser you get back
human readable information. Is the issue here that some computer wants
human readable information? In my prototypes I had a foaf:page link to
html. I will ask that this be added to Ontobee and the computers can use
that.

-Alan

On Thu, Feb 23, 2012 at 3:40 PM, Kingsley Idehen <kidehen@openlinksw.com>wrote:

> On 2/23/12 1:32 PM, Peter DeVries wrote:
>
>> However, I think testing using the Vapour Validator is easier to
>> understand.
>>
>> This might best be shown in comparison to a LOD OWL class that works
>> correctly,
>>
>> OBO Ontology URI http://purl.org/obo/owl/HAO#**HAO_0000000<http://purl.org/obo/owl/HAO#HAO_0000000>
>>
>> Mapped URI http://purl.obolibrary.org/**obo/HAO_0000000<http://purl.obolibrary.org/obo/HAO_0000000>
>>
>> HTML Page http://api.hymao.org/public/**ontology_class/show_expanded/**
>> 4048 <http://api.hymao.org/public/ontology_class/show_expanded/4048>
>>
>> Check in the Vapour Validator http://validator.linkeddata.**org/vapour<http://validator.linkeddata.org/vapour>
>>
>> For comparison
>>
>> URI for the Species Apis mellifera http://lod.taxonconcept.org/**
>> ses/z9oqP#Species <http://lod.taxonconcept.org/ses/z9oqP#Species>
>>
>> Human Page http://lod.taxonconcept.org/**ses/z9oqP.html<http://lod.taxonconcept.org/ses/z9oqP.html>
>>
>> Check the URI using the  Vapour Validator
>>
>> It is my opinion that this ontology could have been (and could still be
>> modified to) implemented in a way that followed LOD best practices.
>>
>> My concern is that other groups like the beetle people
>> (Coleopterologists) etc. would see the HAO ontology and assume that they
>> should also use OBO.
>>
>
> How about using URI Debugger [1] to iron out the Linked Data principles
> concerns.
>
> Start here:
> http://linkeddata.informatik.**hu-berlin.de/uridbg/index.php?**
> url=http%3A%2F%2Fpurl.org%**2Fobo%2Fowl%2FHAO%23HAO_**
> 0000000&useragentheader=&**acceptheader=<http://linkeddata.informatik.hu-berlin.de/uridbg/index.php?url=http%3A%2F%2Fpurl.org%2Fobo%2Fowl%2FHAO%23HAO_0000000&useragentheader=&acceptheader=>
>
> Follow the 302 response "Location:" value, note what's returned compared
> to actual mime type in response headers.
>
> Example:
>
> HTTP/1.1 200 OK
> Date: Thu, 23 Feb 2012 20:11:06 GMT
> Server: Apache/2.2.14 (Ubuntu)
> Last-Modified: Wed, 22 Feb 2012 20:53:47 GMT
> ETag: "10c0630-4bfb71-4b993b94cecc0"
> Accept-Ranges: bytes
> Content-Length: 4979569
> Content-Type: text/plain; charset=UTF-8
> Vary: Accept-Encoding
>
> But the actual content is RDF/XML .
>
> Play around with different mime types via "Accept:" when alternative
> representation requests etc.. Example re. Turtle request:
>
> HTTP/1.1 200 OK
> Date: Thu, 23 Feb 2012 20:11:46 GMT
> Server: Apache/2.2.14 (Ubuntu)
> Last-Modified: Wed, 22 Feb 2012 20:53:47 GMT
> ETag: "10c0630-4bfb71-4b993b94cecc0"
> Accept-Ranges: bytes
> Content-Length: 4979569
> Content-Type: text/plain; charset=UTF-8
> Vary: Accept-Encoding
>
> But actual content is RDF/XML .
>
>
> I think this is the place where Linked Data problems are arising.
>
> Links:
>
> 1. http://linkeddata.informatik.**hu-berlin.de/uridbg/<http://linkeddata.informatik.hu-berlin.de/uridbg/>-- URI Debugger .
>
> --
>
> Regards,
>
> Kingsley Idehen
> Founder&  CEO
>
> OpenLink Software
> Company Web: http://www.openlinksw.com
> Personal Weblog: http://www.openlinksw.com/**blog/~kidehen<http://www.openlinksw.com/blog/~kidehen>
> Twitter/Identi.ca handle: @kidehen
> Google+ Profile: https://plus.google.com/**112399767740508618350/about<https://plus.google.com/112399767740508618350/about>
> LinkedIn Profile: http://www.linkedin.com/in/**kidehen<http://www.linkedin.com/in/kidehen>
>
>
>
>
>
>
>