W3C

- DRAFT -

WebFonts Working Group Teleconference

06 Oct 2010

See also: IRC log

Attendees

Present
Regrets
Chair
SV_MEETING_CHAIR
Scribe
erik

Contents


<Vlad> trackbot start telcon

<Vlad> trackbot, start telcon

<trackbot> Date: 06 October 2010

scribe erik

on the phone, Vlad, Håkon, Erik

Håkon; the normative part of the spec should mention that the notes are non-normative

discussion on normative / non-normative and other W3 specs

Vlad: mixing up normative / non-normative is messy
... not enough participants to decide anythign.

Håkon: can't accept notes to become normative (did I get that right?)

Håkon: in CSS "notes are informative, not normative"

Vlad: concern that the spec becomes fragmented
... if notes are non-normative, can the language be a bit more clear cut?

Håkon: best to avoid MUST in non-normative

using normative language in non-normative notes can open arguments and raise confusion

Vlad, Håkon, I lost connection and can't follow the discussion

Dialing in, but zakim does not answer.

gentlemen?

No answer when I dial in. Can I be excused of my scribe duties?

<howcome> The WOFF-packaged data will typically be decoded to its original sfnt format for use by existing font-rendering APIs that expect OpenType font data, but such a decoded font should not be exposed to other documents or applications.

That sounds reasonable.

<howcome> The WOFF-packaged data will typically be decoded to its original sfnt format for use by existing font-rendering APIs that expect OpenType font data, but such a decoded font must not be exposed to other documents or applications.

<howcome> The WOFF-packaged data will typically be decoded to its original sfnt format for use by existing font-rendering APIs that expect OpenType font data, but such a decoded font must not be made availabl to other documents or applications.

<Vlad> Agreement to add a normative sentence that says that notes are non-normative

<Vlad> The notes should be coherent with the normative text and should not be ambiguous

<Vlad> The notes should help the implementors and users to undertstand the meaning of the normative text, and should not make any confcliting or ambiguous statements

<Vlad> Agreement to rewrite the first note to make it coherent with the normative text

<Vlad> We will continue this discussion on the email list

<Vlad> The call is adjourn, we will continue the discussions on the email list

<Vlad> Please submit your proposed agenda items for the F2F in November

I have to run.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2010/10/06 15:02:24 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/man/mean/
Succeeded: s/implementers/implementors and users/
No ScribeNick specified.  Guessing ScribeNick: erik
Inferring Scribes: erik

WARNING: No "Topic:" lines found.


WARNING: No "Present: ... " found!
Possibly Present: Vlad howcome jdaggett joined tal trackbot webfonts
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 06 Oct 2010
Guessing minutes URL: http://www.w3.org/2010/10/06-webfonts-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]