QFD-RD-+Incorrect+doc+ID+format

Please contribute your comments via the discussion tab above. Outcomes and resolution will be added at the bottom of this page.

=QFD/RD: impact of incorrect doc id format?=

0 row selected - rows selected - [|clear] || [|JoeLamy] Issue: We are seeing an incorrect format for the document unique id value, where instead of an OID or OID^ext it is a UUID.
 * ~ 1 - 1 of 1
 * || [[image:http://www.wikispaces.com/i/user_none_lg.jpg width="48" height="48" caption="JoeLamy" link="http://www.wikispaces.com/user/view/JoeLamy"]] ||
 * JoeLamy ||

Example (returned by Query for docs):      

This does not appear to affect the doc id's subsequent use in Retrieve Doc requests. What is the impact? In cross gateway interactions, is the doc id ever treated as anything other than an opaque string?

Tentative severity level: 4-Low|| || [|[delete]] =Interoperability issues= 0 row selected - rows selected - [|clear] || On the surface this is looks harmless. Except that many XDS/XCA/XDR implementers validate the data format of all fields received in which case the message containing this identifier would be rejected as invalid. Interoperability requires the sender to conform to the defined data formats. || help on how to format text
 * permalink ||
 * ~ 1 - 1 of 1
 * [[image:http://www.wikispaces.com/i/user_none_lg.jpg width="48" height="48" caption="BillMajurski" link="http://www.wikispaces.com/user/view/BillMajurski"]] || [|BillMajurski]