<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none"><!--P{margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>In DDI-Lifecycle 3.2 the narrative documentation <br>
<br>
<a id="lnk103594" href="http://www.ddialliance.org/Specification/DDI-Lifecycle/3.2/XMLSchema/FieldLevelDocumentation/schemas/reusable_xsd/complexTypes/AbstractIdentifiableType.html">http://www.ddialliance.org/Specification/DDI-Lifecycle/3.2/XMLSchema/FieldLevelDocumentation/schemas/reusable_xsd/complexTypes/AbstractIdentifiableType.html</a><br>
<br>
for the type<br>
<br>
{ddi:reusable:3_2}AbstractIdentifiableType<br>
<br>
states that<br>
<br>
&quot;An entity can either be identified either by a URN and/or an identification <br>
sequence. At a minimum, one or the other is required. &quot;<br>
<br>
However, according to the XML Schema, the following XML document is valid.<br>
<br>
---8&lt;---8&lt;---8&lt;---<br>
&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;<br>
&lt;ddi:DDIInstance <br>
&nbsp;&nbsp;&nbsp; xmlns:ddi=&quot;ddi:instance:3_2&quot; <br>
&nbsp;&nbsp;&nbsp; xmlns:r=&quot;ddi:reusable:3_2&quot; <br>
&nbsp;&nbsp;&nbsp; &gt;<br>
&nbsp;&nbsp; &nbsp;<br>
&nbsp; &lt;r:Agency&gt;acme.org&lt;/r:Agency&gt;<br>
&nbsp; &lt;r:ID&gt;ddi_instance&lt;/r:ID&gt;<br>
&nbsp; &lt;r:Version&gt;1&lt;/r:Version&gt;<br>
&nbsp; <br>
&nbsp; &lt;r:Agency&gt;acme.org&lt;/r:Agency&gt;<br>
&nbsp; &lt;r:ID&gt;another_ddi_instance&lt;/r:ID&gt;<br>
&nbsp; &lt;r:Version&gt;2&lt;/r:Version&gt;<br>
&nbsp; <br>
&lt;/ddi:DDIInstance&gt;<br>
---8&lt;---8&lt;---8&lt;---<br>
<br>
This is invalid according to specification, but the restriction<br>
is not expressed formally with XML Schema.<br>
<br>
My question is then:<br>
<br>
Is this a mistake/bug in the XML Schema? (If not, please explain why<br>
it is better to formally allow such invalid documents?)<br>
<br>
The XML Schema language allows one to express formally the restriction <br>
&quot;either one or both&quot;. The details are laid down, for instance, in the answer<br>
http://stackoverflow.com/questions/9863056/xsd-schema-either-one-or-both<br>
<br>
Here's a patch for the file &quot;reusable.xsd&quot; that is included in the current<br>
distribution package of the DDI-Lifecycle 3.2:</p>
<p><br>
</p>
<p><a id="lnk541388" href="http://www.pastebucket.com/72481">http://www.pastebucket.com/72481</a></p>
<p><br>
</p>
<p><br>
</p>
</div>
</body>
</html>