Re: Staying on Topic [Was: Re: WebPortable/PlatformProprietary - An Established Concept]

[Arthur Barstow]

On 2/19/15 9:57 AM, Anders Rundgren wrote:
Where are you supposed to propose new APIs?  Can such proposal be made 
by non-W3C members?
This was a proposal for using Chrome Native Messaging as the 
foundation for a new standard.


Perhaps you should pursue the Community Group process 
.


-Thanks, AB

Re: Staying on Topic [Was: Re: WebPortable/PlatformProprietary - An Established Concept]

[Anders Rundgren]

On 2015-02-19 15:47, Arthur Barstow wrote:

On 2/19/15 9:35 AM, Anders Rundgren wrote:

Hi Anders,


Hi Art,



In the spirit of restricting postings on this list to the group's
chartered scope ...


http://www.w3.org/2008/webapps/

"This work will include both documenting existing APIs such as XMLHttpRequest
 and developing new APIs in order to enable richer web applications"

Where are you supposed to propose new APIs?  Can such proposal be made by 
non-W3C members?
This was a proposal for using Chrome Native Messaging as the foundation for a 
new standard.

Cheers
Anders



I don't see a clear and direct connection between your posting [1] and
WebApps' chartered scope [2]. If I missed such a connection, please
focus your related postings to a specific spec and use the spec's
short-name as the Subject: prefix (f.ex. for the Manifest spec use
"[appmanifest] ...").

-Thanks, AB

[1]

[2] 

Staying on Topic [Was: Re: WebPortable/PlatformProprietary - An Established Concept]

[Arthur Barstow]

On 2/19/15 9:35 AM, Anders Rundgren wrote:

Hi Anders,

In the spirit of restricting postings on this list to the group's 
chartered scope ...


I don't see a clear and direct connection between your posting [1] and 
WebApps' chartered scope [2]. If I missed such a connection, please 
focus your related postings to a specific spec and use the spec's 
short-name as the Subject: prefix (f.ex. for the Manifest spec use 
"[appmanifest] ...").


-Thanks, AB

[1] 


[2] 

WebPortable/PlatformProprietary - An Established Concept

[Anders Rundgren]

HTTPS Client Certificate Authentication is supported by all browsers since 
almost 20 years back.
It exposes a fully standardized interface to Web Applications which simply is 
an URL.
In spite of that it is entirely proprietary with respect to integration in the 
browser platform
with implementations based on PKCS #11, CryptoAPI, JCE, .NET, NSS as well as 
working with a
huge range of secure key-containers like SIM, PIV, TEE, TPM, "Soft Keys".  This 
side of the
coin has not been standardized since it [provably] wasn't needed.

In: 
https://lists.w3.org/Archives/Public/public-webcrypto-comments/2015Jan/.html
Google's Ryan Sleevy writes:
   What you're looking for is
http://blog.chromium.org/2013/10/connecting-chrome-apps-and-extensions.html

This scheme could (after "Polishing" + W3C Standardization), without doubt 
support the same
powerful paradigm as HTTPS Client Certificate Authentication 
(WebPortable/PlatformProprietary),
for virtually any security application you could think of.

Cheers,
Anders