Del element - Revision history

Annevk: categorize

2011-01-26T12:19:46Z

categorize

← Older revision		Revision as of 12:19, 26 January 2011
Line 56:		Line 56:
	* +1 [[User:Tantek\|Tantek Çelik]] - this happens to me often when I have blog-like or other essay content that I update by hand. Since I typically do updates to any particular content about once a day, day-level granularity is sufficient. Picking an arbitrary time seems like being forced to provide "fake" metadata which I don't want to do.		* +1 [[User:Tantek\|Tantek Çelik]] - this happens to me often when I have blog-like or other essay content that I update by hand. Since I typically do updates to any particular content about once a day, day-level granularity is sufficient. Picking an arbitrary time seems like being forced to provide "fake" metadata which I don't want to do.
	* +1 [[User:EdwardOConnor\|EdwardOConnor]] - I have the same sort of experience as Tantek in this case; confabulating precision where none exists feels quite wrong.		* +1 [[User:EdwardOConnor\|EdwardOConnor]] - I have the same sort of experience as Tantek in this case; confabulating precision where none exists feels quite wrong.

			[[Category:Proposals]]

Tantek: /* datetime attribute changes */ link to datetime attribute in w3c dev draft, add related validator.nu bug

2010-08-31T09:19:36Z

datetime attribute changes: link to datetime attribute in w3c dev draft, add related validator.nu bug

