Standards compliance is the key to Bedework's success - present and future. However, standards compliance is a double-edged, possibly triple-edged, sword.
In the name of standards compliance, there are potentially useful features we have not implemented because they would not be standards-compliant and would impede interoperability. Sometimes we simply have not brought enough ingenuity to bear on the problem, but in other instances there does not appear to be a way to have our standards cake and eat it too. And sometimes, we discover that we are not purer than Caesar's wife, and we are not quite as standards compliant as we have advertised.
Standards evolve and new standards come into existence. In our relatively brief history as calendar developers, the IETF began work on RFC2245-bis, an update to RFC2445, “Internet Calendaring and Scheduling Core Object Specification (iCalendar),” and published RFC4791 “Calendaring Extensions to WebDAV (CalDAV),” all requiring changes to our source code.
In his earlier posting, Rob Abel posited that “ . . . Standards organizations are pretty much the only way to get a level playing field when it comes to new open source applications for learning “ however, that won't happen unless the open source projects/communities are active participants.” We are active members of CalConnect, the Calendaring & Scheduling Consortium, as are Mozilla, the Open Software Applications Foundation (OSAF), the Open Connector project, as well as about 20 research universities, commercial vendors and other companies. Although CalConnect is not a standards setting body itself, much of its work is devoted to standards development and interoperability testing. Active participation by both the open sourced developers and academia in these processes has benefited both these communities and the resulting standards.
- 805 reads
