# Re: Minor clarification on url: prefix (fwd)

Michael Mealling (ccoprmm@oit.gatech.edu)
Fri, 3 Dec 93 17:09:51 EST

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: David Robison: "Re: URN functionality from URLs"
- Previous message: Michael Mealling: "Re: Minor clarification on url: prefix (fwd)"

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

    Message-Id: <199312032209.AA01682@oit.gatech.edu>

    Subject: Re: Minor clarification on url: prefix (fwd)

    To: uri@bunyip.com

    Date: Fri, 3 Dec 93 17:09:51 EST

> Larry Masinter said this:
> Yes, but what was promoted at the meeting as 'consensus' was that URL:
> was part of the URL and not part of the wrapper around it.

> I don't see anything wrong with standardizing <URL:http://...as the
> syntax for a wrapper in ascii text, but requiring it in all other
> contexts seems silly.

I think I see the difference here. I don't consider anything "in context".
HTML is just as much an ASCII stream to me as a news message. If I have
to know every context's identification method them I might as well not
have URL: at all.

For example, I give you a bit stream. Nothing more. No identification, no
nothing. With URL: mandatory in all contexts you can find URLs in that
bit stream. With URL: not mandatory in all contexts you have to know and
understand ALL contexts....

    --
    ------------------------------------------------------------------------------
    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: David Robison: "Re: URN functionality from URLs"
- Previous message: Michael Mealling: "Re: Minor clarification on url: prefix (fwd)"