Re: [oslc-core] Proposal to remove Link header option from Resource Preview spec

[Ian Green1 <ian.green@uk.ibm.com>]

Hi Sam
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. 

best wishes,
    -ian

ian.green@uk.ibm.com (Ian Green1/UK/IBM@IBMGB)
IBM Rational

<oslc-core@lists.oasis-open.org> wrote on 21/08/2014
20:07:43:

> From: Samuel Padgett <spadgett@us.ibm.com>
> To: "OASIS OSLC Core TC Discussion List"
<oslc-core@lists.oasis-open.org>
> Date: 21/08/2014 20:08
> Subject: [oslc-core] Proposal to remove Link
header option from 
> Resource Preview spec
> Sent by: <oslc-core@lists.oasis-open.org>
> 
> I suggest we remove the Compact Link header [1] in favor of an 
> oslc:compact property. We would also remove oslc:compacts (the 
> inverse). My reasoning:
> 1. We're already using 'compact' in the Prefer
response. 
> 2. We use property 'compact' for our JSON and
inverse property 
> 'compacts' elsewhere. This is inconsistent and confusing. 
> 3. Compact resources can be included in a query
response as 
> discussed during the call today (e.g., oslc.select=*,oslc.compact{*})
> 
> Then if you GET a resource (no Prefer header), it would have a triple
> 
> <> <oslc:compact> <compact-uri>
> 
> or optionally have the Compact representation inlined.
> 
> With the Prefer header, it would continue to look like Example 3 [2].
> 
> [1] http://tools.oasis-open.org/version-control/browse/wsvn/oslc-
> core/specs/resource-preview.html#linkHeader
> [2] http://tools.oasis-open.org/version-control/browse/wsvn/oslc-
> core/specs/resource-preview.html#preferenceAppliedJsonLDExample
> -- 
> Samuel Padgett | IBM Rational | spadgett@us.ibm.com
> 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