Chris Bizer wrote:
>>The conflict arises in where propertyFormat gets used. If we have just
>>that one predicate and we want it to do the analgous action of
>>resourceFormat+Group ('all properties rendered by the lens for matching
>>resources'), we can't right now. We'd need another predicate.
>>
>>in this case:
>>[ a fresnel:Format ;
>> fresnel:classFormatDomain "foaf:Person" ;
>> fresnel:propertyFormatDomain "foaf:knows" ;
>> fresnel:propertyFormat [ ... ] ] .
>>it isn't clear what propertyFormat should do.
>>
>
>
> I thought you would use either classFormatDomain or propertyFormatDomain,
> but you couldn't use both together. I don't know if we should allow this.
I had the same view as Chris.
> If we allow it, I think it would mean that propertyFormat only applies to
> foaf:knows on foaf:Persons but not to foaf:knows on ex:LivingThing.
>
> But to me this looks more like a use case for FSL.
Yes indeed. It would seem much more elegant to express that kind of
thing with an FSL path expression.
--
Emmanuel Pietriga
INRIA Futurs - Projet In Situ tel : +33 1 69 15 34 66
Bat 490, Université Paris-Sud fax : +33 1 69 15 65 86
91405 ORSAY Cedex FRANCE http://www.lri.fr/~pietriga
Received on Fri Jul 08 2005 - 14:28:35 EDT