We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ISO has just released the 21031 specification, which is just a copy-paste of the SCI methodology of the Green Software Foundation. The methodology is quite easy to follow because quite generic. I am pretty sure that the computations done in the API are already compliant. Cloud Carbon Footprint already made the move for the Emobied Emissions aka the manufacturing carbon footprint. The only issue could be the request to use the marginal location-based grid intensity, which is difficult to obtain. See the article on the ElectricityMaps blog.. I suggest jus to keep using the standard annual grid carbon intensity and saying it.
Express the API methodology in the documentation using the wording of the SCI/ISO specification.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Problem
ISO has just released the 21031 specification, which is just a copy-paste of the SCI methodology of the Green Software Foundation.
The methodology is quite easy to follow because quite generic. I am pretty sure that the computations done in the API are already compliant. Cloud Carbon Footprint already made the move for the Emobied Emissions aka the manufacturing carbon footprint.
The only issue could be the request to use the marginal location-based grid intensity, which is difficult to obtain. See the article on the ElectricityMaps blog.. I suggest jus to keep using the standard annual grid carbon intensity and saying it.
Solution
Express the API methodology in the documentation using the wording of the SCI/ISO specification.
The text was updated successfully, but these errors were encountered: