We have added new functionality to the Profiles you can create in EBU.IO/QC.
From now on each Test has a version indicated next to its ID.
If a newer version is available, a little warning sign appears next to it.
This way users can manage their profiles as they like (there is no forced update to the latest Test version), but at the same time they are encouraged to check out newer versions of the Tests they are using.
Users can decide the version to use in the Profile Manager, using a simple drop-down list.
The version information is visible to users regardless of their log in status, but as currently there is only one single version for each Test published publicly, the general audience will not really make use of it yet.
However, for editors (which are working with many different draft versions of the Tests), the new functionality is already practically relevant.
A large batch of updates to all Tests is expected in Q2, when the EBU QC Output subgroup has completed its work.
With a warm chocolate and a glühwein* next to our laptops, we've been working on improvements of the EBU.IO/QC back-end.
* It is ~+12 degrees Celcius in Geneva...
We now have added linked definitions of parameter types:
The idea is that we want to help EBU QC Test editors to be stricter in the way they define parameter in- and outputs.
By facilitating managed lists of types, representations, ranges and units, we encourage reuse and minimize mistakes.
We've decided to use regexes to help check correct instantiation of ranges.
For example [0,4) is a valid instantation of [a,b).
We also use Regexes to check the names of the managed 'types'.
But we did not dare to go so far as to ask editors to specify their ranges as regexes directly... :-o
In a next step we plan to check default (and later user) values against the instantiated ranges.
Frans and Julien