http://www.w3.org/2008/security-ws/venue.html
I'm going to this event not because of any deep interests in APIs for location or battery power, but because there is a need to discuss how XML protocols like DSKPP, KeyGen2, WASP, WebAuth, and similar should be integrated in browsers. I don't believe that a new MIME-type for every protocol is the right way to go because that would require that the HTTP Accept tag would be indefinitely extended in order for a server to discover if a client is XYZ-protocol-capable. There is also the versioning stuff. My personal preference is to assign a single MIME-type for XML protocols and use the name-space + [optional XSD version] as protocol ID as well as supporting a discovery mechanism, but really, the only thing that matters is that we get "something" which indeed can be the device JavaScript API. The important thing is how easy you can plug-in a new protocol into the framework. That Microsoft's Information Cards specify 2 completely different methods for invocation is an indication that it is about time creating something generic. Anders Rundgren http://WebPKI.org
_______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
