TRS spec examples of paged base response missing required Link header values

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: TRS
    • None

      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"

            Assignee:
            Unassigned
            Reporter:
            davidhoney
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: