Skip to main content

Home/ In-the-Clouds-with-SOA-XML-and-the-Open-Web/ Group items tagged iso

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

The Fall of Microsoft Office - 0 views

www.fool.com/...-fall-of-microsoft-office.aspx

iso odf ooxml xaml

shared by Gary Edwards on 29 May 08 - Cached
  • On the same day that the state of New York published a report supporting open formats for electronic documents, mighty Microsoft (Nasdaq: MSFT) said that it would support the open-source ODF format in Office 2007. Redmond's own Open Office XML specification may be heading for the great Recycle Bin in the sky, never to come back.
  • The company's biggest revenue generator may be a shadow of its former self in a few years. I just hope that Microsoft has some alternative business prospects on tap
  • Gary Edwards on 29 May 08
     
    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 t
Gary Edwards

Independent study advises IT planners to go OOXML: The Bill Gates MSOffice "formats and... - 0 views

talkback.zdnet.com/5206-12558-0.html

anti-trust browser-wars comes gates iowa msoffice netscape ooxml w3c

shared by Gary Edwards on 30 May 08 - Cached
  • 3.2.2.2. A pox on both your houses! gary.edwards - 01/22/08 Hi Robert, What you've posted are examples of MSOffice ”compatibility settings” used to establish backwards compatibility with older documents, and, for the conversion of alien file formats (such as various versions of WordPerfect .wpd). These compatibility settings are unspecified in that we know the syntax but have no idea of the semantics. And without the semantic description there is no way other developers can understand implementation. This of course guarantees an unacceptable breakdown of interoperability. But i would be hesitant to make my stand of rejecting OOXML based on this issue. It turns out that there are upwards of 150 unspecified compatibility settings used by OpenOffice/StarOffice. These settings are not specified in ODF, but will nevertheless show up in OpenOffice ODF documents – similarly defying interoperability efforts! Since the compatibility settings are not specified or even mentioned in the ODF 1.0 – ISO 26300 specification, we have to go to the OOo source code to discover where this stuff comes from. Check out lines 169-211. Here you will find interesting settings such as, “UseFormerLineSpacing, UseFormerObjectPositioning, and UseFormerTextWrapping”. So what's going on here?
  • From: Bill Gates Sent: Saturday, December 5 1998 To: Bob Muglia, Jon DeVann, Steven Sinofsky Subject : Office rendering "One thing we have got to change in our strategy - allowing Office documents to be rendered very well by other peoples browsers is one of the most destructive things we could do to the company. We have to stop putting any effort into this and make sure that Office documents very well depends on PROPRIETARY IE capabilities. Anything else is suicide for our platform. This is a case where Office has to avoid doing something to destroy Windows. I would be glad to explain at a greater length. Likewise this love of DAV in Office/Exchange is a huge problem. I would also like to make sure people understand this as well." Tuesday, August 28, 2007
  • Gary Edwards on 30 May 08
     
    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
Gary Edwards

The Charter Dilemma | ODF Editor Says ODF Loses If OOXML Does | Slashdot - 0 views

tech.slashdot.org/comments.pl

iso odf ooxml w3c

shared by Gary Edwards on 17 Apr 08 - Cached
  • OOXML on the other hand presents ISO with a very different situation. Because of the way the OOXML - Ecma charter is worded, i don't see how ISO JTC-1 could ever fix the OOXML interoperability problems. ISO approval of OOXML would include acceptance of a charter that defines and limits OOXML interoperability to whatever MSOffice determines it to be. If Patrick and the JTC-1 tried to bring OOXML into compliance with existing ISO Interoperability Requirements, they would have to somehow amend a charter duly approved.Given that the JTC-1 has yet to address a two year old ISO directive regarding ODF interop compliance, what are the odds they will dare to amend an approved charter? Not good i think.ISO approval of OOXML is a tragedy for all of us. For sure it's the end of ODF. It's perhaps the end of ISO as a respected standards organization. The issue of open standards itself will become a joke, with the reality of standards by corporation having us all wringing our hands in despair.
  • Gary Edwards on 17 Apr 08
     
    This commentary follows the Stockholm Syndrom post, which is itself in the thread based on Yoon Kit's Open Malaysia comments concerning the dilemma Patrick Durusau is in; the JTC-1 is now filled with Microsoft OOXML supporters!
Gary Edwards

The Stockholm Syndrom at ISO | ODF Editor Says ODF Loses If OOXML Does | Slashdot - 0 views

slashdot.org/comments.pl

durusau iso microsoft odf ooxml slashdot w3c

