-
One of the big modeling tasks that we have not discussed in detail is representing **evidence** and **provenance** information supporting a given variant annotation statement. We have superficially c…
-
In GitLab by @mandresm on Jul 11, 2024, 17:24
## Summary
As mentioned in previous meetings I want to propose that the `conf/metadata/experiment_data.yml` contains information about the provenance of…
-
-
We should define a way to version this, I can't find any version numbers.
Also, what's the release process? This should be documented so that everyone knows how it works.
Happy to propose someth…
-
# Summary
This proposal describes Reference Value Provider Service, a key component to generating reference value, which handles different provenances, extracts reference value, and sends it to Attes…
-
[Emissiebron](https://data.vlaanderen.be/ns/waterkwaliteit#Emissiebron)
Beschrijving
Oorsprong van een emissie.
Gebruik
Het kan een inrichting zijn zoals een fabriek, installatie of scho…
-
- [x] I have read the [CLA Document](https://github.com/creator-assertions/identity-assertion/blob/main/contributor-license.md) and I hereby sign the CLA.
--------------------------------------…
-
[P2318R0](https://wg21.link/p2318r0) A Provenance-aware Memory Object Model for C (Jens Gustedt, Peter Sewell, Kayvan Memarian, Victor B. F. Gomes, Martin Uecker)
-
IMP currently takes as input files in a variety of formats, but doesn't care where those files originate. This becomes a problem when we come to publish a modeling study and deposit the files (e.g. at…
-
In principle we can have different code versions for each process step, e.g., code version "extraction_v1.0.1" and "coaddition_v2.1.3" can coexist and they would just make different provenances.
The…