Can you provide an expanded example to make it clearer what you mean? Maybe how would you replace a single node deep within a document.
What I said about an XML markup for the language was envisioning something similar to Stallman's Guile pipedream. Java is not going to be the trendy language forever, so if XML is aiming for a 20+ year lifespan then we should be too. If we want the server to palm off work onto the client then having the server send code to the client for execution will be a major way to achieve this. Now, ofcourse, we can do that now with Java, but when Java gets replaced by some other language then we'll either have to write versions of the code in both Java and the new language, have the client support both or else have an XML schema for a meta language that the client can transform into whatever language they happen to support. Infact, even now we need support for a multiple of languages as the client connecting to the server will not just be a browser. If the client is performing an administrative task then the user will prefer Python or Perl for the task. For this language to be multi-lingual I think it definitely needs to be a declarative language of some kind - preferably functional. But then I'm not really sure if this falls within the role of xml:db. -- Matthew Parry Bowerbird Computing Proprietor "XML tools designed to *your* specifications." <[EMAIL PROTECTED]> <URL:http://www.bowerbird.com.au/> ICQ#56864663 PO Box 1280 Nowra, NSW 2541, Australia - "There now, didn't I tell you to keep a good count? Well, there's and end of the story. God knows there's no going on with it now." - Sancho Panza. ------------------------------------------------------------------ Post a message: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Contact adminstrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ ------------------------------------------------------------------
