Options:
- # Session Start: Thu Apr 12 00:00:01 2012
- # Session Ident: #html-wg
- # [00:13] * Quits: drublic (drublic@77.2.133.250) (Ping timeout)
- # [00:31] * Joins: mattkelly (mattwkelly@173.252.71.3)
- # [00:55] * Joins: rniwa_ (rniwa@72.14.229.81)
- # [00:55] * Quits: rniwa (rniwa@72.14.229.81) (Connection reset by peer)
- # [00:55] * rniwa_ is now known as rniwa
- # [01:03] * Joins: rniwa_ (rniwa@72.14.229.81)
- # [01:03] * Quits: rniwa (rniwa@72.14.229.81) (Connection reset by peer)
- # [01:03] * rniwa_ is now known as rniwa
- # [01:05] * miketaylr|||| is now known as miketaylr|||||
- # [01:05] * miketaylr||||| is now known as miketaylr||||||
- # [01:15] * Quits: mattkelly (mattwkelly@173.252.71.3) (Ping timeout)
- # [01:36] * Joins: abarsto (abarsto@192.100.120.41)
- # [01:36] * abarsto is now known as ArtB
- # [01:46] * heycam|away is now known as heycam
- # [01:47] * Quits: vimeo_joe (vimeo_joe@71.202.222.94) (Client exited)
- # [01:47] * Joins: vimeo_joe (vimeo_joe@71.202.222.94)
- # [01:50] * Quits: vimeo_joe (vimeo_joe@71.202.222.94) (Ping timeout)
- # [01:55] * Quits: nesta_ (nesta_@88.11.38.57) (Ping timeout)
- # [02:07] * Quits: tantek (tantek@63.245.220.240) (Quit: tantek)
- # [02:20] * Joins: mattkelly (mattwkelly@173.252.71.3)
- # [02:24] * Quits: mattkelly (mattwkelly@173.252.71.3) (Ping timeout)
- # [02:31] * Joins: mattkelly (mattwkelly@64.34.186.7)
- # [02:40] * hiro_away is now known as hiro
- # [02:42] * Quits: tH (Rob@77.86.58.134) (Quit: ChatZilla 0.9.88-rdmsoft [XULRunner 1.9.0.1/2008072406])
- # [02:48] * Joins: tantek (tantek@69.181.124.51)
- # [02:55] * Joins: MikeSmith (MikeSmith@180.7.144.181)
- # [03:20] * Quits: tantek (tantek@69.181.124.51) (Quit: tantek)
- # [03:26] * Joins: tantek (tantek@69.181.124.51)
- # [03:29] * Quits: tantek (tantek@69.181.124.51) (Quit: tantek)
- # [03:31] * Quits: mattkelly (mattwkelly@64.34.186.7) (Ping timeout)
- # [03:51] * Quits: [tm] (MikeSmith@80.68.92.65) (Ping timeout)
- # [03:53] * Joins: mattkelly (mattwkelly@69.181.69.39)
- # [03:56] * Joins: [tm] (MikeSmith@80.68.92.65)
- # [03:58] * hiro is now known as hiro_away
- # [04:00] * Joins: tantek (tantek@69.181.124.51)
- # [04:00] * hiro_away is now known as hiro
- # [04:07] * Quits: ArtB (abarsto@192.100.120.41) (Quit: Leaving.)
- # [04:13] * Quits: mattkelly (mattwkelly@69.181.69.39) (Ping timeout)
- # [04:53] * Joins: dsinger (dsinger@206.205.126.201)
- # [05:12] * Quits: rniwa (rniwa@72.14.229.81) (Quit: rniwa)
- # [05:17] * Quits: miketaylr|||||| (miketaylr@70.112.101.224) (Quit: Leaving...)
- # [05:25] * heycam is now known as heycam|away
- # [05:25] <CIA-1> validator: Michael[tm] Smith <mike@w3.org> * d6e8991f4c34 r435 validator/schema/svg11/svg-font.rnc:
- # [05:25] <CIA-1> validator: Make <svg><font> not cause NullPointerException.
- # [05:25] <CIA-1> validator: b=917
- # [05:28] * Joins: miketaylr (miketaylr@70.112.101.224)
- # [05:43] * Quits: tantek (tantek@69.181.124.51) (Quit: tantek)
- # [05:58] * heycam|away is now known as heycam
- # [06:02] * hiro is now known as hiro_away
- # [06:08] * Joins: tantek (tantek@208.54.5.174)
- # [06:47] * Joins: myakura (myakura@119.243.157.97)
- # [06:50] * Joins: mattkelly (mattwkelly@69.181.69.39)
- # [06:54] * hiro_away is now known as hiro
- # [06:57] * Quits: mattkelly (mattwkelly@69.181.69.39) (Ping timeout)
- # [07:04] * Quits: tantek (tantek@208.54.5.174) (Quit: tantek)
- # [07:06] * Joins: rniwa (rniwa@70.89.66.218)
- # [07:10] * Joins: tantek (tantek@208.54.5.174)
- # [07:13] * hiro is now known as hiro_away
- # [07:18] * Quits: tantek (tantek@208.54.5.174) (Quit: tantek)
- # [07:20] * Joins: tantek (tantek@208.54.5.174)
- # [07:24] * Quits: miketaylr (miketaylr@70.112.101.224) (Quit: Leaving...)
- # [07:25] * Joins: nesta_ (nesta_@88.30.34.113)
- # [07:25] * Quits: nesta_ (nesta_@88.30.34.113) (Quit: nesta_)
- # [07:31] * Quits: tantek (tantek@208.54.5.174) (Ping timeout)
- # [08:33] * Joins: nesta_ (nesta_@81.36.68.79)
- # [08:34] <nesta_> good day! :)
- # [08:46] * Joins: rniwa_ (rniwa@70.89.66.218)
- # [08:47] * Quits: rniwa (rniwa@70.89.66.218) (Ping timeout)
- # [08:47] * rniwa_ is now known as rniwa
- # [09:12] * Joins: tantek (tantek@50.76.55.246)
- # [09:24] * Quits: hober (ted@174.143.153.77) (Client exited)
- # [09:29] * Quits: myakura (myakura@119.243.157.97) (Client exited)
- # [09:33] * Quits: tantek (tantek@50.76.55.246) (Quit: tantek)
- # [09:37] * hiro_away is now known as hiro
- # [09:39] * Joins: lar_zzz (lar_zzz@88.79.143.185)
- # [09:52] * Joins: tantek (tantek@70.36.139.112)
- # [10:03] * hiro is now known as hiro_away
- # [10:15] * Quits: dveditz (dveditz@63.249.86.37) (Quit: dveditz)
- # [10:48] * Joins: drublic (drublic@93.132.253.60)
- # [10:53] * Joins: lar_zzz1 (lar_zzz@88.79.143.185)
- # [10:53] * Quits: lar_zzz (lar_zzz@88.79.143.185) (Connection reset by peer)
- # [10:59] * Joins: lar_zzz (lar_zzz@88.79.143.185)
- # [10:59] * Quits: lar_zzz1 (lar_zzz@88.79.143.185) (Connection reset by peer)
- # [11:01] * Quits: lar_zzz (lar_zzz@88.79.143.185) (Connection reset by peer)
- # [11:02] * Joins: lar_zzz1 (lar_zzz@88.79.143.185)
- # [11:07] * hiro_away is now known as hiro
- # [11:23] * Joins: nonge_ (nonge@91.50.110.229)
- # [11:23] * hiro is now known as hiro_away
- # [11:25] * Quits: nonge (nonge@91.50.107.78) (Ping timeout)
- # [11:55] * Joins: Lachy (Lachy@213.236.208.247)
- # [11:55] * Quits: Lachy (Lachy@213.236.208.247) (Quit: Bye)
- # [11:55] * Joins: Lachy (Lachy@213.236.208.22)
- # [11:59] * Quits: Jedi (Jedi@220.134.95.85) (Ping timeout)
- # [12:00] * Joins: mjs (mjs@76.8.86.25)
- # [12:10] * Quits: mjs (mjs@76.8.86.25) (Quit: mjs)
- # [12:14] * Joins: mjs (mjs@76.8.86.25)
- # [12:16] * Quits: mjs (mjs@76.8.86.25) (Quit: mjs)
- # [12:30] * Joins: Jedi (Jedi@220.134.95.85)
- # [12:46] * Quits: icaaq1 (Adium@85.228.175.141) (Quit: Leaving.)
- # [12:54] * Joins: icaaq (Adium@85.228.175.141)
- # [12:55] * heycam is now known as heycam|away
- # [12:59] * Joins: tH (Rob@77.86.58.134)
- # [13:06] * Joins: mjs (mjs@166.249.128.227)
- # [13:27] * Joins: myakura (myakura@119.243.157.97)
- # [13:32] * Quits: mjs (mjs@166.249.128.227) (Quit: mjs)
- # [13:33] * Joins: mjs (mjs@166.249.128.227)
- # [13:34] * Quits: anne (annevk@82.161.179.17) (Client exited)
- # [13:34] * Joins: anne (annevk@82.161.179.17)
- # [13:34] * Quits: mjs (mjs@166.249.128.227) (Quit: mjs)
- # [14:07] * Joins: plh (plh@128.30.52.28)
- # [14:09] * Joins: abarsto (abarsto@192.100.120.41)
- # [14:09] * abarsto is now known as ArtB
- # [14:13] * Quits: dsinger (dsinger@206.205.126.201) (Quit: dsinger)
- # [14:15] * Joins: davidb (davidb@65.93.94.10)
- # [14:22] * Quits: lar_zzz1 (lar_zzz@88.79.143.185) (Quit: Leaving.)
- # [14:22] * Joins: lar_zzz (lar_zzz@88.79.143.185)
- # [14:55] * Joins: dsinger (dsinger@131.107.32.25)
- # [15:34] * Quits: nesta_ (nesta_@81.36.68.79) (Client exited)
- # [15:35] * Joins: nesta_ (nesta_@81.36.68.79)
- # [15:38] * Quits: nesta_ (nesta_@81.36.68.79) (Ping timeout)
- # [15:40] * Joins: miketaylr (miketaylr@70.112.101.224)
- # [15:59] * Joins: glenn (gadams@174.29.126.179)
- # [16:51] * Joins: hober (ted@174.143.153.77)
- # [16:53] * Quits: lar_zzz (lar_zzz@88.79.143.185) (Quit: Leaving.)
- # [17:06] <MikeSmith> issue-189?
- # [17:06] * trackbot getting information on ISSUE-189
- # [17:06] <trackbot> ISSUE-189 -- Prefix convention needs to be coordinated with IETF -- open
- # [17:06] <trackbot> http://www.w3.org/html/wg/tracker/issues/189
- # [17:15] * Joins: ksweeney (ksweeney@63.119.10.10)
- # [17:16] * Quits: glenn (gadams@174.29.126.179) (Ping timeout)
- # [17:17] * Joins: glenn (gadams@174.29.126.28)
- # [17:19] <hober> MikeSmith: thanks for that email re: ISSUE-189
- # [17:19] <MikeSmith> yup
- # [17:23] * Parts: ksweeney (ksweeney@63.119.10.10)
- # [17:27] * Joins: vimeo_joe (vimeo_joe@71.202.222.94)
- # [17:29] * Joins: dveditz (dveditz@63.249.86.37)
- # [17:30] * Quits: vimeo_joe (vimeo_joe@71.202.222.94) (Client exited)
- # [17:30] * Joins: vimeo_joe (vimeo_joe@71.202.222.94)
- # [17:31] * Joins: vimeo_jo_ (vimeo_joe@71.202.222.94)
- # [17:31] * Quits: vimeo_joe (vimeo_joe@71.202.222.94) (Connection reset by peer)
- # [17:31] * Quits: vimeo_jo_ (vimeo_joe@71.202.222.94) (Client exited)
- # [17:31] * Joins: vimeo_joe (vimeo_joe@71.202.222.94)
- # [17:32] * Quits: dveditz (dveditz@63.249.86.37) (Ping timeout)
- # [17:37] * hiro_away is now known as hiro
- # [17:39] * Quits: anne (annevk@82.161.179.17) (Client exited)
- # [17:56] * Quits: dsinger (dsinger@131.107.32.25) (Ping timeout)
- # [17:56] * hober is now known as hober2
- # [17:57] * Joins: hober (ted@17.212.152.28)
- # [17:59] * Joins: lar_zzz (lar_zzz@88.79.143.185)
- # [18:00] * Quits: Lachy (Lachy@213.236.208.22) (Quit: Computer has gone to sleep.)
- # [18:03] * Joins: paulc (qw3birc@128.30.52.28)
- # [18:04] * Joins: Clarke (qw3birc@128.30.52.28)
- # [18:05] * Joins: rubys (rubys@98.27.59.167)
- # [18:05] * Joins: Zakim (rrs-bridgg@128.30.52.169)
- # [18:06] <glenn> zakim, who's here?
- # [18:06] <Zakim> sorry, glenn, I don't know what conference this is
- # [18:06] <Zakim> On IRC I see rubys, Clarke, paulc, lar_zzz, hober, vimeo_joe, glenn, hober2, miketaylr, davidb, ArtB, plh, myakura, tH, icaaq, Jedi, nonge_, drublic, tantek, rniwa, [tm],
- # [18:06] <Zakim> ... MikeSmith, logbot, arronei, kennyluck, gsnedders, pingo, karl, danielfilho, gavin, krijnh, ed, paul___irish, RRSAgent, johndrinkwater, shepazu, hiro, hsivonen, Hixie, lgombos,
- # [18:06] <Zakim> ... heycam|away, Dashiva, rektide, Philip, trackbot, inimino, jmb, CIA-1, jgraham
- # [18:06] <glenn> zakim, this is html_wg
- # [18:06] <Zakim> ok, glenn; that matches HTML_WG()12:00PM
- # [18:06] <tantek> greetings
- # [18:06] <MikeSmith> Zakim, call Mike
- # [18:06] <Zakim> ok, MikeSmith; the call is being made
- # [18:06] <Zakim> +Mike
- # [18:06] <glenn> zakim, who's here?
- # [18:06] <Zakim> On the phone I see ??P1, ??P7 (muted), Mike (muted)
- # [18:06] <Zakim> On IRC I see rubys, Clarke, paulc, lar_zzz, hober, vimeo_joe, glenn, hober2, miketaylr, davidb, ArtB, plh, myakura, tH, icaaq, Jedi, nonge_, drublic, tantek, rniwa, [tm],
- # [18:06] <MikeSmith> tantek, hola
- # [18:06] <tantek> scribe, I'm only on IRC for this meeting
- # [18:06] <Zakim> ... MikeSmith, logbot, arronei, kennyluck, gsnedders, pingo, karl, danielfilho, gavin, krijnh, ed, paul___irish, RRSAgent, johndrinkwater, shepazu, hiro, hsivonen, Hixie, lgombos,
- # [18:06] <tantek> hi MikeSmith
- # [18:06] <glenn> zakim, ??p7 is glenn
- # [18:06] <Zakim> ... heycam|away, Dashiva, rektide, Philip, trackbot, inimino, jmb, CIA-1, jgraham
- # [18:06] <Zakim> +glenn; got it
- # [18:07] <Clarke> zakim, ??P1 is me
- # [18:07] <Zakim> +Clarke; got it
- # [18:07] * Joins: eliot (eliot@131.107.0.110)
- # [18:07] * Joins: Julian (chatzilla@217.91.35.233)
- # [18:07] * Joins: cjones (cjones@78.148.89.60)
- # [18:07] <Zakim> +Sam
- # [18:08] <Zakim> +[Microsoft]
- # [18:08] <eliot> zakim, Microsoft is me
- # [18:08] <Zakim> +eliot; got it
- # [18:08] <Zakim> +[Apple]
- # [18:08] <hober> Zakim, Apple has me
- # [18:08] <Zakim> +hober; got it
- # [18:08] * Joins: adrianba (qw3birc@128.30.52.28)
- # [18:08] <paulc> havng trouble calling in
- # [18:09] * Joins: MFoladare (qw3birc@128.30.52.28)
- # [18:09] * Joins: KevinStreeter (KevinStree@192.150.10.201)
- # [18:09] * hober it took me a couple of tries
- # [18:09] <Zakim> +[Microsoft]
- # [18:09] <paulc> zakim, [Microsoft] has paulc
- # [18:09] <Zakim> +paulc; got it
- # [18:09] <rubys> chair: paulc
- # [18:09] <Zakim> +Radhika_Roy
- # [18:09] <rubys> scribenick: rubys
- # [18:09] <Zakim> +KevinStreeter
- # [18:10] <Zakim> + +49.251.280.aaaa
- # [18:10] <rubys> agenda: http://lists.w3.org/Archives/Public/public-html-wg-announce/2012AprJun/0004.html
- # [18:10] <paulc> zakim, who is on the call?
- # [18:10] <Zakim> On the phone I see Clarke, glenn (muted), Mike, Sam, eliot, [Apple], [Microsoft], Radhika_Roy, KevinStreeter, +49.251.280.aaaa
- # [18:10] <Zakim> [Apple] has hober
- # [18:10] <Zakim> [Microsoft] has paulc
- # [18:10] <Zakim> +[Microsoft.a]
- # [18:10] <adrianba> zakim, [Microsoft.a] is me
- # [18:10] <Zakim> +adrianba; got it
- # [18:10] <Julian> Zakim, +49.251.280.aaaa is me
- # [18:10] <Zakim> +Julian; got it
- # [18:10] <Julian> Zakim, mute me
- # [18:10] <Zakim> Julian should now be muted
- # [18:11] <rubys> topic: ACTION items due by Thursday, April 12
- # [18:11] <rubys> paulc: there are none
- # [18:11] <Zakim> +Joseph_Scheuhammer
- # [18:11] <rubys> topic: New Issues This Week
- # [18:11] <rubys> paulc: there are no new issues, and there still is one tracker request
- # [18:11] <rubys> topic: Items Closed Last Week
- # [18:11] <rubys> issue-194?
- # [18:11] * trackbot getting information on ISSUE-194
- # [18:11] <trackbot> ISSUE-194 -- Provide a mechanism for associating a full transcript with an audio or video element. -- open
- # [18:11] <trackbot> http://www.w3.org/html/wg/tracker/issues/194
- # [18:12] <rubys> paulc: we have two proposals in hand, and the chairs are now due to review those
- # [18:12] * hiro is now known as hiro_away
- # [18:12] <rubys> issue-148?
- # [18:12] * trackbot getting information on ISSUE-148
- # [18:12] <trackbot> ISSUE-148 -- Algorithm for detecting the charset="" parameter -- closed
- # [18:12] <trackbot> http://www.w3.org/html/wg/tracker/issues/148
- # [18:12] <rubys> paulc: survey closed on April 6, Sam temporarily reopened it to allow a late comment, and there still is some dialog going on
- # [18:12] <paulc> http://lists.w3.org/Archives/Public/public-html/2012Apr/0051.html
- # [18:13] * Joins: ddorwin (qw3birc@128.30.52.28)
- # [18:13] <rubys> paulc: the chairs will have to decide how to handle this message; we may reopen the survey temporarily to allow this to be added
- # [18:13] <rubys> paulc: any comments?
- # [18:13] <rubys> topic: Items Closing This Week
- # [18:13] <rubys> issue-184?
- # [18:13] * trackbot getting information on ISSUE-184
- # [18:13] <trackbot> ISSUE-184 -- Add a data element -- open
- # [18:13] <trackbot> http://www.w3.org/html/wg/tracker/issues/184
- # [18:13] <Zakim> +Juhahi
- # [18:13] <rubys> paulc: CfC closed last night
- # [18:14] <rubys> paulc: I don't see any objections
- # [18:14] <rubys> paulc: I'm expecting that a decision will be issued fairly quickly
- # [18:14] <rubys> issue-198?
- # [18:14] * trackbot getting information on ISSUE-198
- # [18:14] <trackbot> ISSUE-198 -- Ensure innerHTML and related APIs are subject to the W3C patent policy -- open
- # [18:14] <trackbot> http://www.w3.org/html/wg/tracker/issues/198
- # [18:15] * Joins: Juhani (qw3birc@128.30.52.28)
- # [18:15] <rubys> paulc: there has been some debate. The chairs may reissue the CfC
- # [18:15] <rubys> issue-201?
- # [18:15] * trackbot getting information on ISSUE-201
- # [18:15] <trackbot> ISSUE-201 -- Provide canvas location and hit testing capability to fallback content -- open
- # [18:15] <trackbot> http://www.w3.org/html/wg/tracker/issues/201
- # [18:15] <rubys> paulc: closed yesterday, we received the counter proposals; the chairs will hold off any actions until the F2F in May
- # [18:16] <rubys> paulc: this was a request from the a11y TF, and is a reasonable request
- # [18:16] <rubys> issue-183?
- # [18:16] * trackbot getting information on ISSUE-183
- # [18:16] <trackbot> ISSUE-183 -- Enhance and simplify the time element -- open
- # [18:16] <trackbot> http://www.w3.org/html/wg/tracker/issues/183
- # [18:16] <rubys> paulc: closes tomorrow
- # [18:17] <rubys> paulc: are any of the authors on the call?
- # [18:17] <Zakim> +??P14
- # [18:17] * Joins: janina (janina@69.140.165.18)
- # [18:18] <rubys> rubys: Cameron posted his change recently
- # [18:18] <rubys> http://lists.w3.org/Archives/Public/public-html/2012Apr/0065.html
- # [18:18] <paulc> http://www.w3.org/wiki/User:Cjones/ISSUE-183
- # [18:18] <janina> zakim, who's on the phone?
- # [18:18] <Zakim> On the phone I see Clarke, glenn (muted), Mike, Sam, eliot, [Apple], [Microsoft], Radhika_Roy, KevinStreeter, Julian (muted), adrianba, Joseph_Scheuhammer, Juhahi, ??P14
- # [18:18] <Zakim> [Apple] has hober
- # [18:18] <Zakim> [Microsoft] has paulc
- # [18:18] <rubys> paulc: that would put this back into the chairs queue to reevaluate
- # [18:18] <janina> zakim, ??P14 is Janina
- # [18:18] <Zakim> +Janina; got it
- # [18:18] <rubys> topic: Items Closing Next Week
- # [18:18] <rubys> issue-204?
- # [18:18] * trackbot getting information on ISSUE-204
- # [18:18] <trackbot> ISSUE-204 -- Exempt ARIA attributes from the rule that prohibits reference to hidden elements -- open
- # [18:18] <trackbot> http://www.w3.org/html/wg/tracker/issues/204
- # [18:19] <rubys> paulc: the A11y TF is actively working this issue
- # [18:19] <rubys> topic: New Calls this week
- # [18:19] <rubys> paulc: there are none
- # [18:19] <rubys> topic: New Surveys this week
- # [18:19] <rubys> paulc: there are none
- # [18:19] <rubys> topic: Decisions this week
- # [18:19] <rubys> paulc: there are none
- # [18:19] <rubys> topic: Other Business
- # [18:20] <rubys> CfC: Create Media Task Force http://lists.w3.org/Archives/Public/public-html/2012Apr/0007.html
- # [18:20] <rubys> paulc: we got a request to extend this by a week; I've extended this consensus to next wednesday
- # [18:20] * rubys no objection here
- # [18:20] <MikeSmith> q+ to talk about IRI WG ticket related to issue 189
- # [18:20] * Zakim sees MikeSmith on the speaker queue
- # [18:20] <rubys> ack next
- # [18:20] * Zakim sees MikeSmith at the head of the speaker queue
- # [18:20] <Zakim> MikeSmith, you wanted to talk about IRI WG ticket related to issue 189
- # [18:20] * Zakim sees no one on the speaker queue
- # [18:21] <rubys> Call for agenda topics for May face-to-face meeting http://lists.w3.org/Archives/Public/public-html/2012Apr/0006.html
- # [18:21] <rubys> paulc: we already have one suggestions
- # [18:21] <rubys> s/suggestions/suggestion/
- # [18:21] <rubys> paulc: we currently have 30 people registered for the HTML WG meeting
- # [18:21] <rubys> paulc: the registration closes on monday
- # [18:22] <rubys> paulc: we will look for candidate items up to the point of the meeting, which will be run in an unconference style
- # [18:22] <rubys> paulc: comments?
- # [18:22] <rubys> mike: I sent mail about issue 189
- # [18:22] <rubys> http://lists.w3.org/Archives/Public/public-html/2012Apr/0075.html
- # [18:23] <rubys> mike: the IETF IRI working group had an ticket opened on this item
- # [18:23] <rubys> s/an ticket/a ticket/
- # [18:23] <rubys> http://trac.tools.ietf.org/wg/iri/trac/ticket/123
- # [18:24] <rubys> mike: if you look at that ticket, you will see that the current status is CLOSED/FIXED; seen as out of scope
- # [18:24] <Julian> q+
- # [18:24] * Zakim sees Julian on the speaker queue
- # [18:24] * Quits: nonge_ (nonge@91.50.110.229) (Quit: Verlassend)
- # [18:24] <rubys> mike: the IRI working has no plans to work this
- # [18:25] <paulc> http://dev.w3.org/html5/status/issue-status.html#ISSUE-189
- # [18:25] <rubys> mike: the issue contains an assertion that we need to work with the IETF. It is not clear who to coordinate with if the IRI working group hasn't taken this up.
- # [18:25] <rubys> mike: if the status changes, I will communicate that back
- # [18:25] <rubys> mike: neither of the chairs of the IRI WG are members of the HTML WG
- # [18:26] <Julian> Zakim, unmute me
- # [18:26] <Zakim> Julian should no longer be muted
- # [18:27] <rubys> julian: as the one who opened the HTML WG issue and the IRI ticket I can speak to both.
- # [18:27] <rubys> julian: I was in Paris with the IRI WG 14 days ago. They have no plans to discuss this until they are asked by the HTML WG.
- # [18:28] <rubys> julian: I don't know with whom Mike has spoken, the feedback he provided is not what I remember from that meeting
- # [18:29] <MikeSmith> q+ to say that no, I don't think the IRI WG is expecting to be formally contacted by the HTML WG
- # [18:29] * Zakim sees Julian, MikeSmith on the speaker queue
- # [18:29] <rubys> julian: I know that I am on the hook to update my CP. My update will state that we need coordination, and I don't volunteer to be that person as I don't believe that feature is needed.
- # [18:29] * Quits: lar_zzz (lar_zzz@88.79.143.185) (Quit: Leaving.)
- # [18:29] <rubys> paulc: date for update:
- # [18:30] <rubys> julian: I plan to get to that next weekend; it won't be a big change
- # [18:30] <rubys> paulc: ETA would Monday, April 16th
- # [18:30] <rubys> ack next
- # [18:30] * Zakim sees Julian at the head of the speaker queue
- # [18:30] * Zakim sees MikeSmith on the speaker queue
- # [18:30] <rubys> ack next
- # [18:30] * Zakim sees MikeSmith at the head of the speaker queue
- # [18:30] <Zakim> MikeSmith, you wanted to say that no, I don't think the IRI WG is expecting to be formally contacted by the HTML WG
- # [18:30] * Zakim sees no one on the speaker queue
- # [18:31] <rubys> mike: the IRI WG has taken no resolution indicating that they are waiting on anything
- # [18:31] <tantek> rubys - just saw mention of 183 - I'm on IRC but not on the phone.
- # [18:32] <rubys> mike: Julian if you believe differently, please ask them to confirm that. It is quite possible that's not in the minutes.
- # [18:32] <rubys> s/It is quite possible that's not in the minutes.//
- # [18:32] <rubys> julian: It is quite possible that's not in the minutes.
- # [18:32] <tantek> I must admit I'm having trouble following the length and complexity of the CJones proposal
- # [18:32] <rubys> mike: I talked to both chairs
- # [18:33] <rubys> mike: we don't have agreement that any coordination is necessary. That's what is in dispute.
- # [18:33] * Quits: drublic (drublic@93.132.253.60) (Client exited)
- # [18:33] <rubys> julian: it wouldn't be the IRI WG, it would be the apps area in general
- # [18:34] <rubys> julian: I talked Thomas and Mark, we have a meta-coordination area
- # [18:34] <rubys> mike: you should talk to PLH too
- # [18:34] <tantek> what's the best way to iterate on / respond to http://www.w3.org/wiki/User:Cjones/ISSUE-183 ? a point by point discussion?
- # [18:35] <rubys> julian: if an action item were assigned to me, I would close it as already done
- # [18:35] <rubys> paulc: is your advise to wait for the IETF
- # [18:35] <rubys> julian: there is nobody official who can answer that
- # [18:36] <rubys> julian: this is something that should be handled on the liaison people
- # [18:36] <Julian> Zakim, unmute me
- # [18:36] <Zakim> Julian was not muted, Julian
- # [18:36] <rubys> paulc: I will convey this to PLH
- # [18:36] <Julian> Zakim, mute me
- # [18:36] <Zakim> Julian should now be muted
- # [18:38] <paulc> tantek: I suggest you respond directly to the email and if your points are sufficiently different then split the response into separate emails with appropriate Subject: fields
- # [18:38] <paulc> BTW "the email" I meant the one where Cameron announced his revision.
- # [18:38] <rubys> paulc: any other business?
- # [18:39] <cjones> tantek: i'm keen to answer any questions you have on the proposal
- # [18:39] <rubys> janina: from the A11y TF, we would like to get on record requesting that issue-201 hold off further action until after the F2F
- # [18:39] <rubys> paulc: I've already mentioned it on the call; we will likely respond on public-html on that item today
- # [18:39] <rubys> paulc: any other other business?
- # [18:39] <tantek> biggest problems are with the objections to <time> being dependent on future hypotheticals, and the suggestion to use input types instead put far more burden on authors - why should an author have to decide between type="date" and type="datetime" and the numerous other datetime related input types?
- # [18:39] <rubys> paulc: none heard
- # [18:39] <rubys> topic: Scribe for next meeting
- # [18:40] <rubys> ted volunteers to scribe
- # [18:40] <rubys> maciej is the likely chair
- # [18:40] <rubys> topic: Adjournment
- # [18:40] <Zakim> -Radhika_Roy
- # [18:40] <rubys> rrsagent, publish minutes
- # [18:40] <RRSAgent> I have made the request to generate http://www.w3.org/2012/04/12-html-wg-minutes.html rubys
- # [18:40] <Zakim> -Clarke
- # [18:40] <Zakim> -Janina
- # [18:40] <Zakim> -Julian
- # [18:40] <Zakim> -Mike
- # [18:40] <Zakim> -adrianba
- # [18:40] * Parts: janina (janina@69.140.165.18)
- # [18:40] <Zakim> -KevinStreeter
- # [18:40] <Zakim> -Joseph_Scheuhammer
- # [18:40] <Zakim> -[Microsoft]
- # [18:40] <Zakim> -eliot
- # [18:40] <tantek> in fact, by asking the author to distinguish between different datetime types e.g. "month" etc. at that even finer granularity explicitly, it is *worse* than the simple <time> element which automatically determines datetime granularity by parsing the value!
- # [18:40] <Zakim> -glenn
- # [18:40] * Quits: MFoladare (qw3birc@128.30.52.28) (Quit: Page closed)
- # [18:40] * Quits: Juhani (qw3birc@128.30.52.28) (Quit: Page closed)
- # [18:40] * Parts: KevinStreeter (KevinStree@192.150.10.201)
- # [18:41] * Parts: adrianba (qw3birc@128.30.52.28)
- # [18:41] <tantek> hi cjones
- # [18:41] <Zakim> -Juhahi
- # [18:41] <Zakim> -[Apple]
- # [18:41] <tantek> would be great to increase our common understanding of how to best semantically markup / express datetime information
- # [18:42] <tantek> i'd rather work with you on improving shared consensus than debate on an email list
- # [18:43] <cjones> hi tantek
- # [18:43] <tantek> hello
- # [18:44] <cjones> yes, i'm keen to discuss\explore the implications of both techniques for date\time markup
- # [18:44] <cjones> the update to the proposal documents the points which were raised in the bug report
- # [18:45] <tantek> does what I said above about the type granularity of input datetime types vs the simple <time> element make sense?
- # [18:45] <tantek> as to why <time> is more desirable than data type=(various datetime input types)
- # [18:47] * Quits: hober (ted@17.212.152.28) (Quit: ERC Version 5.3 (IRC client for Emacs))
- # [18:48] * hober2 is now known as hober
- # [18:48] <cjones> i understand your point, it is more verbose than relying on the microsyntax but that dosen't mean it is necessarily better for the reasons i put foreward
- # [18:49] <cjones> authors should decide between date and datetime - in fact they must with either approach
- # [18:49] <tantek> it's not just more verbose
- # [18:49] <tantek> it's prone to error due to excessive precise typing
- # [18:50] * Joins: drublic (drublic@93.132.228.105)
- # [18:50] <tantek> e.g.
- # [18:50] <tantek> <time>2012-04</time> just works
- # [18:50] <tantek> where as with <data> it depends on getting the type exactly right
- # [18:50] <tantek> e.g. it depends on <data type="month">2012-04</data>
- # [18:51] <tantek> web authors will easily forget and put something like
- # [18:51] <tantek> <data type="date">2012-04</data>
- # [18:51] <tantek> or perhaps the data will change over time! (as it does)
- # [18:51] <cjones> yes, but <time> requires the microsyntax to be exactly right
- # [18:52] <tantek> a microsyntax determined from actual usage and previous standards - so there's data for people getting that right
- # [18:52] * Quits: ddorwin (qw3birc@128.30.52.28) (Quit: Page closed)
- # [18:52] <tantek> if someone starts with:
- # [18:52] * Joins: J_Voracek (J_Voracek@70.123.106.75)
- # [18:52] <tantek> <data type="date">2012-01-15</data>
- # [18:52] <tantek> and updates the data later (which happens often) to
- # [18:52] <tantek> <data type="date">2012-05</data>
- # [18:52] <tantek> then they get a failure
- # [18:52] <tantek> w
- # [18:52] <tantek> he
- # [18:52] <tantek> re
- # [18:52] <tantek> whereas
- # [18:53] <tantek> if they start with
- # [18:53] <tantek> <time>2012-01-15</time>
- # [18:53] <tantek> and later the data gets updated
- # [18:53] <tantek> <time>2012-05</time>
- # [18:53] <tantek> it just works
- # [18:54] <tantek> = <time> is more robust (especially over time) for authoring than <data type> for date and time related data types
- # [18:54] <cjones> i wouln't say robust...but it does have the potential to be more automatic
- # [18:55] <J_Voracek>
- # [18:55] <tantek> more robust because changes to the data over time just work
- # [18:55] <tantek> rather than requiring a parallel change to an explicit data type
- # [18:55] <tantek> also
- # [18:55] <cjones> alternatively, one can switch between denominations using the same encoding but alternating the discriminator
- # [18:55] <tantek> any time a system ends up requiring such a "parallel change" - it's a sign of a DRY violation
- # [18:56] <cjones> <data type="year" value="2012-04-12T17:30"/>
- # [18:57] <cjones> <data type="month" value="2012-04-12T17:30"/>
- # [18:57] <tantek> and one has no idea what's actually intended by that by the author
- # [18:57] <cjones> it doesn't require a parallel change - its being defined in a different place
- # [18:57] <tantek> by including the full datetime in the data - do they intend that level of precision? I'd think so
- # [18:57] <tantek> but then the indication of year or month is confusing
- # [18:58] <tantek> much simpler (and shorter = easier to read / verify) to have:
- # [18:58] <tantek> <time>2012</time>
- # [18:58] <tantek> and
- # [18:58] * Quits: J_Voracek (J_Voracek@70.123.106.75) (Ping timeout)
- # [18:58] <tantek> <time>2012-04</time>
- # [18:58] <tantek> I guarantee authors will prefer the <time> alternatives to those <data type> examples you just provided.
- # [18:58] <tantek> simpler, cleaner, more readable, less cruft
- # [18:59] <cjones> what about automated document generation? does it make that easier?
- # [19:00] <tantek> nothing is fully automated
- # [19:00] <tantek> some human codes an HTML template by hand
- # [19:00] * Zakim tantek, you typed too many words without commas; I suspect you forgot to start with 'to ...'
- # [19:00] <cjones> no, it has to be programmed
- # [19:00] <cjones> yes, i write html by hand too
- # [19:00] <tantek> and then some robot randomly criticizes your chatter
- # [19:01] <cjones> :)
- # [19:01] <tantek> even programmers have to write the code that generates the HTML by hand
- # [19:01] * Zakim tantek, you typed too many words without commas; I suspect you forgot to start with 'to ...'
- # [19:01] <cjones> ?!?
- # [19:01] <tantek> lol
- # [19:01] <Zakim> -Sam
- # [19:01] <Zakim> HTML_WG()12:00PM has ended
- # [19:01] <Zakim> Attendees were Mike, glenn, Clarke, Sam, eliot, hober, paulc, Radhika_Roy, KevinStreeter, [Microsoft], adrianba, Julian, Joseph_Scheuhammer, Juhahi, Janina
- # [19:01] * Joins: nesta_ (nesta_@83.58.131.121)
- # [19:02] <[tm]> tantek: Zakim don't like the word 'hand'
- # [19:02] <cjones> how would you expect <time> to be able to handle abstract date\times?
- # [19:03] <cjones> the microsyntax has no room for extension
- # [19:03] <[tm]> if you make it the final word
- # [19:03] <tantek> cjones - in my experience pages/templates are far more often hand coded than completely programmatically generated. especially good/modern sites, separate the application logic / view generation from templates.
- # [19:03] <cjones> but - data markup will be driven my automated machines
- # [19:03] <tantek> cjones - sorry to say but that's already been disproven by the expansion of the <time> element to date! (no pun intended)
- # [19:04] <tantek> the <time> element used to only allow full dates (not months or years)
- # [19:04] <tantek> but I proposed expanding it to allow years and year-months
- # [19:04] <tantek> and the microsyntax was subsequently expanded
- # [19:04] <cjones> but they must have a year or month component
- # [19:04] <tantek> we have experience that shows that the microsyntax *can* be extended
- # [19:04] <cjones> you can not refer to the abstract month of "April"
- # [19:04] <tantek> which disputes your assertion without data or reasoning that "the microsyntax has no room for extension"
- # [19:05] <cjones> yes, they can, but how can ISO 8601 be extended?
- # [19:05] <tantek> how does it need to? where's your use case?
- # [19:05] <tantek> every expansion we made came with use cases
- # [19:05] <tantek> well documented on the wiki
- # [19:05] <cjones> my reasoning is that the only way to extend <time> is adding discrimination bringing to closer and closer to what <data> provides
- # [19:05] <tantek> I'm not really interested in discussing hypothetical extensions to ISO 8601
- # [19:05] <cjones> no
- # [19:06] <tantek> cjones - I don't know what you mean by "adding discrimination"
- # [19:06] <tantek> as noted above
- # [19:06] <cjones> type values
- # [19:06] <tantek> we didn't need to add any discrimination
- # [19:06] <tantek> to already extend <time>
- # [19:06] <cjones> but then values are limited to what the microsyntax can encode
- # [19:06] <tantek> you're not providing any reasoning - you're just reiterating an assertion
- # [19:07] <cjones> i'm trying to highlight a concern
- # [19:07] <tantek> sure, so if we need more, we extend the microsyntax
- # [19:07] <tantek> as we already have
- # [19:07] <cjones> i don't see how thats possible
- # [19:07] <tantek> we've already done it
- # [19:07] <cjones> but not for abstract date\times
- # [19:07] <tantek> so don't bother asserting it's impossible :)
- # [19:07] <tantek> what's the use case?
- # [19:07] <cjones> shrove tuesday
- # [19:07] <tantek> and btw - input type="month" is not abstract
- # [19:07] <tantek> it does mean year-month
- # [19:08] <cjones> no, its not
- # [19:08] <cjones> yes
- # [19:08] <tantek> what is shrove tuesday?
- # [19:08] <cjones> pancake day
- # [19:08] <cjones> chnages every year, or easter
- # [19:09] <tantek> repeating events are beyond the scope of a simple element
- # [19:09] <tantek> especially named ones
- # [19:09] <tantek> if you want to create a named event (like a specific holiday)
- # [19:09] <tantek> you need more structure
- # [19:09] <tantek> I'd suggest looking at hCalendar to start with for that: http://microformats.org/wiki/hcalendar
- # [19:09] <cjones> you are limiting the scope arbitrarily
- # [19:09] <tantek> no I'm offering a solution to your use-case
- # [19:10] <tantek> an existing, working solution
- # [19:10] <tantek> anyway - if you prefer I can write-up the above reasoning and side-by-side comparisons of <time> vs. <data type> syntax in the wiki
- # [19:11] <tantek> I think it will be pretty clear to authors (which all of us are) that the <time> syntax simpler and more robust for all the here-and-now established use-cases
- # [19:11] <cjones> sure, i think it will be very helpful
- # [19:11] <tantek> if you have new use-cases to discuss - that's probably worth a different proposal
- # [19:12] <tantek> It took over a year to document sufficient use-cases well enough for the most recent expansion of the <time> element BTW
- # [19:12] <cjones> i initially had no problem with <time> at all, concerns are raised over the seeming duplication in functionality with <data>
- # [19:12] <tantek> so if you're being serious about your additional use-cases, I'd suggest starting wiki pages for those ASAP
- # [19:12] <tantek> I'll try to help where I can with adding more data for your use-cases
- # [19:13] <tantek> cjones - the "seeming duplication" argument can be made about any phrase element in HTML and <span>
- # [19:13] <tantek> or rather <span class>
- # [19:13] <cjones> but thye share the same use case - data markup
- # [19:13] <cjones> what else is it for?
- # [19:14] * Quits: icaaq (Adium@85.228.175.141) (Ping timeout)
- # [19:14] <tantek> i.e. continuing with the proof by contradiction, you don't need <em> <strong> <kbd> etc. just use <span class>
- # [19:14] <tantek> historically HTML has found value ease of authoring and greater semantic value with a small number of more semantically specific elements
- # [19:14] <tantek> <time> is another such element
- # [19:15] <tantek> as we gather data demonstrating strong use cases for more in the future, we can consider those on a case by case basis
- # [19:15] <cjones> yes, a smaller number - having a distinct element for all data types is not
- # [19:15] <tantek> we don't have a distinct element for all types of textual semantics either
- # [19:15] <cjones> <data> is introduced to resolve the use case
- # [19:15] <tantek> e.g. if you reviewed Chicago Manual of Style - you could come up with dozens of more semantic elements
- # [19:16] <tantek> sure, <data> is a good catchall, just as <span> is
- # [19:16] * Joins: icaaq (Adium@85.228.175.141)
- # [19:16] <tantek> but just as the introduction of <span> didn't mean "drop <em> <strong> <kbd> " etc.
- # [19:16] <cjones> so the question is - does <time> represent a significant benefit to warrent its inclusion
- # [19:16] <tantek> the introduction of <data> doesn't mean drop <time>
- # [19:17] <tantek> cjones - the experience with the microformats community over the past 7 years is that yes, dates and times in particular are problematic to just use a generic element with, and that <time> helps significantly
- # [19:17] <tantek> in otherwords, we're not adding <time> lightly
- # [19:17] <tantek> and in general, I do agree with a fairly conservative approach to adding new elements
- # [19:18] <tantek> for example, <geo> could be another case, but I don't think there is sufficient data/experience to justify it yet.
- # [19:18] <cjones> <location> is a better name
- # [19:18] <cjones> more abstract
- # [19:18] <tantek> maybe we'll gather such data and document it extensively over a few years and thus justify it, but not at the moment.
- # [19:18] <tantek> cjones - maybe - that's part of the question - indeed
- # [19:18] <tantek> <geo> vs. <location>
- # [19:19] <cjones> tbh, my feelings over <time> are not that strong
- # [19:19] <tantek> in practice part of the specific challenge is that geo and location tend to have more substructure to them which tends to imply use of multiple elements
- # [19:19] <cjones> my concerns are over the implications of having <data>
- # [19:19] <tantek> and geo itself has evolved over time
- # [19:20] <tantek> i.e. a few years ago latitude and longitude were the only commonly accepted (in standards) fields for geo
- # [19:20] <tantek> now altitude is commonly accepted
- # [19:20] <tantek> and radius (e.g. of interest) is also gaining acceptance
- # [19:20] <cjones> hmmm....geo should represent a point not an area, no
- # [19:20] <cjones> ?
- # [19:21] <tantek> the radius implies a "fuzziness"
- # [19:21] <cjones> which doesn't sound like such a good idea, imo
- # [19:21] <tantek> perhaps due to privacy disclosure reasons, perhaps due to geolocation sensory data imprecision
- # [19:21] <tantek> for more on that - see the W3C GeoLocation API
- # [19:22] <tantek> http://www.w3.org/TR/geolocation-API/
- # [19:22] <cjones> seems a bit leeky on imprecision
- # [19:22] <tantek> in particular: http://www.w3.org/TR/geolocation-API/#coordinates_interface
- # [19:23] <tantek> they use the label accuracy
- # [19:23] <tantek> but essentially it's a radius of fuzziness
- # [19:23] <cjones> i look at ISO 6709 for an indication as to how this would be introduced to HTML, same as for date\times
- # [19:24] <cjones> it's a valuable case to examine as the quesion of whether there should be a <location> element or <data type="location"> has all the same points
- # [19:24] <cjones> if <location> should be added, where does this stop?
- # [19:25] <cjones> how is location encoded with the tag? <location value="ISO-6709"/>
- # [19:25] <tantek> cjones - it likely doesn't stop - that's part of what we've learned with HTML - that adding specific tags over time has value
- # [19:25] <cjones> the overlap is getting quite large...
- # [19:26] <cjones> sorry, i have to go for now....
- # [19:26] <tantek> I don't have an answer for <location> without first seeing good documentation of real world use-cases
- # [19:26] <tantek> that's the key
- # [19:26] <tantek> with <time> (and its expansion) we have *years* of use-cases documentation
- # [19:26] <cjones> can we continue at a later time? <pun>
- # [19:26] <tantek> and took quite a long time to design/create/introduce the element
- # [19:26] <tantek> I expect similar scientific thoroughness for any geo or location or anything else
- # [19:26] <cjones> really?
- # [19:27] <tantek> so I'm ok with that slow pace of adding incremental specific elements
- # [19:27] <tantek> and until then, we can use <data> (without an explicit type) to just gather data (no pun intended) on what kinds of things people publish
- # [19:27] <tantek> we could even hold a vote each year at TPAC
- # [19:28] <tantek> HTML's Top <data>
- # [19:28] <tantek> ;)
- # [19:28] <tantek> and the winner would get its own specific element
- # [19:28] <tantek> though at the current pace, perhaps one every 2-3 years
- # [19:28] <tantek> rather than one every year
- # [19:29] <tantek> cjones - will chat later - I'll try to be on here again, or if you don't find me here, you can probably also find me on #whatwg on Freenode.
- # [19:29] <tantek> thanks for the discussion. I think we're increasing our mutual understanding even if we haven't quite figured out or come to a complete consensus yet.
- # [19:35] * Joins: dveditz (dveditz@63.245.220.240)
- # [19:38] * Quits: myakura (myakura@119.243.157.97) (Client exited)
- # [19:44] * Joins: mjs (mjs@17.245.89.218)
- # [19:46] * Joins: dsinger (dsinger@131.107.32.25)
- # [19:56] <tantek> btw re: f2f meeting and wiki
- # [19:56] <tantek> cc: plh MikeSmith
- # [19:57] <tantek> about a month ago I started some wiki edits to the HTMLWG wiki home page http://www.w3.org/html/wg/wiki/Main_Page since I didn't see much discoverable about f2f meetings etc.
- # [19:58] <tantek> all parallel to what WebApps' wiki already has
- # [19:58] <tantek> e.g. I added meetings section: http://www.w3.org/html/wg/wiki/Main_Page#Meetings
- # [19:59] <tantek> with link to a f2f page: http://www.w3.org/html/wg/wiki/F2F
- # [19:59] * Joins: anne (annevk@94.209.230.36)
- # [20:00] <tantek> where I linked to one old f2f wiki page
- # [20:00] <tantek> and created a new wiki page for the upcoming meeting
- # [20:00] <tantek> http://www.w3.org/html/wg/wiki/2012-05-f2f
- # [20:01] <tantek> subsequently from today's call I saw that plh had created a new page: http://www.w3.org/html/wg/wiki/May2012Agenda
- # [20:01] <tantek> so I linked to that one
- # [20:05] <tantek> I have no particular preference for the HTMLWG wiki page taxonomy - I was merely creating *something* in absence of anything - I'll go along with whatever hierarchy plh MikeSmith or the chairs choose to go with.
- # [20:05] <tantek> let me know how I can help. thanks.
- # [20:09] * Quits: Clarke (qw3birc@128.30.52.28) (Quit: Page closed)
- # [20:11] * Quits: ArtB (abarsto@192.100.120.41) (Quit: Leaving.)
- # [20:12] * Joins: abarsto (abarsto@192.100.120.41)
- # [20:12] * abarsto is now known as ArtB
- # [20:14] * plh back
- # [20:15] <plh> I didn't have a hierarchy in mind to be honest
- # [20:15] <plh> just created a page since it was needed
- # [20:19] <tantek> happy to help evolve it however you wish plh :)
- # [20:19] <plh> actually, I don't have a wish :)
- # [20:19] <tantek> of course my more global preference is that we switch in the next WG charter to using the W3C wiki (rather than a wg-specific wiki) but that's just me and my anti-namespace ways ;)
- # [20:20] <tantek> (also tired of logging into several different W3C wikis)
- # [20:20] <plh> yeah, I don't disagree with that
- # [20:29] * Joins: mattkelly (mattwkelly@173.252.71.3)
- # [20:31] * Joins: myakura (myakura@119.243.157.97)
- # [20:33] <tantek> plh, I proposed that at the last f2f in Santa Clara, and I believe the chairs said that that was something to propose for the next charter
- # [20:33] <tantek> (that the group use the W3C wiki rather than its own)
- # [20:33] <tantek> so I'm waiting patiently for charter renewal
- # [20:34] <tantek> would appreciate if you could help with making that change to the proposed renewal charter
- # [20:34] <tantek> (assuming there are no objections)
- # [20:35] <plh> I'm ok with doing the change
- # [20:35] <tantek> thanks!
- # [20:35] <plh> having said that, it's not we have to wait for a new charter for that imo
- # [20:36] <plh> the charter doesn't restrict us to one wiki
- # [20:36] <tantek> sure, that was simply what the chairs suggested to me - so I was going on their guidance
- # [20:37] <tantek> I'm ok with switching over ASAP to using the W3C wiki - but it would take more than one person to make it stick
- # [20:37] * Quits: rniwa (rniwa@70.89.66.218) (Quit: rniwa)
- # [20:37] <tantek> I suppose in practice if those of us in the HTMLWG decided as a whole to just start using/moving content to the W3C wiki, people would use it
- # [20:37] <plh> correct
- # [20:38] <plh> I don't know if there is a way to setup redirect in our wiki
- # [20:38] <plh> that would help as well
- # [20:40] * Quits: anne (annevk@94.209.230.36) (Quit: anne)
- # [20:46] * Quits: karl (karlcow@128.30.54.58) (Quit: :tiuQ tiuq sah woclrak)
- # [20:48] * Quits: dveditz (dveditz@63.245.220.240) (Quit: dveditz)
- # [20:53] * Quits: paulc (qw3birc@128.30.52.28) (Quit: Page closed)
- # [20:54] * Joins: dveditz (dveditz@63.245.220.240)
- # [21:02] * Quits: dsinger (dsinger@131.107.32.25) (Ping timeout)
- # [21:06] * Zakim excuses himself; his presence no longer seems to be needed
- # [21:06] * Parts: Zakim (rrs-bridgg@128.30.52.169)
- # [21:23] * Joins: rniwa (rniwa@72.14.229.81)
- # [21:26] * Quits: myakura (myakura@119.243.157.97) (Client exited)
- # [21:48] * Joins: anne (annevk@82.161.179.17)
- # [21:55] * Quits: mjs (mjs@17.245.89.218) (Quit: mjs)
- # [21:56] * Joins: mjs (mjs@17.245.89.218)
- # [22:01] <cjones> tantek: hi, i'm back again but it's getting late so might be best to continue the discussions tomorrow\later
- # [22:03] <cjones> i agree that we seem to be achieving greater understanding, which is the goal so good progress so far
- # [22:04] <cjones> i'll stay online here and #whatwg (kalc4), afternoons GMT is good for me
- # [22:11] * Quits: mattkelly (mattwkelly@173.252.71.3) (Quit: mattkelly)
- # [22:11] * Joins: mattkelly (mattwkelly@173.252.71.3)
- # [22:21] * Parts: rubys (rubys@98.27.59.167)
- # [23:08] * Quits: davidb (davidb@65.93.94.10) (Quit: blast off!)
- # [23:26] * miketaylr is now known as miketaylr|
- # [23:26] * miketaylr| is now known as miketaylr||
- # [23:56] * Quits: plh (plh@128.30.52.28) (Quit: always accept cookies)
- # [23:57] * Quits: eliot (eliot@131.107.0.110) (Ping timeout)
- # Session Close: Fri Apr 13 00:00:00 2012
The end :)