-
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
Merged
Merged
media type params #202
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
9204695
using limit-type for slim media types
catkins-miso 9954016
add include-psr-header media type parameter
catkins-miso 462b79c
the 1.9 version of webrick has some deps I'm dubious about
catkins-miso c342b44
initial draft of slim usage examples
catkins-miso 9795490
Merge remote-tracking branch 'origin/1.0.0-wip' into 142-media-type-p…
catkins-miso ebb45dc
improve descriptions
catkins-miso ba2abc7
breadcrumb for where the limit-type names come from in the relevant m…
catkins-miso eb82c09
add include-psr-header media type parameter
catkins-miso 0041214
add include-psr-header media type parameter to seasonal snapshot
catkins-miso d0e2800
and input-used examples
catkins-miso e372fbd
add inputs-used media type param to forecast snapshot
catkins-miso 060a6c1
Merge remote-tracking branch 'origin/1.0.0-wip' into 142-media-type-p…
catkins-miso f8069ea
add inputs-used media type param for RT limits snapshot
catkins-miso a87e173
refactor schema to require inputs-used when requested
catkins-miso b149986
sync lock file
catkins-miso File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.