Points agreed from the meeting of 15 December 2009 : (out of an Email from Jeremy of the 12 Junuary 2010)
During this meeting, we agreed a number of points that provide scope to our activities:
- that our objective is to exchange data easily between communities including: operational meteorology, aviation, INSPIRE, climate & atmospheric scientists
- that we should use topology to classify / categorize our domain model ... extending this to enable description multiple members of a single ensemble analysis
- that rights management / ownership and quality management were becoming increasingly important factors to our community of interest
- that we should focus on a 're-usable core' of feature types that can be specialized as necessary for use within domains that stricter controls over data exchange (such as operational meteorology within aviation)
Furthermore, we agreed to use the INSPIRE methodology for developing our conceptual model. This is detailed in INSPIRE document D2.6 (http://inspire.jrc.ec.europa.eu/reports/ImplementingRules/DataSpecifications/D2.6_v3.0.pdf
The first step in the methodology is to develop the use-cases for interoperability.
I propose that the main body of this meetings discussion should focus on identifying the target use-cases that we will use to develop the conceptual model.
From a WMO perspective, I note that there is a compelling need to focus on the development of data models required to enable retirement of 'traditional alphanumeric codes' [TAC] within Aviation OpMet
that are compatible both with existing 'table driven code forms' [TDCF] and ISO TC/211 conceptual model for geospatial information. The target here is to demonstrate to WMO CBS in Dec 2010 that the correct approach is being adopted - we do not need to have completed development of the complete conceptual model! Whilst considering replacement of TAC, we must also look to the future for Aviation OpMet
, suggesting a move away from exchanging data products
to facilitating the extraction of data from 4-dimensional (x, y, z & T) 'data-cubes' for input alongside other aeronautical information into, say, flight routing algorithms.
I also note that INSPIRE has a milestone to complete the development of version 1 of the Annex 3 theme data specification by 2010Q4.
/ NNEW and SESAR are also likely to have milestones in place.
The goal of the meeting will be to establish a candidate set of use-cases to develop the conceptual model against. If insufficient stakeholders are present to agree the list of use-cases then we will attempt to identify stakeholders to review the list offline.
It is important to gather additional proposals from members of the community to ensure that the use-cases are representative of our concerns.
1) Update on actions
2) Update on selection process for INSPIRE Thematic Working Groups
3) Discussion of use-cases to drive development of conceptual model
4) Any other business
5) Arrangements for next meeting
Hope to hear you at the telcon. Many thanks for your continued participation.
- 12 Jan 2010