W3C home > Mailing lists > Public > www-tag@w3.org > September 2002

Re: suggested replacement text "circle or spline"

From: Graham Klyne <GK@ninebynine.org>
Date: Wed, 11 Sep 2002 11:57:00 +0100
Message-Id: <5.1.0.14.2.20020911114937.03b7ea20@127.0.0.1>
To: Chris Lilley <chris@w3.org>
Cc: www-tag@w3.org

At 10:13 PM 8/30/02 +0200, Chris Lilley wrote:
>   <replacement>
>
>   For instance, if the representation is an HTML 4 document, the
>   fragment identifies an element by its ID. [HTML4frag] The usual
>   effect on a visual presentation of traversing a URI reference
>   containing such a fragment identifier is to scroll the canvas so
>   that the rendering of the identified element comes into view, being
>   placed at the top of the window if possible.
>
>   If the representation is a WebCGM metafile, the fragment identifier
>   identifies an object in the content by the picture identifier and,
>   within that picture, by the name or object id of that object. It may
>   also pass additional information, such as frame selection, or a
>   command to highlight. [WebCGMfrag] The defined effect on a visual
>   presentation of traversing a URI reference containing such a
>   fragment identifier is to display the selected picture and to pan
>   and possibly zoom the canvas at the so that the rendering of the
>   identified element is completely contained in the current viewport.
>   The rendering of one or more selected objects may also be highlighted.
>
>   If the representation is an SVG graphic, the fragment identifier
>   either identifies an element in the content by its ID, or identifies
>   the whole document and passes a view specification. [SVGfrag] The
>   defined effect on a visual presentation of traversing a URI
>   reference containing such a fragment identifier is to pan and
>   possibly zoom the canvas at the so that, if an element is
>   identified, the rendering of the identified element is completely
>   contained in the current viewport; if a view specification is given,
>   the specified view is contained in the viewport.
>
>   In the Resource Description Framework [RDF10frag], fragments do not
>   identify parts of the content but instead can be used to identify
>   the definition of anything, be it abstract (e.g., a dream) or
>   concrete (e.g., an automobile).
>
>   </replacement>

Interesting.

I think this approach is entirely consistent with what we have been trying 
to do for RDF.  One might go on to talk about visualization of RDF 
definitions, e.g. as a graph (as is commonly offered), in which the visual 
affect of traversal might be similar to that for WebCGM or SVG.  (I'm not 
suggesting you should say that, just pointing out that it seems consistent.)

There's an attempt to describe fragments in RDF at:
   http://www.w3.org/TR/2002/WD-rdf-concepts-20020829/#xtocid103660

#g


-------------------
Graham Klyne
<GK@NineByNine.org>
Received on Wednesday, 11 September 2002 07:44:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:11 GMT