- From: Dan Brickley <danbri@w3.org>
- Date: Fri, 26 Oct 2001 09:49:00 -0400 (EDT)
- To: <w3c-rdfcore-wg@w3.org>
Not for discussion this telecon, but here's my proposal on rdfs:ConstraintResource and rdfs:ConstraintProperty: we drop them from the specification. Context (last week's meeting): http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2001Oct/0405.html [[ There is still some uncertainty about the constraint resources/properties issues, though many folks seem happy to lose these. ACTION: 2001-10-19#9, DanBri. Propose resolution of constraint resources for next week ACTION: 2001-10-19#10, DanBri. ditto for constraint properties ]] Context (Issue list): http://www.w3.org/2000/03/rdf-tracking/#rdfs-constraint-properties-resources My proposed closure: [[ The intent behind the rdfs:ConstraintResource mechanism was to allow some future proofing of RDF Schema to anticipate extensions to the Schema spec that addressed some of the facilities the original WG dropped from 1.0. The DAML+OIL specification is an example of such an extension to RDFS. As such, it shows up a flaw in the rdfs:ConstraintResource concept. The notion of a 'constraint resource' confuses two ideas: the idea that some parts of an RDF Schema may be used by automated data validation tools, and the idea that the meaning of certain RDF properties and classes impose constraints on their usage. This confusion makes it unclear as to which new properties-of-properties should be considered "Constraint Resources", for example a class "rdfsx:TransitiveProperty". Various meaningful annotations on RDF properties _could_ be considered to describe constraints on their uses? Does that make them constraint resources? The answer is unclear, because the notion of constraintresource is itself confused. Proposal: the current mechanism, rdfs:ConstraintResource and rdfs:ConstraintProperty, fails to serve its original purpose and should be removed from the RDF Schema 1.0 specification. The accompanying text be amended accordingly. ]]
Received on Friday, 26 October 2001 09:49:00 UTC