Alan, (01)
> The browser then gets
> http://ashby.csail.mit.edu/cgi-bin/obiterm.xsl?ref=OBI_0000225 in
> order to get that transform, then applies it to the RDF/XML to
> generate HTML that it can display. (02)
I thought it could be a browser based transformation, I must have
stayed behind as to what browsers do these days (03)
Thanks for the detailed eplanation and additional perspective
I thought this simple question may be hiding some thorny issues (04)
underspecification seems to be a fact of life that we have to deal with,
the work on' minimal recursion ' seems to discuss some related points (05)
The lack of uri referential integrity could make the massive recursive
dereferencing brittle
http://esw.w3.org/topic/DereferenceURI (06)
in addition to what you point out, it looks like such mechanism relies
heavily on the
redirection set to be uptodate/complete, something that an only happen
if it's updated dynamically (on generation of new resource, if
permission is granted by resource owner/admin, redirect) and with
high reliably. I am not sure this is possible yet (07)
so much to be worked out (08)
PDM (09)
On Sat, Oct 4, 2008 at 7:56 PM, Alan Ruttenberg
<alanruttenberg@xxxxxxxxx> wrote:
> On Sat, Oct 4, 2008 at 8:46 PM, Pat Hayes <phayes@xxxxxxx> wrote:
>>
>> On Oct 4, 2008, at 2:46 AM, paola.dimaio@xxxxxxxxx wrote:
>>
>>> Cool thanks
>>>
>>> it renders well in firefox without extension
>>> but I am not sure understand how one uri can be viewed both as rdf
>>> source and html
>>
>> It is resolved by 'content negotiation', a similar technique used for
>> example to decide which language version you get of a multi-language-
>> edition newspaper. To regard these editions as a single resource is
>> considered good Web practice according to the W3C Architectural
>> guidelines, but the extension of this to the HTML/RDF distinction is
>> currently more controversial. So this might be good practice,
>> depending on how the current debates about RDF and content negotiation
>> finally settle out. In the meantime one should probably treat it as
>> provisionally good practice, or maybe experimental good practice.
>
> Ahem.
>
> There is not a whiff of content negotiation, which I don't like
> because it makes it confusing to figure out what resource the URI
> names. I do not consider using content negotiation good practice, even
> provisionally.
>
> The specific series of events that happens when the browser does a get
> of http://purl.obofoundry.org/obo/OBI_0000225
>
> purl.obofoundry.org is a cname for purl.org, so purl.org is where a
> request is sent.
>
> purl.org has a redirect set so that a request to
> http://purl.obofoundry.org/obo/OBI_0000225 results in a directive that
> says - look for what you are looking at
> http://sw.neurocommons.org/obiterm/OBI_0000225 (a 302 response)
>
> (here's the purl information
>
>http://purl.obofoundry.org/maint/display.pl.cgi?noedit=on&purl=/obo/OBI_0000225&id=nobody)
>
> A get of http://sw.neurocommons.org/obiterm/OBI_0000225 returns a 303
> response, which says: I can't give you the resource you want (the
> "universal" investigation site) how about this instead, where "this"
> is http://ashby.csail.mit.edu/cgi-bin/obiterm?ref=OBI_0000225
>
> This protocol - using a 303 response to indicate that the entity named
> is not the sort of thing you can "get" over the network - is called
> httpRange-14 http://www.w3.org/2001/tag/issues.html#httpRange-14
>
> Note: the relation between what you ask for and what you are given is
> currently underspecified. Here one might consider it "provisional good
> practice" that one serves RDF/XML that contains statements about the
> resource.
>
> A get on that URI retrieves OWL statements about the resource. The OWL
> is serialized as RDF/XML. RDF/XML is XML, and so can have a stylesheet
> directive that says how it can be transformed to be displayed in a
> browser. This is similar in spirit to the model/view distinction in
> engineering user interfaces. The model is the RDF, the view is
> generated from the model. The stylesheet directive looks like this:
>
> <?xml-stylesheet type="text/xsl"
> href="http://ashby.csail.mit.edu/cgi-bin/obiterm.xsl?ref=OBI_0000225";?>
>
> The browser then gets
> http://ashby.csail.mit.edu/cgi-bin/obiterm.xsl?ref=OBI_0000225 in
> order to get that transform, then applies it to the RDF/XML to
> generate HTML that it can display.
>
> For those that might think that this looks like a lot of traffic to
> generate the page, I'll remind that there are a variety of ways that
> this same information can be retrieved much more efficiently, for
> example the whole OBI OWL file
> (http://purl.obofoundry.org/obo/obi.owl), or as a query against the
> Neurocommons triple store at http://sparql.neurocommons.org/ . For the
> single dereference of a citable name, we consider it more important
> that we try as best possible to not confuse what the URI denotes, and
> to have systems in place that reduce as much as possible the chance
> that there be incentive to give another name (URI) for the same
> entity.
>
> -Alan
>
>
>
>>
>> Pat
>>
>>>
>>>
>>> or do we have more than one uri for the same resource? if so, is that
>>> legal/good practice?
>>>
>>> thanks
>>>
>>> PDM
>>>
>>>
>>> On Sat, Oct 4, 2008 at 12:35 AM, Alan Ruttenberg
>>> <alanruttenberg@xxxxxxxxx> wrote:
>>>> Whoops, typo: That should be: http://purl.obofoundry.org/obo/OBI_0000225
>>>> Thanks for noticing!
>>>> Note that if you view source, you will see RDF rather than HTML. The
>>>> HTML is browser only, generated by a stylesheet instruction.
>>>> -Alan
>>>>
>>>> On Sat, Oct 4, 2008 at 3:19 AM, <paola.dimaio@xxxxxxxxx> wrote:
>>>>>> - http://purl.obofoundry.org/obo/OBO_0000225 - an example of what
>>>>>> we
>>>>>> think should be a typical response for an ontology term
>>>>>
>>>>> Alan, when click on that url with firefox i get redirected to
>>>>> http://www.berkeleybop.org/ontologies/OBO_0000225
>>>>>
>>>>> and see 'object not found'
>>>>> is this the response to be expecting, or suggesting should be
>>>>> expected?
>>>>>
>>>>>
>>>>> --PDM
>>>>>
>>>>> _________________________________________________________________
>>>>> Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
>>>>> Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
>>>>> Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
>>>>> Shared Files: http://ontolog.cim3.net/file/
>>>>> Community Wiki: http://ontolog.cim3.net/wiki/
>>>>> To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx
>>>>>
>>>>>
>>>>
>>>> _________________________________________________________________
>>>> Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
>>>> Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
>>>> Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
>>>> Shared Files: http://ontolog.cim3.net/file/
>>>> Community Wiki: http://ontolog.cim3.net/wiki/
>>>> To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Paola Di Maio
>>> School of IT
>>> www.mfu.ac.th
>>> *********************************************
>>>
>>> _________________________________________________________________
>>> Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
>>> Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
>>> Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
>>> Shared Files: http://ontolog.cim3.net/file/
>>> Community Wiki: http://ontolog.cim3.net/wiki/
>>> To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx
>>>
>>>
>>>
>>
>> ------------------------------------------------------------
>> IHMC (850)434 8903 or (650)494 3973
>> 40 South Alcaniz St. (850)202 4416 office
>> Pensacola (850)202 4440 fax
>> FL 32502 (850)291 0667 mobile
>> phayesAT-SIGNihmc.us http://www.ihmc.us/users/phayes
>>
>>
>>
>>
>>
>>
>> _________________________________________________________________
>> Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
>> Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
>> Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
>> Shared Files: http://ontolog.cim3.net/file/
>> Community Wiki: http://ontolog.cim3.net/wiki/
>> To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx
>>
>>
> (010)
--
Paola Di Maio
School of IT
www.mfu.ac.th
********************************************* (011)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx (012)
|