File Specification [Virus checked] ['securiQ.Watchdog': checked]



Date view Thread view Subject view Author view Attachment view

Anand_Lakhani@unipart.co.uk
Date: Wed 01 Sep 2004 - 11:44:08 BST


Jörn,

Thanks for your response.

I suppose EDI would be most fitting, however, there is an XML interface
for the transport method, let me explain:

If a file is sent to the server application then it is sent as an XML
file, with an appropriate transaction request type for the server to
interpret.  I have no problem with specifying the XML part of the file.
The CDATA part, however, corresponds to data from the client application,
which is an external enterprise database system.  The CDATA is in the
format of two header records, n number of records with extracted data, and
then a trailer record.  All records are no greater than 80 characters in
length.

In issuing the specification for the CDATA part of the interface between
the external application and the server application, I have found that the
software engineers are struggling and therefore take longer to develop a
faily simple piece of code.  Hence, it occurred to me that maybe a more
generic specification method can be used to provide a clear and concise
specification.

Can you help?

Maybe, you can help me with the XML part...because it would be good to
model the transport mechanism in UML.  The mechanism is really a set of
HTTP posts in the format of XML files representing requests to the server
application - I'm relatively new to XML - I understand the concept and I
can interpret XML, however, I have not done a great deal of development
with it.

Thanks for all your help with this.

Regards,
 Anand.
(See attached file: C.htm)
This e-mail has been sent in confidence to the named
 addressee(s).  If you are not the intended recipient you
 must not disclose or distribute it in any form, and you are
 asked to contact the sender immediately



Date view Thread view Subject view Author view Attachment view