W3C home > Mailing lists > Public > public-webfonts-wg@w3.org > January 2011

WOFF without SOR?

From: Håkon Wium Lie <howcome@opera.com>
Date: Wed, 26 Jan 2011 13:39:56 +0100
Message-ID: <19776.5660.325037.37441@gargle.gargle.HOWL>
To: John Hudson <tiro@tiro.com>
Cc: info@ascenderfonts.com, public-webfonts-wg@w3.org
John Hudson wrote:

 > Bill Davis wrote:
 > > http://dev.w3.org/webfonts/WOFF/spec/ states: "When using such fonts, user
 > > agents MUST implement a 'same-origin restriction' on the downloading of WOFF
 > > files using the same-origin matching algorithm described in the HTML5
 > > specification..."
 > > What part of "MUST" does Opera not understand?
 > I presume we have Anne van Kesteren to thank for this. At the 
 > face-to-face meeting in Lyon

John, Bill, I don't your rethoric advances your case. Neither does
singling our people or companies.

The last time I checked, Chrome, Safari and Opera didn't support SOR
for WOFF files. 

The WOFF submission didn't include SOR, and adding it to the WD has
been controversial.

Personally, I can see that it makes sense; it prevents people from
leeching bandwidth off innocent users. I don't think it's a crucial
part of the "protection" that WOFF provides, but I understand if
others disagree.

Given that the WD describes the "WOFF File Format 1.0", I can
understand why people argue that the spec shouldn't make demands at
the HTTP level. Architecturally, it seems clear that the WOFF format
is orthogonal to SOR. I therefore suggest we split the SOR part out
from the WOFF WD and place it in a separate draft. 

For the record, this is consistant with my position, as expressed


              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome
Received on Wednesday, 26 January 2011 12:40:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:15 UTC