We should distinguish the endpoints for history-based use-cases and real-time ones for topology and capacity

carbon-data-specification / Power-Systems-Data

This repository is dedicated to the Power Systems Data Working Group

Other

10 stars 8 forks source link

We should distinguish the endpoints for history-based use-cases and real-time ones for topology and capacity #101

Open Pierre-VF opened 6 months ago

Pierre-VF commented 6 months ago

History-requiring use-cases are still unclear at the moment, while real-time ones drive the current spec.

We should maybe explicitly distinguish these in the spec, and make it clear that we're looking for specific use-cases that would motivate the collection and sharing of historical topology/capacity/availability (most likely around MRV and additionality)