What should an engine do with the generated FnO execution triples (from the function triples map)? about rml-fnml HOT 5 OPEN

@pmaria raised this first, so I'll let him explain further, but my take:

Right now the RML+FnO mapping files also describe FnO execution triples via TripleMaps via fnml:functionValue.
It is currently not specified what should happen with the actual resulting triples (and I think most implementations just ignore the generated triples).
There's currently a proposal to use those execution triples when (automatically) generating provenance statements of the mapping process, so you can also include provenance of the data transformations: https://fno.io/prov/
So I think that's at least one use case to use those execution triples,
but discussion is needed to see whether (i) this is relevant, useful, worth the effort, and how much we want to put that in the spec as a MUST or a SHOULD or a CAN or ..., and (ii) what other use cases this could be relevant for

from rml-fnml.

Could you explain this issue a bit more?

from rml-fnml.

Yes, exactly this.

from rml-fnml.

got it, thanks! really important in terms of provenance but also reproducibility!

from rml-fnml.

If it makes sense, this can be transferred to https://github.com/kg-construct/fnml-spec

from rml-fnml.