winningham at gmail.com
Tue Jan 25 15:35:48 EST 2005
I'm looking at some peoples' prior art into merely referencing a URI
pointing to a general license of any kind. That could be a great
Thanks for the comments, and I'm sure I'll be posting again soon.
On Sun, 23 Jan 2005 23:20:01 -0800, Mike Linksvayer
<ml at creativecommons.org> wrote:
> Thomas Winningham wrote:
> > Thank you all so much for all comments. I'm compiling them, and first
> > off I would agree that a separate dictionary in the .torrent may be
> > best.
> Based on your use cases I think that 'flat' name-value pairs along the
> lines of the below would be a good approach. Of course in addition to
> cc:license you could also have dc:title, etc. Such would map cleanly to
> a simple dictionary.
> However, before you commit to this I'd make real sure that you don't
> want to include complex metadata in the .torrent. Per-file metadata is
> the obvious case (which you seem to have ruled out), but there are
> probably many others. Though if you do think you need complex metadata,
> you should consider whether it shouldn't live on the web and only be
> referenced in the .torrent.
> > On Fri, 21 Jan 2005 21:19:28 -0800, Mike Linksvayer
> > <ml at creativecommons.org> wrote:
> >>Something flat, akin to
> >>http://dublincore.org/documents/dc-xml-guidelines/ would probably
> >>satisfy your requirements, though I'm not sure what those are. You can
> >>specify a license with cc:license = licenseURI. Those who want to know
> >>what permissions, etc. are associated with licenseURI can grab the RDF
> >>from that URI.
> Mike Linksvayer
More information about the cc-metadata