OPENPGP URI PROPOSAL

[Robert J. Hansen]

> This proposal is to provide an alternative to the openpgp block 
> messages, in the form of a uri ( e.g. `http://` ).

The format of a URI is, generally, "mechanism:address for that
mechanism".  For instance, email has a URI scheme:

	mailto:rjh at sixdemonbag.org?subject=URI%20schemes

FTP has one, too:

	ftp://ftp.gnupg.org

HTTP has them:

	http://www.gnupg.org

Filesystems have them:

	file:///Users/rjh/.gnupg/random_seed

There's an ISO standard for serial numbers:

	urn:ISSN:1535-3613

Heck, there's even a URI scheme for Gopher.

	gopher://wait.people.still.use.gopher?

You'll notice that for each of them, the first element in the URI is the
protocol by which a network resource should be obtained.  Web resources
start with "http:" to let people know to use HTTP to obtain them.  Mail
links start with "mailto:" to let people know they need an email client
to obtain the resource (or, in that case, deliver to that resource).  Etc.

It seems to me that you're confused as to what a URI is.  Your proposal
actually *delivers content*, as opposed to telling people where they can
find/deliver content and what protocol they should use to access it.

There may be some good ideas in this proposal, but there seems to be
such a misunderstanding of URIs and how they work that I'm not inclined
to delve too deeply.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20150521/35d48ede/attachment.sig>