[Bug 26957] Allow sending DOM objects to Workers and expose a DOM (or DOM-like) interface to workers
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26957 Ms2ger ms2...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED CC||ms2...@gmail.com Resolution|--- |WONTFIX --- Comment #4 from Ms2ger ms2...@gmail.com --- Closing for all the same reasons as before. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 25540] Invalid use of [EnsureUTF16]
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25540 Bug 25540 depends on bug 24581, which changed state. Bug 24581 Summary: Fix ByteString type [EnsureUTF16] flag story https://www.w3.org/Bugs/Public/show_bug.cgi?id=24581 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 23346] Use TypeError for argument validation
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23346 Bug 23346 depends on bug 24581, which changed state. Bug 24581 Summary: Fix ByteString type [EnsureUTF16] flag story https://www.w3.org/Bugs/Public/show_bug.cgi?id=24581 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.
Re: Looking for a home for a proposed Credential Management API.
On 09/24/2014 09:57 AM, Mike West wrote: There's a credentials community group that has nothing to do with the proposal There's more in common than you might think. Fundamentally, the Credentials CG would like to ensure that the Credentials API that you're proposing supports the type of high-stakes, digitally signed credentials (like government-issued passports, professional licenses, background checks, etc.) that we need for the Web Payments work. I suggest reading up on what we'd like to see here: http://manu.sporny.org/2014/credential-based-login/ http://manu.sporny.org/2014/identity-credentials/ I'll do a review of your spec and use cases from a Credentials CG viewpoint. I'm happy to get on the phone w/ you and discuss things in more technical depth when you become available. That said, the right place to discuss the API is most likely Web Apps with input from WebCrypto WG, Security IG, Web Payments IG, FIDO Alliance, and the Credentials CG. I don't think you can do a good job on the API you're proposing without all of their involvement. and given the weak IPR protections of a CG, I'd prefer to avoid them in the long run (though they might be the right place for short-term incubation). I agree that the Credentials CG (or any CG) isn't the right place for the work in the long run. Keep in mind that the Web Payments work will most likely be starting soon, and they'll be in charge of recommending new WGs to be chartered to support the work. Transmitting credentials is a big part of the problem and a few modifications to your API could address that issue. Another option would be to create a new a new CG (although I suppose there could be some confusion with Manu's Credentials CG http://www.w3.org/community/credentials/). The Credentials CG can provide input, but most of the right people to talk about the API (and all of the potential security issues) probably exist in WebApps. As Robin said earlier in the thread, I wouldn't focus too much on the process and the right group too much. Get documents published, get implementations and polyfills done, then ping all of the groups listed above to get their feedback. The Credentials CG would be happy to provide input on the API as it relates to our use cases. -- manu -- Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny) Founder/CEO - Digital Bazaar, Inc. blog: High-Stakes Credentials and Web Login http://manu.sporny.org/2014/identity-credentials/
[TPAC2014] Final Reminder: f2f meeting registration deadline is October 8
On 9/10/14 10:17 AM, Arthur Barstow wrote: This is a reminder WebApps will meet on Monday and Tuesday (October 27 and 28) during [TPAC2014]. Registration for WebApps' meeting (as well as all other meetings and events that week) is mandatory. https://www.w3.org/2002/09/wbs/35125/TPAC2014/ The registration deadline is October 8. The meetings will be at the Santa Clara Marriott hotel (just a few miles from SJC airport) and the hotel discount for meeting participants expires October 3. The daily meeting fee has increased to 75.00 USD. The group's meeting page including draft agenda is still mostly an open template [Agenda]. I'm expecting to again focus the agenda on high(er) priority Bugs and Issues, as well as to preallocate some time slots in advance and to determine the other slots at the meeting. As I did before WebApps' last meeting, a few weeks before the meeting, I will ping all Editors for status, plans, hot topics, blocking issues, etc. Please note the Wednesday October 29 Technical Plenary meeting will end at 14:15 and proposals for parallel breakouts sessions can be made at [SessionIdeas]. The W3C @ 20 event [W3C@20] starts @ 15:00 that day and includes a few speakers plus a Future of the Web panel, followed by gala dinner. I expect this day to be interesting and lot of fun; I encourage everyone to attend. -Thanks, AB [TPAC2014] http://www.w3.org/2014/11/TPAC/ [Agenda] https://www.w3.org/wiki/Webapps/November2014Meeting [SessionIdeas] https://www.w3.org/wiki/TPAC2014/SessionIdeas [W3C@20] http://www.w3.org/20/
