This is intended to be a DAML community draft of a
"requirements/desiderata" document for the DAML validator.
|
Id |
Summary |
Priority |
Description |
Author |
Entered |
|
|
|
|
| It would be great if the Validator could produce its results as an XML file, which could then be sorted, filtered, and rendered as desired by the user. xsv does this. DAML itself could also be used, but would be slightly harder to use with XSLT. |
|
|
|
|
|
|
|
| The Validator should flag any obvious violations of RDF property/Class striping. |
| Not sure what "striping" is. Can you elaborate? |
|
|
|
|
|
|
|
| To the extent possible, the Validator should give the character offset (or range) within the indicated file where an error occurred. This may require use of a custom XML parser. |
| this is pretty much the same as item-2001-02-13T23:36 |
|
|
|
|
|
|
|
| The Validator should check for obvious violations of daml:disjointWith or daml:disjointUnionOf, i.e. an object with 2 conflicting rdf:type statements. |
|
|
|
|
|
|
|
| The Validator should check for multiple occurances of the same <code>ID="name"</code>. Since ID vs. about information is often lost, this may require use of a custom parser. |
| The Validator should check for occurances of <code>ID="#foo"</code>, e.g. by checking for the occurance of 2 consecutive #'s in Resource identifiers. |
|
|
|
|
|
|
|
| The Validator should check any cardinality constraints on properties. This was originally posted at http://www.daml.org/projects/integration/homework/1/lessons.html |
|
|
|
|
|
|
|
| The Validator should check that all namespaces referenced are accessible. Inaccessibility should be a warning by default, since it may be due to a network outage and some namespaces (such as Dublin Core) don't resolve to RDF content. This was originally posted at http://www.daml.org/projects/integration/homework/1/lessons.html |
|
|
|
|
|
|
|
| The Validator should check any domain/range constraints specified for properties. This was originally posted at http://www.daml.org/projects/integration/homework/1/lessons.html |
|
|
|
|
|
| Class/Property definitions accessibility |
|
|
| The Validator should check that all Classes and Properties used are defined. This was originally posted at http://www.daml.org/projects/integration/homework/1/lessons.html |
|
|
|
|
|
|
|
| The Validator should identify any resources used as objects that are not also used as subjects. This was originally posted at http://www.daml.org/projects/integration/homework/1/lessons.html |
|
|
|
|
|
| selective invocation by Class name |
|
|
| it should be able to take the name of a Class (or list of names) for which to validate the instances for (rather than validating *everything* in e.g. a large crawled database!) |
|
|
|
|
|
|
|
| it would be nice if the validator itself could produce its "errors and warnings" report in DAML |
|
|
|
|
|
| selective invocation by file |
|
|
| the name of a file (containing DAML ontology definitions) from which to take the Class names for which the validation will occur |
|
|
|
|
|
|
|
| based on RDFAPI (as in "working well in conjunction with" because virtually all DAML contractors use it already -- possibly by being based on the tripelized output of it - also this way you can validate against a triple database) |
|
|
|
