Supporting European Aviation SWIM COI Walter Van Hamme

Supporting European Aviation SWIM COI Walter Van Hamme, Scott Wilson EUROCONTROL 20 Jul 2020

Supporting European Aviation Service Description Schema task

regular technical sessions Service Description Schema task 20 th Jul’ 20 Context • Schema context - Inputs, objectives • Schema resources - Links, tooling, terminology, tips • Schema requirements - List of reqts for schema • Intentions with Service Overview - Formalises our intentions Object under assessment • Schema releases – schema used for operational registry Outcome 1 = improved validation • JSON Schema 0. 0. 3 - 3 f (fully aligned with guidance) Outcome 2 = guidance material a) Guidance starting from the schema: • Guidance starting from schema • • • guidelines, rules, links, and notes for evolutions JSON Service Descriptions ; JSON Donlon example Guidance on spec requirements • JSON guidance added to spec reqts Guidance on non-spec requirements • for conformance with Service Description spec Schema comments - discussed answered Schema walk-through - walk through all elements with Integrated within Service Description Handbook. b) Guidance starting from requirements: • Guidance for JSON service descriptions - Entry point • Approach to the task • Approach to the task - 3 threads & 3 cases. • Registry JSON Schema 0. 3 - assessment Complete JSON guidance for other reqts (eg Registry or Serv Overview) Outcome 3 = evolution (for review/approval by Registry CCB) • Schema evolution - proposed evolution for a future release grouped in sections that would become Change Requests Complete • Early draft schema + Draft Example – TBC (eg behaviour) 3

JSON Schema task Current schema Schema Evolution • • SSCONE role • Support in self-validation • New schema editions (. 3 x) • • • Gap, justification, guideline, … add validation capability no impact on structure or Registry can be ignored if no interest in self-validation • • Support in using the schema Registry role • Corrective maintenance • Loose-coupled from this task, but can benefit from (inconsistencies & understanding) Draft new version of the schema • Impact structure and validation rules Coordinate with Registry CCB • Registry review and approval process • Common understanding • Guidance material • Example • Identify schema evolution • Support stakeholders • Intention of conversion tool • Registry role • Evolution maintenance • Review and approve the proposed new schema • Implement the new structure and rules 4

Schema Evolution - steps Schema Evolution - roles • • Summer 2020 • • Later on • Deprecate schema 0. 0. 3 Coordinate with Registry CCB • Registry review and approval process Process comments on schema evolution Updated version of schema evolution Release new schema version Update guidance Draft new version of the schema • Impact structure and validation rules Review and/or approve • Support stakeholders • Intention of conversion tool When approved • • Identify schema evolution • Gap, justification, guideline, … When comments • • Finalise Schema evolution Propose it to Registry CCB Sep 2020 - Registry CCB meeting • SSCONE role • Registry role • Evolution maintenance • Review and approve the proposed new schema • Implement the new structure and rules 5

Supporting European Aviation Retrospective

Specification for SWIM Service Description Implementing the spec Getting the spec Prevalidation Phase Drafting Spec Kick. Off Spec Publication Needs Initial Supporting Material (context, guidance, conformance, example) Advice CR processing Practical Sup. Mat. (integrated guidance for JSON Schema 0. 0. 3, schema evolution) Feb’ 18 Jun’ 16 2016 SSCONE SWIM Service Community of Interest Review of Comments Phase Consultation Phase 2018 2017 Jun’ 18 2020 2019 Aug’ 18 Specs Evolution Workshop Dec’ 19 Jul’ 20 retrospective SWIM COI Kick. Off today 7

Initial Goals slid ef rom De c 20 19 • Develop supporting material to ensure that the SWIM Specification for Service Description / Information Definition is: • Understood by users in a similar way; • Supported by examples; • Used effectively • Make the developed Supporting Material available 8

Retrospective - achievements slid ef rom De c What was done? What was not done? working together • Collaboration tool for the SWIM Community • Regular meetings with a mix webex and F 2 F SSCONE • discuss & develop practical aspects of spec implementation such as format of the SD (Template and/or Schema) and service categories • some tasks not finalised • effective use of the spec • • • initially separated, now joint + “Get into SWIM” session + “SWIM implementation” workshop 20 19 sharing experience (ASM, MET, workshop) output • Advice provided on handling Change Requests • SWIM Supporting Material developed and published • • SITCOM • effective use of the spec Service Description Handbook 1. 0. 0 with guidance on some requirements, an example, and clarifying conformance assessment Information Definition Handbook 1. 0. 0 with … Better Practices… 9

Retrospective – assessment slid ef What was done? What was not done? working together: Collaboration tool + Regular meetings Output: Advice on CR + SWIM Supporting Material developed and published SSCONE: practical aspects ; tasks not finalised ; effective use of the spec SITCOM: effective use of the spec What went well? What could be improved? • • • Comments addressed rapidly and efficiently. Proper dialogues took place. Confluence helped with this. Handbook really helped with learning SWIM. Provide your input on working together & output on subjects & objectives • • rom De c 20 19 more practical examples (incl. encountered difficulties; effective implementation) JSON and registry took people by surprise – structure is different from the XSD but no mapping was provided. Poor communication. Need JSON examples in the Handbooks. Coordination with the other groups e. g. registry, AIRM CCB. Still have SWIM stove-pipes. Make the COIs better known e. g. let’s mention them at future workshops as the place to work. Level of engagement 10

SSCONE Activities • rom De c 20 19 support MET services … ? support other services …? Being more practical • • • ef Support effective implementation • • • slid Work on going in Registry service description format (template / Schema) service classification / categories More ? • service definition • provider agnostic service descriptions that facilitate alignment and interoperability in the implementation of services • prospective service • guidelines for describing services that are not operational yet (~candidate service) • other ideas? 11

Next steps • More focussed on specific implementations • Only when we have sufficient implementations should we revise the guidance/specifications 12