CustomData - Revision history

GPHemsley: +spec

2012-11-10T16:14:58Z

+spec

← Older revision		Revision as of 16:14, 10 November 2012
Line 1:		Line 1:
	{{obsolete}}		{{obsolete\|spec=[http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#embedding-custom-non-visible-data-with-the-data--attributes HTML Standard: Embedding custom non-visible data with the data- attributes]}}

	Here are some ideas for how to include custom data in HTML documents.		Here are some ideas for how to include custom data in HTML documents.

2012-11-10T15:43:11Z

part of html

← Older revision		Revision as of 15:43, 10 November 2012
Line 1:		Line 1:
			{{obsolete}}

	Here are some ideas for how to include custom data in HTML documents.		Here are some ideas for how to include custom data in HTML documents.

2009-03-07T01:23:29Z

Reverted edits by Diyaseb (Talk); changed back to last version by Hixie

← Older revision		Revision as of 01:23, 7 March 2009
Line 32:		Line 32:

	''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're syndicating Web apps you're much more likely to run into problems with JS globals first. --Hixie''		''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're syndicating Web apps you're much more likely to run into problems with JS globals first. --Hixie''

	~~----~~
	[http://www.teachingsolutions.org/ftce.html FTCE test ]-"Who Else Wants To 'Crack-The-Code' 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?"

2009-03-06T09:35:52Z

← Older revision		Revision as of 09:35, 6 March 2009
Line 32:		Line 32:

	''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're syndicating Web apps you're much more likely to run into problems with JS globals first. --Hixie''		''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're syndicating Web apps you're much more likely to run into problems with JS globals first. --Hixie''

			----
			[http://www.teachingsolutions.org/ftce.html FTCE test ]-"Who Else Wants To 'Crack-The-Code' 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?"

2008-04-09T02:08:50Z

← Older revision		Revision as of 02:08, 9 April 2008
Line 30:		Line 30:

	If "custom" was site-specific, then wouldn't, e.g. "markbaker-my-thing" be better than a global "data-my-thing"? Otherwise there's a pretty good chance of collisions. Much more author friendly than namespaces. "data-" suggests that a central registry/wiki would be required to avoid collision.		If "custom" was site-specific, then wouldn't, e.g. "markbaker-my-thing" be better than a global "data-my-thing"? Otherwise there's a pretty good chance of collisions. Much more author friendly than namespaces. "data-" suggests that a central registry/wiki would be required to avoid collision.

			''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're syndicating Web apps you're much more likely to run into problems with JS globals first. --Hixie''

2008-04-09T01:08:52Z

Rejected

← Older revision		Revision as of 01:08, 9 April 2008
Line 27:		Line 27:
	<span custom-my-thing="50" custom-my-other-thing="4,5,1,2">bla bla</span>		<span custom-my-thing="50" custom-my-other-thing="4,5,1,2">bla bla</span>
	(rejected because "custom-" is not as good a prefix as "data-".)		(rejected because "custom-" is not as good a prefix as "data-".)
			</pre>

	If "custom" was site-specific, then wouldn't, e.g. "markbaker-my-thing" be better than a global "data-my-thing"? Otherwise there's a pretty good chance of collisions. Much more author friendly than namespaces. "data-" suggests that a central registry/wiki would be required to avoid collision.		If "custom" was site-specific, then wouldn't, e.g. "markbaker-my-thing" be better than a global "data-my-thing"? Otherwise there's a pretty good chance of collisions. Much more author friendly than namespaces. "data-" suggests that a central registry/wiki would be required to avoid collision.
	~~</pre>~~

2008-04-09T01:01:39Z

Value of site-specific prefixes

← Older revision		Revision as of 01:01, 9 April 2008
Line 27:		Line 27:
	<span custom-my-thing="50" custom-my-other-thing="4,5,1,2">bla bla</span>		<span custom-my-thing="50" custom-my-other-thing="4,5,1,2">bla bla</span>
	(rejected because "custom-" is not as good a prefix as "data-".)		(rejected because "custom-" is not as good a prefix as "data-".)

			If "custom" was site-specific, then wouldn't, e.g. "markbaker-my-thing" be better than a global "data-my-thing"? Otherwise there's a pretty good chance of collisions. Much more author friendly than namespaces. "data-" suggests that a central registry/wiki would be required to avoid collision.
	</pre>		</pre>

2008-04-05T00:23:35Z

Candidates

← Older revision		Revision as of 00:23, 5 April 2008
Line 5:		Line 5:
	<span data-thing="50" data-doohickey="4,5,1,2">bla bla</span>		<span data-thing="50" data-doohickey="4,5,1,2">bla bla</span>

	if (span.~~dataset~~.thing > 10) { ... }		if (span.dataSet.thing > 10) { ... }
	span.~~dataset~~.doohickey = '1,2,3,4';		span.dataSet.doohickey = '1,2,3,4';
	</pre>		</pre>

2008-04-04T20:51:03Z

Rejected

← Older revision		Revision as of 20:51, 4 April 2008
Line 13:		Line 13:
	<pre>		<pre>
	<span custom:my-thing="50" custom:my-other-thing="4,5,1,2">bla bla</span>		<span custom:my-thing="50" custom:my-other-thing="4,5,1,2">bla bla</span>
			(rejected because colons have special meaning in XML and so this would lead to
			the HTML and XML DOM representations differing, which violates our intent to
			keep the DOM accessors serialisation-agnostic.)
	</pre>		</pre>

	<pre>		<pre>
	<span ~~custom-~~my-thing="50" ~~custom-~~my-other-thing="4,5,1,2">bla bla</span>		<span><param name=my-thing value="50"><param name=my-other-thing value="4,5,1,2">bla bla</span>
			(rejected because it's so verbose that people would likely just do what
			they do now, violating the spec, instead of using it.)
	</pre>		</pre>

	<pre>		<pre>
	<span~~><param name=~~my-thing ~~value~~="50"~~><param name=~~my-other-thing ~~value~~="4,5,1,2">bla bla</span>		<span custom-my-thing="50" custom-my-other-thing="4,5,1,2">bla bla</span>
			(rejected because "custom-" is not as good a prefix as "data-".)
	</pre>		</pre>

	~~What are the reasons for rejection? The first uses namespaces which suck, and the third is super verbose, but what's wrong with the second?~~

2008-04-04T19:43:36Z

Why?

← Older revision		Revision as of 19:43, 4 April 2008
Line 22:		Line 22:
	<span><param name=my-thing value="50"><param name=my-other-thing value="4,5,1,2">bla bla</span>		<span><param name=my-thing value="50"><param name=my-other-thing value="4,5,1,2">bla bla</span>
	</pre>		</pre>

			What are the reasons for rejection? The first uses namespaces which suck, and the third is super verbose, but what's wrong with the second?