Explore how to incorporate human observations as valid 'sensors' in low digital maturity environments

[zachzeus]

From Golda - pilot lead of UNCRM Cobalt from Democratic Republic of Congo.

the main issue i had with the sensorElementList https://github.com/uncefact/spec-untp/blob/main/website/schema/traceabilityTransactionEvent.v0.3.0.JSONLDContext.jsonld#L47 in the spec, is that it really pushes towards automated sensors, and I don't think in some areas that is how it will work or is the key measure. Also sensors generally are going to produce a really high volume stream of data, so its more the summaries anyway that we probably will put in the passport.

I want to encourage people to use 3rd party auditors and observers as much as possible, in areas where human rights are an issue. sensors is more for carbon footprint i suppose.

I wonder if we could either replace it with or add a section of more generic

observation
who/from
what
where
when

who/from =
source w hashref
OR
issuer & signature

we could use other fields, but to me the critical part is the observation, and the fact that it contains either its own signature or a source and hashref, which makes it easy to incorporate 3rd party data or sources

maybe this is an alternative to the sensorElementList ?

[gvelez17]

thanks Zach! I am hoping we could incorporate the key question - were there independent observers at that mine site, or not, and if so who were they, and make it easy to process a conformity credential and determine this in a human readable way

In the DRC the key question is access to the mine sites, for independent human observation, most of the big mining companies i believe are NOT giving access to observers.

The other question is if the mining companies are actually supporting the community as they have a legal requirement to, and who is certifying that.

[onthebreeze]

Zach and Golda to catch up about this.

• we should make sure that DCC (or some variant of it) can provide a way to register second party observations.