shared by Gary Edwards on 17 Apr 08 - Cached
  • ISO is bound to the business of "interoperability", and has very strict guidelines for interoperability requirements, that are themselves tied to international trade agreements and legal conventions. In this context, it is beyond surprising that ISO allows the "OASIS PAS" and "Ecma Fast Track" channels to remain open, with specification work remaining under the controlling influence of the vendors.IMHO, the change in Patrick's position is entirely due to the realization that it is impossible to map between OOXML and ODF. I don't know this for sure, but when i read the German Standards Group (DIN) report on harmonization, authorized by the EU-IDABC and provided to ISO, i couldn't help but wonder how Patrick would react. The report definitively ends his OOXML ODF mapping dream.
  • Gary Edwards on 17 Apr 08
     
    Response to Yoon Kit's comments that Patrick Durusau is caught between a rock and hard place. His ISO JTC-1 group is now overwhelmed with MS OOXML supporters!
Gary Edwards

OOXML/ODF: Just One Battlefield in a Much Bigger War | Brian Proffitt Linux Today - 0 views

www.linuxtoday.com/news_story.php3

cloud-computing ooxml soa xaml

shared by Gary Edwards on 19 Apr 08 - Cached
  • Once in a while, a confluence of random events (or not so random, depending on your belief system) can create the ideal aha! moment. The moment of clarity when all the pieces just fall into place and you realize "that's what's going on!" I believe I have had one of those moments. And if this thought has any basis in reality, it could mean that everything we have seen in IT is about to make a huge change.
  • Gary Edwards on 19 Apr 08
     
    Brian figures out that the document wars are really about Cloud Computing. Big vendors IBM, Sun, Google and Microsoft are jockeyign for position in our cloud computing future. And this is why Microsoft MUSt get ISO approval of MSOffice-OOXML! What Brian misses is the key to a Microsoft Cloud that can be found int he MSOffice SDK; the OOXML<>XAML conversion component. XAML, Silverlight and Smart Tags replace W3C XHTML-CSS, SVG-Flash, and RDF. Makign the MS Cloud one where Microsoft owned protocols, formats and .NET components dominate all processes. ISO approval of MSOffice-OOXML establishes MSOffice as a standards "editor", thus masking the cloud computing shift to XAML. A shift that will lock out all other Web 2.0 - Cloud providers dependent on Open Web - W3C protocols and formats!
  • Gary Edwards on 19 Apr 08
     
    Note that Brian posted this article in February, on the eve of the Geneva BRM. Since then ISO has gone on to approve MSOffice-OOXML. Note also that, a week prior to this publication, i had sent Brian a lengthy discussion entitled "Windows can't do Cloud Computing", where all of these issues were discussed except for the IBM motivations. Not wanting to interfere with the upcoming Geneva BRM and vote, I had declined Brian's request to publish.
Gary Edwards

The Mesh lives but the cloud Office is vaporous | Outside the Lines - CNET News.com - 0 views

www.news.com/8301-13953_3-9926440-80.html

live-mesh ms-cloud msoffice ooxml soa xaml

shared by Gary Edwards on 24 Apr 08 - Cached
  • Office Live will bring Office to the web, and the web to Office. We will deliver new and expanded productivity experiences that build upon the device mesh vision to extend productivity scenarios seamlessly across the PC, the web, and mobile devices. Individuals will seamlessly enjoy the benefits of each - the rich, dynamic editing of the PC, the mobility of the phone, and the work-anywhere ubiquity of the web. Office Live will also extend the PC-based Office into the social mesh, expanding the classic notion of "personal productivity" into the realm of the "inter-personal" through the linking, sharing and tagging of documents. Individuals will have a productivity centric web presence where they can work and productively interact with others. This broadly extended vision of Office is being realized today through Office Mobile and Office Live Workspace on the web, augmented by SharePoint, Exchange, and OCS for the connected enterprise.
  • Gary Edwards on 24 Apr 08
     
    I don't think Dan Farber gets it. ISO approval of MSOffice-OOXML establishes MSOffice as a standards compliant web/cloud/WOA "editor" for client/Web-Stack/server systems. No need to try to squeeze all tha tcomplexity into a browser. Just use the MSOffice SDK OOXML <> XAML conversion component to convert rich, business process loaded, documents to a web ready format. OH my, XAML is proprietary and IE-8 does not support XHTML2, CSS3, SVG, XForms, RDF, SPARQL, SWF, PDF or JavaScript. Bummer. ISO has done the unthinkable and Microsoft can now break the web without worry of anti trust retribution. They are after all, simply implementing an open standard.
Gary Edwards

What's up at the OpenDocument Foundation? Linux.com - Wikipedia Link - 0 views

www.linux.com/121034

