Left out on first run through of implementing datatypes due to it not being integral to getting a working demo, the DataModelExtension (DME) specs are still being finalised as mentioned here https://wbcsd.github.io/data-model-extensions/spec/, return to implement once further down the track with primary execution path for the software.

There are some docs changes currently in PR that I'm waiting to land, but I need to move forward, so I've implemented it using a mixture of the current technical spec at https://wbcsd.github.io/data-exchange-protocol/v2/#dt-assurance, and the Pathfinder Framework V2 docs, and common sense. There will undoubtedly be drift over the next few months, by the time I make it back.

https://wbcsd.github.io/data-exchange-protocol/v2/#liststatuscode

https://wbcsd.github.io/data-exchange-protocol/v2/#api-auth

https://sine-fdn.github.io/introduction/#events

https://wbcsd.github.io/data-exchange-protocol/v2/#lifecycle

https://wbcsd.github.io/data-exchange-protocol/v2/#api-action-events-case-2

https://wbcsd.github.io/data-exchange-protocol/v2/#api-action-list-pagination

https://sine-fdn.github.io/introduction/#getFootprint

CarbonFootprint is only partially completed, the core datatype is there and the tests show that values can be provided to the relevant compulsory attributes, but there is basically no validation on the type itself, only on the subtypes that it uses in aggregate, also the docstring is not completed. Ultimately didn't have the time or patience to fuck around with the other bits right now, just wanna get the final ProductFootprint done, so that all the datatypes are in there and I can move towards compulsory conformance prior to the next connectathon deadline.

TODO: Implement the additional functionality to support:
4.21.1. Custom Product Ids (Product Codes)
4.21.2. ProductId based on CAS Registry Numbers
4.21.3. ProductId based on IUPAC InChi Code

https://wbcsd.github.io/tr/2023/data-exchange-protocol-20230221/#dt-productid

https://sine-fdn.github.io/introduction/#authenticate

https://wbcsd.github.io/data-exchange-protocol/v2/#api

DQI is not used by anything currently, it is not part of compulsory nor optional requirements, and it does not really go live until 2025. So I am leaving it until I have more pressing code finished.

https://wbcsd.github.io/data-exchange-protocol/v2/#dt-assurance

I had briefly started work on migrating some of the core datatypes (String, etc) to using Root Custom Types https://docs.pydantic.dev/usage/models/#custom-root-types in order to move away from key value basic types and to something with a stronger model for comparison, but I realised that the V2 for Pydantic had just released as Alpha, and it removes Root Custom Types, so I'm going to continue on with the current approach with V1, implement the data types, then round back with V2 and refactor the new features in/out.

TODO: Implement the additional functionality to support SHOULD behaviour
4.19.1. Custom Company Ids (Company Codes)

https://wbcsd.github.io/tr/2023/data-exchange-protocol-20230221/#dt-companyid

https://wbcsd.github.io/data-exchange-protocol/v2/#filter

https://sine-fdn.github.io/introduction/#error-responses

https://wbcsd.github.io/data-exchange-protocol/v2/#api-action-events-case-1

Flake8 cannot be configured by pyproject.yaml, making it tedious to set up and use, other issues were found that I cannot remember but the default line length setting is inconsistent with other tooling, for example, black has longer default line lengths, remove flake8 and then the custom line length for black. Do this after the datatypes major branch is merged in order to isolate what will be a bit ugly sweeping edit by black.

https://sine-fdn.github.io/introduction/#listFootprints