Ryan Lee wrote:
> Emmanuel Pietriga wrote:
>
>> I think that for this specific point we should discuss requirements.
>> What I'd like to have:
>>
>> - be able to associate CSS instructions with specific graphical
>> regions/entities of the displayed document. By regions and entities, I
>> mean things like "the object that represents the resource", "the
>> object that represents the property name", "the object that represents
>> the property value".
>
>
> Agreed, though by 'associate' I don't mean including CSS fragments in
> Fresnel but allowing custom hooks to identify those regions for later
> CSS selection.
Yes.
>> - be able to apply styling instructions based on conditions at the
>> source RDF model level, i.e. be able to say things like "color in red
>> all ex:age properties that have a value > to 47".
>
>
> This is not a core requirement, is it? I agree that being able to
> distinguish part of the RDF model for later styling is important, but
> complex conditions implies that it's outside of core's capabilities.
No, this is not part of core. But I think it would be really useful. And
I guess it has consequences on the overall design.
>> I also would like to have a well-defined intermediate tree format.
>> Ryan, I haven't had time to look at the code you wrote. Did you
>> already make a choice w.r.t that issue?
>
>
> This is what it looks like right now, based solely on the selection phase:
>
> <results>
> <resource label="Eric Miller">
> <property label="name" uri="http://xmlns.com/foaf/0.1/name">
> <value label="Eric Miller"/>
> </property>
> </resource>
> <resource label="Ryan Lee">
> <property label="name" uri="http://xmlns.com/foaf/0.1/name">
> <value label="Ryan Lee"/>
> </property>
> <property label="Surname" uri="http://xmlns.com/foaf/0.1/surname">
> <value label="Lee"/>
> </property>
> <property label="depiction" uri="http://xmlns.com/foaf/0.1/depiction">
> <value
> label="http://ryanlee.org/photodb/image-display?photo_id=119&size=sm"
> uri="http://ryanlee.org/photodb/image-display?photo_id=119&size=sm"/>
> </property>
> </resource>
> ...
> </results>
A few comments:
- wouldn't the value's text (which I guess label represents) be better
put in a #PCDATA node? I'm thinking about multiline values, and more
generally about long values. This only applies to value, not property.
- do we want a namespace for results/resource/property/...?
- Isn't there some kind of XML serialization of RDF that looks a lot
like this? If so, should we consider using (and extending) it?
A question:
- in your view, how does the non-presentational part of styles fit into
this?
--
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 May 26 2005 - 06:21:27 EDT