Does this not point to a requirement to separate asset classes by namespace and version separately?
Derek LaSalle
IB Architecture
----- Original Message -----
From: [Daniel.Dui@xxxxxxxxxxxxxxxxxxx]
Sent: 09/18/2008 10:49 AM CET
To: <awg@xxxxxxxx>
Subject: RE: FpML-AWG AWG Teleconference 18-Sep 9am NYC/ 2pm LON
I will not be able to join the call this afternoon.
I think we should keep separate a “marketing
version number” from a “technical release number”.
The “marketing version number”
is more or less what we have now. I.e. X.Y where X increases when there is a
big change (whatever that might be) and Y when there is a small change.
This is what appears on the webpage and
what people generally use to refer to a published version of FpML It’s really
just a label from a developer’s perspective.
The “technical release number”
is something that a system consuming FpML messages can use to determine if and
how a message should be processed. This could be just a build number or
something more complex that indicates if a version is backwards compatible or
not with a previous one.
I am skeptical on how useful it is to
indicate at a global level that a version is compatible/incompatible with
another one. For example if the FX definitions change in backwards incompatible
way, a consumer that uses only the IR definitions is unaffected. It would certainly
be a bad idea for the IR consumer to discard messages that are marked as
backwards incompatible.
-daniel
From:
Sent: 18 September 2008 09:14
To:
Subject: FpML-AWG AWG
Teleconference 18-Sep 9am NYC/ 2pm LON
The AWG has a scheduled call today at 9am
NYC/ 2pm LON. Please join if you can.
US: 888 481 3032
Intl: 617 801 9600
Participant Code: 8682747
Agenda
1. Updates
2. FpML versioning numbering (continued)
3. AOB
Thanks
Andrew Jacobs
Director, HandCoded Consulting Ltd.
Director, HandCoded Software Ltd.
Mob: +44 (0)7710 304239
_______________________________________________
This e-mail may contain
information that is confidential, privileged or otherwise protected from
disclosure. If you are not an intended recipient of this e-mail, do not
duplicate or redistribute it by any means. Please delete it and any attachments
and notify the sender that you have received it in error. Unless specifically
indicated, this e-mail is not an offer to buy or sell or a solicitation to buy
or sell any securities, investment products or other financial product or
service, an official confirmation of any transaction, or an official statement
of Barclays. Any views or opinions presented are solely those of the author and
do not necessarily represent those of Barclays. This e-mail is subject to terms
available at the following link: www.barcap.com/emaildisclaimer.
By messaging
with Barclays you consent to the foregoing. Barclays Capital is the investment
banking division of Barclays Bank PLC, a company registered in
_______________________________________________
Generally, this communication is for informational purposes only and it is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. In the event you are receiving the offering materials attached below related to your interest in hedge funds or private equity, this communication may be intended as an offer or solicitation for the purchase or sale of such fund(s). All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities.