The Linked Data Platform Paging specification, informally LDP-Paging, describes a HTTP-based protocol for clients and servers to be able to efficiently retrieve large Linked Data Platform Resource representations by splitting up the responses into separate URL-addressable page resources.. This document describes the approach and references to the conditions that LDP-Paging servers must satisfy in order to be conformant with the specification and presents a common format for describing LDP-Paging test results. These test cases both illustrate the features of the specification and can be used for testing conformance. [[LDP-PAGING]]


This document introduces a test suite that can be used to evaluate the conformance of LDP-Paging servers to the LDP-Paging specification [[LDP-PAGING]]. The test suite leverages the testing approach used for the Linked Data Platform specification [[LDP-TESTSUITE]].

The purpose of the test cases is to illustrate the specification features and to help in testing conformance. The provided set of test cases is "incomplete" in the sense that passing all the tests does not prove that a given system conforms to the LDP-Paging specification; failing a test does, however, prove that the system does not conform to the specification.

The presented format is intended to facilitate the use of tests by LDP-Paging server developers, e.g., in a test harness, as well as the extension of the test suite with new tests. Developers can check the LDP Primer [[LDP-PRIMER]] for concrete examples of inputs and expected outputs that can be used for testing.

Design principles

The design principles match that from the LDP test suite [[LDP-TESTSUITE]]. The goal is to automate as much as possible, though there will be cases when the automated tests may not be enough and some manual validation will be needed.

Testing process

Like the LDP Test Cases, the LDP-Paging Test Cases are defined in a location, within Java source code. [[LDP-PAGING-TESTCASES]] Details about each individual test case, such as information about whether it can be attempted by automated means or manual, will be found in the Java source code annotations. Also in the Java source code annotations the status of each test case, such as approved by the LDP Working Group, awaiting approval or not yet implemented.[[LDP-PAGING-TESTSUITE-COVERAGE]]

  1. The person or agent in charge of executing the test cases in a specific LDP-Paging server will take the test case definitions and run every test case on the LDP-Paging server. The execution of test cases must produce a test execution report for the LDP-Paging server, in RDF format, that contains for every test case: the specific inputs used during its execution, the produced outputs, and the assertion of whether the test case is passed. The test execution report must be supplied as defined in the document on implementation conformance reports. [[LDP-PAGING-CONFORM]]
  2. A report generator software will take all the LDP-Paging server execution reports and will generate an implementation report that includes the results of all the LDP-Paging servers. [[LDP-PAGING-CONFORM]]

Submitting results

Here is a summary of the steps needed for an assertor to submit the compliance results for an implementation.

Describing testing artifacts in RDF

See details in LDP Test Suite [[LDP-TESTSUITE]].

Change history