You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openoffice.apache.org by bu...@apache.org on 2011/12/01 00:55:39 UTC
svn commit: r799529 [15/18] - in
/websites/staging/ooo-site/trunk/content/marketing: ooocon2005/
ooocon2005/logos/ ooocon2005/presentations/ ooocon2005/schedule/
ooocon2006/ ooocon2006/img/ ooocon2006/logos/ ooocon2006/photos/
ooocon2006/presentations/...
Added: websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/dev_abstracts.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/dev_abstracts.html (added)
+++ websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/dev_abstracts.html Wed Nov 30 23:54:05 2011
@@ -0,0 +1,463 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+ <meta content="text/html; charset=us-ascii" http-equiv="content-type" />
+ <link rel="stylesheet" type="text/css" href="schedule.css" />
+ <style type="text/css">
+ /*<![CDATA[*/
+ .abstract .header {
+ background-color: rgb(252, 179, 190) ! important;
+ padding-left: 0.5em;
+ }
+ /*]]>*/
+ </style>
+
+ <title>Developer Stream</title>
+
+
+</head>
+
+<body>
+ <div id="banner">
+ <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+ <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+ <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+ <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+ <div id="bannercenter"><br/>(incubating) | The Free and Open Productivity Suite</div>
+ </div>
+ <div id="clear"></div>
+
+ <div id="content">
+
+
+
+ <h2>Abstracts of Conference Papers - Developer Streams</h2>
+
+ <div class="abstract" name="d1" id="d1">
+ <div class="header">
+ <p class="title">Locks and Threads and Monads - OOo My</p>
+ <p class="by">Stephan Bergmann - Sun Microsystems Inc.</p>
+ </div>
+
+ <div class="content">
+ <p>Future advances in hardware performance will come from parallel execution
+ rather than faster execution. However, in order to benefit from these advances,
+ application code will need to change. Then, in what ways will OOo have to change
+ so that it will count as a productive 21st century office suite? What languages
+ will we be writing code in tomorrow, and what paradigms will we use? Will UNO
+ turn out a strategic advantage in moving forward, or will it become a burden? Is
+ the UNO threading framework a step in the right direction? Where shall we start?
+ And what has the Wizard of Oz got to do with it?</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Stephan Bergmann</strong>, by now regular presenter at OOoCon, from
+ the StarOffice/OpenOffice.org development team at Sun Hamburg</p>
+ </div>
+ <p><a href="tuesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="d2" id="d2">
+ <div class="header">
+ <p class="title">Run trhough the jungle</p>
+ <p class="by">Mathias Bauer</p>
+ </div>
+
+ <div class="content">
+ <p>OpenOffice.org is not as monolithic as it might appear sometimes. Its internal
+ architecture allows to work in one module without the necessity to change others.
+ Some modules that build the framework and architecture of OpenOffice.org have an
+ influence on the other modules and working on any higher level module as e.g. the
+ Writer module is not possibly without understanding the basic modules and how they
+ interact with the others.</p>
+
+ <p>This presentation will outline the general software architecture of OpenOffice.org
+ to enable interested developers to find their way into the code. It will also give
+ hints to further documentation.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Mathias Bauer</strong>, working on OpenOffice.org and its predecessor
+ StarOffice for 11 years now, before this working as a software developer for a
+ graphical and font software at URW University courses in chemistry, finished with
+ a doctor's degree.</p>
+ </div>
+ <p><a href="tuesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="d3" id="d3">
+ <div class="header">
+ <p class="title">Lightning Fast Startup</p>
+ <p class="by">Michael Meeks & Jan Holesovsky</p>
+ </div>
+
+ <div class="content">
+ <p>Startup time of OOo is not insignificant – everyone knows that. But
+ there are other large applications that look like starting instantly; what do
+ they do differently? Are they cheating? Or not?</p>
+
+ <p>This talk will describe the cheating techniques used by others, and also the
+ ones that we do already (early feedback – startup notification, splash,
+ etc.; re-using a running instance; preloading an instance; ...)</p>
+
+ <p>Where the cheating ends, we will talk about improvements and optimizations
+ made by Novell, including some that did not find their way to the up-stream
+ OOo yet.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Michael Meeks</strong> is a Christian and enthusiastic believer in
+ Free software. He very much enjoys working for Novell where as a member of
+ the Desktop research team he has worked on desktop infrastructure and
+ applications, particularly the CORBA, Bonobo, Nautilus and accessibility,
+ amongst other interesting things. He now works full time developing
+ OpenOffice.org. Prior to this he worked for Quantel gaining expertise in real
+ time AV editing and playback achieved with high performance focused
+ hardware / software solutions.</p>
+
+ <p><strong>Jan Holesovsky</strong>, 29 years old, married, programmer.
+ Jan is with OpenOffice.org since 2003, employed by SUSE/Novell. Previously
+ he graduated from the Charles University (2003), worked as a YaST2 developer
+ (1999-2002, also SUSE), and programmed the drawing part of KTTV, a Linux word
+ processor and a vector drawing program for lecture notes (1998-9). In
+ OpenOffice.org, he focuses on KDE integration (http://kde.openoffice.org/index.html),
+ x86-64 porting, etc.</p>
+ </div>
+ <p><a href="tuesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="d4" id="d4">
+ <div class="header">
+ <p class="title">OpenOffice.org Performance Improvements</p>
+ <p class="by">Xiaoyang Yu & Michael Leibowitz</p>
+ </div>
+
+ <div class="content">
+ <p>We looked at several factors that could help improve OpenOffice.org startup
+ performance, especially on Linux. We focused on disk sub-system-level solutions
+ to mitigate performance impact of several application-specific factors. At launch,
+ especially on cold-start, the application makes significant scattered disk accesses,
+ due to a combination of page-faults arising out of execution flow and dynamic
+ library loads interspersed with configuration reads and writes. We will therefore
+ focus on speedup techniques based on reducing the disk access penalty at startup.</p>
+
+ <p>A systemic approach of minimizing seek penalties is to arrange data blocks used
+ during application start-up in an appropriate sequence on the disk. We will briefly
+ describe our trace gathering and simulation environment for costing and optimizing
+ block order for a collection of application disk access traces. We will also discuss
+ results and experiences for a prototype reordering scheme for the ext2 filesystem.
+ We will outline the design and progress on a post-install reordering utility for
+ OpenOffice.org, and conclude by presenting some initial ideas on extending and
+ generalizing this approach into an adaptive monitoring and optimizing mechanism
+ with kernel and file-system support.</p>
+
+ <p>The second approach is a deep refactoring of configmgr using berkeleydb to,
+ in effect, coalesce configuration data into a contiguous disk block. A new backend,
+ dbbe, accesses xml blobs stored in the database, avoiding multiple file reads. We
+ will discuss our experiences creating a new backend as well as further opportunities
+ for optimizing configmgr.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Xiaoyang Yu</strong> was born in Oct, 1974, and got the master
+ degree in Computer Science from Institute of Computing Technology, Chinese
+ Academy of Sciences in 2000. Since joining Intel in 2005, he is focused on
+ disk access factors in OpenOffice.org startup. Prior to Intel, he was a project
+ manager and lead developer at Turbolinux, designing TurboHA - a high availability
+ cluster software, working on embedded systems for government projects, in
+ addition to overseeing internationalization and GUI development for the
+ Turbolinux Distribution 10.</p>
+
+ <p><strong>Michael Leibowitz</strong> is a software engineer at Intel Corporation
+ where he works on OpenOffice.org performance improvements and community
+ infrastructure. Previously he has worked in the embedded Linux system space in
+ various capacities.</p>
+ </div>
+ <p><a href="tuesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="d5" id="d5">
+ <div class="header">
+ <p class="title">Cleaning Up OOo Multi Trheading</p>
+ <p class="by">Kay Ramme</p>
+ </div>
+
+ <div class="content">
+ <p>More or less frequently people complain about OOo in respect to multi
+ threading. Either because it is complicated to implement a service, or that
+ there is only few documentation, or that the UNO API is not thread safe, or
+ that it does not scale etc.</p>
+
+ <p>The “Cleaning Up OOo Multi Threading” effort1 aims to put OOos
+ usage of multiple threads on a solid base, while simplifying the implementation
+ of thread related OOo respectively UNO code, eliminating anachronistic
+ constructs such as the Solar Mutex or the Main Thread Executor.</p>
+
+ <p>This sessions gives a brief overview over OOos current usage of threads and
+ how synchronization primitives are used to protect office code and data. It develops
+ a solution of how to simplify thread related code development and where OOo should
+ head wrt its threading architecture2. It gives a brief overview of the UNO based
+ implementation of the suggested solution, how it works and how it has been
+ applied to OOo.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Kay Ramme</strong>,
+ <ul>
+ <li>Started programming 1980 on CBM PET</li>
+ <li>Masters degree computer science, Hamburg University</li>
+ <li>Works on StarOffice since 1997</li>
+ <li>Works for Sun since 1999</li>
+ </ul>
+ </p>
+ </div>
+ <p><a href="tuesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="d6" id="d6">
+ <div class="header">
+ <p class="title">Introduction to OpenOffice.org scripting features</p>
+ <p class="by">Laurent Godard</p>
+ </div>
+
+ <div class="content">
+ <p>Openoffice.org offers a lot of scripting capabilities. A complete framework
+ and API is available to adapt and drive the office elements to your wokflow and
+ daily activities. The available languages to access this API are numerous and
+ one can start easily to develop extensions and macros with OOoBasic and Python
+ languages.</p>
+
+ <p>The session will present the different tools like the IDE, SDK and other
+ available helpers. Then some starting elements covering the first steps of
+ extensions(macros) creation in OOoBasic will be presented. Addon and Extensions
+ creation using Python will also be covered, showing the power and simplicity
+ of the pyUNO approach.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Laurent Godard</strong> is technical director of Indesko, Nuxeo division,
+ building solutions for workflows and free ECM integration (like CPS) with
+ OpenOffice.org for large companies. Involved in the OOo community for many years
+ and author of various well known tools such as DicOOo, FontOOo, OOoWikipedia ...,
+ the speaker is dedicated to macros writing in various language and known as a reference
+ regarding OOo API use. He is also the co-author of the only french book dealing with
+ OOo macros and API. He is now the leader of the Extensions project and Community
+ Contributor Representative at the Community Council.</p>
+ </div>
+ <p><a href="tuesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="d7" id="d7">
+ <div class="header">
+ <p class="title">Modular Building, splitting the build</p>
+ <p class="by">Caolán McNamara</p>
+ </div>
+
+ <div class="content">
+ <p>OpenOffice.org is a large monolithic build, and has a large output install
+ image size. One problem of this is for distributions which want to ship bugfix
+ updates to their users and customers. For most distributions the smallest
+ addressable update unit is effectively that of src.rpm. All output rpms which
+ are generated from a given src.rpm are included in the update set.</p>
+
+ <p>Other similiarly large monolithic build trees have been split into separately
+ buildable modules e.g. x.org. This enables separate src.rpms to be created, and
+ independant update builds of the afflicted src.rpms with consequently faster
+ builds for updates, and smaller update sizes. Here I outline a sample modular-build
+ split of OpenOffice.org into OpenOffice.org-URE and the rest of OpenOffice.org.</p>
+
+ <p>The target of the BOF is that by discussing the problem and a prototype sample
+ solution an understanding might be reached as to the viability to a universally
+ acceptable modular build process.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Caolán McNamara</strong> works for Red Hat, Inc. for a number of
+ years as a Desktop Engineer with overall responsibility for OpenOffice.org.
+ He has been working on OpenOffice.org for approx 6 years.</p>
+ </div>
+ <p><a href="tuesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="d8" id="d8">
+ <div class="header">
+ <p class="title">Building OO.o (faster?) with Jam</p>
+ <p class="by">Kai Backman</p>
+ </div>
+
+ <div class="content">
+ <p>A How-to presentation on the prototype Jam build system and how it can
+ reduce those convenient “go fetch coffee and take a break” moments
+ of compilation. After this session you should know how to use the prototype, why
+ to use it, and a bit about what's inside. Also inluded by popular demand:
+ “Top Ten common usage patterns that will cause the prototype to promptly
+ explode and disintegrate your planet”</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Kai Backman</strong> works on Google OO.o team and has been interested
+ in improving build times. He is a vi friendly emacs user and moonlights
+ occasonally as a game developer.</p>
+ </div>
+ <p><a href="wednesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="d9" id="d9">
+ <div class="header">
+ <p class="title">OpenOffice.org Buildbot Infrastructure</p>
+ <p class="by">Michael Leibowitz</p>
+ </div>
+
+ <div class="content">
+ <p>We will detail a new system being developed for openoffice.org, that will
+ allow automated testing of code changes and make life easier for QA.
+ This system, using build-bot, allows developers to submit their CWS or SVN
+ branch for building, testing, and install-set creation on different architectures
+ and configurations. By including performance, code-quality, and correctness tests
+ in the battery, we allow developers to track regressions across many platforms,
+ without requiring those platforms in their possession. By making install sets
+ available from the build, we enable developers to submit their changes easily,
+ even when they don't have the same platforms/build systems as QA.</p>
+
+ <p>In addition, the automated nature of the system makes running these tests
+ easy and painless. The “head” branch can also be automatically
+ tested, giving a running regression for the project as a whole. With this system,
+ we hope to make the process of making changes and getting them integrated
+ considerably less difficult for developers and QA engineers alike.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Michael Leibowitz</strong> is a software engineer at Intel
+ Corporation where he works on OpenOffice.org performance improvements and
+ community infrastructure. Previously he has worked in the embedded Linux
+ system space in various capacities.</p>
+ </div>
+ <p><a href="wednesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="d10" id="d10">
+ <div class="header">
+ <p class="title">OpenOffice.org Extensions Infrastructure: What it is - What it can - What is planned</p>
+ <p class="by">Jürgen Schmidt</p>
+ </div>
+
+ <div class="content">
+ <p>The session will give an overview of the OpenOffice.org extension infrastructure.</p>
+
+ <p>The OpenOffice.org office suite gets more and more popular and the demand to
+ customize or extend the existing functionality by own extensions is growing as well
+ to integrate it in existing business workflows. Customized extensions can provide new
+ functionality or can be the interface to other applications, e.g. integration in
+ document management systems.</p>
+
+ <p>But what are the requirements for the extensions infrastructure to provide a
+ reliable framework for deploying and maintaining extensions for several versions
+ of OpenOffice.org? Even that is important for ISV's to protect their intellectual
+ property and to make it possible to run a business based on extensions and an
+ open source product.</p>
+
+ <p>This session will try to cover this question. Requirements like licensing,
+ versioning, dependencies and others are discussed and the session will give an
+ overview of the current status and what is planned for the near future. Besides
+ the common requirements a special focus will be taken on commercial
+ extensions.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Jürgen Schmidt</strong> has worked for StarOffice for 9 years.
+ He was deeply involved in the development of the UNO component model which is
+ the foundation for the StarOffice API. Currently he is technical lead for the
+ StarOffice Software Development Kit (SDK) which is used in StarOffice and
+ OpenOffice.org. He is also the project lead of the OpenOffice.org API project.</p>
+ </div>
+ <p><a href="wednesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="d11" id="d11">
+ <div class="header">
+ <p class="title">Getting introduced to URE</p>
+ <p class="by">Cédric Bosdonnat</p>
+ </div>
+
+ <div class="content">
+ <p>Getting introduced to UNO programming and URE use is not an easy task.
+ This session is about to explain how to create a new URE application without
+ to much pain. An occasion to show the state of the Eclipse integration project,
+ this session will demonstrate the features of the plugin and expose its
+ possible future.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Cédric Bosdonnat</strong>, 22, graduated in INSA Lyon, has been
+ introduced to OpenOffice.org development during the Google Summer of Code
+ 2005. He works on an Eclipse plugin to help UNO component development. He
+ has started a UNO Component to use Gstreamer free multimedia framework from
+ OpenOffice.org</p>
+ </div>
+ <p><a href="wednesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="d12" id="d12">
+ <div class="header">
+ <p class="title">C++ development within OOo: Tricks of the trade</p>
+ <p class="by">Thorsten Behrens</p>
+ </div>
+
+ <div class="content">
+ <p>Large-scale C++ development is tough business, and so is grokking and
+ improving OOo's approximately 6 million lines of code. The author
+ will share the accumulated knowledge of Sun's OOo development team,
+ touching areas such as:
+ <ul>
+ <li>dependency management: how to architect for encapsulation</li>
+ <li>tools for working on the code: IDE/editor review, (semi)-automatic
+ code transformations and refactorings, debuggers</li>
+ <li>patterns: the most frequent design patterns and their incarnations</li>
+ <li>helpers: the what and the where of helper functionality</li>
+ <li>recommended readings: literature, links to OOo resources (API
+ documentation, coding guidelines), mailing lists and news groups</li>
+ </ul>
+ </p>
+
+ <p>This session should be suitable for all levels of C++ programmers, that want
+ to become familiar with OOo's way of doing things in C++.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Thorsten Behrens</strong>, being a programmer since ages, he
+ finished a degree in computer science, and joined Sun's StarOffice/OpenOffice
+ team shortly thereafter. Since winter 2003, he's been busy redesigning and
+ implementing OOo's new rendering and slideshow components.</p>
+ </div>
+ <p><a href="wednesday.html">Back</a></p>
+ </div>
+
+
+ </div>
+
+ <div id="footera">
+ <div id="poweredbya">
+ <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+ </div>
+ <div id="copyrighta">
+ <p>
+ Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+ Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+ decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+ not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+ yet to be fully endorsed by the ASF.</p>
+ <p>
+ <a href="/contact.html">Contact Us</a> |
+ <a href="/terms.html">Terms of Use</a>
+ <br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+ <br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+ <br />Other names appearing on the site may be trademarks of their respective owners.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/general_abstracts.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/general_abstracts.html (added)
+++ websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/general_abstracts.html Wed Nov 30 23:54:05 2011
@@ -0,0 +1,512 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+ <meta content="text/html; charset=us-ascii" http-equiv="content-type" />
+ <link rel="stylesheet" type="text/css" href="schedule.css" />
+ <style type="text/css">
+ /*<![CDATA[*/
+ .abstract .header {
+ background-color: rgb(255, 240, 181);
+ padding-left: 0.5em;
+ }
+ /*]]>*/
+</style>
+
+ <title>General streams</title>
+
+
+</head>
+
+<body>
+ <div id="banner">
+ <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+ <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+ <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+ <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+ <div id="bannercenter"><br/>(incubating) | The Free and Open Productivity Suite</div>
+ </div>
+ <div id="clear"></div>
+
+ <div id="content">
+
+
+
+ <h2>Abstracts of Conference Papers - General Streams</h2>
+
+ <div class="abstract" name="g1" id="g1">
+ <div class="header">
+ <p class="title">VBA Interoperability & OpenOffice.org</p>
+ <p class="by">Noel Power</p>
+ </div>
+ <div class="content">
+ <p>1.The Why: Describe the macro import problem, the need for a solution and the
+ potential wins in terms of Openoffice adoption.</p>
+
+ <p>2.The How: Describe the origins of the incubator project, description of
+ architecture of the solution, the type of problems encountered and what we are
+ doing and what we have to do to solve them.</p>
+
+ <p>3.The Present: Describe where we are at right now in terms of upstreaming
+ (hooks already integrated into upstream basic etc ), object Model, the approach
+ we are taking, what works right now.</p>
+
+ <p>4.The Future: Describe whats next, the main areas that don't work,
+ whats required, why it is necessary to integrate the object model and more
+ basic enhancements upstream.</p>
+
+ <p>Demo: Show some cool demos that demonstrate import of Excel macros</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Noel Power</strong>, Working as part of Novell's Openoffice
+ developement team. Responsible for improving VBA interoperability by enabling
+ Excel macros to run natively within Openoffice. Prior to joining Novell worked
+ as a Software developer with Sun, Lucent Technologies, Iona, Siemens, IBM,
+ Hewlett Packard & Motorola.</p>
+ </div>
+ <p><a href="tuesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="g2" id="g2">
+ <div class="header">
+ <p class="title">Using OpenOffice.org as a redaction tool for office automation document</>
+ <p class="by">Garnett Yeatts & Boyd Fletcher</p>
+ </div>
+
+ <div class="content">
+ <p>The United States Joint Forces Command, USJFCOM, has developed an application
+ that leverages the Open Office technologies to assist in the redaction of office
+ automation documents. Redaction is the process of securely cleansing (or preparing)
+ a document for release and sharing. The solution also provides an automated (batch)
+ mechanism to convert MS Office to ODF and redact them. The redacted documents can be
+ stored in MS Office format, ODF, or PDF.</p>
+
+ <p>Secure Save allows users to continue to use familiar tools while allowing an
+ organization to protect itself from external compromise due to malicious executable
+ code and from accidental release (leakage) of information due to unseen information
+ in documents. The Secure Save application can operate as either a OOo plugin for
+ individual document processing or as a standalone Java application for batching
+ processing. The secure save redaction options are controlled via site specific policy
+ configuration files.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Garnett Yeatts</strong> has thirteen years of experience developing and fielding custom
+ software systems. He holds a Bachelor's Degree in Computer Science from James Madison
+ University and a Master's Degree in Business Administration from Regis University.</p>
+
+ <p><strong>Boyd Fletcher</strong> started his career in IT in the banking industry in 1986 and
+ graduated in 1993 from Old Dominion University with Bachelors in Computer Science.
+ He has spend most of the last 13 years working for the Department of Defense as a
+ software developer and systems engineer. First as a contractor with a variety of companies
+ and now as a civil servant with the Dept of Navys Space and Naval Warfare Command. As
+ deputy chief engineer at the United States Joint Forces Command Joint Experimentation
+ Directorate Joint Prototype Pathways Prototype Engineering branch, Boyd is responsible
+ for software architecture design</p>
+ </div>
+ <p><a href="tuesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="g3" id="g3">
+
+ <div class="header">
+ <p class="title">Mac OS X porting : the Next Step</p>
+ <p class="by">Eric Bachard</p>
+ </div>
+
+ <div class="content">
+ <p>As starting point, a brief description of last year objectives, will be completed
+ with current status.</p>
+
+ <p>Negative points: visibility, native port speed, Apple changes, API knowledge.
+ Events how caused problems will be analysed in this part.</p>
+
+ <p>Positive points: changes, vcl documentation writing. Progress made since last year
+ will be described in this part.</p>
+
+ <p>Development: native port ( objectives, what is done, timeline, roadmap) Some more
+ “code oriented ” parts will be described in this part, including (if possible),
+ a running demonstration of changes.</p>
+
+ <p>Propositions for improve Mac OS X porting project: a short analysis will present
+ what is needed to make the project do progress in "runtime" in resources management</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Eric Bachard</strong>, contributor since 2003, is Professor of applied physics
+ in Belfort Montbeliard University of Technology, contributes as co-lead for porting project
+ in OpenOffice.org porting project, and as mentor of Pierre de Filippis for the
+ Google Summer of Code 2006.</p>
+ </div>
+ <p><a href="tuesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="g4" id="g4">
+ <div class="header">
+ <p class="title">Spreadsheet Compatibility. Forwards, Backwards ans Sideways</p>
+ <p class="by">Jody Goldberg</p>
+ </div>
+
+ <div class="content">
+ <p>Recent research into spreadsheet error rates are not enouraging (see Panko),
+ even experienced users make significant errors (off by over 5%) regularly.
+ Even slight variances in implementation between different applications and different
+ versions of applications compound the problem. Spreadsheet formulas are poor
+ documented functional programming languages. Despite the ongoing work in the
+ OpenDocument Formula subcommittee, and in Microsoft's ECMA TC45 standardization
+ effort the notion of one true standard to rule them all is a long way off.</p>
+
+ <p>This discussion will deal with the extensions necessary in spreadsheet UI and
+ file formats to offer users a familiar syntax, and to allow different implementations
+ to at least know about the differences.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Jody Goldberg</strong> (Toronto Canada) has been involved with free
+ software for more than a decade. After spending years in various investment
+ banks developing analytics and talking to MS Excel support personnel, he discovered
+ Gnumeric and the GNOME project. Novell now employs him to work on
+ OpenOffice.org's Spreadsheet during business hours, and he continues to work
+ on Gnumeric once the kids go to sleep.</p>
+ </div>
+ <p><a href="tuesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="g5" id="g5">
+
+ <div class="header">
+ <p class="title">Discovering the New Chart Module</p>
+ <p class="by">Björn Milcke & Pierre-André Galmes</p>
+ </div>
+
+ <div class="content">
+ <p>Charts are used for visualizing data sets, e.g. numbers contained in the cells
+ of a spreadsheet. There are many kinds of charts to choose from (e.g. bar
+ chart, pie chart, scatter chart). As the current chart implementation has become
+ unmaintainable over the years, the chart team has decided to redesign the chart
+ module from scratch and create a usable base for further development and integration
+ of missing features.</p>
+
+ <p>The new chart implementation is now gaining in maturity and is proving to be
+ a valuable tool. The purpose of this presentation is therefore to showcase this
+ brand new feature planned for one of the next releases. The presentation will focus
+ on the new chart as seen from two points of view: the user's (new features)
+ and the developer's (code design and API). Demos will be given to illustrate the
+ various features.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Björn Milcke</strong> graduated in Computer Science in Würzburg, Germany.
+ Working on StarOffice/OpenOffice.org Chart since 1999 (first for StarDivision then
+ for Sun Microsystems, Inc.)</p>
+ <p><strong>Pierre-André Galmes</strong> is working as a free-software consultant
+ at StarXpert in Paris since 2004. His work includes tasks like teaching to users OpenOffice.org
+ and C++ development. He recently started helping the chart team.</p>
+ </div>
+ <p><a href="tuesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="g6" id="g6">
+ <div class="header">
+ <p class="title">WordForge - localisation infrastructure for everyone</p>
+ <p class="by">Dwayne Bailey</p>
+ </div>
+
+ <div class="content">
+ <p>Localisation is hard. It's made harder because there is a high technical
+ skill requirement to implement and integrate a localisation. A good translator,
+ who is technically skilled enough to localise software, is also difficult to find.
+ Now consider all this in relation to minority languages: no skilled resources and
+ few volunteer translators. Is this a recipe for mediocre localisations or an opportunity
+ for software to help elevate quality and help us produce localisations for very small languages?</p>
+
+ <p>There are over 200 languages in Africa with more than 1 million speakers. If
+ we want to see those in OpenOffice.org we need to dramatically improve the process
+ of localisation so that we can reduce the barriers to entry.</p>
+
+ <p>The WordForge project is delivering localisation infrastructure that helps
+ localisation teams effectively manage their localisations by ensuring good process
+ and by imporoving quality through glossary management and translation reuse.</p>
+
+ <p>WordForge is focused on using the localisation formats developed by the localisation
+ industry including XLIFF, TMX and TBX. These standardised localisation formats add
+ large amounts of value to FOSS projects and translation teams, through the embeding and
+ managment of the localisation process, terminology and translation memory. WordForge's
+ existing translation management system, Pootle, is being extending to manage XLIFF files.
+ The present PO format does not allow effectively allow for this information to be
+ delivered to localisers.</p>
+
+ <p>WordForge builds on the existing Translate Toolkit used by most OpenOffice.org
+ localisers and enhances the existing Pootle Translation Management Software. These
+ are real tools being expanded and enhanced by real localisers so that we can deliver
+ OpenOffice.org in many more languages.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Dwayne Bailey</strong> started Translate.org.za which has translated
+ OpenOffice.org into the 11 official languages of South Africa. This effort has played no small part in
+ getting Microsoft to localise into 3 South African languages. He is part of the
+ team that built the oo2po convertor used by most OpenOffice.org localisation teams. Dwayne,
+ together with Javier Sola from the KhmerOS team, founded the WordForge project as a means
+ to help improve the quality of localisations as well as to help more minority languages
+ translate FOSS.</p>
+ </div>
+ <p><a href="tuesday.html">Back</a></p>
+ </div>
+
+
+ <div class="abstract" name="g6bis" id="g6bis">
+ <div class="header">
+ <p class="title">OpenOffice.org / RedOffice in China</p>
+ <p class="by">Cai Hong Hu</p>
+ </div>
+
+ <div class="content">
+ <p>This session is about how Beijing Bedflag Chinese 2000 Co. LTD., worked
+ hard to develop OpenOffice.org into a product RedOffice that would suit the
+ needs of Chinese business, including debugging OpenOffice.org, localizing the
+ information, Chinese typesetting, and developing lots of new fonctions for
+ the chinese customer.</p>
+
+ <p>RedOffice has been excellent in government purchase from 2002 to now and its
+ bid-winning ratio is more than 30%. Until now, RedOffice products have spread over
+ more than twenty provinces and be widely used in various industries such as Water
+ Resource, Electrical Power, Tobacco, Mining, Iron and Steel Industry, etc.</p>
+
+ <p>As an OpenOffice.org based software, RedOffice has a big market in China. Beijing
+ Redflag Chinese 2000 Co. LTD. helps to get support from China authority to support ODF
+ format in he passed ISO standard vote.</p>
+ </div>
+ <p><a href="tuesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="g7" id="g7">
+ <div class="header">
+ <p class="title">OOo Documentation - Online Help and Beyond</p>
+ <p class="by">Frank Peters & Uwe Fischer</p>
+ </div>
+
+ <div class="content">
+ <p>This session will deal with multiple aspects of the OOo help system, and
+ documentation in general. It will encompass technological aspects, such as an
+ overview of OOo help system, information on how to write, modify, and build help,
+ how to localize or extend help. Common pitfalls when working with the help sources
+ will also be addressed. Further discussion will focus on community collaboration
+ aspects where the relation between the Sun-based help authors and the documentation
+ community will be discussed with the goal of highlighting existing and potential
+ collaboration paths and tools. Finally, we will try to collect ideas about the future
+ of OOo documentation and help, such as consolidation of documentation formats and the
+ feasibility of alternative delivery vehicles.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Uwe Fischer</strong> is a technical writer for StarOffice since 1995 and
+ has suffered from many team leads that gave different directions over time, yet
+ survived them all. He is a living fossil that proves that learning by doing can easily
+ lead nowhere.</p>
+
+ <p><strong>Frank Peters</strong> is working on OOo and StarOffice documentation since
+ 2001 and is one of the many team leads that gave Uwe different directions. He worked
+ on implementing the help xml format and tools around it and helped making the help a
+ proper component in the product release process.</p>
+ </div>
+ <p><a href="tuesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="g8" id="g8">
+ <div class="header">
+ <p class="title">Getting started with Automated GUI Testing - The VCL TestTool Application</p>
+ <p class="by">Thorsten Bosbach</p>
+ </div>
+
+ <div class="content">
+ <p>The VCL TestTool Application is used to test the functionality which is
+ available via the graphical user interface of OpenOffice.org.</p>
+ <p>Step by step hands on session:
+ <ul>
+ <li>Where is the VCL TestTool Application?</li>
+ <li>Where are the test scripts?</li>
+ <li>What steps are needed on using the VCL TestTool Application for the first time?</li>
+ </ul>
+ </p>
+
+ <p>The test scripts make sure that the general functions of OOo are available
+ and working. Automated testing makes it easy to check if OOo behaves
+ equaly on different platforms and languages with a minimum manual effort.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Thorsten Bosbach</strong> is working at Sun Microsystems the last 6 years as
+ Quality Assurance Engineer in the StarOffice group, developing automated
+ GUI test scripts.</p>
+ </div>
+ <p><a href="wednesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="g9" id="g9">
+ <div class="header">
+ <p class="title">Developing and improving OpenOffice.org dictionaries</p>
+ <p class="by">Németh László</p>
+ </div>
+
+ <div class="content">
+ <p>Overview of new features in OpenOffice.org spell checker, hyphenator and
+ thesaurus; and a practical guide to developing (much better) dictionaries for
+ these tools:</p>
+
+ <ul>
+ <li>(semi)automated spell checking dictionary development (making,
+ extending and verifying spell checking dictionaries, developing affix
+ files for morphologically complex languages)</li>
+
+ <li>using Hunspell (alias compression, complex prefixes for right-to-left
+ agglutinative languages, compound word support, pattern recognition for
+ numbers and number+letter combinations, forbidding taboo word suggestions etc.)</li>
+
+ <li>making Unicode spell checking dictionaries, hyphenation patterns
+ and thesauri (not only for exotic writing systems)</li>
+
+ <li>developing hyphenation patterns with discretionary and compound
+ word hyphenation support (need for Dutch, German, Hungarian, Norwegian,
+ Swedish etc.)</li>
+
+ <li>handling morphological data for automatic stemming and affixation in thesaurus</li>
+ <li>moving to the standard writing (case study: supporting ligatures in French)</li>
+ <li>developing state-of-the-art language tools (case study: Hungarian
+ spell checking and hyphenation)</li>
+ </div>
+
+ <div class="bio">
+ <p><strong>Németh László</strong>, member of the Lingucomponent and
+ Hungarian language projects. Developed Unicode, compound word, morphological analysing
+ and agglutinative language support to OpenOffice.org Myspell spell checker (now Hunspell), and the
+ automatic discretionary and Unicode hyphenation patch to OpenOffice.org
+ AltLinux Libhnj hyphenator. Author of the Hungarian spell checking dictionary.
+ Lingucomponent co-lead.</p>
+ </div>
+ <p><a href="wednesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="g10" id="g10">
+ <div class="header">
+ <p class="title">GStreamer in OpenOffice.org</p>
+ <p class="by">Cédric Bosdonnat & Radek Doulík</p>
+ </div>
+
+ <div class="content">
+ <p>This session will introduce the GStreamer media handling library and
+ its use in the OpenOffice.org. The talk will present the integration process
+ and the encountered problems as well as the work already done. It will also
+ mention possible future work in this area.</p>
+
+ <p>The GStreamer integration includes these parts:
+ <ul>
+ <li>Enhancing media support in OpenOffice.org on Linux</li>
+ <li>Using the GStreamer framework to play multimedia files and streams</li>
+ <li>Creating macros handling GStreamer</li>
+ </ul>
+ </p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Cédric Bosdonnat</strong>, 22, graduated in INSA Lyon, has been
+ introduced to OpenOffice.org development during the Google Summer of Code 2005.
+ He works on an Eclipse plugin to help UNO component development. He has started
+ a UNO Component to use GStreamer free multimedia framework from OpenOffice.org.</p>
+
+ <p><strong>Radek Doulík</strong>, 31, Graduated on Charles University in Prague, Worked
+ 6 years for Helixcode/Ximian/Novell in the Evolution project team. Today working
+ in the Open Office team, mainly on cairo canvas and Impress.</p>
+ </div>
+ <p><a href="wednesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="g11" id="g11">
+ <div class="header">
+ <p class="title">Moving OOo to XCanvas, Step 2 - Draw and Impress</p>
+ <p class="by">Thorsten Behrens</p>
+ </div>
+
+ <div class="content">
+ <p>After having sucessfully converted the Impress slideshow to the new UNO
+ XCanvas rendering framework for OOo2.0, the next step in moving the whole
+ office suite to canvas-based rendering is the port of Draw and Impress</p>
+
+ <p>This talk will show-case a working prototype of Impress, already rendering
+ the main edit view via XCanvas, displaying nicely anti-aliased graphics and
+ using the hardware-accelerated canvas sprite primitives while manipulating shapes.</p>
+
+ <p>Furthermore, and overview is given about the underlying architectural rework
+ of the Impress drawing layer, which is now based on true MVC. Additionally,
+ the engine then offers an extensible display list of shape primitives, which
+ facilitates transparent switching of the rendering subsystem.</p>
+
+ <p>The session concludes with an outlook on the port of Calc and Writer, and
+ the obstacles that have to be overcome beforehand.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Thorsten Behrens</strong>, being a programmer since ages, he finished
+ a degree in computer science, and joined Sun's StarOffice/OpenOffice team
+ shortly thereafter. Since winter 2003, he's been busy redesigning and
+ implementing OOo's new rendering and slideshow components.</p>
+ </div>
+ <p><a href="wednesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="g12" id="g12">
+ <div class="header">
+ <p class="title">OpenOffice.org and GNU/Linux distributions</p>
+ <p class="by">René Engelhard</p>
+ </div>
+
+ <div class="content">
+ <p>OpenOffice.org increasingly gets common and increasingly gets included
+ in GNU/Linux dustibutions. Unfortunately the working relationship with the
+ free software community at large and especially the GNU/Linux distributions
+ is not always as optimal as it can and there often are some stones in the
+ way for them when trying to package OpenOffice.org optimally.</p>
+
+ <p>This Talk is intended to show those up and maybe to search ways for a
+ better working relationship in the future.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>René Engelhard</strong>, during his (aborted) studies of CS
+ at the University of Dortmund, Germany, he came in contact with Linux and
+ Free Software and not long after it joined the Debian Project. There he then
+ participated in the initial OpenOffice.org packaging efforts and now is
+ one of the two Debian OpenOffice.org Maintainers.</p>
+ </div>
+ <p><a href="wednesday.html">Back</a></p>
+ </div>
+
+
+ </div>
+
+ <div id="footera">
+ <div id="poweredbya">
+ <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+ </div>
+ <div id="copyrighta">
+ <p>
+ Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+ Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+ decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+ not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+ yet to be fully endorsed by the ASF.</p>
+ <p>
+ <a href="/contact.html">Contact Us</a> |
+ <a href="/terms.html">Terms of Use</a>
+ <br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+ <br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+ <br />Other names appearing on the site may be trademarks of their respective owners.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/keynotes_abstracts.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/keynotes_abstracts.html (added)
+++ websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/keynotes_abstracts.html Wed Nov 30 23:54:05 2011
@@ -0,0 +1,178 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+ <meta content="text/html; charset=us-ascii" http-equiv="content-type" />
+ <link rel="stylesheet" type="text/css" href="schedule.css" />
+ <style type="text/css">
+ /*<![CDATA[*/
+ .abstract .header {
+ border: thin solid black;
+ padding-left: 0.5em;
+ }
+
+ /*]]>*/
+</style>
+
+ <title>Keynotes</title>
+
+
+</head>
+
+<body>
+ <div id="banner">
+ <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+ <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+ <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+ <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+ <div id="bannercenter"><br/>(incubating) | The Free and Open Productivity Suite</div>
+ </div>
+ <div id="clear"></div>
+
+ <div id="content">
+
+
+
+ <h2>Abstracts of Conference Papers - Keynotes</h2>
+
+ <div class="abstract" name="k1" id="k1">
+ <div class="header">
+ <p class="title">The Novell migration to OpenOffice.org</p>
+ <p class="by">Debra Anderson</p>
+ </div>
+
+ <div class="content">
+ <p> Debra Anderson Novell's CIO will speak about Novell's experience adopting
+ OpenOffice.org, the importance of Open Source to the company and how it has
+ transformed the business within IT.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Debra Anderson</strong>, Appointed Chief Information Officer
+ in 2002, oversees Novell's Information Services & Technology Group.
+ Her responsibilities include the deployment of strategic
+ business information systems globally, driving Novell's open source adoption
+ in-house, providing internal company technical support and developing,
+ implementing and managing Novell's IT services. As the first user of Novell's
+ technologies, Debra regularly provides input into Novell's technical direction
+ and insight and recommendations to customers deploying Novell's open source
+ and identity offerings.</p>
+
+ <p>Prior to joining Novell, Debra spent 18 years in grocery retailing with
+ Lucky Stores, American Stores and Albertsons, holding both IT and general
+ business positions.</p>
+
+ <p>Debra holds a BA Degree in Computer Science from the State University
+ of New York at Potsdam.</p>
+
+ <p>Novell delivers Software for the Open Enterprise. With more than 50,000
+ customers in 43 countries, Novell helps customers manage, simplify, secure
+ and integrate their technology environments by leveraging best-of-breed, open
+ standards-based software. With more than 20 years of experience, 4,700 employees,
+ 5,000 partners and support centers around the world, Novell helps customers
+ gain control over their IT operating environments while reducing costs. More
+ information about Novell can be found at http://www.novell.com.</p>
+ </div>
+ <p><a href="tuesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="k2" id="k2">
+ <div class="header">
+ <p class="title">Google Summer of Code</p>
+ <p class="by">Zaheda Bhorat</p>
+ </div>
+
+ <div class="content">
+ <p>Zaheda Bhorat, Open Source Program Manager at Google, will explain the
+ importance of the Google 's Summer of code and why you should join.</p>
+ </div>
+
+ <p><a href="tuesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="k3" id="k3">
+ <div class="header">
+ <p class="title">OpenDocument, Open Revolution</p>
+ <p class="by">E. Gutentag & Bob Sutor & Nathaniel Borenstein & Charles-H.Schulz</p>
+ </div>
+
+ <div class="content">
+ <p>A one hour panel discussion on the merits of OpenDocument Format.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Eduardo Gutentag</strong> has been involved in the SGML/XML
+ world for over 10 years, and has participated in many SGML/XML related
+ activities at W3C and OASIS (even when it was still called SGML Open),
+ as well as at ebXML. He is currently a Senior Staff Engineer at the Web
+ Technology and Standards organization of Sun Microsystems. He is Sun's
+ W3C AC representative, and an elected member of the OASIS Technical
+ Advisory Board. In the UBL group, he participates in the Naming and
+ Design Rules subcommittee, and is the editor and chair of the Context
+ Methodology subcommittee.</p>
+
+ <p><strong>Bob Sutor</strong>, Vice President Standards & Open Source,
+ IBM Corporation, Executive responsible for driving and executing the
+ cross-company business and technical strategy for open standards and open
+ source as they relate to software, hardware, services, vertical industries,
+ and emerging markets. In particular, helps move IBM from its traditional
+ technical and intellectual property approach to one where business exploitation
+ of standards and open source for greater customer value is paramount, especially
+ in vertical industries and emerging markets. Chairman of the IBM internal
+ Corporate Standards Advisory Committee and the Open Source Steering Committee.
+ Works with partners, customers, government leaders and government agencies
+ around the world to understand and adopt modern, business-savvy open strategies
+ and policies. Leads the IBM team accelerating the adoption of the OASIS and ISO
+ OpenDocument Format standard. Senior IBM spokesperson and evangelist for
+ standards and open source, and a widely quoted and read global expert on
+ these areas and Service Oriented Architecture (SOA).
+ Cofounder of the OpenDocument Format Alliance.</p>
+
+ <p><strong>Dr. Nathaniel S. Borenstein</strong> is a Distinguished Engineer
+ with IBM Lotus Division, working on Internet standards and strategy and
+ overseeing the Lotus research program. He is also the President of Computer
+ Professionals for Social Responsibility, and a part time research faculty
+ member at the School of Information of the University of Michigan.
+ He has been an Internet user, developer, standardizer, entrepreneur, and
+ social activist since 1980.
+ His credits include the MIME standard, the Andrew Mail System, the metamail
+ software, the Safe-Tcl programming language, "Programming as if People Mattered"
+ and two other books, three patents, the startups First Virtual Holdings and
+ NetPOS.com, and the "One Planet, One Net" manifesto.</p>
+
+ <p><strong>Charles-H.Schulz</strong> is the Lead of the Native-Language
+ Confederation of OpenOffice.org, and a partner of the Ars Aperta Consulting
+ Group. A member of both OASIS' ODF Adoption and Technical Committees, he will
+ be chairing the panel discussion and also representing OpenOffice.org.</p>
+ </div>
+ <p><a href="wednesday.html">Back</a></p>
+ </div>
+
+
+ </div>
+
+ <div id="footera">
+ <div id="poweredbya">
+ <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+ </div>
+ <div id="copyrighta">
+ <p>
+ Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+ Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+ decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+ not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+ yet to be fully endorsed by the ASF.</p>
+ <p>
+ <a href="/contact.html">Contact Us</a> |
+ <a href="/terms.html">Terms of Use</a>
+ <br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+ <br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+ <br />Other names appearing on the site may be trademarks of their respective owners.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/monday.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/monday.html (added)
+++ websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/monday.html Wed Nov 30 23:54:05 2011
@@ -0,0 +1,207 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+ <meta http-equiv="CONTENT-TYPE" content="text/html; charset=us-ascii" />
+
+
+
+
+ <title>OOoConf 2006 Monday September 11th 2006</title><!-- Include the common CSS stylesheet --><link rel="stylesheet" type="text/css" href="../default.css" />
+ <link rel="stylesheet" type="text/css" href="schedule.css" />
+
+</head>
+
+<body>
+ <div id="banner">
+ <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+ <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+ <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+ <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+ <div id="bannercenter"><br/>(incubating) | The Free and Open Productivity Suite</div>
+ </div>
+ <div id="clear"></div>
+
+ <div id="content">
+
+
+
+
+<div id="content">
+
+ <div id="logo">
+ <a href="/conference/index.html">
+ <img style="border: 0px solid ;" src="../OOoConLyon.png" alt="OpenOffice.org Conferences logo" />
+ </a>
+ </div>
+
+ <div id="title">
+ <h3>OpenOffice.org Conference (OOoCon 2006)</h3>
+ <p>Monday September 11th 2006 – Programme</p>
+ </div>
+
+ <table class="timetable" summary="Programme">
+ <tbody>
+ <tr>
+ <td class="timebox">
+ 9:00 - 11:00
+ </td>
+
+ <td class="sessionbox">
+ Community Council Meeting
+ </td>
+
+ <td class="sessionbox">
+ </td>
+
+ <td class="sessionbox">
+ </td>
+ </tr>
+
+ <tr>
+ <td class="timebox">
+ 11:00 - 12:00
+ </td>
+
+ <td colspan="1" rowspan="2" class="sessionbox"><br />Engineering Steering Committee Meeting
+
+ </td>
+
+ <td class="sessionbox">
+ </td>
+
+ <td class="sessionbox">
+ </td>
+ </tr>
+
+ <tr><td class="timebox">
+ 12:00 - 13:00
+ </td>
+ <td class="sessionbox">
+ Marketing Project Meeting
+ <span class="links">
+ <a href="monday_abstracts.html#c1"><img src="abstract.gif" alt="abstract" /></a>
+ </span>
+ </td>
+
+ <td class="breakbox" colspan="4">
+ Break
+ </td>
+ </tr>
+
+ <tr>
+ <td class="timebox">
+ 14:00 - 16:00
+ </td>
+
+ <td class="sessionbox">
+ Extensions Project meeting
+ <span class="links">
+ <a href="monday_abstracts.html#a1"><img src="abstract.gif" alt="abstract" /></a>
+ </span>
+ </td>
+
+ <td class="sessionbox">
+ OpenOffice.org QA Project meeting
+ <span class="links">
+ <a href="monday_abstracts.html#a2"><img src="abstract.gif" alt="abstract" /></a>
+ <a href="../presentations/monday_a2.odp">
+ <img src="../impress.png" alt="presentation (.odp)" title="presentation (.odp)" /></a>
+ <a href="../presentations/monday_a2.pdf">
+ <img src="../pdf.gif" alt="presentation (.pdf)" title="presentation (.pdf)" /></a>
+ </span>
+ </td>
+
+ <td class="sessionbox">
+ Release Planning Meeting
+ </td>
+ </tr>
+
+ <tr>
+ <td class="breakbox" colspan="4">
+ Break
+ </td>
+ </tr>
+
+ <tr>
+ <td class="timebox">
+ 17:00 - 19:00
+ </td>
+
+ <td class="sessionbox">
+ NLC Meeting
+ </td>
+
+ <td class="sessionbox">
+ </td>
+
+ <td class="sessionbox">
+ </td>
+ </tr>
+
+ <tr>
+ <td class="timebox">
+ 20:00 -
+ </td>
+
+ <td class="partybox" colspan="3">
+ NLC Party
+ </td>
+ </tr>
+ </tbody>
+ </table>
+
+ <p style="font-style: italic;">Please note this Programme is provisional and may change without notice</p>
+
+</div>
+
+
+<!-- Right menu -->
+<div id="menu">
+
+ <h3>What is OOoCon</h3>
+ <p><a href="../index.html">Home</a></p>
+ <h3>How to participate</h3>
+ <p><a href="../sponsorship.html">Sponsors</a></p>
+ <p><a href="../registration.html">Registration</a></p>
+ <h3>Travel informations</h3>
+ <p><a href="../travel.html">Travel</a></p>
+ <p><a href="../accommodation.html">Accommodation</a></p>
+ <p><a href="../map.html">Map</a></p>
+ <h3>Programme</h3>
+ <p><a href="../schedule.html">Overview</a></p>
+ <p>Monday</p>
+ <p><a href="tuesday.html">Tuesday</a></p>
+ <p><a href="wednesday.html">Wednesday</a></p>
+</div>
+
+
+
+
+ </div>
+
+ <div id="footera">
+ <div id="poweredbya">
+ <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+ </div>
+ <div id="copyrighta">
+ <p>
+ Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+ Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+ decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+ not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+ yet to be fully endorsed by the ASF.</p>
+ <p>
+ <a href="/contact.html">Contact Us</a> |
+ <a href="/terms.html">Terms of Use</a>
+ <br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+ <br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+ <br />Other names appearing on the site may be trademarks of their respective owners.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/monday_abstracts.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/monday_abstracts.html (added)
+++ websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/monday_abstracts.html Wed Nov 30 23:54:05 2011
@@ -0,0 +1,152 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+ <meta content="text/html; charset=us-ascii" http-equiv="content-type" /><title>OOoCon2006
+- Monday abstracts</title>
+<style type="text/css">
+/*<![CDATA[*/
+h3 { background-color: rgb(255, 255, 102) ! important;
+color: rgb(0, 0, 0);
+}
+/*]]>*/
+</style>
+
+</head>
+
+<body>
+ <div id="banner">
+ <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+ <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+ <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+ <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+ <div id="bannercenter"><br/>(incubating) | The Free and Open Productivity Suite</div>
+ </div>
+ <div id="clear"></div>
+
+ <div id="content">
+
+
+ Abstract of Third
+party meetings</h2> <h3><a name="a1"></a>Extensions
+project meeting</h3> <table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody> <tr>
+<td><span style="font-style: italic;">Laurent Godard
+- Nuxeo - Indesko division</span></td> </tr> <tr>
+<td> <p style="margin-bottom: 0cm;">The Extensions
+project has been proposed last year at Koper and been setup some month
+later. Valuable work occured and the wiki is up and starts to be filled.</p>
+<p style="margin-bottom: 0cm;">The proposed meeting will
+cover the following points, involving all participants</p> <ul>
+<li> <p style="margin-bottom: 0cm;">State of the
+project</p> </li> </ul> <ul> <li> <p style="margin-bottom: 0cm;">Started work : what is currently
+developped (especially in Hamburg) ?</p> <p style="margin-bottom: 0cm;">When will it be ready ? Do we
+have to wait or should we propose an intermediate solution ...</p>
+</li> <li> <p style="margin-bottom: 0cm;">Express
+and formalize the needs : Help mechanism, new UNO controls (treeview),
+deployement of addons at installation time ...</p> </li> <li>
+<p style="margin-bottom: 0cm;">Translations : pages of the
+wiki are in english. Is the translation mechanism proposed sufficient ?</p>
+</li> <li> <p style="margin-bottom: 0cm;">Pending
+projects : prebuilt wizards, Extension Translation framework</p> </li>
+<li> <p style="margin-bottom: 0cm;">Volunteers
+questions regarding the organization of the project</p> </li>
+<li> <p style="margin-bottom: 0cm;">Proposal :
+organize an annual developpers meeting (coding sprint) to push
+particular aspects of the project (installer, pre-built wizards,
+Extension translation framework, documentations and starting guides ...
+)</p> </li> <li> <p style="margin-bottom: 0cm;">Any
+point and discussion regarding Extensions project</p> </li>
+</ul> <p style="margin-bottom: 0cm;">All the point
+discussed will be recorded and a synthesis of all discussion will be
+relayed to involved project (Framework, installer, l10n ...) </p>
+</td> </tr> <tr style="font-style: italic;"><td><p>The
+speaker is technical director of Indesko,
+Nuxeo division, building solutions for workflows and free ECM
+integration (like CPS) with OpenOffice.org for large companies.
+Involved in the OOo community for many years and author of various well
+known tools such as DicOOo, FontOOo, OOoWikipedia ..., the speaker is
+dedicated to macros writing in various language and known as a
+reference regarding OOo API use. He is also the co-author of the only
+french book dealing with OOo macros and API. He is now the leader of
+the Extensions project and Community Contributor Representative at the
+Community Council.</p> </td> </tr> </tbody> </table>
+<a href="monday.html">Back</a><br /> <h3><a name="a2"></a>OpenOffice.org QA Project (bug hunting
+party)</h3> <table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody>
+<tr> <td><span style="font-style: italic;">Joost
+Andrae - Sun Microsystems GmbH</span></td> </tr> <tr>
+<td> <p style="margin-bottom: 0cm;">This session
+gives information about the QA project and about it's work</p> </td>
+</tr> <tr> <td> <p>After starting at a
+company where I learned a lot about data processing I worked as
+Informix 4GL programmer at several companies. After making my degree as
+a merchant of data processing I went to StarDivision (1995) where I
+started as QA engineer for Calc and Chart as well as Math and server
+based products like Sun ONE Webtop. Nowadays I'm working as StarOffice
+Program Manager within the StarOffice development team in Hamburg. As a
+co-lead of the OpenOffice.org QA project I help to coordinate all
+activities and additionally I test (QA) , upload and announce
+OpenOffice.org builds.</p> </td> </tr> </tbody>
+</table><a href="monday.html">Back</a><br />
+<a href="monday.html">Back</a><br /> <h3 style="background-color: rgb(182, 198, 224) ! important;"><a name="c1"></a>OpenOffice.org
+Marketing Project</h3>
+<table style="text-align: left; width: 100%;" border="1" cellpadding="2" cellspacing="2"> <tbody><tr><td><span style="font-style: italic;"><a href="http://www.mealldubh.org">John
+McCreesh</a> - <a href="http://marketing.openoffice.org">Marketing
+Project</a> Lead</span></td></tr>
+<tr><td><p style="font-style: italic;">This
+session is open to MarCons and other interested and active members
+of the Marketing Project.
+</p><p>If you are planning to attend, please come prepared
+to share with
+others your experience of marketing OOo in the last twelve months.
+Tell us the things that worked well for you, and the things that did
+not :-)
+Please bring along any examples of marketing collateral you have
+produced
+(flyers, posters, newspaper / magazine articles...).
+</p><p>Looking at <a href="http://wiki.services.openoffice.org/wiki/Strategic_Marketing_Plan#Marketing_Project">our
+organisation</a>,
+there will be a discussion on the most effective way to organise
+the project going forward. Is our present MarCon based structure the
+best one? if so, how can
+we find and empower good MarCons - what support do they need from the
+wider community?
+How do MarCons fit in with the work of Native-Language Projects?
+</p><p>On the campaigns side, how well has the 'Why?'
+campaign worked for you?
+Please
+bring your suggestions for more counter-marketing activities like <a href="http://why.openoffice.org/getlegal.html">"Get Legal"</a>
+and <a href="http://why.openoffice.org/keepthecar.html">"Keep
+the Car"</a>.
+</p><p>If there's time, we'll also have a very quick look
+at the <a href="http://wiki.services.openoffice.org/wiki/Strategic_Marketing_Plan">Marketing
+Strategy</a>.
+Is it still valid? In particular, are the target markets still the
+right ones?</p></td></tr></tbody></table><a href="monday.html">Back</a><br />
+
+
+ </div>
+
+ <div id="footera">
+ <div id="poweredbya">
+ <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+ </div>
+ <div id="copyrighta">
+ <p>
+ Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+ Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+ decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+ not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+ yet to be fully endorsed by the ASF.</p>
+ <p>
+ <a href="/contact.html">Contact Us</a> |
+ <a href="/terms.html">Terms of Use</a>
+ <br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+ <br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+ <br />Other names appearing on the site may be trademarks of their respective owners.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/odf_abstracts.html
==============================================================================
--- websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/odf_abstracts.html (added)
+++ websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/odf_abstracts.html Wed Nov 30 23:54:05 2011
@@ -0,0 +1,215 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link href="/css/ooo.css" rel="stylesheet" type="text/css">
+
+
+ <meta content="text/html; charset=us-ascii" http-equiv="content-type" />
+ <link rel="stylesheet" type="text/css" href="schedule.css" />
+ <style type="text/css">
+ /*<![CDATA[*/
+ .abstract .header {
+ background-color: rgb(200, 231, 190) ! important;
+ padding-left: 0.5em;
+ }
+ /*]]>*/
+ </style>
+
+ <title>ODF Streams</title>
+
+
+</head>
+
+<body>
+ <div id="banner">
+ <div id="bannerleft"><a alt="Apache OpenOffice.org (incubating)" href="/">
+ <img id="ooo-logo alt="Apache OpenOffice.org (Incubating)" src="/images/ooo-logo.png"/></a></div>
+ <div id="bannerright"><a alt="Apache Incubator" href="http://incubator.apache.org">
+ <img id="asf-logo" alt="Apache Incubator" src="/images/apache-incubator-logo.png"/></a></div>
+ <div id="bannercenter"><br/>(incubating) | The Free and Open Productivity Suite</div>
+ </div>
+ <div id="clear"></div>
+
+ <div id="content">
+
+
+
+ <h2>Abstracts of Conference Papers - ODF Streams</h2>
+
+ <div class="abstract" name="o1" id="o1">
+ <div class="header">
+ <p class="title">XML based filters in OpenOffice.org</p>
+ <p class="by">Svante Schubert</p>
+ </div>
+
+ <div class="content">
+ <p>The editing of XML content with OpenOffice.org is a frequent requested task
+ of users. But to be able to edit solely the content and not the XML as a simple
+ textfile, a filter has to be established.</p>
+
+ <p>This session should give a quick overview over the existing functionality
+ OpenOffice.org offers to establish such a filter, giving powerful examples.
+ But also giving scenarios showing the current limitations to finally offer
+ ideas to the community to broaden the functionality.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Svante Schubert</strong> works for Sun Microsystems and has been
+ full-time developer for OpenOffice.org since its foundation. His responsibilities
+ included the development of the XSL stylesheets for the XHTML1.0 export filter.
+ He is now co-lead of the 'XML project' on OpenOffice.org</p>
+ </div>
+ <p><a href="wednesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="o2" id="o2">
+ <div class="header">
+ <p class="title">OpenDocument/ISO/IEC 26300: The Present and the Future</p>
+ <p class="by">Michael Brauer</p>
+ </div>
+
+ <div class="content">
+ <p>The “OASIS Open Document Format for Office Applications (OpenDocument)
+ ” (also known as ODF) was recently approved as ISO and IEC International
+ Standard ISO/IEC 26300, and its adoption is accelerating day by day.</p>
+
+ <p>This presentation provides an overview of recent development in the OpenDocument
+ space. It is divided into two parts. In the first part. it provides an inside
+ into the work of the OpenDocument TC in the last two years. It introduces the
+ charters and work programs of the new Accessibilty, Formula and Metadata subcommittees
+ and reveals what the future plans of the TC and its subcommittees for OpenDocument are.</p>
+
+ <p>In the second part, the presentation throws a glance on the adoption of
+ OpenDocument. It shows which national and local public bodies have already
+ adopted OpenDocument, and where an adoption is in progress. The second part
+ further introduces organizations and groups that provide assistance to parties
+ that are interested in adopting OpenDocument and lists resources that provide
+ further information regarding OpenDocument.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Michael Brauer</strong> is a Technical Architect in the
+ StarOffice/OpenOffice.org development team at Sun Microsystems, Inc. ,
+ focusing on XML technologies. He is also the chair of the OASIS
+ Open Document Format for Office Applications (OpenDocument) Technical
+ Committee. He joined the StarOffice/OpenOffice.org development team in
+ 1995, and is the lead of the OpenOffice.org XML Project that developed
+ the OpenOffice.org XML file format since its formation in 2000.</p>
+ </div>
+ <p><a href="wednesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="o3" id="o3">
+ <div class="header">
+ <p class="title">A Technical Comparison: ISO/IEC 26300 vs Microsoft
+ Office Open XML (Ecma International TC45 OOXML WD 1.3)</p>
+ <p class="by">Robert Weir</p>
+ </div>
+
+ <div class="content">
+ <p>Two XML office file formats have been pressing upon our attention,
+ the OASIS OpenDocument Format, recently standardized by ISO, and the
+ Draft Ecma Office Open XML. This presentation will review history
+ of each, the process that created them, and examine each format to
+ compare and contrast how they deal with issues such extensibility,
+ modularization, expressivity, performance, reuse of standards,
+ programability, ease of use, and application/OS neutrality.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Rob Weir</strong> is a 16 veteran of IBM and Lotus Development
+ corporation. He has extensive experience working with office file formats,
+ from the old binary formats in Lotus SmartSuite and Microsoft Office, to
+ the new generation of XML formats undergoing standardization. He is a
+ member of the OASIS ODF TC and INCITS V1.</p>
+ </div>
+ <p><a href="wednesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="o4" id="o4">
+ <div class="header">
+ <p class="title">OpenOffice.org and ODF Accessibility</p>
+ <p class="by">Malte Timmermann</p>
+ </div>
+
+ <div class="content">
+ <p>All about OpenOffice.org and ODF Accessibility. Information about Accessibility
+ features inside OpenOffice.org, like scheming, support for Assistive Technology (AT)
+ and some special and unique features.</p>
+
+ <p>Some overview about how support for AT is done. As a member of OASIS OpenDocument
+ Accessibility SC, I give an overview about of ODF Accessibility findings, and some
+ future outlook. Some information about what's going on with OOo and ODF
+ around the world (Massachusetts, ...)</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Malte Timmermann</strong>, graduated in Computer Science in 1994. Working
+ in StarOffice Development since 1991.</p>
+ </div>
+ <p><a href="wednesday.html">Back</a></p>
+ </div>
+
+ <div class="abstract" name="o5" id="o5">
+ <div class="header">
+ <p class="title">Innovation Opportunities with ODF XML</p>
+ <p class="by">Douglas Heintzman</p>
+ </div>
+
+ <div class="content">
+ <p>Today, the ODF XML technology standard for document data is most closely
+ associated with office application suites that provide an alternative to
+ MS-Office. But ODF as an XML technology opens the gates for new programmatic
+ access to the document data held within. Previously, the value of document
+ data was by and large unrealized due to the closed nature of today’s
+ predominant office application suite. All this is about to change.</p>
+
+ <p>This presentation will illustrate how ODF XML, and related open programming
+ technologies can benefit new types of solutions that effectively re-define how
+ documents, and the data contained within may participate in the context of
+ business processes, their workflows and transactions. These new solutions may
+ be deployed directly on the Internet and accessed by multiple runtimes: industry
+ standard Web browsers, an Eclipse-based rich client platform runtime, or directly
+ from an ODF editor runtime such as OpenOffice, KOffice, Sun Star Office or IBM
+ Workplace. Users will be able to collaborate and interact with document data in
+ ways never before possible. Brief demonstrations will be included.</p>
+ </div>
+
+ <div class="bio">
+ <p><strong>Doug Heintzman</strong>, prior to his current position as Director
+ of Strategy for Lotus Software, was Director of Strategy for IBM Software
+ Group encompassing all the five brands: Information Management, WebSphere,
+ Tivoli, Rational and Lotus. Doug led IBM's open source strategy development
+ and related topics and he has led IBM initiatives in eGovernment. In the world
+ of open standards, Doug was a key contributor to SynchML, where he teamed with
+ Nokia, Sun and other vendors contributing to the development of this standard.</p>
+ </div>
+ <p><a href="wednesday.html">Back</a></p>
+ </div>
+
+
+ </div>
+
+ <div id="footera">
+ <div id="poweredbya">
+ <p><img src="/images/feather-small.gif"/><br/>Powered by the Apache CMS.</p>
+ </div>
+ <div id="copyrighta">
+ <p>
+ Apache "OpenOffice.org" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+ Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+ decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+ not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+ yet to be fully endorsed by the ASF.</p>
+ <p>
+ <a href="/contact.html">Contact Us</a> |
+ <a href="/terms.html">Terms of Use</a>
+ <br />Apache and the Apache feather logos are trademarks of The Apache Software Foundation.
+ <br />OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation.
+ <br />Other names appearing on the site may be trademarks of their respective owners.
+ </p>
+ </div>
+ </div>
+
+</body>
+</html>
Added: websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/schedule.css
==============================================================================
--- websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/schedule.css (added)
+++ websites/staging/ooo-site/trunk/content/marketing/ooocon2006/schedule/schedule.css Wed Nov 30 23:54:05 2011
@@ -0,0 +1,96 @@
+/* Abstracts */
+
+.abstract {
+ margin-top: 2em;
+ margin-bottom: 2em;
+}
+
+.abstract .header .title {
+ font-size: large;
+ font-weight: bolder;
+ margin-bottom: 0em;
+ padding-bottom: 0em;
+}
+
+.abstract .header .by {
+ font-size: smaller;
+ font-style: italic;
+ padding-top: 0em;
+ margin-top: 0em;
+}
+
+.abstract .content {
+ margin-left: 3em;
+ text-align: justify;
+}
+
+.abstract .bio {
+ margin-top: 1em;
+ margin-left: 3em;
+ text-align: justify;
+ border-top: thin solid grey;
+}
+
+/* timetables */
+
+.timetable {
+ border: 1px solid rgb(0, 62, 161);
+ border-collapse: collapse;
+ width: "100%";
+}
+
+.sessionbox, .communitybox, .devbox, .generalbox, .odfbox, .breakbox, .partybox, .keynotebox {
+ border: 1px dotted rgb(0, 62, 161);
+ text-align: left;
+ vertical-align: top;
+ padding: 0.5em;
+}
+
+.sessionbox, .timebox, .partybox, .keynotebox {
+ border: 1px dotted rgb(0, 62, 161);
+ background-color: #f0f0f0;
+ padding: 0.5em;
+}
+
+.sessionbox, .timebox, .keynotebox {
+ font-size: smaller;
+ text-align: left;
+}
+
+.timebox {
+ font-weight: bolder;
+ text-align: left;
+}
+
+.breakbox {
+ text-align: center;
+ border: 1px solid rgb(0, 62, 161);
+}
+
+.communitybox {
+ background-color: rgb(182, 198, 224);
+}
+
+.devbox {
+ background-color: rgb(252, 179, 190);
+}
+
+.generalbox {
+ background-color: rgb(255, 240, 181);
+}
+
+.odfbox {
+ background-color: rgb(200, 231, 190);
+}
+
+.partybox, .keynotebox {
+ text-align: center;
+}
+
+.sessionbox .links, .keynotebox .links {
+ display: block;
+}
+
+a img {
+ border: 0px;
+}