[mapserver-commits] r12644 - trunk/docs/en/mapfile
svn at osgeo.org
svn at osgeo.org
Sat Oct 8 05:02:01 EDT 2011
Author: havatv
Date: 2011-10-08 02:02:00 -0700 (Sat, 08 Oct 2011)
New Revision: 12644
Modified:
trunk/docs/en/mapfile/xmp_metadata.txt
Log:
Fixed som typos (xml_<namespace> -> xmp_<namespace>) and some formatting in the new xmp_metadata document (xmp support added in #3932).
Modified: trunk/docs/en/mapfile/xmp_metadata.txt
===================================================================
--- trunk/docs/en/mapfile/xmp_metadata.txt 2011-10-07 19:40:47 UTC (rev 12643)
+++ trunk/docs/en/mapfile/xmp_metadata.txt 2011-10-08 09:02:00 UTC (rev 12644)
@@ -6,28 +6,59 @@
XMP Metadata Support
====================
-One of the challenges of advertising licensing and terms of use in a web map service is that the terms are usually advertised separately from the actual content. So an OpenGIS WMS service might specify terms in the Capabilities document, but the map images themselves will be unmarked. Watermarking is one approach to propagating license terms with a map image, but watermarking restricted in the amount of information that can be conveyed without detracting from the map output. Another approach to propagating license information is to embed the license information in the image file using a common metadata standard.
+.. versionadded:: 6.2
-XMP is the "`extensible metadata platform <http://en.wikipedia.org/wiki/Extensible_Metadata_Platform>`_" which allows the embedding of metadata information across a wide range of document and image formats: PNG, GIF, JPEG, PDF, etc. XMP was originally developed by `Adobe <http://www.adobe.com/products/xmp/overview.html>`_ and is supported across their product line. It is now being increasingly included in other standards for metadata embedding and supported by tools for viewing image information (e.g. exiftools).
+One of the challenges of advertising licensing and terms of use in a
+web map service is that the terms are usually advertised separately
+from the actual content. So an OpenGIS WMS service might specify terms
+in the Capabilities document, but the map images themselves will be
+unmarked. Watermarking is one approach to propagating license terms
+with a map image, but watermarking restricted in the amount of
+information that can be conveyed without detracting from the map
+output. Another approach to propagating license information is to
+embed the license information in the image file using a common
+metadata standard.
-Because XMP is generic and extensible, any metadata can be embedded in it. Creative Commons has `standards for using XMP <http://wiki.creativecommons.org/XMP>`_ to embed commons licensing in images and other documents, including a specific Creative Commons schema. There is also a standard schema for Dublin Core metadata.
+XMP is the "`extensible metadata platform
+<http://en.wikipedia.org/wiki/Extensible_Metadata_Platform>`_" which
+allows the embedding of metadata information across a wide range of
+document and image formats: PNG, GIF, JPEG, PDF, etc. XMP was
+originally developed by `Adobe
+<http://www.adobe.com/products/xmp/overview.html>`_ and is supported
+across their product line. It is now being increasingly included in
+other standards for metadata embedding and supported by tools for
+viewing image information (e.g. exiftools).
+Because XMP is generic and extensible, any metadata can be embedded in
+it. Creative Commons has `standards for using XMP
+<http://wiki.creativecommons.org/XMP>`_ to embed commons licensing in
+images and other documents, including a specific Creative Commons
+schema. There is also a standard schema for Dublin Core metadata.
+
Prerequisites
-------------
In order to use XMP metadata you will need to
- 1. ensure that XMP support is built into MapServer; and,
- 2. use the GDAL output driver to produce your images.
+1. ensure that XMP support is built into MapServer.
+
+ You can test for XMP support in an existing `mapserv` program by
+ running `mapserver -v` and looking for `SUPPORTS=XMP` in the return
+ line.
+
+2. use the GDAL output driver to produce your images.
-You can test for XMP support in an existing `mapserv` program by running `mapserver -v` and looking for `SUPPORTS=XMP` in the return line.
+To build MapServer with XMP support, you will need to first install
+the `exempi` library on your system.
-To build MapServer with XMP support, you will need to first install the `exempi` library on your system.
+1. Download libexempi from
+ http://libopenraw.freedesktop.org/wiki/Exempi
- * Download libexempi from http://libopenraw.freedesktop.org/wiki/Exempi
- * Configure MapServer using the `--with-exempi` option, and re-build
+2. Configure MapServer using the `--with-exempi` option, and re-build
-To use the GDAL output driver, for each format you want to output you will need to set up an :ref:`OUTPUTFORMAT <outputformat>` that uses the GDAL driver. Here is an example of a GDAL output for PNG images::
+To use the GDAL output driver, for each format you want to output you
+will need to set up an :ref:`OUTPUTFORMAT <outputformat>` that uses
+the GDAL driver. Here is an example of a GDAL output for PNG images::
OUTPUTFORMAT
NAME png
@@ -37,14 +68,19 @@
EXTENSION "png"
END
-For more examples of GDAL output formats, see the :ref:`OUTPUTFORMAT <outputformat>` reference.
+For more examples of GDAL output formats, see the :ref:`OUTPUTFORMAT
+<outputformat>` reference.
Using XMP Metadata
------------------
-There can be one XMP package per image, so the XMP metadata for a map is set in the top level of the map file, in the :ref:`WEB` object under the `METADATA` section.
+There can be one XMP package per image, so the XMP metadata for a map
+is set in the top level of the map file, in the :ref:`WEB` object's
+`METADATA` section.
-The `METADATA` key for each XMP entry is of the form `xml_<namespace>_<tag>`, so for example setting just the Dublin Core "Title" would look like::
+The `METADATA` key for each XMP entry is of the form
+`xmp_<namespace>_<tag>`, so for example setting just the Dublin Core
+"Title" would look like::
WEB
METADATA
@@ -52,21 +88,25 @@
END
END
-Note that the Dublin Core schema is specified using the code"dc" and the tag is specified using the fully spelled out tag name, "Title". The following schema codes are supported by default:
+Note that the Dublin Core schema is specified using the code "dc", and
+the tag is specified using the fully spelled out tag name ("Title").
+The following schema codes are supported by default:
- * "meta_" which is the standard XMP tag set
- * "cc_" which is the Creative Commons tag set
- * "dc_" which is the Dublin Core tag set
- * "rights_" which is the standard XMP Rights tag set
- * "exif_" which is the EXIF tags set
- * "tiff_" which is the TIFF tags set
- * "crs_" which is the Photoshop Camera Raw Schema
- * "photoshop_" which is the Photoshop tag set
-
-For a listing of the valid tags within each namespace, see http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/XMP.html.
+* "meta_" which is the standard XMP tag set
+* "cc_" which is the Creative Commons tag set
+* "dc_" which is the Dublin Core tag set
+* "rights_" which is the standard XMP Rights tag set
+* "exif_" which is the EXIF tags set
+* "tiff_" which is the TIFF tags set
+* "crs_" which is the Photoshop Camera Raw Schema
+* "photoshop_" which is the Photoshop tag set
-Here is an example of setting several tags using the default namespaces::
+For a listing of the valid tags within each namespace, see
+`http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/XMP.html`_.
+Here is an example of setting several tags using the default
+namespaces::
+
WEB
METADATA
"xmp_rights_Marked" "true"
@@ -76,7 +116,8 @@
END
END
-It is also possible to define a new namespace and place any tags you like within it. Here is an example::
+It is also possible to define a new namespace and place any tags you
+like within it. Here is an example::
WEB
METADATA
@@ -85,7 +126,10 @@
END
END
-The first tag, of the form "xml_<namespace>_namespace" defines the unique URI for the XML namespace, which will be declared in the XMP document. The following tags can then reference the namespace the same way they reference the default namespaces.
+The first tag, of the form "xmp_<namespace>_namespace" defines the
+unique URI for the XML namespace, which will be declared in the XMP
+document. The following tags can then reference the namespace the same
+way they reference the default namespaces.
.. _meta: http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/XMP.html#xmp
.. _cc: http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/XMP.html#cc
@@ -95,6 +139,6 @@
.. _tiff: http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/XMP.html#tiff
.. _crs: http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/XMP.html#crs
.. _photoshop: http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/XMP.html#photoshop
-
+.. _http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/XMP.html: http://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/XMP.html
More information about the mapserver-commits
mailing list