- From: Bob DuCharme <bob@snee.com>
- Date: Sat, 09 Oct 2010 14:37:18 -0400
- To: "Laskey, Ken" <klaskey@mitre.org>
- CC: "semantic-web@w3.org" <semantic-web@w3.org>
Hi Ken, I know of no way to specify those constraints using the SKOS standard, and more importantly, no standardized way to check whether those constraints have been violated, unless you want to go to a different, related standard: SPARQL. ASK queries can stored the constraints and check whether they've been violated. In TopQuadrant's products we have ways to store the queries as part of the class metadata (after converting them to triples) but there's nothing proprietary about the principles behind the implementation. See See http://topquadrantblog.blogspot.com/2010/08/how-to-find-skos-constraint-violations.html for more. Bob DuCharme On 10/9/2010 1:09 PM, Laskey, Ken wrote: > I am looking to define a controlled vocabulary that contains a list of description elements. Values will be associated with the individual description elements, where some of values should be constrained by other controlled vocabularies. For example, my description set contains (length, weight, color) and color is to be constrained to (red, yellow, blue). > > I was looking to represent this in SKOS. My thoughts were: > > - The descriptive elements would each be SKOS Concepts > > - The set of description elements forming the controlled vocabulary would be a SKOS Concept Scheme > > - The controlled values would a SKOS Collection. > > What I am missing is how to say a given description element in one controlled vocabulary, e.g. a SKOS Concept Scheme, can be constrained to a list of values, e.g. a SKOS Collection. I was considering rdfs:range but I’m not sure that is applicable. > > I was surprised that the SKOS examples I found on the Web don’t mention this. Am I missing something fundamental? > > Ken > > --------------------------------------------------------------------------- > Dr. Kenneth Laskey > MITRE Corporation, M/S H305 phone: 703-983-7934 > 7515 Colshire Drive fax: 703-983-1379 > McLean VA 22102-7508 >
Received on Saturday, 9 October 2010 18:37:48 UTC