licensing-brainstorming
Revision as of 00:30, 14 October 2006 by Mike Linksvayer (talk | contribs) (first cut, very beginning)
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 convention | Existing class(es); source | Notes |
---|---|---|
work title | fn; hCard | |
attribution name | author; hAtom | Might be a vcard with fn, may also be an organization |
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? |
donation url | payment; rel-payment | |
commercial licensing url, purchase url |
payment; rel-payment | How to disambiguate from donation? |
content hash | checksum, sha1; hash-examples |
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