opengeospatial / opengeospatial/timeseriesML

"Supporting and contributing organizations and projects" section

Open
#19 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
2
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Inspired by this STA Issue

Currently the spec has no "Supporting and contributing organizations and projects" section.

Suggestion to mimic the OMS approach (https://docs.ogc.org/as/20-082r4/20-082r4.html) with its 'Supporting and contributing organizations" section and extend its target to also embrace 'projects'.

Several side projects (research ?but maybe not only?) have made contribution on that update possible. They deserve to be mentioned.

This could also help highlighting to funding organisation that playing the collective game is helping the community

Thinking on which organizations projects and initiatives fed into TSML:

  • Organizations:
    • BRGM
    • Datacove e.U.
    • Fraunhofer IOSB
    • NOAA
    • WMO
  • Projects:
    • Water4All Partnership (European Union's Horizon Europe Programme under Grant Agreement 101060874)
    • OneWater Data French Research project (ANR-22-PEXO-0009)
    • WMO TT-W2FH WHOS work... (what is this really called?)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the TSML specification source and reviewing the OMS supporting and contributing organizations section linked in the issue. Confirm the names and wording for the listed organizations, projects, and the WMO initiative with the project context. Done means the specification includes a clear section covering both supporting organizations and contributing projects.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.