Browse Prior Art Database

Method for Recipient-Preferred Format of Meeting Notices

IP.com Disclosure Number: IPCOM000110943D
Original Publication Date: 1994-Jan-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 66K

Publishing Venue

IBM

Related People

Johnson, WJ: AUTHOR [+2]

Abstract

The originators of meeting notices do not use a standard protocol for the meeting notices. When the recipients of these meeting notices post multiple notices on their calendars, the format of these various calendar events often varies considerably. This causes problems in visually discerning various types of calendar events from other events when the user scans the calendar. For example, it would be very helpful if all the meeting notices on a particular calendar were displayed in the same format. Users need a method of standardizing calendar event format on their own calendars, according to the type of event.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Method for Recipient-Preferred Format of Meeting Notices

      The originators of meeting notices do not use a standard
protocol for the meeting notices.  When the recipients of these
meeting notices post multiple notices on their calendars, the format
of these various calendar events often varies considerably.  This
causes problems in visually discerning various types of calendar
events from other events when the user scans the calendar.  For
example, it would be very helpful if all the meeting notices on a
particular calendar were displayed in the same format.  Users need a
method of standardizing calendar event format on their own calendars,
according to the type of event.

      This system allows the user to specify formatting criteria for
various types of calendar events, and it standardizes each event to
conform to the user's criteria before the event is posted.  The user
builds a Calendar Posting (CP) profile reflecting the desired format
for calendar events.  For example, suppose the CP profile contained
these entries:

  Meeting Notices:

    Meeting = "Department Meeting"  ==>  prefix = "G: "

    Meeting = "Design Review"       ==>  prefix = "I: "

    Attendees                       ==>  format = "fn ln"

      When any Department Meeting is posted to the calendar, the
system checks the CP profile before posting, and automatically
precedes "Department Meeting" with "G:" (for General meeting).
Likewise, the system precedes any "Design Review" with "I:" (for
Inspection).  Also, if any names listed as attendees are not in the
format of first name / last name (such as first initial / middle
initial / last name), then the system automatically performs an
address book search in order to post the names as first name / last
name.

For example, suppose a user sends the following meeting notice:

  March 3, 1993, 9:00...