By "should", I merely meant that the API as specifies insertion of the source attribution attributes and code as written does insert the source attribution information when functioning correctly. If the behavior of the code fulfills the contract of the API, then the presence of source attribution information is not a bug (perhaps instead a feature you do not desire).
I was not commenting on the correctness/incorrectness of the API. The API does have a few rough edges, I suppose.
I just remove the source attribution information from returned XML Resources when necessary (e.g. some parser doesn't like it).
I recall that the "src" prefix will always be made unique
when necessary to avoid conflict with any existing prefixes
so you may be able to handle the presence of the src:col and
src:key. To locate the prefix, you need to search the namespace
definitions for the one that matches the URI. If you do not wish to have those present, then, you
are correct in observing that you are responsible for
stripping them out.
Since this is open source, you are free to propose and implement an enhancement providing some means to control whether or not source attribution attributes are added to the returned XML Resources.
-Terry
Kurt Kavanaugh wrote:
I respectfully disagree. This is our data. in SQL land you do not add data to a ResultSet. I would argue this is akin to a ResultSetMetaData item in JDBC land. an XML database should not alter the content in a return XML set. Data is sacred. If you wish to have this information available it should be in the Resource object separate from the content. As it is for each and every returned item resource I must strip this out.
Just my opinion.
-----Original Message----- From: Terry Rosenbaum [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 06, 2004 10:22 AM To: [EMAIL PROTECTED] Subject: Re: Top level tag attributes: src:col, src:key
These attributes should appear once in the result. That is not a bug. Currently, there is no way to turn off the source attribution information (src:col and src:key).
The bug was that the xmlns:src and other namespace definitions were appearing in each element of the result thus providing useless redundant information. AFAIK, that bug () is now fixed.
Are you still seeing the bug, or are you merely seeing the normal behavior (xmlns:src once per result at the top level)?
-Terry
Kurt Kavanaugh wrote:
Still in the returned xml from a query. I am using the beta3 jar. It was mentioned in the user archives that this was a bug. Is this fixed? Is it going to be fixed.
We are going to release soon and I either need to ignore these attributes and wait for the fix. Or strip them out upon contact.
Thanks
Kurt
P.S. I put this to the user communitiy... the answer I got was not what I am seeing. I have been using Xindice for about 6 months on a project that is going live very soon.
