Define required and recommended vocabularies

[amilan17]

• Require WMDS Domain
• Require WMDS ObservedParametersXYZ
• Recommend other vocabularies -- should we add a list known vocabularies?
• what other fields should have controlled vocabularies? Contact > organization, formats, ...?

This will support faceting (see #100)

[tomkralidis]

• initial WCMP2 codelists: https://github.com/wmo-im/wcmp2-codelists
• WCMP1 codelists: https://github.com/wmo-im/wcmp-codelists
  • needs analysis of what can/should be ported to WCMP2 codelists

[tomkralidis]

TT-WISMD 2023-06-09:

• need to clarify "codelist" vs "controlled vocabularies"
• update themes/concepts:
  • REQUIREMENT: when describing observations, use WMDS ObservedParameters*
  • REQUIREMENT: use domain/discipline
    • ACTION: @amilan17 review relationship between WMDS Domain and WTH earth-system-discipline
• what about formats?
  • may become difficult to manage across communities?
  • users should search for content/data
  • data (via search results) can be provided in a number of formats/representations
  • example: BUFR/GRIB need formal media types
    • register BUFR MIME type with IANA BUFR4#140
    • register GRIB MIME type with IANA GRIB2#175
• data policy
  • realized via properties.wmo:dataPolicy enumeration

[amilan17]

mapping of domain/discipline/application areas in ppt.
codesMapping.pptx

[david-i-berry]

We have a related requirement in TT-CDM and will be discussing at our next meeting.

[tomkralidis]

TT-WISMD 2023-07-07:

• start with requirement for WMO data policy CV
• @tomkralidis to PR

[tomkralidis]

PR in #113

[amilan17]

• REQUIREMENT: when describing observations, use WMDS ObservedParameters*

@tomkralidis Did we decide to include this requirement? I can't find it in the WCMP2 specification....