Refactored concept

ical4j · Jan 22, 2024 · 40fb685 · 40fb685
1 parent 9e25063
commit 40fb685
Show file tree

Hide file tree

Showing 4 changed files with 11 additions and 8 deletions.
diff --git a/docs/extensions/concept/availability.md b/docs/extensions/concept/availability.md
@@ -1 +1,10 @@
 # iCal4j Extensions - Concept: Availability
+
+
+### Subscription
+
+* Subscription - a recurring transparent event representing an active subscription to a resource
+
+### Invitation
+
+* Invitation - a transparent event representing eligibility to participate in an activity
diff --git a/docs/extensions/concept/event.md b/docs/extensions/concept/event.md
@@ -22,11 +22,3 @@ cases. Some of these are represented by the following concepts:
 ### Performance
 
 * Performance - a public event with one or more performers and no active participation of attendees
-
-### Subscription
-
-* Subscription - a recurring transparent event representing an active subscription to a resource
-
-### Invitation
-
-* Invitation - a transparent event representing eligibility to participate in an activity
diff --git a/docs/extensions/concept/index.md b/docs/extensions/concept/index.md
@@ -11,6 +11,7 @@ use-cases for iCalendar objects.
 These concepts include:
 
 * [Event](event.md) - an opaque `VEVENT` object that may support recurrences.
+* [Observance](observance.md) - a transparent `VEVENT` object that may support recurrences.
 * [Action](action.md) - a `VTODO` object that is assignable to individuals for resolution. Supports recurrences.
 * [Issue](issue.md) - a `VTODO` object capturing a one-off impediment to other activities or actors. Does not support recurrences.
 * [Request](request.md) - a `VTODO` object representing a service request, often fulfilled via an [Action](action.md). May support recurrences.

diff --git a/docs/extensions/concept/observance.md b/docs/extensions/concept/observance.md
@@ -0,0 +1 @@
+# iCal4j Extensions - Concept: Observance