W3C home > Mailing lists > Public > public-webappsec@w3.org > January 2015

Re: [Integrity] typos with ni URIs

From: Mike West <mkwst@google.com>
Date: Tue, 20 Jan 2015 11:48:27 +0100
Message-ID: <CAKXHy=dtFGvE6Og_rZFc=8PQ0kb7eF=4th1OT=o7aQmJgXKEgA@mail.gmail.com>
To: Devdatta Akhawe <dev.akhawe@gmail.com>, Frederik Braun <fbraun@mozilla.com>, Joel Weinberger <jww@google.com>, Brad Hill <hillbrad@gmail.com>
Cc: Brian Smith <brian@briansmith.org>, "public-webappsec@w3.org" <public-webappsec@w3.org>, "Manger, James" <James.H.Manger@team.telstra.com>, Martin Thomson <martin.thomson@gmail.com>
+people who might care.

Without thinking about it too hard, I'd be fine with either of these. I'd
also be fine with keeping the `ni:`-style URL.

-mike (he of weak opinions, weakly held)

Mike West <mkwst@google.com>, @mikewest

Google Germany GmbH, Dienerstrasse 12, 80331 München,
Germany, Registergericht und -nummer: Hamburg, HRB 86891, Sitz der
Gesellschaft: Hamburg, Geschäftsführer: Graham Law, Christine Elizabeth
(Sorry; I'm legally required to add this exciting detail to emails. Bleh.)

On Tue, Jan 20, 2015 at 6:27 AM, Martin Thomson <martin.thomson@gmail.com>

> On 19 January 2015 at 13:40, Brian Smith <brian@briansmith.org> wrote:
> > Note that this is a valid URL, where the scheme is the digest name and
> > the path is the digest-value.
> Why go to the trouble of making it look like a URI?  A space separated
> list of hash-colon-base64urlDigest tuples should suffice.  Give
> content type its own attribute and avoid the bizarre delimiter.
Received on Tuesday, 20 January 2015 10:49:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:44 UTC