Ryan Lee wrote:
>> If the label lens is used together with FOAF knows then something like
>> this
>> could be rendered:
>>
>> Name: Chris Bizer
>> eMail: Chris_at_bizer.de
>> knows Ryan (ryanlee_at_w3.org)
>> Emmanuel (Emmanuel.Pietriga_at_lri.fr)
>
>
> I tend to agree with Emmanuel; absent any instruction from the Fresnel
> directives, those parentheses don't belong in the output. My question
> was about the meaning in a vacuum, and I think an intuitive answer is to
> simply string values of distinct properties together with spaces. If
> you want more, you can say more, as Chris demonstrates below.
Yes.
>>> Is each implementer going to be left to determine how to concatenate
>>> multiple property values on their own? Multiple values for one
>>> property?
>>>
>>> Though... does this look reasonable (abbreviated lens)?
>>>
>>> :foafPersonLabelLens fresnel:showProperties (
>>> foaf:name
>>> [ rdf:type fresnel:PropertyDescription ;
>>> fresnel:property foaf:mbox ;
>>> fresnel:valueFormat [
>>> fresnel:contentBefore "(" ;
>>> fresnel:contentAfter ")" ;
>>> ]
>>> ) .
>>>
>>> If it does, should we include it as an example somewhere?
>>
>>
>> I think we are still trying to somehow striclty seperate between
>> selection
>> (lens) and formating (format) and I would thus prefer.
>>
>> :foafPersonLabelLens fresnel:showProperties (
>> foaf:name
>> [ rdf:type fresnel:PropertyDescription ;
>> fresnel:property foaf:mbox ;
>> fresnel:use :mboxFormat .
>> ]
>> ) .
>>
>> :mboxFormat rdf:type fresnel:Format ;
>> fresnel:valueFormat [
>> fresnel:contentBefore "(" ;
>> fresnel:contentAfter ")" ] .
>>
>>
>> or even
>>
>> :foafPersonLabelLens fresnel:showProperties (
>> foaf:name
>> [ rdf:type fresnel:PropertyDescription ;
>> fresnel:property foaf:mbox .
>> ]
>> ) .
>>
>> :mboxFormat rdf:type fresnel:Format ;
>> fresnel: propertyFormatDomain foaf:mbox;
>> fresnel:valueFormat [
>> fresnel:contentBefore "(" ;
>> fresnel:contentAfter ")" ] .
>>
>> Without the hardcoded link between the two.
>>
>> I think we really shouldn't mix selection and formatting/styling!
>
>
> Right, good point. Can we include your example somewhere?
I'll try to add something in the manual on Monday.
>>> 3. Searching for sublenses
>>>
>>> Section 2.5 discusses using FSL to search Fresnel for a sublens. Aside
>>> from being outside of core, this feels like an odd capability since FSL
>>> is normally used to query the data being Fresnel'ed. This raises
>>> questions of consistency. Also, the introspection aspect of using FSL
>>> on Fresnel seems like it would force implementers to consider their
>>> Fresnel information as a navigable RDF model in addition to whatever
>>> else they do with it. They should anyways, but it's... weird.
>>
>>
>> This example is in the manual to show how Haystack functionality could be
>> emmulated. Therefor moving it should be discussed with David Karger.
>
>
> Getting David's time is not an easy task. I've spoken with him briefly
> and let him know the vocabulary will be re-released for his review,
> which he agreed would be better for him than trying to review our
> discussions on the list.
>
> Our decision on this matter should also be placed in the vocabulary,
> perhaps with blaring notices to him if we decide something other than
> what's currently there.
>
> Emmanuel and I are for leaving it aside for now. Completely aside from
> the functionality, I believe it's not core because it relies on FSL.
Right. Just because of this, it cannot be part of core. Or FSL becomes
part of core, and we don't want that. So I'll move this to extended.
BTW, my Jena-based FSL implementation is almost finished. Just a few
core XPath-like functions like startswith() or local-name() to add.
--
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 Sat Jul 02 2005 - 08:05:43 EDT