Mark: 1. on naming cdsIndex We talked about this in the meeting on Wednesday briefly. Folks seemed to be indicating they we're fine with cdsIndex. I'm actually currently working on preparing the notes from the meeting and I'm referring to it as cdsIndex. I see your point regarding the inconsistency - I agree with you. However, unless other people on the email list voice the same concern, we are going to stay with cdsIndex. Yes, CDS is a very commonly used abbreviation for credit default swap. 2. on enumeration There will be optional FpML schemes associated with both indexId and indexName -- very much analogous to what we have for referenceEntity. Check out the architecture document for examples. There will not be XML Schema enumerations associated with either of these elements. The valid values for indexId and indexName are too dynamic (and perhaps too large) to represent in an enumeration. Yes, Mark-It Partners say they will provide RED identifiers for the indices. FpML will not require the use of RED identifiers. However, you will definitely be able to use RED identifiers with FpML and many users will probably do so. Ben Lis Deputy CTO creditex, Inc. main: 212-633-7277 direct: 917-661-5935 -----Original Message----- From: Marc Gratacos [mailto:MGratacos@xxxxxxxx] Sent: Friday, January 23, 2004 10:44 AM To: 'cd@xxxxxxxxxxxxxxxxxxxxx' Subject: FpML-CD40 Two questions about indices Hi all, I have a couple of questions regarding indices. cdsIndex vs. creditDefaultSwapIndex The first one is regarding the name of "cdsIndex". I am probably too picky but I was thinking about how we named the cdsIndex element. From a technical point of view, the use of abbreviations in XML is a bad practice (the only exception are identifiers, IDs). At the same time, it's probably true that "cds" as a name is very common name in the derivatives community. On the other hand, there is the element named creditDefaultSwap. Looking at this element, I see a lack of consistency for naming an element "creditDefaultSwap" and another element "cdsIndex". To sum up: - The use of abbreviations is a bad practice in XML. - Lack of consistency for naming an element creditDefaultSwap and another element cdsIndex But, - cds is a very common name in the derivatives community. indexName If I understand correctly, in our last meeting, besides the use of "indexID" (9 digit identifier) we proposed to use an element named indexName in order to identify the index too. I think we said that Mark-it partners will provide the values for this element. I am assuming this value will be defined as an enumeration scheme in our schema. Is this assumption correct? Have a nice weekend, -Marc --------------------------------------------------------------------- This is a commercial communication sent by SwapsWire Limited. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Please contact info@xxxxxxxxxxxxx if you no longer wish to receive commercial communications from us, identifying the email addresses to which you no longer wish commercial emails to be sent. --------------------------------------------------------------------- This is a commercial communication sent by SwapsWire Limited. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Please contact info@xxxxxxxxxxxxx if you no longer wish to receive commercial communications from us, identifying the email addresses to which you no longer wish commercial emails to be sent. This email and any files transmitted with it are intended solely for the person(s)to whom it is addressed. If you are not the intended recipient, please delete the message and all copies of it from your system, and destroy any hardcopies of it and contact the sender of the email.
<<attachment: winmail.dat>>