Ihre Favoritenliste enthält derzeit keine Seiten. Sie fügen dieser Liste Seiten hinzu, indem Sie im Menü Extras der angezeigten Seite Favorit selektieren.
TG conversion into formats manageable on GitHub in progress (fully automated conversion not possible)
TG: template for issues not yet available
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)
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)
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) → in the future documents are no longer published in the IKB (will be migrated to another system), only on GitHub
no need to change either XML schema or UML, but conclusions should be shared with the community → change proposal will be closed and new discussion issue in the generic INSPIRE helpdesk (new category) will be created
no change proposal anymore, but recommendation/workaround → this change proposal will be closed and new change proposal to add this recommendation in the TG and new discussion issue in the generic INSPIRE helpdesk (new category) will be created