]> namespace accessibility 1 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 2001-03-12 Class/Property definitions accessibility 1 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 2001-03-12 domain/range constraints 1 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 2001-03-12 undefined objects 1 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 2001-03-12 cardinality 1 The Validator should check any cardinality constraints on properties. This was originally posted at http://www.daml.org/projects/integration/homework/1/lessons.html 2001-03-12 disjointness 2 The Validator should check for obvious violations of daml:disjointWith or daml:disjointUnionOf, i.e. an object with 2 conflicting rdf:type statements. 2001-03-20 IDhash 2 ID="#foo", e.g. by checking for the occurance of 2 consecutive #'s in Resource identifiers. ]]> 2001-03-20 duplicate ID 2 ID="name". Since ID vs. about information is often lost, this may require use of a custom parser. ]]> 2001-03-20 property/Class striping 2 The Validator should flag any obvious violations of RDF property/Class striping. 2001-03-20 character offset 2 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. 2001-03-20 XML results 2 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. 2001-03-20 offline operation 4 It would be nice if the Validator could support offline operation (e.g. while on airplanes) by optionally cacheing at least the base ontologies for RDF, RDFS, and DAML+OIL. Cacheing of user ontologies would be a further feature. Alternatively, perhaps we could provide suggestions/instructions for using the Validator with a general-purpose HTTP proxy cache. 2001-04-12 indication IDs 3 It would be nice if indication in validator.dtd contained an id element/attribute so that people could refer to specific indications (e.g. "Hey Dave, I think i27 when validating http://... is bogus because ..."). If we use an attribute, it should probably be marked as an ID, but this precludes using just numbers. 2001-04-12 inconsistent cardinality 3 The Validator should produce some sort of InconsistentCardinality indication if both cardinality and either maxCardinality or minCardinality restrictions are specified for a given property. It could also produce this if minCardinality is greater than maxCardinality. 2001-07-12 UnambiguousProperty 3 The Validator should check UnambiguousProperty, i.e. that a given instance can be the value of the property for at most 1 instance. 2001-09-18 UnambiguousProperty is an ObjectProperty 3 The Validator should check that no values for UnambiguousProperty's are literals (unless this already gets checked by the fact that UnambiguousProperty is a subclass of ObjectProperty). 2001-09-18