What you need to know as a Contributor

  1. You need to be familiar with the GLEC Framework (contains concepts of ISO14083). Knowledge of the key terms (such as Transport Operation Category (TOC), Transport Chain (TC) and Transport Chain Element (TCE), etc. is necessary for understanding of the iLEAP project).
  2. iLEAP builds on the work of WBCSD PACT and SINE Foundation (in particular the data exchange protocol; see also the Resources Section below) to enable interoperable data exchange, especially with shippers, to logistics service providers on a global scale.
  3. The primary deliverable of iLEAP are the “so-called” iLEAP Tech Specs: this is a technical document to be used by companies implementing iLEAP compliant software. The iLEAP Tech Specs specifically address the ability to exchange logistics emissions data between companies in an interoperable and software solution-agnostic way.
  4. There are several ways to contribute to iLEAP, such as:
    1. Providing high-level feedback: e.g. suggesting new business cases. By business case we mean that there is a need to exchange data between several companies, in the context of logistics emissions. Details can be found here.
    2. Make a concrete proposal for the iLEAP Tech Specs, as explained here.
    3. Suggest a contributor or pilot tester for iLEAP: If you think there is another party that might be interested in iLEAP, you can find further instructions here.

How to contribute

As a contributor, you can partake in the project through various ways and opportunities. Some of these are described in more detail below.

When contributing, you always have the option to share your input and thoughts in a more private way with the project team (see here for contact information). In some cases, you may also be invited to provide feedback via GitHub.

Option 1: Giving (high-level) feedback to the iLEAP Tech Specs

If you found something that is missing or should be improved (or maybe even removed from the tech specs), please let us know.

For such kind of feedback, we have

a) The Public Feedback Tracker where you can also find past feedback documented

b) Our team’s emails through which you can confidentially give us feedback as well

Option 2: Suggest a new business case or use case for iLEAP

If you find that a more general business case is missing (a sort-of made up example: you would like to use iLEAP in a market-based measures scenario), please get in touch with us.

See Option 1 on how to give feedback in this case, please.

Option 3: Detailed feedback and comments on iLEAP Tech Specs Pull Requests

As a contributor you are part of the iLEAP community and are generally welcome and asked to provide feedback to changes we make to the iLEAP Tech Specs.

This is generally coordinated through GitHub Pull Requests comments.