Re: What does a document mean?

What is the context of this? It seems to perpetuate the fuzziness 
between 'document' and 'resource' (e.g., section 1 leads one to believe 
that it's possible to 'exchange' resources). A lot of the uses of XML, 
etc. are document-centric, but IMO the terminology and concepts should 
still mesh with the larger uses of these formats on the Web.

Also, it's unclear how deep this goes; for example, terms like 'message' 
are used, but I'm not sure they're being used in the sense that HTTP 
does. [1] may be help get a perspective from the other end (i.e., from 
the bytes on the wire up), to determine the scope of discussion.

This may just mean attaching a note that explains that 'documents' are 
considered on their own, separately from the issues brought about 
putting them on the Web and moving them around.

Sorry if I've missed other relevant discussion here, but it's been hard 
to keep up with this list recently.


On Thursday, March 28, 2002, at 08:28  AM, Norman Walsh wrote:

> Paul and I agreed to make this document public, and I did so on
> Monday, but forgot to announce it. Ooops. Here it is, moments before I
> vanish for two weeks vacation. Sorry about the timing.
>                                         Be seeing you,
>                                           norm
> --
> Norman.Walsh@Sun.COM   | If someone tells you he is going to make 'a
> XML Standards Engineer | realistic decision', you immediately
> XML Technology Center  | understand that he has resolved to do
> Sun Microsystems, Inc. | something bad.--Mary McCarthy
Mark Nottingham

Received on Saturday, 30 March 2002 14:03:49 UTC