Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize a context type representing a Currency #651

Closed
Tracked by #643 ...
kriswest opened this issue Mar 31, 2022 · 2 comments · Fixed by #708 or #724
Closed
Tracked by #643 ...

Standardize a context type representing a Currency #651

kriswest opened this issue Mar 31, 2022 · 2 comments · Fixed by #708 or #724
Labels
Context Data & Intents Contexts & Intents Discussion Group context-data FDC3 Context Data Working Group enhancement New feature or request
Milestone

Comments

@kriswest
Copy link
Contributor

Enhancement Request

Create a context type that can be used to represent a Currency.

Use Case:

A Currency context type is needed in order to compose other context types (such as an Order, Trade, Valuation or Position). However, an issue has also been raised to standardize recommended formats for 'primitive' fields, which might include ISO currency codes which may negate the need for this context as part of other context types.

A Currency context type may also be useful as a independent type, allowing it to be broadcast as part of workflows involving FOREX, liquidity pools or pricing.

Contexts

Currency

Represents and individual Currency.

Details
Property Type Required Example Value
type string Yes 'fdc3.currency'
name string No 'US Dollar'
ISOCODE * string No 'USD'

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

Example
const currency = {
    type: 'fdc3.currency',
    name: 'US Dollar',
    ISOCODE: "USD"
}
@kriswest kriswest added enhancement New feature or request context-data FDC3 Context Data Working Group Context Data & Intents Contexts & Intents Discussion Group labels Mar 31, 2022
@nemery-flextrade
Copy link

Per my comment on #645 we need to consider minor currency codes as well

@kriswest
Copy link
Contributor Author

@nemery-flextrade said:

Just commenting here for direct reference, I believe the consensus was that we expect only major currency to be communicated on the wire, conversions to minor currency should be the responsibility of the consuming system (where required)

#645 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Context Data & Intents Contexts & Intents Discussion Group context-data FDC3 Context Data Working Group enhancement New feature or request
Projects
None yet
2 participants