Chris Bizer wrote:
>
> Hi David,
>
> > chris, I would set it up a bit differently (in order to avoid hardwiring
> > defaults): write a labelLens that applies to everything and produces
> > (in preference order) value of rdfs:label of object, or dc:title of
> object,
> > or uri of object. Then make sure that lens has lowest priority/gets
> overridden
> > by any more specific lens for the object.
> Sure, no problem. We can use fresnel:alternateProperties to encode this
> behaviour. See:
> http://simile.mit.edu/repository/fresnel/trunk/docs/manual/FresnelVocabulary.htm#alternateandmerged
>
> Example:
>
> :smartDefaultLens rdf:type fresnel:Lens ;
> fresnel:domain foaf:Person ;
> fresnel:purpose fresnel:defaultLens ;
> fresnel:showProperties
> ( [ rdf:type fresnel:propertyDescription
> * fresnel:alternateProperties* ( foaf:name
>
> foaf:surname
>
> vcard:name
>
> ex:alsoAName
> rdfs:label
>
> dc:title ) ] ) .
>
> But I would rather like to hardwire some defaults, so that the usual
> stuff is also tried when we don't have such smart defaultLenses.
>
> This defaults could be realized by a labelLens using alternateProperties
> and having the domain rdfs:Class as you proposed or be hardwired into
> the browser. Both is possible.
I like David's suggestion of having a lens for this rather than
hardwiring it. It reminds me of XSLT's two default rules that get
overriden if you specify more specific ones, in the sense that you
encode default behaviour with the language (Fresnel in our case) rather
than by writing something abstract in the spec.
--
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 Thu Mar 24 2005 - 18:02:10 EST