constantinpape / ngff

Next-generation file format (NGFF) specifications for storing bioimaging data in the cloud.

Home Page:https://ngff.openmicroscopy.org

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

ome-ngff

Next-generation file format (NGFF) specifications for storing bioimaging data in the cloud.

Editing

Specifications are written in markdown, or technically bikeshed -- a markdown document, with special extensions understood by the bikeshed tool. The bikeshed tool is run on-commit via the spec-prod github action, generating the familiar "spec looking" ReSpec format. ReSpec is just html with a javascript ReSpec library.

Specification files end with the .bs file extension. The github action runs on commit to automatically convert to respec/html, via bikeshed.

Learn more about bikeshed

Reviewing

Commits on GitHub can be viewed using web services from the W3C:

New version

  • Make new changes to latest/index.bs
  • Update changelog at the bottom of latest/index.bs
  • Find references to previous version and in most cases, bump to the current version.

Release process

  • copy latest/index.bs to $VERSION/index.bs
  • copy latest/copyright.include to $VERSION/copyright.include
  • update the head matter in the $VERSIONed file
    • Use: Status: w3c/CG-FINAL
    • Update URL:
    • Use the following Status Text:: "This is the $VERSION release of this specification. Migration scripts will be provided between numbered versions. Data written with the latest version (an "editor's draft") will not necessarily be supported."
  • update the footer matter in the $VERSIONed file
    • Version in the citation block including release date
  • Update https://github.com/ome/spec-prod for the new version

Citing

Please see https://ngff.openmicroscopy.org/latest#citing for the latest citation.

About

Next-generation file format (NGFF) specifications for storing bioimaging data in the cloud.

https://ngff.openmicroscopy.org

License:Other


Languages

Language:Python 97.9%Language:HTML 2.1%