I think I see what Bill means. The minimum you have to do to get a 
piece of text out of a XML is: XMLOpen to open the document, then 
XMLRoot to get a reference to the root node, then XMLFind (or other 
commands) to get a reference to the node you want, and finally 
XMLGetText to get the text (or XMLGetAttribute to get an attribute's 
value.)

You have to get used to it.

Emmanuel

At 8:55 PM +0200 5/29/07, Andreas Kiel wrote:
>I'm with JB,
>
>It's not so complicated to get the data out, maybe you want to have 
>a look at the w3org on how to work with xPath that might be helpful 
>(there is another site but can't recall the name - w3school or 
>something like that -

that's http://www.w3schools.com

>they have a lot of easy to understand examples.

Also, our site's documentation (user guide + tutorial) is not so bad:
http://www.satimage-software.com/en/xml_suite.html

>Though I have to agree depending on the structure of the XML there 
>might be a lot of calls. But this can be easily handled by some 
>handlers.
>You can send me the XML as well maybe I can help also.
>
>
>Regards
>Andreas
>
>On 29.05.2007, at 19:31, Jean-Baptiste Le Stang wrote:
>
>>CAn you send us a XML sample and your script ? I'm using the XMLLib 
>>scripting a lot and in my experience parsing XML documents has 
>>never required much call to the osax.
>>
>>++ JB
>>
>>On May 29, 2007, at 5:10 PM, Bill Steele wrote:
>>
>>>Whatever it is, it sure isn't intuitive.  Most everything I've 
>>>tried brings back "Can't make .... into type reference" or just 
>>>"can't get every..."
>>>
>>>Satimage XML suite works, but seems to require an awful lot of 
>>>steps to get down to the data.
>>>--
>>>
>>>Bill Steele
>>>[log in to unmask]