Glide 3.0 has been released and it is excellent! Does not yet run on a Treo, but htings are looking great. The sync program is very intriguing, and they seem to have a well thought out hosting model. Way beyond Google Docs and Zoho. Not much information on the file format side of things. Glide is written in Flex with native OS adaptations written in C-C++. Optimized for Firefox. I'm still ocnfused about the browser vs. Flex runtime (VM).

Tags: glide on 06-03-2008 -Cached -About Shared by:Gary Edwards

more from www.transmediacorp.com

Adobe's Erik Larson introduces Acrobat.com. His blog comments echo his post in response to an article at ComputerWorld: http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9091678

In the CW article, Guy Creese of the Burton Group holds the line, defending, as expected, the Microsoft alighnment of MSOffice, Exchange and SharePoint.

Tags: acrobat adobe air buzzword on 06-02-2008 -Cached -About Shared by:Gary Edwards

more from blogs.adobe.com

good interview with Kevin Lynch about the future of the Web. Covers AIR, Flex, Flash, Silverlight and how the Web is moving from universal access and exchange of documents to that of applications. Lynch places Adboe products into a larger context of which problems these inventions solved. The new problem is that of expanding the Web to the desktop through these emerging universal applications.

Tags: adobe air flash flex lynch silverlight on 05-31-2008 -Cached -About Shared by:Gary Edwards

more from knowledge.wharton.upenn.edu

The IOWA Comes vs. Microsoft antitrust suit evidence is now publicly available. This ZDNet Talkback posts an extraordinary eMail from Bill Gates concerning the need to control MSOffice formats and protocols as Microsoft pushes onto the Web.

The key point is that Chairman Bill understands that the real threat to Microsoft is that of Open Web formats and protocols outside of Microsoft's control. It's 1998, and the effort to "embrace and eXtend" W3C HTML, XHTML, SVG and CSS isn't working well. The good Chairman notifies the troops that MSOffice must come up with another plan.

Interestingly, it's not until 2001, when OpenOffice releases an XML encoding of the OpenOffice/StarOffice imbr that Microsoft finally sees a solution! (imbr = in-memory-binary-representation)

The MSOffice crew immediately sets to work creating a similar XML encoding of the MSOffice binary (imbr) dump. The first result is released in the MSOffice 2003 beta as "WordprocessingML and SpreadsheetML".

XML was designed as a structured language for creating specific structured languages. OpenOffice saw the potential of using XML to create an OpenOffice specific XML language. MSOffice seized the innovation and the rest is history. Problem solved!

So what was the "problem" the good Chairman identified in this secret eMail? It's that the Web is the future, and Microsoft needed to find a way of leveraging their existing desktop document "editor" monopoly share into owning and controlling the Web formats produced by Microsoft applications. MSOffice OOXML is the result.

ISO approval of MSOffice OOXML is beyond important to Microsoft. It establishes MSOffice "editors" as standards compliant. It also establishes the application, platform and vendor specific MSOffice OOXML as an international "open" standard.

Many will ask why this isn't a case of Microsoft actually opening up the MSOffice formats in compliance with government antitrust demands. It is "compliance", but not in the sense of what the world expects and needs. It's compliance with what the world demanded back in 1995: full documentation of the application specific MSOffice binary (and xml encoded) format representation.

The thing is, the web is the future. What matters is the conversion of MSOffice OOXML to a web ready format.

In December of 2007, when much of the world was focused on the 1995 battle between OpenOffice ODF and MSOffice OOXML at ISO, Microsoft released the MSOffice 2007 SDK beta. In this beta was a nifty two way conversion component for converting OOXML <> XAML "fixed/flow".

Uh Oh.

XAML is the "Web ready" format aspect of the entirely proprietary Windows Presentation Foundation layer (WPF). XAML joins Silverlight, XPS, Smart Tags and LINQ as core components of WPF.

These core components can be seen as proprietary alternatives to Open Web and Adobe standards such as the W3C's XHTML, CSS, SVG, XForms, CDF, RDF, RDFa, SPARQL, Mozilla's XUL, JavaScript, and Adobe's Flash, Flex, AIR, PDF and ePUB.

And there you go. The IE 8.0 beta limits support to HTML-5 bits and CSS 2.1. Forget about JavaScript, SVG, RDF, and XHTML.

What i see here is that Microsoft is preparing a complete Web-Stack of business oriented applications and services capable of speaking both "low level" Web and "high level" WPF (XAML-Silverlight).

