Frederik

That's great. Excited about all the features JuMP 0.19 is going to offer!

We may want to start with including energy, and time symbols [here](https://lanl-ansi.github.io/PowerModels.jl/stable/developer/), define suffixes for all entities (e.g.`g` for generators), map these names to the [parameters and variables](https://lanl-ansi.github.io/PowerModels.jl/stable/storage/) and define...

In favor of being explicit in terms of power and current for ratings instead of 'thermal'. (A thermal limit eventually should be the maximum acceptable conductor temperature.)

Indeed, we renamed it to "'Slack Bus 1'" for the case3_dc.m as well.

I'm impartial about state vs status. I have used the following approach in the past. statemin and statemax are both binary parameters, state is the binary variable statemin

just to scale the objective or as an actual base for parameters and variables with a currency as a unit?

Interesting discussion! In this context, an OTS variant with [spanning tree constraints](https://ieeexplore.ieee.org/abstract/document/6140618) would be quite interesting.

In the math model, powermodels sticks with the convention pf+ pt = ploss >=0 (if r>=0). Matpower, however in its data model, defines pf-pt=ploss. I think this is mainly because...

I'd like to make a proposal as well. Classically, power system people define impedance as z = r + j x and admittance as y = g + j b....

Great, I'll get on this soon (likely after #622).