Re: ISSUE-69: BroaderIrreflexive

Dear all,

Sorry, backtracking from my previous mail: at the time I wrote it, I had 
not anticipated it was planned to close ISSUE-44 without addressing all 
its initial content.
So this ISSUE-69 shall not be closed right now.

Antoine

>
> I would propose to close immediately this issue, since it is contained 
> in ISSUE-44, and treat it as a reminder that no resolution for 
> ISSUE-44 can close it if it does not address reflexivity.
>
> Antoine
>> ISSUE-69: BroaderIrreflexive
>>
>> http://www.w3.org/2006/07/SWD/track/issues/69
>>
>> Raised by: Alistair Miles
>> On product: SKOS
>>
>> This is a sub-issue of ISSUE-44.
>>
>> Currently, skos:broader is *not* defined as an irreflexive property.
>>
>> Therefore, graphs such as:
>>
>> <A> skos:broader <A> .
>>
>> ... are consistent with the SKOS data model.
>>
>> However, such a graph would never be found in a representation of a 
>> thesaurus or classification scheme, and if it did, would probably 
>> indicate some sort of error.
>>
>> If skos:broader were formally defined as an irreflexive property in 
>> the normative specification, this would endorse stronger checking of 
>> instance data against the SKOS data model, which would probably be 
>> both useful and appropriate to most SKOS use cases.
>>
>> Should skos:broader be normatively irreflexive?
>>
>>
>>
>>
>>   
>
>
>

Received on Wednesday, 23 January 2008 10:08:55 UTC