The type product_specification carries (much but not all) of the metadata to describe a specific concrete data product.
It currently includes:
creator_, an algorithm_name (perhaps better renamed as node_name) the contains the plugin and algorithm name, which uniquely identify a node in a data flow graphsuffix_, which can be used to distinguish between objects of the same type produced by the same nodetype_id_, which is an identifier of the concrete data product type
What is currently missing is:
- an identifier of the stage in which the product in question was produced
- an identifier of the data product concept which the data product models
- an optional identifier of the translator that produced the data product (optional because data products are not always the result of a translation)
- a (mathematical) set of
layer_paths indicated with layer_paths the data product is associated with. In most of our (simple) examples, this set would be of size 1; I believe that in real use, most will be a larger size.
The type
product_specificationcarries (much but not all) of the metadata to describe a specific concrete data product.It currently includes:
creator_, analgorithm_name(perhaps better renamed asnode_name) the contains the plugin and algorithm name, which uniquely identify a node in a data flow graphsuffix_, which can be used to distinguish between objects of the same type produced by the same nodetype_id_, which is an identifier of the concrete data product typeWhat is currently missing is:
layer_paths indicated withlayer_paths the data product is associated with. In most of our (simple) examples, this set would be of size 1; I believe that in real use, most will be a larger size.