TEST: last call candidate (?)

not quite really - two things to do
  - move Nothing to Lite, corresponding impact on test classification
  -  add a "changes as a result of last call" section, including the Nothing 
to Lite movement.

However, this should now be reviewable.

There is a detailed change log:
http://lists.w3.org/Archives/Public/www-archive/2003May/att-0008/L#changes
(excluded from the last call candidate)

The text is largely unchanged except for the datatypes treatment. Additional 
datatype related text is included in this message.

Of the test changes, I believe the most important to review are the ones to 
the approved tests, other than the syntactic changes.

These are highlighted in:
http://lists.w3.org/Archives/Public/www-archive/2003May/att-0008/L#changes-to-approved

Could I ask Jeff to review the imports tests:
http://www.w3.org/2002/03owlt/editors-draft/draft/byFunction#function-imports

On datatypes the new text is found in:
 first part of section 3; 
last paragraph of section 6 
and changed SHOULD to MUST for xsd:integer and xsd:string in section 4.2.2. 
Also see test examples, for example in C.2.6 Datatypes 

i.e section 3:
[[
Some of the tests require certain datatypes to be supported in the datatype 
theory [OWL Semantics and Abstract Syntax]. These are indicated with the 
test. Other datatypes, which are used in the test, but which are not required 
to be supported in the datatype theory are also indicated. The datatypes 
xsd:integer, xsd:string from [XML Schema Datatypes] are not indicated, even 
when used or required. 
]]

4.2.2
[[
The datatype theory of an OWL consistency checker MUST minimally support at 
least xsd:integer, xsd:string from [XML Schema Datatypes]. 
]]

section 6
[[
The datatypes used in the test are given with the otest:usedDatatype property 
or with its subproperty otest:supportedDatatype, which furthermore, indicates 
that the test is only valid when the datatype is supported by the datatype 
theory being used. 
]]


Example tests:

===
DL
Positive Entailment Test:
004

Description: (informative) <I5.8/Manifest004#test> 

There are precisely 128 different values of xsd:byte that are also 
xsd:unsignedInt.

Required datatype support:
 xsd:byte, xsd:unsignedInt, 
===
_:a rdf:type owl:Restriction .
first:p rdf:type owl:DatatypeProperty .
first:p rdfs:range xsd:byte .
first:p rdfs:range xsd:unsignedInt .
_:a owl:onProperty first:p .
_:a owl:cardinality "128"^^xsd:nonNegativeInteger  .
first:john rdf:type _:a .
===
first:john rdf:type owl:Thing .
first:john first:p "5"^^xsd:byte  .
first:p rdf:type owl:DatatypeProperty .
===

and

===
DL
Negative Entailment Test:
005

Description: (informative) <I5.8/Manifest005#test> 

There are 128 different values of xsd:byte that are also xsd:unsignedInt.

Other datatypes:
 xsd:byte, xsd:unsignedInt, 

N3 format is informative.

DL
Premises: <I5.8/premises005> 
===
_:a rdf:type owl:Restriction .
first:p rdf:type owl:DatatypeProperty .
first:p rdfs:range xsd:byte .
first:p rdfs:range xsd:unsignedInt .
_:a owl:onProperty first:p .
_:a owl:cardinality "127"^^xsd:nonNegativeInteger  .
first:john rdf:type _:a .
==
first:john rdf:type owl:Thing .
first:john first:p "5"^^xsd:byte  .
first:p rdf:type owl:DatatypeProperty .
===

NOTE: the first (004) is only true with knowledge of the datatypes. In 
contrast the non-entailment 005 holds with ot without such knowledge.

Received on Wednesday, 7 May 2003 16:04:26 UTC