Abstract

This document report test subject conformance for and related specifications for RDF-star Test Suite according to the requirements of the Evaluation and Report Language (EARL) 1.0 Schema [EARL10-SCHEMA].

Status of This Document

This document is merely a W3C-internal document. It has no official standing of any kind and does not represent consensus of the W3C Membership.

This report describes the state of implementation conformance at the time of publication.

Table of Contents

• 1. Introduction
• 2. Instructions for submitting implementation reports
• 3. Test Manifests
  • 3.1 N-Triples-star Syntax Tests
  • 3.2 RDF-star Semantics tests
  • 3.3 SPARQL-star Evaluation Tests
  • 3.4 SPARQL-star Syntax Tests
  • 3.5 TriG-star Evaluation Tests
  • 3.6 TriG-star Syntax Tests
  • 3.7 Turtle-star Evaluation Tests
  • 3.8 Turtle-star Syntax Tests
• A. Test Subjects
  • A.1 Apache Jena
  • A.2 Oxigraph (Rust)
  • A.3 Oxigraph Rio Turtle (Rust)
  • A.4 RDF.ex (Elixir)
  • A.5 EYE (Prolog)
  • A.6 RDF::TriG (Ruby)
  • A.7 Ruby SPARQL (Ruby)
• B. Individual Test Results
• C. Report Generation Software

Introduction

This implementation report covers the implementations of the RDF-star specification which have submitted test results. It is intended to be maintained by the RDF-DEV Community Group. The implementation report serves two purposes:

1. To demonstrate that there are multiple, independent implementations of the specifications. This is a prerequisite for progression of any standard to Recommendation.

2. To catalog the known, conforming implementations and which features each supports.

Instructions for submitting implementation reports

Reports should be submitted in Turtle format to RDF-DEV CG or via a Pull Request to the w3c/rdf-star. Add or update a file in the /reports directory named so that it can be associated with your implementation. See instructions on using the GitHub web interface or submit a pull request from a forked repository using a branch other than "main".

Tests should be run using the test manifests defined in the Test Manifests Section.

The assumed base URI for the tests is <http://example/base/> if needed.

Include an earl:Assertion for each test, referencing the test resource from the associated manifest and the test subject being reported upon. See the example below:

  [ a earl:Assertion;
    earl:assertedBy <--your-developer-identifier-->;
    earl:subject <--your-software-identifier-->;
    earl:test <--uri-of-test-from-manifest>;
    earl:result [
      a earl:TestResult;
      earl:outcome earl:passed;
      dc:date "2016-12-26T10:18:04-08:00"^^xsd:dateTime];
    earl:mode earl:automatic ] .

The Test Subject should be defined as a doap:Project, including the name, homepage and developer(s) of the software (see DOAP). Optionally, including the project description and programming language. An example test subject description is the following:

  <> foaf:primaryTopic <--your-software-identifier--> ;
    dc:issued "2016-12-26T10:18:04-08:00"^^xsd:dateTime ;
    foaf:maker <--your-developer-identifier--> .

  <--your-software-identifier--> a doap:Project, earl:TestSubject, earl:Software ;
    doap:name          "My Cool RDF-star Parser" ;
    doap:release [
      doap:name     "--short name wih version number--";
      doap:revision "--Software version number--" ;
      doap:created  "2020-02-19"^^xsd:date;
    ] ;
    doap:developer     <--your-developer-identifier--> ;
    doap:homepage      <--your-software-homepace--> ;
    doap:description   "--your-project-description--"@en ;
    doap:programming-language "--your-implementation-language--" .

The software developer, either an organization or one or more individuals SHOULD be referenced from doap:developer using FOAF. For example:

  <--your-developer-identifier--> a foaf:Person, earl:Assertor;
    foaf:name "--My Name--";
    foaf:homepage <--my homepage--> .

3. Test Manifests