foundation ms-web-stack msoffice odf ooxml wikipedia xaml

shared by Gary Edwards on 03 May 08 - Cached
  • Re: Finally, the beef... Posted by: Anonymous [ip: 76.14.48.79] on November 12, 2007 11:32 PM XHTML + CSS is the base. Add XForms, SVG and SMiL where needed. Study the work being done on microformats. Like most modern portable XML file formats, the basic packages are those of content and presentation. In CDF speak, this is XHTML content and CSS as the portable presentation package. ODF and MS-OOXML both struggle with the legacy tradition of the presentation package being application specific. Meaning, the portability is limited to other applications that are either of the same version, or, share the same layout and rendering model so that the exchange of the presentation package is lossless.
    • Paul Merrell
      Paul Merrell on 04 May 08
       
      See also "Putting Andy Updegrove to Bed (without his supper)," http://www.universal-interop-council.org/node/4 for a thorough rebuttal of claims that the W3C Compound Document Formats and framework are not suitable for use in the office productivity software sector.
  • Gary Edwards on 03 May 08
     
    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. 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.Good explanation of MSOffice-OOXML and the MS Web-Stack :: MS Cloud.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.
Gary Edwards

Has Microsoft lost its way on desktop computing? | The Apple Core | ZDNet.com - 0 views

blogs.zdnet.com/Apple

msoffice ooxml saas soa xaml

shared by Gary Edwards on 17 Apr 08 - Cached
  • OM MALIK: You outlined Microsoft’s software-plus-services strategy, but what I want to know about is the changing role of the desktop in this service’s future. RAY OZZIE: I think the real question is (that) if you were going to design an OS today, what would it look like? The OS that we’re using today is kind of in the model of a ’70s or ’80s vintage workstation. It was designed for a LAN, it’s got this great display, and a mouse, and all this stuff, but it’s not inherently designed for the Internet. The Internet is this resource in the back end that you can design things to take advantage of. You can use it to synchronize stuff, and communicate stuff amongst these devices at the edge. A student today or a web startup, they don’t actually start at the desktop. They start at the web, they start building web solutions, and immediately deploy that to a browser. So from that perspective, what programming models can I give these folks that they can extend that functionality out to the edge? In the cases where they want mobility, where they want a rich dynamic experience as a piece of their solution, how can I make it incremental for them to extend those things, as opposed to learning the desktop world from scratch?
  • Gary Edwards on 17 Apr 08
     
    ZDNet's David Morgenstern must have missed ISO approval of OOXML! MS has a desktop strategy, but involves proprietary protocols, formats and API's as the protective barrier for transitioning desktop bound client/server business processes to MS Web Stack bound SaaS-SOA business processes. Welcome to the Microsoft Cloud!
Gary Edwards

Introducing Microsoft Online Services - 0 views

www.mosbeta.com/Welcome.aspx

cloud-computing collaborative-computing ms-cloud ms-live ooxml soa xaml

shared by Gary Edwards on 18 Apr 08 - Cached
  • Gary Edwards on 18 Apr 08
     
    The MS Cloud has arrived!!!! Grab your ankles and kiss your ever lovin Open Web good-bye. This is a video describing how Microsoft Online Services can add value to your organization. Interestingly, the software-plus-service offerings from Microsoft are being marketed as a way for corporate IT to break free; reducing systems management cost and operation overhead while leveraging existing "rich client" systems. Meaning, MSOffice is now connected to the MS Cloud. The transition of legacy client/server systems to MS Cloud hosted client/Web-Stack /server systems can now begin. No doubt the recent ISO approval of MSOffice-OOXML played no small part in this announcement!
Gary Edwards

ECIS Accuses Microsoft of Plotting HTML Hijack | BetaNews Jan 2007 - 0 views

www.betanews.com/...1169824569

css html ooxml open-web wpf xaml xhtml

shared by Gary Edwards on 18 Apr 08 - Cached
  • An industry coalition that has represented competitors of Microsoft in European markets before the European Commission stepped up its public relations offensive this morning, this time accusing Microsoft of scheming to upset HTML's place in the fabric of the Internet with XAML, an XML-based layout lexicon for network applications.
  • Gary Edwards on 18 Apr 08
     
    Look at the date on this! A full year has passed and we now can clearly see the importance to Microsoft of ISO approval for MSOffice-OOXML. The MSOffice SDK provides an easy to implement OOXML <> XAML conversion component, pavign the way for billions of complex, business process rich MSOffice documents to be used by IE-8 and the emerging MS Web-Stack. XAML is proprietary and exclusive to the Microsoft Web.
1 - 10 of 10
Showing 20▼ items per page