FpML Issues Tracker
closed
Minor
Always
Architecture
Admin
andrew
Summary
The PositionsAsserted complex type in fpml-reconciliation.xsd has two elements with the same name: "definePosition". This is legal XML Schema in this case because there is a choice between them. However this contravenes the FpML Architecture rules to quality a type with a unique name (name an element), see issue #603.
The first "definePosition" is used to specify a new position. The second "definePosition" is used to specify any type of position whether new or updated.
I propose we rename the new position "newPosition" to comply with the Architecture.
currently we have:
I propose we change this to:
Notes:
matthewdr
03/13/08 1:49 pm
Discussed at the AWG. There was mix of views, but there was consensus that Andrew Jacobs would document his view in the FpML Architecture Document that messages should do not need to be normalized.
Once documented in Architecture 2.1 this would resolve this issue.
andrew
10/02/08 11:18 am
The modelling guidelines paper discusses the use of grammar to control content which this issue is an example of.
andrew
10/02/08 1:52 pm
AWG agreed on 02-10-2008 to close this issue.