Skip to content

Commit

Permalink
Multiple cardinaltiy for after state for positions
Browse files Browse the repository at this point in the history
Cardinality change for after state within CounterpartyPositionBusinessEvent
  • Loading branch information
rogerguitart committed Nov 20, 2023
1 parent 2407121 commit fdd1209
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion rosetta-source/src/main/rosetta/event-common-type.rosetta
Original file line number Diff line number Diff line change
Expand Up @@ -100,7 +100,7 @@ type CounterpartyPositionBusinessEvent: <"A business event represents a life cyc
eventDate date (0..1) <"Specifies the date on which the event is taking place. This date is equal to the trade date in the case of a simple execution. However it can be different from the trade date, for example in the case of a partial termination.">
effectiveDate date (0..1) <"The date on which the event contractually takes effect, when different from the event date.">
packageInformation IdentifiedList (0..1) <"Specifies the package information in case the business event represents several trades executed as a package (hence this attribute is optional). The package information is only instantiated once at the business event level to preserve referential integrity, whereas individual trades make reference to it to identify that they are part of a package.">
after CounterpartyPositionState (0..1) <"Specifies the after position state(s) created.">
after CounterpartyPositionState (0..*) <"Specifies the after position state(s) created.">

type ObservationInstruction: <"Specifies inputs needed to process an observation.">
observationEvent ObservationEvent (1..1) <"Contains all information related to an observation.">
Expand Down

0 comments on commit fdd1209

Please sign in to comment.