[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: "Open XML" et al... Blech... Re: Microsoft buy

  • From: Len Bullard <len.bullard@u...>
  • To: Jonathan Robie <jonathan.robie@r...>, Michael Kay <mike@s...>
  • Date: Fri, 7 Sep 2007 11:33:08 -0500

RE:  "Open XML" et al...  Blech...  Re:  Microsoft buy
Fully?  Probably not.  If nothing else churn in design will mean there is
always something undone.   Even HTML has this problem.  Even before DocBook
there was MIL-D-28001 and it was a bear.  We're still uncovering unspecified
areas of X3D and there wasn't that much controversy.  It simply is a tough
domain to standardize and still meet the participation agreements.

But good enough?  That can be done for document formats.   We'll be able to
make better predictions once the BRM completes because 1) the success or
failure of the ballot won't stop or start the market initiatives 2) we'll
have a finalized version.  Picking that apart will be much easier.

Do note Brian Jones comment on Rick Jeliffe's blog at XML.COM about the
means employed to handle the document size.  Given experts, that seemed
reasonable although he did not answer my query about how they were handling
inter-part dependencies given parallel editing tracks.   A 6000 page spec is
pretty big for one or two editors to process.

The harder problem is semantic-laden exchanges where small differences make
big differences (eg, the spreadsheet formulas).   I would have been happier
with several smaller specifications than one big one.   This is why I
believe that both ODF and OOXML are going to be market dodos in the large
even if reasonably useful in parts.   That has been the fate of every one
side fits all design I've seen.

len


From: Jonathan Robie [mailto:jonathan.robie@r...] 
 
Another factor: exchanging office files with anyone was once very 
difficult, because there were quite a few competing programs, and they 
didn't do that great a job of reading and writing each other's formats. 
They were often bad even at handling their own earlier formats. Many 
environments were eager to see one file format win. RTF was one non-XML 
format that was trying to play this role.

An XML format has real advantages for this. Docbook never became that 
format. So far, ODF hasn't either. OOXML will make it easier to read 
Microsoft's data, but I'd be surprised if it becomes the universal 
document exchange format, partly because it is 6,000 pages and not fully 
specified.

Not sure if we'll ever get there ....

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.