Alright, take #2...
The name
XML::UPS was not liked and more than one reply said I should try writing a module myself. I think a module would be great, but my
question was
to anyone who might have prior experience using Perl to interface with the XML query servers of the United Postal Service.
I will admit, the notion of writing such a module myself has a definate appeal. It would be a heck of a learning experience. But I am only now trying to grasp
use strict; and
use Module::Name;, I am unfamiliar with XML, and know nothing about what goes into writing a module. I would hate to pollute the greater Perl community with insecure and/or buggy code.
That said, what do the Monks think? Should a
lowly initiate such as myself dare to undertake such an ambitious quest?
As for the module name
XML::UPS, ok, so you didn't like it and thought
Business::UPS::XML would be better. I was not invested in the name. It seemed a decent enough title for my post. Giving the name further consideration, I might instead suggest a name such as
Business::XML::UPS which would allow for a nice use of Module Namespace hierarchy allowing for future modules writen for FedEx, USPS, etc to be substituted for the
UPS portion. As there seems to be a trend towards utilizing XML as a Peer to Peer Data Interchange medium, it might be a good fit.
Are there any XML gurus who could advise me on XML and on XML modules? UPS uses a very specific XML format and must be queried with a specific XML format. Are there any modules which can be made to conform to user defined specifications?
edited: Sun May 4 16:13:32 2003
by jeffa - title change (was: XML & United Postal Service)