-
Notifications
You must be signed in to change notification settings - Fork 2
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
media type params #202
media type params #202
Conversation
…edia type parameter
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.
This needs to be expanded, and I will do so under #155, but this is already way too much for one PR.
<<: *forecast-limit-snapshot | ||
description: | | ||
A slim snapshot of the forecast for a monitoring set, including the inputs | ||
that were used to determine the continuous limits. |
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.
@getorymckeag Please take particular note of this: continuous limits. The issue is that different providers can potentially set continuous versus emergency limits, so a single input for each period's rating set might be insufficient. Since this is about creating situational awareness in interop, I felt the compromise of only guarantee the input was associated with the continuous limit was worthwhile.
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 think this is fine. I am having trouble imaging a scenario where the inputs are actually different. It would be kind of strange to have a weather measurement that is used to generate an emergency rating but NOT a continuous rating. While the inverse seems at least possible (maybe ignore some more "exotic" cooling factor?), the difference for emergency limits and continuous is really an internal of the TO's rating methodology, and I would think is something market monitors could work with the TO to simply rederive from the available continuous input + equipment characteristics if they really wanted to.
<<: *forecast-limit-snapshot | ||
description: | | ||
A slim snapshot of the forecast for a monitoring set, including the inputs | ||
that were used to determine the continuous limits. |
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 think this is fine. I am having trouble imaging a scenario where the inputs are actually different. It would be kind of strange to have a weather measurement that is used to generate an emergency rating but NOT a continuous rating. While the inverse seems at least possible (maybe ignore some more "exotic" cooling factor?), the difference for emergency limits and continuous is really an internal of the TO's rating methodology, and I would think is something market monitors could work with the TO to simply rederive from the available continuous input + equipment characteristics if they really wanted to.
closes #142