licensing-brainstorming: Difference between revisions
Jump to navigation
Jump to search
(→Discussion: parent work reference) |
(→Discussion: too url-happy?) |
||
Line 8: | Line 8: | ||
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]]. | 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]]. | ||
The first column may be too URL-centric, see notes for parent work, may apply to others. | |||
<table border="1" cellpadding="3" cellspacing="2"> | <table border="1" cellpadding="3" cellspacing="2"> | ||
Line 66: | Line 68: | ||
<tr> | <tr> | ||
<td>parent work url</td> | <td>parent work <em>url?</em></td> | ||
<td></td> | <td></td> | ||
<td>See [[licensing-examples#Attribution_to_derivative.27s_source_work|examples#derivative]]</td> | <td>Should this be a url? Maybe it should be a TBD "media" microformat which may be otherwise described. | ||
<br/>See [[licensing-examples#Attribution_to_derivative.27s_source_work|examples#derivative]]</td> | |||
</tr> | </tr> | ||
Revision as of 06:58, 22 October 2006
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.
The first column may be too URL-centric, see notes for parent work, may apply to others.
Overly descriptive strawman not intended to conform with any convention | Existing class(es); source | Notes |
---|---|---|
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? | Should this be a url? Maybe it should be a TBD "media" microformat which may be otherwise described.
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