licensing-brainstorming

2008-12-19T22:30:14Z

CaaccNapas: racdarliz

alvarlic
= 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.

<table border="1" cellpadding="3" cellspacing="2">
<tr><th>Overly descriptive strawman not intended to conform with any convention</th><th>[[existing-classes|Existing class(es)]]; source</th><th>Notes</th></tr>

<tr>
<td>work title</td>
<td>fn; hCard</td>
<td>See [[licensing-examples#Attribution_with_work_title|examples#title]]</td>
</tr>

<tr>
<td>attribution name, creator?</td>
<td>author; hAtom, [[hcard]]</td>
<td>Might be a vcard with fn, may also be an organization
<br/>See [[licensing-examples#Attribution_to_creator|examples#attribution]]</td>
</tr>

<tr>
<td>attribution url</td>
<td>url; hCard</td>
<td>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?
<br/>See [[licensing-examples#Attribution_with_link_required|examples#link]]</td>
</tr>

<tr>
<td>donation url</td>
<td>payment; rel-payment<br/>
offer; hListing</td>
<td>How to disambiguate from commercial licensing and purchase?
<br/>See [[licensing-examples#Donation_related_to_work|examples#donation]]</td>
</tr>

<tr>
<td>commercial licensing url</td>
<td>payment; rel-payment<br/>
sell, offer; hListing<br/>
copyright; HTML LinkType</td>
<td>How to disambiguate from donation and purchase?
<br/>See [[licensing-examples#Commercial_licensing|examples#commercial]]</td>
</tr>

<tr>
<td>purchase url</td>
<td>payment; rel-payment<br/>
sell, offer; hListing</td>
<td>How to disambiguate from donation and commercial licensing?
<br/>See [[licensing-examples#Purchase_related_media|examples#purchase]]</td>
</tr>

<tr>
<td>content hash</td>
<td>checksum, sha1; [[hash-examples]]</td>
<td>See [[licensing-examples#License_notice_with_content_hash|examples#hash]]</td>
</tr>

<tr>
<td>provenance url<td>
<td> See [[licensing-examples#Rights_provenance.2Fwarranty.2Fidemnification|examples#provenance]] </td>
</tr>

<tr>
<td>parent work <em>url?</em>, derivitave-source</td>
<td></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]]<br/>
Probably should be a URL -- a uf can have a #URL if it has an id.</td>
</tr>

<tr>
<td>attribution, copied-source</td>
<td></td>
<td>Shows where the media was immediately copied from (not necessarily the same as its original source). Has the same challenges as derivative-source. Perhaps use the approach loosely outlined in [[licensing-brainstorming#Attribution_Challenges|Attribution Challenges]]</td>
</tr>

<tr>
<td>source</td>
<td></td>
<td>Like 'copied-source' but points to the original source.</td>
</tr>

</table>

== Attribution Challenges ==

Tags dealing with specifying sources and tracking a piece of media's path through the Web (any of the -source tags above) are a little ambiguous in terms of what they can reference. For instance when specifying a derivative work it could be from another image on the Internet, in which case an URL would be appropriate, or it could be a quotation from a magazine or other "real" world source where an URL doesn't really work. Perhaps we can encourage the content of these 'media source' tags to be one of the following:
<table border="1" cellpadding="3">
<tr>
<th>Media source type</th>
<th>Format</th>
<th>Notes</th>
</tr>
<tr>
<td>Internet source</td>
<td>An URL</td>
<td></td>
</tr>
<tr>
<td>Person</td>
<td>[[hcard]]</td>
<td></td>
</tr>
<tr>
<td>Publication <br />(book, magazine, etc.)</td>
<td>[[citation]]</td>
<td>Citation appears to be heavily weighed towards academia but it looks like it should work for most purposes</td>
</tr>
<tr>
<td>Film/Video</td>
<td> ?? </td>
<td>I'm not sure about this one. Would citation stretch over visual media? Perhaps [[media-info]]?</td>
</tr>
</table>

== 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):

<pre>
<nowiki>
<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>
</nowiki>
</pre>

== Strawman example for media ==

Note the [[media-info]] is not even defined yet, this is not even strawman quality.

<pre>
<nowiki>
<div class="media">
<img class="url attribution mediaitem" src="http://example.com/cake.jpg"/>
<span class="fn">Picture of a giant cake</span>
<div class="author vcard">
<div class="fn attribution">J Doe</div>
</div>
<a rel="license" href="http://creativecommons.org/licenses/by-nc/2.5/">(cc)</a>
<a rel="payment" href="http://paypal.com/...">don't let me <s>starve</s>eat cake</a>
<a rel="payment" href="http://artdelivery.example">buy this pic, framed</a>
<a rel="payment" href="http://photoclearing.example">get commercial rights</a>
...
</div>
</nowiki>
</pre>

== Todo ==
* Answer questions above and those not posed
* Discover and fix gratuitous problems with the above
* Examples working with [[media-info]]

= Creative Commons Vocab =

Creative Commons has an [http://creativecommons.org/ns RDF vocabulary] which may be suitable for reuse. Here is an example using the Creative Commons vocab. It goes a long way to meeting all the stated requirements.

<pre><nowiki>
<div class="License">
<a rev="license" href="http://example.org/work">The work</a> is licensed under
the <a rel="legalcode" href="http://example.org/foo">Foo Licence</a>.
Summary: it permits <abbr title="DerivativeWorks" class="permits">derivative
works</abbr> but requires <abbr title="Attribution" class="requires"
>attribution</abbr>. The credit to give when reusing the work is "<span
class="vcard"><a href="http://tobyinkster.co.uk" class="fn url
attributionName" rel="attributionURL">Toby Inkster</a></span>".
</div>
</nowiki></pre>

The microformat could use the following terms:

* '''License''' {1} (root class name)
** legalcode ? (rel value, not class)
** ''morePermissions'' * (rel value, not class)
** ''permits'' * ("Reproduction" | "Distribution" | "DerivativeWorks" | "HighIncomeNationUse" | "Sharing")
** ''requires'' * ("CopyrightNotices" | "Attribution" | "ShareAlike" | "SourceCode")
** ''prohibits'' * ("CommercialUse")
** ''jurisdiction'' * (text | hCard | adr)
** attributionName ?
** attributionURL ? (rel value, not class)
** deprecatedOn ? (ISO date)

The license linked to using rel="legalcode" (if any) should be taken to be the definitive license. When such a license is present, the "permits", "requires", "prohibits" and "jurisdiction" classes are taken to be merely advisory. When no "legalcode" license is linked to, these classes are definitive.

[[rel-license]] {{should}} be used to link from the work to the license (an ID attribute on the license will help). A license {{may}} link back to the work using rev="license", but forward links are preferred.

As an extension to the creative commons vocabulary (which focuses on open-source-like licenses) a payment URL {{may}} be linked to using an anchor element simultaneously carrying class="requires" and rel="payment". Example:

<pre><nowiki>
<a class="requires" rel="payment" href="https://payment.example.org">buy</a>
</nowiki></pre>

If [[rel-payment]] is used without a class of "requires", then the link is taken to be an optional payment link - i.e. a donation.

Microformats Wiki - User contributions [en]

licensing-brainstorming