-
Notifications
You must be signed in to change notification settings - Fork 41
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
Publish 0.4 specification #97
Conversation
I think two items are good here, because the changes to the multiscales and the hcs spec are unrelated. |
<td>multiscales: add axes type, units and coordinateTransformations</td> | ||
</tr> | ||
<tr> | ||
<td>0.4.0</td> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd be for combining the two rows.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I see @constantinpape was for the opposite. Hmm.... happy to look into it later. (Also need to look into removing the "W3C" in the versioned pages)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have a strong opinion here. Maybe we could start to introduce sub-points? like
- v0.4
- multiscales: ...
- high-content-screen: ...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW, I am not the biggest fan of the double row either but I was hoping someone would come with an authoritative suggestion 😄
In the absence of a strong consensus, I'd be inclined to not delay the publication of the spec and capture this as an issue to investigate. We will certainly face similar cases in the future and it would be good not to be constrained in terms of what we want to document.
See #86.
Follows the release steps mentioned in https://github.com/ome/ngff#release-process.
Happy to take suggestions on the wording and the rendering of the version history block. Previously we had one item per version but there were more changes in 0.4.0
See http://api.csswg.org/bikeshed/?url=https://raw.githubusercontent.com/sbesson/ngff/0.4_publication/0.4/index.bs for a rendered version of the page