This ChandlerGlossary page includes entries for some of the software products that seem to get mentioned often on the Chandler Wiki pages, such as Agenda, Ecco, and Eudora. This glossary does not include a complete list of relevant software products. For a longer list, see OtherPIMSoftware20030225.
Note: Lists of Software Standards
This ChandlerGlossary page includes entries for some of the software standards that seem to get mentioned often on the Chandler Wiki pages, such as IMAP, Jabber, and RDF. This glossary does not include a complete list or relevant software standards. For more standards, see also CodeInfrastructureIssues and EmailStandards.
AmbiguousTerms -- A page for highlighting and discussing terms that may cause problems with documentation or labelling.
a a a a a a a a a a a a a a a a a a a a a a a a a a a a a a
Agents are plug-in modules containing Python scripts and other resources like images, that perform tasks on behalf of the user, either when explicitly requested or when the agent notices particular conditions arising. See AgentIssues. See http://osafoundation.org/agent_framework_v.3.htm
an annotation is an item that represents a note that a Chandler user adds to an email message or to any other item. An annotation might also represent an actual editing change to the original message itself. See EditingReceivedEmail. See MessageAnnotation.
Application Programmer Interface. An API is something created by computer programmers working on one project, like Chandler, in order to allow other programmers to build components that work with the project. See http://wiki.osafoundation.org/bin/view/Main/APIs
In Microsoft Outlook, an archive is like a special repository that holds older, archived email messages. (@@@ - Does Chandler have any notion of archives?)
(@@@ - using user names and passwords to try to verify that a user can log in to an account. Probably used for email and IM, as well as communication between Chandler clients, and between a Chandler client and a Chandler server)
a set of access control mechanisms that Chandler provides for sharing calendars and for delegating authority for others to control one's calendar. See CalendarAuthorization. See AuthorizationIssues. (@@@ - Are the same access control mechanisms used throughout the rest of Chandler)
As a noun, a bounce message is a type of incoming email message. As a verb, outgoing email can sometimes bounce. Bounces usually occur due to misspelt or unknown recipient addresses, or because the recipient's mailbox full (aka over quota). See BounceManagement
Bugzilla is a piece of software, developed by the Mozilla project, that the Chandler team uses to fix bugs and that OSAF uses to track projects. You can find Chandler's Bugzilla at http://bugzilla.osafoundation.org; you can find out more about Bugzilla at http://www.bugzilla.org/ .
A build system is the infrastructure used to create something a computer can understand from something that humans create. This is not always as simple and straightforward as simply compiling something, because those pesky humans seem to always want to have a zillion different options (e.g. debug mode or optimization mode), use three zillion different libraries that are in two zillion different places, and be able to have the code run on two or three different versions of two or three different operating systems.
blocks of time on one person's calendar that appear to a second person as being booked, without the other person seeing why the first person is busy or who the first person is meeting with. See available time. See free time.
c c c c c c c c c c c c c c c c c c c c c c c c c c c c c c
1. There may be a Calendar parcel as one of Chandler's standard parcels.
2. A calendar is a collection of a user's event items. Only it's actually far more complicated that that. For example, a calendar also has associated authorizations. And a calendar may be associated with a resource rather than a person.
a view type, showing an ECCO like outline, for events, tasks, and items associated with a range of time (week, day, month, etc). See CalendarOutlineView.
a feature in some applications. When a user types text into a text field, the application tries to guess how the text should be completed. For example, in the "to:" field of an email message window, if a user starts to type "lessig@os", the application may automatically complete the line to read "lessig@osafoundation.org". See NamespaceCompletion20030116. See smart parsing. See auto completion.
A condition is a state that the data in a repository can be in. For example, one condition might be that there are more than 10 task items which are not marked closed. A conditions can trigger a script.
Cross-platform code is code that runs on more than platform without a programmer needing to write different versions of the code for the different platforms. See platform.
d d d d d d d d d d d d d d d d d d d d d d d d d d d d d d
1. An event is an item that represents an entry on a calendar. For example, "dinner with Sara". Events nominally have start times and end times and durations, but some events may just have a date, and some events may repeat on different days or at different times. See item.
2. An event is something that a Chandler instance performs, either in response to a user action, or automatically, because a condition was met. For example, deleting an email message would be an event, as would sorting a list of tasks based on their urgency. An event can trigger a script.
a set of calendar events, with a 'master' event and one or more related events. For example, a series of events in a conference. See CalendarEventSets.
copying data out of a Chandler repository to some external data file, in a format useful to some other application, like Outlook. See import. See archive. See CalendarImportExport.
1. In some email applications, filters are used to sort incoming email messages. For example, a filter might be used to filter out SPAM. In Microsoft applications, filters are called rules.
2. In Chandler, a filter is a named item that specifies how to sort other items, such as email messages. Filters in Chandler are likely to be implemented as queries in specialized view types. Filters will be useful for managing email messages, but filters will also be useful for managing other types of items, such as events in a calendar. See RulesFiltersIssues. See EmailFilters. See MailFilters
This is an old name for the initial, preliminary version of Chandler. The "first public release" is now being called Chandler Release 0.1. It's scheduled to be released in the first half of 2003. See http://www.osafoundation.org/Chandler_rel._0.1.htm
In Microsoft Outlook, a folder is like a mini-repository that can hold items. See virtual folder. Some mail tools use the term folder to describe a user's collection of email messages. Eudora uses the term "mailbox". In Chandler, data items (including email messages) are organized into views. See also AmbiguousTerms
the interface through which a user accesses their Chandler data. Chandler may someday have a web based front end and a PDA front end, in addition to the normal Chandler client front end.
g g g g g g g g g g g g g g g g g g g g g g g g g g g g g g
an application that Chandler calls in order to display attachments of some registered type, like PDF attachments or Microsoft Word attachments. See media handler.
Hypertext Markup Language. A software standard. HTML is a document format. HTML was originally designed to be used for creating web pages. Now HTML is also used as a format for email messages.
Hypertext Transfer Protocol. A software standard. HTTP is a protocol that computers use to communicate. Web browsers use HTTP to get web pages from server computers.
i i i i i i i i i i i i i i i i i i i i i i i i i i i i i i
Internet Mail Access Protocol. A software standard. IMAP is a protocol that computers use to exchange information. Email clients use IMAP to get email messages from servers.
how text gets from a keyboard to a computer's memory in the right character encoding. One example of a Chinese input method is a utility where the user types a transcription (using Latin characters) of the Chinese character into a small window. Characters that correspond to the transcription pop up in a menu, and the user can then select the appropriate character(s).
After Jane creates an event in her calendar, she can send invitations for the event to other people. (@@@ - Are these invitations sometimes just a simple email message, and are they sometimes independent items themselves?)
Chandler items are things like email messages, events in a calendar, to-do list tasks, address list contacts, and email attachments. Chandler items are stored in Chandler repositories. Users can create items that represent all sorts of different things, such as web page bookmarks, MP3 music tracks, files in a file system, glossary terms, book citations, capital cities, or just about anything else. See ItemsAndAttributesDataModelIssues. See http://blogs.osafoundation.org/mitch/000092.html.
A type of item. An item type has a defined set of attributes, but the item type itself does not have values for any of the attributes. For example, "Book" might be a new item type, with attributes like "Title", "Author" and "Copyright Date". A particular book would be an item, with attribute values like "Green Eggs and Ham", "Dr. Seuss", and "1960".
an installation of Chandler where the client software is installed without a local repository. In kiosk mode the Chandler client is not associated with a particular user permanently, but can be shared by lots of users. For example, a computer in a library might have a kiosk mode installation of Chandler.
l l l l l l l l l l l l l l l l l l l l l l l l l l l l l l
A part of the user interface. A web-like tool bar that displays the URL of the primary view it is referring to. The location bar has "back", "forward", "refresh" and "stop" buttons as in a web browser. See http://www.osafoundation.org/Vista_prototype.htm
m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m
A service that forwards email messages to a list of subscribers. For example, the Yahoo Groups service provides a feature for setting up a mailing list. See ChandlerMailingListFeatures.
a component of Chandler that knows how to display some particular type of media. Chandler will probably have lots of media handlers, including image handlers, audio handlers, and movie handlers. See helper application.
Metadata is data that describes the structure or roll of normal data. For example, let's say you have a piece of normal contact info data like this: (Pat Collins, 650-555-1212, 415-555-4386). The corresponding metadata might be ("name", "home phone", "fax"). Without the metadata, it's hard to know how to interpret the data, and you might end up accidentally calling the fax machine.
A milestone is calendar date with a build associated with it used for planning purposes only. Milestones can be entered in as due dates in Bugzilla and it gives OSAF a convenient shorthand for talking about issues. "Oh, I think I can get that in by the next milestone." Note that milestones are based on dates, not on features: "July 25th" might be a milestone, but "when POP is ready" is not.
the process of a user going from view to view, or going from item to item within a view. The user might navigate by clicking on links, or by pressing a "back" button, or by typing in the URL for an item or view.
A part of the user interface. A web-like tool bar that displays the URL of the current view parcel and associated navigation buttons to return to past views.
Chandler can send a user a notification when some event happens, or when some condition arises. A notification might be sent via email, or via IM, or in some platform specific way, like by animating an icon on a system tray. See CalendarNotifications.
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
An outline view is a view type that displays items in a hierarchical outline. For example, a to-do list view that shows a list of tasks and sub-tasks would be an outline view. See OutlineViewIssues?.
A parcel is an aggregate object, conveyed in a single file, that adds new functionality to Chandler; it's the main way of distributing Chandler extensions. A parcel may contain Chandler data items (contacts, calendars, images, etc), plus Python scripts to implement new types of views and agents, as well as version and dependency information, and cryptographic credentials. Chandler will be distributed with a few built-in parcels, but others can be downloaded from the web or shared using Chandler's sharing capabilities. Standard parcels will probably be Email, Calendar, Contacts, Tasks, and Instant Messaging. Chandler will include a simple UI that allows users to install, remove, inspect, create and share parcels. See Parcels
The foundation of the application, the parcel framework provides common services to the parcels. The parcel framework also manages the Parcel Independent UI, which provides user interface elements common to the application, independent of a particular viewer parcel. See ZeroPointOneReleaseComponents.
A user can have multiple roles to play or may want to split between work and home related stuff. Chandler uses the concept of persona to distinguish between these roles. Personas are useful in providing authorization for access controls. (Eudora uses the term "Personalities" for its version of "Personas".) See also MultiplePersonas.
Software applications run on platforms. A platform is a type of computer or a software environment. For example, Microsoft's Internet Explorer runs on the Mac and Windows platforms. Internet Explorer can itself be viewed as a platform, and some software components, like JavaScript scripts, run within the Internet Explorer environment. Chandler will run on the Mac, Windows, and Linux platforms. Eventually, Chandler itself may serve as a software platform, and then other software components will run within the Chandler environment.
a user can publish a calendar for other users to subscribe to. See subscription. See CalendarPublishingAndSharing?. (@@@ - What else can a user publish?)
A query is used to populate a view with items. For example, a Calendar Week View might query the repository for all of the events created by Mary that occur between 21 December 2003 and 27 December 2003. Complicated queries can be built up from simpler queries. See remote query.
r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r
Resource Description Framework. A software standard. RDF is a general purpose document format used for creating documents that have clear labels to describe the data the documents contain. See http://www.osafoundation.org/technology.htm
A special file or directory that holds a bunch of Chandler data items. A repository may hold all the items of a single user, or a number of users may connect to a single shared repository. See RepositoryIssues.
Items can have relationships to other items. For example, an event is related to the calendar that it appears in. Or perhaps a meeting event might have a related conference room where the meeting will be held. See link.
1. In the context of calendars, a resource is typically a conference room or a piece of equipment. A resource calendar is a calendar that doesn't represent a person's schedule, but instead represents the schedule of a shared resource, like a lecture hall or a company van.
2. in web terminology, a resource is anything addressable via a URL
1. A Chandler script is little set of commands that Chandler knows how to execute. For example, a script might contain commands to send a daily email message with a list of upcoming appointments. Scripts can be triggered by conditions.
2. An email script is a script that arrives as an attachment on an incoming email message.
Each view or item can have it's own sharing policy which determines who can see, or edit, the view or item. The two most simple sharing policies are just "public" and "private".
a feature where Chandler recognizes dates, names, addresses, and items already in the repository. In some applications, when a user types text into a text field, the application tries to guess about what the text means. For example, the application might recognize "10 Oct 1999" as being a date, or might recognize "Steve Jobs" as being the name of a contact in the address book. See completion. See ContentParsingFrameworkIssues.
Simple Mail Transfer Protocol. A software standard. SMTP is a protocol that computers use to exchange information. Email clients use SMTP to send email messages from servers.
"Snake" is a word used inside OSAF (borrowed from Netscape) to mean important problems that we don't have consensus on how to attack. This can mean either that the OSAF staff doesn not have a clue, that OSAF has too many clues, or that we don't have someone whose job it is to have a clue. Note that merely being difficult doesn't make something a snake. Running a marathon is very difficult, but
marathons are not very important to OSAF
it is very clear what is required to finish the course
The standard attributes are attributes that are pre-defined by OSAF. There are a small number of standard attributes that all items have, like "Project" and "Status". There are other standard attributes that not all items have, but that all items of a special type have. For example, all email message items have a recipient attribute. See attribute. See user-defined attribute.
In Microsoft applications, stationery is something that makes your document pretty, sort of like a style sheet. In Eudora, stationary is a response template (aka boilerplate, aka "form letter", aka "canned response"). In Chandler, templates refer to the text and style sheets refer to the presentation.
1. In the context of calendars, a user can subscribe to a calendar, or part of a calendar. Users subscribe in order to get updates when the source calendar changes. See publish. See CalendarSubscription.
2. In the context of instant messaging, Jabber servers maintain subscription info, so that one user can subscribe to the presense status of another user.
A table view is a view type that displays items in a table. For example, the view that shows a list of email messages -- with subject, date, sender, size, etc -- would be a table view. See also tabular view. See also email table view.
User Interface. The part of an application that a user sees. ("A language of interaction that matches the human communication system to that of the computer." -- DanIngalls?, "Design Principles behind Smalltalk," 1981)
Uniform Resource Locator. A software standard. A URL is an address for a document. Here's an example URL: http://osafoundation.org/contact.htm. Chandler will have URLs for parcels, views, and items.
For example, pressing a button, or selecting a menu item. User actions trigger events. The term "command" has also been used as a synonym for user action. See RepeatLastCommandInToolbar20030124.
the actual data in a particular attribute of a particular item. For example, the "home phone" attribute of a contact might have the value "650-555-1212".
Views are the primary interface in which users browse, create and edit Chandler items. A view consists of a view type and a set of queries applied to Chandler's data repositories. See also ViewIssues20021219
A view type is the user interaction implementation of the view. A view uses a view type to display items to a user. For example, Chandler might offer view types for: table views, outline views, icon views, weekly calendar views, and address card views. See also ViewIssues20021219
Chandler keeps all of its email messages in one place, but allows users to view the messages in virtual folders that display selected subsets of messages.
Extensible Markup Language. A software standard. XML is a general purpose document format used for creating documents or exchanging data packets between computers.
y y y y y y y y y y y y y y y y y y y y y y y y y y y y y y
z z z z z z z z z z z z z z z z z z z z z z z z z z z z z z