<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Neat. Does that reference mention anything about how XML was originally designed as a generic storage mechanism for data being moved from one architecture to another where the original meaning of the data might be lost due to differences of those architectures? I suppose a case can be made for using XML to transfer a SIP phone config from the tftp server to the phone itself but it makes no sense what-so-ever (to me at least) to use XML for a static config sitting on a server.<div><br class="webkit-block-placeholder"></div><div>It comes across to me about the same as someone saying they think using ftp would be a neat way to transfer rtp in a SIP conversation. It really doesn't matter if it can be done or not; why bother??</div><div><br class="webkit-block-placeholder"></div><div><br><div><div>On Dec 9, 2007, at 1:48 PM, Martin Smith wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"> <div> <!-- Converted from text/plain format --><p><font size="2">> Try to implement '#include' and '#exec' in a sane way with XML.<br> > You can't just include one valid XML in another. You have to make a<br> > partial XML. And apitting it out is usually way more complicated.<br> ><br> > Furthermore, there is the issue of partial processing: do you opt for<br> > one big XML file? Or continue with one XML file per .conf file?<br> ><br> <br> I'm pretty sure you can include one valid XML entity in another. This<br> functionality exists in SGML as well. I've seen it done both with parser<br> support and also simply defining your own &entity; (you can define an<br> entity in place or in another file somewhere else), which is relatively<br> easily, and then referring to that entity elsewhere in your document. I<br> found a nice IBM reference to using entities at<br> <a href="http://www.ibm.com/developerworks/xml/library/x-tipgentity.html">http://www.ibm.com/developerworks/xml/library/x-tipgentity.html</a>.<br> <br> In fact, I'd argue XML includes are more like the dialplan's idea of<br> inclusion when compared to includes in something like GCC.<br> <br> :)<br> <br> Martin Smith, Systems Developer<br> <a href="mailto:martins@bebr.ufl.edu">martins@bebr.ufl.edu</a><br> Bureau of Economic and Business Research<br> University of Florida<br> (352) 392-0171 Ext. 221<br> <br> _______________________________________________<br> --Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--">http://www.api-digital.com--</a><br> <br> asterisk-users mailing list<br> To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br> </font> </p> </div> </blockquote></div><br></div></body></html>