Somewhat better handling of component property values that are not
numeric or for the domain component property in the evaluation of SPARQL
query results in getDerivations().
Reverting check on whether the component property equals the domain
component property (i.e. use the domain component property twice).
Instead of stating the domainComponentProperty explicitly in
getDerivations query get the variable name dynamically and assign it to
FILTER and ORDER.
Build this.classifier (not classifier) though it probably makes no
difference.
Make sure to query for the qb:order of component specifications in
getDerivations as to load the components of an observations in the
correct order in memory.
Bugfix situation store to situation writer