item-license - Revision history

Tantek: drop entry-title thing

2020-08-28T16:54:42Z

drop entry-title thing

← Older revision		Revision as of 16:54, 28 August 2020
Line 1:		Line 1:
	~~<entry-title>item-license</entry-title>~~		<dfn>item-license</dfn> is one of several [[licensing]] [[licensing-brainstorming\|brainstorm proposals]], per the microformats [[process]] towards developing a licensing microformat for authors to indicate licenses to portions of pages or external resources like images.

	<dfn>[[item-license]]</dfn> is one of several [[licensing]] [[licensing-brainstorming\|brainstorm proposals]], per the microformats [[process]] towards developing a licensing microformat for authors to indicate licenses to portions of pages or external resources like images.

Tantek: Reverted edits by Redirect fixer (talk) to last revision by Tantek

2020-08-28T16:39:33Z

Reverted edits by Redirect fixer (talk) to last revision by Tantek

Show changes

Redirect fixer: andhika63.net has been moved, it is now a redirect to hcard

2012-08-25T01:27:21Z

andhika63.net has been moved, it is now a redirect to hcard

Show changes

Tantek: add Mike Linksvayer as co-editor as recognition for his contributions to this brainstorm proposal, and his evaluation of it as "good enough to gather some data".

2010-03-27T07:25:58Z

add Mike Linksvayer as co-editor as recognition for his contributions to this brainstorm proposal, and his evaluation of it as "good enough to gather some data".

← Older revision		Revision as of 07:25, 27 March 2010
Line 3:		Line 3:
	<dfn>[[item-license]]</dfn> is one of several [[licensing]] [[licensing-brainstorming\|brainstorm proposals]], per the microformats [[process]] towards developing a licensing microformat for authors to indicate licenses to portions of pages or external resources like images.		<dfn>[[item-license]]</dfn> is one of several [[licensing]] [[licensing-brainstorming\|brainstorm proposals]], per the microformats [[process]] towards developing a licensing microformat for authors to indicate licenses to portions of pages or external resources like images.

	<~~div~~ class="vcard">
	; <span class="~~role~~">~~Editor~~</span>		; Editors
	: <span class="fn">[~~[User~~:~~Tantek\|Tantek Çelik]~~]</span> (<span class="~~url~~">http://~~tantek~~.~~com~~/</span>)		: <span class="vcard"><span class="fn">[[User:Tantek\|Tantek Çelik]]</span> (<span class="url">http://tantek.com/</span>)</span>
	</~~div~~>		: <span class="vcard"><span class="fn">[http://creativecommons.org/about/people#ml Mike Linksvayer]</span> (<span class="org">[http://creativecommons.org/ Creative Commons]</span>)</span>

	== summary ==		== summary ==

Tantek: /* item-url details */ Possible additions to item-url to handle local items in other parts of the page

2010-03-05T18:58:20Z

item-url details: Possible additions to item-url to handle local items in other parts of the page

← Older revision		Revision as of 18:58, 5 March 2010
Line 84:		Line 84:
	* Authors {{should}} provide at least one "item-url" when an external resource is being licensed.		* Authors {{should}} provide at least one "item-url" when an external resource is being licensed.
	* If more than one "item-url" is provided, they must be considered copies/mirrors/versions (perhaps different resolutions or formats) of the same item, and all have the same license(s) and attribution terms (if any) applied to them.		* If more than one "item-url" is provided, they must be considered copies/mirrors/versions (perhaps different resolutions or formats) of the same item, and all have the same license(s) and attribution terms (if any) applied to them.

			Possible additions to item-url to handle local items in other parts of the page:
			* At most one "item-url" may reference a local fragment id (e.g. <code><a href="#real-item" class="item-url"></code>), and if there is such an "item-url" then it indicates that the entirety of the item is represented by the microformat at that fragment id. This would permit licensing information on one part of a page to refer to an item (such as a blog post) on another part of a page. Anecdotally, I remember seeing blogs where the licensing of the blog posts is in the footer, separate from the chunk of content that contains the blog posts themselves. In most cases [[rel-license]] may be sufficient here - that is, applying to the whole page, but that doesn't cover the "attribution" use case, nor the possible (but needs examples) use case of where the posts are licensed, but not other content on the page.
			** real world examples needed to help guide this.
			* Allow "item-url" to reference multiple items that the license applies to, e.g. all the blog posts on a page, but not the page itself. A space separated set of fragment id references could work for representing this, e.g. (e.g. <code><a href="#real-item-1 #real-item-2 #real-item-n" class="item-url"></code>), but would likely not work well in the interactivity of that hyperlink.
			** real world examples needed to help guide this
			* Alternatively, some other mechanism for a license description (rel-item-license + attribution) to reference one or more items elsewhere on the page.
			** Though it probably makes more sense to simply use the [[include-pattern]] in those items elsewhere on the page to all include a common "item-license" at the footer of a page. The only case this wouldn't work for is if the item-license was an ancestor of all the items, which the include-pattern would disallow including.

	==== attribution details ====		==== attribution details ====
	* If "attribution" is directly specified on a hyperlink (<code><a href></code>), the "href" indicates the suggested link to the original item that is being licensed and contains copyright information for the item being licensed.		* If "attribution" is directly specified on a hyperlink (<code><a href></code>), the "href" indicates the suggested link to the original item that is being licensed and contains copyright information for the item being licensed.

Tantek: added feedback section at bottom

2010-03-03T23:04:32Z

added feedback section at bottom

← Older revision		Revision as of 23:04, 3 March 2010
Line 200:		Line 200:
	* consider any interactions between "item, item-url, attribution" and [[citation]], and document how to use together of possible future interoperability		* consider any interactions between "item, item-url, attribution" and [[citation]], and document how to use together of possible future interoperability
	* consider any interactions between "item-url" and [http://citability.pbworks.com/ Citability]		* consider any interactions between "item-url" and [http://citability.pbworks.com/ Citability]

			== feedback ==
			Please feel free to provide feedback (questions, issues etc.) about [[item-license]] here. If this section gets too big we can move it to [[item-license-feedback]]. Thanks! -Tantek

			* ...

Tantek: /* content portion licensing */ add example of dual licensing

2010-03-03T22:18:49Z

content portion licensing: add example of dual licensing

@@ Line 23: / Line 23: @@
 </div>
 </source>
 == external resource licensing ==

Tantek: add explicit format, root class name, properties, property details sections and a bit more explanation of examples, remove deed.en, upgrade cc examples to 3.0

2010-03-03T14:32:24Z

add explicit format, root class name, properties, property details sections and a bit more explanation of examples, remove deed.en, upgrade cc examples to 3.0

Show changes

Tantek: noted background from licensing-brainstorming, added some more specific to dos along with related links

2010-03-01T09:17:58Z

noted background from licensing-brainstorming, added some more specific to dos along with related links

@@ Line 10: / Line 10: @@
 == summary ==
 This proposal (re-)uses the containing/root class "item" (see also [[hReview]], [[hListing]], [[hProduct]]) to indicate the scope of the thing that is being licensed, <code>rel="item-license"</code> to indicate the specific license(s), "item-url" to license one or  external resources like images, and "attribution" to indicate attribution information.
 == content portion licensing ==
@@ Line 52: / Line 43: @@
 == multiple resolutions licensing ==
- E.g. a link to the photo and embedding a thumbnail or small version of the photo:
+E.g. a link to the photo and embedding a thumbnail or small version of the photo:
 <source lang=html4strict>
@@ Line 140: / Line 131: @@
 # if on an hCard, the "fn" of the hCard indicates the name of an author/creator of the work, and the "url" indicates the URL that is suggested for linking to their name (prefer the first "url" with "uid" if any, otherwise the first "url" if the hCard has more than one).
 # if not on a hyperlink nor an hCard, then the element indicates the name of an author/creator of the work.
 == see also ==
@@ Line 146: / Line 140: @@
 * [[licensing-formats]]
 * [[licensing-brainstorming]]

Tantek: move more to-dos from licensing-brainstorming

2010-03-01T01:05:59Z

move more to-dos from licensing-brainstorming

← Older revision		Revision as of 01:05, 1 March 2010
Line 12:		Line 12:

	== to do ==		== to do ==
	* ~~add embedded~~/~~linked image to~~ brainstorm ~~with Mike Linksvayer on whiteboard,~~ 2010-055 at Creative Commons offices.		* post photo (and embed/link here) of whiteboard brainstorm 2010-055 at Creative Commons offices with Tantek Çelik and Mike Linksvayer and details
			** item
			** attribution (1. on a href means URL to the item including copyright info; 2. on an [[hCard]] means use name of person/org from hCard, and optionally URL for the name if present; 3. else treat it as a name to attribute. may have multiple attribution properties per item.)
			** rel="item-license"
			** item-url
			* have [[hNews]] reference this page
			* write-up item-license examples similar to [http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html#licensing-works microdata works vocabulary] samples/examples (also [http://dev.w3.org/html5/md/#examples microdata works vocab to RDF example].)

	== content portion licensing ==		== content portion licensing ==