Marking Works Technical - Revision history

Matt Lee at 14:31, 25 September 2014

2014-09-25T14:31:28Z

← Older revision		Revision as of 14:31, 25 September 2014
Line 16:		Line 16:

	<nowiki>This text is licensed to the public under the <a rel="license"		<nowiki>This text is licensed to the public under the <a rel="license"
	href="~~http~~://creativecommons.org/licenses/by-sa/2.5/">Creative		href="https://creativecommons.org/licenses/by-sa/4.0/">Creative
	Commons Attribution 2.5 License</a>.</nowiki>		Commons Attribution 4.0 License</a>.</nowiki>

	That HTML snippet says that the current document is licensed under CC Attribution 2.5. The current document is the default subject, <code>rel="license"</code> sets the predicate or verb, the URL in the <code>href</code> value sets the object.		That HTML snippet says that the current document is licensed under CC Attribution 4.0. The current document is the default subject, <code>rel="license"</code> sets the predicate or verb, the URL in the <code>href</code> value sets the object.

	For detailed background on the web metadata model and syntax being used, see [[RDFa]].		For detailed background on the web metadata model and syntax being used, see [[RDFa]].
Line 33:		Line 33:
	=== Attribution ===		=== Attribution ===

	A licensor can specify how they wish to be attributed for use of their work (see, for example, § 4(b) of ~~http~~://creativecommons.org/licenses/by/2.5/legalcode). This includes:		A licensor can specify how they wish to be attributed for use of their work (see, for example, § 4(b) of https://creativecommons.org/licenses/by/4.0/legalcode). This includes:

	# The title of the work		# The title of the work
Line 59:		Line 59:
	of 'Paginas Blancos Si!'</a>, is licensed to the public under		of 'Paginas Blancos Si!'</a>, is licensed to the public under
	the <a rel="license"		the <a rel="license"
	href="~~http~~://creativecommons.org/licenses/by/2.5/">Creative		href="https://creativecommons.org/licenses/by/4.0/">Creative
	Commons Attribution 2.5 License</a>.		Commons Attribution 4.0 License</a>.

	This produces the triples above plus these:		This produces the triples above plus these:
Line 66:		Line 66:
	# <> dc:creator <http://example.org/jr.html> .		# <> dc:creator <http://example.org/jr.html> .
	# <> dc:source <http://example.org/bps.html> .		# <> dc:source <http://example.org/bps.html> .
	# <> license <~~http~~://creativecommons.org/licenses/by/2.5/> .		# <> license <https://creativecommons.org/licenses/by/4.0/> .

	=== Included Objects ===		=== Included Objects ===
Line 75:		Line 75:

	<nowiki>Photo licensed under <a about="http://example.com/some-image.png"		<nowiki>Photo licensed under <a about="http://example.com/some-image.png"
	rel="license" href="~~http~~://creativecommons.org/licenses/by/2.5/">cc by 2.5</a>.</nowiki>		rel="license" href="https://creativecommons.org/licenses/by/4.0/">cc by 4.0</a>.</nowiki>

	See the RDFa Primer on [http://www.w3.org/2006/07/SWD/RDFa/primer/#beyond-current-document beyond the current document] for additional examples.		See the RDFa Primer on [http://www.w3.org/2006/07/SWD/RDFa/primer/#beyond-current-document beyond the current document] for additional examples.
Line 84:		Line 84:

	<nowiki><span rel="dc:type" href="http://purl.org/dc/dcmitype/Sound"/>Audio</span> <a rel="license"		<nowiki><span rel="dc:type" href="http://purl.org/dc/dcmitype/Sound"/>Audio</span> <a rel="license"
	href="~~http~~://creativecommons.org/licenses/by-nc/2.5/">(cc)</a> <span property="dc:date">2006</span>.		href="https://creativecommons.org/licenses/by-nc/4.0/">(cc)</a> <span property="dc:date">2006</span>.
	See <a rel="cc:morePermissions" href="http://johnsmith.com/store">my store</a> to obtain permissions not		See <a rel="cc:morePermissions" href="http://johnsmith.com/store">my store</a> to obtain permissions not
	granted by the CC license, signed CDs, and concert tickets.</nowiki>		granted by the CC license, signed CDs, and concert tickets.</nowiki>
Line 128:		Line 128:
	<nowiki><span about="urn:sha1:DATAG7ENBVHFNQPM4W626VDVK25RYECI">		<nowiki><span about="urn:sha1:DATAG7ENBVHFNQPM4W626VDVK25RYECI">
	'Good Dream' is licensed under		'Good Dream' is licensed under
	<a rel="license" href="~~http~~://creativecommons.org/licenses/by/2.5/">CC BY</a>.		<a rel="license" href="https://creativecommons.org/licenses/by/4.0/">CC BY</a>.
	</span></nowiki>		</span></nowiki>

	Produces the following triple:		Produces the following triple:

	<urn:sha1:DATAG7ENBVHFNQPM4W626VDVK25RYECI> license <~~http~~://creativecommons.org/licenses/by/2.5/> .		<urn:sha1:DATAG7ENBVHFNQPM4W626VDVK25RYECI> license <https://creativecommons.org/licenses/by/4.0/> .

	== XMP ==		== XMP ==

Kat Walsh: /* XMP */ typos

2013-05-28T16:49:55Z

XMP: typos

← Older revision		Revision as of 16:49, 28 May 2013
Line 137:		Line 137:
	== XMP ==		== XMP ==

	[[XMP]] has the broadest support of any embedded metadata format (perhaps it is the only such format with anything approaching broad support) across many different media formats. With the exception ~~meida~~ formats where a workable embedded metadata format is already ~~ubiquituous~~, Creative Commons recommends adopting XMP as an embedded metadata standard and use of the following two fields in particluar:		[[XMP]] has the broadest support of any embedded metadata format (perhaps it is the only such format with anything approaching broad support) across many different media formats. With the exception of media formats where a workable embedded metadata format is already ubiquitous, Creative Commons recommends adopting XMP as an embedded metadata standard and use of the following two fields in particluar:

	* Web reference: value of <code>xapRights:WebStatement</code>		* Web reference: value of <code>xapRights:WebStatement</code>
	* License: value of <code>cc:license</code>		* License: value of <code>cc:license</code>


	== Audio ==		== Audio ==

MartiniPeres: /* Principles */

2012-08-13T09:13:59Z

Principles

← Older revision		Revision as of 09:13, 13 August 2012
Line 8:		Line 8:

	* Copyright notice should be published on the '''web'''. Offline or peer-distributed works should refer to notice published on the web. A web notice allows content to be found via web search, content owners to be found by viewers of untethered works, may be trusted to the extent a web page may be trusted, and allows for further annotation by the owner and others.		* Copyright notice should be published on the '''web'''. Offline or peer-distributed works should refer to notice published on the web. A web notice allows content to be found via web search, content owners to be found by viewers of untethered works, may be trusted to the extent a web page may be trusted, and allows for further annotation by the owner and others.
	* Copyright notice should be '''visible''' and unambiguous to humans and computers, especially the former. Human and computer visible notices should be one and the same.		* Copyright notice should be '''visible''' and unambiguous to humans and computers, especially the former. Human and computer visible notices should be one and the same.Offline or peer-distributed works should not refer to notice published on the web.
	* Copyright notice best practices should be '''general''' rather than applicable only to works offered under one of the Creative Commons licenses.		* Copyright notice best practices should be '''general''' rather than applicable only to works offered under one of the Creative Commons licenses.

Akozak: moved Http://kamalabac3.kamalabacalsd.blogger.com to Marking Works Technical over redirect

2010-11-16T17:53:33Z

moved Http://kamalabac3.kamalabacalsd.blogger.com to Marking Works Technical over redirect

← Older revision	Revision as of 17:53, 16 November 2010
(No difference)

Kamalabacalsd: moved Marking Works Technical to Http://kamalabac3.kamalabacalsd.blogger.com

2010-11-16T15:30:30Z

moved Marking Works Technical to Http://kamalabac3.kamalabacalsd.blogger.com

← Older revision	Revision as of 15:30, 16 November 2010
(No difference)

Nathan Yergler at 22:42, 15 February 2008

2008-02-15T22:42:43Z

← Older revision		Revision as of 22:42, 15 February 2008
Line 3:		Line 3:
	This article describes best practices for marking works licensed with a Creative Commons license or dedicated to the public domain with both human readable and machine readable notices, on the web and otherwise.		This article describes best practices for marking works licensed with a Creative Commons license or dedicated to the public domain with both human readable and machine readable notices, on the web and otherwise.

	Although the importance of human-visible attribution and notice is stressed, this primary focus of this article is machine-readable metadata. Best practice for presentation of human-visible attribution and notice in various formats (apart from ~~colocation~~ with machine-readable equivalents) is currently beyond the scope of this article and will be presented [[Marking\|elsewhere]].		Although the importance of human-visible attribution and notice is stressed, this primary focus of this article is machine-readable metadata. Best practice for presentation of human-visible attribution and notice in various formats (apart from collocation with machine-readable equivalents) is currently beyond the scope of this article and will be presented [[Marking\|elsewhere]]. An index of specific technical recommendations, organized by file type, is [[:Category:Filetype\|available]].

	= Principles =		= Principles =

Nathan Yergler: /* Document formats */

2008-02-15T22:39:15Z

Document formats

← Older revision		Revision as of 22:39, 15 February 2008
Line 188:		Line 188:
	Ideally these metadata fields should be used to directly populate the human-visible parts of the document, e.g., via a document field, as is typically used to automatically place page numbers and document titles throughout such documents. This gives us the best of both worlds -- any software that indexes embedded metadata can easily find license information, and that information is perfectly reflected in notices humans see.		Ideally these metadata fields should be used to directly populate the human-visible parts of the document, e.g., via a document field, as is typically used to automatically place page numbers and document titles throughout such documents. This gives us the best of both worlds -- any software that indexes embedded metadata can easily find license information, and that information is perfectly reflected in notices humans see.

	~~What follows is a very incomplete accounting~~ of how ~~these guidelines~~ may be ~~used~~ in ~~various popular office document~~ formats.		Details of how metadata may be embedded in specific file formats is available [[:Category:Filetype\|here]].

	~~=== PDF ===~~

	~~Visible notice as above. Use XMP embedded metadata.~~

	~~=== Microsoft Office ===~~

	~~Visible notice as above. Metadata TBD.~~

	~~=== OpenOffice.org ===~~

	~~Visible notice as above. Metadata TBD~~.

Nathan Yergler at 22:37, 15 February 2008

2008-02-15T22:37:26Z

← Older revision		Revision as of 22:37, 15 February 2008
Line 88:		Line 88:
	granted by the CC license, signed CDs, and concert tickets.</nowiki>		granted by the CC license, signed CDs, and concert tickets.</nowiki>

	In addition to the familiar <code>license</code> statement and <code>dc:type</code> from Dublin Core we have <code>cc:morePermissions</code>. The intention of <code>cc:~~moreRights~~</code> is to point to a URL at which one can discover permissions outside the scope of those granted to the public by the licensor via a CC license.		In addition to the familiar <code>license</code> statement and <code>dc:type</code> from Dublin Core we have <code>cc:morePermissions</code>. The intention of <code>cc:morePermissions</code> is to point to a URL at which one can discover permissions outside the scope of those granted to the public by the licensor via a CC license.

	See [[CCPlus]] for more information on specifying ~~morePermissions.~~		See [[CCPlus]] for more information on specifying <code>cc:morePermissions</code>.

	~~=== Namespaces ===~~

	~~In the example snippets above we have used the~~ <code>cc:</code> ~~and <code>dc:</code> namespaces without definition~~. ~~To define a namespace for subsequent use include an <code>xmlns</code> attribute on the element in which the namespace is used on any parent element. Example:~~

	~~<nowiki><span xmlns:dc="http://purl.org/dc/elements/1.1/" property="dc:title">My Book</span></nowiki>~~

	=== Interoperability with other web-based metadata formats ===		=== Interoperability with other web-based metadata formats ===
Line 102:		Line 96:
	==== RDF/XML ====		==== RDF/XML ====

	RDF/XML is another RDF serialization that can be used to make any statement that can be made with RDFa. RDF/XML may be <code><link></code>ed in the <code><head></code> of a web page or ~~(deprecated CC recommendation)~~ included in HTML comments. RDF/XML is perfectly interoperable with RDFa, but the latter is preferred as it is ~~colocated~~ with human-visible content.		RDF/XML is another RDF serialization that can be used to make any statement that can be made with RDFa. RDF/XML may be <code><link></code>ed in the <code><head></code> of a web page or [[Extend_Metadata#Embedding_RDF_in_HTML\|included in HTML comments]], as the deprecated CC recommendation advocated.

			RDF/XML is perfectly interoperable with RDFa, but the latter is preferred as it is collocated with human-visible content.

	==== Microformats ====		==== Microformats ====

	[[RelLicense]] is both an [http://microformats.org/wiki/elemental-microformat elemental microformat] (specifically [http://microformats.org/wiki/rel-license rel license]) and an [[RDFa]] statement. Compound Microformats should be interoperable via [http://www.w3.org/TR/grddl/ GRDDL] or [http://www.w3.org/2001/sw/BestPractices/HTML/2006-08-08-hgrddl-xhtml1 hGRDDL].		[[RelLicense\|rel=license]] is both an [http://microformats.org/wiki/elemental-microformat elemental microformat] (specifically [http://microformats.org/wiki/rel-license rel license]) and an [[RDFa]] statement. Compound Microformats should be interoperable via [http://www.w3.org/TR/grddl/ GRDDL] or [http://www.w3.org/2001/sw/BestPractices/HTML/2006-08-08-hgrddl-xhtml1 hGRDDL].

	Use cases for licensing and related metadata as microformats may be found at [http://microformats.org/wiki/licensing on the microformats wiki]; they remain hypothetical as microformats, but generalize to use cases for Creative Commons web metadata.		Use cases for licensing and related metadata as microformats may be found at [http://microformats.org/wiki/licensing on the microformats wiki]; they remain hypothetical as microformats, but generalize to use cases for Creative Commons web metadata.
Line 112:		Line 108:
	==== Feeds ====		==== Feeds ====

	~~RSS1~~.0, ~~RSS2~~.0, and Atom 1.0 syndication formats each may include [[Syndication\|license annotations]]. These should also be reflected on web pages referenced by feed items.		RSS 1.0, RSS 2.0, and Atom 1.0 syndication formats each may include [[Syndication\|license annotations]]. These should also be reflected on web pages referenced by feed items.

	= Non-Web =		= Non-Web =
Line 122:		Line 118:
	* To the extent possible license notice provided by non-web objects should use mechanisms and conventions in '''common use''' for the format of the non-web object in question.		* To the extent possible license notice provided by non-web objects should use mechanisms and conventions in '''common use''' for the format of the non-web object in question.

	We will now apply these principles to a variety of content formats, after describing two building blocks for Non-Web metadata -- web metadata and XMP.		We will now apply these principles to a variety of content formats, after describing two building blocks for Non-Web metadata -- web statement metadata and XMP.

	== Web Statement ==		== Web Statement ==
Line 170:		Line 166:
	== Still Images ==		== Still Images ==

	Although possible, visible attribution and copyright notice generally either does not fit in an image due to size or aesthetic limitations. Even where possible human-visible notice will not be ~~colocated~~ with machine-readable metadata (for bitmap formats currently in use).		Although possible, visible attribution and copyright notice generally either does not fit in an image due to size or aesthetic limitations. Even where possible human-visible notice will not be collocated with machine-readable metadata (for bitmap formats currently in use).

	For embedded metadata XMP is recommended.		For embedded metadata XMP is recommended.

Nathan Yergler at 21:28, 15 February 2008

2008-02-15T21:28:15Z

← Older revision		Revision as of 21:28, 15 February 2008
Line 41:		Line 41:
	Ideally this information would also be available as machine-readable metadata. As an example, this could be encoded in the following triples (assuming the work in question is the current document):		Ideally this information would also be available as machine-readable metadata. As an example, this could be encoded in the following triples (assuming the work in question is the current document):

	1. <> dc:title "Compact Representation of Blank Pages" .		# <> dc:title "Compact Representation of Blank Pages" .
	2. <> cc:attributionName "James Roberts" .		# <> cc:attributionName "James Roberts" .
	3. <> cc:attributionURL <http://example.org/crobp.html> .		# <> cc:attributionURL <http://example.org/crobp.html> .

	Why the new properties?		Why the new properties?
Line 64:		Line 64:
	This produces the triples above plus these:		This produces the triples above plus these:

	5. <> dc:creator <http://example.org/jr.html> .		# <> dc:creator <http://example.org/jr.html> .
	6. <> dc:source <http://example.org/bps.html> .		# <> dc:source <http://example.org/bps.html> .
	7. <> license <http://creativecommons.org/licenses/by/2.5/> .		# <> license <http://creativecommons.org/licenses/by/2.5/> .

	=== Included Objects ===		=== Included Objects ===

	Objects included in web pages (images) should be annotated as above within their "host" web pages. Ideally all included objects should also embed object format native notice and metadata as described below, but this is only crucial for objects where the publisher intends for or is concerned about distribution outside the context of the "host" web page.		Objects included in web pages, such as images, should be annotated as above within their "host" web pages. Ideally all included objects should also embed object [[:Category:Filetype\|format native]] notice and metadata as described below, but this is only crucial for objects where the publisher intends for or is concerned about distribution outside the context of the "host" web page.

	Metadata about include objects that have their own URIs should be qualified with <code>about</code>, as <code>rel="license"</code> without an <code>about</code> attribute makes a statement about the current document (which is the "host" web page). Example:		Metadata about include objects that have their own URIs should be qualified with <code>about</code>, as <code>rel="license"</code> without an <code>about</code> attribute makes a statement about the current document (which is the "host" web page). Example:
Line 90:		Line 90:
	In addition to the familiar <code>license</code> statement and <code>dc:type</code> from Dublin Core we have <code>cc:morePermissions</code>. The intention of <code>cc:moreRights</code> is to point to a URL at which one can discover permissions outside the scope of those granted to the public by the licensor via a CC license.		In addition to the familiar <code>license</code> statement and <code>dc:type</code> from Dublin Core we have <code>cc:morePermissions</code>. The intention of <code>cc:moreRights</code> is to point to a URL at which one can discover permissions outside the scope of those granted to the public by the licensor via a CC license.

	~~A prominent use case is Magnatune's commercial licensing system. Example:~~		See [[CCPlus]] for more information on specifying morePermissions.

	* http://magnatune.com/artists/albums/anup-embrace/ "Embrace" by Anup
	* <code>cc:morePermissions~~</code> for this work would point to https://magnatune.com/artists/license/?artist=Anup&album=Embrace&genre=World where one can obtain commercial licensing for advertising, film, video games, etc~~.

	=== Namespaces ===		=== Namespaces ===
Line 122:		Line 119:

	* To the extent possible copyright notice should be '''visible''' to users of the licensed object.		* To the extent possible copyright notice should be '''visible''' to users of the licensed object.

	* The licensed object should contain a '''web reference''' to a web page that provides an equivalent licensing notice for the object in question. This makes a non-web object's licesning status as certain as that of a web page's status -- if the web reference does not agree with the non-web object's license notice, ignore the latter.		* The licensed object should contain a '''web reference''' to a web page that provides an equivalent licensing notice for the object in question. This makes a non-web object's licesning status as certain as that of a web page's status -- if the web reference does not agree with the non-web object's license notice, ignore the latter.

	* To the extent possible license notice provided by non-web objects should use mechanisms and conventions in '''common use''' for the format of the non-web object in question.		* To the extent possible license notice provided by non-web objects should use mechanisms and conventions in '''common use''' for the format of the non-web object in question.

Nathan Yergler at 20:00, 15 February 2008

2008-02-15T20:00:55Z

← Older revision		Revision as of 20:00, 15 February 2008
Line 8:		Line 8:

	* Copyright notice should be published on the '''web'''. Offline or peer-distributed works should refer to notice published on the web. A web notice allows content to be found via web search, content owners to be found by viewers of untethered works, may be trusted to the extent a web page may be trusted, and allows for further annotation by the owner and others.		* Copyright notice should be published on the '''web'''. Offline or peer-distributed works should refer to notice published on the web. A web notice allows content to be found via web search, content owners to be found by viewers of untethered works, may be trusted to the extent a web page may be trusted, and allows for further annotation by the owner and others.

	* Copyright notice should be '''visible''' and unambiguous to humans and computers, especially the former. Human and computer visible notices should be one and the same.		* Copyright notice should be '''visible''' and unambiguous to humans and computers, especially the former. Human and computer visible notices should be one and the same.

	* Copyright notice best practices should be '''general''' rather than applicable only to works offered under one of the Creative Commons licenses.		* Copyright notice best practices should be '''general''' rather than applicable only to works offered under one of the Creative Commons licenses.

Line 35:		Line 33:
	=== Attribution ===		=== Attribution ===

			A licensor can specify how they wish to be attributed for use of their work (see, for example, § 4(b) of http://creativecommons.org/licenses/by/2.5/legalcode). This includes:

	~~A licensor can specify (see 4(b)~~ of		# The title of the work
	~~http://creativecommons.org/licenses/by/2.5/legalcode):~~		# The name of the person, group or organization to attribute the work to
			# The URL to link the attribution to
	# name of ~~author~~ or ~~designated entity~~
	~~# title of work~~
	~~# url associated with~~ work ~~referencing copyright~~
	# ~~identification of derivative use~~

	Ideally ~~all of these~~ would be available as machine-readable metadata. I		Ideally this information would also be available as machine-readable metadata. As an example, this could be encoded in the following triples (assuming the work in question is the current document):
	~~think~~ the triples ~~we want~~ (assuming the work in question is the current
	document) ~~are~~:

	1. <> cc:~~attributionName~~ "~~James Roberts~~" .		1. <> dc:title "Compact Representation of Blank Pages" .
	2. <> dc:~~title~~ "~~Compact Representation of Blank Pages~~" .		2. <> cc:attributionName "James Roberts" .
	3. <> cc:attributionURL <http://example.org/crobp.html> .		3. <> cc:attributionURL <http://example.org/crobp.html> .
	~~4. <> cc:derivativeDescription "translation of 'Paginas Blancos Si!'" .~~

	Why the new properties?		Why the new properties?

	# dcterms:rightsHolder and dc:creator don't say which should be attributed -- or if someone else should be.		# dcterms:rightsHolder and dc:creator don't say which should be attributed -- or if someone else should be; cc:attributionName has the semantics necessary for the task.
	~~# not new, dc~~:~~title works just fine~~.		# The attribution URL will often be the current URL, but we need some way to specify that it should be cited; cc:attributionURL provides this.
	# often ~~this will~~ be the current URL, but need some way to specify that it should be cited.
	~~# dc~~:~~source refers to the source work, not how source work was reused~~.

	Fortunately RDFa allows us to annotate human readable notices and		Fortunately RDFa allows us to annotate human readable notices and include both the custom properties needed for attribution as well as additional useful properties, e.g.
	include both the custom properties needed for attribution as well as
	additional useful properties, e.g.

	<a rel="cc:attributionURL" href="http://example.org/crobp.html"		<a rel="cc:attributionURL" href="http://example.org/crobp.html"
Line 68:		Line 56:
	<a rel="dc:creator" href="http://example.org/jr.html"		<a rel="dc:creator" href="http://example.org/jr.html"
	property="cc:attributionName">James Roberts</a>, a <a		property="cc:attributionName">James Roberts</a>, a <a
	rel="dc:source" href="http://example.org/bps.html"		rel="dc:source" href="http://example.org/bps.html">translation
	~~property="cc:derivativeDescription">translation~~ of 'Paginas		of 'Paginas Blancos Si!'</a>, is licensed to the public under
	Blancos Si!'</a>, is licensed to the public under the <a		the <a rel="license"
	rel="license"
	href="http://creativecommons.org/licenses/by/2.5/">Creative		href="http://creativecommons.org/licenses/by/2.5/">Creative
	Commons Attribution 2.5 License</a>.		Commons Attribution 2.5 License</a>.

	This produces the ~~four~~ triples above plus these:		This produces the triples above plus these:

	5. <> dc:creator <http://example.org/jr.html> .		5. <> dc:creator <http://example.org/jr.html> .