h-entry-issues

(Difference between revisions)

Jump to: navigation, search
(see github issues for this spec)
Current revision (11:47, 5 August 2016) (view source)
(move past resolved issues from feedback page to here)
 
Line 1: Line 1:
-
For [[h-entry]] issues, see:
+
For current and filing new [[h-entry]] issues, see:
* https://github.com/microformats/h-entry/issues
* https://github.com/microformats/h-entry/issues
 +
 +
== Resolved Issues ==
 +
Past resolved issues:
 +
* 2012-245 Resolved. See [http://krijnhoetmer.nl/irc-logs/microformats/20120830#l-120 2012-243 IRC discussion/consensus] for:
 +
** Use '''<code>p-summary</code> instead of <code>p-entry-summary</code>'''. The historical semantic of "entry-summary" is not different from "summary" in any significant (or discernible way). Collapsing the two will simplify the overall microformats2 vocabularies further. In microformats2, entry-summary is no more.
 +
** Use '''<code>e-content</code> instead of <code>e-entry-content</code>'''. Same point and advantage. In microformats2, entry-content is no more.
 +
** '''drop <code>p-entry-title</code>'''. Unnecessary and subsumed by "p-name". Would consider move to backward compat only if cases are presented - known publishing uses are expected to be updated shortly.
 +
 +
== See Also ==
 +
* [[h-entry]]
 +
* [[microformats2]]
 +
* [[microformats2-parsing]]

Current revision

For current and filing new h-entry issues, see:

Resolved Issues

Past resolved issues:

See Also

h-entry-issues was last modified: Friday, August 5th, 2016

Views