4.7. Data Product Management

Todo

  • Data cell definitions

  • Data family definitions

  • Data product definitions

  • Data product specifications

  • Data-product lookup policies

  • Describes what data products should be used/created by an algorithm

  • Describes how the \(\textit{label}\) operator can be used (as described in Section 3.5)

4.7.1. Specifying Familiies

As discussed in Section 3.4, the input family to a HOF is specified via a family(...) clause, where the ellipsis is replaced by a family specification. One of the specifications provided is product_query{.suffix = "good_hits", .layer = "spill"}, which indicates that a family should be formed from data products labeled "good_hits" from each "spill" data layer.

4.7.2. Input Family Specification

A family specification contains one or more product specifications and zero or more resource specifications, expressed in EBNF grammar [Wiki-EBNF] as:

input_family_spec   ::= input_product_specs | input_products "," resources
input_product_specs ::= Product | Product "," (input_product_specs | resources)
input_products      ::= Product | Product "," input_products
resources           ::= Resource | Resource "," resources

where Product and Resource specify a single product and a single resource, respectively.

In the code examples that follow, the bracketed term <input_family_spec> will refer to any specification allowed in the family(...) clause. The specifications for Product and Resource depend on the computing language of the algorithm and are defined elsewhere.

Todo

Where will be define the Product and Resource specifications, and what are they?

4.7.3. Output family specification

output_family_spec ::= ProductOutputSpec | ProductOutputSpec "," output_family_spec

References