TAG TODO: Unresolved issues in Web Architeture

Here are a few issues in Web Architecture which I would like to see the TAG

 - Why does the Web use mime types and not URIs?

 - What's the proper terminology for distinguishing between the HTTP/HTML
Web, things with URIs, the services Web, etc.? Alternately, what is the Web?

 - Do Web Architecture principles continue to make sense in a world with
decentralized systems like Freenet and Mojo Nation?

One example is the "security by obscurity" issue for URIs[1]. On the HTTP
Web, where passwords can be changed and there is an official "host" for any
document, this makes sense. But what about a system like Mojo Nation, where
the only way to protect document secrecy is by guarding the document's URI
(MojoID), since that allows you to reconstruct the document.

[1] http://www.w3.org/DesignIssues/LinkMyths

Of course, there are the "completed" issues of Web Architecture, which only
need to be formalized and written down. I'd love to see the TAG take on this
job also, as a formal W3C Note or Recommendation would be helpful for
explaining these issues to others.

Best of luck,
[ "Aaron Swartz" ; <mailto:me@aaronsw.com> ; <http://www.aaronsw.com/> ]

Received on Monday, 17 December 2001 13:31:39 UTC