← Older revision		Revision as of 09:19, 31 August 2010
Line 29:		Line 29:
	ACCEPTED 2010-08-24: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/028113.html		ACCEPTED 2010-08-24: http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/028113.html

	The <code>del</code> element has a <code>datetime</code> attribute that requires an explicit date and time.		Related: [http://bugzilla.validator.nu/show_bug.cgi?id=763 Validator.nu Bug 763]

			The <code>del</code> element has a <code>[http://dev.w3.org/html5/spec/edits.html#attr-mod-datetime datetime]</code> attribute that requires an explicit date and time.

	Summary: the <code>datetime</code> attribute (on both del and ins elements) should permit just a date value, in addition to permitting explicit dates with times.		Summary: the <code>datetime</code> attribute (on both del and ins elements) should permit just a date value, in addition to permitting explicit dates with times.

Tantek: /* timeref */ t

2010-08-25T01:42:43Z

timeref: t

← Older revision		Revision as of 01:42, 25 August 2010
Line 18:		Line 18:
	Advantages:		Advantages:
	* <strong>visible metadata!</strong> the date of the change can be shown visibly (as many real world examples do (citations needed), rather than invisibly in a hidden datetime attribute, which encourages higher fidelity metadata.		* <strong>visible metadata!</strong> the date of the change can be shown visibly (as many real world examples do (citations needed), rather than invisibly in a hidden datetime attribute, which encourages higher fidelity metadata.
	* <strong>DRY! (don't repeat yourself).</strong> compare the previous example to the timeref one - the timeref example provides the date only <em>once</em> instead of duplicating it. Whenever multiple del/ins edits occur at the same date/time they can all reference a single <code><time&gt</code> element.		* <strong>DRY! (don't repeat yourself).</strong> compare the previous example to the timeref one - the timeref example provides the date only <em>once</em> instead of duplicating it. Whenever multiple del/ins edits occur at the same date/time they can all reference a single <code><time></code> element.

	Opinions / discussion:		Opinions / discussion:

Tantek: dates without times accepted

2010-08-25T01:40:58Z

dates without times accepted

@@ Line 1: / Line 1: @@
 Research, data, use cases, issues, and enhancements related to the [http://www.w3.org/TR/html5/edits.html#the-del-element HTML5 <code>del</code> element].
 == datetime attribute ==
 The <code>del</code> element has a <code>datetime</code> attribute that requires an explicit date and time.
 Summary: the <code>datetime</code> attribute (on both del and ins elements) should permit just a date value, in addition to permitting explicit dates with times.
 ;ISO8601 syntax
 :YYYY-MM-DD
@@ Line 29: / Line 54: @@
 * +1 [[User:Tantek|Tantek Çelik]] - this happens to me often when I have blog-like or other essay content that I update by hand.  Since I typically do updates to any particular content about once a day, day-level granularity is sufficient.  Picking an arbitrary time seems like being forced to provide "fake" metadata which I don't want to do.
 * +1 [[User:EdwardOConnor|EdwardOConnor]] - I have the same sort of experience as Tantek in this case; confabulating precision where none exists feels quite wrong.

TheresaOConnor: added my +1s

2010-08-14T04:02:38Z

added my +1s

← Older revision		Revision as of 04:02, 14 August 2010
Line 28:		Line 28:
	Opinions / discussion:		Opinions / discussion:
	* +1 [[User:Tantek\|Tantek Çelik]] - this happens to me often when I have blog-like or other essay content that I update by hand. Since I typically do updates to any particular content about once a day, day-level granularity is sufficient. Picking an arbitrary time seems like being forced to provide "fake" metadata which I don't want to do.		* +1 [[User:Tantek\|Tantek Çelik]] - this happens to me often when I have blog-like or other essay content that I update by hand. Since I typically do updates to any particular content about once a day, day-level granularity is sufficient. Picking an arbitrary time seems like being forced to provide "fake" metadata which I don't want to do.
	* ...		* +1 [[User:EdwardOConnor\|EdwardOConnor]] - I have the same sort of experience as Tantek in this case; confabulating precision where none exists feels quite wrong.


	=== timeref ===		=== timeref ===
Line 50:		Line 49:
	Opinions / discussion:		Opinions / discussion:
	* +1 [[User:Tantek\|Tantek Çelik]]		* +1 [[User:Tantek\|Tantek Çelik]]
	* ...		* +1 [[User:EdwardOConnor\|EdwardOConnor]] - This would be great for blog post authoring.

Tantek: typos

2010-08-01T09:14:42Z

typos

← Older revision		Revision as of 09:14, 1 August 2010
Line 26:		Line 26:
	</nowiki></pre>		</nowiki></pre>

	Opinions / ~~discusion~~:		Opinions / discussion:
	* +1 [[User:Tantek\|Tantek Çelik]] - this happens to me often when I have blog-like or other essay content that I update by hand. Since I typically do updates to any particular content about once a day, day-level granularity is sufficient. Picking an arbitrary time seems like being forced to provide "fake" metadata which I don't want to do.		* +1 [[User:Tantek\|Tantek Çelik]] - this happens to me often when I have blog-like or other essay content that I update by hand. Since I typically do updates to any particular content about once a day, day-level granularity is sufficient. Picking an arbitrary time seems like being forced to provide "fake" metadata which I don't want to do.
	* ...		* ...
Line 48:		Line 48:
	* <strong>DRY! (don't repeat yourself).</strong> compare the previous example to the timeref one - the timeref example provides the date only <em>once</em> instead of duplicating it. Whenever multiple del/ins edits occur at the same date/time they can all reference a single <code><time&gt</code> element.		* <strong>DRY! (don't repeat yourself).</strong> compare the previous example to the timeref one - the timeref example provides the date only <em>once</em> instead of duplicating it. Whenever multiple del/ins edits occur at the same date/time they can all reference a single <code><time&gt</code> element.

	Opinions / ~~discusion~~:		Opinions / discussion:
	* +1 [[User:Tantek\|Tantek Çelik]]		* +1 [[User:Tantek\|Tantek Çelik]]
	* ...		* ...

Tantek: /* timeref */ a bit more advantage text

2010-07-30T01:17:02Z

timeref: a bit more advantage text

← Older revision		Revision as of 01:17, 30 July 2010
Line 45:		Line 45:

	Advantages:		Advantages:
	* <strong>visible metadata!</strong> the date of the change is shown visibly (as many real world examples do (citations needed), rather than invisibly in a hidden datetime attribute, which encourages higher fidelity metadata.		* <strong>visible metadata!</strong> the date of the change can be shown visibly (as many real world examples do (citations needed), rather than invisibly in a hidden datetime attribute, which encourages higher fidelity metadata.
	* <strong>DRY! (don't repeat yourself).</strong> compare the previous example to the timeref one - the timeref example provides the date only <em>once</em> instead of duplicating it.		* <strong>DRY! (don't repeat yourself).</strong> compare the previous example to the timeref one - the timeref example provides the date only <em>once</em> instead of duplicating it. Whenever multiple del/ins edits occur at the same date/time they can all reference a single <code><time&gt</code> element.

	Opinions / discusion:		Opinions / discusion:
	* +1 [[User:Tantek\|Tantek Çelik]]		* +1 [[User:Tantek\|Tantek Çelik]]
	* ...		* ...

Tantek: /* timeref */ note type idref

2010-07-29T23:50:20Z

timeref: note type idref

← Older revision		Revision as of 23:50, 29 July 2010
Line 32:		Line 32:

	=== timeref ===		=== timeref ===
	Summary: add a new <code>timeref</code> attribute that can be used to reference the <code>id</code> of a local to document <code><time></code> element which is then used as the <code>datetime</code> value of when the deletion or insertion occurred.		Summary: add a new <code>timeref</code> attribute (of type <code>idref</code>) that can be used to reference the <code>id</code> of a local to document <code><time></code> element which is then used as the <code>datetime</code> value of when the deletion or insertion occurred.

	Example:		Example:

Tantek: /* dates without times */ add example, plus add new "timeref" attribute proposal for visible metadata + dry

2010-07-29T22:39:43Z

dates without times: add example, plus add new "timeref" attribute proposal for visible metadata + dry

@@ Line 5: / Line 5: @@
 === dates without times ===
-In short: the <code>datetime</code> attribute (on both del and ins elements) should permit just a date value, in addition to permitting explicit dates with times.
+Summary: the <code>datetime</code> attribute (on both del and ins elements) should permit just a date value, in addition to permitting explicit dates with times.
 ;ISO8601 syntax
 :YYYY-MM-DD
-Currently the <code>datetime</code> attribute requires <em>both</em> a date and time.
+Currently the <code>datetime</code> attribute requires <em>both</em> a date and a time.
 On the other hand, the [[time]] element's datetime attribute allows just a date.
@@ Line 17: / Line 17: @@
 # easier for hand-authoring (per the preferring authors principle of the HTML5 design principles).  Authors can more easily add ins/del elements with explicit datetime attributes if they are permitted to specify only the date (they might not know or care about the precise time), e.g. in blog posts that are updated by the author.
 # avoids artificial precision. Forcing an explicit date and time forces authors to enter artificial precision (e.g. YYYY-MM-DDT00:00:00Z instead of YYYY-MM-DD). Allowing just dates permits authors to convey that a del/ins occurred on a certain day, and that the precise time is unknown or irrelevant.
 Opinions / discusion:
 * +1 [[User:Tantek|Tantek Çelik]]
 * ...

Tantek: drafted

2010-07-29T01:04:09Z

drafted

New page

Research, data, use cases, issues, and enhancements related to the [http://www.w3.org/TR/html5/edits.html#the-del-element HTML5 <code>del</code> element].

== datetime attribute ==
The <code>del</code> element has a <code>datetime</code> attribute that requires an explicit date and time.

=== dates without times ===
In short: the <code>datetime</code> attribute (on both del and ins elements) should permit just a date value, in addition to permitting explicit dates with times.

;ISO8601 syntax
:YYYY-MM-DD

Currently the <code>datetime</code> attribute requires <em>both</em> a date and time.

On the other hand, the [[time]] element's datetime attribute allows just a date.

Allowing just a date has the following advantages:
# easier for hand-authoring (per the preferring authors principle of the HTML5 design principles). Authors can more easily add ins/del elements with explicit datetime attributes if they are permitted to specify only the date (they might not know or care about the precise time), e.g. in blog posts that are updated by the author.
# avoids artificial precision. Forcing an explicit date and time forces authors to enter artificial precision (e.g. YYYY-MM-DDT00:00:00Z instead of YYYY-MM-DD). Allowing just dates permits authors to convey that a del/ins occurred on a certain day, and that the precise time is unknown or irrelevant.

Opinions / discusion:
* +1 [[User:Tantek|Tantek Çelik]]
* ...