Hi Sam,
Are you requiring that all resources
for which I might want to supply a preview will be LDPRs? - that is, will
deal with the type="describedby". (I know I ought to know
the answer to that but I've lost track!)
If so, then your suggestion seems better
to me.
best wishes,
-ian
(Ian Green1/UK/IBM@IBMGB)
IBM Rational
Samuel Padgett <> wrote on
22/08/2014 15:06:49:
> From: Samuel Padgett <>
> To: Ian Green1/UK/IBM@IBMGB
> Cc: "OASIS OSLC Core TC Discussion List"
<>
> Date: 22/08/2014 15:07
> Subject: Re: [oslc-core] Proposal to remove Link
header option from
> Resource Preview spec
>
> Ian Green1 <> wrote on 08/22/2014 09:04:51
AM:
>
> > Isn't there a requirement that I can discover the preview of
a non-
> > RDF resource, for example, a binary? Link header serves
this purpose.
>
> Ian, this is a really good point and probably the easiest way to
> implement it.
>
> Another approach is to use an associated RDF source from LDP [1].
>
> Request:
>
> HEAD /attachments/foo.gif
> Host: example.com
>
> Response:
>
> 200 OK
> Link: <http://example.com/attachments/foo.rdf>;
rel="describedby"
> [other headers]
>
> then
>
> Request:
>
> GET /attachments/foo.rdf
> Host: example.com
> Accept: application/json
> Prefer: return=representation; include="http://open-
> services.net/ns/core#PreferCompact"
>
> to get the Compact resource.
>
> The benefit of the second approach is that we don't have define a
new
> Link relation. It's the same amount of HTTP requests.
>
> We're working on an OSLC Change Management attachments spec now, so
it's
> timely feedback.
>
> [1] http://www.w3.org/TR/ldp/#ldpc-post-createbinlinkmetahdr
> --
> Samuel Padgett | IBM Rational |
> Eclipse Lyo: Enabling tool integration with OSLC
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
