- From: <bugzilla@jessica.w3.org>
- Date: Tue, 18 Dec 2012 06:03:49 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17682
Adrian Bateman [MSFT] <adrianba@microsoft.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adrianba@microsoft.com
--- Comment #7 from Adrian Bateman [MSFT] <adrianba@microsoft.com> ---
At TPAC (and then at the 12/11 telcon) we discussed:
* If we want to build a JSON syntax based on an extension to
draft-ietf-jose-json-web-key then we should document this in an appendix to the
spec and work with IETF to see if they will incorporate these extensions into
one of their specs. If we are successful then we could remove the appendix and
replace it with a normative reference as late as the CR->PR transition.
* By incorporating the details in an appendix to the EME spec we keep hold of
our own destiny rather than making the spec dependent on another group.
* The next action is to propose actual spec text for a concrete JSON-based
proposal.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 18 December 2012 06:04:07 UTC