-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
632f720
commit 6cb920c
Showing
15 changed files
with
156 additions
and
170 deletions.
There are no files selected for viewing
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
# iCal4j Template - Groupware: Action | ||
|
||
Follow-up actions are a common output of meetings. Action instances may be associated with individual meetings or | ||
where available, the associated Agenda. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,47 @@ | ||
# iCal4j Template - Groupware: Agenda | ||
|
||
An Agenda represents one or more objectives for a meeting, or series of meetings. Sometimes a meeting may not | ||
address all the items on an agenda due to lack of time, etc., so it is useful to maintain the Agenda separately | ||
such that it may be shared across multiple meetings if required. | ||
|
||
### Examples | ||
|
||
Multiple Agenda may be linked in sequence to track items individually. This can be useful where time constraints | ||
require additional meetings to address outstanding Agenda items: | ||
|
||
VToDo item4 = new Agenda().summary("Further business and close").uid(...).apply(); | ||
VToDo item3 = new Agenda().summary("Standing items").uid(...).nextItem(item4).apply(); | ||
VToDo item2 = new Agenda().summary("Business arising").uid(...).nextItem(item3).apply(); | ||
VToDo item1 = new Agenda().summary("ACME Monthly Board Meeting").uid(...).nextItem(item2).apply(); | ||
|
||
ComponentList agenda = new ComponentList(Arrays.asList(item1, item2, item3, item4); | ||
|
||
The resulting component list looks like this: | ||
|
||
BEGIN:VTODO | ||
DTSTAMP:20231113T000000Z | ||
CONCEPT:https://ical4j.org/action-types/ACTION | ||
SUMMARY:ACME Monthly Board Meeting | ||
UID:1 | ||
LINK;VALUE=UID;LINKREL=next:2 | ||
END:VTODO | ||
BEGIN:VTODO | ||
DTSTAMP:20231113T000000Z | ||
CONCEPT:https://ical4j.org/action-types/ACTION | ||
SUMMARY:Business arising | ||
UID:2 | ||
LINK;VALUE=UID;LINKREL=next:3 | ||
END:VTODO | ||
BEGIN:VTODO | ||
DTSTAMP:20231113T000000Z | ||
CONCEPT:https://ical4j.org/action-types/ACTION | ||
SUMMARY:Standing items | ||
UID:3 | ||
LINK;VALUE=UID;LINKREL=next:4 | ||
END:VTODO | ||
BEGIN:VTODO | ||
DTSTAMP:20231113T000000Z | ||
CONCEPT:https://ical4j.org/action-types/ACTION | ||
SUMMARY:Further business and close | ||
UID:4 | ||
END:VTODO |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
# iCal4j Template - Groupware: Appointment | ||
|
||
An Appointment is similar to a Meeting but is more of an open invitation to recipients. It is used to publish | ||
events to either a broad or narrow audience, and specifically doesn't cater for RSVPs or Attendance tracking. | ||
An Appointment may still have an associated Agenda for planning, but typically wouldn't include follow-up Actions. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
# iCal4j Template - Groupware: Attendance | ||
|
||
A useful metric to track for meetings and other events is actual attendance. Whilst opaque events provide an | ||
intention to attend, Attendance can provide a record of actual participation after the event. | ||
|
||
### Examples | ||
|
||
For each participant in a meeting attendance may be recorded as follows: | ||
|
||
VEvent meeting = ... | ||
VCard attendee = ... | ||
VJournal attendance = new Attendance().participant(new Contact(attendee)) | ||
.start(LocalDateTime.of(2023, 11, 15, 9, 0)) | ||
.end(LocalDateTime.of(2023, 11, 15, 9, 30)) | ||
.context(meeting) | ||
.apply(); | ||
|
||
The attendance record looks something like this: | ||
|
||
BEGIN:VJOURNAL | ||
DTSTAMP:20231115T000000Z | ||
DTSTART:20231115T090000 | ||
DTEND:20231115T093000 | ||
RELATED-TO:9000 | ||
BEGIN:PARTICIPANT | ||
PARTICIPANT-TYPE:CONTACT | ||
UID:1234 | ||
CALENDAR-ADDRESS:mailto:[email protected] | ||
STRUCTURED-DATA;VALUE=BINARY;ENCODING=BASE64;FMTTYPE=text/vcard:QkVHSU46VkNBUkQNClVJRDoxMjM0DQpGTjpBdHRlbmRlZQ0KQ0FMQURSVVJJOm1haWx0bzphdHRlbmRlZUBleGFtcGxlLmNvbQ0KRU5EOlZDQVJEDQo= | ||
END:PARTICIPANT | ||
END:VJOURNAL |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
# iCal4j Template - Groupware | ||
|
||
Groupware is a term used to describe software tools used for communication and collaboration within and across teams. | ||
The most widely adopted use of the iCalendar and vCard standards are in Groupware applications, where almost every | ||
calendar implementation supports the iCalendar format. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
# iCal4j Template - Groupware: Meeting | ||
|
||
Perhaps the most common use of iCalendar is to define and share meeting invites. A Meeting is a closed invitation to | ||
select recipients in order for collaborative discussion or other activities. This template may be used to create | ||
or modify `VEVENT` objects to conform with conventional approaches to defining meeting invites. | ||
|
||
### Examples | ||
|
||
Assuming we use vCard to represent meeting participants, we can construct a new meeting: | ||
|
||
VCard organizer = ... | ||
VCard chair = ... | ||
|
||
VEvent meeting = new Meeting().organizer(organizer) | ||
.chair(new Contact(chair)) | ||
.start(LocalDate.of(2023, 11, 13).atStartOfDay()) | ||
.duration(Duration.ofMinutes(30)).apply(); | ||
|
||
The result is something like this: | ||
|
||
BEGIN:VEVENT | ||
DTSTAMP:20231113T000000Z | ||
ORGANIZER;CN=Big Boss:mailto:[email protected] | ||
DTSTART:20231113T000000 | ||
DURATION:PT30M | ||
CONCEPT:https://ical4j.org/event-types/MEETING | ||
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=CHAIR:mailto:[email protected] | ||
BEGIN:PARTICIPANT | ||
PARTICIPANT-TYPE:CONTACT | ||
UID:1234 | ||
CALENDAR-ADDRESS:mailto:[email protected] | ||
STRUCTURED-DATA;VALUE=BINARY;ENCODING=BASE64;FMTTYPE=text/vcard:QkVHSU46VkNBUkQNClVJRDoxMjM0DQpGTjpUZWFtIExlYWQNCkNBTEFEUlVSSTptYWlsdG86bGVhZC1ieUBleGFtcGxlLmNvbQ0KRU5EOlZDQVJEDQo= | ||
END:PARTICIPANT | ||
END:VEVENT |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
# iCal4j Template - Groupware: Note | ||
|
||
A Note is used to capture useful information such as outcomes of discussions, talking points and anything else | ||
not specifically actionable. Notes may be associated with Meetings or Agenda, and can also exist independently. |
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters