27.05.2021 Kick-Off Meeting

Teilnehmer

Präsentation

Notizen

Tour de table

  • members: CZ, DE, ES, IT, PL, Helpdesk facilitators, JRC (Marco Minghini, Alexander Kotsev, Vlado Cetl, Lukasz Ziemba, Fabio Vinci)

Introduction, scope & organization of work

organization
  • no mailing list
  • 4 meetings per year before MIG-T meetings
  • next meetings: 01.07.2021, 15 Uhr (only on bug fixes), 16.09.2021, 15 Uhr (all changes)
  • ad-hoc meetings when needed
  • external communications directly in the GitHub issues
tasks of sub-group
  • follow GitHub repositories
  • provide feedback to GitHub workflows if relevant
  • provide feedback on GitHub and in the meetings to change proposals
  • prepare report summarizing change proposals and short presentation for MIG-T Meetings (for endorsement)

Q&A, discussion

  • who can put/change labels? > JRC, helpdesk facilitators
  • change proposals received via other channels in the past will be collected and successively added to the new repositories (by JRC and helpdesk facilitators)

01.07.2021 Status Meeting

Teilnehmende (de)

Notizen

  • workflow and issue template added to TG repository
  • helpdesk facilitators will go through 82 change requests of former Community Forum and add them to GitHub, if still relevant
  • change requests that are already approved don't need to go through the whole process
  • discussion about versioning of schemas and updating UML models → needs to be further elaborated
  • change proposals to schemas and TG (opinion of the sub-group 2.3.1 is documented on GitHub)  

16.09.2021 Status Meeting

Teilnehmende (de)

Präsentationen

Notizen

  • Jordi Escriu (neu beim JRC) will take the lead of sub-group 2.3.1
  • all change proposals regarding schemas approved by INSPIRE CT/MIG-T and by INSPIRE MIG in July 2021
  • release plan: release 2021.2 (planned for summer 2021) was postponed (further discussion on versioning rules needed)
  • TGs können jetzt konvertiert werden (JRC hat halb-automatisches Verfahren entwickelt und erfolgreich getestet)

INSPIRE schemas

  • versioning of schema releases

  • restructuring the schema repository

  • JRC hat lange über die verschiedenen Varianten diskutiert und ist noch nicht abschließend zu einer Lösung gekommen
  • other idea: use Git-version possibilities to maintain schemas (e.g. use branches) → URIs sollen nicht "github" enthalten, sondern die offzielle "inspire" URL → a harmonisation of both approaches might be interesting, e.g. output of latest schemas to official repository
  • discussion will be continued after the meeting

INSPIRE TG

  • discussion on new change proposals
    • issue #6 (issue #1 and #3 closed)
    • issue #2 → add a new requirement instead of a note? sub-group agreed that a change is needed → approved by sub-group
    • issue #7 → guidance just informative (not a recommendation)

AOB

  • use of milestones in github

15.12.2021 Status Meeting

Teilnehmende (de)

Präsentationen / Notizen

Welcome and news on the Action: change proposals endorsed by the MIG, schema release, next steps

  • all change proposals approved by MIG-T and MIG
  • schema release v2021.2 (6 of 7 change proposals included, #7 required additional information)
  • repository has been cleaned and restructured (new folder with previous versions)
  • redirections in some cases were setup to preserve existing implementations
  • issues and pull requests are assigned to milestones, that have been created to plan the changes to be included in each release 

Discussion on new change proposals

Technical Guidance
Application-schemas

Next meeting in March (before next MIG-T meeting)

24.03.2022 Status Meeting

Teilnehmende (de)

  • keine

Präsentationen

13.09.2022 Status Meeting

Teilnehmende (de)

Präsentationen / Notizen

Updates and news on INSPIRE artefacts

  • proposal #60 on XML schemas still pending, comment from AT not received yet
  • other proposals endorsed by MIG-T and MIG have been implemented in release v2022.2 (published on )
  • 1st release of UML models
  • Technical Guidance documents available as GitHub pages and in other formats (PDF, asciidoc, html) → (Info) in the future documents are no longer published in the IKB (will be migrated to another system), only on GitHub

Change proposals on INSPIRE schemas

Change proposals on INSPIRE TGs

Next steps

  • short MIG-T meeting on 7th october, physical meeting on 24/25th november (b2b with MIG in Brussels)

17.04.2023 Status Meeting

Teilnehmende (de)

Präsentationen / Notizen

Change proposals on INSPIRE schemas

Change proposals on INSPIRE TGs

Next steps

  • discussions and voting on the change proposals → next MIG-T on  

10.11.2023 Status Meeting

Teilnehmende (de)

Daniela Witter 

Präsentation

Notizen

News

  • Verordnung zur Änderung der Interoperabilitätsverordnung ist veröffentlicht und tritt am in Kraft → Die davon abhängigen Change Proposals können nun umgesetzt werden.
  • 74th MIG-T meeting: alle Änderungsvorschläge wurden angenommen
  • kein Release der UML Schemata, da alle Änderungen eine Änderung der Interoperabilitätsverordnung bedingen

Implementation of GP on Data and Service Linking Simplification

  • Good Practice zur Vereinfachung der Daten-Dienste-Kopplung wurde angenommen → Umsetzung: Änderungsvorschlag für die TG Metadaten (#108) und in den TG View und Download Services (#105, #110, #112) und neue ATS/ETS für INSPIRE Validator: "Conformance Class 2d INSPIRE Data-Service Linking Simplification Good Practice"
  • Verabschiedung der Änderungen in den TGs durch die MIG(-T) erforderlich? 

Change proposals on INSPIRE Technical Guidance

  • #82 (PR #83) - Auswirkungen auf andere Requirements wurden geprüft und CR und PR entsprechend angepasst → approved
  • #84 - no feedback from MIG-T so far, very specific requirement from one member state with a high impact (changes in the IR required) → no agreement at the moment, further information required
  • #105, #108, #110, #112 - alle Änderungen, die Bezug zum GP zur Vereinfachung der Daten-Dienst-Kopplung haben, haben keine Auswirkungen auf existierende Implementierungen (non-breaking changes) und werden der MIG-T zur Entscheidung vorgelegt mit der Bitte diese bis zur Sitzung in Brüssel dezidiert zu prüfen
  • #115 - no suitable element was found to map the resolution of a raster in an atom feed → CP wird erneut evaluiert, wenn ein konkreter Vorschlag für ein mapping vorliegt

Next steps

  • next MIG-T meeing in Brussels at the end of november
  • next sub-group meeting before MIG Meeting if needed
  • next releases at the end of january 2024

Change proposals on INSPIRE Registry

  • #6 - new attributes to include links to the schema repository and to the UML model → approved
  • #14 - 5 items have no descriptions → approved, but expert input needed for missing descriptions (e. g. European Geological Survey)
  • #28 - on hold, change in TG of natural risk zones is needed first
  • #34 - IR references Interinstitutional style guide → CP rejected, but reference link should be changed (new change proposal to change the link to Interinstitutional style guide and use two-letter codes)

06.05.2024 Status Meeting

Teilnehmende (de)

Daniela Witter 

Präsentation

Notizen

Change proposals on INSPIRE Technical Guidance

https://github.com/INSPIRE-MIF/technical-guidelines/issues?q=is%3Aissue+is%3Aopen+label%3A%22for+Sub-group%22

  • #172 - View Services TG - Deprecate WMS 1.1.1

    • DE: WMS 1.1.1 is still partly used in Germany, as it has proven itself and is considered by some data providers to be more reliable than 1.3.0. Therefore, I cannot agree today.
    • PL: From Polish perspective we prefere WMS 1.3 and don't recomment to use v1.1.1. 
    • DK: I agree with the change proposal.
    • ES: In Spain the WMS INSPIRE services are 1.3.0.
    • IT: In Italy is acepted only 1.3.0.
    • PL: But if some countries use v1.1.1 eg. DE, the TG could be stay without changes and the MS's can decided what version use.
    • Wait for additional feedback. DE will add some further explanation to the ticket.
  • #173 - LU - Correct broken link
    • sub-group approved change proposal - trivial change, can be changed without further vote of MIG/MIG-T
  • #174 - GE - Major update of TG to version 3.3
    • sub-group approved change proposal, pull request on concrete changes will be provided for the next MIG-T Meeting
    • corresponding changes in the registry, schemas and validator

Change proposals on INSPIRE Schemas

https://github.com/INSPIRE-MIF/application-schemas/issues?q=is%3Aissue+is%3Aopen+label%3A%22for+Sub-group%22

  • #123 - PF_Link from ProductionSite to ProductionFacility is missing
    • DK: no mistake, information is in the data itself
    • JRC: If not wrong INSPIRE D2.5 was recommending only unidirectional relationships.
    • more evidence needed, DK will add a comment

Change proposals on INSPIRE Registry

https://github.com/INSPIRE-MIF/helpdesk-registry/issues?q=is%3Aissue+is%3Aopen+label%3A%22for+Sub-group%22

  • intermediate release 2024.1b (changes derived from the amendment of interoperability regulation
  • #92 - add CRS EPSG:3794 to the list of accepted CRS, consider adding EPSG:4326 as well
    • JRC: EPSG:4326 should NOT be added
    • sub-group approved change proposal
  • #84-#87 - translation issues DE
    • sub-group approved change proposals
  • #17 - add 2 new items in the Protocol Value code list
    • sub-group approved change proposal
  • #71 - the code list for the country codes has to refer to the Interinstitutional style guide
  • #28 - INSPIRE layer register
    • IT: change of technical guidelines not necessary
    • go ahead with the change proposal, but not foreseen for the next release
  • #21 - inconsistencies
    • JRC propose not to correct this minor inconsistencies (too much effort and minor benefit)
    • sub-group agreed to reject change proposal

Announcements

11.11.2024 Status Meeting

Teilnehmende DE

Daniela Witter 

Notizen

Change proposals on INSPIRE Registry

https://github.com/INSPIRE-MIF/helpdesk-registry/issues?q=is%3Aissue+is%3Aopen+label%3A%22for+Sub-group%22

  • #103 → would have no impact on existing implementations
  • #28
  • #98
  • #99

sub-group approved all change proposals on INSPIRE Registry (changes will be included in next release on January 2025)

Change propsals on INSPIRE Technical Guidance

https://github.com/INSPIRE-MIF/technical-guidelines/issues?q=is%3Aissue+is%3Aopen+label%3A%22for+Sub-group%22

  • #172 → additonal feedback? What does deprecation really mean? Definition would be added to the issue (will be discussed further in the upcoming MIG-T meeting)
  • #175 → rejected by sub-group
  • #192 → accepted by sub-group, but IR shall change first, maybe as a corrigendum (JRC will check)

Change proposals on INSPIRE Schemas

https://github.com/INSPIRE-MIF/application-schemas/issues?q=is%3Aissue+is%3Aopen+label%3A%22for+Sub-group%22

  • #123 / #126 → was already discussed and rejected, but further comments proposing to remove the association roles from the UML (for clarification) → proposal: keep it in the model and hide it in the diagram → agreed by sub-group, no vote by MIG-T needed (for information only)
  • #131 → non-breaking change → accepted by sub-group

MIG Work Programme: Action 2.3.1 should be continued (transition period 2025/2026) → Decision in the next MIG Meeting on November 28







Datenschutzerklärung | Impressum | Nutzungsbedingungen