Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
/ngffPublic
generated fromw3c-ccg/markdown-to-spec

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

License

NotificationsYou must be signed in to change notification settings

ome/ngff

Repository files navigation

DOI

ome-ngff

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

Editing

Specifications are written in markdown, or technicallybikeshed -- a markdown document, withspecial extensions understood by the bikeshed tool. The bikeshed tool is runon-commit via thespec-prod github action,generating the familiar "spec looking" ReSpec format. ReSpec is just html witha javascript ReSpec library.

Specification files end with the .bs file extension. The github action runs oncommit 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 tolatest/index.bs
  • Update changelog at the bottom oflatest/index.bs
  • Find references to previous version andin most cases, bump to the current version.

JSON schemas

For each top-level metadata key of the OME-NGFF specification, JSON schemas are maintainedfor each version of the specification and stored under$VERSION/schemas/ orlatest/schemas/.Tests validating these schemas must be implemented to follow principles of theJSON schema test suiteand stored under$VERSION/tests/ orlatest/tests/ to allow their execution on each CI build.

All official example snippets must also be extracted and managed as separate JSON files under$VERSION/examples/ orlatest/examples/, validated by the appropriate schema by adding a.config.json file specifying the JSON schema to use and included in thespecification document using theinclude-code directive.

The official OME-NGFF JSON schemas are published underhttps://ngff.openmicroscopy.org//schemas/<schema_name>.schema using theSpec prod GitHub action. When a new JSON schema is introduced,this action needs to be reviewed to update the deployment script and allow the publicationof the schema.

Release process

  • copylatest/index.bs to$VERSION/index.bs
  • copylatest/copyright.include to$VERSION/copyright.include
  • update the head matter in the$VERSIONed file
    • Use:Status: w3c/CG-FINAL
    • UpdateURL:
    • Use the followingStatus 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
  • Updatehttps://github.com/ome/spec-prod for the new version

Citing

Please seehttps://ngff.openmicroscopy.org/latest#citing for the latestcitation.


[8]ページ先頭

©2009-2025 Movatter.jp