Skip to main content

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

Rss Feed Group items tagged

Paul Merrell

Microsoft releases Office 2008 SP1, says VBA to make return - 0 views

  •  
    ""The response has been amazing -- since we launched in January, the velocity of sales for Office 2008 is nearly three times what we saw after the launch of Office 2004," said Craig Eisler, general manager of the Mac BU at Microsoft. ... As part of its announcements Tuesday, the Mac BU also said it intends to bring VBA-language support back to the next version of Office for Mac, but offered no timeframe for the update." According to the article, sales for MS Office 2008 for the Mac have tripled what MS Office 2004 accomplished. There's a bit of a wookie hidden in the claim because new Mac sales have far more than tripled since the comparable period following the release of Office 2004. So even though Microsoft Office gross sales on the Mac have increased from the period compared, there is a strong appearance that Microsoft is losing market share on the Mac, something I would be concerned about were I Steve Ballmer, not something to celebrate. Also note that the lack of VBA support in Office 2008 plus a few other Microsoft moves dealt Office for the Mac out of the Micrsooft cloud. Why Redmond might suddenly have a change of heart and deal Apple into the MS Cloud afer all is something not explained. But it is somewhat plausible that Microsoft feels the need to change its mind on VBA because it is losing market share on the Mac. My assessment? The VBA announcement is vaporware until proved otherwise, designed to slow the adoption of competing office software on the Mac, which makes the rapidly expanding OS X stack, e.g., now able to run Linux apps, a bigger threat to Windows. Microsoft is obviously losing Office market share on the Mac platform and OS X is eating Windows market share. Time for vaporware.
Paul Merrell

Building Office Business Applications: A New Breed of Business Applications Built on th... - 0 views

  •  
    2006 MSDN white paper that is the best overview I've found thus far of the bridges Microsoft is building between Office 2007 and the Microsoft cloud. 12 pp. Somewhat dated in the intervening two years. Describes the Microsoft "line of business" vision for vertical markets in some detail. "This white paper introduces Office Business Applications (OBAs), a new breed of easily customizable solutions that address real-world business problems through the 2007 Microsoft Office system. OBAs deliver people-centric, collaborative solutions to the enterprise through familiar Microsoft Office servers, clients, and tools. This document discusses today's business environment, identifies a "results gap" that contributes to reduced productivity, and shows that OBAs are an effective new approach that enables enterprises to achieve the "last mile of productivity." You will see that several key components of the 2007 Microsoft Office system can be used to develop Office Business Applications and that, when Line of Business Integration (LOBi) for Microsoft Office SharePoint Server is released, it will further simplify the development of OBAs. Finally, if you would like to develop a collaboration-planning scenario using the 2007 Office system, just follow the steps outlined in this paper."
Gary Edwards

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

  • 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.
  •  
    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

Google Search To Surpass Size of Microsoft Windows in 2009 - Silicon Alley Insider - 0 views

  • Google's search business will pass Microsoft's Windows business by early next year (at the latest). Good thing Microsoft has another huge, wildly profitable monopoly: Office. Add that to the calculation, and Microsoft can breathe easy for a few more years: GOOGLE SEARCH vs MICROSOFT WINDOWS + OFFICEQuarterly Revenue Q3 2006-Q1 2008 Of course, Google's visible in that Microsoft rearview mirror, too--especially now that it offers a product that is directly competitive with Office. And then there's the most depressing comparison (from Microsoft's perspective). After 13 years of heavy investment, frequent doubling down, and--until recently--a browser monopoly, here's how Microsoft's online business is doing relative to Google's search business. Remember: Google was founded four years after Microsoft launched its online business, and Microsoft's search business is just a tiny piece of Microsoft Online.
  • The "Windows monopoly+Office monopoly=Microsoft" story was absolutely true 10 years ago, but less so now. 1. It looks as if the "Office" revenue figures are coming from MSFT's reported revenues in the Business segment. That's not all Office. Based on what they've said at the last few Financial Analyst Meetings, Exchange is approaching $2B/year, SharePoint is about $1B/year, and Dynamics (formerly Microsoft Business Solutions) is more than $1B per year. I also know that Project has been a $1B/year business for a long time (believe it or not), and products such as Comms Server and Visio contribute around $500m/year. Margins on all these products are lower than on Office, but most (not Comms Server) are profitable. 2. In addition to all the non-Office products that compose its Business segment as mentioned above, the Server and Tools business (Windows Server, SQL Server) is profitable (30% margins) and growing revenues average of 15% for the last six years. Not monopoly, but a good business. Look at all these stats together, and seems like they should get out of search and advertising and sell off (or scale back to maintenance mode) most of the consumer online sites, focusing instead on hosted business apps--they're already doing it with Exchange and SharePoint, why not Office? If somebody's going to canniblize their "real" business, it might as well be them.
  •  
    The Henry Blodgett article comparing Google and Microsoft. Excellent source!
  •  
    Blodgett calls Windows a "natural monopoly," a term derived from the science of economics. But the view of Windows as a natural monopoly blinks past more than a few facts: [i] the monopoly at all times was firmly rooted in government-granted monopoly created by copyrights, patents, and trade secrets; [ii] even the 3.x versions depended mightily on antitrust violations involving DR DOS; and [iii] the dependence on antitrust violations to build, maintain, and extend the monopoly continue to this day. I see scant basis for labeling Windows as a "natural monopoly." Economic theory may blink past the antitrust issues on free market principles, but it may not blink past the government grants of monopolies in similar fashion..
Paul Merrell

Obama technology election plank adds national CTO, interoperability - 0 views

  •  
    (Use page search) Obama will appoint the nation's first Chief Technology Officer (CTO) to ensure that our government and all its agencies have the right infrastructure, policies and services for the 21st century. The CTO will ensure the safety of our networks and will lead an interagency effort, working with chief technology and chief information officers of each of the federal agencies, to ensure that they use best-in-class technologies and share best practices. ... The CTO will also ensure technological interoperability of key government functions. For example, the Chief Technology Officer will oversee the development of a national, interoperable wireless network for local, state and federal first responders as the 9/11 commission recommended. This will ensure that fire officials, police officers and EMTs from different jurisdictions have the ability to communicate with each other during a crisis and we do not have a repeat of the failure to deliver critical public services that occurred in the aftermath of Hurricane Katrina. ...
Gary Edwards

Is MSOffice the new Netscape? | Rough Type: Nicholas Carr's Blog: - 0 views

  • One of the cornerstones of Microsoft's competitive strategy over the years has been to redefine competitors' products as features of its own products. Whenever some upstart PC software company started to get traction with a new application - the Netscape browser is the most famous example - Microsoft would incorporate a version of the application into its Office suite or Windows operating system, eroding the market for the application as a standalone product and starving its rival of economic oxygen (ie, cash). It was an effective strategy as well as a controversial one.
  • Google is trying to pull a Microsoft on Microsoft by redefining core personal-productivity applications - calendars. word processing, spreadsheets, etc. - as features embedded in other products. There's a twist, though. Rather than just incorporating the applications as features in its own products, Google is offering them up to other companies, particularly big IT vendors, to incorporate as features in their products.
  • Google's advantage here doesn't just lie in the fact that it is ahead of Microsoft in deploying Web-based substitutes for Office applications. Microsoft can - and likely will - neutralize much of that early-mover advantage by offering its own Web-based versions of its Office apps. Its slowness in rolling out full-fledged web apps is deliberate; it doesn't see Google Apps, or similar online offerings from other companies, as an immediate threat to its Office franchise, and it wants to avoid, for as long as possible, cannibalizing sales of the highly profitable installed versions of Office.
  • ...2 more annotations...
  • It knows that, should traditional personal-productivity apps become commonplace features of the cloud, supplied free or at a very low price, the economic oxygen will slowly be sucked out of the Office business. That doesn't necessarily mean that customers will abandon Microsoft's apps; it just means that Microsoft won't be able to make much money from them anymore.
  • Microsoft may eventually win the battle for online Office applications, but the victory is likely to be a pyrrhic one.
  •  
    Microsoft faces down threats from Google, IBM and SalesForce.com with it's threat to enterprise IT - MSOffice as the ultimate browser.
  •  
    Google Office productivity alternatives are "trapped inside the browser". MSOffice, Silverlight, Live Mesh and Adobe Flex "RIA" browser alternatives are comparatively feature rich and powerfull.
Gary Edwards

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

  • 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
  •  
    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 Fall of Microsoft Office - 0 views

  • 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
  •  
    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

Australia blows $51 million on Microsoft Office | One more reason for open source | The... - 0 views

  • Opposition Leader Martin Hamilton-Smith yesterday said the computer "blunder" saw thousands of Health Department computers loaded up with $675 versions of Microsoft Office software, which the computers did not use or need. Just 4000 of the 16,000 computers actually used the software, Mr Hamilton-Smith told Parliament. Health Minister John Hill was quick to defend the decision and insisted that all of the licenses are in use (on "computers that monitored patients, analysed pathology data or kept patient records and staff records using specific software designed for those purposes"
  •  
    Once again it's the business processes bound to MSOffice that bind users to MS products. The Massachusetts ODF Pilot Study first uncovered the business processes bound to MSOffice issue tha tmade implementation of ODF impossible. The IBM "rip out and replace" approach simply does nto work anywhere there are these bound business processes. Massachusetts CIO Louis Gutierrez correctly identified the problem and the solution: coem up with an ODF plug-in for MSOffice. Replace the docuemnt format - not the application and bound business processes.
Gary Edwards

Ozzie signals Microsoft's surrender to the cloud | Software as Services | ZDNet.com - 0 views

  • It’ll be cheaper to put apps in the cloud than to run them on your own servers: “It’s an inevitable business. The higher levels in the app stack require that this infrastructure exists, and the margins are probably going to be higher in the stack than they are down at the bottom … Somebody who is selling [business] apps is going to build in, more than likely, the underlying utility costs within their higher-level service. It will still be cheaper to do those things on a service infrastructure than it is on a server infrastructure.” Taken together, these statements — by the company’s chief strategy officer, no less — add up to a huge strategic shift under way within Microsoft. They suggest that, in five years’ time, the company will be unrecognizable compared to today, with services revenues taking a significant share while licence revenues dwindle.
  •  
    Phil Wainwright comments on Ray Ozzie statements concerning the Microsoft Cloud Strategy. Phil of course thinks MS is in trouble.
Paul Merrell

My take on why Microsoft finally decided to support ODF « Arnaud's Open blog - 0 views

  • Let’s just now hope that Microsoft won’t try to play games anymore. Besides their rather poor track record at delivering on the ongoing chain of announcements about becoming open and caring about interoperability (as opposed to intraoperability), there are other reasons one might want to take today’s announcement with caution. One trick they could try and pull for instance would be to put just enough support for ODF to claim that they support it but not enough for people to really use it systematically. They could then tell customers who complain something isn’t working that it’s because ODF isn’t powerful enough, and if they want the full power of Office they need to use OOXML.
  •  
    IBM's Arnaud La Hors on why Microsoft should be blamed for what is inevitable given that ODF is not designed for interoperability and is not application-neutral. One might rationally fault Microsoft for not having joined the ODF TC earlier, but the ODF TC studiously avoided enabling interoperability even among ODF implementations and ODF has almost no mandatory conformity requirements, with application-specific extensions classified as conformant. The real ODF standard is the OOo code base controlled by Sun Microsystems. IBM played along with that game and cloned the OOo code base instead of fighting on the TC to make the myth of ODF interoperability come true. I don't see a lot of moral high ground for IBM here.
Gary Edwards

Three myths Microsoft tells Russia | The Open Road - The Business and Politics of Open ... - 0 views

  • Even so, we interoperate with Microsoft products, anyway, even without Microsoft's blessing. As just one example, which content collaboration/management system integrates most seamlessly with Microsoft Office? If you said, "Sharepoint," you would be wrong. The answer is Alfresco. Who has seamlessly integrated the Microsoft CIFS interface into a Java-based CMS? If you said, "Sharepoint," you would again be wrong. The answer, again, is "Alfresco."
  •  
    OSS Innovation and MS IPR :: OSS Interop vs. MS Interop :: OSS Profit vs. MS Profit
Gary Edwards

A reminder of why Microsoft wanted Yahoo | Tech news blog - CNET News.com - 0 views

  • When Windows has a real rival, Microsoft has real problems. As Blodget notes, there are caveats: The unofficial Office monopoly should give Microsoft breathing room for a few more years. But even that could be threatened as Google's more-affordable Web applications improve. This storm has been gathering for years. In 2005, we wrote a piece at News.com about Google's longterm threat to Microsoft. The impetus was a major management shuffle at MSN, but we had fun pulling out some old Microsoft memos about now-defunct Netscape in the early days of the World Wide Web. My favorite was a note written in 1995 by Microsoft engineer Ben Slivka describing a "nightmare" scenario for his company. "The Web...exists today as a collection of technologies that deliver some interesting solutions today, and will grow rapidly in the coming years into a full-fledged platform (underlined for emphasis in the original memo) that will rival--and even surpass--Microsoft's Windows," Slivka wrote. Microsoft didn't pay too much attention to the warning. Ten years later, another internal memo put a name to that nightmare--Google. Now Blodget has advanced that nightmare scenario a few more steps with his analysis.
  •  
    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.
Gary Edwards

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

  • 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
       
      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.
  •  
    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.
1 - 14 of 14
Showing 20 items per page