Skip to main content

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

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
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 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

Live Mesh: Microsoft hews to open standards rule | John Carroll | ZDNet.com - 0 views

blogs.zdnet.com/carroll

live-mesh ms-cloud ms-web-stack xaml

shared by Gary Edwards on 24 Apr 08 - Cached
  • Live Mesh is supposed to be a common framework to enable cross-device interoperability. It also includes a bunch of shared services that can be used from any Mesh-compatible device, such as network storage space and photo-sharing services, among others (others likely include many of the “Live” properties) . This makes sense given the direction that the world is moving in, with an ever-growing proliferation of computing devices both on one’s person and within the home that, currently, are too much like islands of processing power. A true mesh platform that standardized cross-device communication and synchronization in the same way HTML / CSS / Javascript has standardized user interfaces on the web would surely be a step forward from an IT evolutionary standpoint. Perhaps it was a Freudian slip, but I think the use of the term “standard” was the essential part of the previous sentence. Microsoft won’t get anywhere if they tried to peddle a closed-protocol environment to developers in 2008.
  • Gary Edwards on 24 Apr 08
     
    I saw Live-Mesh today at the Web 2.0 Expo. It's still flashware, but very cool flashware. (Or is that "silverware" :) If they get this right the web will belong to Microsoft. I disagree with John that mesh will be standards base. Yes, mesh will work with HTML/CSS amd MAYBE JavaScript. But it will also work with the prorietary XAML, Silverlight, Smart Tags - LINQ. All of which are proprietary alternatives to what mesh won't support :: the advanced format standards from the W3C - XHTML, CSS3, SVG, XForms, CDF, RDF, RDFa and SPARQL. Live-Mesh will break the open web just s surely as the MSOffice SDK OOXML <> XAML conversion component will break the open web future into a Google consumer web, and a Microsoft business web.
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.
Paul Merrell

We need an onotology for the tags - 20 views

The tagging feature on Diigo is far less useful if we do not give some thought to an agreed ontology. This not to suggest that free tagging should be discouraged, but it's difficult to maximize the...

group ontology

started by Paul Merrell on 12 May 08 no follow-up yet
Diego Morelli

Microformats for News Articles: the hNews Standard - 0 views

www.victorgodot.com/newmedia

web evolution web3.0 information ideas technology microformats news web 3.0 semantic web semantic standards linked data RDF semantics

shared by Diego Morelli on 27 Nov 09 - Cached
  • Diego Morelli on 27 Nov 09
     
    "A new microformat for online news has been developed by the Media standards Trust and the Web Science Reaseach Initiative: it's called hNews. The goal is to make relevant elements of news articles machine-readable, and at the same time, to disply these metadata in a user-friendly format. ....."
1 - 6 of 6
Showing 20▼ items per page