Discussions/Solutions related to supporting the INSPIRE specifications in MapServer 

== Introduction ==

There is a need for MapServer to support the INSPIRE specifications. Several discussions have already happened through mailing list and trac bugs.
The goal of this page is to organize these discussions and come up with solutions that that will allow to support the specification

== References ==

Tickets:

 * ticket:1632 : support for named group layers using wms_layer_group
 * ticket:3608 : INSPIRE related suport

Mailing list and reference documents:

 * http://inspire.jrc.ec.europa.eu/documents/Network_Services/Technical_Guidance_View_Services_v2.12.pdf
 * This [http://osgeo-org.1803224.n2.nabble.com/INSPIRE-compliancy-A-request-for-comments-on-a-possible-RFC-td5661761.html#a5661761]
 * http://osgeo-org.1803224.n2.nabble.com/file/n5661761/MS_RFC_INSPIRE.pdf


== Getcapabilities document  ==

 1. Links to documents extracted from the reference document
 * Schema [http://www3.dmsolutions.ca/tmp/inspire.xsd]
 * Get Capabilities [http://www3.dmsolutions.ca/tmp/get_capabilities.xml]

 2. Tasks
 * add a link to the inspire schema as part of the overall schema list
 * generate an ExtendedCapabilities
 * include all elements by reading inspire type metadata
 * all other metadata outside that extended capabilities should already be part of the regular wms output 

== Presentation of layers in a GetCapabilities document  ==

== Mandatory metadata the need to be supported  ==

== Multi-Language support  ==

== Grouped layers and DescribeLayer request  ==

== Grouped layers and GetMap request  ==

== Grouped layers and SLD  ==

== Grouped layers and GetFeatureInfo request  ==