Here we'll explore the nexus of legal rulings, Capitol Hill
policy-making, technical standards development, and technological
innovation that creates -- and will recreate -- the networked world as we
know it. Among the topics we'll touch on: intellectual property
conflicts, technical architecture and innovation, the evolution of
copyright, private vs. public interests in Net policy-making, lobbying
and the law, and more.
Disclaimer: the opinions expressed in this weblog are those of the authors and not of their respective institutions.
In the blog entry from March, Richard Fink points out some clear evidence that Typekit either isn't working as designed or is putting up misleading copyright information. Fink uses the word "fraud" but in the comment back and forth with Typekit's Jeffrey Veen, Fink admits that he may be guilty of unnecessary hyperbole. Veen's defense, that he (and Typekit) don't know how to write licenses and so may be guilty of bad wording at worst, may be true but seems like sloppy work. Is there no one at Creative Commons or other organization that could help out here?
One other tech link I saw in Fink's post is worth surfacing here: The League of Moveable Type, an organization dedicated to the production and distribution of free and open fonts for use on the Web and elsewhere.