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

Re: boundaries for the Web

From: Rob Lanphier <robla@real.com>
Date: Thu, 21 Mar 2002 19:15:30 -0800 (Pacific Standard Time)
To: "Simon St.Laurent" <simonstl@simonstl.com>
cc: "www-tag@w3.org" <www-tag@w3.org>
Message-ID: <Pine.WNT.4.43.0203211857270.-273717@goomoon.ietf53.cw.net>
On 21 Mar 2002, Simon St.Laurent wrote:
> So what is the Web?
> Conservatively, I'd suggest that:
> The Web is a hypertext-based system built around the Hypertext Transfer
> Protocol which uses a combination of marked-up information and software
> to convey information to people.
> I'm quite aware that definition is constraining, but I'd be happy to
> hear others which provide constraints.

I agree that we need scoping for these things:

*  What the W3C works on
*  What the TAG defines
*  What "Web architecture" needs to be compatible with (e.g. IETF
definition of "Internet architecture"

However, I don't think we necessarily need to get into too many food
fights over the term "Web architecture" itself.  So, I think Mark Baker's
proposed definition could be o.k., so long as later parts of the document
*are* properly scoped.

That said, I would suggest somehow working the following set of
constraints into the wording:

"Web architecture" generally consists of defining applications that
utilize one or more of the following architectures:
*  XML architecture
*  URI architecture
*  HTTP architecture

...as well as future extensions and replacements for those key components.

"Web architecture" relies heavily on "Internet architecture".  Key
components of Internet architecture which the W3C relies on include:
*  Media Type (MIME type) architecture
*  Protocol architecture

However, if these ideas aren't made clear in the intro, that's probably
ok, so long as discussion of these boundries occurs at some point.

Received on Thursday, 21 March 2002 22:17:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:55:50 UTC