rocknbil - 6:17 pm on Jan 26, 2012 (gmt 0)
ie all values that appear after the <Height> element. Is there something wrong with the <Height>? Is the XML being truncated?
Don't think so, those both generate different errors if they are malformed. You can figure out how I know that. :-P
I just tried forcing the L/W/H values to int instead of .xx, no effect.
where is the DTD/Schema defined...
That is an EXTREMELY good question. I have no idea and part of this was searching for it. I don't know. :-\
Were you me I would be on the phone with USPS... or maybe on hold with USPS (sadLOL)
That's coming. I fear the hold time (I have a statue of a skeleton at a computer on my desk . . . you know the one . . . )
read this and see if you get any inspiration from it:
Yeah that's the (semi-worthless) documentation of the V4 API. The PDF version is at least a little more digestible.
Machinable is required for large packages, and it must be false, container must be rectangular . . . chokes without it. Played around with rearranging the order of the attributes too, unless you put them outside the tree it doesn't seem to have any effect.