|
Since no one had any comments on this, we’ll
go ahead with the change and won’t meet today. One thing to point out is that this change
will add a required position Id and version to the position … it might be
that for our purposes at least the version should be optional. Brian Lynn, CTO Global Electronic Markets, http://global-emarkets.com High-speed FpML matching, reconciliation,
and validation: From: The changes are relatively minor,
including some minor structural changes, some increased optionality, and some
additional identification information. If anyone has any questions, comments, or objections
to this change, please circulate them to the list (note the new email address
for the list). If there are significant issues raised
with this by Friday, we’ll schedule a meeting for next week to review
this in more detail. Also, if anyone has any other issues or
proposals that they’d like to raise, please let me know and/or circulate
to the group. I’d be happy to hold a meeting if we have anything
substantial to discuss. Brian Lynn, CTO Global Electronic Markets, http://global-emarkets.com High-speed FpML matching, reconciliation,
and validation: From: All, The Business Process Working Group is working on having an
FpML representation for portfolio reconciliation. One of the tasks has been to
review the current position representation defined by this group because we
wanted to reuse the same representation for portfolio reconciliation. We have
identified some potential changes to the Position type.
The changes include:
Let me know your thoughts. Best regards, -Marc |