-
Notifications
You must be signed in to change notification settings - Fork 4
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
Create preliminary list of specifications to develop #7
Comments
Based on the Server Metadata example, it seems that API Endpoints would be broken down by customer datasets. Is it worth drafting the list of API endpoints or customer datasets upfront? Would data formats also specifically link to customer datasets, or does that apply more broadly? (Typo: "accessed an interacted" I think should be "and") |
On March 27, 2023, reorganized from 4 specs to 3 (see edit history of parent post). |
…ustomerdata.carbondataspec.org domain
My thoughts on the initial list of specs:
CDSC-WG1-01
- Server Metadata - How companies and users can discover what utilities have what capabilities Create server discovery spec draft ("Server Metadata") #15CDSC-WG1-02
- Client Registration - How companies can register and onboard with utilities to access to their offered capabilities Create client registration spec draft ("Client Registration") #16CDSC-WG1-03
- Customer Data - How utilities offer access to customer data, including capability scopes, api endpoints, and data formats Create data access spec draft ("Customer Data") #24The text was updated successfully, but these errors were encountered: