Skip to content
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

Ranges of parameters : where do they come from ? #85

Closed
Bonnarel opened this issue Nov 18, 2021 · 1 comment
Closed

Ranges of parameters : where do they come from ? #85

Bonnarel opened this issue Nov 18, 2021 · 1 comment

Comments

@Bonnarel
Copy link
Contributor

Bonnarel commented Nov 18, 2021

In the discussion of PR #83 recently merged in master this comment I made a couple of days ago was not adressed. This is not blocking for publishing the WD 1.1 but I would like this discussed before RFC

Hence, I'd say this should read: "To allow for expressive, usable user interfaces, operators SHOULD indicate useful ranges of parameters in MIN and MAX children or, for enumerated parameters, indicate the valid values in OPTIONS." Or something like that.

This was discussed in the past. In case you come from ObsCore, SSA, SIA and the service is SODA or SODA-like the values can be inferred from the dataset metadata. In general we don't need to repeat that in VALUES. So I suggest to add these words to Markus sentence after "OPTIONS" : , "in case these values cannot be inferred from relevant metadata retrieved before the service descriptor discovery".

@Bonnarel Bonnarel changed the title Ranges of parameters : where do the come from ? Ranges of parameters : where do they come from ? Jan 5, 2023
@Bonnarel Bonnarel closed this as completed May 4, 2023
@Bonnarel
Copy link
Contributor Author

Bonnarel commented May 4, 2023

change has been merged with PR#100

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant