From: Rutger V. <rut...@gm...> - 2010-06-03 17:36:35
|
I think the problem we want to solve is that we can give a canonical treebase purl to a linkeddata browser and it can do something with it, whether that's through conneg is almost secondary. Linkeddata browsers apparently (according to @rdmpage, mind) expect 303, but our purls give them 302. They won't know what to do with that, so until we reconfigure our purls, we can't use them in a linkeddata context. On Wed, Jun 2, 2010 at 10:15 PM, Hilmar Lapp <hl...@ne...> wrote: > I don't think the issue is that easy. Without content negotiation, the 303 > makes not much sense to hop from one place to the next, so I'm not sure why > it's being used right now over a 301 or a 302. LD is somewhat being glued together by convention, so I'm as baffled as you - but if the convention is 303 and we wanna play, we'll have to do 303 also. > LD compliance requires more than using 303. You need to have separate URIs > for a thing, and resources about that thing. A tree would be a thing, with > one URI. The HTML page about it can't have the same URI, nor can the RDF > document about it. Right, the canonical thing URI would be the purl, and the different serializations describing it are identified by the phylows "?format=$foo" query string parameter. > Going from a canonical URI to the implementation URL sounds like a 302 to > me, not a 303. Really? I interpret the examples I've seen as 303, not 302. > Maybe I'm wrong here but that's why I think we need to think this through > first. I'll try to come up with some scenarios with visuals, I'll have to for the ievobio talk anyway. > On Jun 2, 2010, at 4:56 PM, Rutger Vos wrote: > >> On Wed, Jun 2, 2010 at 8:27 PM, Hilmar Lapp <hl...@ne...> wrote: >>> >>> I think we need to wrap this issue into discussing how to make PhyloWS >>> LD-compliant. Once we understand the full picture and have a diagram of >>> which URI we want to behave how we can implement it. >> >> Well, maybe - but this isn't about phylows per se, but about how we go >> from purl to treebase, as opposed to from phylows urls to the "ugly" >> urls (for this redirect, as implemented in the PhyloWSController, we >> have always used 303). In this sense, phylows is already linkeddata >> compliant, but the simple purls aren't (for that you need to use the >> "advanced" purls). >> >>> On Jun 2, 2010, at 12:38 PM, Rutger Vos wrote: >>> >>>> Hi, >>>> >>>> it seems our current purl configuration results in 302 redirects. >>>> Hilmar, maybe you can make these 303 redirects? Unless I am >>>> misunderstanding the admin interface I don't have the privilege to do >>>> so. >>>> >>>> Rutger >>>> >>>> -- >>>> Dr. Rutger A. Vos >>>> School of Biological Sciences >>>> Philip Lyle Building, Level 4 >>>> University of Reading >>>> Reading >>>> RG6 6BX >>>> United Kingdom >>>> Tel: +44 (0) 118 378 7535 >>>> http://www.nexml.org >>>> http://rutgervos.blogspot.com >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> _______________________________________________ >>>> Treebase-devel mailing list >>>> Tre...@li... >>>> https://lists.sourceforge.net/lists/listinfo/treebase-devel >>> >>> -- >>> =========================================================== >>> : Hilmar Lapp -:- Durham, NC -:- informatics.nescent.org : >>> =========================================================== >>> >>> >>> >>> >> >> >> >> -- >> Dr. Rutger A. Vos >> School of Biological Sciences >> Philip Lyle Building, Level 4 >> University of Reading >> Reading >> RG6 6BX >> United Kingdom >> Tel: +44 (0) 118 378 7535 >> http://www.nexml.org >> http://rutgervos.blogspot.com > > -- > =========================================================== > : Hilmar Lapp -:- Durham, NC -:- informatics.nescent.org : > =========================================================== > > > > -- Dr. Rutger A. Vos School of Biological Sciences Philip Lyle Building, Level 4 University of Reading Reading RG6 6BX United Kingdom Tel: +44 (0) 118 378 7535 http://www.nexml.org http://rutgervos.blogspot.com |