Refining the CDMS specification Bruce Bannerman Australian Bureau
Refining the CDMS specification Bruce Bannerman Australian Bureau of Meteorology e-mail: b. bannerman@bom. gov. au Co-Chair Expert Team – Climate Data Management Systems, Commission for Climatology ET-CDMS, Geneva, 04 -07 November 2014
Current Version of CDMS Spec • Is intended to provide a strategic vision • Refers readers to many other references – Need to balance: • Self-contained stand-alone doc, versus • References to authoritative sources • Sufficient detail is provided to: – support a primary evaluation of CDMS current state capabilities – commence business case, planning and IT architecture activities 2
Current Version of CDMS Spec • Not sufficient detail to: – Remove ambiguities in different WMO guidelines • e. g. rules on missing values – commence software development – describe use cases of how the CDMS is to be used – describe how components are intended to interact 3
Work required for CDMS Spec • Expand refine each component. Ensure that it – contains the best information available – is not ambiguous – Describes the requirement in a clear, concise and consistent manner – is stand alone and does not direct reader to other documents – retains the lineage to the source document to facilitate maintenance of the spec, should the source change – Contains relevant use cases and swim lanes to describe the intended use and inter-relation ship of the component(s) – Contains sufficient technical detail to support IT development 4
Work required for CDMS Spec #2 • Define requirements for defining the source of data – Formal NMHS data – Informal data, e. g. Crowd Sourced data • Climate Metadata – Ensure that Observations Metadata is covered by WIGOS Metadata Standard • If not, Define Climate Profile of WIGOS Metadata Standard Review WMO Core Profile of ISO 19115 Discovery Metadata • Consider implications of CDMS Spec Climate Metadata • Is a Climate Profile of WCMDP now required to cover Data Provenance Metadata and Observations Metadata linkages? – Define what we want in Data Provenance Metadata 5
Prioritise work • Prioritise work on ‘Required Components’ – Need to support: • Developing Countries • CDMS Developers • Therefore we will need early deliverables • How do we allocate and coordinate work? 6
Version Management • Start with MS Word version of WMO No. 1131 used by WMO Editor • Use: – MS Word 2010 (Windows) – MS Word 2011 (Mac) – Track Changes • Version numbering – Use file naming convention 7
- Slides: 7