- From: McDonald, Ira <imcdonald@sharplabs.com>
- Date: Wed, 12 Nov 2003 13:01:06 -0800
- To: "'hardie@qualcomm.com'" <hardie@qualcomm.com>, uri@w3.org
Hi Ted, I like your idea as originally floated: - IANA assigns an 'orgname' (preferred source being an existing 'vnd.orgname' arc in the MIME registry). - First come, first served for 'orgname'. I do not like Larry Masinter's apparent suggestion (perhaps I'm misreading??) that we should break the existing rules in RFC 2717, which are that new top-level trees (non-IETF) MUST be unique and MUST be followed by a hyphen-dash before the remainder of the URI scheme name. Cheers, - Ira Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com -----Original Message----- From: hardie@qualcomm.com [mailto:hardie@qualcomm.com] Sent: Wednesday, November 12, 2003 2:04 PM To: uri@w3.org Subject: Re: non-IETF tree URI scheme draft > > The IANA would then construct and assign a URI scheme of the form: > > orgname-schemename. > >So 'info' would be 'niso-info'? 'doi' would be 'idf-doi'? > >Is the intention that if for example Mount Saint Mary's College came up with >an 'info' scheme it wanted registered, them there would be a 'clmsm-info' >scheme? > >--Ray That's the basic idea; niso-info: and idf-doi:. This would allow for the gnome folks (who are apparently already using info: as well, according to a previous note) to use gnome-info: without collision, but wouldn't require any more complex decoration. Obviously, you still have the "two NISOs" problem, but that seems to be something that can be managed without adding extra complexity to avoid it. regards, Ted Hardi
Received on Wednesday, 12 November 2003 16:01:26 UTC