[mapserver-dev] metadata language parameter (inspire)

[Bart van den Eijnden]

The INSPIRE specs are not yet set in stone, so I would advice not to implement this as yet.

This would be about supporting multilingual capabilities, and also interpreting an extra LANGUAGE parameter for WMS requests. The capabilities documents are mono-lingual in that sense (one language at a time). If a non-supported language is requested, the service should respond in the default language. However the OGC change requests for multi lingual capabilities have multiple languages in the same GetCapabilities document. Also the encoding of the LANGUAGE parameter differs.

However, it can get tricky if one has to translate things like legends (and GetFeatureInfo responses) as well. I took the approach of having a separate MAP file and a separate dataset per language in an INSPIRE proof of concept which was written as a simple Python Mapscript wrapper see:

http://pastebin.com/f4cb916ce

Best regards,
Bart

On Jun 11, 2010, at 5:50 PM, Yewondwossen Assefa wrote:

> Hi Martin,
> 
> 
> 
> I am not aware of current plans related to supporting the concept of extended capabilities in WMS.
> I am not really familiar with the INSPIRE specs, and I am not also sure I fully understand  what functionality is expected from a MapsServer wms point of vue: beside the fact that somehow we can configure MapServer to return the INSPIRE language settings in the capability document, what is excepted from MapServer  when a language parameter is sent through a request? (possibility use language specific meta data such as wms_title_english or wms_title_french, ignore the language setting resulting in the default language ..)
> I would be willing to put some effort toward this provided we define properly what is expected.
> 
> best regards,
> 
> On 11/06/2010 6:51 AM, Martin Kofahl wrote:
>> Hi there,
>> 
>> INSPIRE requires WMS services to have a language parameter in the Capabilities (see [1] Technical Guidance View Services 3.2.3.3.1.11).
>> 
>> <INSPIRE:ViewCapabilities>
>> 	<INSPIRE:Languages>
>> 		<INSPIRE:Language>ENG</Language>
>> 		<INSPIRE:Language default="true">FRA</Language>
>> 	</INSPIRE:Languages>
>> 	<INSPIRE:CurrentLanguage>
>> 		<INSPIRE:Language>ENG</Language>
>> 	</INSPIRE:CurrentLanguage>
>> </INSPIRE:ViewCapabilities>
>> 
>>   
> 
> 
>> Are there plans to implement this information? Otherwise I would using a metadata in the web section, for now limited to one language code only.
>> 
>>   
> 
> 
>> Martin
>> 
>> [1] http://inspire.jrc.ec.europa.eu/documents/Network_Services/Technical%20Guidance%20View%20Services%20v%202.0.pdf
>> _______________________________________________
>> mapserver-dev mailing list
>> mapserver-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>> 
>>   
> 
> 
> -- 
> ----------------------------------------------------------------
> Assefa Yewondwossen
> Software Analyst
> 
> Email: yassefa at dmsolutions.ca
> http://www.dmsolutions.ca/
> 
> Phone: (613) 565-5056 (ext 14)
> Fax:   (613) 565-0925
> ----------------------------------------------------------------
> 
> 
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>