qname and namespace context

Section 8.4.1 ("Namespace Context") specifies that namespace context must be preseved when copying attribute values or text nodes from the source to the destination. There are a number of complexities in this, and in some cases it is impossible.

For instance, attribute alpha created by <copy> #1 may require prefix P to be bound to foo.com while attribute beta created by <copy> #2 for the same element my require prefix P to be bound to bar.com. This conflict cannot be resolved.

There is another problem having to do with default namespace for element-to-element copy. These problems are due to xml 1.0 not allowing a namespace declaration of the form:

xmlns:P=""

(this is legal in xml 1.1).

How do other bpel engine developers handle this issue ?

 

 

 

I think it is important to preserve the actual namespace, not the prefix. However you are right, it is an interesting use case if two namespace prefixes collide. In our (designer) case it is not possible, since you define the prefixes only on the root element, so all prefixes which can be used in XPath are unique.

--
Chief Architect (R&D) SEEBURGER.com
http://bernd.eckenfels.net

XML.org Focus Areas: BPEL | DITA | ebXML | IDtrust | OpenDocument | SAML | UBL | UDDI
OASIS sites: OASIS | Cover Pages | XML.org | AMQP | CGM Open | eGov | Emergency | IDtrust | LegalXML | Open CSA | OSLC | WS-I