-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: upload all press releases in textual format, combine with annou…
…ncements when appropriate (with announcement information moved to abstract)
- Loading branch information
Showing
52 changed files
with
2,391 additions
and
1,519 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,64 +13,5 @@ excerpt: | | |
*August 20, 2004* + | ||
*CalConnect Interoperability Event Publicity Release*: The first publicity | ||
release issued by the Consortium following the July 29-30 2004 Event. | ||
link:{{'/docs/press-releases/0407interop1.pdf' | relative_url }}[CalConnect | ||
Interoperability Event Publicity Release]. | ||
|
||
*Industry Leaders Score at Calendaring and Scheduling Interop* | ||
|
||
_IBM, Oracle Demonstrate Conformance with Key Parts of IETF | ||
Specification; + Interoperability Testing Highlights Need for Well-Focused | ||
Consortium*Berkeley, CA – August 20, 2004 –* On July 29-30, the University of | ||
California at Berkeley hosted the first calendaring consortium-sponsored | ||
testing event on the interoperable exchange of | ||
calendaring and scheduling information between dissimilar programs, platforms, and | ||
technologies. | ||
|
||
“UC Berkeley has long depended on and fostered the use and development | ||
of standards,” noted Jeffrey McCullough, Principal Programmer, | ||
University of California, Berkeley. “Hosting this event was a great | ||
opportunity to further enhance interoperability in calendaring by | ||
providing forward thinking, standards compliant vendors a place to come | ||
together and test their products.” | ||
|
||
The technical goal of the Interop was to test a set of specifications | ||
developed by the Internet Engineering Task Force (IETF), specifically | ||
RFC 2445-6 and 7: iCalendar, iTIP and iMIP. Organizers produced the | ||
event to move the RFCs forward toward standards status as well as to | ||
ascertain the need for an industry/customer consortium on calendaring | ||
and scheduling. | ||
|
||
Dr. Nathaniel S. Borenstein, Distinguished Engineer, IBM Lotus Division, | ||
said, “IBM's Lotus Software helped lead the definition of the original | ||
iCal standards, and has supported them in our products since their | ||
publication in 1998. The standards represented an important step | ||
forward, but since then, the implementor community has learned a great | ||
deal about calendar interoperation.” | ||
|
||
Regarding the Interop, Dr. Borenstein added, “IBM's Lotus Software | ||
enthusiastically supports the efforts of the emerging Calendaring & | ||
Scheduling Consortium to revitalize the standards process and iron out | ||
the wrinkles that have kept Internet calendaring from reaching its full | ||
potential. We view this Interop as another step in the long march | ||
towards fully interoperable calendar systems, and look forward to | ||
further cooperation and progress.” | ||
|
||
“Oracle is delighted to have contributed to this interoperability | ||
testing event for the benefit of our customers and the global | ||
calendaring and scheduling community,” said Marten den Haring, Director | ||
of Product Management, Oracle Collaboration Suite Calendar. “We support | ||
the development and promotion of emerging open standards as well as the | ||
efforts of a number of standards bodies, including the IETF. These | ||
efforts help build momentum for the adoption of an open protocol to | ||
access and manage calendaring information.” | ||
|
||
*Media Contact* + | ||
Maryann Karinch + | ||
970-577-8500 + | ||
[.underline]#[email protected]# | ||
|
||
*Consortium Contact* + | ||
Dave Thewlis + | ||
707-840-9391 + | ||
[.underline]#[email protected]# | ||
|
||
HTML: link:{{'/news/2004-08-20-industry-leaders-score-at-interop' | relative_url }}[Industry Leaders Score at Calendaring and Scheduling Interop]. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,75 @@ | ||
--- | ||
layout: page | ||
title: Industry Leaders Score at Calendaring and Scheduling Interop | ||
type: news | ||
date: 2004-08-20 | ||
categories: press-releases | ||
excerpt: | | ||
IBM, Oracle Demonstrate Conformance with Key Parts of IETF Specification; | ||
Interoperability Testing Highlights Need for Well-Focused Consortium | ||
--- | ||
:page-liquid: | ||
|
||
== Industry Leaders Score at Calendaring and Scheduling Interop | ||
|
||
_IBM, Oracle Demonstrate Conformance with Key Parts of IETF | ||
Specification; Interoperability Testing Highlights Need for Well-Focused | ||
Consortium_ | ||
|
||
PDF: link:{{'/docs/press-releases/0407interop1.pdf' | relative_url }}[CalConnect Interoperability Event Publicity Release]. | ||
|
||
*Berkeley, CA – August 20, 2004 –* On July 29-30, the University of | ||
California at Berkeley hosted the first calendaring consortium-sponsored | ||
testing event on the interoperable exchange of calendaring and | ||
scheduling information between dissimilar programs, platforms, and | ||
technologies. | ||
|
||
“UC Berkeley has long depended on and fostered the use and development | ||
of standards,” noted Jeffrey McCullough, Principal Programmer, | ||
University of California, Berkeley. “Hosting this event was a great | ||
opportunity to further enhance interoperability in calendaring by | ||
providing forward thinking, standards compliant vendors a place to come | ||
together and test their products.” | ||
|
||
The technical goal of the Interop was to test a set of specifications | ||
developed by the Internet Engineering Task Force (IETF), specifically | ||
RFC 2445-6 and 7: iCalendar, iTIP and iMIP. Organizers produced the | ||
event to move the RFCs forward toward standards status as well as to | ||
ascertain the need for an industry/customer consortium on calendaring | ||
and scheduling. | ||
|
||
Dr. Nathaniel S. Borenstein, Distinguished Engineer, IBM Lotus Division, | ||
said, “IBM's Lotus Software helped lead the definition of the original | ||
iCal standards, and has supported them in our products since their | ||
publication in 1998. The standards represented an important step | ||
forward, but since then, the implementor community has learned a great | ||
deal about calendar | ||
interoperation.” | ||
|
||
Regarding the Interop, Dr. Borenstein added, “IBM's Lotus Software | ||
enthusiastically supports the efforts of the emerging Calendaring & | ||
Scheduling Consortium to revitalize the standards process and iron out | ||
the wrinkles that have kept Internet calendaring from reaching its full | ||
potential. We view this Interop as another step in the long march | ||
towards fully interoperable calendar systems, and look forward to | ||
further cooperation and progress.” | ||
|
||
“Oracle is delighted to have contributed to this interoperability | ||
testing event for the benefit of our customers and the global | ||
calendaring and scheduling community,” said Marten den Haring, Director | ||
of Product Management, Oracle Collaboration Suite Calendar. “We support | ||
the development and promotion of emerging open standards as well as the | ||
efforts of a number of standards bodies, including the IETF. These | ||
efforts help build momentum for the adoption of an open protocol to | ||
access and manage calendaring information.” | ||
|
||
*Media Contact* + | ||
Maryann Karinch + | ||
970-577-8500 + | ||
[.underline]#[email protected]# | ||
|
||
*Consortium Contact* + | ||
Dave Thewlis + | ||
707-840-9391 + | ||
[.underline]#[email protected]# | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -16,59 +16,5 @@ excerpt: | | |
Consortium following the 23-24 September 2004 Roundtable on the Future | ||
of Interoperable Calendaring and Scheduling sponsored by the Consortium | ||
and hosted by Oracle. | ||
link:{{'/docs/press-releases/0409roundtable1.pdf' | relative_url }}[Roundtable Publicity | ||
Release]. | ||
|
||
*Top Vendors, Users Act to End Problem of Incompatible Calendaring and | ||
Scheduling Products* | ||
|
||
*McKinleyville, CA – October 5, 2004 –* On September 23-24, industry | ||
leaders and major academic customers of calendaring and scheduling | ||
products focused on the path to + | ||
interoperability in a second event sponsored by the emerging Calendaring | ||
and Scheduling Consortium. Hosted by Oracle Corporation in Montreal, “A | ||
Roundtable Discussion on the Future of Interoperable Calendaring and | ||
Scheduling” participants included Duke University, IBM Lotus Software, | ||
Isamet, The Mozilla Foundation, Novell, Oracle, the Open Source | ||
Applications Foundation, Stata Labs, the University of California at | ||
Berkeley, the University of Washington, and Yahoo. It was a follow-up to | ||
a Consortium-sponsored testing event at the University of California, | ||
Berkeley on July 29-30. | ||
|
||
“A lack of interoperable calendaring and scheduling products is a major | ||
productivity barrier,” said Dave Thewlis, executive director of the | ||
Calendaring and Scheduling Consortium. “It can lead to serious | ||
miscommunications, failed activities, and a huge waste of time.” | ||
|
||
By involving both the vendors and the user community, participants | ||
intended the Roundtable to contribute to measurable progress toward | ||
achieving interoperable calendaring and scheduling. Products of the | ||
Roundtable include statements of common vision and shared goals, a | ||
charter for the Consortium, and the kernel of an action plan. | ||
|
||
"A primary goal of the consortium is to further the design and | ||
implementation of calendaring and scheduling standards,” said Marten den | ||
Haring, director, Product Management, Oracle + | ||
Collaboration Suite Calendar. “The Roundtable's outcome is the blueprint | ||
for the Calendaring and Scheduling Consortium, and Oracle is proud to be | ||
one of the organizations involved with this effort, which will create | ||
initiatives that benefit collaboration.” | ||
|
||
Discussions at the event covered topics such as the applicability of | ||
existing forums; co-existence and harmonization with the Internet | ||
Engineering Task Force (IETF), customer and user involvement with use | ||
cases, requirements setting and directions; and interoperability testing | ||
and conformance. | ||
|
||
*Media Contact* + | ||
Maryann Karinch + | ||
970-577-8500 + | ||
[.underline]#[email protected]# | ||
|
||
*Consortium Contact* + | ||
Dave Thewlis + | ||
707-840-9391 + | ||
[.underline]#[email protected]# | ||
|
||
|
||
|
||
HTML: link:{{'/news/2004-10-05-vendors-users-interop' | relative_url }}[Top Vendors, Users Act to End Problem of Incompatible Calendaring and Scheduling Products]. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,64 @@ | ||
--- | ||
layout: page | ||
title: Top Vendors, Users Act to End Problem of Incompatible Calendaring and Scheduling Products | ||
type: news | ||
date: 2004-10-05 | ||
categories: press-releases | ||
excerpt: | | ||
On September 23-24, industry leaders and major academic customers of calendaring | ||
and scheduling products focused on the path to interoperability in a second event | ||
sponsored by the emerging Calendaring and Scheduling Consortium. | ||
--- | ||
:page-liquid: | ||
|
||
== Top Vendors, Users Act to End Problem of Incompatible Calendaring and Scheduling Products | ||
|
||
PDF: link:{{'/docs/press-releases/0409roundtable1.pdf' | relative_url }}[Roundtable Publicity Release]. | ||
|
||
*McKinleyville, CA – October 5, 2004 –* On September 23-24, industry | ||
leaders and major academic customers of calendaring and scheduling | ||
products focused on the path to | ||
interoperability in a second event sponsored by the emerging Calendaring | ||
and Scheduling Consortium. Hosted by Oracle Corporation in Montreal, “A | ||
Roundtable Discussion on the Future of Interoperable Calendaring and | ||
Scheduling” participants included Duke University, IBM Lotus Software, | ||
Isamet, The Mozilla Foundation, Novell, Oracle, the Open Source | ||
Applications Foundation, Stata Labs, the University of California at | ||
Berkeley, the University of Washington, and Yahoo. It was a follow-up to | ||
a Consortium-sponsored testing event at the University of California, | ||
Berkeley on July 29-30. | ||
|
||
“A lack of interoperable calendaring and scheduling products is a major | ||
productivity barrier,” said Dave Thewlis, executive director of the | ||
Calendaring and Scheduling Consortium. “It can lead to serious | ||
miscommunications, failed activities, and a huge waste of time.” | ||
|
||
By involving both the vendors and the user community, participants | ||
intended the Roundtable to contribute to measurable progress toward | ||
achieving interoperable calendaring and scheduling. Products of the | ||
Roundtable include statements of common vision and shared goals, a | ||
charter for the Consortium, and the kernel of an action plan. | ||
|
||
"A primary goal of the consortium is to further the design and | ||
implementation of calendaring and scheduling standards,” said Marten den | ||
Haring, director, Product Management, Oracle | ||
Collaboration Suite Calendar. “The Roundtable's outcome is the blueprint | ||
for the Calendaring and Scheduling Consortium, and Oracle is proud to be | ||
one of the organizations involved with this effort, which will create | ||
initiatives that benefit collaboration.” | ||
|
||
Discussions at the event covered topics such as the applicability of | ||
existing forums; co-existence and harmonization with the Internet | ||
Engineering Task Force (IETF), customer and user involvement with use | ||
cases, requirements setting and directions; and interoperability testing | ||
and conformance. | ||
|
||
*Media Contact* + | ||
Maryann Karinch + | ||
970-577-8500 + | ||
[.underline]#[email protected]# | ||
|
||
*Consortium Contact* + | ||
Dave Thewlis + | ||
707-840-9391 + | ||
[.underline]#[email protected]# |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
--- | ||
layout: page | ||
title: Top Vendors, Users Launch Calendaring and Scheduling Consortium | ||
title: Top Vendors, Users Launch Calendaring and Scheduling Consortium | ||
type: news | ||
date: 2004-12-14 | ||
categories: press-releases | ||
|
@@ -14,114 +14,5 @@ excerpt: | | |
*December 14, 2004* + | ||
*Public Launch Release*: The publicity release issued by the Consortium | ||
to mark its public launch. | ||
link:{{'/docs/press-releases/041214publiclaunch.pdf' | relative_url }}[Public Launch | ||
Release]. | ||
|
||
*Top Vendors, Users Launch Calendaring and Scheduling Consortium* _Goal: | ||
End the Problem of Incompatible Calendaring and Scheduling Products_ | ||
|
||
*McKinleyville, CA – December 14, 2004 –* Seven vendors, six | ||
universities, two open source foundations, and a research | ||
facilityembership of the Calendaring and Scheduling Consortium (), which | ||
named David C. | ||
|
||
Thewlis the first Executive Director. The on the interoperable exchange | ||
of calendaring and scheduling information between dissimilar programs, | ||
platforms, and technologies. The founding members are (in alphabetical | ||
order) Duke University, EVDB, Isamet, Jet Propulsion Laboratory, Meeting | ||
Maker, M.I.T., The Mozilla Foundation, Novell, Open Source Application | ||
Foundation, Oracle Corporation, Stanford University, Symbian, UC | ||
Berkeley, University of Washington, University of Wisconsin Madison, and | ||
Yahoo! Inc. | ||
|
||
“Our members’ intent is to enable calendaring and scheduling tools and | ||
applications to enter the mainstream of computing,” said Dave Thewlis. | ||
“After email, the World Wide Web, and instant messaging, calendaring and | ||
scheduling capabilities are what business people and consumers will | ||
really care about.” | ||
|
||
“This isn’t simply about calendar programs,” noted Patricia Egen, | ||
Interop manager and member of the Board of Directors, who originated the | ||
idea of the Consortium. “This is about seamlessly connecting your | ||
calendar with others so that your professional and personal life runs | ||
more smoothly.” | ||
|
||
The Consortium, planned to have a three- to five-year lifespan in which | ||
to achieve its objectives, builds on work already accomplished or in | ||
progress within the Internet Engineering Task Force (IETF). Currently, | ||
large consumers such as universities and corporations face costly | ||
problems coordinating resources because departmental calendaring and | ||
scheduling applications may not be based on open standards that allow | ||
interoperability. Even standards-based systems from different vendors | ||
may not work together. With sets of IETF specifications as the heart of | ||
a solution, the Consortium provides a forum for vendors to mitigate | ||
conflicts between their competing products. | ||
|
||
The Consortium has a schedule of activities that give the relevant | ||
standards commercial value, that is, promotion, requirements setting, | ||
and validation. Events on the agenda include• Three to four interoperability testing events (“Interops”) a year, with | ||
the next one scheduled for January 11-12 in Seattle, WA.• Roundtables and Technical Committee meetings of the Consortium; the next | ||
is scheduled for 11-13 January in Seattle, WA, co-located with the | ||
Interop event.• Ongoing Technical Committee work, intended to provide feedback or | ||
information to IETF standards activities• Presentations at related conferences + | ||
Non-members are welcome to participate in the Interops, but Roundtables | ||
and Technical Committees are for members only. | ||
|
||
_Quotes from Members of the Steering Committee_ | ||
|
||
Duke University (www.duke.edu) + | ||
“The Calendaring and Scheduling Consortium appears to be re-invigorating | ||
the + | ||
development of calendaring standards that became stalled for a few | ||
years,” Michael Gettes, senior IT architect at Duke University, said. | ||
“We now have customer involvement along with all the important calendar | ||
standards leaders and vendors to ensure we develop interoperable | ||
solutions as quickly as possible. It is an exciting time for the | ||
calendaring industry.” | ||
|
||
The Mozilla Foundation (www.mozilla.org) + | ||
“The launch of the Calendaring and Scheduling Consortium represents a | ||
promising step forward in the development of critical calendaring | ||
standards,” said Mike Shaver of the Mozilla Foundation. “The Mozilla | ||
Foundation is excited to participate in the + | ||
Consortium's efforts to link users, vendors and protocol architects in | ||
pursuit of + | ||
universally interoperable calendaring.” | ||
|
||
Open Source Application Foundation (www.osafoundation.org) + | ||
“OSAF is pleased to be able to support the development of | ||
interoperable + | ||
calendaring solutions by becoming a founding member of the Calendaring + | ||
and Scheduling Consortium,” said Lisa Dusseault, Development manager, | ||
standards architect, OSAF. “The Consortium plays an important role in | ||
enabling the dialog between partners that is essential for the | ||
establishment of open and interoperable standards.” | ||
|
||
The University of Washington (www.cac.washington.edu) + | ||
“For years there has been a large need within higher education for | ||
interoperable standards-based calendaring,” noted Oren Sreebny; | ||
Director, Client Services + | ||
and Learning Technologies; Computing & Communications; University of + | ||
Washington. “This need is growing with the proliferation of online | ||
scheduling and pervasive portable devices. The ability for an | ||
organization like CalConnect to provide a neutral forum to encourage all | ||
interested parties to collaborate on solving these sets of issues and to | ||
demonstrate the usefulness of interoperation is critical for moving this | ||
mission forward. We are proud to be part of the founding of this | ||
organization, and look forward to working with the members to advance | ||
the state of the art in calendaring and scheduling.” | ||
|
||
The University of Wisconsin (www.doit.wisc.edu) + | ||
“The University of Wisconsin-Madison became a founding member of the | ||
Calendaring and Scheduling Consortium to help our campus customers,” | ||
explained Bill Scheuerell Director of Enterprise Internet Services, | ||
Division of Information Technology, + | ||
University of Wisconsin-Madison Campus. “Departments rely on integrated | ||
calendaring to organize university schedules. The consortium will help | ||
all of us set interoperability standards and system features, and | ||
communicate them to potential vendors.” | ||
|
||
Contact: Maryann Karinch, 970-577-8500, [email protected] | ||
|
||
|
||
|
||
HTML: link:{{'/news/2004-12-14-public-launch' | relative_url }}[Public Launch Release]. |
Oops, something went wrong.