Re: 1.c-d: Define a Link Processor and Communicate With It? (repost)

At 11:50 AM 1/31/97, Tim Bray wrote:
>[Oops - cut & paste error, screwed this up first time around.]
Now I understand!
>1.c Should we define a link processor and specify any actions
> required of it?

As a separate document, or possibly as a part of the processing spec
("style sheet") language.

We should separate the descriptive and procedural aspects, but for linking,
people _expect_ and _require_ at least a minimal set of procedures -- and
unlike text formatting are much more naive about the possibilities.

>1.d Should we specify a way for a document to provide a summary of
> the linkage machinery it uses?

Already answered this.

I am not a number. I am an undefined character.
David Durand              dgd@cs.bu.edu  \  david@dynamicDiagrams.com
Boston University Computer Science        \  Sr. Analyst
http://www.cs.bu.edu/students/grads/dgd/   \  Dynamic Diagrams
--------------------------------------------\  http://dynamicDiagrams.com/
MAPA: mapping for the WWW                    \__________________________