Properties v classes in validation

I'm not sure that this is an actual issue, so I thought I'd ping the 
group before making it official...

Many of the validation requirements coming out of the cultural heritage 
community are conceived as requirements on "things" (defined as rdf:type 
classes) not on properties. As an example, a rule might be:

for every subject of type ex:CulturalObject
-- there can be one or more subjects in the same graph of type ex:Person

There are also rules regarding what rdf:type(s) are allowed in general 
in a graph. (This would be a closed shape.)

SHACL, however, has property validation rules, but no class validation 
rules. In some cases in CH data, there is a single property that 
connects the subjects, but for example in the case of cultural resources 
there are literally hundreds of different properties that can link a 
person to an object.

It's possible that we just need to adjust our thinking, but I'd like to 
hear if others have similar situations with their data.

Thanks,
kc
-- 
Karen Coyle
kcoyle@kcoyle.net http://kcoyle.net
m: 1-510-435-8234
skype: kcoylenet/+1-510-984-3600

Received on Monday, 31 August 2015 15:25:16 UTC