Skip to Content.
Sympa Menu

cc-metadata - Re: BitTorrent

cc-metadata AT lists.ibiblio.org

Subject: discussion of the Creative Commons Metadata work

List archive

Chronological Thread  
  • From: Lucas Gonze <lgonze AT panix.com>
  • To: Thomas Winningham <winningham AT gmail.com>, discussion of the Creative Commons Metadata work <cc-metadata AT lists.ibiblio.org>
  • Cc:
  • Subject: Re: BitTorrent
  • Date: Tue, 25 Jan 2005 11:04:49 -1000 (HST)


Over time I've gotten to appreciate the wisdom of that approach. It has a lot going for it --

* the license metadata can be updated over time to reflect things like
name changes.
* it's easy to do a string comparison on a URI to see what the permissions
are, and CC license URIs are absolutely not going to change meaning.
* it's easier to parse the CC RDF and {.torrent,SVG,SMIL,...} if they're
in separate documents. EG, you don't have to fudge around with
conflicting character sets.

- Lucas

On Tue, 25 Jan 2005, Thomas Winningham wrote:

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
option.

Thanks for the comments, and I'm sure I'll be posting again soon.

Thomas


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
http://creativecommons.org/about/people#21

_______________________________________________
cc-metadata mailing list
metadata AT creativecommons.org
http://lists.ibiblio.org/mailman/listinfo/cc-metadata





Archive powered by MHonArc 2.6.24.

Top of Page