Seems like a poor idea for standards organizations to require that which is technically arbitrary. Which have done so? Can you supply references?
=p= From: Scott Hinkelman [mailto:scott.hinkel...@oracle.com] Sent: Friday, July 09, 2010 1:12 PM To: user@xmlbeans.apache.org Subject: RE: XMLBeans does not correctly propagate namespaces Please be aware that while at the XML/namespace technology level prefixes are technically arbitrary, from a higher business perspective several standards organizations have standardized them associate with specific name space names for consistency and some increase in interoperability. Thanks, Scott --------------- Scott R. Hinkelman Software Standards Architect AIA Standards Architecture and Strategy Oracle Corporation Mobile: 512.415.8490 From: Duane Zamrok [mailto:zam...@cubrc.org] Sent: Thursday, July 08, 2010 6:05 PM To: user@xmlbeans.apache.org Subject: RE: XMLBeans does not correctly propagate namespaces None the less, if XMLBeans does not present a means by which to dictate the namespaces (which I'm almost positive it does through the Dom Nodes) then that is a shortcoming, if only small. From: Wing Yew Poon [mailto:wing.yew.p...@oracle.com] Sent: Thursday, July 08, 2010 5:51 PM To: user@xmlbeans.apache.org Subject: RE: XMLBeans does not correctly propagate namespaces Justin, as Peter has clearly explained, prefixes are arbitrary; they are not what is important; namespaces are what matters. It appears that some people are hung up over the prefixes that get used to represent the namespaces ("the correct namespace prefix"). If your (or your customer's) code relies on some fixed prefixes, then, as Geir wrote, "I am afraid you may be in deep shit." That deep shit is not the fault of XMLBeans; it is the fault of bad code/software. - Wing Yew _____ From: Justin Bailey [mailto:justinbaile...@yahoo.com] Sent: Thursday, July 08, 2010 2:08 PM To: user@xmlbeans.apache.org Subject: Re: XMLBeans does not correctly propagate namespaces Follow-up... After some more searching, I found this thread which seems to describe exactly what the problem is: http://www.opensubscriber.com/message/user@xmlbeans.apache.org/1601039.html So it looks like this is a deficiency in XMLBeans, which is very disappointing. :( Anyway, I have resolved the issue by adding a regular expression parser which inspects the prefix that XMLBeans assigns to the namespace, then replaces it with the expected prefix. It's not what I would have preferred, but it does solve the problem. Thanks to the people who were kind enough to reply and provide assistance. I remain hopeful that this functionality will be added to XMLBeans in the future, since XMLBeans is in all other respects a very good library. Thanks, Justin
