Renaming inner and outer consumes/produces

[mrchtr]

Propose to rename the inner and outer consumes/produces to something more meaningful.

Idea was to have self explaining names. An OperationSpec is consuming fields from the dataset, and produces fields to dataset (previous outer). The OperationSpec holding operation_consumes, and operation_produces (previous inner). As well as the mapping (operation_to_dataset_mapping and dataset_to_operation_mapping).

[RobbeSneyders]

Thanks @mrchtr. This doesn't change anything user facing right? I'm wondering if we should make a distinction there as well.

[mrchtr]

Thanks @mrchtr. This doesn't change anything user facing right? I'm wondering if we should make a distinction there as well.

Indeed, it's only a renaming of methods. It might make sense to define domain names somewhere, as this could likely enhance the explainability of our concepts. For example, a Dataset has a global schema and fields, and Components apply operations on the dataset, etc. .. This could be based on the feedback from the framework blog post, or perhaps we could use the blog post directly for it.

I wouldn't change the pipeline interface. I think we've had this discussion before, where we considered a dataclass for the consumes and produces mapping, and to enable the naming of the dict entries. But it was just more overhead and didn't added so much value.

[mrchtr]

This PR is outdated. The changes here are already part of #867