Re: FpML-VAL Updated FX Rule Proposal

[Christian Nentwich <christian@xxxxxxxxxxxxxxxx>]

A few more comments (forwarding these):

1.	fx-5 and fx-6 I think are the wrong way round.
Currency1SideRate/currency s/b same as quotedCurrencyPair/currency2 not
currency 1 and vice versa. All the examples supplied by ISDA fail these
rules, but would pass if the rules were the other way round
2.	fx-12 - it says observeredDate, s/b observationDate
3.	fx-26 - s/b /valueDate not \valueDate for consistency
4.	fx-33 - I think the document should say
initialPayerReference/@href and initalReceiverReference/@href
5.	fx-40 - I think the doc means fxSingleLeg/currency1ValueDate not
valueDate1, similarly with valueDate2

regards,

Christian

matthew.d.rawlings@xxxxxxxxxxxx wrote:
> The rules are very welcome. They will help with FX.
>
> I have a few comments:
>
>    1. "present" versus "exists" - we previously discussed this choice
>       of terms at the VWG and agreed to use "exists" because the
>       semantics are clearly defined in XPath.
>    2. Why can't fx-24 be represented in the schema using a facet?
>    3. fx-12 - how do I "match one of the calculated schedule dates"?
>    4. fx-13 - how do I "should fall on a date defined by
>       averageRateObservationDate/observationDate"?
>
>
>
> Matthew Rawlings
> +44 7917 596 827
>
>
> *"Andrew Jacobs" <andrew.jacobs@xxxxxxxxxxxxxx>*
> Sent by: valwg@xxxxxxxx
>
> 11/03/2008 11:44
> Please respond to
> valwg@xxxxxxxx
>
>
> 	
> To
> 	<valwg@xxxxxxxx>
> cc
> 	
> Subject
> 	FpML-VAL Updated FX Rule Proposal
>
>
>
> 	
>
>
>
>
>
> With the corrections discussed previously.
>
> Thanks
>  
> Andrew Jacobs
> Director & CTO
> HandCoded Software Ltd
> Mob: +44 (0)7710 304239
>  [attachment "FX Business Validation Rules.doc" deleted by Matthew D 
> Rawlings/JPMCHASE]
>
> ------------------------------------------------------------------------
>
> This communication is for informational purposes only. 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. 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.

-------------------------------------------------------------------------------
To unsubscribe: Email majordomo@xxxxxxxx with a blank subject line
In the body include the line: unsubscribe valwg youremail@address
To view archives: http://www.fpml.org/_wgmail/_valwgmail/threads.html