- From: Thomas Lord <lord@emf.net>
- Date: Thu, 30 Jul 2009 19:48:09 -0700
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: John Hudson <tiro@tiro.com>, John Daggett <jdaggett@mozilla.com>, www-font <www-font@w3.org>
On Thu, 2009-07-30 at 21:16 -0500, Tab Atkins Jr. wrote: > On Thu, Jul 30, 2009 at 9:07 PM, John Hudson<tiro@tiro.com> wrote: > > Thomas Lord wrote: > > > >>> A DRM-enabling mechanism is something that restricts use of a font by a > >>> user agent. > > > >> You have a usable font file but the standard > >> says "you MUST NOT use it" -- yes, that is DRM. > > > > No, that is not DRM. > > > > DRM is a *business model* made possible by technical measures. There is no > > business model that exploits the rejection as invalid of an EOTL that fails > > to conform to the spec for that format. In what way is this managing rights? > > Hudson's got it. There are no Rights being Managed, Digital or > otherwise, in any way by such a check. Thus no DRM. But for the "check" the browser could perfectly well render the font. No reason why it shouldn't. What purpose does the check serve, if not rights enforcement? -t > > ~TJ >
Received on Friday, 31 July 2009 02:48:49 UTC