W3C home > Mailing lists > Public > www-font@w3.org > July to September 2009

cutting to the chase

From: Thomas Lord <lord@emf.net>
Date: Sun, 02 Aug 2009 17:20:34 -0700
To: www-font <www-font@w3.org>
Message-Id: <1249258834.6784.64.camel@dell-desktop.example.com>
These conclusions from the discussion seem
correct to me:

1) Consensus on a wrapper format is not
forthcoming anytime soon.  Implementation
experience with wrapper formats in UAs is
missing and not expected in any serious form
anytime soon.

2) Consensus on EOT-classic (with or without
rootstring enforcement, MTX, and so forth)
is unlikely to ever be reached.

3) Consensus on EOTL variants is unlikely
to ever be reached.

4) Rough consensus on TTF/OTF exists and
plenty of working code exists.  If this 
were to appear as a requirement in a draft
Recommendation, formal Objections would likely
be raised by some font vendors and/or Microsoft.
It is unlikely that these Objections could be
resolved by the WG and thus they would be taken
up by the Director in consultation with the AB
and TAG.

5) Rough consensus on same-origin+CORS restrictions
on font linking is achievable.

The sanctification of a Recommendation that requires
TTF/OTF, most likely with same-origin+CORS, would 
encourage the use of fonts on the web.  It would
contribute to the breadth and depth of conforming
web content.  It would likely stimulate the development
and release of fonts for web use.

Such sanctification risks creating a schism in 
which Microsoft refuses to ever conform.  Perhaps
such a schism harms W3C's overall efforts or perhaps

Withholding such sanctification risks creating a 
schism in which Microsoft plays an unduly dominant
role in determining the content of Recommendations.

The formal Objection process, in which the Director
hears the claims of those not agreeing to the consensus
view, exists to address such difficult situations.


A font WG should be formed.

It should draft a Recommendation requiring TTF/OTF

It should consider whether or not to require 
same-origin+CORS restrictions on font linking.

It should forward the resulting draft Recommendation to
the Director, along with such unresolved formal Objections
as Microsoft and some font vendors may wish to register.

Received on Monday, 3 August 2009 00:21:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:01:41 UTC