[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FpML-AWG Changes to scheme genericode files?
- To: awg@xxxxxxxx
- Subject: Re: FpML-AWG Changes to scheme genericode files?
- From: Daniel Dui <daniel.dui@xxxxxxxxx>
- Date: Mon, 8 Feb 2010 22:38:23 +0000
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=OMmLSihuS37tam7KORqcHr1rma9bEsK0yiigJsHi8uk=; b=awbpMXHt486WVZm7skE6DkQf+TOT10bGJCm+D8bx0oRIF+OlrAVIk66lEP/0j2ldqk lvJARe+tJNGaocc8kISO30eopH4MWs5Z8f/y1pZQbEQQfHMZcIFM4eTOHL5yUm0sGIm3 JWZqA26ycp0oIAb26yVt9pVk5vddOqzRvnxh4=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=joX77h6ThvbglfT51DPQEACew3e5vW8Ut+NWwpVY0QJBBdFUmC2Rs0L4ZoJuekgZ3r f/DQLHeR3caSytk2iTLlyv3S8pDVFGLi4Zktmg4C+HY7u4tnsJgkeHJNMiaQDbE2yxJb 6i1x0zFnvHlkioe0wN+cWirTc99kcB3SByYhg=
- In-reply-to: <58F8B576691EBF43B2BF1173C756C90904915213D2@USMAIL>
- References: <58F8B576691EBF43B2BF1173C756C90904915213D2@USMAIL>
- Reply-to: awg@xxxxxxxx
- Sender: owner-awg@xxxxxxxx
Hi Marc
Just my first thoughts after seeing your slides and example.
Are the five attributes required?
- What's the numeric index for? Is it basically a row number? Since
code values are already short and unique, I don't find it very useful.
- I also don't think that the code name attribute would be of much use
in FpML, since a code is mnemonic already.
- I guess that for valid from we could use the date when the FpML
recommendation was published where that code was used for the first
time.
I don't understand how "introduced date" and "code status date" are
meant to be used. Is there any documentation available from ISO20022?
Should they be compared to the trade date? The date when a message is
produced? The release date of the version of FpML to which the message
that uses the code is compliant?
- Perhaps for status "active", "deprecated", and "inactive" is all we need.
regards
-daniel
On 8 February 2010 20:04, Marc Gratacos <MGratacos@xxxxxxxx> wrote:
> A set of code list requirements have been published by ISO 20022. Based on
> these requirements, some additional data would need to be represented in the
> code lists. I put together a few slides describing them and an
> example scheme showing the changes.
>
> Let me know your thoughts.
>
> Kind Regards,
> Marc
> ________________________________
> The information contained in either this email and, if applicable, the
> attachment, are confidential and are intended only for the recipient. The
> contents of either the email or the attachment may not be disclosed or used
> by anyone other than the addressee. If you are not the intended
> recipient(s), any use, disclosure, copying, or distribution is prohibited
> and may be unlawful. If you have received this communication in error,
> please notify us by e-mail at isda@xxxxxxxx <mailto:isda@xxxxxxxx> then
> delete the e-mail and all attachments and any copies thereof. This
> communication is part of an ISDA process and is not intended for
> unauthorized use or distribution.
>
--
____________________________________________________________
Daniel Dui - daniel.dui@xxxxxxxxx - skype: danieldui
-------------------------------------------------------------------------------
To unsubscribe: Email majordomo@xxxxxxxx with a blank subject line
In the body include the line: unsubscribe awg youremail@address
To view archives: http://www.fpml.org/_wgmail/_awgmail/threads.html