[wp-trac] [WordPress Trac] #30783: Support Microformats 2

[WordPress Trac]

#30783: Support Microformats 2
-------------------------+------------------------------
 Reporter:  dshanske     |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Themes       |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:
-------------------------+------------------------------

Comment (by dshanske):

 Replying to [comment:11 pento]:
 > I'm cool with doing this, but I do have some questions, mostly around my
 lack of familiarity with microformats.
 >
 > * How does microformats discovery work? Do we need to put something in
 the header?
 > * Is there a down side to ceasing microformats 1 support?
 > * Can we support microformats 1 and 2 simultaneously?
 >
 > If we can get away without adding yet another theme option, I think that
 would be the vastly more preferable method.

 Microformats don't require a header. We already have microformats 1 in
 WordPress, but the implementation has some issues. The proposed patch has
 both the classic and the newer formatting in it.

 I'd prefer to deprecate the older standard, but we go back to the legacy
 of the original inclusion. Too many things depend on the microformats
 classes as a styling element, which is what necessitated the theme option
 flag.

 Whether we want to go as far as to remove all of the older microformats in
 favor of the new ones if the flag is set is certainly a question. But, a
 lot of plugins and themes style the output of certain fields based on the
 classic microformats classes, therefore it would cause some chaos.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/30783#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform