Page Comparison

This page contains a list of outstanding tasks.

1. Complete the axioms for:
   1. claim (v)
   2. report (v)
   3. verify
   4. audit (v)
   5. measure
   6. report (n)
   7. developer
2. Think about "attesting" and "attestation".
3. Create proper, fully elaborated example of a project expressed in AIAO.
4. Consider creating an "Arithmetic" class.

5. Create a stronger link in the protos between activities and environments.

6. Continue with term/class definitions.

7. Expand the second and third… n levels of the ontology, as necessary.
   1. "sensor" and "actuator" are good candidates for subclasses to the "instrument" class. 
   2. What should the subclasses to thing:claim be? E.g., where would "measurement" fit in? Should we first distinguish between qualitative and quantitative claims? 
8. Update the diagram with the latest axioms.
9. Add a definition and example to each of the classes in Protégé. Also do it on this page.
10. Align the ontology with OWL specifications and syntax.
11. Incorporate W3C's time ontology (owl-time) into ours. Wouter already did some work on this in the past.
12. See if we can use any of these ontologies for the spatial classes: W3C, DBpedia 
13. Check out Regen1's place-based stuff.
14. Review PROV-O (provenance ontology). Wouter worked on it a bit already.
15. Embed ontology into BFO and its extensions. Some useful resources: BFO 6-part video series. Perhaps check if we should not rather go with AFO.
16. Review UN SEEA terminology.
17. Can we / should we try to align our ontology with ISDA CDM?
18. Develop tools for applying the ontology (see our GitHub repo for what has already been done).
19. Get industry entities to test our ontology & tools. Possible testers:
    1. SAP (https://community.sap.com/topics/sustainability/climate21)
20. Review PACT and their Pathfinder tool:
    1. - https://www.carbon-transparency.com/resources
    2. - https://www.carbon-transparency.com/media/jpslsujn/pathfinder-framework.pdf
21. Review W3C's PROV-O (provenance ontology). Wouter worked on it a bit already.
22. Incorporate W3C's time ontology (owl-time) into ours. Wouter already did some work on this in the past.
23. Check out: https://w3c-ccg.github.io/traceability-vocab/#undefinedTerm\ (Wouter has possibly worked on this already.)Consider creating a "Role" protobuf.
24. Update landing page.
25. How does W3C's "claim" schema for VCs compare to our "claim" class?
26. Keep tabs on OS Climate.

27. How does the UN SEEA framework compare to our ontology?

28. Create a stronger link in the protos between activities and environments.

29. Continue with term/class definitions.

30. Submit a paper about our work to the Semantic Web Journal (www.semantic-web-journal.net).

31. Test our control class against https://www.api.org/-/media/Files/Policy/ESG/GHG/API_Climate_Reporting_Factsheet.pdf.

32. Causality: How is causality expressed mathematically? 
33. Check out: https://www.ecometricsllc.com/what-we-do/
34. Make sure we've explained our alignment to / differentiation from CDM's glossary everywhere applicable.
35. Review https://arxiv.org/pdf/2304.02711.pdf (from Henriette).
36. Review https://henrietteharmse.com/wp-content/uploads/2017/11/uml-class-diagram-to-owl-and-sroiq-reference.pdf (from Henriette).
37. Check out https://www.worldstandardscooperation.org/.
38. Get other experts to review the ontology etc., e.g., Szymon Klarman.
39. Check out: https://lov.linkeddata.es/dataset/lov.
40. Check out: http://ns.nature.com/terms/Agent.
41. Check out: http://www.cidoc-crm.org/cidoc-crm/E39_Actor.
42. Check out: https://schema.org/agent.