-
Notifications
You must be signed in to change notification settings - Fork 2
Issues: trolie/spec
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
doc bug catch-all for tasks not associated with spec changes
emergency-operating-limits
description
Task
remove Track specific spec changes ideas until they are complete. Should be placed into a milestone.
resource-id
from proposals-considered
as it is redundant with source.origin-id
Spec Change
document and test forecast proposal validation rules
Task
catch-all for tasks not associated with spec changes
add optional Inquiries that we want to have a record of for future reference. Can turn into "Spec Change" issues.
day-night
from Seasonal proposals and snapshots to Seasonal Overrides?
Discussion
improve catch-all for tasks not associated with spec changes
period
RFC 3339 timestamp docs in spec
Task
optional 'inputs-used' in slim proposals
Discussion
Inquiries that we want to have a record of for future reference. Can turn into "Spec Change" issues.
extended details in forecasts for time-bound static ratings
Discussion
Inquiries that we want to have a record of for future reference. Can turn into "Spec Change" issues.
limit "analysis type"
Discussion
Inquiries that we want to have a record of for future reference. Can turn into "Spec Change" issues.
conventional naming for differing emergency durations on a jointly owned facility
Discussion
Inquiries that we want to have a record of for future reference. Can turn into "Spec Change" issues.
extraneous elements are permitted due to use of Inquiries that we want to have a record of for future reference. Can turn into "Spec Change" issues.
allOf
Discussion
#162
opened Sep 14, 2024 by
catkins-miso
add "quality" indicator(s) to ratings proposals and limits provenance
Discussion
Inquiries that we want to have a record of for future reference. Can turn into "Spec Change" issues.
Forecast RC-to-RC reconciliation
Discussion
Inquiries that we want to have a record of for future reference. Can turn into "Spec Change" issues.
consider making names header optional in snapshots
Discussion
Inquiries that we want to have a record of for future reference. Can turn into "Spec Change" issues.
#142
opened Aug 19, 2024 by
catkins-miso
normalize element name for all uses of data-provenance.yaml
Discussion
Inquiries that we want to have a record of for future reference. Can turn into "Spec Change" issues.
#140
opened Aug 19, 2024 by
catkins-miso
add kV as optional to Current type
Proposal
Proposals should both have a label and an issue title of "Proposal: ____". Can become a Spec Change.
Proposal: change Proposals should both have a label and an issue title of "Proposal: ____". Can become a Spec Change.
incomplete-ratings-obligations
--> unsatisfied-ratings-obligations
Proposal
#104
opened Apr 22, 2024 by
catkins-miso
Previous Next
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.