logo       

Re: FW: VoiceXML 2.1 and PI issue: msg#00022

web.voice

Subject: Re: FW: VoiceXML 2.1 and PI issue



I agree with DanC that the main inconvenient about PIs is that they
aren't bound to namespaces. And it would be a problem if VoiceXML was
mixed with other markup in a document. Unless the PI's semantics
applied to any XML document, which I don't expect VoiceXML 2.1 to do.

> Dave gave another: the DOM doesn't give access to them.

It does and XSLT too.
See
http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/core.html#ID-1004215813

On the other hand, SOAP 1.2 doesn't allow them. I know the reasons for
that have been discussed many times, but I'm still hold the grudge that
SOAP has unilaterally killed PIs in any XML document that might be wrapped
in it. Just like doctypes. But I digress.

So my point is: the only reason why PIs should be avoided is
namespaces. The other ones mentioned in this thread aren't valid, in
my opinion.

Max.






<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise