Minutes, telcon 0/04/2011

http://www.w3.org/2011/05/04-webfonts-minutes.html

and the text version below:

                               - DRAFT -

                 WebFonts Working Group Teleconference

04 May 2011

   See also: [2]IRC log

      [2] http://www.w3.org/2011/05/04-webfonts-irc

Attendees

   Present
   Regrets
          John, Hudson

   Chair
          SV_MEETING_CHAIR

   Scribe
          cslye

Contents

     * [3]Topics
     * [4]Summary of Action Items
     _________________________________________________________

   <trackbot> Date: 04 May 2011

   <jfkthame> Zakim: aabb is jfkthame

   <jdaggett> i'm on the phone but not sure which of these numbers
   skype matches...

   <erik> one of the skype numbers is erik

   <jdaggett> i'd like to discuss the current wording in the css3 fonts
   spec related to SOR

   <jdaggett>
   [5]http://dev.w3.org/csswg/css3-fonts/#same-origin-restriction

      [5] http://dev.w3.org/csswg/css3-fonts/#same-origin-restriction

   Discussing present wording of origin checking mechanism. Håkon
   inquiring.

   Vlad explaining current wording, approved by Apple.

   [6]http://lists.w3.org/Archives/Public/public-webfonts-wg/2011May/00
   02.html

      [6] http://lists.w3.org/Archives/Public/public-webfonts-wg/2011May/0002.html

   jdaggett: I just updated the CSS Fonts spec. Webfonts group should
   approve.

   [7]http://dev.w3.org/csswg/css3-fonts/

      [7] http://dev.w3.org/csswg/css3-fonts/

   jdaggett: Apple is comfortable with link-specific origin checking,
   not type-specific?

   Vlad: Yes.

   <jdaggett>
   [8]http://dev.w3.org/csswg/css3-fonts/#same-origin-restriction

      [8] http://dev.w3.org/csswg/css3-fonts/#same-origin-restriction

   jdaggett: Reviewing Section 4.8, Same-origin restriction for fonts.

   sergeym: Do origin checking policies need to be made explicit for
   WOFF loaded by different mechanisms?

   Vlad: WOFF is designed to be loaded by web mechanisms (i.e.
   @font-face) so should be okay.

   jdaggett: This new policy makes some existing UAs noncompliant.
   ... Apple should explicitly approve the current wording.

   Håkon: I think some parts of the community will have a problem with
   the current wording.

   jdaggett: I will post about this on the www-style list.

   Disposition of comments:
   [9]http://dev.w3.org/webfonts/WOFF/DoC/issues-lc-2010.html

      [9] http://dev.w3.org/webfonts/WOFF/DoC/issues-lc-2010.html

   <tal> [10]http://www.w3.org/Fonts/WG/track/actions/open

     [10] http://www.w3.org/Fonts/WG/track/actions/open

   [11]http://www.w3.org/Fonts/WG/track/actions/open

     [11] http://www.w3.org/Fonts/WG/track/actions/open

   Open action items...

   <Vlad> action 87?

   <trackbot> Sorry, bad ACTION syntax

   <jfkthame> action-87?

   <trackbot> ACTION-87 -- Jonathan Kew to add updated at-risk wording
   to spec -- due 2011-05-04 -- OPEN

   <trackbot> [12]http://www.w3.org/Fonts/WG/track/actions/87

     [12] http://www.w3.org/Fonts/WG/track/actions/87

   <Vlad> close action-87

   <trackbot> ACTION-87 Add updated at-risk wording to spec closed

   <Vlad> action-88?

   <trackbot> ACTION-88 -- Jonathan Kew to add wording on last call
   issue 34 -- due 2011-05-04 -- OPEN

   <trackbot> [13]http://www.w3.org/Fonts/WG/track/actions/88

     [13] http://www.w3.org/Fonts/WG/track/actions/88

   <Vlad> close action-88

   <trackbot> ACTION-88 Add wording on last call issue 34 closed

   jfkthame: Need to discuss 62 and 81 with Chris L.

   Vlad: We'll keep remain items open for now.
   ... Asking about next F2F.
   ... Do we want to meet at TypeCon in New Orleans in July?

   jdaggett: What topics would be discussed?

   Vlad: Finalizing test suite.
   ... Will send email to list. We need to decide specific plans.
   ... No call for next two weeks.

   Next call May 25.

Summary of Action Items

   [End of minutes]