Shortly after starting to create the glossary several of the team members and some others decided to create an ER diagram of a possible implementation of a C&S system. We do not have a goal of creating such a system but this was done as an exercise to see if we could communicates with each other on this subject. The exercise clearly demonstrated that the glossary was useful and that it needed a lot more work.
It may also be helpful to look at this introduction to groupware.
access control - the ability to limit users to certain tasks or operations.
alarm - a notification to be sent, (with a "snooze time" and retry limit?)
assistant - see proxy
calendaring - 1) to register in a calendar or list, to register, to record. 2) management of any schedulable resource and related information.
conflict management - see negotiation They can't fly yet, but intelligent agents and smart software are beginning to walk. Here's how they can make you work smarter.
free time search - (bounded) common free time
groupware - computer based interpersonal collaboration, a buzzword with no inherrent meaning
negotiation - resource conflict resolution, at this point we are not commenting if there is an automated process in negotiation or if this is a manual process that possibly require multiple users to resolve.
notification - 1) The action of making known, an intimation, a notice. 2) reminder or alarm sent when any resource, or parties interested in the resource need an indicator that some attention is required. Possible notification methods include email, paging, zephyr, audible signal at the computer, visual indicator at the computer, voice mail, telephone
priority -
proxy agents - a user or group of users granted some rights or access control to a resource or other user. E.g. a secretary may be a proxy agent for a faculty member. Having the rights to comitt the faculty member to a meeting time. (Can a proxy agent be a program? Consider the HASSD lottery program as a possible example.)
recurring tasks - recurring events, either daily, weekly, monthly, yearly, 2nd Tuesday of the month excluding holidays and weekends, being examples.
reminders - see notification
rollover -
resource - 1) a stock or reserve upon which one can draw when necessary. 2) A resource is an item that may be scheduled usually under the control of a user or proxy. Resources do not control their own schedules while users normally do. Examples: facilities, physical objects that need to be shared, work (levels of effort). Examples of non-resources: courses, events, meetings, memos, todo lists.
scheduling - The action of entering in or drawing up a schedule esp. the preparation of a timetable for the completion of the various stages of a complex project, the co-ordination of many related actions or tasks into a single time sequence. A list of some things that can be scheduled: courses, events, facilities, meetings, resources, work. A list of some things that cannot be scheduled but may relate to calendaring: memos, todo lists, address book, phone logs.
scalability - a favorite DCNS buzzword. Design with the intent that a given service or application can be used by a large concurrent population without a degradation of service or having a negative impact on other services and users.
transport mechanism - how the data gets delivered. There are multiple ways to look at this. At a low layer we assume that TCP/IP is a requirement at MIT and that an institue wide solution cannot be based on Appletalk or IPX. At a higer layer we assume that very large systems should be based on a client server architecture rather than relying on email based solutions such as CC Mail, Groupwise, or SMTP. Why? see scalability and take a look at elementary queueing theory textbooks.
visibility - defines what portion of the calendar is visible to whom
XAPIA - X.400 API Association, which defines the XAPIA and MAPI from Byte Magazine Calendaring and Scheduling API (CSA) and the Common Messaging Call (CMC) API. The CSA defines an API that can be supported by calendaring and scheduling services. This API is designed to be independent of the actual calendaring and scheduling implementation.
