# Re: options, not nesting?

Michael Mealling (ccoprmm@oit.gatech.edu)
Fri, 29 Oct 93 10:49:52 EDT

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Dirk Herr-Hoyman: "Re: Single protocol for UR*?"
- Previous message: Michael Mealling: "Re: options, not nesting?"

    From: ccoprmm@oit.gatech.edu (Michael Mealling)

    Message-Id: <199310291449.AA14864@oit.oit.gatech.edu>

    Subject: Re: options, not nesting?

    To: terry@ora.com (Terry Allen)

    Date: Fri, 29 Oct 93 10:49:52 EDT

    In-Reply-To: <199310282259.AA24745@rock.west.ora.com>; from "Terry Allen" at Oct 28, 93 3:59 pm

Terry Allen said this:
> If the contents of your template are of the form
> URI: URN
> URI: URL
> URI: URL
> URI: URL
> what is the point of URI? I'm sure you have one, but I missed it.

None if you have URL: in front of a URL. If you don't you end up with

URN:IANA:blabla
http://bla.com/bla/bla

Then your parser has to know about EVERY possible URL protocol scheme. Plus
it needs to be updated whenever you add a new scheme. If you just
have URN: and URL: exist within a Template you end up with:

URN:URN:IANA:bla
URL:http://bla.com/bla

That's acceptable but it makes URNs just look funny. I would prefer this:

URN:IANA:bla
URL:http://bla.com/bla

but I can live with the URN:URN: version...

-MM

    --
    ------------------------------------------------------------------------------
    Michael Mealling                     ! Hypermedia WWW, WAIS, and gopher will be
    Georgia Institute of Technology      ! here soon via MIME. Your view of the
    Michael.Mealling@oit.gatech.edu      ! internet is about to change completely!

- Next message: Dirk Herr-Hoyman: "Re: Single protocol for UR*?"
- Previous message: Michael Mealling: "Re: options, not nesting?"