On Fri, 26 Sep 2003 21:28:50 -0400, Terry Rosenbaum wrote: >> One question. As the documents the differences are in text as opposed >> to xml structure (they compare as the same) why is changing the prefix >> a problem. If the app calling the xml is sensitive to the prefix change >> then I think it has a problem. > > It does look messy. And the resulting documents have extra unnecessary > text. I the src prefix is already defined with the correct namespace, > why add another one? > > If we already have a definition > > > xmlns:src="http://xml.apache.org/xindice/Query";
You shouldn't be using this namespace in your documents as this namespace is internal to Xindice. > Why add: > > xmlns:src1064505904532="http://xml.apache.org/xindice/Query"; > > and use a different prefix (src1064505904532) when you could still use > "src" since it is correctly defined? > > > It also may be the case that xindice does not use the same prefixes > > used in the query as are present in the resulting document. > > I'm not sure what you mean here. say I set my query to have xmlns:a="http://example.org/one"; and xmlns:b="http://example.org/two"; but the document is stored xmlns:x="http://example.org/one"; and xmlns:y="http://example.org/two";. At the moment xindice will return the ns prefix stored in the document not the one used in the query. It may also be possible that optimizations might mean the prefix is the one stored internally for the document. The prefix *must* to be changed if the src prefix is used with any other namespace. -k
