xhtml - Gary Edwards on Diigo

4Expand

IE aims to embrace the web again | Technology | The Guardian

Tags: CSS, HTML, Hachamovitch, IE, Microsoft, Silverlight, W3C, WPF, XAML, XHTML on 2008-08-14 -All Annotations (0) -About

more fromwww.guardian.co.uk

I asked Hachamovitch, who has led the Explorer team since 2003, why it has taken Microsoft so long to address these deficiencies. "It comes down to what we were doing with our time," he said. "Between 2001 and 2003 we were building what you experience now as Windows Presentation Foundation and Silverlight."
These technologies display not HTML, the language of web pages, but XAML, Microsoft's proprietary code for creating rich visual content.
It sounds good, but Hachamovitch's warmth begins to fade when I broach the vexed subject of browser scripting. The context is important. Hachamovitch had already stated that Microsoft spent three years neglecting IE for the sake of a more proprietary technology, which is now appearing on the web as a browser plug-in called Silverlight. This is similar in some ways to Adobe's Flash, and supports rich multimedia effects within web pages, as well as the ability to run applications written in Microsoft's .NET Framework.
Is it possible that Microsoft is stifling the advancement of JavaScript in order to promote programming within Silverlight instead?
Add Sticky Note
- Is this is arhetorical question? Early in the article Tim discovers that Micrsoft spent the post Netscape years working on WPF and Silverlight instead of IE and compliance with emerging open web standards such as HTML5, CSS3 and JavaScript (the WebKit Docuemnt Model)
  posted by garyedwards on 2008-08-14

5Expand

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

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.

Tags: html, xhtml, css, javascript on 2008-07-10 and saved by3 people -All Annotations (0) -About

more frommondaybynoon.com

# See also my comment on the same web page that explains why HTML 5 is NOT it for document exchange between web editing applications. . - comment by marbux

# 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 platform they own. The Web is going to be broken. There is no way of stopping Microsoft at this point. What we can do though is focus on Open Web solutions that are worthy alternatives to Microsoft's proprietary push. For me, this means the WebKit layout/document model supported by Apple, Adobe and Google.

~ge~
post by garyedwards on 2008-07-10
Response to marbux comments.
post by garyedwards on 2008-07-09

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

1Expand

Understanding HTML, XML and XHTML | Webkit Surfin’ Safari

Tags: webkit, html, xhtml, xml on 2008-07-03 and saved by3 people -All Annotations (0) -About

more fromwebkit.org

1Expand

Beware of XHTML

Tags: xhtml, html, css, javascript, webkit on 2008-07-03 and saved by13 people -All Annotations (0) -About

more fromwww.webdevout.net

1Expand

HTML5, XHTML2, and the Future of the Web : Digital Web Magazine

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

Tags: html5, xhtml, xml, xhtml2, html4 on 2008-05-27 and saved by11 people -All Annotations (0) -About

more fromwww.digital-web.com

1Expand

ConsortiumInfo.org - Standards to the People! (Updated Twice)

Strange demands from Andy Updegrove: "I call on Ecma to withdraw OOXML from ISO and keep control of it themselves. We need it for legacy documents...."

Why would anyone want Ecma to take back control of MSOffice-OOXML from ISO? The best circumstance would be for OASIS to turn OpenOffice-ODF over to the same ISO JTC-S1, where they can finally begin the difficult (if not impossible) harmonization process. Let me add on other thing; the place for ISO to begin harmonization is "presentation". We desperately need a standardized presentation model useful to MSOffice-OOXML, OpenOffice-ODF, XHTML and HTML. I suggest they start with CSS 3, and work back into ODF - OOXML. But that's just me :)

Tags: ODF, OOXML, CSS, XHTML, ISO on 2008-05-20 -All Annotations (0) -About

more fromwww.consortiuminfo.org

1Expand

How To make Web-Clean Documents in AbiWord

Bonus points to Paul!

Tags: HTML, CSS, AbiWord, XHTML, CDF on 2008-05-08 -All Annotations (0) -About

