metadata

[stefano.parodi]

Lately I've been busy setting up the deegree CSW service for the
metadata. I managed to compile Inspire compliant metadata for the
Dataset and I'm currently looking at implementing the metadata for the
view and discover services.

Talking about metadata, I read in the "Technical Guidance to implement
INSPIRE View Services" [1] that an extension
"<inspire_vs:ExtendedCapabilities>" to the capability document is
required and I noticed that this extension is not implemented in the
capability document of deegree. This extension seem quite important
because it allows the linkage from the capability document of the
service to the service metadata stored in the Discovery Service.
There is yet another important linkage between the capability document
and the data metadata, this is expressed using the <wms:MetadataURL>
element of the single layer (in case of view/WMS services).

By the way the <inspire_vs:ExtendedCapabilities> allows also the
implementation of the language requirements that are an important part
of the inspire requirements.

I was wondering if anyone has yet faced this matter. It seems to me
that the linkages between the various components (data, services,
metadata for data and services) is one the most challenging parts of
the inspire architecture. Regarding this the "INSPIRE Domain
Model" [2] document is a good overview.

Also a merging of the csw component in the inpire-node deegree could
be an interesting thing. Have you ever think about it?

Best Regards.

Stefano.

[1] http://inspire.jrc.ec.europa.eu/documents/Network_Services/Technical%20Guidance%20View%20Services%20v%202.0.pdf

[2]
http://inspire.jrc.ec.europa.eu/documents/INSPIRE_/INSPIRE_Domain_Model_v0.9_-_draft_final.pdf

[Just van den Broecke]

Hi Stefano,

Yes, I have heard about this WMS 1.3 INSPIRE-specific extension (from
Markus I think) but have not yet dived into this. Possibly Markus can
expand here.

Yes, deegree CSW was on my list to look into and would be a very useful
addition to the deegree inspire node. I am not familiar yet with deegree
CSW (only with GeoNetwork). Maybe, as a first start we may setup a CSW
maven/.war config similar to
http://code.google.com/p/inspire-foss/source/browse/#svn%2Ftrunk%2Fwebapps%2Fdeegree3
the WMS/WFS webapp. Ideas welcome.

best,

Just van den Broecke

[Markus Schneider]

Hi Stefano,

Am 20.01.2011 18:41, schrieb stefano.parodi:
> Talking about metadata, I read in the "Technical Guidance to implement
> INSPIRE View Services" [1] that an extension
> "<inspire_vs:ExtendedCapabilities>" to the capability document is
> required and I noticed that this extension is not implemented in the
> capability document of deegree. This extension seem quite important
> because it allows the linkage from the capability document of the
> service to the service metadata stored in the Discovery Service.
> There is yet another important linkage between the capability document
> and the data metadata, this is expressed using the<wms:MetadataURL>
> element of the single layer (in case of view/WMS services).

Actually, deegree 3 CSW does support these extended capabilities. Try
the following CSW configuration:

<deegreeCSW xmlns="http://www.deegree.org/services/csw"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
configVersion="3.0.0"
xsi:schemaLocation="http://www.deegree.org/services/csw
http://schemas.deegree.org/services/csw/3.0.0/csw_configuration.xsd">
<EnableTransactions>true</EnableTransactions>
<EnableInspireExtensions>true</EnableInspireExtensions>
</deegreeCSW>

> By the way the<inspire_vs:ExtendedCapabilities> allows also the
> implementation of the language requirements that are an important part
> of the inspire requirements.
>
> I was wondering if anyone has yet faced this matter. It seems to me
> that the linkages between the various components (data, services,
> metadata for data and services) is one the most challenging parts of
> the inspire architecture. Regarding this the "INSPIRE Domain
> Model" [2] document is a good overview.
>
> Also a merging of the csw component in the inpire-node deegree could
> be an interesting thing. Have you ever think about it?

Yes, we thought about it and it would be cool to do it. It would
especially be interesting to have a tight metadata integration between
WMS/WFS and the CSW.

However, it's currently unclear when we are able to work on that, as
there's no funding or customer project that requires it.

Best regards,
Markus

[stefano.parodi]

Hi Markus.

> Actually, deegree 3 CSW does support these extended capabilities. Try
> the following CSW configuration:
>
> <deegreeCSW xmlns="http://www.deegree.org/services/csw"
> xmlns:xlink="http://www.w3.org/1999/xlink"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> configVersion="3.0.0"

> xsi:schemaLocation="http://www.deegree.org/services/cswhttp://schemas.deegree.org/services/csw/3.0.0/csw_configuration.xsd">

>    <EnableTransactions>true</EnableTransactions>
>    <EnableInspireExtensions>true</EnableInspireExtensions>
> </deegreeCSW>
>

I'll try it out!
Even though I can't see how it can affect the capability response of
the WMS/WFS server.
What are the effects of this configuration?
Maybe I better pose this question to the deegree forum, tell me if
this is the case.

Thank you.

Best Regards.
Stefano.