The mission of the EOT Working Group, part of the EOT Activity, is to develop the EOT (Embedded OpenType) specification. EOT is a wrapper format for OpenType fonts that allows the latter to be embedded in Web documents.
End date | [September 2009] |
---|---|
Confidentiality | Member-confidential |
Initial Chairs | [] |
Initial Team Contacts | [Bert Bos (20%)] |
Meeting Schedule | [weekly teleconferences, two face-to-face meetings] |
The goal of EOT (and of the working group) is to allow OpenType fonts to be embedded in Web documents, in particular (but not exclusively) in documents that can refer to fonts via W3C's Web Fonts technology. Currently, Web Fonts is part of CSS and SVG.
Embedded in this case means that there is a bi-directional link between the document and the font: The Web Fonts technology defines how to link from a document to a font and EOT defines how to link from an Open Type font to a document.
The basis for the EOT specification will be the EOT submission by Microsoft (with contributions by Monotype). It is expected, but not a requirement, that the EOT specification will remain close to the EOT submission, which has been in use by Microsoft for several years.
The working group aims to make a W3C Recommendation for EOT, which also requires developing a test suite. The Recommendation should be implemented on at least two different platforms.
The group may also organize one or more workshops, to gather feedback, to coordinate implementations, etc.
This charter was approved by the Director on [September XX] and is valid for the period [September 2008 until September 2009].
The expected deliverables are:
The group may also need to register an Internet Media Type for EOT.
The working group will review the Web Fonts specification (which is expected to be developed by the CSS and/or SVG working groups).
Specification transition estimates and other milestones
Specification | FPWD | LC | CR | Test | PR | Rec |
---|---|---|---|---|---|---|
EOT | September 2008 | April 2009 | May 2009 | July 2009 | August 2009 | August 2009 |
The group will document significant changes from this initial schedule on the group home page.
The first face-to-face meeting will be held at the TPAC, 20–24 October 2008.
Effective participation to the EOT Working Group is expected to consume 0.2 fte (one work day per week) for each participant; 0.4 fte (two days per week) for editors.
The working group may apply the Good Standing requirements of the W3C Process.
The initial chair and team contact [is/are…].
This group primarily conducts its work on the public mailing list <www-eot@w3.org> and may also use the member-only mailing list <w3c-eot@w3.org>.
Information about the group (deliverables, participants, face-to-face meetings, teleconferences, etc.) is available from the EOT Working Group home page.
The group holds weekly, one-hour teleconferences and two or three face-to-face meetings. The group may meet more or less frequently as needed.
As explained in the Process Document (section 3.3), this group will seek to make decisions by consensus. When the Chair puts a question and observes dissent, after due consideration of different opinions, the Chair should record a decision (possibly after a formal vote) and any objections, and move on.
This charter is written in accordance with section 3.4, Votes of the W3C Process Document and includes no voting procedures beyond what the Process Document requires.
This Working Group operates under the W3C Patent Policy (5 February 2004 version). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis.
For more information about disclosure obligations for this group, please see the W3C Patent Policy Implementation.
This charter for the EOT Working Group has been created according to section 6.2 of the Process Document. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process takes precedence.
Bert BosCopyright © 2008 W3C ® (MIT, ERCIM, Keio), All Rights Reserved.
Created: 5 May 2008
Modified: $Date: 2008/08/12 12:14:49 $