more fromwww.abisource.com

1Expand

Open Stack: ISO Does The Unthinkable. How ISO approval of MSOffice-OOXML will break the Web

In response to a recent question posted to a rather old OpenStack blog, i posted this summary of my views on ISO approval of MSOffice-OOXML and the impact it will have on the futrue of the open web.

Tags: odf, ooxml, xaml, xhtml, css, msoffice, interoperability, daVinci on 2008-04-22 -All Annotations (0) -About

more fromopenstack.blogspot.com

9Expand

ECIS Accuses Microsoft of Plotting HTML Hijack | BetaNews Jan 2007

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.

Tags: xaml, xhtml, wpf, ooxml, open-web, html, css on 2008-04-18 -All Annotations (0) -About

more fromwww.betanews.com

Great summary quote! At least someone gets it.
post by garyedwards on 2008-04-18
Vista is not the threat! The threat is that of the MS Web-Stack, at the core of which is the Exchange/SharePoint juggernaut tha tis rapidly replacing Lotus Notes and Apache as the premier server system for eMail, messaging, portal CMS, calendar-scheduling, project management, and collaborative computing.

The MS Web-Stack is able to speak HTML5-CSS2.1 as well as the proprietary XAML-Silverlight-Smart Tags set of WPF technologies designed as alternatives to advancing W3C XHTML, CSS, SVG, XForms, and RDF.
post by garyedwards on 2008-04-18

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.
Add Sticky Note
- What difference does that make? XML is a language for developing domain specific XML languages. Sometimes these domain specific dialects are shared, sometimes they are not. There are ZERO interoperability requirements with XML!!!! XAML is 100% proprietary XML language written exclusively for the MSOffice-OOXML <> MS Web-Stack <> IE-8 use. That it's XML has nothing to do with the interop expected of Opne Web formats.
  
  XAML is proprietary.
  posted by garyedwards on 2008-04-18
Add Sticky Note
- Now that ISO/IEC has approved MSOffice-OOXML as an international standard, there is no need for Microsoft to submit XAML for consideration as an open web format.
  
  This is the true impact of ISO's unthinkable actions. In the future, Microsoft can always respond to XAML critics that MSOffice-OOXML is an open standard and the world is free to convert OOXML to whatever format they want, including advanced XHTML2-CSS3-RDF.
  
  The truth of the matter however is that no one will be able to perfect this kind of conversion in ways competitive with the OOXML <> XAML conversion component found in the MSOffice SDK. MSOffice-OOXML itself is a moving target that ISO will spend the next ten years trying to stabilize.
  
  Meanwhile, billions of complex, business process rich, MSOffice documents will be transitioned to the MS Web-Stack. Thye Exchange/SharePoint/MS-SQL juggernaut is rapidly replacing Apache, J2EE, and Lotus Notes Web server systems as Microsoft picks up the low hanging fruit of basic Web services. All teh while introducing proprietary protocols, formats and application-platform-vendor specific dependencies.
  posted by garyedwards on 2008-04-18
Add Sticky Note
- Uh, why would Microsoft do that? Now that MSOffice-OOXML is an aprroved ISO standard, there is no need to push XAML as an open web technology.
  posted by garyedwards on 2008-04-18

3Expand

Is HTML in a Race to the Bottom? A Large-Scale Survey of Open Web Formats

What makes the Internet so extraordinary is the interoperability of web ready data, content, media and the incredible sprawl of web applications servicing the volumes of information. The <i>network of networks</i> has become the information system connecting and converging all information systems. The Web is the universal platform of access, exchange and now, collaborative computing. This survey exammines the key issue of future interoperability; Web Document Formats.

Tags: html, xhtml, ooxml, xaml, css, cdf on 2008-04-18 -All Annotations (0) -About

more fromdsonline.computer.org

The "race to the bottom" is a
familiar phenomenon that occurs when multiple standards compete for acceptance.
In this environment, the most lenient standard usually attracts the greatest
support (acceptance, usage, and so on), leading to a competition among
standards to be less stringent. This also tends to drive competing standards
toward the minimum possible level of quality. One key prerequisite for a race
to the bottom is an unregulated market because regulators mandate a minimum
acceptable quality for standards and sanction those who don't
comply.^1,2 In examining current HTML standards, we've come to
suspect that a race to the bottom could, in fact, be occurring because so many
competing versions of HTML exist.

At this time, some nine different versions of HTML (including its successor,
XHTML) are supported as W3C standards, with the most up-to-date being XHTML
1.1. Although some versions are very old and lack some of the newer versions'
capabilities, others are reasonably contemporaneous. In particular, HTML 4.01
and XHTML 1.0 both have "transitional" and "strict" versions.
Clearly, the W3C's intent is to provide a pathway to move from HTML 4.01 to
XHTML 1.1, and the transitional versions are steps on that path. It also aims
to develop XHTML standards that support device independence (everything from
desktops to cell phones), accessibility, and internationalization. As part of
this effort, HTML 4.01's presentational elements (used to adjust the appearance
of a page for older browsers that don't support style sheets) are eliminated in
XHTML 1.1.

Our concern is that Web site designers might decline to follow the newer
versions' more stringent formatting requirements and will instead keep using
transitional versions. To determine if this is likely, we surveyed the top
100,000 most popular Web sites to discover what versions of HTML are in
widespread use.
Add Sticky Note
- The summary statement glosses over the value of a highly structured portable XML document. A value that goes far beyond the strict separation of content and presentation. The portable document model is the essential means by which information is exchanged over the Web. It is the key to Web interop.
  
  Up till now, Web docuemnts have been very limited. With the advent of XHTML-2, CSS-3, SVG, XForms and CDF (Compound Document Framework for putting these pieces together), the W3C has provisioned the Web with the means of publishing and exchanging highly interactive but very complex docuemnts. The Web documents of the future will be every bit as complex as the publishing industry needs.
  
  The transition of complex and data rich desktop office suite documents to the Web has been non existent up till now. With ISO approval of MSOffice-OOXML, Microsoft is now ready to transition billions of business process rich "office" documents to the Web.
  
  This transition is accomplished by a very clever conversion component included in the MSOffice SDK. MS Developers can easily convert OOXML documents to Web ready XAML documents, adn back again, without loss of presentation fidelity, or data. No matter what the complexity!
  
  The problem here is that while MSOffice-OOXML is now an ISO/IEC International Standard, XAML "fixed/flow" is a proprietary format useful only to the IE-8 browser, the MS Web Stack (Exchange, SharePoint, MS SQL, and Windows Server), and the emerging MS Cloud.
  
  Apache, J2EE, Mozilla Firefox, Adobe and Open Source Servers in general will not be able to render these complex, business process rich, office suite documents. MSOffice-OOXML itself is far to complicated and filled with MS application-platform-vendor specific dependencies to be usefully converted to Open Web XHTML-CSS, ePUB or CDF.
  
  XAML itself is only the tip of the iceberg. The Microsoft Web Stack also implements Silverlight, Smart Tags and other WPF - .NET
  posted by garyedwards on 2008-04-18

Picasa HTML-CSS Page Layout - Brian - Redfern

Basic layout of highly strucutred HTML - CSS page design

Tags: html, css, xhtml on 2008-04-05 -All Annotations (0) -About

more frompicasaweb.google.com

1Expand

Standards competition and globalization | John Carroll | ZDNet.com

Tags: odf, ooxml, w3c, xaml, xhtml on 2008-03-27 -All Annotations (0) -About

more fromblogs.zdnet.com

1Expand

India Votes Against OOXML | Slashdot discussion

MSOffice SDK OOXML <> XAML converter. It is all about the web!!!!!!

Tags: iso, microsoft, odf, ooxml, w3c, xaml, xhtml on 2008-03-26 -All Annotations (0) -About

more frompolitics.slashdot.org

NicEdit - WYSIWYG Content Editor, Inline Rich Text Application

Tags: ajax, editor, html, xhtml on 2008-03-23 and saved by30 people -All Annotations (0) -About

more fromnicedit.com

1Expand

Unbreaking the Web: IE 8 passes ACID 2 Test | John Resig

Tags: CDF, CSS, ISO, Microsoft, ODF, OOXML, W3C, XHTML on 2008-03-07 -All Annotations (0) -About

more fromejohn.org

1Expand

The future of XML

Tags: odf, ooxml, xhtml, xml on 2008-02-14 and saved by4 people -All Annotations (0) -About

more fromwww.ibm.com

HTML Playground, html, css reference by example - Flock

very cool interactive reference for xhtml + css design.

Tags: css, html, xhtml on 2008-02-10 and saved by165 people -All Annotations (0) -About

more fromhtmlplayground.com

2Expand

Independent study advises IT planners to go OOXML | All about Microsoft | ZDNet.com

Tags: burtongorup, cdf, css, garyedwards, maryjo, odf, okelly, ooxml, w3c, xhtml on 2008-01-20 -All Annotations (0) -About

more fromblogs.zdnet.com

“ODF represents laudable design and standards work. It’s a clean and useful design, but it’s appropriate mostly for relatively unusual scenarios in which full Microsoft Office file format fidelity isn’t a requirement. Overall, ODF addresses only a subset of what most organizations do with productivity applications today.”

The report continues:

“ODF is insufficient for complex real-world enterprise requirements, and it is indirectly controlled by Sun Microsystems, despite also being an ISO standard. It’s possible that IBM, Novell, and other vendors may be able to put ODF on a more customer-oriented trajectory in the future and more completely integrate it with the W3C content model, but for now ODF should be seen as more of an anti-Microsoft political statement than an objective technology selection.”
Add Sticky Note
- Mary Jo takes on the recently released Burton Group Report comparing OOXML and ODF. Peter O'Kelly, one of the Burton Group authors, once famously said, "ODF is a great format if you live in an alternative universe where MSOffice doesn't exist!"
  
  This observation speaks to the core problem facing ODF and those who seek to implement the ODF standard: ODF was not designed for the conversion of MSOffice documents. Nor was ODF designed to work with MSOffice applications.
  
  Another way of saying this is to state that ODF was not designed to be interoperable with MSOffice documents, applications and bound processes. The truth is that ODF was designed for OpenOffice/StarOffice. It is an application specific format.
  
  Both OOXML and ODF do a good job of separating content from presentation (style). The problem is that the presentation - layout layers of both ODF and OOXML remains bound to specific applications producing it. While the content layers are entirely portable and can be exchanged without information loss, the presentation layers can not.
  
  Microsoft makes no bones about the application specific design and purpose of OOXML. It's stated right in the Ecma 376 charter that OOXML was designed to be compatible with MSOffice and the billions of binary documents in MSOffice specific binary formats. The situation however is much more confusing with ODF.
  
  ODF is often promoted as being application, platform and vendor independent. After five years of development though, the OASIS ODF TC has been unable to strip ODF of it's OpenOffice/StarOffice specific aspects. ODF 1.0 - ISO 26300 had three areas that were under specified; meaning these areas were described in syntax only, and lacked the full semantics demanded by interoperable implementations. Only OpenOffice and StarOffice code base applications are able to exchange documents with an acceptable fidelity.
  
  The three under specified areas of ODF are: Lists (numbered), F
  posted by garyedwards on 2008-01-14

1Expand

CDI WICD 2.0

Tags: cdf, css, svg, w3c, wicd, xforms, xhtml on 2008-01-20 -All Annotations (0) -About

more fromwww.w3.org

2Expand

Brian Jones: Open XML Formats : Mapping documents in the binary format (.doc; .xls; .ppt) to the Open XML format

Tags: burtongroup, cdf, css, ibm, iso, microsoft, odf, okelly, ooxml, opendocument, openxml, sun, w3c, xhtml on 2008-01-20 -All Annotations (0) -About

more fromblogs.msdn.com

Well well well. We knew that IBM had access to the secret binary blueprints back in 2006. Now we know that Sun ALSO had access!

