Re: FpML-AWG RE: character set for code lists - issue 999

[Daniel Dui <daniel.dui@xxxxxxxxx>]

I don't have a problem with using shorter codes and a mapping table,
if the long codes are making adoption of the standard difficult. But,
unless I am wrong, the values in floatingRateIndex scheme have been
there for a long while and so far the issue has not been raised. Does
anyone know why this has become a problem only now?


This issue is not too different from the various discussions regarding
the length of element and attribute names, but I don't recall scheme
values being discussed as much.

XML itself has no problem with values that are long and contain spaces
or other non-alphanumeric characters. In fact also non-latin
characters should work.

The problem usually arises when you need to load the values in a
database, which probably allows only a short (by XML-standards) string
of alphanumeric latin characters. As Derek has mentioned,
non-alphanumeric characters often need to be escaped, which can easily
leads to buggy code and queries.

I have checked the architecture specs and I think that there is no
mention of scheme values up to the latest recommendation, which is
version 2.1.

The 2.2 and 3.0 working drafts contain a short section on scheme
values. This section imposes only to define values as if they were of
type xsd:token and gives some restrictions about the value length.

http://www.fpml.org/spec/fpml-arch-2-2-wd-1/html/index.html#s2.3.11

http://www.fpml.org/spec/fpml-arch-3-0-wd-2/html/index.html#s2.3.11

So the values that currently appear in the scheme definition don't
violate the spec as it is currently.


-daniel







2010/1/13 Derek N LaSalle <derek.n.lasalle@xxxxxxxxxxxx>:
> I'd second Stephen Turner's assertion that Codes with limited character are
> common for reference data. What now appears is a description rather than a
> code which lends itself to many permutations of mistakes in replicating or
> keying as there may be a need to escape characters etc. Codes are typically
> alpha without spaces or other strange characters that must be escaped to
> process.
>
>
>
> I'd recommend that all codes consistently adopt the following base type
> restriction of codes as used in the xsd:
>
>
>
>                                 <xsd:restriction base="xsd:NMTOKEN">
>
>                                                 <xsd:pattern
> value="[a-zA-Z,_,\p{N}]*"/>
>
>                                 </xsd:restriction>
>
>
>
> Regards,
>
> Derek LaSalle
>
> Information Architecture
>
> JP Morgan
>
> From: owner-awg@xxxxxxxx [mailto:owner-awg@xxxxxxxx] On Behalf Of Marc
> Gratacos
> Sent: Wednesday, January 13, 2010 6:33 AM
> To: awg@xxxxxxxx
> Subject: FpML-AWG character set for code lists - issue 999
>
>
>
> An issue has been raised regarding the characters being used in code lists
> such as the commodity reference price, floating rate index, the commodity
> business calendar, and possibly others:
>
>
>
> http://www.fpml.org/issues/view.php?id=999
>
>
>
> Some of these values such as the commodity reference price, are extracted
> directly from the ISDA Definitions. The source of these values is ISDA and
> not FpML. Limiting the character set would mean that we'd need an additional
> mapping between the ISDA and the transformed FpML codes.
>
>
>
> Technically, I don't see why we should limit the character set but I may be
> missing something.
>
>
>
> Any thoughts?
>
>
>
> ________________________________
>
> 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.
>
> This email is confidential and subject to important disclaimers and
> conditions including on offers for the purchase or sale of securities,
> accuracy and completeness of information, viruses, confidentiality, legal
> privilege, and legal entity disclaimers, available at
> http://www.jpmorgan.com/pages/disclosures/email.



-- 
____________________________________________________________
   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