Look at the connection between MSOffice and the Exchange/SharePoint/SQL Server Web-Stack. It's filled with proprietary protocols and format conversions. Microsoft owns the "client" in client/server. The OBA (Office Business Architecture) binds many a client/server business process and more than a few workgroup-workflow activities. It was the OBA phenomenon that stopped ODF in Massachusetts! Stopped it so cold that the phrase "ODF is impossible to implement" found it's way into the general lexicon.

So imagine that the world is really thirsting to migrate these client/server business processes to the newly emerging model known as client/Web-Stack/server. Microsoft has been busy putting in the pieces to facilitate this, but, as the 1998 eMail reads, seeks to control the transition. They needed their own "web ready" formats and protocols; including the collaboration protocols!

They also needed a Web-Stack capable of speaking both Open Web and MS Web.

My feeling is that ISO approval of MSOffice OOXML was the final piece to the MS puzzle. It solved the antitrust problem while protecting the proprietary WPF alternative to Open Web formats and protocols. In the aftermath of ISO approval, Live-Mesh and Silverlight development efforts were thrown into high gear. The Exchange/SharePoint/SQL-S3erver juggernaut looks unstoppable. And MSOffice is now an open standards compliant "editor" producing formats that have only one useful future direction; a XAML "fixed/flow" web ready direction.

In light of these developments, it makes sense that Microsoft would comply with as many antitrust related ISO NB concerns as possible. Supporting ODF in MSOffice and joining the OASIS ODF TC are a small price to pay for the opportunity ISO approval of MSOffice-OOXML creates. ODF is not an interoperable format anyway, so data loss on conversion happens to everyone. Who can blame Microsoft for lousy conversions when, after over five years as a member of the OASIS ODF TC, KOffice will have even worse conversion fidelity!

It's important to note that the greatest threat to Microsoft's Web push is that of antitrust. If they can corral antitrust concerns and focus them on 1995 issues, they can push MSOffice client/server to the MS Web without notice. Thus achieving exactly what antitrust was designed to prevent; the leveraging of an existing monopoly into control and dominance of emerging markets.

At the end of the day, Google may well own the "consumer" side of the Web. With Microsoft owning the "business" side of the Web. Such is the power of controlling that transition from client/server to client/Web-Stack/server and the Mesh of SOA, SaaS and Web RIA 3.0 that follows.

Hope this helps,
~ge~

Tags: anti-trust browser-wars comes gates iowa msoffice netscape ooxml w3c on 05-30-2008 -Cached -About Shared by:Gary Edwards

more from talkback.zdnet.com

list of email evidence presented in the antitrust action Microsoft rushed to settle.

Tags: antitrust comes formats iowa microsoft msoffice protocols on 05-30-2008 -Cached -About Shared by:Gary Edwards

more from iowa.gotthefacts.org

Another JavaSript library concept, but this time secure. Not as robust as jQuery, but Yahoo is off to a great start. wikiWORD could use this for dynamic page generation.

Tags: css html-5 javascript jquery on 05-30-2008 -Cached -About Shared by:Gary Edwards

more from browserplus.yahoo.com

Aaron Miller writes about the limitations and difficulties with ePUB. He suggests a new format, "BOOK" based on ePUB but web ready. BOOK is an AJAX format in that it includes (X)HTML, CSS and JavaScript! Excellent stuff! The discussion on this page is one of the best on the Web. ePUB gets thrashed, but with arguments very difficult to contest. The web is everything, and Aaron's friends fully understand this. Sadly, the ePUB crowd does not. I found this site looking to solve the problem of numbered lists in ePUB.

Tags: ajax book css ebook epub html-5 on 05-30-2008 -Cached -About Shared by:Gary Edwards

more from www.teleread.org

More confusion about the MS announcement of native support for ODF, with delayed support for whatever ISO finally determines to be ISO 29500; "OOXML". Damn but these guys are all twisted up about this. The truth is, ISO National Bodies traded their vote in favor of OOXML for MSOffice support for ODF and Microsoft's joining the OASIS ODF TC. It's not complicated. MS wants ISO approval of OOXML because it established MSOffice as a "standards" editor. The rest of this kurfufull is all about anti trust concerns and Microsoft's need to put htose concerns to bed before the world figures out that they are leveraging the MS desktop monopoly into an MS Web monopoly. ISO approval of OOXML is the final piece of very complex puzzle.

The harmonization of OOXML-ODF is impossible. MS knows this. So why not join OASIS ODF TC if it means putting aside the anti trust claims from ISO NB's and getting that all important standardization of OOXML? Both ODF and OOXML are both XML encodings of entirely application specific binary formats. There is no possible to way to reconcile the file formats without also reconciling the applications! Incuding feature sets and layout engines!!!! Impossible!!

The real game is the transition from client/server to the emerging client/Web-Stack/server model. MS is the "client" in client/server. No way were they about to give that up without a plan to control the transition of MSOffice documents to the emerging client/Web-Stack/server model. They sought to fully control the formats, protocols and API's of this new model. ISO handed it to them.

The thing to watch is the MSOffice SDK where one can find a very cool OOXML <> XAML converter. XAML is totally proprietary, but "web ready". Meaning, MSOffice is a "web ready" application. It's just that the web readiness is 100% MS .NET-Silverlight.

The great transition to client/Web-Stack/server is now on. Thanks to ISO. All this ODF stuff is just background noise designed to quiet the anti trust crowd. Despicable, but well done.

~ge~

Tags: iso odf ooxml xaml on 05-29-2008 -Cached -About Shared by:Gary Edwards

more from www.fool.com

great article walking through the history of HTML, XHTML, and browsers. Summary is that HTML5 is the future. Good thinking, great arguments.

Tags: html4 html5 xhtml xhtml2 xml on 05-27-2008 -Cached -About Shared by:Gary Edwards

more from www.digital-web.com

The Henry Blodgett article comparing Google and Microsoft. Excellent source!

Tags: google microsoft msoffice web-platform on 05-18-2008 -Cached -About Shared by:Gary Edwards

more from www.alleyinsider.com

Review of Henry Blodgett's predicitve analysis that within the next year Google's search revenue will surpass Microsoft's revenue from Windows. MS still has MSOffice and the Exchange/SharePoint/SQL Server juggernaut. But Blodgett fearlessly predicts the beginning of the end fo rthe great monopolist. Great quote from Microsoft's Ben Slovika.

Tags: google microsoft msoffice web-platform windows on 05-14-2008 -Cached -About Shared by:Gary Edwards

more from www.news.com

Tags: air ajax ria silverlight web-3.0 on 05-13-2008 -Cached -About Shared by:Gary Edwards

more from www.infoworld.com

Bonus points to Paul!

Tags: abiword cdf css html xhtml on 05-08-2008 -Cached -About Shared by:Gary Edwards

more from www.abisource.com

Excellent whitepaper from Duane.

Tags: soa web-2.0 web-stack woa on 05-08-2008 -Cached -About Shared by:Gary Edwards

more from www.adobe.com

uh oh. JavaScript - SVG rendering engine relacing HTML - CSS with SVG drawn from a transform library.

Tags: ria svg on 05-08-2008 -Cached -About Shared by:Gary Edwards

more from www.crn.com

More review of the Gilmopre Gang interview

Tags: google mesh microsoft xaml on 05-06-2008 -Cached -About Shared by:Gary Edwards

more from www.lorenheiny.com

Techcrunch review of a recent Gilmore Group interview with MS Live Mesh product manager

Tags: cloud-computing google mesh microsoft yahoo on 05-06-2008 -Cached -About Shared by:Gary Edwards

more from www.techcrunch.com

SOA platform that extends across client, server and cloud. Scary stuff that preceeded the Live Mesh - Silverlight announcement at Web 2.0 (2008)

Tags: cloud-computing mesh soa woa on 05-05-2008 -Cached -About Shared by:Gary Edwards

more from www.microsoft.com

Joel rails on HailStorm and it's latest Ray Ozzie Groove inspired incarnation, "Live Mesh".

Tags: groove mesh microsoft ozzie synchronization on 05-03-2008 -Cached -About Shared by:Gary Edwardsand 1 member(s) first by: marbux

more from www.joelonsoftware.com

<p>The Wikipedia "OpenDocument Foundation" page is continually re edited, changing the factual truth to portray the Foundation in the worst light possible. Every time we try to repair the page to reflect the truth, the liars jump right back in. Is there a Wikipedia resolution for liies? Our facts can be verified by the five year history of the OASIS membership and ODF TC records that are public information.</p><p> This anonymous post to Joe Barr's Linux.com article is perhaps the best explanation on the Web of why the Foundation choose CDF, and could not use ODF.</p><p>Good explanation of MSOffice-OOXML and the MS Web-Stack :: MS Cloud.</p><p>No mention of the December 2007 MSOffice SDK beta that provided us with that first all important glimpse of the MSOffice-OOXML <> XAML converter component. I take it the article comment was written before that most important discovery. XAML "fixed/flow" is an alternative to W3C/ISO XHTML-CSS and ISO PDF.</p>

Tags: foundation ms-web-stack msoffice odf ooxml wikipedia xaml on 05-04-2008 -Cached -About Shared by:Gary Edwards

more from www.linux.com