Re: ISSUE-81: Final names of property pair constraints?

As I recall it, the relevant SKOS constraint is that a pref label must be unique in a given language.

Thus, the appropriate constraint is the one on cardinality (max 1), but it needs to take into account language tag.

If one was to follow this line of thinking, in addition to regular cardinality constraints, there would need to be cardinality constraints within a language.

Or may be Karen is thinking about having a constraint that two different resources can't have the same pref label in the same language.

SKOS constraints are pretty specific. I think it would make sense for the SKOS community to define their own library of SKOS templates.

Other communities with well defined vocabularies and specific data quality needs, could be encouraged to do the same.

Sent from my iPhone

> On Sep 13, 2015, at 8:43 AM, Karen Coyle <> wrote:
> Holger, my basic reaction is that the term "Constraint" on all of them is awkward, and the constraints should just be:
> Equal, NotEqual, LessThan, LessThanOrEqual
> That's because the question is whether the values are equal, not whether the constraints are equal.
> However, I'm curious how the latter two will be implemented since they imply an order between the two values.
> It also seems that this mechanism assumes that there will always be two different predicates to compare, and I'm not sure that this is the case. For example, for the SKOS-related case, where you want to say that you cannot have two skos:prefLabels with the same value (including language code), a common instance example is:
>      <skos:prefLabel xml:lang="fr">sabliers</skos:prefLabel>
>      <skos:prefLabel xml:lang="en">sandglasses</skos:prefLabel>
>      <skos:prefLabel xml:lang="es">reloj de arena</skos:prefLabel>
>      <skos:prefLabel xml:lang="nl">zandlopers</skos:prefLabel>
> and more often having many more languages. How will this be handled?
> kc
>> On 9/10/15 6:35 AM, Holger Knublauch wrote:
>> Could a native speaker please let me know if any of the following names
>> sound "funny" and how they should be replaced, keeping in mind
>> consistency and compactness?
>> - EqualConstraint   (EqualTo? Equals?)
>> - NotEqualConstraint
>> - LessThanConstraint (LessConstraint?)
>> - LessThanOrEqualConstraint (LessThanOrEqualToConstraint?)
>> Example usage:
>> ex:MyShape
>>     a sh:Shape ;
>>     sh:constraint [
>>         a sh:EqualConstraint ;
>>         sh:predicate1 ex:property1 ;
>>         sh:predicate2 ex:property2 ;
>>     ]
>> .
>> Thanks
>> Holger
> -- 
> Karen Coyle
> m: 1-510-435-8234
> skype: kcoylenet/+1-510-984-3600

Received on Sunday, 13 September 2015 08:53:26 UTC