Many of these attributes (e.g. Algorithm Type) are not naturally Quantities
Descriptor or Quantifier would be better classifiers for the type

Change Type of Attributes Wrongly Modelled as Quantities

The following attributes need to change their type from QuantityDescriptor to Descriptor:
endorsingOperator
endorsementKind
algorithmType
algorithmValidation
priority

When making a recommendation a level of confidence is give to the accuracy of that recommendation.

When recommendations are deferred to the user and the level of confidence changes through time then a decision aid may wish to send a new/updated recommendation with a higher (or lower) confidence.

This (or another) section could do with some narrative as to the expected model for achieving this: i.e. does the decision aid send a new recommendation and expect the application to detect that a previous recommendation has now been superseded.

Allow update of deferred recommendations

Add Guidance to Response Interface, to state that whilst in the deferred state a recommendation may be update by repeating the recommendation method with the same recommendation id.

The Percentage type does not express how it is to be represented when mapped into a PSM. For example it is represented by a double in DDS. The specification should give advice on whether a percentage is expected to be mapped from 0-100 rather than 0-1 particularly as the type is often used to represent attributes which are named probability.

Clearly state the interpretation of percentage in DDS PSM

Add to description of real-valued quantities in the DDS PSM

Recommendations should enable the supply of a rationale or rule as a descriptor to aid an operator in particular.

Add Rationale to the MetaData for a Recommendation

Add Rationale to the MetaData for a Recommendation (in the properties class)
Model rationale in the style of ALMAS dynamic data:

• have a reference to resource string(s) (that could provide multi-language support)
• have a list of dynamic data with:
  • replacement Tag
  • data type
  • value

Whilst it is possible to specify outcomeProbability as part of overall confidence on a recommendation, this information is not played back when a resulting plan (or any PlanExecutionConstituent) is published.

Such information remains useful to consumers of this information - not least operators.

Whilst the current Capability of a Resource can have a quantifier, it is not possible to specify this when tasking a resource - e.g. number of objects to deliver.

Some recommendation are likely to have time limited validity. The system processing such recommendation would benefit from visibility of such constraints in order to better process and prioritize recommendations