Ongoing discussions within the SWIM communities of interest
Ongoing discussions within the SWIM communities of interest
This page is part of the ongoing SWIM communities of interest discussions. The content is working material. It should not be treated as final as it is still subject to review, comment and change.
This task will look after the maintenance of the supporting material including when to add new content to the "reference" website.
Benefit from the evolution of the other supporting material
E.g. role of the SWIM SRV Spec can be used as inspiration for updating the "Introduction to" the spec page.
|The group will develop a new diagram to better reflect the role of the specification. SINTEF and EUROCONTROL to lead.||Not Started||2||Sprint 2|
After simplifying the scope statement it is now possible that it is too simple. It does not say what information is include. Basically it says "this scope of the service is this service"...
|To be discussed in SSCONE||Not Started||1||Sprint 2|
|23||Information||update standard's version number|
The ISO 2005 standards referenced here have all be withdrawn and replaced with 2011/15 versions? Should this change be reflected.
However, ISO 19103:2005 is used in the AIRM and in AIXM. That version of the standard seems pretty "hard-coded" for the moment. There is a need to talk to the various communities in order to move. However, hopefully there is no fundamental change between versions on what a boolean, etc. is. Likewise, hopefully, the conversion rules would be unaffected.Is anybody able to check that?
|Not Started||1||Sprint 2|
|28||Services||JSON guidance to reference||The JSON schema guidance is available in the supporting material. We need to decide when it is mature enough to be stamped as "reference".||Not Started||2||Sprint 3|
|29||Services||Geographical extent||Add content of Geographical extent change proposal once the new version of schema is published||Not Started||-|
|30||Services||Service categories||Add Using Service Categories once new version of the specification is published||Already live as has no negative impact even with current version of the specification.||Completed||-|
|31||Services||Abstract||The expected content of the abstract should be made more explicit in the supporting material including the mapping to other fields. Based on the new best practice and expected service overview content/||Not Started||-|
|32||Services||Relations between certain elements|
Add clarification of the relationships between e.g.:
|33||Services||Structural aspects of services||Add a matrix to show how interface, operation, message are used.||Not Started||-|
|34||Services||Data formats||Add guidance on how to list different types of data format e.g. GRIB2. Also clarify how this relates to the various requirements looking for "standards" e.g. service standards, information definitions.||Not Started|
|35||Services||Clarification on service level agreements||Add guidance on how the content of a service description relates to service level agreements.||See Formal Arrangements - Service Level Agreements||Completed|
Table widths are not consistent. Some do not seem to respond to a reduced window size:
SWIM-INFO-014 cannot be made smaller due to the length of the urn.
The rest of the tables have been made responsive so will match the window size.
|2||Continue to add examples|
Add an example of an information definition as it could appear in a service description using
|4||Identification of best practices||Ongoing process where the community decides that something should become a best practice.|
See 15 and 27 for current work.
This has been moved to a separate activity as it is beyond simple maintenance.
|5||Annotation of the Donlon example|
Annotating the Donlon example would make it clearer which parts of the specification are satisfied by which parts of the example.
Reviewing Donlon Example: Overall the example is very comprehensive and I think really useful for advanced users. But for an introduction to the topic (especially coming from a non-aviation point of view - like me) it is huge, in particular in combination with the Service Description part and/or when using the XML format. I think it could be helpful to add some more comments which SWIM-INFO parts are covered. In the XML example there are some comments for the information definition level (SWIM-INFO-003 to 005) but not below. What really helped me was the fact that there are more formats (not just xsd/xml but also data catalogue)! In combination with the Service Description point of view many things became clearer. So this is something I would definitely keep in the evolution/updates.
|6||Reference AIRM Community||Add a reference to the AIRM Community to SWIM-INFO-014 and the "Using the AIRM" page. This gives the obvious links to where to raise change requests on the AIRM.||Completed|
|7||ISO 19115 examples|
Show how to meet the requirements using ISO 19115 metadata standard.
|No priority to be given to this just yet.||Moved|
|8||out of dates urn||update urns and examples to use v1.0.0 of the AIRM||Completed|
|12||metadata standard comments||https://ext.eurocontrol.int/swim_confluence/display/SWIM/SWIM-INFO-011+Semantics+of+metadata||Completed|
|13||information exchange comments||See: https://ext.eurocontrol.int/swim_confluence/display/SWIM/Introduction+to+the+information+definition+specification||Completed|
|15||element names used to record the fields required by the specification|
This task grew out of the comments found on:
|This has been moved to a separate activity as it is beyond simple maintenance.||Closed|
|16||reuse of standards||Merged with 15 above.||Completed|
|17||clarification of "dedicated"||https://ext.eurocontrol.int/swim_confluence/display/SWIM/SWIM-INFO-006+Information+definition+namespace||Completed|
|18||improvements to SWIM-INFO-007||https://ext.eurocontrol.int/swim_confluence/display/SWIM/SWIM-INFO-007+Information+definition+concepts||Completed|
|19||stronger unique identifier||https://ext.eurocontrol.int/swim_confluence/display/SWIM/SWIM-INFO-008+Unique+identifiers+for+concepts||Completed|
|20||preservation of "name"||https://ext.eurocontrol.int/swim_confluence/display/SWIM/SWIM-INFO-009+Preservation+of+meaning||Completed|
|21||principles for good definitions||https://ext.eurocontrol.int/swim_confluence/display/SWIM/SWIM-INFO-010+Principles+for+definitions+for+concepts||Completed|
|22||example of metadata semantics||https://ext.eurocontrol.int/swim_confluence/display/SWIM/SWIM-INFO-011+Semantics+of+metadata||Completed|
|24||clarification on the xml elements used||https://ext.eurocontrol.int/swim_confluence/display/SWIM/SWIM-INFO-014+Forms+of+semantic+correspondence||Completed|
|25||namespaces in non XSD||https://ext.eurocontrol.int/swim_confluence/display/SWIM/SWIM-INFO-006+Information+definition+namespace||Completed|
|26||publication and management of info. defns.||https://ext.eurocontrol.int/swim_confluence/display/SWIM/SWIM-INFO-001+Need+for+information+definitions||Completed|
|27||Differentiating the traces||Better understanding/differentiating the types of traces to the AIRM||This has been moved to a separate activity as it is beyond simple maintenance.||Closed|