<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.whatwg.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Diyaseb</id>
	<title>WHATWG Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.whatwg.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Diyaseb"/>
	<link rel="alternate" type="text/html" href="https://wiki.whatwg.org/wiki/Special:Contributions/Diyaseb"/>
	<updated>2026-04-16T13:27:01Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.3</generator>
	<entry>
		<id>https://wiki.whatwg.org/index.php?title=CustomData&amp;diff=3557</id>
		<title>CustomData</title>
		<link rel="alternate" type="text/html" href="https://wiki.whatwg.org/index.php?title=CustomData&amp;diff=3557"/>
		<updated>2009-03-06T09:35:52Z</updated>

		<summary type="html">&lt;p&gt;Diyaseb: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Here are some ideas for how to include custom data in HTML documents.&lt;br /&gt;
&lt;br /&gt;
== Candidates ==&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;span data-thing=&amp;quot;50&amp;quot; data-doohickey=&amp;quot;4,5,1,2&amp;quot;&amp;gt;bla bla&amp;lt;/span&amp;gt;&lt;br /&gt;
&lt;br /&gt;
if (span.dataSet.thing &amp;gt; 10) { ... }&lt;br /&gt;
span.dataSet.doohickey = &#039;1,2,3,4&#039;;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Rejected ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;span custom:my-thing=&amp;quot;50&amp;quot; custom:my-other-thing=&amp;quot;4,5,1,2&amp;quot;&amp;gt;bla bla&amp;lt;/span&amp;gt;&lt;br /&gt;
(rejected because colons have special meaning in XML and so this would lead to&lt;br /&gt;
the HTML and XML DOM representations differing, which violates our intent to&lt;br /&gt;
keep the DOM accessors serialisation-agnostic.)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;span&amp;gt;&amp;lt;param name=my-thing value=&amp;quot;50&amp;quot;&amp;gt;&amp;lt;param name=my-other-thing value=&amp;quot;4,5,1,2&amp;quot;&amp;gt;bla bla&amp;lt;/span&amp;gt;&lt;br /&gt;
(rejected because it&#039;s so verbose that people would likely just do what&lt;br /&gt;
they do now, violating the spec, instead of using it.)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&amp;lt;span custom-my-thing=&amp;quot;50&amp;quot; custom-my-other-thing=&amp;quot;4,5,1,2&amp;quot;&amp;gt;bla bla&amp;lt;/span&amp;gt;&lt;br /&gt;
(rejected because &amp;quot;custom-&amp;quot; is not as good a prefix as &amp;quot;data-&amp;quot;.)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If &amp;quot;custom&amp;quot; was site-specific, then wouldn&#039;t, e.g. &amp;quot;markbaker-my-thing&amp;quot; be better than a global &amp;quot;data-my-thing&amp;quot;?  Otherwise there&#039;s a pretty good chance of collisions.  Much more author friendly than namespaces.  &amp;quot;data-&amp;quot; suggests that a central registry/wiki would be required to avoid collision.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;The whole feature is site-specific -- who are you going to collide with? In syndication environments, of course, you could provide per-site prefixes as a convention, e.g. data-markbaker-thing, but if you&#039;re syndicating Web apps you&#039;re much more likely to run into problems with JS globals first. --Hixie&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
[http://www.teachingsolutions.org/ftce.html  FTCE test ]-&amp;quot;Who Else Wants To &#039;Crack-The-Code&#039; Of Your FTCE Test In ONLY 7 Days And Go To $37,857.00 In Florida Teacher Salary Right Now...Much EASIER Than You Ever Thought Possible?&amp;quot;&lt;/div&gt;</summary>
		<author><name>Diyaseb</name></author>
	</entry>
</feed>