- From: Ben Weiner <ben@readingtype.org.uk>
- Date: Sat, 18 Jun 2011 22:59:36 +0100
- To: www-font@w3.org
- Cc: Glenn Adams <glenn@skynav.com>, W3C Style <www-style@w3.org>
On 18 Jun 2011, at 22:45, Glenn Adams wrote: <snipped> > Second, I am not saying "they shouldn't be specified". I'm saying they (same-origin mandate) should not be specified in WOFF or CSS3-FONTS. These are not the correct place to mandate or enforce such restrictions. If there are restrictions on access, the mechanism by which this is imposed and enforce should be specified where the access occurs, and that is not in WOFF or CSS3-FONTS, but in a UA that uses these. I agree. I like the fact that the webfonts spec is both stimulating and originating potential specifications beyond its own remit. It feels good to see stuff like CORS and From-origin being fleshed out here with compelling use cases, but I for one hope that they are being devolved away from a spec about fonts to places where they will be nurtured better and debated more comprehensively by the right people. Webfonts shouldn't be keeping these good new things to itself. > Further, it must be possible to build UAs that are not required to enforce such restrictions, and which remain compliant. Indeed, ones that can use permissively-licensed web fonts where the idea of restricting the origin of the file might happen not to be interesting or relevant. Ben -- Ben Weiner | http://readingtype.org.uk/about/contact.html +44 (0) 7780 608 659
Received on Saturday, 18 June 2011 22:00:40 UTC