- From: Alex Muir <alex.g.muir@gmail.com>
- Date: Sat, 20 Oct 2012 22:35:31 -0400
- To: public-xml-processing-model-comments@w3.org
- Message-ID: <CAFtPEJZfqdtpPA0PBRycKrR65ZwN8spN961VTHAwYpPYLbqM_g@mail.gmail.com>
"Vojtech: Instead of changing XDM we should take a simple, pragmatic approach. ... It's not full support for non-XML, it's stilly mainly an XML processing language, it just makes things easier if you get non-XML." [ http://www.w3.org/XML/XProc/2012/10/04-minutes.html#item05] Given this is a good idea above...Just wondering if it would be a good idea to given the use of a resource manager to make it that non xml data input or output would need to be stored in a resource manager and thus not need to flow through the pipeline but rather be easily accessible. Perhaps what would flow from a step that produced non-xml into the resource manager would be some xml letting the user know something related to it's storage in the resource manager. Regards -- - Alex G. Muir Software Engineering Consultant Linkedin Profile : http://ca.linkedin.com/pub/alex-muir/36/ab7/125 Love African Kora Music? Take a moment to listen to Gambia's - Amadu Diabarte & Jali Bakary Konteh www.bafila.bandcamp.com Your support keeps Africa's griot tradition alive... Cheers!
Received on Sunday, 21 October 2012 02:35:58 UTC