And why is this important? In June of 2006, Massachusetts CIO Louis Gutierrez asked the OpenDocument Foundation's da Vinci Group to work with IBM on developing the da Vinci ODF plug-in clone of Microsoft's OOXML Compatibility Pack plug-in. When we met with IBM they were insistent that the only way OASIS ODF could establish sufficient compatibility with MSOffice and the billions of binary documents would be to have the secret blueprints open.

Even after we explained to IBM that da Vinci uses the same internal conversion process that the OOXML plug-in used to convert binaries, IBM continued to insist that opening up the secret binaries was a primary objective of the OASIS ODF community.

For sure this was important to IBM and Sun, but the secret binaries were of no use to us. da Vinci didn't need them. What da Vinci needed instead was a subset of ODF designed for the conversion of those billions of binary documents! A need opposed by Sun.

Sun of course would spend the next year developing their own ODF plug-in for MSOffice. But here's the thing: it turns out that Sun had complete access to the secret binary blueprints dating back to 2006!!!!!!

So even though IBM and Sun have had access to the blueprints since 2006, they have been unable to provide effective conversions to ODF!

This validates a point the da Vinci group has been trying to make since June of 2006: the problem of perfecting a high fidelity conversion between the billions of binaries and ODF has nothing to do with access to the secret binary blueprints. The real issue is that ODF was NOT designed for the conversion of those binary documents.

It is true that one could eXtend ODF to achieve the needed compatibility. But one has to be very careful before taking this ro
post by garyedwards on 2008-01-20

The second issue we had feedback on was an interest in the mapping from the binary formats into the Open XML formats. The thought here was that the most effective way to help people with this was to create an open source translation project to allow binary documents (.doc; .xls; .ppt) to be translated into Open XML. So we proposed the creation of a new open source project that would map a document written using the legacy binary formats to the Open XML formats. TC45 liked this suggestion, and here was the TC45 response to the national body comments:

We believe that Interoperability between applications conforming to DIS 29500 is established at the Office Open XML-to- Office Open XML file construct level only.

Gary Edwards's Bookmarks tagged xhtml → View Popular

IE aims to embrace the web again | Technology | The Guardian

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

Understanding HTML, XML and XHTML | Webkit Surfin’ Safari

Close your `<script>` and `<canvas>` tags!

Beware of XHTML

HTML5, XHTML2, and the Future of the Web : Digital Web Magazine

XHTML2 is XML

ConsortiumInfo.org - Standards to the People! (Updated Twice)

How To make Web-Clean Documents in AbiWord

HTML Formatting Instructions - Cascading Style Sheets (CSS)

Open Stack: ISO Does The Unthinkable. How ISO approval of MSOffice-OOXML will break the Web

ECIS Accuses Microsoft of Plotting HTML Hijack | BetaNews Jan 2007

Is HTML in a Race to the Bottom? A Large-Scale Survey of Open Web Formats

Picasa HTML-CSS Page Layout - Brian - Redfern

Standards competition and globalization | John Carroll | ZDNet.com

India Votes Against OOXML | Slashdot discussion

NicEdit - WYSIWYG Content Editor, Inline Rich Text Application

Unbreaking the Web: IE 8 passes ACID 2 Test | John Resig

The future of XML

HTML Playground, html, css reference by example - Flock

Independent study advises IT planners to go OOXML | All about Microsoft | ZDNet.com

CDI WICD 2.0

1.1. Conformance

Brian Jones: Open XML Formats : Mapping documents in the binary format (.doc; .xls; .ppt) to the Open XML format

Gary Edwards's Related Tags

See More Top Contributors

Related Groups on Diigo

Diigo - Highlight and Share the Web!

Gary Edwards's Bookmarks tagged xhtml → View Popular

Close your <script> and <canvas> tags!

XHTML2 is XML

1.1. Conformance

Gary Edwards's Related Tags

See More Top Contributors

Related Groups on Diigo

Diigo - Highlight and Share the Web!

Close your `<script>` and `<canvas>` tags!