@shahor02 @chiarazampolli this is at least part of the puzzle. It will allow you to create InputSpecs which match description and subspec simultaneously via something like:

inputs = {
  {DataDescriptorQueryBuilder::parse("header:CALH")},
  {DataDescriptorQueryBuilder::parse("payload:CALP")}
}

it still requires WorkflowSerialization.cxx to handle it correctly, but I should be able to get it later this evening (I need to take the day off).

thanks, can you make it work also for outputs?

So this will take any pairs that have the data origin "CALH" and "CALP", and then same description and subSpec, right?

Yes.

@shahor02 this should work also for outputs, what do you get?

will check later this evening

The correct syntax is actually:

DataDescriptorSpec{
{
  Inputs{DataDescriptorQueryBuilder::parse("header:CALH;payload:CALP")},
  ...
}
}

It however needs some fix in workflowSerialization.cxx, as I said. Looking into it.

@ktf : It fails

Invalid workflow: No matching output found for <matcher query: (and origin::CLW (and description:$1 (and subSpec:$2 (just startTime:$0 ))))>. Candidates:
-DPL/ENUM/2564289612
-TOF/DATASIZE/0
-TOF/CALIBDATA/0
-CLP/TOF_LHCphase
-CLW/TOF_LHCphase

i.e. CLW/TOF_LHCphase was not matched to CLW

The test branch with my code + your commit from this PR is https://github.com/shahor02/AliceO2/tree/pr_clb1.
The inputs and outputs are defined here:
https://github.com/shahor02/AliceO2/blob/92147a54c67f5a220c736d58726b12f0c2ba10e6/Detectors/Calibration/workflow/CCDBPopulatorSpec.h#L81
https://github.com/shahor02/AliceO2/blob/92147a54c67f5a220c736d58726b12f0c2ba10e6/Detectors/TOF/calibration/testWorkflow/LHCClockCalibratorSpec.h#L107-L108

For the wildcarded output: how the DataDescriptorQueryBuilder::parse(... can be used for the OutputSpec if it returns InputSpec?