INSPIRE - support for CSW LANGUAGE parameter

[heikki]

Remarks about the implementation:

• CSW server configuration has been moved from System settings to a custom form (accessible from Administration > CSW server), where the user can configure also the translated values for any natural language fields (Titles, Abstracts, Fees and Access constraints) in Capabilities document.

• If INSPIRE is enabled, it's returned Capabilities response including language extensions and used the language provided:
  • Natural language fields are returned in the language requested
  • The end-points are returned for the language requested:

Request: ​http://localhost:8080/geonetwork/srv/en/csw?request=GetCapabilities&service=CSW&version=2.0.2&language=esp

  <ows:Operation name="GetRecords">
      <ows:DCP>
        <ows:HTTP>
          <ows:Get xlink:href="http://localhost:8080/geonetwork/srv/es/csw" />
          <ows:Post xlink:href="http://localhost:8080/geonetwork/srv/es/csw">

<ows:ExtendedCapabilities>
    <inspire_ds:ExtendedCapabilities>
      <inspire_ds:Languages>
        <!--
            List of supported languages
            -->
        <inspire_ds:Language>ger</inspire_ds:Language>
        <inspire_ds:Language>eng</inspire_ds:Language>
        <inspire_ds:Language>por</inspire_ds:Language>
        <inspire_ds:Language>fre</inspire_ds:Language>
        <inspire_ds:Language default="true">eng</inspire_ds:Language>
        <inspire_ds:Language>rus</inspire_ds:Language>
        <inspire_ds:Language>esp</inspire_ds:Language>
        <inspire_ds:Language>dut</inspire_ds:Language>
      </inspire_ds:Languages>
      <inspire_ds:CurrentLanguage>esp</inspire_ds:CurrentLanguage>
    </inspire_ds:ExtendedCapabilities>
</ows:ExtendedCapabilities>

• If INSPIRE is NOT enabled, the standard capabilities document is returned, but:
  • Natural language fields are returned in the language requested in url locale
  • The end-points are returned for the language requested in url locale

Request: ​http://localhost:8080/geonetwork/srv/es/csw?request=GetCapabilities&service=CSW&version=2.0.2

  <ows:Operation name="GetRecords">
      <ows:DCP>
        <ows:HTTP>
          <ows:Get xlink:href="http://localhost:8080/geonetwork/srv/es/csw" />
          <ows:Post xlink:href="http://localhost:8080/geonetwork/srv/es/csw">

Request: ​http://localhost:8080/geonetwork/srv/en/csw?request=GetCapabilities&service=CSW&version=2.0.2

  <ows:Operation name="GetRecords">
      <ows:DCP>
        <ows:HTTP>
          <ows:Get xlink:href="http://localhost:8080/geonetwork/srv/en/csw" />
          <ows:Post xlink:href="http://localhost:8080/geonetwork/srv/en/csw">

For GetRecords, language parameter is supported. Jose did some tests to verify that is working with metadata in different languages using queries like:

<csw:GetRecords xmlns:csw="http://www.opengis.net/cat/csw/2.0.2" 
 xmlns:ogc="http://www.opengis.net/ogc" 
service="CSW" resultType="results" 
outputFormat="application/xml" 
outputSchema="http://www.isotc211.org/2005/gmd" 
startPosition="1" maxRecords="10">
<csw:Query typeNames="gmd:MD_Metadata">
  <csw:ElementSetName typeNames="gmd:MD_Metadata">full</csw:ElementSetName>
  <csw:Constraint version="1.1.0">
    <ogc:Filter>
      <ogc:PropertyIsEqualTo>
        <ogc:PropertyName>Language</ogc:PropertyName>
        <ogc:Literal>eng</ogc:Literal>
      </ogc:PropertyIsEqualTo>
   </ogc:Filter>
  </csw:Constraint>
</csw:Query>
</csw:GetRecords>

[tomkralidis]

To verify, is the language parameter also supported via the HTTP Accept-Languages header?

[josegar74]

It´s not supported.

I checked the document ​http://inspire.jrc.ec.europa.eu/documents/Network_Services/Technical_Guidance_Discovery_Services_v2.12.pdf and didn´t find anything about the support of HTTP Accept-Languages header.

Maybe I miss it or it´s defined in another document?

[tomkralidis]

Does / will the GN CSW implementation support the ebRIM profile? It's part of OGC document 07-110r4.

[heikki]

hi Tom,

there is a CSW/ebRIM implementation in the GeoNetwork 3.x branch, which is not yet released.

In my opinion it should be good to release this in the foreseeable future, as you are not the only one asking about this.

Could you pose this question directly in an email to the GN developers list? That is a more appropriate forum, and may attract some more attention to this.

[heikki]

integrated in 2.6.x revision 6979

[heikki]

integrated in trunk revision 7005