- From: Mark Baker <distobj@acm.org>
- Date: Tue, 19 Mar 2002 20:58:28 -0500 (EST)
- To: david.orchard@bea.com (David Orchard)
- Cc: simonstl@simonstl.com ('Simon St.Laurent'), www-tag@w3.org
Dave, > I would be completely comfortable in considering XML messages flowing > between URI identified resources using BEEP/TCP/SMTP to be an evolutionary > step, part of the web, and maybe part of web services. As long as the core architectural principles are upheld, I'm all for it. But the only way BEEP could be used on the Web, would be if you defined a REST based application protocol on top. Ditto for TCP (but, er, we've already got one of those). SMTP is an application protocol with application semantics that are much more specific than HTTP/REST, so you'd have to tunnel on top - I'm not sure you'd find many mail adminstrators who'd appreciate that. If you don't want to obey these principles, you don't have to. But then you're no longer on the Web, you're on the Internet. At this point, perhaps it would help to ask for a definition of the Web from the TAG? Aaron previously asked about this; http://lists.w3.org/Archives/Public/www-tag/2001Dec/0015 MB -- Mark Baker, Chief Science Officer, Planetfred, Inc. Ottawa, Ontario, CANADA. mbaker@planetfred.com http://www.markbaker.ca http://www.planetfred.com
Received on Tuesday, 19 March 2002 20:53:43 UTC