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

RE: FW: EOT-Lite File Format

From: Richard Fink <rfink@readableweb.com>
Date: Fri, 31 Jul 2009 21:06:36 -0400
To: <robert@ocallahan.org>, <info@ascenderfonts.com>
Cc: "'www-font'" <www-font@w3.org>
Message-ID: <007701ca1244$5290fc30$f7b2f490$@com>
Friday, July 31, 2009 Robert Callahan Robert@ocallahan.org:

 

>How do you expect authors to comply with your EULA requirement for access control, for IE<=8 users?

 

Rob, 

 

I didn’t interpret Ascender’s response to your questions about their EULAS as *requiring* access control.

According to Bill Davis’s previous post, the language in their EULA is, at present:

“reasonably restricts access to Font Software for use in any way by web pages not originating from the CUSTOMER Web Server (For example; by using referrer checking to prevent hotlinking or deeplinking).”

Well, what’s reasonable?

Once user agents that support EOTL are out in the market enforcing same-origin restrictions, it seems quite reasonable for me to do nothing at all at the server level except let those browsers do their thing and *not* specifically enable linking in the htaccess file.

And I think this would be a more effective example than referrer checking.

Lawyers! 

 

Regards,

 

rich

 

 

From: www-font-request@w3.org [mailto:www-font-request@w3.org] On Behalf Of Robert O'Callahan
Sent: Friday, July 31, 2009 6:49 PM
To: info@ascenderfonts.com
Cc: www-font
Subject: Re: FW: EOT-Lite File Format

 

On Sat, Aug 1, 2009 at 10:35 AM, Bill Davis <info@ascenderfonts.com> wrote:

Robert, first of all, we can only speak for Ascender. Every other type designer & foundry can and will have their own EULA.

But I don't understand why you are bringing up rootstrings. They are not part of the EOT Lite specification.

I think you are overly complicating things. Or maybe I am missing your point?


 

How do you expect authors to comply with your EULA requirement for access control, for IE<=8 users?

I see only two realistic options:
1) Referer checking
2) Rootstrings in the font

Referer checking sucks. Rootstrings suck less.

Rob
-- 
"He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]
Received on Saturday, 1 August 2009 01:07:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 11 June 2011 00:14:03 GMT