separate Fabric data channels for different emissions types

[sichen1234]

Can we create separate Fabric data channels for different types of emissions (Scope 1, 2 ,3 or by type UTILITY_EMISSIONS_ELECTRICITY, TRAVEL_AIR, TRAVEL_CAR)

[brioux]

@sichen1234 I think this makes more sense by source/type of emission rather than scope (e.g. utility, travel, ....). The interpretation of scopes are relative - e.g., scope 1 for electric utility are scope 2 for the buyer of electricity and scope 3 upstream for the buyer of goods produced from the electricity (e.g. aluminum production through electrolytic reduction).

[sichen1234]

OK I agree with you on that.

Si Chen Open Source Strategies, Inc.

New Video: Creating Climate Solutions with Blockchain and Open Source https://youtu.be/gtO3COq8crQ

On Thu, Oct 14, 2021 at 9:55 AM Bertrand Rioux @.***> wrote:

I think this makes more sense by source/type rather than scope (e.g. utility, travel). The interpretation of scopes is relative - i.e. this is scope 1 for the utility, scope 2 for the buyer of electricity, and scope 3 upstream for the buyer of goods produced using the electricity (e.g. aluminum production through electrolytic reduction).

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/hyperledger-labs/blockchain-carbon-accounting/issues/320#issuecomment-943542294, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANAS4KTDRFTMDFZ3YG4PIDUG4DRBANCNFSM5F6UU5QQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.