Beruflich Dokumente
Kultur Dokumente
Bedework
Hello World!
What is Bedework
Comprehensive calendaring /events system Jasig community source project Platform independent (Java) Modular & extensible Intended for higher education
and
Standards based!
Institutional Calendar
Bedework History
2006
Bedework 3.0 1st Release Mellon Foundation MATC Award
2009
Jasig incubator project
2010
Bedework 3.6 Jasig sponsored project
2011
Bedework 3.7
UC Berkeley Brown University Duke University Public University of Navarra (Spain) Rensselaer Polytechnic Institute (RPI) Yale University
Use your database system Use your local authentication Use your language and culture Use your portal Use your look and feel Use your calendaring clients and smart phones Integrate with your applications Install with your IT staff you dont have to be calendaring or Java experts!
Bedeworks preoccupation with standards and interoperability is in large part recognition that in many organizations, Bedework is unlikely to be the only calendaring product in an enterprise. The ability to share and exchange data with other calendaring products and environments is an important key to Bedeworks future. We implement standards, we author standards, we promote standards!
Putting events in
root
Engineering
Mann Lib
...
Seminars Staff Events
...
CALS
...
Lectures
Meetings
...
Roundtable
...
Dept. Functions
Putting events in
root
Engineering
Mann Lib
...
Seminars Staff Events
...
CALS
...
Lectures
Meetings
...
Roundtable
...
Dept. Functions
Putting events in
root
Engineering
Mann Lib
...
Seminars Staff Events
...
CALS
...
Lectures
Meetings
...
Roundtable
...
Dept. Functions
Bedework @ Jasig
Bedework on iPad
Bedework Mobile
http://m.rpi.edu
Architecture
Make use of standard http features Encryption, Authentication (basic) are accommodated
SOAP
More robust than REST Appropriate for SOA Based on UML or XML Schema Tools in most popular frameworks (e.g. JAXB) Operations and target defined by WSDL documents
Motivation
Many requests/inquiries from BW community, but until there was a standard BW interest dovetails with CalConnect/OASIS calendaring WS project for SmartGrid
Implementation
Implemented by CalDAV service Under sub-context defined in configuration
http://dev/bedework.org/ucaldav/calws/....
Protocols/formats
RESTful so POST/GET/PUT with request parameters XML responses Calendar data all XML
Status
Full (sans mulitget) but unexercised implementation
Case Study
UC Berkeley
Brown University
http://events.brown.edu/
Duke University
http://calendar.duke.edu/events/
University of Navarra
http://agenda.unavarra.es/
Yale University
http://calendar.yale.edu/
Q&A