[cc-devel] In liblicense, why does Raptor support the old namespace?

Jason Kivlighn jkivlighn at gmail.com
Thu Jan 10 15:52:30 EST 2008

The only reason web.resource.org is in there is because Inkscape for a
long time produced SVG's that used this namespace.  I decided in
liblicense to write the new namespace unless there was already license
metadata present and that license metadata used the old namespace.  Most
likely that metadata was written by Inkscape and, so that it could
subsequently still be read by Inkscape, the namespace is left as
web.resource.org.  Toward the end of the summer, my patch to have
Inkscape read and write the new namespace got committed to svn.  So I'd
assume that most SVG's in the wild that have license metadata are using
the old namespace.

I know... supporting legacy standards is a pain, but I'm trying to avoid
confusion on the user end (at the expense of the developer end,


Asheesh Laroia wrote:
> I noticed that modules/io/raptor.c checks for the old namespace based
> on web.resource.org rather than creativecommons.org.
> Scott or Jason, do you have a moment to explain the logic or rationale
> behind why we would us the old namespace?  Is there data in the wild
> that uses the old NS?
> Also, the intent of this code is to use the new namespace by default?
> Thanks!
> -- Asheesh.

More information about the cc-devel mailing list