You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+11-1Lines changed: 11 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,14 +25,24 @@ You can leverage this library in your automation framework to process circuit ma
25
25
-**account**: identifies an account associated with the service that is the subject of the maintenance notification.
26
26
-**maintenance_id**: contains text that uniquely identifies the maintenance that is the subject of the notification.
27
27
-**circuits**: list of circuits affected by the maintenance notification and their specific impact.
28
-
-**status**: defines the overall status or confirmation for the maintenance.
29
28
-**start**: timestamp that defines the start date of the maintenance in GMT.
30
29
-**end**: timestamp that defines the end date of the maintenance in GMT.
31
30
-**stamp**: timestamp that defines the update date of the maintenance in GMT.
32
31
-**organizer**: defines the contact information included in the original notification.
33
32
33
+
and may additionally contain the following attributes:
34
+
35
+
-**status**: defines the overall status or confirmation for the maintenance.¹
36
+
-**sequence**: a sequence number for notifications involving this maintenance window. In practice this is generally redundant with the **stamp** field, and will be defaulted to `1` for most non-iCal parsed notifications.²
37
+
-**summary**: human-readable details about this maintenance notification.
38
+
-**uid**: a unique (?) identifer for a thread of related notifications. In practice this is generally redundant with the **maintenance_id** field, and will be defaulted to `0` for most non-iCal parsed notifications.
39
+
34
40
> Please, refer to the [BCOP](https://github.com/jda/maintnote-std/blob/master/standard.md) to more details about these attributes.
35
41
42
+
¹ Per the BCOP, **status** (`X-MAINTNOTE_STATUS`) is an optional field in notifications. However, a `Maintenance` object will always contain a `status` value; in the case where the source notification omits this field, the `status` will be set to `"NO-CHANGE"`, and it's up to the consumer of this library to determine how to appropriately handle this case.
43
+
44
+
² Per the BCOP, **sequence** is a mandatory field in notifications. However, some NSPs have been seen to send notifications which, while otherwise consistent with the BCOP, omit the `SEQUENCE` field; in such cases, this library will report a sequence number of `-1`.
45
+
36
46
## Workflow
37
47
38
48
1. We instantiate a `Provider`, directly or via the `init_provider` method, that depending on the selected type will return the corresponding instance.
0 commit comments