-
Notifications
You must be signed in to change notification settings - Fork 31
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
GeneralSOS convention missing #39
Comments
Good idea. I note that for the standard... |
Sounds good - I'll try to find time for a draft before the next standards meeting :) |
Hi! Just a question: is there any data for GeneralSOS? I ask because we're following the idea that we create conventions only for data which exist... |
Nothing I have in mind. In this case I thought it would be nice to have a complete set of General* conventions. But I am also fine with leaving it as a pull until a use case emerges. |
Pleas re-open this topic once data is available. |
I have a vague memory that we said we wanted to have this for completeness in this case, without data but I'm not sure. @petibub do you remember? I'm fine with both anyhow |
Sorry, I did not realize that this is the issue not the pull. In the pull we agreed to include it in API_MO: #41 |
I noted that there is no
GeneralSOS
convention. It would be consistent to have it and fairly easy to generate, and it could easily be verified using sofar. Should we add it?The text was updated successfully, but these errors were encountered: