EIP-4824 Documentation, Schema Files, Ontology

Dec. 1
Project lead
Related to Working Groups (Projects)
Comments
Related to People (1) (Related to Projects (Project lead))
Update Oct. 12
Update 2022-08-18
Ido is still out of commission
Priority
Medium
Project doc
Update 2022-10-27
No update.
Nov 17
Jan 19 2023
Update Sep 15
Ido is back!
Update May 19
Next step: generate a daostar.rdf file and start using it as the canonical source of truth for the ontology
Last update (Apr. 14)
Ido has been in the desert; schema not uploaded
Update 2022-11-03
No update.
Action Items
Come up with a project plan for this, starting by identifying how daostar.org/schema will actually be used. E.g., it’s clearly referenced in the actual EIP, so there needs to be SOMETHING HUMAN READABLE there. But when a computer goes to daostar.org/schema and tries to parse it (e.g. because they want to display it in their UX), what should it expect—an RDF file? A JSON-LD file? Also, we need a JSON Schema implementation. 2. Parsers + data science to illustrate the use of this data 3. Standardized docs for every DAO reference implementation 4. Generate standardized docs for every actual 4824 endpoint. 3. Plan for daostar.org/schema, what is it actually being used for? 4. links to all the nice files .owl, .rdf files at daostar.org/schema 5. clean up daostar.org/schema 6. add link to daostar.org/schema from daostar.org 7. and some sort of schema.org integration TBD
Ido is the lead here.

EIP-4824 Documentation, Schema Files, Ontology

Dec. 1
Project lead
Related to Working Groups (Projects)
Comments
Related to People (1) (Related to Projects (Project lead))
Update Oct. 12
Update 2022-08-18
Ido is still out of commission
Priority
Medium
Project doc
Update 2022-10-27
No update.
Nov 17
Jan 19 2023
Update Sep 15
Ido is back!
Update May 19
Next step: generate a daostar.rdf file and start using it as the canonical source of truth for the ontology
Last update (Apr. 14)
Ido has been in the desert; schema not uploaded
Update 2022-11-03
No update.
Action Items
Come up with a project plan for this, starting by identifying how daostar.org/schema will actually be used. E.g., it’s clearly referenced in the actual EIP, so there needs to be SOMETHING HUMAN READABLE there. But when a computer goes to daostar.org/schema and tries to parse it (e.g. because they want to display it in their UX), what should it expect—an RDF file? A JSON-LD file? Also, we need a JSON Schema implementation. 2. Parsers + data science to illustrate the use of this data 3. Standardized docs for every DAO reference implementation 4. Generate standardized docs for every actual 4824 endpoint. 3. Plan for daostar.org/schema, what is it actually being used for? 4. links to all the nice files .owl, .rdf files at daostar.org/schema 5. clean up daostar.org/schema 6. add link to daostar.org/schema from daostar.org 7. and some sort of schema.org integration TBD
Ido is the lead here.