-
Notifications
You must be signed in to change notification settings - Fork 127
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
formal XMIR specification must be generated from the XSD #3375
Comments
@yegor256 @maxonfjvipon Could you take a look, please? |
@volodya-lombrozo we intentionally did it like this (with a blog post) because the format is still rather volatile: we change it once in a while. I suggest we keep it like this, only updating the blog post when something is missing or changing. If you have questions to any parts of the XMIR format, ask them, I will update the blog post. |
@maxonfjvipon in the mean time, can we add a text to all error messages that are related to XMIR:
This will help everybody. |
@yegor256 There are some problems with the blog post:
|
@volodya-lombrozo maybe we can generate documentation right from our XSD: https://stackoverflow.com/questions/237938/how-to-convert-xsd-to-human-readable-documentation |
Sounds cool |
XMIR
Specification
I usually work closely with
xmir
files. So, I need to understand this format to be able to work with it. However, I failed to find any developer specification on this format. It is extremely important to have this specification, otherwise any work withxmir
becomes fortune telling on coffee grounds.As far as I know we have some separate knowledge isles like comments or blog posts (it's written in 2022 btw).
But it's extremely hard to find them. Actually you need to know where to find them. And it is the only chance.
I suggest to create a centralised documentation for
xmir
format.The text was updated successfully, but these errors were encountered: