- From: Aaron Swartz <aswartz@swartzfam.com>
- Date: Thu, 18 Jan 2001 21:11:59 -0600
- To: Larry Masinter <masinter@adobe.com>, <uri@w3.org>, <Donald.Eastlake@motorola.com>
- CC: Donald Eastlake 3rd <dee3@torque.pothole.com>, Graham Klyne <GK@ninebynine.org>, Michael Mealling <michaelm@netsol.com>, Ted Hardie <hardie@equinix.com>
Larry Masinter <masinter@Adobe.COM> wrote: >> What's wrong with the current system of URI mapping: >> http://www.isi.edu/in-notes/iana/assignments/ > IANA makes no guarantees that its web site will not change substantially > in organization. > Our examination of the current IANA web site is that the organizations > of URIs is informal and not intended for automatic processing. > There is no guarantee that "www.isi.edu" will continue to be the authority > for IANA. So why not build a new web site that does not have these problems? Or why not have the RFC declare a specific HTTP-URI which is unchanging? At least then you'd have the possibility of browsing the URI-space and getting more information on the values with current browsers. > I'm not sure what requirement Don Eastlake was looking at; the problem that > got the rest of us going was the proposal that CCPP > (http://www.w3.org/Mobile/CCPP/) use URIs to identify media features and > similar elements. I'm writing a system that also uses URIs to identify media formats and etc. and we're planning to use the isi.edu addresses -- is there a serious problem that should cause us to rethink this? -- [ Aaron Swartz | me@aaronsw.com | http://www.aaronsw.com ]
Received on Thursday, 18 January 2001 22:12:19 UTC