ISSUE-7: Deciding if we integrate a high level API in our deliverable
high level API
Deciding if we integrate a high level API in our deliverable
- State:
- CLOSED
- Product:
- design for Web Crypto API
- Raised by:
- Virginie GALINDO
- Opened on:
- 2012-08-01
- Description:
- During the Summer F2F meeting of the WG, a consensus was reached that the high level API would not be a priority for the group. This issue is to keep a track of the fact that we did not decide to cancel this high level API but to postpone it.
- Related Actions Items:
- No related actions
- Related emails:
- W3C Web Crypto WG - agenda for our call on monday 15th of april @ 20:00 UTC (from Virginie.GALINDO@gemalto.com on 2013-04-12)
- Re: [W3C Web Crypto WG] Proposal to close ISSUE-7 (from hhalpin@w3.org on 2013-04-04)
- [W3C Web Crypto WG] Proposal to close ISSUE-7 (from Virginie.GALINDO@gemalto.com on 2013-04-04)
- Proposal to close ISSUE-7 (from Virginie.GALINDO@gemalto.com on 2013-02-25)
- crypto-ISSUE-7 (high level API): Deciding if we integrate a high level API in our deliverable [Web Cryptography API] (from sysbot+tracker@w3.org on 2012-08-01)
Related notes:
Closed per http://www.w3.org/2013/04/15-crypto-minutes.html
Ryan Sleevi, 15 Apr 2013, 20:16:24Display change log