Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initiating JSON templates #155

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

castelao
Copy link
Member

Proponents:
Moderator: @OceanGlidersCommunity/format-mantainers

Type of PR

  • Typo without possible change of interpretation of the related text.
  • Fix of some error, inconsistency, unforeseen limitation.
  • Style that only affects visually the compiled document
  • Addition that does not require change in the current structure.
  • Enhancement that require changes to improve the format.

Related Issues

Dates when it got review approvals

Release checklist

  • Approved by at least two members of the committee?
  • There were modifications after the review approvals? If so, please
    ask reviewers to update their review.
  • Proponents and moderador should explicitly agree that it is ready to
    to merge.
  • The moderador is the one in charge to actually merge or close this PR
    according to the final decision.

For maintainers

  • Update the moderator with a volunteer from the committee. It would be
    best to have one single moderator to guide and help this PR to move
    forward. It is OK to update the moderador pass it to another one.
  • Confirm that the associated branch was deleted after the merging.
  • Wrap-up and close the related issues.

Comments

@emmerbodc, I used a few json to format and validate Spray data files. Let's build at least one here to reflect the manual. This is not only an excercise to review the manual, but also make it easier for everyone a source to copy-n-paste in their own applications.

It is interesting that it is not clear here it all these attributes are
mandatory. And the most important, it is not clear if the values are
examples or fixed values, i.e. everyone should repeat exactly those
values? For instance, if there is no QC, should the
'ancillary_variables' be ignored?
@emmerbodc
Copy link
Collaborator

@castelao Great, i'll add to this shortly

@vturpin vturpin added the 1.1 Tickets for )G 1.1 release label Feb 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.1 Tickets for )G 1.1 release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants