OK, great. My only gentle suggestion is to treat the RDF files as RDF instead of straight up XML if possible. We make every effort to keep things stable but I know that MIT's DSpace ran into problems at one point because they were treating RDF as XML. We made a tooling change which inadvertantly changed the namespace prefixes (IIRC we went from having the CC namespace as the default to the RDF as the default, with CC prefixed by cc:) and broke their integration. Of course, we're much more aware of this sort of dependency now...
Perhaps your comment about "well-defined namespaces" accounts for that sort of thing? FWIW... On Tue, Feb 24, 2009 at 5:44 PM, Jim Eng <[email protected]> wrote: > Those files look like we could process them, but I don't know the format. > I've already written parsing routines for the RDF files (actually just > treating them as XML with well-defined namespaces). I could switch to PO > files if need be. Of course, the RDF files give us much more than the > resource bundles we usually use for i18n. So I'm happy to stay with the RDF > files if we can. > > Thanks. > > Jim > > > > On Feb 24, 2009, at 5:02 PM, Nathan Yergler wrote: > >> Hi Jim, >> >> Also, just of note, the RDF is probably not quite as up to date as the >> PO files themselves (in Subversion; see >> http://code.creativecommons.org/viewsvn/i18n/). >> >> We can probably do some sort of "packaging" of those if it'd be >> helpful. I'm not sure what Java expects with respect to translation >> files... do they use PO files? >> >> Nathan >> >> >> On Sat, Feb 7, 2009 at 9:55 AM, Greg Grossmeier >> <[email protected]> wrote: >>> >>> Hi Jim, >>> >>>> But we'd really like to use a "released" version packaged as a jar or >>>> zip archive with version number and such so we can easily track >>>> changes and make sure we are getting a stable version for our >>>> releases. Ideally, we would let maven get the specified version from >>>> from http://mirrors.ibiblio.org/pub/mirrors/maven2/ or some mirror. >>>> So the question is whether there are versioned releases of these >>>> files, and whether there is a best way to get them? >>> >>> I forgot to mention that there are packages of the license RDF as part >>> of the liblicense library [0] (which reads and writes license metadata >>> to a variety of file formats). There is liblicense-rdf which is a >>> released package of the license.rdf code tree. I don't believe I know >>> what system Sakai runs on but there are deb packages or rpms >>> available through most distributions. In fact we host our own >>> repository for liblicense for Debian and Ubuntu [1] >>> >>> This could be one solution, but not exactly what you want. >>> >>> Best, >>> >>> Greg >>> >>> >>> [0] http://wiki.creativecommons.org/liblicense >>> >>> [1] http://mirrors.creativecommons.org/packages/ >>> _______________________________________________ >>> cc-devel mailing list >>> [email protected] >>> http://lists.ibiblio.org/mailman/listinfo/cc-devel >>> >> >> > > _______________________________________________ cc-devel mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/cc-devel
