14:02:18 RRSAgent has joined #webfonts 14:02:18 logging to http://www.w3.org/2010/06/16-webfonts-irc 14:02:41 rrsagent, bookmark 14:02:41 See http://www.w3.org/2010/06/16-webfonts-irc#T14-02-41 14:03:01 tiro_j has joined #webfonts 14:03:53 trying to connect 14:04:11 Zakim has joined #webfonts 14:04:19 Zakim, who is on the phone? 14:04:27 sorry, jdaggett, I don't know what conference this is 14:04:37 On IRC I see tiro_j, RRSAgent, erik_, sergeym, jfkthame, jdaggett, cslye, tal, Vlad, sylvaing, trackbot 14:06:00 Zakim, list 14:06:00 I see Team_W3M()8:00AM, IA_Fonts()10:00AM, UW_DAP()10:00AM active 14:06:01 also scheduled at this time are IA_MFWG()3:00AM, SW_CG()9:00AM, WAI_(AGE TF)9:30AM, Team_(xhtml)13:45Z 14:06:27 Zakim, this conference is IA_Fonts 14:06:27 ok, Vlad; that matches IA_Fonts()10:00AM 14:06:44 Zakim, who is on the phone 14:06:44 I don't understand 'who is on the phone', Vlad 14:07:10 Zakim, who is here? 14:07:10 On the phone I see +1.781.970.aaaa, +1.443.895.aabb, [IPcaller], +1.510.816.aacc, +1.425.882.aadd, +1.250.668.aaee, +1.206.324.aaff 14:07:12 On IRC I see tiro_j, RRSAgent, erik_, sergeym, jfkthame, jdaggett, cslye, tal, Vlad, sylvaing, trackbot 14:07:35 zakim, [IPcaller] is jdaggett 14:07:36 +jdaggett; got it 14:07:36 still wrestling with phone, it hangs up after entering the access code. 14:09:22 it seems like it's just not hearing me enter the code 14:09:27 to attach your phone number: http://www.w3.org/1998/12/bridge/info/name.php3 14:09:29 it asks again, and then just hangs up 14:09:37 csyle: using the format "zxxx, xxx is c 14:10:09 cslye: you're the only 510 number, right? 14:10:18 That's correct. 14:10:28 So, let me try this... 14:10:47 Zakim, aacc is cslye 14:10:47 +cslye; got it 14:11:04 zakim, who is noisy? 14:11:15 jdaggett, listening for 10 seconds I heard sound from the following: +1.781.970.aaaa (80%) 14:11:29 unable to connect - same here. 14:11:44 star / zero doesn't go anywhere either. 14:13:01 trackbot-ng, start telcon 14:13:03 RRSAgent, make logs world 14:13:05 Zakim, this will be 3668 14:13:05 ok, trackbot; I see IA_Fonts()10:00AM scheduled to start 13 minutes ago 14:13:06 Meeting: WebFonts Working Group Teleconference 14:13:06 Date: 16 June 2010 14:14:38 Vlad: Should we discuss origin restrictions or metadata first? 14:15:55 http://lists.w3.org/Archives/Public/public-webfonts-wg/2010Jun/0092.html 14:17:28 ChrisL has joined #webfonts 14:18:08 despite repeated tries, I'm unable to connect 14:18:20 rrsagent, here 14:18:20 See http://www.w3.org/2010/06/16-webfonts-irc#T14-18-20 14:18:54 also unable to connect - i can watch the irc channel but no phone connection 14:19:57 1) there is no security benefit here. 14:19:57 I can connect via the US number. France number seems unable to accept touch tones 14:20:16 trying 14:20:20 2) same-origin is not defined in HTML5 but in CORS. CORS depends on HTML5 for the definition of origin and origin matching 14:20:54 I connected to the Boston number with no problem, fwiw. 14:22:04 not opposed 14:22:07 I could connect via the uS number 14:22:20 howcome has joined #webfonts 14:23:27 Anne (CORS editor) opposes using CORS for WOFF 14:24:04 Howcome: is same-origin for WOFF or for other formats? 14:24:07 Font vendors do not want to license raw fonts so that shouldn't be an issue 14:24:18 at least for some time 14:24:28 I think the point is that WOFF is a "protected" format and deserves the mild protection it gets from same-origin, whereas "raw" fonts don't need it. 14:24:56 howcome, you mentioned a range of opinions in Opera - what are the others? 14:25:50 howcome: others say its good, for example to save bandwidth 14:26:30 When we refer to the "security" argument, we mean attacks and such, as opposed to theft? 14:26:38 cslye: yes 14:29:37 notes that TypeKit et al. rely on cross domain font access so the licensing benefit depends on who the vendor is 14:32:49 typekit uses data urls 14:33:02 i.e. they are not affected by this 14:33:15 jdaggett: for Firefox, yes 14:33:30 I think Typekit delivers EOT files for IE, though. 14:33:31 this is the license FSI links to in their current WOFF releases: http://www.fontfont.com/eula/license_webfonts_v_1_0.html 14:33:37 jdaggett: there still are other browsers :) and other font providers who link across domain e.g. ascender 14:33:46 2.3. Font Software File Protection. You must ensure, by applying reasonable state-of-the-art measures, that other websites cannot access the Font Software for display (e. g. by preventing hotlinking and blocking direct access to the Font Software via .htaccess or other web server configurations). 14:33:53 http://www.fontshop.com/help/licenses/fontfont/ 14:33:57 sure 14:35:14 sg: if browsers do this, font vendors are willing in return to llosen their licenses 14:35:40 Not just loosen their license, but would be more inclined to offer web font licenses in the first place. 14:36:16 erik: makes it much easier for us certainly 14:36:38 (that's John, not Erik0 14:36:52 ... current licensing is in flux and depends on how WOFF spec ends up 14:37:12 s/John/erik/ 14:37:41 installing adequate technical protection measures that restrict the use and/or access to the Font Software and/or Derivative Works, for instance by binding an EOT font to the Licensed Websites, utilizing JavaScript or access control mechanism for cross-origin resource sharing and/or protecting a sIFR Flash file against use on other websites than Licensed Websites by restricting domain access only to Licensed Websites. 14:38:18 ack syl 14:38:30 zakim, unmute sylvaing 14:38:30 sorry, ChrisL, I don't know what conference this is 14:38:37 zakim, this is font 14:38:37 ok, ChrisL; that matches IA_Fonts()10:00AM 14:38:40 zakim, unmute sylvaing 14:38:40 sorry, ChrisL, I do not know which phone connection belongs to sylvaing 14:38:43 + +1.206.324.aaii 14:41:09 :) 14:41:29 vlad: monotype license encourages woff usage 14:42:13 sylvaing: generaly positive on same-origin 14:42:26 howcome: abstain 14:43:05 Does anyone explicitly object to requiring access control? 14:43:32 resolution: same-origin restriction is mandatory for WOFF. modulo editorial changes discussed on the list 14:44:06 topic: extension mechanisms 14:44:19 topic: f2f 14:44:26 I agree. 14:44:44 vlad: majority favour a f2f at typecon in LA 14:45:43 chris: will try, but CSS in Oslo next day, also affects howcome, jdagett and sylvaing 14:46:04 My concern with ATypI is that it's closer to TPAC. (Also more difficult for me personally.) 14:46:05 vlad: dublin atypi 14:46:33 john: can't do dublin 14:46:43 cslye: cant do dublin 14:46:48 (sep 9-12) 14:47:07 will be at TPAC 14:47:08 howcome: do we need a physical f2f? 14:47:12 http://atypi.org/03_Dublin 14:47:16 vlad: seen as desirable 14:47:32 http://www.typecon.com/ 14:47:35 It's possible for me -- but travel budget makes it difficult. 14:48:02 sylvaing: is there enough of an agenda to justify travel? 14:48:14 if people find themselves in the same spot, they can certainly meet 14:48:27 vlad: colocating would capitalize on existing travel 14:48:56 chris: can do call-in using a bridge 14:50:07 cslye: travel restrictions - good to have the WG there. How can we entice people? 14:50:37 vlad: everyone plese restate their travel plans including existing travel 14:51:00 would love to come to typecon but with another meeting directly following it, that's tricky 14:51:33 same as jdaggett even though it's fewer miles for me 14:52:39 chris: some of tpac will be spent in liaison 14:52:52 I will be at TypeCon, but not at ATypI, posibly at TPAC 14:53:04 vlad: we asked for no overlap with css, can we reschedule? 14:53:12 overlap with CSS would be quite unhelpful for 4+ of us 14:53:38 action: chris ask tpac organisers to reschedule webfonts to thur/fri at tpac 14:53:38 Created ACTION-9 - Ask tpac organisers to reschedule webfonts to thur/fri at tpac [on Chris Lilley - due 2010-06-23]. 14:54:30 topic: metadata extensions 14:55:09 vlad: from discussions so far, etadata as specified in draft seems near consensus. number and type of elements is ok for font vendors 14:55:22 ... implementors said it was ok even though optional 14:55:43 ... so we can state consensus on the existing set of standard metadata elements 14:55:58 ... so then we can discuss extension mechanism only 14:56:09 (no objections) 14:56:22 howcome: not sure 14:56:46 howcome: want to see a complete proposal 14:57:14 vlad: can modify for good reason after fpwd 14:57:53 doesn't know either but acknowledges that what we have is already being used. that's important 14:58:03 vlad: simple key-value is proposed for extensions 14:59:34 vlad: localisation is important, tried to be impartial in summary, hope that was clear. but speaking for monotype, opinion is that the solution form jonathan kew was the best one 15:00:11 ... sergei commented to say it was simple to implement, one pass 15:00:25 sergeym: yes 15:00:57 vlad: duplication should not cause significant size increase as it compresses well 15:01:41 howcome: difficult to discuss now, propose to delay all metadayta out of 1.0 15:02:03 vlad: including the standard metadata? 15:02:05 Wouldn't that just create a lot of ad hoc metadata in shipping WOFFs? 15:02:24 tal: strongly object, that is the basis we got people to sign on, removing it would be insulting 15:02:38 vlad: so please respond on email 15:02:43 we could keep what we have and postpone extensibility. I think this is what Hakon is saying ? 15:03:34 howcome: yes. just t eh extensibility 15:03:43 sylvaing: document what is used now 15:04:08 ... extensibility comes later 15:04:24 ... now one is using extensibility right now 15:04:46 ... so drive to LC, CR. Extend once we have actual requirements 15:05:15 howcome: ok with that 15:06:33 sylvaing: do we want to delay for uncertain extensibility? 15:06:50 vlad: if its in fpwd theyn we get feedback and can take it out if needed 15:06:54 If we want to get use cases for extended metadata for 1.0, we might get that out of TypeCon and ATypI conversations. 15:07:06 sylvaing: bar metadata, what other issues do we have? 15:07:10 vblad: not many 15:07:25 howcome: so lets get fpwd soon 15:08:03 vlad: want to have a solution that many of us can live with. if its in the fpwd we can ask for comments. if its not in the draft we can't get comments 15:08:11 sylvaing: ok lets get it out there 15:08:37 sergeym: font vendors unlikely to want to remove the extensibility 15:09:18 cslye; any objection to put it in current draft? 15:09:31 sylvaing: current draft represents what is out there 15:09:52 Vlad: better to have an extension proposal for people to discuss 15:11:03 john: put extensibility as a separate item? 15:11:51 chris: putting in extensibility and deleting later if needed is better from a patent policy point of view 15:12:15 vlad: lets use next couple of weeks to try to get agreement here. only half a page or so anyway 15:13:13 history has been made... 15:13:32 howcome: i am willing to let microsoft cast my vote here 15:14:07 resolved: fpwd in a couple of weeks with whatever we have consensus on 15:14:17 rrsagent, make minutes 15:14:17 I have made the request to generate http://www.w3.org/2010/06/16-webfonts-minutes.html ChrisL 15:14:39 -jdaggett 15:14:40 - +1.250.668.aaee 15:14:40 -cslye 15:14:41 - +31.70.360.aahh 15:14:42 -ChrisL 15:14:43 - +1.443.895.aabb 15:14:43 - +47.21.65.aagg 15:14:44 - +1.206.324.aaii 15:14:46 -??P22 15:14:48 - +1.781.970.aaaa 15:14:50 - +1.425.882.aadd 15:14:52 IA_Fonts()10:00AM has ended 15:14:54 Attendees were +1.781.970.aaaa, +1.443.895.aabb, +1.510.816.aacc, +1.425.882.aadd, +1.250.668.aaee, +1.206.324.aaff, jdaggett, cslye, +47.21.65.aagg, ChrisL, +31.70.360.aahh, 15:14:57 ... +1.206.324.aaii 15:15:04 chair: vlad 15:15:07 tal has left #webfonts 15:15:08 scribe: chris 15:15:17 zakim, list attendees 15:15:17 sorry, ChrisL, I don't know what conference this is 15:15:22 rrsagent, make minutes 15:15:22 I have made the request to generate http://www.w3.org/2010/06/16-webfonts-minutes.html ChrisL 15:43:59 jfkthame has left #webfonts 16:09:25 sylvaing has left #webfonts 17:34:06 Zakim has left #webfonts 18:08:22 jfkthame has joined #webfonts