licensing-brainstorming

From Microformats Wiki
Revision as of 04:12, 21 October 2006 by Mike Linksvayer (talk | contribs) (→‎Discussion: parent work reference)
Jump to navigation Jump to search

Licensing Brainstorming

The very beginning.

See licensing for background.

Discussion

Set of classes pertinent to supporting licensing and attribution requirements and complements. These classes could be used at webpage level or within relevant microformats, e.g., media-info.

Overly descriptive strawman not intended to conform with any conventionExisting class(es); sourceNotes
work title fn; hCard See examples#title
attribution name author; hAtom Might be a vcard with fn, may also be an organization
See examples#attribution
attribution url url; hCard An author might have a url, should this be taken as the attribution url? If a work has a url, should it be taken as the attribution url?
See examples#link
donation url payment; rel-payment How to disambiguate from commercial licensing and purchase?
See examples#donation
commercial licensing url payment; rel-payment How to disambiguate from donation and purchase?
See examples#commercial
purchase url payment; rel-payment How to disambiguate from donation and commercial licensing?
See examples#purchase
content hash checksum, sha1; hash-examples See examples#hash
provenance url See examples#provenance
parent work url See examples#derivative

Strawman example

Perhaps there should be an 'attribution' class which might hint that a fn or url should be used for attribution? Something like (webpage scope):


<a class="url attribution fn" href="http://example.com">My First Cookbook</a>
<div class="author vcard">
  <div class="fn attribution">J Doe</div>
</div>
<a rel="license" href="http://creativecommons.org/licenses/by/2.5/">(cc)</a>
<a rel="payment" href="http://paypal.com/...">don't let me starve</a>

Todo

  • Answer questions above and those not posed
  • Discover and fix gratuitous problems with the above
  • Examples working with media-info