Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <016b01cd7a68$d37833b0$7a689b10$@rosenlaw.com>
References: 
 <OFAF74BF90.E00E487E-ON85257A5A.005651D7-85257A5A.005737D4@gesmer.com>
	<016b01cd7a68$d37833b0$7a689b10$@rosenlaw.com>
Date: Tue, 14 Aug 2012 18:59:52 -0400
Message-ID: 
 <CAP-ksoiaDyTMSVvAMF5LCnGMjRB91sWtfeDpxmR1k0C-MBiNxw@mail.gmail.com>
Subject: Re: FW: Office to Become Fully Open XML Compliant (at last)
From: Rob Weir <robweir@apache.org>
To: ooo-dev@incubator.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Aug 14, 2012 at 6:04 PM, Lawrence Rosen <lrosen@rosenlaw.com> wrote=
:
> FYI. /Larry
>

It is great to read about the improved ODF support, including ODF 1.2,
with OpenFormula and digital signature support.  Those are two of the
major additions we made in ODF 1.2.  The other was adding RDFa/RDF XML
support, which neither OpenOffice nor MS Office support. ( But there
is some support in Calligra Suite).

OOXML Strict was a concession to ISO National Bodies, a last ditch
effort invented in a conference room in Geneva to pacify delegates at
the Ballot Resolution Meeting.  I was there.  I saw it.  There may be
specialized applications where OOXML Strict support is useful, such as
a format that a document generation application can target.  But for
AOO, and for any other editor that cannot control the formats of input
documents,  we need to be prepared to handle whatever users toss to
us, and that includes OOXML from Office 2007 and 2010, as well as
2013.

-Rob


>
>
> Lawrence Rosen
>
> Rosenlaw & Einschlag, a technology law firm ( <http://www.rosenlaw.com> w=
ww.rosenlaw.com)
>
> 3001 King Ranch Rd., Ukiah, CA 95482
>
> Office: 707-485-1242
>
>
>
> From: Andy Updegrove [mailto:Andrew.Updegrove@gesmer.com]
> Sent: Tuesday, August 14, 2012 8:53 AM
> To: andrew.updegrove@gesmer.com
> Subject: Office to Become Fully Open XML Compliant (at last)
>
>
>
>
> Between 2005 and 2008, an unparalleled standards war was waged between
> Microsoft, on the one hand, and IBM, Google, Oracle and additional
> companies on the other hand. At the heart of the battle were two document
> formats, one called ODF, developed by OASIS, a standards development
> consortium, and Open XML, a specification developed by Microsoft. Both
> were submitted to, and adopted by, global standards groups ISO/IEC.
>
> But after the dust settled, Microsoft did not fully implement the standar=
d
> that it had fought so vigorously to have become a global standard.
> Instead, it implemented what it called "Transitional Open XML," which was
> better adapted for use in connection with documents created using older
> versions of Office.
>
> According to a blog posted yesterday by Jim Thatcher at the Office Next W=
eb
> site, Office 13 will - finally - permit users to open, edit and save
> documents in the format that ISO/IEC approved. Thatcher says that Office
> 13 will also provide similar capabilities for the latest version of ODF,
> approved by OASIS in January of this year (ODF 1.2), as well as for PDF.
>
> Much has changed since the great format wars of the last decade, and
> perhaps this is why, one day after the announcement, the announcement has
> been mentioned in only two brief articles in the trade press. That=E2=80=
=99s a
> shame, because document interoperability and vendor neutrality matter mor=
e
> now than ever before as paper archives disappear and literally all of hum=
an
> knowledge is entrusted to electronic storage.
>
> Only if documents can be easily exchanged and reliably accessed down ton =
an
> ongoing basis will desktop competition in the present be preserved, and t=
he
> availability of knowledge down through the ages be assured.  Without
> robust, universally adopted document formats, both of those goals are
> impossible to attain.
>
> Read the entire story here: http://tinyurl.com/czwwke9
>
> As always, please let me know if you would like to be removed from this
> list.
>
> Andy
>
> Andrew Updegrove
> Gesmer Updegrove LLP
> 40 Broad Street
> Boston, Massachusetts 02109
> T: 617/350-6800
> F: 617/350-6878
> www.gesmer.com
> www.consortiuminfo.org
>
> Have you discovered The
> Alexandria Project? http://amzn.to/xo00rn
>
>   _____
>
> Any tax information or written tax advice contained herein (including any=
 attachments) is not intended to be and cannot be used by any taxpayer for =
the purpose of avoiding tax penalties that may be imposed on the taxpayer. =
(The foregoing legend has been affixed pursuant to U.S. Treasury Regulation=
s governing tax practice.)
>
> Electronic mail from Gesmer Updegrove LLP, 40 Broad Street, Boston, MA 02=
109. Voice: (617) 350-6800, Fax: (617) 350-6878. This communication is inte=
nded only for the use of the individual or entity named as the addressee. I=
t may contain information which is privileged and/or confidential under app=
licable law. If you are not the intended recipient or such recipient's empl=
oyee or agent, you are hereby notified that any dissemination, copy or disc=
losure of this communication is strictly prohibited. If you have received t=
his communication in error, please immediately notify Christopher O'Sulliva=
n at (617) 350-6800 and notify the sender by electronic mail. Please expung=
e this communication without making any copies. Thank you for your cooperat=
ion.
>