MIWP-Action #2140

MIWP-18 XML schema maintenance

Added by Lorena Hernandez Quiros over 6 years ago. Updated over 5 years ago.

Status:ClosedStart date:27 Apr 2015
Priority:NormalDue date:30 Apr 2015
Assignee:Michael Lutz% Done:




In the amendment of the Implementing Rules and the corresponding updated versions of the data specification Technical Guidelines, a number of changes have been introduced to the Annex I data models (for details, see Annex II of Commission Regulation (EU) No 1253/2013 and the updated data specifications), namely:

  1. Some candidate types and placeholders and the references to them have been removed (since they have been replaced by other types in the Annex II+III themes).
  2. Some candidate types and placeholders have been re-included in the Physical Waters package in the Hydrography theme
  3. Some references have been updated to types in Annex II+III themes
  4. Some additional sub-types of HydroObject have been created in the Sea Regions theme
  5. An additional data model has been developed for Maritime Units.
  6. One minor change of a geometry type (from GM_Surface to GM_MultiSurface) has been made in the candidate type Shore.

As a consequence, some of the Annex I xml schemas need to be updated to reflect these changes. If possible, any data sets that have already been created according to the current schemas (v3.0) should also be valid according to the updated schemas (or could be made valid by only changing a namespace).

Since such changes can impact on implementation of software, a development and release process should be developed for updating/maintaining XML schemas. This process should address acceptance, versioning, corrigenda etc. There is a need to coordinate with software developers and data providers about proposed changes to ensure implications of changes are kept to a minimum, that people are informed and plans made about how to migrate. The communication strategy should also be covered by the development and release process.

Finally, there is also a need to discuss, whether, when and how the updated encoding rules (that have been used for the Annex II+III schemas) are applied to the Annex I schemas.

Proposed change or action:

  • Define a formal process for management and updates of XML schemas
  • Propose updates to XML schemas for Annex I to make them consistent with the amended IRs
  • Propose a roadmap for applying the new encoding rules to the Annex I schemas

Organisational set-up:

Establish a MIG sub-group to address the issue. This could be the same group as for MIWP-11 and MIWP-12.


  • Proccess for management and updates of XML schemas
  • Updated XML schemas for Annex I

Possible funding:

  • JRC institutional / competitive budget
  • MS funding


MIWP-Action #2419: MIWP-18a: Annex I xml schema updatesWork in progressMichael Lutz

MIWP-Action #2420: MIWP-18b XML schema maintenanceProposedMichael Lutz


#1 Updated by Michael Lutz over 6 years ago

  • Tracker changed from Task to MIWP-Action

#2 Updated by Michael Lutz about 6 years ago

  • Status changed from Submitted to Work in progress
  • Start date changed from 10 Mar 2014 to 01 May 2014
  • % Done changed from 0 to 40
Status 2014-09-04:
  • Tasks MIWP-11/12/18 are documented on the GML encoding wiki
  • A proposal for updating the Annex I xml schemas was discussed at the initial workshop on GML-related issues on 28 May 2014 in Paris and at an ad-hoc meeting at the INSPIRE conference in Aalborg. Based on these discussions, proposed updates of the Annex I schemas were published for consultation and testing until 15 September. The updated schemas are planned to be published in October.
  • There is an open action on JRC to develop a work plan for MIWP-11/12/18 and to propose how actions could be achieved (e.g. through MIG sub-group, contracts, ...)

#3 Updated by Michael Lutz over 5 years ago

  • Description updated (diff)
  • Status changed from Work in progress to Closed

This action was split up into two sub-actions #2419 and #2420.

Also available in: Atom PDF