Return-Path: X-Original-To: apmail-incubator-general-archive@www.apache.org Delivered-To: apmail-incubator-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 81D4C6647 for ; Tue, 28 Jun 2011 11:38:32 +0000 (UTC) Received: (qmail 58348 invoked by uid 500); 28 Jun 2011 11:38:31 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 58120 invoked by uid 500); 28 Jun 2011 11:38:30 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 58112 invoked by uid 99); 28 Jun 2011 11:38:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jun 2011 11:38:30 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rabastus@gmail.com designates 209.85.210.175 as permitted sender) Received: from [209.85.210.175] (HELO mail-iy0-f175.google.com) (209.85.210.175) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jun 2011 11:38:26 +0000 Received: by iym10 with SMTP id 10so62823iym.6 for ; Tue, 28 Jun 2011 04:38:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=F6IoYj1d/IIFxo4IhPk2uMJJfzvtFlUi3AV/mr6Yb2w=; b=MIWaf9LfqQvTC8PC6ZrPFXeOuZub9aT272mPHCqHY+FrvNP1Ni2cmfPNL+4xf//9+G IPEG6SPiItIqR9u8AG5sZKWj9MBWh7CXNaTkrryi+Zaqcq+4+ZncmnGn3WO1v/0JhiUW 9v6ToWJV699M5iQEGI9SmMMY/IUxHaFMRbW/o= MIME-Version: 1.0 Received: by 10.42.148.132 with SMTP id r4mr8134684icv.159.1309261084788; Tue, 28 Jun 2011 04:38:04 -0700 (PDT) Sender: rabastus@gmail.com Received: by 10.42.213.71 with HTTP; Tue, 28 Jun 2011 04:38:04 -0700 (PDT) In-Reply-To: References: Date: Tue, 28 Jun 2011 07:38:04 -0400 X-Google-Sender-Auth: d-J2YlsrNc0C3WYhZ0xqIiBtdqQ Message-ID: Subject: Fwd: ODF Toolkit Incubation Pre-Proposal From: Rob Weir To: dev@poi.apache.org, general@incubator.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Passing along, from the ooo-dev list. -Rob ---------- Forwarded message ---------- From: J=C3=BCrgen Schmidt Date: 2011/6/28 Subject: Re: ODF Toolkit Incubation Pre-Proposal To: ooo-dev@incubator.apache.org Hi Rob, i support your idea and i think that it make sense to move the ODFToolkit project to Apache as well. ODF is a key element in an open standard based world. Probably more automatically processed =C2=A0document workflows become available in the fu= ture because of an open standard that everybody can read and write. Fat client applications like OpenOffice, LibreOffice, Symphony are only one part of th= e story. But when we think about the new generation of devices (smartphones, tablets) it becomes obvious that a smaller library that can handle this document format really make sense. Simple viewers are necessary to make the format popular like PDF for easy exchange of documents. Other applications that generate documents in a backend or again full featured or simplified editors are altogether necessary to build a working eco-system around ODF. I would prefer a new project to give them the visibility it needs. Ideally the project will not only support a Java library but also other languages (e.g. Python, the existing C#, etc.). Juergen On Mon, Jun 27, 2011 at 9:42 PM, Rob Weir wrote: > I'm cc'ing the POI and OpenOffice projects, inviting them to join this > discussion on the Incubator general list: general@incubator.apache.org > > When we were discussing the OpenOffice proposal a few weeks ago I > mentioned that there was another set of technology called the ODF > Toolkit, that we might want to bring to Apache as well. =C2=A0I heard som= e > enthusiasm for this at the time, but I didn't have the bandwidth to > put together another proposal. =C2=A0Now I do. =C2=A0I'd like to pitch th= e idea, > and see if there is still interest in having a formal incubation > proposal submitted, and if so, identifying a Champion and Sponsor for > the proposal. > > Note that this would not be a fork. =C2=A0The ODF Toolkit Union Steering > Committee met this morning and agreed to propose moving to Apache. > > As you probably know, ODF =3D=3D Open Document Format, a open standard > document format for office documents. =C2=A0The ODF standard is created a= t > OASIS and then sent to ISO/IEC JTC1 for transposition into an > International Standard. =C2=A0ODF 1.0 was first published in 2005. =C2=A0= ODF 1.1 > came out in 2007. =C2=A0And ODF 1.2 is "Candidate OASIS Standard" awaitin= g > final approval in OASIS, probably by end of September. =C2=A0ODF 1.2 is > what most applications are supporting today. =C2=A0 OpenOffice, > LibreOffice, Symphony, KOffice/Calligra Suite use ODF as native > formats. =C2=A0Other applications, including Microsoft Office, Corel > Wordperfect and Google Docs offer some degree of import/export > support. =C2=A0ODF 1.2 is the version also supported by the ODF Toolkit. > > The ODF Toolkit Union maintains the following toolkits, all of them > under the Apache 2.0 license: > > 1) ODFDOM is Java-based typed DOM API, relatively low level, a 1-to-1 > mapping to the ODF schema. =C2=A0In fact, much of the code is generated b= y > processing the schema. > > http://odftoolkit.org/projects/odfdom/pages/Home > > 2) Simple Java API for ODF is a high level wrapper of ODFDOM. =C2=A0So > operations that might require several DOM-level operations, like > deleting a column in a spreadsheet, are a single operation in the > Simple API. =C2=A0Search and replace, copying slides from one presentatio= n > to another, adding hyperlinks to a selection, etc., are top level > operations. > > http://simple.odftoolkit.org/ > > 3) The Conformance Tools projects is also in Java, and includes an > online conformance checker of ODF documents, which can also be run in > command line mode. > > http://odftoolkit.org/projects/conformancetools/pages/Home > > 4) XSLTRunner and XSLT Runner Task allows easy use of XSLT transforms > with ODF documents. > > http://odftoolkit.org/projects/conformancetools/pages/ODFXSLTRunner > > 5) AODL is a C#/.NET library for ODF > > http://odftoolkit.org/projects/aodl/pages/Home > > I think there is natural synergy with Apache, especially with the Java > components. =C2=A0For example, I could see publishing pipelines involving > the ODF Toolkit with PDFBox, Batik, FOP, and POI. Having these tools > under a common license, in one place, has obvious benefits. > > Moving this project over would not be a large technical effort. > Mercurial =3D=3D> SVN, =C2=A0some simple website/wiki migration, 30 or so > pages, a few mailing lists and bugzilla databases. =C2=A0It is currently = on > the Kenai infrastructure, so similar to OpenOffice, just much, much > smaller in scale. > > I'm open as to whether this would be best eventually as a TLP or as > part of an existing project, like POI or even OpenOffice. =C2=A0I'm leani= ng > a little toward having this as a TLP, but I'm open to other ideas. > > Also, since this is already an open source project with all code under > Apache 2.0, I assume no SGA is required? > > So please let me know if you agree that Apache would be a good > location to further develop the ODF Toolkit libraries. > > Regards, > > -Rob > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org