-
Notifications
You must be signed in to change notification settings - Fork 45
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
document client feature support #71
Comments
This would be great to have! |
Agreed, great idea! This table is already useful to point to (and have the information collected). I especially like how the links in the table above provide a nice preview prior discussion. I guess the question is whether it should live under a separate domain/site (e.g. |
https://github.com/ome/ngff/blob/main/caniuse.md would be one option. Another might be https://nicolas-van.github.io/easy-markdown-to-github-pages/ 👍 for getting something in place ASAP. cc: @tischi |
As the spec evolves, it's increasing likely that there will be parts of it that are not supported by all the clients, either because of technical limitations or the work just hasn't been done/released.
It would be really nice for new and existing users to be able to see what is supported by which clients, or what's NOT supported (without having to search the issues of each repo). This would also be a nice way to show what clients are available to view OME-NGFF data.
I'm thinking of something like a support table, similar to e.g. https://caniuse.com/flexbox (although in that case it's a table for a single feature, with different versions of each tool). I'd suggest we limit it to documenting only the latest release of each tool.
If this looks like a popular idea, where would this doc/table live? Include it in the spec page, or a doc page on this repo?
The text was updated successfully, but these errors were encountered: