Page MenuHomePhabricator

Investigate Use of vevent CSS Class
Open, MediumPublic

Description

Background

Several Wikipedia articles (approximately 3 million on English Wikipedia alone) use a CSS class called vevent to display events. Examples of articles that have such an element are:
https://en.wikipedia.org/wiki/2007_Steelback_Grand_Prix
https://en.wikipedia.org/wiki/File:Mes-e6.svg
https://en.wikipedia.org/wiki/File:Bulgaria-Army-OR-5.svg
https://en.wikipedia.org/wiki/List_of_Riverdale_episodes

The hCalendar microdata format allows marking up events with the vevent CSS class. There is a minimum set of expected fields that are supposed to accompany a vevent element.

vevent is intended to allow marking up events in the sense of events that people can attend, such as concerts, shows, and such. Search engines (Google at the very least) use this to render events in a rich result format. However, given that most Wikipedia articles seem to use vevent for past / historical events and that several required fields such as location and dstart aren't provided, Google's Search Console reports millions of errors for incomplete events.

This is not a problem in any sense that it affects users directly. As far as Google's public documentation is concerned, there isn't any declared impact on search ranking. This task can be closed if we can conclude with one of the following:

  • The use of vevent in this way is unintentional. It might be good to remove it (as a very, very low-priority task)
  • The use if vevent in this way is intentional and capture the intention in this task.
  • The use of vevent in this way is intentional but it is not complete, and refer to the task that would make it complete.

Event Timeline

We do know but the answer isn't a good one: There are many templates and modules that add the vevent class and fixing the template on enwiki won't fix the template on say frwiki.

In this particular case the offender is:
https://en.wikipedia.org/wiki/Template:Infobox_American_championship_car_race_report

To fix these problems we have two options

  1. We manually go in and fix those templates.
  2. We provide better tooling to editors to help them fix those templates themselves (See T200880)

What project is this about? Please add a project tag so this task can be found - thanks.

  • The use of vevent in this way is unintentional. It might be good to remove it (as a very, very low-priority task)
  • The use if vevent in this way is intentional and capture the intention in this task.
  • The use of vevent in this way is intentional but it is not complete, and refer to the task that would make it complete.

The use of vevent is intentional. Lacking any 'required' subproperties is not. AFAIK Google is not the entity that produces the relevant specification though of course they are probably one of the few entities that would have the tooling to know what is/not missing. @Pigsonthewing probably knows more and/or can possibly help sort out en.wp at a minimum.

Thank you, Izno.

The use of vevent in this way is intentional and the intention is captured in https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Microformats and pages and templates linked from there.

Errors are caused by editors (unintentionally ?) breaking or removing microformat markup, or by them neglecting to use sub-templates such as (for dtstart, for example) {{Start date}}.

Do we have any linting tools/gadgets we could add to warn editors of invalid markup?

Arlolra triaged this task as Medium priority.Aug 17 2023, 11:09 PM