Difference between revisions of "User:Tantekelik/drop pubdate"

From W3C Wiki
Jump to: navigation, search
(postpone even discussing moddate til after HTML5)
(Other Proposals: reword rebuttal summaries to better communicate the rebuttals, add more to why we don't need a moddate attr either)
Line 40: Line 40:
 
Rebuttals to other proposals:
 
Rebuttals to other proposals:
 
* [http://www.w3.org/html/wg/wiki/User:Idevlin/keep_pubdate_change_proposal keep pubdate change proposal]
 
* [http://www.w3.org/html/wg/wiki/User:Idevlin/keep_pubdate_change_proposal keep pubdate change proposal]
** claim of '''pubdate attribute is already in widespread use''' - no citations provided, and prose mentions (e.g. Wordpress 'Twenty Eleven' theme) already use hAtom and therefore have no need for 'pubdate' (i.e. such examples fail to justify keeping pubdate because the far more [http://microformats.org/wiki/hatom-examples-in-wild well-established and widespread hAtom] markup already handles the functionality). Bottom line: no evidence for "widespread" 'pubdate' and no evidence for non-trivial use of 'pubdate' *by itself*.
+
** '''exaggerated claim of pubdate attribute is already in widespread use''' - no citations provided, and prose mentions (e.g. Wordpress 'Twenty Eleven' theme) already use hAtom and therefore have no need for 'pubdate' (i.e. such examples fail to justify keeping pubdate because the far more [http://microformats.org/wiki/hatom-examples-in-wild well-established and widespread hAtom] markup already handles the functionality). Bottom line: no evidence for "widespread" 'pubdate' and no evidence for non-trivial use of 'pubdate' *by itself*.
** '''new <code>moddate</code> attribute''' - this is a new feature and even discussion of which at this point should be postponed to after HTML5.
+
** '''postpone new <code>moddate</code> attribute''' - the proposed moddate attribute is a new feature and even discussion of which at this point should be postponed to after HTML5. However, even then it is also unnecessary for the same reasons that pubdate is unnecessary: hAtom has an "updated" property that is already in use by those who wish to publish that kind of information.
  
 
== References ==
 
== References ==

Revision as of 18:07, 17 May 2012


drop pubdate attribute change proposal

Summary

Drop the pubdate attribute and associated interface(s) from the HTML5 time element.

Dropping the pubdate attribute was discussed in the HTML Working Group on 2011-11-03, and there was a rough consensus in support of dropping it.

This is a change proposal to address:

Rationale

The pubdate attribute is a vestigial piece of markup left-over from the attempt to provide automatic HTML5 to Atom conversion, and in practice is either not used, or typically used in conjunction with the hAtom microformat which supersets its functionality.

Details

  • drop 'pubdate' attribute from the definition of the <time> element
  • drop DOM attribute 'pubDate' from the definition of the <time> element

Impact

Positive Effects

Negative Effects

Conformance Classes

As defined by the editor.

Risks

  • None.

Other Proposals

Rebuttals to other proposals:

  • keep pubdate change proposal
    • exaggerated claim of pubdate attribute is already in widespread use - no citations provided, and prose mentions (e.g. Wordpress 'Twenty Eleven' theme) already use hAtom and therefore have no need for 'pubdate' (i.e. such examples fail to justify keeping pubdate because the far more well-established and widespread hAtom markup already handles the functionality). Bottom line: no evidence for "widespread" 'pubdate' and no evidence for non-trivial use of 'pubdate' *by itself*.
    • postpone new moddate attribute - the proposed moddate attribute is a new feature and even discussion of which at this point should be postponed to after HTML5. However, even then it is also unnecessary for the same reasons that pubdate is unnecessary: hAtom has an "updated" property that is already in use by those who wish to publish that kind of information.

References

References are inline.