XML, as suggested, is a flexible container but I think that the pundits suggest that you use elements for data and attributes for metadata which is used to refine or modify the default behaviour of an element. For example: <Money currency="aud">12.99</Money>
Then if you needed to store or convert the currency in your application - you have the option to do so. In your example the "Result" is described by the "precision" attribute as an "address" and the address data is contained in nested elements within the Result element. Pretty logical (though the "precision" nomenclature seems weird). So, depending on how and where you want to use the result would determine how you convert it to a dynamic array. I'd probably just convert the XML into: a [U2]attribute for the "precision" and one each for the address elements. However, you could easily put the precision into one [U2]attribute and the address elements into another [U2]attribute as multi-values. It really depends on how and where you want to use the result. Stuart Boydell -----Original Message----- since space concerns do not fall into place for my part, the xml has already been done, I had no control over that. I'm just trying to interpret the data correctly. > > <Result precision="address"><Latitude>39.931085</Latitude> > > <Longitude>-77.387943</Longitude><Address>1001 N Some Rd</Address> > > > > > > <City>Somewhere</City><State>PA</State><Zip>15063- > 1404</Zip><Country>US</Cou > > ntry> > > </Result> _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
