addition of language metadata

Kralidis,Tom [Burlington] Tom.Kralidis at EC.GC.CA
Thu Nov 2 14:38:13 EST 2006


> -----Original Message-----
> From: UMN MapServer Developers List 
> [mailto:MAPSERVER-DEV at LISTS.UMN.EDU] On Behalf Of Daniel Morissette
> Sent: 02 November, 2006 2:28 PM
> Subject: Re: [UMN_MAPSERVER-DEV] addition of language metadata
> Kralidis,Tom [Burlington] wrote:
> > Hi,
> > 
> > Does anyone think that something like:
> > 
> > MAP/WEB/METADATA/"ows_language"
> > 
> > Would be valuable?  Note that language is a part of the OGC 
> OWS Common 
> > 1.0.0 specification.  Example:
> > 
> Since I don't think any OGC spec supports language as a 
> request parameter, all this ows_language metadata would do is 
> allow the server to report to clients in which language it 
> was configured and in which error messages and capabilities 
> metadata are returned, right?

> Actually, since error messages in MapServer are currently 
> hardcoded in English, does it really make sense to specify 
> any value other than English for exceptions?

For exceptions, yes.  This would cover more than exceptions.
ows_language could apply to more metadata (such as  DataIdentification
within OWS Common 1.0.0).

> Um... I'm starting to realize that this is useless until we 
> have the ability to translate error messages in MapServer... 
> and at that point what we'll need is a LANGUAGE mapfile 
> parameter to control the feature for all of MapServer and not 
> just OGC services.

In the context of Exceptions, maybe we can (at this point) set to
English?  But which one?  en-US?  en-CA?  en-GB?

In terms of content, I think this would be valuable in preparation for
OWS Common support.

> Daniel
> --
> Daniel Morissette

More information about the mapserver-dev mailing list