Standardize a context type representing a Valuation

[kriswest]

Enhancement Request

Create a context type representing the price and value of a holding.

Use Case:

A Valuation may be used as a key component of a Trade or Position context, perhaps also an Order. Although it may be used rarely as a standalone context (although use-cases may exist), it is a multi-field type that is likely to be needed in the definition of multiple other types, yielding an advantage to standardizing it.

Contexts

Valuation

Represents the value of a holding in a specified currency.

Details

Property	Type	Required	Example Value
type	string	Yes	'fdc3.valuation'
value	number	Yes	'500.0'
price	number	No	'5.0'
CURRENCY_ISOCODE *	string	Yes	'USD'

* CURRENCY_ISOCODE should conform to 3 character alphabetic codes standardized as part of ISO 4217.

Example

const valuation = {
    type: 'fdc3.valuation',
    value: 500.0,
    price: 5.0,
    CURRENCY_ISOCODE: 'USD'
}

Additional Information

An issue has also been raised to standardize recommended formats for 'primitive' fields, which might include ISO currency codes:

• Standardize recommended formats for 'primitive' Context fields #645

If that issue is NOT accepted the CURRENCY_ISOCODE field should be replaced with a currency field that makes use of the Currency context type prosed in issue:

• Standardize a context type representing a Currency #651

[robmoffat]

I think this is already covered by FpML: https://www.fpml.org/spec/fpml-5-2-4-tr-1/html/confirmation/schemaDocumentation/schemas/fpml-valuation-5-2_xsd/complexTypes/AssetValuation.html

I think we should use existing specifications where they are available and well-defined, as we have done with currency, time, country code etc.