That sounds good, Nathan. I prefer the strings to come from the rdf and xml files for our purposes. So everything you said makes sense to me.
Thanks. Jim On Mar 2, 2009, at 12:18 PM, Nathan Yergler wrote: > Hi Jim -- > > Just to summarize, I think we've discussed that it'd be helpful to > have the following items as packaged releases (at the very least as > tags): > > * translation strings (po files from the i18n module in Subversion) > * license metadata (currently sourced from the liblicense release) > * chooser questions (questions.xml) > > With respect to the first (i18n), I'm not sure it makes much sense to > do releases. That is, things are committed to trunk directly from the > translation system by our affiliates and we don't do any additional > checking or QA on that (in theory the people doing the committing have > already QA'd things). Note that those strings then flow into the RDF, > etc, although that's not as automated (yet). > > I've created a ticket for the latter two (since they'll be bundled > together) in our tracking system -- > http://code.creativecommons.org/issues/issue186 -- and we'll being > looking at that. > > With respect to the licensing, README in license_xsl says that the > package is MIT licensed. > > Finally, note that you *can* find the RDF separate from liblicense in > Subversion/git (in the license.rdf module). I imagine git will be the > one that "wins" eventually; right now it mirrors Subversion but has a > few additional assertions that help us drive the license engine stack. > > Nathan > > On Fri, Feb 27, 2009 at 6:45 AM, Jim Eng <[email protected]> wrote: >> Hi Nathan and Greg, >> >> This is a followup on some earlier messages. I want to use >> information from >> the file I found at this location: >> >> http://code.creativecommons.org/svnroot/license_xsl/trunk/questions.xml >> >> This contains the set of questions used in a license chooser. I >> would like >> to find this file (or a derivative containing all the same >> information in >> another form such as RDF) in a release package or tag rather than >> in SVN >> trunk. That would help us keep it up to date as new translations >> are added >> or corrections are made. >> >> I have a copy of that file in our SVN in a branch that is not yet >> on track >> to be included in a release of our code, but I would like to move >> it into >> trunk within the next few weeks. My hope is that I can add a >> readme file to >> the directory containing that file and include information about >> the source >> of that file and any conditions for its use. An alternative would >> be to >> embed that information in the file itself in comments. I suspect >> the terms >> would vary depending on whether I get the file from a released >> Creative >> Commons product or from your SVN. Can you advise me on that? >> >> I would also like to include the RDF for CC licenses in a future >> release. I >> am getting these from the licenses directory of liblicense-0.8.1 >> retrieved >> from a mirror of: >> >> http://downloads.sourceforge.net/cctools/liblicense-0.8.1.tar.gz >> >> My plan would be to update that set of licenses as you make new >> versions >> available. Again I'd appreciate advice about any problems that >> might arise. >> >> As we discussed in earlier emails, it would be really cool if the CC >> metadata resources mentioned above were released as a package >> separate from >> your software releases but until that happens, I am hoping to work >> out a way >> that I can reuse these items and keep them up to date. >> >> Thanks. >> >> Jim >> >> > > _______________________________________________ cc-devel mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/cc-devel
