> However, I am not sure that the physical storage model has to be the
> same as the node model. There could be an assumption that the server
> will do something to break apart node sets and deliver them one
> at a time.
Right now the # suffix is used for links to parts of documents, and
browsers adjust the display position to show the referenced location.
Servers could choose to return just the referenced part e.g. when
the requested ID identifies a DIVn element rather than say a paragraph.
This would offer a relatively clean approach to keeping nodes in a
single file. It requires that current browsers are adapted to search
for ID attributes rather than just the NAME attribute on the <A> element.
>> I have recently added the SRC attribute to LINK in a bid to allow authors
>> to use images for links which are intended appear in a document specific
>> toolbar.
> I would like to see this src attribute (and shape?) available as a
> "button" (I believe that hytime calls/used to call this an endterm)
> to allow a graphics to be consistently associated with a link.
> This assumes that the "A" element will be extended to include an IDREF to
> a link element; I believe has been recommended before to help with
> link maintenance.
Currently documents use HREF and SRC attributes to specify documents
and inline images respectively as URLs. Alternative attributes are needed
if we wish to support HyTime CLINKs - this needs to be discussed at
the WWW Conference in May.
> BTW...the version of the HTML+ dtd available via the web
> (tp://15.254.100.100/pub/htmlplus.dtd.txt) does not have the src
> attribute.
I have updated this and added parameter entities to specify the set
of relationship types. The set needs further discussion as little use
has yet been made of these.
Dave Raggett