- From: Svensson, Lars <L.Svensson@dnb.de>
- Date: Fri, 8 May 2015 09:25:17 +0000
- To: Mark Baker <distobj@acm.org>
- Cc: Martynas Jusevičius <martynas@graphity.org>, "public-lod@w3.org" <public-lod@w3.org>
Mark, On Thursday, May 07, 2015 7:36 PM, Mark Baker wrote: > On Thu, May 7, 2015 at 9:13 AM, Svensson, Lars <L.Svensson@dnb.de> wrote: > > Mark, > > > >> On Thu, May 7, 2015 at 7:05 AM, Martynas Jusevičius > >> <martynas@graphity.org> wrote: > >> > On the other hand, it seems like you want different descriptions of a > >> > resource -- so it seems to me that these should in fact be different > >> > resources? That could be split into > >> > http://example.org/some/resource/dcat and > >> > http://example.org/some/resource/premis, for example. > >> > >> ^ This. > > > > Can you please elaborate a bit on this? I'm not quite sure I get your point. > > Only that IME, having separate URIs is almost always the best option > because it allows problems to be solved within the linked data model > itself. But then how do I show that all descriptions describe the same entity? What I want to describe is http://example.org/some/resource. How do I tell a client that there are different descriptions of that entity available (schema.org, org ontology, foaf) and that each of those descriptions are available as xhtml+RDFa, RDF/XML and Turtle? > To your mobile-optimized page example, I'd add that from a REST POV, > that is a separate resource because representations are consistently > different (aka they have different membership functions). OK, so that means that when I return representations for a generic resource, all representations need to have the same scope (or the same membership function, assuming that we talk about the same thing... [1]). I can understand that it in a way makes things easier. OTOH at least some sites look at the User-Agent header and redirect to a mobile-optimised if they assume that it is the best format for the client (one example being http://www.spiegel.de/ that redirects to http://m.spiegel.de/ when accessed from a mobile phone). Isn't that also a kind of conneg, or should we speak of profile negotiation or format negotiation? [1] https://en.wikipedia.org/wiki/Membership_function_%28mathematics%29 Apologies to all if I seem enervating, I'm just trying to understand how all of this works (or is supposed to work...). Best, Lars
Received on Friday, 8 May 2015 09:25:46 UTC