The Open Document Format (ODF)
standard has been developed by a variety of organizations and
is publicly accessible. This means it can be implemented into any
system, be it open source or a closed proprietary product,without
royalties. The ODF is intended to provide an open alternative to
proprietary document formats so organizations and individuals can enjoy document portability, a common taxonomy and vendor independence.
Public
entities (e.g. federal, state and local governments) have a unique
obligation to their customers (i.e. the taxpayer) that private sector
enterprises do not. From accessibility, to availability, to archiving, public
documents must withstand a higher level of scrutiny all the while operating within the confines of strict public budgets. ODF plays a crucial role filling that requirement.
Join BostonPHP along with Tim Vaverchak (Manager of Shared Services
from the Commonwealth of MA IT Division) and Greg Rundlett (Technical
Services Manager from OASIS) discuss the Commonwealth's business reasons for deploying
ODF and the technical/PHP methodology to access, manipulate and create
ODF documents.
Reservations accepted only from Tue, Nov 28th, 2006, @12:00am to Wed, Apr 4th, 2007, @11:59pm.
Background
OASIS - http://www.oasis-open.org/home/index.php:
OASIS (Organization for the Advancement of Structured Information
Standards) is a not-for-profit, international consortium that drives
the development, convergence, and adoption of e-business standards.
The Commonwealth of MA IT Division (ITD) - http://www.mass.gov/
ITD plans to implement ODF using translator technology plugged in to
Microsoft Office, in a group of early adopter agencies, including the
Massachusetts Office on Disability, by January 1, 2007. Thereafter, ITD
plans to migrate all Executive Department agencies to compliance with
the standard, in phases, by June of 2007. These target dates are not
set in stone; they are dependent on a number of factors, including the
adoption by the OASIS standard setting organization of ODF Version 1.1
(which will address minor accessibility issues related to the format
itself), the timely delivery of completed translators by one or more of
the multiple vendors that are currently developing this technology, and
the validated accessibility of the translators themselves.