last-modified-brainstorming - Revision history

Tantek: link overview, hAtom

2011-02-04T19:11:43Z

link overview, hAtom

← Older revision		Revision as of 19:11, 4 February 2011
Line 1:		Line 1:
	= "Last-modified" Brainstorming =		= "Last-modified" Brainstorming =
			Towards the development of a [[last-modified]] microformat.

	== Purpose ==		== Purpose ==
Line 84:		Line 85:
	== Related ==		== Related ==
	* ←[[last-modified-formats]]		* ←[[last-modified-formats]]
			* [[hAtom]]
	* [[datetime-design-pattern]]		* [[datetime-design-pattern]]

Brian: Reverted edits by CotamOntac (Talk) to last version by Eron Wright

2008-12-20T22:21:46Z

Reverted edits by CotamOntac (Talk) to last version by Eron Wright

← Older revision		Revision as of 22:21, 20 December 2008
Line 1:		Line 1:
	~~rololota~~
	= "Last-modified" Brainstorming =		= "Last-modified" Brainstorming =

Line 16:		Line 15:
	=== Class name considerations ===		=== Class name considerations ===
	==== Class names for the date of publication ====		==== Class names for the date of publication ====
	* ~~âdateâ~~: Dublin Core		* “date”: Dublin Core
	* ~~âpublishedâ~~: Atom		* “published”: Atom
	* ~~âdtpublishedâ~~: As suggested by Paul Bryson for [[hatom\|hAtom]]. See http://microformats.org/discuss/mail/microformats-discuss/2005-December/002520.html		* “dtpublished”: As suggested by Paul Bryson for [[hatom\|hAtom]]. See http://microformats.org/discuss/mail/microformats-discuss/2005-December/002520.html

	==== Class names for the date of the last modification ====		==== Class names for the date of the last modification ====
	* ~~âlast~~-~~modifiedâ~~: ~~âLast~~-~~Modifiedâ~~ used by HTTP 1.0 and 1.1, hCalendar		* “last-modified”: “Last-Modified” used by HTTP 1.0 and 1.1, hCalendar
	* ~~âmodifiedâ~~: Dublin Core		* “modified”: Dublin Core
	* ~~âupdatedâ~~: Atom 1.0 syndication specification		* “updated”: Atom 1.0 syndication specification

	=== Different class name for page specific and item specific dates? ===		=== Different class name for page specific and item specific dates? ===

	For example ~~âpage~~-last-~~modifiedâ~~ is used to indicate the last modification date of a page and ~~âlast~~-~~modifiedâ~~ for the last modification date of a specific item*.		For example “page-last-modified” is used to indicate the last modification date of a page and “last-modified” for the last modification date of a specific item*.
	However, this seems to be not a good idea. Other microformats leave it to the parser to pick the scope of the element, e.g. [[rel-tag]].		However, this seems to be not a good idea. Other microformats leave it to the parser to pick the scope of the element, e.g. [[rel-tag]].

	See http://microformats.org/discuss/mail/microformats-discuss/2005-August/000726.html for a related discussion.		See http://microformats.org/discuss/mail/microformats-discuss/2005-August/000726.html for a related discussion.

	<nowiki>*</nowiki> This specific item is marked-up with a microformat, e.g: a microformat to describe blog posts may use ~~âlast~~-~~modifiedâ~~ to indicate when a blog post was last modified.		<nowiki>*</nowiki> This specific item is marked-up with a microformat, e.g: a microformat to describe blog posts may use “last-modified” to indicate when a blog post was last modified.

	== Possible date formats ==		== Possible date formats ==

CotamOntac: dronerdomget

2008-12-20T04:54:04Z

dronerdomget

← Older revision		Revision as of 04:54, 20 December 2008
Line 1:		Line 1:
			rololota
	= "Last-modified" Brainstorming =		= "Last-modified" Brainstorming =

Line 15:		Line 16:
	=== Class name considerations ===		=== Class name considerations ===
	==== Class names for the date of publication ====		==== Class names for the date of publication ====
	* ~~“date”~~: Dublin Core		* âdateâ: Dublin Core
	* ~~“published”~~: Atom		* âpublishedâ: Atom
	* ~~“dtpublished”~~: As suggested by Paul Bryson for [[hatom\|hAtom]]. See http://microformats.org/discuss/mail/microformats-discuss/2005-December/002520.html		* âdtpublishedâ: As suggested by Paul Bryson for [[hatom\|hAtom]]. See http://microformats.org/discuss/mail/microformats-discuss/2005-December/002520.html

	==== Class names for the date of the last modification ====		==== Class names for the date of the last modification ====
	* ~~“last~~-~~modified”~~: ~~“Last~~-~~Modified”~~ used by HTTP 1.0 and 1.1, hCalendar		* âlast-modifiedâ: âLast-Modifiedâ used by HTTP 1.0 and 1.1, hCalendar
	* ~~“modified”~~: Dublin Core		* âmodifiedâ: Dublin Core
	* ~~“updated”~~: Atom 1.0 syndication specification		* âupdatedâ: Atom 1.0 syndication specification

	=== Different class name for page specific and item specific dates? ===		=== Different class name for page specific and item specific dates? ===

	For example ~~“page~~-last-~~modified”~~ is used to indicate the last modification date of a page and ~~“last~~-~~modified”~~ for the last modification date of a specific item*.		For example âpage-last-modifiedâ is used to indicate the last modification date of a page and âlast-modifiedâ for the last modification date of a specific item*.
	However, this seems to be not a good idea. Other microformats leave it to the parser to pick the scope of the element, e.g. [[rel-tag]].		However, this seems to be not a good idea. Other microformats leave it to the parser to pick the scope of the element, e.g. [[rel-tag]].

	See http://microformats.org/discuss/mail/microformats-discuss/2005-August/000726.html for a related discussion.		See http://microformats.org/discuss/mail/microformats-discuss/2005-August/000726.html for a related discussion.

	<nowiki>*</nowiki> This specific item is marked-up with a microformat, e.g: a microformat to describe blog posts may use ~~“last~~-~~modified”~~ to indicate when a blog post was last modified.		<nowiki>*</nowiki> This specific item is marked-up with a microformat, e.g: a microformat to describe blog posts may use âlast-modifiedâ to indicate when a blog post was last modified.

	== Possible date formats ==		== Possible date formats ==

Eron Wright at 19:43, 13 February 2006

2006-02-13T19:43:45Z

← Older revision		Revision as of 19:43, 13 February 2006
Line 36:		Line 36:

	See [[datetime-design-pattern]].		See [[datetime-design-pattern]].

			== Issues ==
			* 2006-02-13 raised by [http://microformats.org/wiki/User:Eron_Wright Eron Wright]
			*# ''Last-modified dates are unsuitable as version numbers. As the HTTP 1.1 spec mentions, dates lack fidelity and are difficult to generate for dynamic content. A better solution is to use an opaque string, as HTTP does with the ETag header. Indeed, If-Modified-Since is deprecated.''

	<!-- -->		<!-- -->

BenjaminCarlyle: last-modified is used by hCalendar

2006-01-09T07:00:32Z

last-modified is used by hCalendar

← Older revision		Revision as of 07:00, 9 January 2006
Line 20:		Line 20:

	==== Class names for the date of the last modification ====		==== Class names for the date of the last modification ====
	* “last-modified”: “Last-Modified” used by HTTP 1.0 and 1.1		* “last-modified”: “Last-Modified” used by HTTP 1.0 and 1.1, hCalendar
	* “modified”: Dublin Core		* “modified”: Dublin Core
	* “updated”: Atom 1.0 syndication specification		* “updated”: Atom 1.0 syndication specification

RyanKing at 02:10, 4 January 2006

2006-01-04T02:10:00Z

← Older revision		Revision as of 02:10, 4 January 2006
Line 6:		Line 6:
	== Authors ==		== Authors ==
	* [[User:RobertBachmann\|Robert Bachmann]]		* [[User:RobertBachmann\|Robert Bachmann]]
			* [[User:RyanKing\|Ryan King]]

			== Semantics ==
			Since both Atom and HTTP define the last-modified date (or its equivalent) as a "user-defined" value, this microformat should have the same semantics. In other words, the value should represent the last instance that the resource was changed in a way deemed significant to the publisher/author, which is not neccessarily the same as a file-system modified date-time. --RyanKing

	== Possible class names ==		== Possible class names ==

ChrisHibbert: /* Purpose */

2005-12-30T18:29:28Z

Purpose

← Older revision		Revision as of 18:29, 30 December 2005
Line 39:		Line 39:
	== Purpose ==		== Purpose ==

	Many web pages (and parts thereof) state ~~there~~ publication and/or modification date in a human readable way. This proposed microformat specifies how this can be done in a fashion that is both human- and machine-readable.		Many web pages (and parts thereof) state their publication and/or modification date in a human readable way. This proposed microformat specifies how this can be done in a fashion that is both human- and machine-readable.

	=== Specifying the date of publication ===		=== Specifying the date of publication ===

RobertBachmann: /* Specifying the date of modification */ fixed a mistake

2005-12-30T11:18:26Z

Specifying the date of modification: fixed a mistake

← Older revision		Revision as of 11:18, 30 December 2005
Line 51:		Line 51:
	The date of modification is enclosed by <code><abbr class="date-modified<sup>[[#footnote1\|1]]</sup>" title="''Date in ISO format''">''Date in arbitary format''</abbr></code>, e.g:		The date of modification is enclosed by <code><abbr class="date-modified<sup>[[#footnote1\|1]]</sup>" title="''Date in ISO format''">''Date in arbitary format''</abbr></code>, e.g:

	<code><p>Last modified on <abbr class="date-~~published~~<sup>[[#footnote1\|1]]</sup>" title="2005-12-29T14:39:12+0100">Thursday, December 29, 2005 02:39:12 a.m.</abbr>.</p></code>.		<code><p>Last modified on <abbr class="date-modified<sup>[[#footnote1\|1]]</sup>" title="2005-12-29T14:39:12+0100">Thursday, December 29, 2005 02:39:12 a.m.</abbr>.</p></code>.

	If no date of modification is present the parsers MAY use the date of publication as the date of the last modification.		If no date of modification is present the parsers MAY use the date of publication as the date of the last modification.

RobertBachmann: /* Possible date formats */ Added fragment link

2005-12-30T00:31:12Z

Possible date formats: Added fragment link

← Older revision		Revision as of 00:31, 30 December 2005
Line 34:		Line 34:

	<!-- -->		<!-- -->
			<span id="proposal"> </span>

	= Proposal (2nd, strawman) =		= Proposal (2nd, strawman) =

RobertBachmann: /* and */ typo

2005-12-30T00:23:26Z

<del> and <ins>: typo

← Older revision		Revision as of 00:23, 30 December 2005
Line 59:		Line 59:
	<code><del class="date-modified<sup>[[#footnote1\|1]]</sup>" datetime="2005-12-29T14:39:12+0100">wrong words</del></code>.		<code><del class="date-modified<sup>[[#footnote1\|1]]</sup>" datetime="2005-12-29T14:39:12+0100">wrong words</del></code>.
	The class value "date-modified<sup>[[#footnote1\|1]]</sup>" is implied for every <code><del></code> and <code><ins></code>		The class value "date-modified<sup>[[#footnote1\|1]]</sup>" is implied for every <code><del></code> and <code><ins></code>
	element which has an datetime attribute.		element which has a <code>datetime</code> attribute.

	=== Multiple dates in a page (or a part thereof) ===		=== Multiple dates in a page (or a part thereof) ===