Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Automated Meeting Data Structure for Information Interchange in an Office Network

IP.com Disclosure Number: IPCOM000038390D
Original Publication Date: 1987-Jan-01
Included in the Prior Art Database: 2005-Jan-31
Document File: 1 page(s) / 12K

Publishing Venue

IBM

Related People

Scully, KJ: AUTHOR [+2]

Abstract

A data structure is described that provides a common way for applications to: (1) support interchanging meeting information between like and unlike systems in a common structure, (2) support automatic scheduling of meetings onto a selected number of calendars by connecting the meeting to a list of invited individuals and using the list to send out invitations, (3) support interchanging meeting status and individual requests for meeting status, (4) support storing meeting status in a common accessible format, (5) support remotely creating, changing and deleting portions of a meeting notice, (6) support applying an error action, security, identifier, distribution list identifier, time stamp, meeting date(s) and time(s), owner/arranger name, meeting status, owner/arranger role and address(s), meeting status, a user-defined field, meeting subject, meeting location and meeting details, (7) provide flexibility in requesting or not requesting an operator initiated response to a meeting notice with an RSVP indicator, and (8) support, with an algorithm, the scheduling of a meeting automatically into an open time block on an individual's calendar.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 58% of the total text.

Page 1 of 1

Automated Meeting Data Structure for Information Interchange in an Office Network

A data structure is described that provides a common way for applications to:
(1) support interchanging meeting information between like and unlike systems in a common structure, (2) support automatic scheduling of meetings onto a selected number of calendars by connecting the meeting to a list of invited individuals and using the list to send out invitations, (3) support interchanging meeting status and individual requests for meeting status, (4) support storing meeting status in a common accessible format, (5) support remotely creating, changing and deleting portions of a meeting notice, (6) support applying an error action, security, identifier, distribution list identifier, time stamp, meeting date(s) and time(s), owner/arranger name, meeting status, owner/arranger role and address(s), meeting status, a user-defined field, meeting subject, meeting location and meeting details, (7) provide flexibility in requesting or not requesting an operator initiated response to a meeting notice with an RSVP indicator, and
(8) support, with an algorithm, the scheduling of a meeting automatically into an open time block on an individual's calendar. This structure provides fields for like and unlike calendar products to interchange and to remotely create/change a meeting notice. The structure is a common way to carry a meeting notice and associated meeting information. The notice is configured...