European Commission logo
INSPIRE Community Forum

element name="inspireID" instead of "inspireId" in PS XSD Schema

Hello everybody,

In the  ProtectedS Sites XSD schema found at http://inspire.ec.europa.eu/schemas/ps/4.0/ProtectedSites.xsd it is declared the element with the name "inspireID" with upper case D, as follows: <element name="inspireID" type="base:IdentifierPropertyType">.

However, in GN, AU and BR schemas, the same element is declared with the name "inspireId", with lower case d, as follows:

http://inspire.ec.europa.eu/schemas/gn/4.0/GeographicalNames.xsd

<element name="inspireId" type="base:IdentifierPropertyType">


http://inspire.ec.europa.eu/schemas/au/4.0/AdministrativeUnits.xsd

<element name="inspireId" type="base:IdentifierPropertyType">


http://inspire.ec.europa.eu/schemas/br/4.0/Bio-geographicalRegions.xsd

<element minOccurs="0" name="inspireId" type="base:IdentifierPropertyType">

 

This created a certain problem when we intented to create some stored querries on a dataset containing a mix of ps:ProtectedSites, gn:NamedPlaces, br:BiogeographicalRegions, au:AdministrativeUnits and au:AdministrativeBoundaries feature types.

The  http://inspire.ec.europa.eu/schemas/ps/4.0/ProtectedSites.xsd PS XSD schema should be corrected in order to change <element name="inspireID" type="base:IdentifierPropertyType"> into <element name="inspireId" type="base:IdentifierPropertyType">.

 

Most probably there are other elements in other schemas as well that are ending in "ID" instead of "Id" (lower/upper camel case) that need to be corrected. Most probably simmilar errors are in the TGs.

Any comments are welcomed.

Best regards,

Iurie Maxim

 

  • Stefania MORRONE

    By Stefania MORRONE

    Hi Iurie,

    I agree that it would be better to have the same 'inspireId' element for all INSPIRE themes. Nevertheless, the issue you pointed out is not due to an application schema error, because  for the Protected Sites theme the attribute name 'InspireID' is defined in the Implementing Rules. Therefore currently a change in the PS schema would violate the IR.

    Best Regards

    Stefania

  • Iurie MAXIM

    Hi Stefania,

    Thank you for indicating this. Therefore, I looked in the IR 1089/2010 with all the ammendments and for all data themes the element name is "inspireId" except for Protected Sites where is "inspireID". My understanding is that this is a typo error in the IR.

    Just to provide a simmilar, but oposite case for PS: "Geological" in IR vs. "geological" in XSD: <enumeration value="geological">. Here is viceversa, namely the XSD is corrected but violates the IR. In the Registry the value is like in the XSD and not like in the IR http://inspire.ec.europa.eu/enumeration/ProtectionClassificationValue/geological

    Therefore I see that there are cases where the corrections are violating the IR, so either always the XSD, Registries, etc should be according to IR, either they need to be corrected prior the corrections in the IR, that are more difficult to be operated.

    I remember when I indicated to you as well another simmilar issue for PS in the envPlus validator, namely: 

    "ProtectedLandscapeOrSeascape" (in IR) vs. "protectedLandscapeOrSeascape" (according to the loweCamelCase rule) vs. the value in the registry: http://inspire.ec.europa.eu/codelist/IUCNDesignationValue/ProtectedLandscapeOrSeascape

    The correct value is as you indicated as well: "protectedLandscapeOrSeascape" with first letter in lower case.

    I have no ideea if so many issues are only for PS, or if this is common to other data themes as well.

    Anybody knows simmilar cases ?

    Best regards,

    Iurie Maxim

     

     

  • Iurie MAXIM

    Dear all,

    We noticed that implementations are done having in mind that one dataset = one feature type, and till now we did not identified any dataset served via WFS where one dataset = more feature types.

    If someone can provide an example, it would be usefull.

    So we created one such WFS for a dataset with more feature types having the geometries of different features topologicaly correct in order to allow computing with WPS, namely to determine for each protected site in which administrative unit(s) is located and in which bio-geographical region(s) is located. We generated as well the named places under GN schema for all ProtectedSites and will follow the generation of all named places for all AdministrativeUnits.

    To understand the issue of inspireID <> inspireId, please see the request below and imagine a way to automate the request in order to retrieve the inspire identifiers of all the features in a a WFS that serves a dataset composed by multiple feature types:

    http://inspire.biodiversity.ro/WFS/RO_ENV_PADS/wfs?service=WFS&version=2.0.0&request=GetFeature&TypeNames=gn:NamedPlace,br:Bio-geographicalRegion,au:AdministrativeUnit,ps:ProtectedSite&propertyName=(inspireId)(inspireId)(inspireId)(inspireID) .

    Even if still some work is to be done for this service to be finished, the link works and brings the inspire identifier for more than 6000 features of different types (gn:NamedPlace,br:Bio-geographicalRegion,au:AdministrativeUnit,ps:ProtectedSite).

    The link above provides all the inspire identifiers for all the features in the "PADS" dataset to be used in order to retrieve each feature trough localId and versionId (if it exist), as for example:

    http://inspire.biodiversity.ro/WFS/RO_ENV_PADS/wfs?service=WFS&version=2.0.0&request=GetFeature&STOREDQUERY_ID=GETpsPSRefByInspireId&localId=RONPA0022

    http://inspire.biodiversity.ro/WFS/RO_ENV_PADS/wfs?service=WFS&version=2.0.0&request=GetFeature&STOREDQUERY_ID=GETgnNPRefByInspireId&localId=RONPA0025

    These requests are necessary in order to be able to make such redirects:

    http://gmlid.ro/ENV/PADS/psPSRef/RONPA0022

    http://gmlid.ro/ENV/PADS/gnNPRef/RONPA0025

    Best reagrds,

    Iurie Maxim

  • Stefania MORRONE

    By Stefania MORRONE

    Dear Iurie and all,

    renaming the attribute ps:inspireID to ps:inspireId is one of the agreed changes to the INSPIRE Technical Documentation for “D2.8.I.9 Data Specification on Protected Sites – Technical Guidelines” version 3.2.

    Documents that will be affected by the change: IR, TG, UML, XML schema, existing GML data sets.

    More details the corrigendum document.

    Kind regards,

    Stefania

     

  • Iurie MAXIM

    Dear all,

    Noticed that in the corigendum of the Technical Guidelines on data Specification for protected sites there is the Change: 3 but the https://inspire.ec.europa.eu/schemas/ps/4.0/ProtectedSites.xsd is not changed and a new version did not appeared.

    As this issue is known at least from 2015, there is any information when this change wil be made and version 4.1 of the ProtectedSites.xsd will be issued ?

    Change: 3

    Affected documents: IR, TG, UML, XML schema, existing GML data sets

    Themes: Protected Sites

    Subject: Correct the spelling of the attribute ps:inspireID to ps:inspireId:

    Description: Within the theme of Protected Sites the INSPIRE identifier is spelled as “inspireID” and not as “inspireId”. It is proposed to harmonise the name of the inspire identifier attribute and to use inspireId in the INSPIRE Protected sites theme. Corrigendum: replace “inspireID” with “inspireId”.

    Change the UML data model, Technical Guidelines and XML schemas accordingly.

    Discussion link: https://ies-svn.jrc.ec.europa.eu/issues/2568 

    Best regards,

    iurie Maxim

    http://essensys.ro

     

This discussion is closed.

This discussion is closed and is not accepting new comments.

Biodiversity & Area Management

Biodiversity & Area Management

If themes like Protected Sites, Area Management/Restriction/Regulation Zones and Reporting Units, Habitats and Biotopes, Species Distribution, Bio-geographical Regions matters to you, join these groups!