[OASIS Issue Tracker] (OSLCCORE-160) TRS spec examples of paged base response missing required Link header values

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/OSLCCORE-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Honey updated OSLCCORE-160:
---------------------------------

    Description: 
The original spec athttp://open-services.net/wiki/core/TrackedResourceSet-2.0/#Paged-Base shows a response for a paged base as including the following Link header value:
Link: <http://cm1.example.com/baseResources/page1>; rel="first", 
      <http://cm1.example.com/baseResources/page2>; rel="next",
      <http://www.w3.org/ns/ldp#Page>; rel="type"

However, an LDPC response is also supposed to include values for rel="type" for both ldp:Resource and the RDF type of the LDPC itself. See example 13 in https://www.w3.org/2012/ldp/hg/ldp-paging.html#ldpc-informative.

For the example, I think the LInk header in the response should be:
Link: <http://cm1.example.com/baseResources/page1>; rel="first", 
      <http://cm1.example.com/baseResources/page2>; rel="next",
      <http://www.w3.org/ns/ldp#Page>; rel="type",
      <http://www.w3.org/ns/ldp#Resource>; rel="type",
      <http://www.w3.org/ns/ldp#DirectContainer>; rel="type"

  was:
The original spec athttp://open-services.net/wiki/core/TrackedResourceSet-2.0/#Paged-Base shows a response for a paged base as including the following Link header value:
Link: <http://cm1.example.com/baseResources/page1>; rel="first", 
      <http://cm1.example.com/baseResources/page2>; rel="next",
      <http://www.w3.org/ns/ldp#Page>; rel="type"

However, an LDPC response is also supposed to include values for rel="type" for both ldp:Resource and the RDF type of the LDPC itself. For the example, I think the LInk header in the response should be:
Link: <http://cm1.example.com/baseResources/page1>; rel="first", 
      <http://cm1.example.com/baseResources/page2>; rel="next",
      <http://www.w3.org/ns/ldp#Page>; rel="type",
      <http://www.w3.org/ns/ldp#Resource>; rel="type",
      <http://www.w3.org/ns/ldp#DirectContainer>; rel="type"


> TRS spec examples of paged base response missing required Link header values
> ----------------------------------------------------------------------------
>
>                 Key: OSLCCORE-160
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-160
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>          Components: TRS
>            Reporter: David Honey
>
> The original spec athttp://open-services.net/wiki/core/TrackedResourceSet-2.0/#Paged-Base shows a response for a paged base as including the following Link header value:
> Link: <http://cm1.example.com/baseResources/page1>; rel="first", 
>       <http://cm1.example.com/baseResources/page2>; rel="next",
>       <http://www.w3.org/ns/ldp#Page>; rel="type"
> However, an LDPC response is also supposed to include values for rel="type" for both ldp:Resource and the RDF type of the LDPC itself. See example 13 in https://www.w3.org/2012/ldp/hg/ldp-paging.html#ldpc-informative.
> For the example, I think the LInk header in the response should be:
> Link: <http://cm1.example.com/baseResources/page1>; rel="first", 
>       <http://cm1.example.com/baseResources/page2>; rel="next",
>       <http://www.w3.org/ns/ldp#Page>; rel="type",
>       <http://www.w3.org/ns/ldp#Resource>; rel="type",
>       <http://www.w3.org/ns/ldp#DirectContainer>; rel="type"



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)