</ul><hr><p>The following <a href=#event-handler-content-attributes>event handler content attributes</a> may
</ul><div class=impl>
<p>These attributes are only defined by this specification as
attributes for <a href=#html-elements>HTML elements</a>. When this specification
refers to elements having these attributes, elements from namespaces
that are not defined as having these attributes must not be
considered as being elements with these attributes.</p>
<div class=example>
<p>For example, in the following XML fragment, the "<code title="">bogus</code>" element does not have a <code title=attr-dir><a href=#the-dir-attribute>dir</a></code> attribute as defined in this
specification, despite having an attribute with the literal name
<hr><p>The following <a href=#event-handler-content-attributes>event handler content attributes</a> may
be specified on any <a href=#html-elements title="HTML elements">HTML
element</a>:</p>
<h4 id=microdata-and-other-namespaces><span class=secno>5.2.6 </span>Microdata and other namespaces</h4>
<p>Currently, the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>,
<code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code>, and other microdata
attributes are only defined for <a href=#html-elements>HTML elements</a>. This
means that attributes with the literal names "<code title="">itemscope</code>", "<code title="">itemprop</code>", etc,
do not cause microdata processing to occur on elements in other
namespaces, such as SVG.</p>
<div class=example>
<p>Thus, in the following example there is only one item, not
two.</p>
<pre class=bad><p itemscope></p> <!-- this is an item (with no properties and no type) -->
<svg itemscope></svg> <!-- this is not, it's just an <code><a href=#svg>svg</a></code> element with an invalid unknown attribute --></pre>
</div>
<h3 id=microdata-dom-api><span class=secno>5.3 </span>Microdata DOM API</h3>
</ul><hr><p>The following <a href=#event-handler-content-attributes>event handler content attributes</a> may
</ul><div class=impl>
<p>These attributes are only defined by this specification as
attributes for <a href=#html-elements>HTML elements</a>. When this specification
refers to elements having these attributes, elements from namespaces
that are not defined as having these attributes must not be
considered as being elements with these attributes.</p>
<div class=example>
<p>For example, in the following XML fragment, the "<code title="">bogus</code>" element does not have a <code title=attr-dir><a href=#the-dir-attribute>dir</a></code> attribute as defined in this
specification, despite having an attribute with the literal name
<hr><p>The following <a href=#event-handler-content-attributes>event handler content attributes</a> may
be specified on any <a href=#html-elements title="HTML elements">HTML
element</a>:</p>
<h4 id=microdata-and-other-namespaces><span class=secno>5.2.6 </span>Microdata and other namespaces</h4>
<p>Currently, the <code title=attr-itemscope><a href=#attr-itemscope>itemscope</a></code>,
<code title=attr-itemprop><a href=#names:-the-itemprop-attribute>itemprop</a></code>, and other microdata
attributes are only defined for <a href=#html-elements>HTML elements</a>. This
means that attributes with the literal names "<code title="">itemscope</code>", "<code title="">itemprop</code>", etc,
do not cause microdata processing to occur on elements in other
namespaces, such as SVG.</p>
<div class=example>
<p>Thus, in the following example there is only one item, not
two.</p>
<pre class=bad><p itemscope></p> <!-- this is an item (with no properties and no type) -->
<svg itemscope></svg> <!-- this is not, it's just an <code><a href=#svg>svg</a></code> element with an invalid unknown attribute --></pre>
</div>
<h3 id=microdata-dom-api><span class=secno>5.3 </span>Microdata DOM API</h3>