Page Comparison

...

<?​xml version=​"1.0"​ encoding=​"UTF-8"​?>
<​rss​​xmlns:atom​=​"http://www.w3.org/2005/Atom"xmlns:content​=​"http://purl.org/rss/1.0/modules/content/"​​version​=​"2.0"​>
  <​channel​>
    <​title​>Test Feed</​title​>
    <​link​>http://example.com/test.atom</​link​>
    <​description​>feed description</​description​>
    <​atom:link​​href​=​"http://example.com/test.atom"​​rel​=​"self"​ />
    <​lastBuildDate​>Tue, 16 Apr 2019 14:45:15 +0000</​lastBuildDate​>
    <​item​>
      <​title​>Title</​title​>
      <​description​>Description</​description​>
      <​guid​>65c96b7f-a410-4494-b840-d5b82a5d2907</​guid​>
      <​pubDate​>Tue, 16 Apr 2019 10:45:15 +0000</​pubDate​>
      <​endDate​>Tue, 16 Apr 2019 11:45:15 +0000</​endDate​>
      <image>
         <url>https://www.w3schools.com/images/logo.gif</url>
      </image>
    </​item​>
    ... 
  </​channel​>
</​rss​>

...

• <title> string

• <description> string

• <guid> string | number. Can be replaced by <id>

• <pubDate> datetime. Can be replaced by <start_date>, <startDate>, <start>, <startdate>, <pubdate>, <published>

• <endDate> datetime (optional)

• <image>

If more than one of the <pubDate> tags is present, we use the first and ignore the others.

If no <endDate> is provided, the default value is 3 hours from <pubDate>.

Image is set in this priority:

1. If there is a url in the <image>, we set that as the Event image.

2. If not, we look for <enclosure url="http://example.com/file.jpg" length="123456789" type="jpg" />

3. If not, we look for any paths for images (in an <a> or <img> tag) within the description field, and set the first one we find as the Event image

4. If not, we apply our own default image logic to match on the most appropriate icon (based on keyword analysis of title/description, or date, or generic fall-back)

Note: Please make sure that the GUID key is unique for each event. The GUID key is a combination of the event host, feed URL, and GUID.

...

BEGIN:VCALENDAR
VERSION:2.0
CALSCALE:GREGORIAN
BEGIN:VEVENT
DTSTART:20180128T003000Z
DURATION:PT3H
SUMMARY:Summary
DESCRIPTION:Description
UID:id
IMAGE;VALUE=URI;DISPLAY=BADGE;FMTTYPE=image/png:http://example.com/images/party.png
END:VEVENT
...

We strongly recommend following the RFC 2445 specification to format the feed.

...

• <DTSTART> Datetime

• <SUMMARY> String

• <DESCRIPTION> String (Optional)

• <UID> String | Number. Can be replaced by <URL>​

• <DTEND> Datetime (Optional)

• <DURATION> (Optional)

• <LOCATION> String (Optional)

• <RRULE> RRULE (Optional)

• <IMAGE> See: https://icalendar.org/New-Properties-for-iCalendar-RFC-7986/5-10-image-property.html