FpML-FXWG-Legacy Fwd: FW: 1st stab

["Danielle Cauthen" <dcauthen@xxxxxxxx>]

--- In fpml-fx@xxxxxxxxxxxxxxx, Rick Schumacher 
<rick.schumacher@...> wrote:

FYI ... below are some changes that Justin made to the DTD, based 
upon his
work with Steven.

Rick


-----Original Message-----
From: Oglethorpe, Justin [IT] [mailto:justin.oglethorpe@...]
Sent: Wednesday, December 12, 2001 6:18 AM
To: 'Steven.Lord@...'; Oglethorpe, Justin [IT]
Cc: rick.schumacher@...
Subject: RE: 1st stab


Steven,
I have now updated the DTD. Here's an audit trail of the changes I 
have now
made:

1) replaced choice of "touch" and "noTouch" empty elements with a 
single
element "touchCondition" with a scheme to hold allowable values 
of "touch"
and "noTouch"
2) likewise, replaced choice of "aboveTrigger" and "belowTrigger" 
empty
elements with a single element "triggerCondition" with a scheme to 
hold
allowable values of "aboveTrigger" and "belowTrigger"
3) deleted element "routing"
4) deleted element "address"
5) added lots of missing "type" attributes to elements with content 
models
defined by parameter entities
6) reinstated the following parameter entities:
	FpML_SplitSettlement
	FpML_RoutingIds
7) removed the e-dtype "string" attribute of the following elements:
	routingReferenceText
	routingAccountNumber
8) taken out comments that really belonged in the element 
definitions xml
file
9) re-deleted %FpML_FXFee
10) re-instated cutNameScheme and cutNameSchemeDefault
11) re-instated the changes to optionOnCurrency and faceOnCurrency 
and
removal of id attributes from putCurrencyAmount and 
callCurrencyAmount

I attach a zip which contains the new DTD and a subdirectory of new 
or
replacement .gif files, in line with the above changes. I'm not sure 
of your
process, so let me know if you need anything else. I haven't had 
time to
supply missing definitions - maybe Rick can pick this up when he 
gets back -
but I hope this gives you enough to make it worth moving forward.

Best regards,
Justin.


Justin Oglethorpe
+44 (0) 20 7508 3852 (desk)

This message is confidential and the property of Citigroup. It may 
also
be privileged or otherwise protected by work product immunity or 
other
legal rules. If you have received it by mistake please let us know by
reply and then delete it from your system; you should not copy the
message or disclose its contents to anyone.


-----Original Message-----
From: Steven.Lord@... [mailto:Steven.Lord@...]
Sent: 11 December 2001 11:20
To: justin.oglethorpe@...
Cc: rick.schumacher@...
Subject: RE: 1st stab


I think it will be easier if you just send me your most upto date 
DTD. 
Assuming it's as well documentated as the previous one it will not 
be 
difficult for me to put it into the structure.

I don;t have any real tips - I end up editing it and then opening up 
the top level dtd into XML Authority to check it.

Steven

-----Original Message-----
From: justin.oglethorpe 
Sent: 11 December 2001 11:16
To: Lord, Steven
Cc: justin.oglethorpe; rick.schumacher
Subject: RE: 1st stab


Steven,
That's what I thought. Trouble is, I made a number of clean-up 
changes
before I handed the DTD over to Rick, but because I also mucked 
things 
up by
re-arranging the order of the entity declarations, he seems to have 
decided
- understandably - to go back to the previous version. I don't mind 
making
the changes again in your version (in the dtd.zip file you sent 
out), 
but do
you have any tips on how to view and edit this component DTD with 
all 
the
references to externally defined parameter entities resolved? At the 
moment
it has 53 errors because of the way the DTDs are split - it would 
just 
be
easier to see what I was doing without them showing up!

Any tips?
Justin.

Justin Oglethorpe
+44 (0) 20 7508 3852 (desk)

This message is confidential and the property of Citigroup. It may 
also
be privileged or otherwise protected by work product immunity or 
other
legal rules. If you have received it by mistake please let us know by
reply and then delete it from your system; you should not copy the
message or disclose its contents to anyone.


-----Original Message-----
From: Steven.Lord@... [mailto:Steven.Lord@...]
Sent: 10 December 2001 18:21
To: justin.oglethorpe@...
Cc: rick.schumacher@...
Subject: RE: 1st stab


Rick is in Florida (or some such exotic place) the first few days of 
this week. I think now that the DTD has been integrated we need to 
be 
careful with amendments - either make them within the DTDs I sent 
you 
or be VERY careful to note the changes you are making if you are 
doing 
it in your own version since I will need to integrate into the 
central 
copy.

Steven

-----Original Message-----
From: justin.oglethorpe 
Sent: 10 December 2001 17:42
To: Lord, Steven
Cc: justin.oglethorpe; rick.schumacher
Subject: RE: 1st stab


Steven,
Is Rick out of touch at the moment? I was hoping he would be able to 
tell me
a bit about the DTD version he sent you before I went ahead and 
fixed 
the
issues you had raised. If he is away at the moment, I'll try to fix 
the
issues anyway and send you something afresh tomorrow.

Regards,
Justin.

Justin Oglethorpe
+44 (0) 20 7508 3852 (desk)

This message is confidential and the property of Citigroup. It may 
also
be privileged or otherwise protected by work product immunity or 
other
legal rules. If you have received it by mistake please let us know by
reply and then delete it from your system; you should not copy the
message or disclose its contents to anyone.


-----Original Message-----
From: Steven.Lord@... [mailto:Steven.Lord@...]
Sent: 10 December 2001 11:53
To: rick.schumacher@...
Cc: justin.oglethorpe@...
Subject: RE: 1st stab


Cool. Attached is the first cut documentation. 

A couple of points:

1. There are empty elements belowTriggerRate and aboveTriggerRate - 
the 
approach in the IRD WG (not sure if this is a formal part of the 
architecture) was not to have empty elements for choices but instead 
have an element and a scheme (values here are above and below).

2. Similar with touch and noTouch except this is merely a boolean so 
instead should have a single element (say touch) of type boolean.

3. Some element descriptions seem to be missing (search for 'TBA'). 

4. Also some type information is missing (you'll see this with the 
search for 'TBA') for example streetAddress does not have the type 
attribute defined. 

5. FpML_PaymentRouting.gif is missing.

6. FpML_FXFee has a description stating it may no longer be 
required. 
Need to remove if it isn't required.

I thought it best you guys review this prior to circulating to the 
co-ord group for comments.

Attached are the dtds. I have removed any version / date info as I 
have 
them in a repository so I don't want the dtds name changing in the 
working copies. When we publish to the standards committee I will 
add a 
date to each dtd.

Let me know when you want a new version. I should get a chance to do 
a 
more thorough review later this week.

Steven

-----Original Message-----
From: rick.schumacher 
Sent: 07 December 2001 23:43
To: Lord, Steven
Cc: rick.schumacher; justin.oglethorpe
Subject: 1st stab


OK Steven ... here's all the GIF files, as well as the element and 
entity
descriptions, along with the DTD.  If you look at the DTD source, 
you'll see
comments for the sections that you'll need to remove.  I didn't send 
the
product architecture section yet, because I'm only about 50% done.

I've copied Justin as well ... he might be able to assist if you have
specific questions (although he's been very busy lately).

Let me know how it goes.  FYI ... I'll be back on Thursday.

Rick

 <<FX-forSteven.zip>> 


Visit our website at http://www.ubswarburg.com

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.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities 
or 
related financial instruments.


Visit our website at http://www.ubswarburg.com

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.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities 
or 
related financial instruments.

--- End forwarded message ---



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