Merge pull request qt4cg#2449 from michaelhkay/2445-xsi-attributes-in-element-to-map

ndw · web-flow · commit 661d70da0aa1 · 2026-02-10T16:56:50.000Z
2445 Add rules for xsi namespace elements in element-to-map
diff --git a/specifications/xpath-functions-40/src/xpath-functions.xml b/specifications/xpath-functions-40/src/xpath-functions.xml
@@ -7479,7 +7479,7 @@ correctly in all browsers, depending on the system configuration.</emph></p>-->
                <olist>
                   <item><p>Let <code>$EE</code> be
                   the set of all elements named <var>N</var>, specifically
-                  <code>$input/descendant-or-self::*[node-name(.) eq <var>N</var>]</code>.</p>
+                  <code>$input/descendant-or-self::*[node-name(.) eq <var>N</var>]</code>. </p>
                   </item>
                   
                   <item>
@@ -7601,6 +7601,27 @@ correctly in all browsers, depending on the system configuration.</emph></p>-->
                
             </div3>
             
+            <div3 id="id-xsi-attributes">
+               <head>Attributes in the <code>xsi</code> namespace</head>
+               <p>This section defines modifications to the above rules that apply to elements having
+               attributes in the <code>xsi</code> namespace (that is, 
+                  <code>http://www.w3.org/2001/XMLSchema-instance</code>).</p>
+               
+               <ulist>
+                  <item><p>When analyzing a corpus using <function>fn:element-to-map-plan</function>,
+                  elements having the attribute <code>xsi:nil="true"</code> are ignored. If all
+                  elements with a given name have this attribute, allocate the layout <code>mixed</code>.</p></item>
+                  <item><p>When deciding whether an element has any attributes (for example to decide
+                        between the layouts <code>empty</code> and <code>empty-plus</code>),
+                        all attributes in the <code>xsi</code> namespace are ignored.</p></item>
+                  <item><p>When converting an individual element to a map, 
+                        all attributes in the <code>xsi</code> namespace are ignored.</p></item>
+                  <item><p>Notwithstanding the above, elements having the <code>nilled</code> property
+                  (which essentially means they are schema-validated and have the attribute <code>xsi:nil="true"</code>),
+                  are treated specially by each of the possible element layouts.</p></item>
+               </ulist>
+            </div3>
+            
             <div3 id="id-conversion-plan-structure">
                <head>Structure of the conversion plan</head>
                
@@ -8014,6 +8035,9 @@ map( xs:string,
                   
                   <item><p><emph>Element order: </emph> The order of child elements is lost when
                   <code>record</code> layout is used and the element has multiple children with the same name.</p></item>
+                  
+                  <item><p><emph>XSI attributes: </emph> Attributes in the <code>xsi</code> namespace (for example,
+                        <code>xsi:type</code> and <code>xsi:nil</code>) are not represented in the result. .</p></item>
                </ulist>
             </div3>
             
@@ -8093,18 +8117,7 @@ map( xs:string,
     }
   ] }]]></eg></td>
                      </tr>
-                     <!--<tr>
-                        <td><eg><![CDATA[]]></eg></td>
-                        <td><eg><![CDATA[]]></eg></td>
-                     </tr>
-                     <tr>
-                        <td><eg><![CDATA[]]></eg></td>
-                        <td><eg><![CDATA[]]></eg></td>
-                     </tr>
-                     <tr>
-                        <td><eg><![CDATA[]]></eg></td>
-                        <td><eg><![CDATA[]]></eg></td>
-                     </tr>-->
+ 
                   </tbody>
                </table>
                <p>The following more complex example demonstrates a case where the default conversion is
