Skip to main content

Home/ Groups/ Future of the Web
Rss Feed
Sort By: Most Recent | Popular Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

A Proprietary Web? Blame the W3C | TechConsumer Paul Ellis - 0 views

www.techconsumer.com/...-proprietary-web-blame-the-w3c

adobe flash html5 microsoft silverlight whatwg

shared by Gary Edwards on 10 Jul 08 - Cached
  • The real culprit This may seem like a forgone conclusion to many of you after seeing the W3C’s development timetables, but the real reason Flash and Silverlight exist is because the “open-web” people dropped the ball. HTML simply can handle what Flash and Silverlight can do. It has become increasingly stale for modern web development needs. Here is some perspective, HTML5 has finally added a tag for handling video. Flash 6 came out in 2002 with video support! Where is the HTML version of Line Rider? It is in Flash and Silverlight now. If you want to see something really interesting check out Hard Rock Cafe’s memorabilia page (Silverlight 2 required) and tell me if you’ve ever seen something like that with HTML
  • Gary Edwards on 10 Jul 08
     
    A must read. This article was slashdotted.
Gary Edwards

Siding with HTML over XHTML, My Decision to Switch - Monday By Noon - 0 views

mondaybynoon.com/...er-xhtml-my-decision-to-switch

css html javascript xhtml

shared by Gary Edwards on 03 Jul 08 - Cached
  • Publishing content on the Web is in no way limited to professional developers or designers, much of the reason the net is so active is because anyone can make a website. Sure, we (as knowledgeable professionals or hobbyists) all hope to make the Web a better place by doing our part in publishing documents with semantically rich, valid markup, but the reality is that those documents are rare. It’s important to keep in mind the true nature of the Internet; an open platform for information sharing.
  • XHTML2 has some very good ideas that I hope can become part of the web. However, it’s unrealistic to think that all web authors will switch to an XML-based syntax which demands that browsers stop processing the document on the first error. XML’s draconian policy was an attempt to clean up the web. This was done around 1996 when lots of invalid content entered the web. CSS took a different approach: instead of demanding that content isn’t processed, we defined rules for how to handle the undefined. It’s called “forward-compatible parsing” and means we can add new constructs without breaking the old. So, I don’t think XHTML is a realistic option for the masses. HTML 5 is it.
    • Gary Edwards
      Gary Edwards on 09 Jul 08
       
      Great quote from CSS expert Hakon Wium Lie.
  • @marbux: Of course i disagree with your interop assessment, but I wondered how it is that you’re missing the point. I think you confuse web applications with legacy desktop – client/server application model. And that confusion leads to the mistake of trying to transfer the desktop document model to one that could adequately service advancing web applications.
  • Gary Edwards on 03 Jul 08
     
    A CMS expert argues for HTML over XHTML, explaining his reasons for switching. Excellent read! He nails the basics. for similar reasons, we moved from ODF to ePUB and then to CDf and finally to the advanced WebKit document model, where wikiWORD will make it's stand.
  • Paul Merrell on 09 Jul 08
     
    See also my comment on the same web page that explains why HTML 5 is NOT it for document exchange between web editing applications. .
  • Gary Edwards on 09 Jul 08
     
    Response to marbux supporting the WebKit layout/document model. Marbux argues that HTML5 is not interoperable, and CSS2 near useless. HTML5 fails regarding the the interop web appplications need. I respond by arguing that the only way to look at web applications is to consider that the browser layout engine is the web application layout engine! Web applications are actually written to the browser layout/document model, OR, to take advantage of browser plug-in capabilities. The interoperability marbux seeks is tied directly to the browser layout engine. In this context, the web format is simply a reflection of that layout engine. If there's an interop problem, it comes from browser madness differentials. The good news is that there are all kinds of efforts to close the browser gap: including WHATWG - HTML5, CSS3, W3C DOM, JavaScript Libraries, Google GWT (Java to JavaScript), Yahoo GUI, and the my favorite; WebKit. The bad news is that the clock is ticking. Microsoft has pulled the trigger and the great migration of MSOffice client/server systems to the MS WebSTack-Mesh architecture has begun. Key to this transition are the WPF-.NET proprietary formats, protocols and interfaces such as XAML, Silverlight, LINQ, and Smart Tags. New business processes are being written, and old legacy desktop bound processes are being transitioned to this emerging platform. The fight for the Open Web is on, with Microsoft threatening to transtion their entire business desktop monopoly to a Web platfomr they own. ~ge~
Gary Edwards

Time to Pounce: Stephane Rodriguez Responds | Is Microsoft slow to the punch on SOA, or... - 1 views

talkback.zdnet.com/5208-10536-0.html

cloud mesh soa

shared by Gary Edwards on 09 Jul 08 - Cached
  • Time to pounce Noted document expert Stephane Rodriquez has two blog posts (1 and 2) well worth reading. He also supports the opinion that Microsoft has won. They've done the impossible. And every Microsoft executive should be facing criminal charges.
  • Gary Edwards on 09 Jul 08
     
    Links to two posts from Stephane Rodriquez.
Gary Edwards

The Time to Pounce Has Come : Is Microsoft slow to the punch on SOA, or just waiting fo... - 0 views

talkback.zdnet.com/5208-10536-0.html

cloud mesh soa

shared by Gary Edwards on 09 Jul 08 - Cached
  • The Time to Pounce Has Come I agree with DonnieBoy. Microsoft will try to leverage their MSOffice monopoly to dominate the newly emerging marketplace of Web-Stack and Cloud Computing solutions. I also believe that for Microsoft, the final pieces of this puzzle fell into place on March 29th, 2008 with ISO approval of the MSOffice-OOXML document format. For most businesses, Microsoft is the "client" in "client/server". The great transition from client/server to client/ Web-Stack /server has been slow because Microsoft was uncertain as to how they could control this transition. Some light was shed on the nature of this "uncertainty" when the Combs vs. Microsoft antitrust case brought forth a 1998 eMail from Chairman Bill to the MSOffice development team. The issue for the good Chairman was that of controlling the formats and protocols used to connect MSOffice to a Web centric world. MSOffice support for Open Web formats and protocols like (X)HTML, CSS, and WebDAV were out of the question. Microsoft needed to figure out how pull off this transition with proprietary formats and protocols. And avoid the wrath of antitrust in the process!
  • Gary Edwards on 09 Jul 08
     
    ge response to Joe McKendrick's SOA article.
Paul Merrell

Office Business Applications (OBA) - 0 views

msdn.microsoft.com/...bb977469.aspx

architecture microsoft oba office business applications white paper

shared by Paul Merrell on 08 Jul 08 - Cached
  • Paul Merrell on 08 Jul 08
     
    Homepage for the MSDN Architecture Center Office Business Applications white papers.
Paul Merrell

Office Business Applications: Building Composite Applications Using the Microsoft Platform - 0 views

msdn.microsoft.com/...bb220800.aspx

composite apps microsoft oba office business applications

shared by Paul Merrell on 08 Jul 08 - Cached
  • Summary: This book is about composite applications and how they can be developed as OBAs using the 2007 Microsoft Office System. It provides an overview of the technologies available in the 2007 Microsoft Office System, and gives several examples from various industries to build OBAs using composition at the presentation, business-logic, and data layers. This book is meant for solution architects, industry architects, or senior developers who are designing, developing, and deploying composite applications. (97 total printed pages)
« First ‹ Previous 3841 - 3846 of 3846
Showing 20▼ items per page