request for verification: paging in TPF

Dear all,

We're all happy that paging is finally decided, but at the same time, this presents a breaking change for the Triple Pattern Fragments spec. Therefore, I'd kindly ask you to verify whether the TPF spec now implements paging correctly.

May I ask you the following?

1) Could you verify whether http://www.hydra-cg.com/spec/latest/triple-pattern-fragments/#paging correctly uses the latest Hydra Core Vocabulary?

2) Could you shine your light on http://www.hydra-cg.com/spec/latest/triple-pattern-fragments/#issue-3, which is about the predicate to be used between a page and a fragment?

3) I have updated our main server and client implementations as follows:
– Client: backwards-compatible (https://github.com/LinkedDataFragments/Client.js/commit/9b02a0)
– Server: breaking change (https://github.com/LinkedDataFragments/Server.js/commit/4f3377f0)
The server has not been deployed, but would give the following responses:
– https://gist.github.com/RubenVerborgh/78038d94d857f79976d5
Could you please verify whether these responses are in line with the Hydra Core Vocabulary spec?
Current issue: hydra:itemsPerPage is gone. How to mitigate this?

Thanks in advance for your input.
When I have collected all inputs, I will:

a) Adjust and finalize the TPF spec, in particular, update http://www.hydra-cg.com/spec/latest/triple-pattern-fragments/#controls to be more exact.

b) Notify all known implementers of clients and/or servers that there has been a breaking change, so that they can update their code.

c) Start working on an automated test suite that verifies whether a server implements the TPF spec correctly.

Thanks,

Ruben

Received on Thursday, 29 October 2015 09:51:00 UTC