You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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".
The text was updated successfully, but these errors were encountered:
Bonnarel
changed the title
Ranges of parameters : where do the come from ?
Ranges of parameters : where do they come from ?
Jan 5, 2023
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
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".
The text was updated successfully, but these errors were encountered: