XMP - Revision history

John-bishop-images: Add XMP_help_for_Adobe_applications XMP help for Adobe applications

2015-01-15T05:58:01Z

Add XMP_help_for_Adobe_applications XMP help for Adobe applications

← Older revision		Revision as of 05:58, 15 January 2015
Line 50:		Line 50:
	* [http://en.wikipedia.org/wiki/Extensible_Metadata_Platform Wikipedia article]		* [http://en.wikipedia.org/wiki/Extensible_Metadata_Platform Wikipedia article]
	* [[Adobe Metadata Panel\|Adobe XMP FileInfo Panel]]		* [[Adobe Metadata Panel\|Adobe XMP FileInfo Panel]]
			* [[XMP help for Adobe applications\|XMP help for Adobe applications]]

	<small>The XMP logo is either a registered trademark or trademark of the Adobe Systems Incorporated in the United States and/or other countries.</small>		<small>The XMP logo is either a registered trademark or trademark of the Adobe Systems Incorporated in the United States and/or other countries.</small>

CC Wiki Bot: CC Wiki Bot moved page Property:XMP to XMP over a redirect without leaving a redirect: Undo move

2014-02-10T14:26:36Z

CC Wiki Bot moved page Property:XMP to XMP over a redirect without leaving a redirect: Undo move

← Older revision	Revision as of 14:26, 10 February 2014
(No difference)

Alryan Morang: Alryan Morang moved page XMP to Property:XMP

2014-02-10T12:00:36Z

Alryan Morang moved page XMP to Property:XMP

← Older revision	Revision as of 12:00, 10 February 2014
(No difference)

Mike Linksvayer: Reverted edits by Nethanbraker (talk) to last revision by Mike Linksvayer

2013-10-05T23:46:15Z

Reverted edits by Nethanbraker (talk) to last revision by Mike Linksvayer

← Older revision		Revision as of 23:46, 5 October 2013
Line 29:		Line 29:
	== Verification Links and XMP ==		== Verification Links and XMP ==

	A publisher can boost confidence in embedded metadata by providing a '''verifying web statement'''. A verifying web statement is a [http://~~enhanced-identity-theft-protection~~.com/~~how-chase-identity-theft-protection~~-~~plans~~-~~help~~/ URL] which contains metadata with assertions matching those embedded in the file. The difference is that instead of making the assertions about a URL, the assertions are made in reference to the SHA-1 hash of the file.		A publisher can boost confidence in embedded metadata by providing a '''verifying web statement'''. A verifying web statement is a [http://watersoftenerreviewspro.com/water-softener-comparison/ URL] which contains metadata with assertions matching those embedded in the file. The difference is that instead of making the assertions about a URL, the assertions are made in reference to the SHA-1 hash of the file.

	For example, the example web statement <code>http://example.com/pdf-metadata.html</code> would include metadata encoded as [[RDFa]].		For example, the example web statement <code>http://example.com/pdf-metadata.html</code> would include metadata encoded as [[RDFa]].

Nethanbraker: /* Verification Links and XMP */

2013-09-24T11:09:21Z

Verification Links and XMP

← Older revision		Revision as of 11:09, 24 September 2013
Line 29:		Line 29:
	== Verification Links and XMP ==		== Verification Links and XMP ==

	A publisher can boost confidence in embedded metadata by providing a '''verifying web statement'''. A verifying web statement is a [http://~~watersoftenerreviewspro~~.com/~~water~~-~~softener~~-~~comparison~~/ URL] which contains metadata with assertions matching those embedded in the file. The difference is that instead of making the assertions about a URL, the assertions are made in reference to the SHA-1 hash of the file.		A publisher can boost confidence in embedded metadata by providing a '''verifying web statement'''. A verifying web statement is a [http://enhanced-identity-theft-protection.com/how-chase-identity-theft-protection-plans-help/ URL] which contains metadata with assertions matching those embedded in the file. The difference is that instead of making the assertions about a URL, the assertions are made in reference to the SHA-1 hash of the file.

	For example, the example web statement <code>http://example.com/pdf-metadata.html</code> would include metadata encoded as [[RDFa]].		For example, the example web statement <code>http://example.com/pdf-metadata.html</code> would include metadata encoded as [[RDFa]].

Mike Linksvayer: Reverted edits by Babsesun (talk) to last revision by Boetbre

2013-09-15T20:38:30Z

Reverted edits by Babsesun (talk) to last revision by Boetbre

← Older revision		Revision as of 20:38, 15 September 2013
Line 42:		Line 42:
	</pre></code>		</pre></code>

	When processing a file containing an embedded ~~[http://webmediavault.com~~ web] statement, an [http://www.windows8softwares.com application] can retrieve the statement and parse it for additional metadata. If matching assertions are found which apply to the calculated SHA-1 hash of the file, the application can display an indicator noting increased confidence in the metadata. This approach has the added benefit of taking advantage of an existing mechanism (copyright take-down procedures) in order to break the confidence in the case of inappropriately licensed material.		When processing a file containing an embedded web statement, an [http://www.windows8softwares.com application] can retrieve the statement and parse it for additional metadata. If matching assertions are found which apply to the calculated SHA-1 hash of the file, the application can display an indicator noting increased confidence in the metadata. This approach has the added benefit of taking advantage of an existing mechanism (copyright take-down procedures) in order to break the confidence in the case of inappropriately licensed material.

	== Additional Information ==		== Additional Information ==

Babsesun: /* Verification Links and XMP */

2013-08-19T05:12:46Z

Verification Links and XMP

← Older revision		Revision as of 05:12, 19 August 2013
Line 42:		Line 42:
	</pre></code>		</pre></code>

	When processing a file containing an embedded web statement, an [http://www.windows8softwares.com application] can retrieve the statement and parse it for additional metadata. If matching assertions are found which apply to the calculated SHA-1 hash of the file, the application can display an indicator noting increased confidence in the metadata. This approach has the added benefit of taking advantage of an existing mechanism (copyright take-down procedures) in order to break the confidence in the case of inappropriately licensed material.		When processing a file containing an embedded [http://webmediavault.com web] statement, an [http://www.windows8softwares.com application] can retrieve the statement and parse it for additional metadata. If matching assertions are found which apply to the calculated SHA-1 hash of the file, the application can display an indicator noting increased confidence in the metadata. This approach has the added benefit of taking advantage of an existing mechanism (copyright take-down procedures) in order to break the confidence in the case of inappropriately licensed material.

	== Additional Information ==		== Additional Information ==

Boetbre: /* Verification Links and XMP */

2013-08-02T08:50:17Z

Verification Links and XMP

← Older revision		Revision as of 08:50, 2 August 2013
Line 42:		Line 42:
	</pre></code>		</pre></code>

	When processing a file containing an embedded web statement, an application can retrieve the statement and parse it for additional metadata. If matching assertions are found which apply to the calculated SHA-1 hash of the file, the application can display an indicator noting increased confidence in the metadata. This approach has the added benefit of taking advantage of an existing mechanism (copyright take-down procedures) in order to break the confidence in the case of inappropriately licensed material.		When processing a file containing an embedded web statement, an [http://www.windows8softwares.com application] can retrieve the statement and parse it for additional metadata. If matching assertions are found which apply to the calculated SHA-1 hash of the file, the application can display an indicator noting increased confidence in the metadata. This approach has the added benefit of taking advantage of an existing mechanism (copyright take-down procedures) in order to break the confidence in the case of inappropriately licensed material.

	== Additional Information ==		== Additional Information ==

Calvinharris: /* Verification Links and XMP */

2013-06-05T16:32:09Z

Verification Links and XMP

← Older revision		Revision as of 16:32, 5 June 2013
Line 29:		Line 29:
	== Verification Links and XMP ==		== Verification Links and XMP ==

	A publisher can boost confidence in embedded metadata by providing a '''verifying web statement'''. A verifying web statement is a URL which contains metadata with assertions matching those embedded in the file. The difference is that instead of making the assertions about a URL, the assertions are made in reference to the SHA-1 hash of the file.		A publisher can boost confidence in embedded metadata by providing a '''verifying web statement'''. A verifying web statement is a [http://watersoftenerreviewspro.com/water-softener-comparison/ URL] which contains metadata with assertions matching those embedded in the file. The difference is that instead of making the assertions about a URL, the assertions are made in reference to the SHA-1 hash of the file.

	For example, the example web statement <code>http://example.com/pdf-metadata.html</code> would include metadata encoded as [[RDFa]].		For example, the example web statement <code>http://example.com/pdf-metadata.html</code> would include metadata encoded as [[RDFa]].

Hamilton Abreu: /* Specifying License Information */

2011-06-01T21:32:54Z

Specifying License Information

← Older revision		Revision as of 21:32, 1 June 2011
Line 18:		Line 18:
	* '''xmpRights:Marked''' — ''False'' if Public Domain, ''True'' otherwise.		* '''xmpRights:Marked''' — ''False'' if Public Domain, ''True'' otherwise.
	* '''xmpRights:WebStatement''' — ''http://example.com/pdf-metadata.html'' (Replace with URL containing metadata about the XMP-embedded file; this is referred to as the [[WebStatement\|Web Statement]].)		* '''xmpRights:WebStatement''' — ''http://example.com/pdf-metadata.html'' (Replace with URL containing metadata about the XMP-embedded file; this is referred to as the [[WebStatement\|Web Statement]].)
	* '''xmpRights:UsageTerms''' — An optional field describing legal terms of use; Creative Commons recommends that when present this take the form ''This work is licensed to the public under the Creative Commons Attribution-ShareAlike license http://creativecommons.org/licenses/bysa/2.0/ verify at http://example.com/pdfmetadata.html'' (Replace URL following 'verify at' with URL containing metadata about the XMP-embedded file; this is typically the URL specified by '''xmpRights:WebStatement'''.) ~~NOTE~~ as of 2011-05 http://www.metadataworkinggroup.org/pdf/mwg_guidance.pdf suggests using '''dc:rights''' and xmpRights:WebStatement; it probably makes sense to populate dc:rights and xmpRights:UsageTerms with identical content.		* '''xmpRights:UsageTerms''' — An optional field describing legal terms of use; Creative Commons recommends that when present this take the form ''This work is licensed to the public under the Creative Commons Attribution-ShareAlike license http://creativecommons.org/licenses/bysa/2.0/ verify at http://example.com/pdfmetadata.html'' (Replace URL following 'verify at' with URL containing metadata about the XMP-embedded file; this is typically the URL specified by '''xmpRights:WebStatement'''.)<br />'''''Note''': as of 2011-05 http://www.metadataworkinggroup.org/pdf/mwg_guidance.pdf suggests using '''dc:rights''' and xmpRights:WebStatement; it probably makes sense to populate dc:rights and xmpRights:UsageTerms with identical content.''

	We also define a Creative Commons schema ''http://creativecommons.org/ns#'' whose common prefix is cc. It currently has the following properties:		We also define a Creative Commons schema ''http://creativecommons.org/ns#'' whose common prefix is cc. It currently has the following properties: