You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Discussion: the future of processing:expression (keep, freeze, or deprecate) #49
In #47, @m-mohr asked to keep this subject separate from the scope clarification. This issue is the place for it.
Why the question
processing:expression is the only field of the extension that describes the processing itself and not a property of the data. All the open proposals that extend the extension start from it (#31, #33, #44, #46). Its definition is very open: any format, any expression type, no rule on what a client can do with it. With the move to Stable (#48), we must decide if we want to commit to this field as it is.
Who uses it
openEO: the GeoPySpark, Python and Sentinel Hub drivers write the process graph of a batch job with format: openeo. The Copernicus Data Space documentation shows it as the provenance record of a job.
CEOS-ARD: maps requirements 1.13 / 1.15 (machine-readable processing chain) to the field.
MLM: the best practices recommend format: stac-mlm with a URI to the model Item.
The field is thus used for one main case: an openEO process graph as the record of what produced the data. Deprecation has a real cost for these users.
Options
Keep and freeze. The field stays as it is. We add no sub-field and no new recommended format. New needs go to links or to other extensions.
Keep and narrow. Same as 1, and the README says that the expression is the transformation itself, given inline (process graph, band math). A reference to code, an image or a model is a link.
Deprecate the field in favour of the processing-expression link. The process graph moves to a linked document. Existing data stays valid until a 2.0.0.
Move it to another extension (Application, or a new one) and deprecate it here.
Questions
openEO maintainers (@m-mohr@soxofaan@jdries): is a link to the process graph an acceptable replacement, or is the inline record a requirement?
CEOS-ARD: can a link satisfy requirements 1.13 / 1.15? @m-mohr
For options 3 and 4: which extension takes an inline expression today? The Application extension points back to this field for that purpose.
I'm not entirely convinced by the argument that processing:expression is different because it describes the processing itself rather than a property of the data.
I see processing:software, processing:lineage, and processing:expression as different ways of documenting the provenance of a data product:
processing:software describes the tools involved.
processing:lineage describes how the data was produced.
processing:expression describes the transformation applied.
All three are about the production history of the data, rather than intrinsic properties of the resulting data.
I agree that the definition of processing:expression is not ideal, but I think in general such metadata belongs in this extension. And it seems you agree, because you did not plan to remove the corresponding relation type?!
For CEOS-ARD, I think we can live with a link. For openEO it would be a rather big change, but in principle possible.
Activity
m-mohr commentedon Nov 17, 2026
I'm not entirely convinced by the argument that
processing:expressionis different because it describes the processing itself rather than a property of the data.I see
processing:software,processing:lineage, andprocessing:expressionas different ways of documenting the provenance of a data product:processing:softwaredescribes the tools involved.processing:lineagedescribes how the data was produced.processing:expressiondescribes the transformation applied.All three are about the production history of the data, rather than intrinsic properties of the resulting data.
I agree that the definition of
processing:expressionis not ideal, but I think in general such metadata belongs in this extension. And it seems you agree, because you did not plan to remove the corresponding relation type?!For CEOS-ARD, I think we can live with a link. For openEO it would be a rather big change, but in principle possible.