Support for event metadata on event websites

Updated Example

Here is the most recent example of event metadata that I think we should recommend conference organizers to include on their conference website.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ConferenceEvent",
  "name": "EuroPython 2025",
  "url": "https://ep2025.europython.eu",
  "startDate": "2025-07-14",
  "endDate": "2025-07-20",
  "location": {
    "@type": "PostalAddress",
    "name": "The Prague Congress Centre",
    "addressCountry": "CZ"
  },
  "hasParticipationOffer": {
     "@type": "Offer",
     "name": "Call for Proposals",
     "url": "https://ep2025.europython.eu/cfp/",
     "availabilityEnds": "2025-02-03"
  },
  "hasSponsorshipOffer":  {
    "@type": "Offer",
    "name": "Sponsor Packages",
    "url": "https://ep2025.europython.eu/sponsorship/sponsor/"
   }
}
</script>

https://github.com/schemaorg/schemaorg/pull/4506/files

Original Proposal

It would be great if there were a standardized way for an event website to provide machine-readable information about itself.

• Option 1: Use HTML meta tags on the event homepage
• Option 2: Use a JSON file such as https://us.pycon.org/2025/event.json

Is there a way that we could encourage event organizers to use one of the two options below?

Is there any other metadata that we should ask organizers to include?

@Mariatta @jonafato @chrisjrn

Option 1: Use HTML meta tags on the event homepage

<meta name="event-name" content="PyCon US">
<meta name="event-start-date" content="2025-05-14">
<meta name="event-end-date" content="2025-05-22">
<meta name="event-location" content="Pittsburgh, Pennsylvania, United States of America">
<meta name="event-country" content="USA">
<meta name="event-venue" content="David L. Lawrence Convention Center">
<meta name="event-proposal-deadline" content="2024-12-19">
<meta name="event-proposal-uri" content="https://us.pycon.org/2025/speaking/guidelines/">
<meta name="event-sponsorship-uri" content="https://us.pycon.org/2025/sponsorship/why-sponsor/">

Option 2: Use a JSON file such as https://us.pycon.org/2025/event.json

{
  "event-name": "PyCon US",
  "event-start-date": "2025-05-14",
  "event-end-date": "2025-05-22",
  "event-location": "Pittsburgh, Pennsylvania, United States of America",
  "event-country": "USA",
  "event-venue": "David L. Lawrence Convention Center",
  "event-proposal-deadline": "2024-12-19",
  "event-proposal-uri": "https://us.pycon.org/2025/speaking/guidelines/",
  "event-sponsorship-uri": "https://us.pycon.org/2025/sponsorship/why-sponsor/",  
}

Start by reviewing the updated JSON-LD example, the original HTML meta-tag and JSON-file proposals, and schema.org PR 4506. No project file or test is named, so clarify with maintainers which metadata format and fields should be supported and what documentation or project behavior would count as done.