iCalendar_parser 0.1.1

iCalendar file parser
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58

## Field Description

### `BEGIN:VCALENDAR` / `END:VCALENDAR`
- **Description**: These lines enclose the entire iCalendar document. They define the start and end of the calendar content.

### `VERSION`
- **Description**: Specifies the iCalendar version being used. In this case, it's version `2.0`.
- **Example**: `VERSION:2.0`

### `PRODID`
- **Description**: Identifies the product or software that generated the iCalendar file. The value `-//hacksw/handcal//NONSGML v1.0//EN` is typically used as a placeholder for this example, representing a non-standard or generic product ID.
- **Example**: `PRODID:-//hacksw/handcal//NONSGML v1.0//EN`

---

## Event Fields

### `BEGIN:VEVENT` / `END:VEVENT`
- **Description**: These lines enclose an individual event within the calendar. They mark the start and end of the event.

### `UID`
- **Description**: A globally unique identifier for the event. It ensures that this event is uniquely identifiable across different systems.
- **Example**: `UID:a.trokhymchuk@gmail.com`

### `ORGANIZER`
- **Description**: Identifies the person or entity organizing the event. The format includes the name of the organizer (`CN=Artem Trokhymchuk`) and the email address (`MAILTO:a.trokhymchuk@gmail.com`).
- **Example**: `ORGANIZER;CN=John Doe:MAILTO:john.doe@example.com`

### `DTSTART`
- **Description**: The start date and time of the event, given in UTC. The format is `YYYYMMDDTHHMMSSZ`.
- **Example**: `DTSTART:19970714T170000Z` (July 14, 1997, 17:00 UTC)

### `DTEND`
- **Description**: The end date and time of the event, also given in UTC.
- **Example**: `DTEND:19970715T040000Z` (July 15, 1997, 04:00 UTC)

### `SUMMARY`
- **Description**: A short description or title of the event.
- **Example**: `SUMMARY:NaUKMA birthday`

### `GEO`
- **Description**: The geographical coordinates of the event's location. In this case, it represents the latitude and longitude of the event’s location.
- **Example**: `GEO:48.85299,2.36885` (Coordinates for a location in Paris, France)

---

## Summary
These are the core fields present in the provided iCalendar file. The required fields include:
- `BEGIN:VCALENDAR` / `END:VCALENDAR`
- `VERSION`
- `PRODID`
- `BEGIN:VEVENT` / `END:VEVENT`
- `UID`
- `ORGANIZER`
- `DTSTART`
- `DTEND`
- `SUMMARY`
- `GEO`