<p>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. </p>
<p> XAML is proprietary.</p>
This link has been bookmarked by 1 people . It was first bookmarked on 18 Apr 2008, by Gary Edwards.
-
18 Apr 08
Gary EdwardsLook 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.
-
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
-
-
Add Sticky Note
-
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
-
-
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.
-
-
Public Stiky Notes
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.
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.
Page Comments
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.
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.