/irc-logs / w3c / #html-wg / 2015-09-18 / end

Options:

Previous day, Next day

  1. # Session Start: Fri Sep 18 00:00:01 2015
  2. # Session Ident: #html-wg
  3. # [00:08] * heycam is now known as heycam|away
  4. # [01:17] * heycam|away is now known as heycam
  5. # [01:57] * heycam is now known as heycam|away
  6. # [03:10] * heycam|away is now known as heycam
  7. # [03:29] * Quits: bdougherty (~bdougherty@public.cloak) (Ping timeout: 180 seconds)
  8. # [03:29] * Joins: bdougherty (~bdougherty@public.cloak)
  9. # [06:26] * heycam is now known as heycam|away
  10. # [06:41] * heycam|away is now known as heycam
  11. # [07:39] * heycam is now known as heycam|away
  12. # [08:52] * Joins: johndrinkwater (~beta@public.cloak)
  13. # [08:57] * Quits: [Beta] (~beta@public.cloak) (Ping timeout: 180 seconds)
  14. # [09:18] * Joins: [Beta] (~beta@public.cloak)
  15. # [09:22] * Quits: johndrinkwater (~beta@public.cloak) (Ping timeout: 180 seconds)
  16. # [10:08] <MikeSmith> gsnedders: it hasn't all been decided yet but however it does end up being decided, there are a couple different ways you can choose to imagine conceptually what is happening
  17. # [10:08] <MikeSmith> one is to think of it as the html wg being merged into the webapps wg
  18. # [10:09] <MikeSmith> but I think that's not the best or more accurate way to look at it
  19. # [10:10] <MikeSmith> so the other more accurate way is to think of it as, a completely new group is being creating, with its scope defined such the it includes all technologies that are in the scope of the current webapps wg, and all that is in scope of the current html wg
  20. # [10:11] <MikeSmith> logistically that's actually exactly what's happening
  21. # [10:12] <MikeSmith> because, when the W3C says a group is "rechartered" (as opposed to just having its charter extended) it is in practice the same as creating a completely new group
  22. # [10:13] <MikeSmith> among other reasons why that's true is that when a group is rechartered, everybody currently in the group is basically kicked out of it
  23. # [10:13] <MikeSmith> that is, nobody joins the new WG automatically
  24. # [10:14] <MikeSmith> instead they have to go through the same process of joining the rechartered group that they would have to for a completely new group
  25. # [10:16] <MikeSmith> finally, everybody should be clear on the fact that the WebApps and HTML groups are not being "merged" in the sense that the new group is inheriting any members/participants from the HTML WG, nor any of the HTML WG's policies, or culture, or history
  26. # [10:16] <MikeSmith> it's starting from a clean slate
  27. # [10:17] <MikeSmith> in particular, the ~400 public-invited experts currently in the HTML WG are not going to have the opportunity to join the new WG
  28. # [10:17] <MikeSmith> instead, they have the same opportunity that everybody else in the community has, which is it join the Web Platform CG
  29. # [10:20] <MikeSmith> so the plan is the make the Web Platform WG relatively boring to tourists and dilettantes in that the WG will focus just on nuts-and-bolts technical discussions among implementors and other interested parties that are needed to get interoperability among implementations
  30. # [10:22] <MikeSmith> sao as far as people who want to have discussions about things other than "what do we need to do to get interoperability on feature X" and related topics that fall out from that goal, well, those people will be encouraged to take those discussion to other fora (e.g., the CG)
  31. # [10:25] <MikeSmith> and certainly if/when cranks and members of the lunatic fringe show up and want to have extended crazy talk about, say, <keygen> * or other non-features, then the chairs will be encouraged to move swiftly to show those people the door
  32. # [10:26] * Quits: hgl (~hgl@public.cloak) (hgl)
  33. # [10:27] * Joins: hgl (~hgl@public.cloak)
  34. # [10:27] <MikeSmith> in other words, the plan is to make the WG a place for actual implementors of specs can get real work done together without distractions and noise and loonies wandering in
  35. # [12:01] * Joins: johndrinkwater (~beta@public.cloak)
  36. # [12:07] * Quits: [Beta] (~beta@public.cloak) (Ping timeout: 180 seconds)
  37. # [14:58] * Joins: plh (plehegar@public.cloak)
  38. # [15:59] * Quits: hgl (~hgl@public.cloak) (hgl)
  39. # [16:00] * Joins: hgl (~hgl@public.cloak)
  40. # [17:02] * Quits: plh (plehegar@public.cloak) ("Leaving")
  41. # [17:03] * Joins: plh (plehegar@public.cloak)
  42. # [17:16] * Joins: gavin (~gavin@public.cloak)
  43. # [17:26] * Joins: gavin_ (~gavin@public.cloak)
  44. # [17:32] * Quits: gavin (~gavin@public.cloak) (Ping timeout: 180 seconds)
  45. # [17:33] <gsnedders> MikeSmith: does this also mean the majority of the work of the W3C outside of the Web Platform WG isn't part of the Web? :P
  46. # [17:49] <jgraham> I didn't think that was even controversial
  47. # [17:52] <gsnedders> Oh, I don't make that to sound controversial
  48. # [17:52] <gsnedders> just having a WG with that name makes it so much more obvious
  49. # [18:06] * Joins: rniwa (~textual@public.cloak)
  50. # [18:18] * Quits: hgl (~hgl@public.cloak) (Ping timeout: 180 seconds)
  51. # [18:20] * Joins: hgl (~hgl@public.cloak)
  52. # [19:12] * Quits: plh (plehegar@public.cloak) ("Leaving")
  53. # [19:12] * Joins: plh (plehegar@public.cloak)
  54. # [19:34] * Quits: rniwa (~textual@public.cloak) ("My Mac has gone to sleep. ZZZzzz…")
  55. # [20:10] * Joins: rniwa (~textual@public.cloak)
  56. # [20:34] <MikeSmith> gsnedders: yeah for me at least that's a postive feature of that name
  57. # [20:35] <MikeSmith> though I'm not the other people who upvoted that name choice realize yet that's the effect it had
  58. # [20:36] <MikeSmith> we do still have the Web Applications Security WG, which clearly working on specs for part of the Web (Platform)
  59. # [20:42] <hober> CSS, obvs.
  60. # [21:50] <MikeSmith> iaHixie_:
  61. # [21:50] <MikeSmith> hober: yeah
  62. # [21:53] * Quits: rniwa (~textual@public.cloak) ("Textual IRC Client: www.textualapp.com")
  63. # [21:59] <AAA_awright> MikeSmith: A problem I have (though haven't raised yet) is the Web Apps WG is very browser-centric. Take DOM, for instance, is implemented in Java, PHP, C++, just about everything, right. What about IndexedDB? That's not useful on servers too?
  64. # [22:00] <AAA_awright> And HTML should not be defining anything Javascript or WebIDL whatsoever, except element-specific APIs for DOM
  65. # [23:13] * Quits: plh (plehegar@public.cloak) ("Leaving")
  66. # Session Close: Sat Sep 19 00:00:00 2015

Previous day, Next day

Think these logs are useful? Then please donate to show your gratitude (and keep them up, of course). Thanks! — Krijn