> >
> > Here's another stray thought. It seems that our rendering is attempting
> > to "unroll" an rdf model, which can be an arbitrary graph, into a tree.
> > It is not necessarily the case that the entire tree needs to be
displayed
> > all at once. As is the case with ajax, you could imagine sending a
quite
> > extensive tree of information back to the client, but then leaving it up
> > to the client (under the user's control) to make decisions about which
> > parts of the tree to "expand"/display at a given moment. This would
seem
> > to hold out the possibility of supporting various types of semantic zoom
> > at the client, without need for going back to the server each time you
> > want more details.
Not a stray thought. Giving the user this kind of control is exactly what we
are trying to achieve.
If the tree gets send at once or better in parts is more an implementation
detail, where one would just go for the more performant alternative.
Chris
> >
> >
> > Mailing-List: contact general-help_at_simile.mit.edu; run by ezmlm
> > X-No-Archive: yes
> > Reply-To: <general_at_simile.mit.edu>
> > X-Authenticated: #1074481
> > From: "Chris Bizer" <bizer_at_gmx.de>
> > Date: Mon, 21 Mar 2005 11:10:17 -0500
> > X-Y-GMX-Trusted: 0
> > X-Spam-Level:
> > X-Spam-Status: No, hits=-4.8 required=5.0
tests=AWL,BAYES_00,HTML_MESSAGE
> > autolearn=ham version=2.63
> > X-LocalTest: Local Origin
> >
> > This is a multi-part message in MIME format.
> >
> > ------=_NextPart_000_00A6_01C52E06.900DEB80
> > Content-Type: text/plain;
> > charset="iso-8859-1"
> > Content-Transfer-Encoding: quoted-printable
> >
> > Hi,
> >
> > I'm starting to like Stefano's idea of getting rid of the style =
> > vocabulary.
> > Let's make my conversion process public and answer the questions I =
> > raised yesterday :-)
> >
> > We could have lenses that do selection and some basic styling:
> >
> > :personsKnowsLens rdf:type fresnel:Lens ;
> > rdfs:label "Displays persons together with people they =
> > know."_at_en^^dtype:string ;
> > fresnel:lensDomain foaf:Person ;=20
> > fresnel:showProperties ( foaf:name=20
> > [ fresnel:property foaf:depiction ;
> > fresnel:label fresnel:none ;
> > fresnel:value fresnel:image ]
> > [ fresnel:property foaf:homepage ;
> > fresnel:label "Homepages of the guy: ";
> > fresnel:value fresnel:uri ]
> > [ rdf:type fresnel:PropertyDetails ;=20
> > fresnel:property foaf:knows ;
> > fresnel:label "He knows the following =
> > people: ";
> > fresnel:sortValues fresnel:asc ;
> > fresnel:sublens :FOAFPersonDefaultLens ] ) =
> > .
> >
> >
> > This lens could produce an XML tree like this:
> >
> > <fresnel:container>
> > <foaf:person uri=3Dex:stefano>
> > <fresnel:property>
> > <foaf:name>
> > <fresnel:label>Name: </fresnel:label>
> > <fresnel:value>Stefano</fresnel:value>
> > </foaf:name>
> > <foaf:depict>
> > <fresnel:value>
> > =
> > <fresnel:image>http://idontknow.org/image.gif</fresnel:image>
> > <fresnel:value>
> > </foaf:depict>
> > <foaf:homepage>
> > <fresnel:label>Homepages of the guy: </fresnel:label>
> > =
> >
<fresnel:value><fresnel:uri>
http://idontknow.org</fresnel:uri></fresnel:v=
> > alue>
> > =
> >
<fresnel:value><fresnel:uri>
http://idontknow.org</fresnel:uri></fresnel:v=
> > alue>
> > <foaf:homepage>
> > <fresnel:property>
> > </foaf:person>
> > </fresnel:container>
> > =20
> > Which could be styled using CSS and relying heavyly on child element
=
> > selectors:
> >
> > fresnel:container {background-color: white}=20
> > foaf:person {border-top-style: solid }
> > foaf:person > fresnel:property > foaf:depict > fresnel:value > =
> > fresnel:image {border: thick silver solid }
> > foaf:homepage > fresnel:label {font-weight: bold }
> > foaf:homepage > fresnel:value:after {content: "," }
> >
> > When the tree is finally rendered to different output formats like
HTML =
> > or SVG, the renderer would have to replace <fresnel:image> or =
> > <fresnel:uri> with the appropriate tags from the output language.
e.g. =
> > <img>. He might also want to adjust the CSS selectors abouve to the
CSS =
> > class names, which he uses in the output.
> >
> > Stefano: Is the above the direction into which you were thinking?
> > If not please correct me. Looks like we are inventing some nice use =
> > cases for Cocoon ;-)
> >
> > Advantages:
> > - Less terms in Fresnel.
> > - Better integration into the XML would (XSLT,Cocoon)
> > - Reuse of CSS selectors and classic CSS stylesheets.
> >
> > Disadvantages
> > - Less expressive.
> > - blurres the distinction between selection and styling (by having
label =
> > and image in the lens)
> >
> > Comments?
> >
> > Chris
>
> --
> Stefano Mazzocchi
> Research Scientist Digital Libraries Research Group
> Massachusetts Institute of Technology location: E25-131C
> 77 Massachusetts Ave telephone: +1 (617) 253-1096
> Cambridge, MA 02139-4307 email: stefanom at mit . edu
> -------------------------------------------------------------------
>
Received on Mon Mar 21 2005 - 19:01:58 EST
