W3C home > Mailing lists > Public > public-payments-wg@w3.org > April 2017

Re: [w3c/webpayments] Fingerprint and version metadata (in Web App Manifest spec) (#225)

From: Domenic Denicola <notifications@github.com>
Date: Mon, 03 Apr 2017 19:14:45 -0700
To: w3c/webpayments <webpayments@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webpayments/issues/225/291374773@github.com>
I'm a little worried people will think that the same considerations apply here as they do for SRI. That is, that adding this and basing it on SRI (even by just using the name "integrity") implies that Android supports all the same hash functions that SRI does; that it supports the fallback semantics of using multiple hash functions and the UA choosing the strongest; etc. Are we planning to actually reuse the SRI codepaths in our implementation, @rsolomakhin? My impression was that this was more of an Android-specific thing that we'd hand off to them.

In general I am more comfortable letting vendor-specific use cases be covered by vendor-specific properties, instead of trying to broaden the scope and make these generally applicable.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Received on Tuesday, 4 April 2017 02:15:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:25 UTC