1 / 12

Relevant Standards?

Relevant Standards?. OSA / Mellon Meeting December 11, 2002. Goals. What are the relevant standards in the application domains of: Messaging Calendaring / Scheduling Reservations Notifications Learning Management Systems. Messaging. Traditional email POP IMAP SMTP / eSMTP MAPI

anais
Download Presentation

Relevant Standards?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Relevant Standards? OSA / Mellon Meeting December 11, 2002

  2. Goals • What are the relevant standards in the application domains of: • Messaging • Calendaring / Scheduling • Reservations • Notifications • Learning Management Systems

  3. Messaging • Traditional email • POP • IMAP • SMTP / eSMTP • MAPI • PGP / SMIME

  4. Calendaring and Scheduling • iCalendar from IETF • Data format for event data • MIME object • XML with a DTD, 1-to-1 transformation, less extensible than XML with namespace

  5. Products using iCalendar • Various Oracle/Corporate Time product lines • Lotus Domino and Notes Release Rnext, Organizer • Sun Calendar Server Version 5.next • Exchange, Outlook, Outlook Express • MeetingMaker (data import) • Apple iCAL currently uses vCalendar

  6. iTIP • A transport independent protocol to transport iCalendar objects • iMIP defines email as an iTIP transport • iRIP is another iTIP binding or profile • ISIP is a proposed binding

  7. CAP – Calendar Access Protocol • Intended as the protocol between a calendar user agent and a calendar server • CAP is a BEEP profile • Still in draft, no known implementations, however libical has been planning an implementation • BEEP uses SASL / TLS for authentication • VSQueries of data on server to create views

  8. SKICAL • iCalendar extensions driven by Swedish tourism requirements • ‘the 11:00am tour of the castle will be in German but a taped presentation will be available in English’

  9. OKI’s C&S API • Not intended for a server implementation • Very simple API that can be used to create a gateway into other C&S systems for simple queries or commitments.

  10. The SIP community • ISIP - iCalendar SIP-Based Interoperability Protocol • The goal of this document is to extend the iCalendar framework so that it can be used to describe Internet multimedia conferences and chat rooms. • Discussion about using this as event notification to user’s cell phones. • This is an iTIP binding

  11. MAPI providers • Replacement MAPI providers have been used to provide group scheduling in Outlook without and Exchange server • Corporate Time’s Outlook Connector • Bynari’s Insight Connector

  12. Reservation Systems • Reservation Systems are C&S systems constrained by rule based authorization systems • No standard protocols or APIs at this time. Some SIP work is a small subspace of this application domain.

More Related