W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > October to December 2007

mf:resultCardinality

From: Lee Feigenbaum <lee@thefigtrees.net>
Date: Mon, 19 Nov 2007 00:45:13 -0500
Message-ID: <474122E9.20104@thefigtrees.net>
To: 'RDF Data Access Working Group' <public-rdf-dawg@w3.org>

Andy suggested that adding a second rdf:type to indicate tests that have 
a relaxed cardinality requirement (because the queries use REDUCED) 
might be a burden on some implementors.

I've changed this to add a new manifest property and a value for it to 
indicate REDUCED tests with the appropriately changed test-evaluation 
semantics.

from test-manifest.n3 :


:resultCardinality rdf:type rdf:Property ;
     rdfs:comment "Specifies whether passing the test requires strict or 
lax cardinality adherence" ;
     rdfs:domain :ManifestEntry ;
     rdfs:range :ResultCardinality .

## ---- Test cardinality ----

:ResultCardinality rdf:type rdfs:Class ;
     rdfs:comment "Potential modes of evaluating a test's results with 
respect to solution cardinality" .

:LaxCardinality rdf:type :ResultCardinality ;
     rdfs:comment
"""The given mf:result for a test with an mf:resultCardinality of 
mf:ReducedCardinalityTest
is the results as if the REDUCED keyword were omitted. To pass such
a test, an implementation must produce a result set
with each solution in the expected results appearing at least once and
no more than the number of times it appears in the expected results. Of
course, there must also be no results produced that are not in the
expected results.""" .


Let me know if anyone objects to this. If no one does, I'll send out the 
updated test suite to implementors on Tuesday and solicit results for 
the REDUCED tests.

Lee
Received on Monday, 19 November 2007 05:45:30 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:37 GMT