Re: [ALL] review of n-ary relations

> About URLs use, in the "Pattern 2" example (purchase) it would be good 
> to avoid using of
> the same fragment identifier for properties and classes with a simple 
> case/Case
> difference, like "#purpose" vs "#Purpose", and "#object" vs "#Object".
> This does not help much to have people clarify the difference between 
> property and class,
> let alone that casual readers (both human and machines) are not always 
> case-sensitive. I
> know this is an usual practice in (lazy?) modeling, but I think we 
> should not implicitly
> approve it as a good practice.
>
> I suggest to use instead the usual "#hasObject" , "#hasPurpose" for 
> the properties, and
> "#isObject" , "#isPurpose" for the inverse ones.
>

hmmm... I am wondering what's the consensus on this. Is it really so 
bad to use different cases? I am pretty sure machines are 
case-sensitive (they better be!). And I am not sure it is that much of 
a problem for humans either, since they look at things in context. I 
don't know -- what do others think?

Natasha