Create server discovery spec draft ("Server Metadata")

[daniel-utilityapi]

This is the specification describing how customer data sources (e.g. utilities) disclose what standardized functionality they offer.

• Write summary overview with example
  • Source: https://github.com/daniel-utilityapi/Customer-Data/blob/issue_15_server_metadata/website/specs/cdsc-wg1-01/overview.md
  • Render: https://daniel-utilityapi.github.io/Customer-Data/specs/cdsc-wg1-01/overview
• Review summary overview and example with working group
• Write specification draft
  • Source: https://github.com/daniel-utilityapi/Customer-Data/blob/issue_15_server_metadata/specifications/cdsc-wg1-01.md
  • Render: https://daniel-utilityapi.github.io/Customer-Data/specs/cdsc-wg1-01
• Open pull request for specification draft
• Review pull request with working group
• Update based on feedback
• Merge when consensus is obtained

[halliecramer1]

This is great! I'm excited to dig more into the "capabilities" piece.

For infrastructure types - is it worth considering customers with assets or load at the transmission level, e.g. datacenters or RE projects, and having a distinction between TSO and DSO? Or would the TSO information come from the DSO communicating with the TSO to pull that information?

ideas for customer data [cdsc-wg1-03]: meter location (of load source or RE), timestamp, consumption or generation, flags for DR notifications, TOU rate mapping - requires authorization of data owner for associated meter but that would be done through oauth capability, not customer_data capability? If production is part of green tariff, how is it allocated across customers?

[ssuffian]

This looks really good and reads really clearly. Excited to get more into the details regarding the Customer Data spec. Hallie's comments have me wondering where the line is between the Power System Data Working Group and this one. Would utilities be willing to provide the node that a customer is on, so that it could get linked to the Power System data?

Also a small typo under "Metadata Endpoint"
Server metedata -> Server metadata

[daniel-utilityapi]

Discussed the example at the 2022-08-25 meeting

[daniel-utilityapi]

An update, I finally got an initial draft of the specification done.

Website render: https://daniel-utilityapi.github.io/Customer-Data/specs/cdsc-wg1-01/
Markdown in repo: https://github.com/daniel-utilityapi/Customer-Data/blob/main/specifications/cdsc-wg1-01.md