Open, De Jure, De Facto And Proprietary:  Standards and Microsoft Chris Wilson Group Program Manager Internet Explorer Pla...
Who Is This Character? An unknown member of Flock of Seagulls? <ul><li>Browser guy since 1993 </li></ul><ul><li>NCSA Mosai...
What Am I Here To Discuss? Now that you know who I am <ul><li>Define terms around “standards” </li></ul><ul><li>Discuss pr...
What’s A “Standard”? The OED definition <ul><li>Standard, n. ('stændəd)  A rule, principle, or means of judgment or estima...
Defining Some Terms That describe standards <ul><li>De Jure </li></ul><ul><li>De Facto </li></ul><ul><li>Open </li></ul><u...
De Jure vs. De Facto Declared vs. In Practice <ul><li>De Jure - by right, according to law </li></ul><ul><ul><li>De Jure s...
Open vs. Proprietary More than one definition <ul><li>Open exchange of ideas – anyone can participate in developing the st...
Open Versus Proprietary Why isn’t everything open? <ul><li>With openly-developed standards, you get: </li></ul><ul><li>Lot...
Open Versus Proprietary No really, why isn’t everything open? <ul><li>With proprietary standards, you get: </li></ul><ul><...
Innovation Happens How does innovation get standardized? <ul><li>Sometimes tried out in a proprietary way first – like bor...
What’s AJAX? And is it a standard? <ul><li>Shorthand for “Asynchronous JavaScript + XML” </li></ul><ul><li>“ Ajax isn’t a ...
Proprietary To De Facto XMLHttpRequest – An example <ul><li>In 1998, the core technology in AJAX was created and implement...
Principles of Our Standards Support Yes, we do have principles <ul><li>We have always responded to our customers’ needs </...
This isn’t new In April 2000 we said: <ul><li>“ Since its genesis, Microsoft's Internet Explorer technology has been focus...
So Where’ve You Been? Since 2001… <ul><li>Security exploits grew more profitable– and therefore more sophisticated </li></...
DHTML And WPF  A comparison <ul><li>WPF designed as an integrated platform for Documents, UI, and Media (incl. anim and 3D...
A Few Thoughts To Kick Off Discussion <ul><li>There are lots of formats that make up the web – not all of them are open </...
© 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes n...
Upcoming SlideShare
Loading in …5
×

Open, De Jure, De Facto and Proprietary: Standards and Microsoft

2,289 views

Published on

How is Microsoft approaching standards for tomorrow's applications? Come discuss the landscape of HTML, Javscript, C#, XAML, XHTML, XML, SVG, and others with the Group Program Manager of IE.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,289
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
20
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Open, De Jure, De Facto and Proprietary: Standards and Microsoft

  1. 1. Open, De Jure, De Facto And Proprietary: Standards and Microsoft Chris Wilson Group Program Manager Internet Explorer Platform and Security Microsoft Corporation NGW028
  2. 2. Who Is This Character? An unknown member of Flock of Seagulls? <ul><li>Browser guy since 1993 </li></ul><ul><li>NCSA Mosaic for Windows </li></ul><ul><li>SPRY Mosaic </li></ul><ul><li>Internet Explorer </li></ul><ul><ul><li>2.0, 3.0, 4.0, 5.0, 5.5, 6.0, 7.0! </li></ul></ul><ul><ul><li>And a stint in Avalon (WPF) </li></ul></ul><ul><li>Web standards guy </li></ul><ul><ul><li>HTML, CSS, DOM, I18n, XSL </li></ul></ul>
  3. 3. What Am I Here To Discuss? Now that you know who I am <ul><li>Define terms around “standards” </li></ul><ul><li>Discuss proprietary versus open </li></ul><ul><li>(re-)State our commitments </li></ul><ul><li>Open discussion! </li></ul>
  4. 4. What’s A “Standard”? The OED definition <ul><li>Standard, n. ('stændəd) A rule, principle, or means of judgment or estimation; a criterion, measure </li></ul><ul><li>Translation: </li></ul><ul><ul><li>Descriptive declaration of a set of features with which to measure implementations </li></ul></ul>
  5. 5. Defining Some Terms That describe standards <ul><li>De Jure </li></ul><ul><li>De Facto </li></ul><ul><li>Open </li></ul><ul><li>Proprietary </li></ul>
  6. 6. De Jure vs. De Facto Declared vs. In Practice <ul><li>De Jure - by right, according to law </li></ul><ul><ul><li>De Jure standards are declared to be the standard – often by a consortium </li></ul></ul><ul><ul><li>Often but not always not always open </li></ul></ul><ul><li>De Facto - in reality, as a matter of fact </li></ul><ul><ul><li>De facto standards grow to become adopted as a standard </li></ul></ul><ul><ul><li>Often but not always proprietary </li></ul></ul><ul><ul><li>Strong backwards compatibility needs </li></ul></ul>
  7. 7. Open vs. Proprietary More than one definition <ul><li>Open exchange of ideas – anyone can participate in developing the standard </li></ul><ul><ul><li>Challenge – balancing participant input </li></ul></ul><ul><li>Open can also mean open for anyone to implement – e.g., royalty-free </li></ul><ul><li>Proprietary can mean private - “license must be obtained, if available” </li></ul><ul><li>Proprietary can mean privately developed - but others free to implement </li></ul>
  8. 8. Open Versus Proprietary Why isn’t everything open? <ul><li>With openly-developed standards, you get: </li></ul><ul><li>Lots of different people participating </li></ul><ul><ul><li>Smart people everywhere! </li></ul></ul><ul><li>Influence and experience from a wider variety of consumers/producers </li></ul><ul><li>Better interoperability across vendors </li></ul><ul><li>“Design by committee” </li></ul><ul><ul><li>Less direct ownership, drive to participate </li></ul></ul><ul><ul><li>Participants may have different goals </li></ul></ul>
  9. 9. Open Versus Proprietary No really, why isn’t everything open? <ul><li>With proprietary standards, you get: </li></ul><ul><li>To solve only a limited set of problems </li></ul><ul><ul><li>Maintain a coherent goals and design </li></ul></ul><ul><ul><li>No “design by committee” </li></ul></ul><ul><ul><li>May have own vision of the needs/future </li></ul></ul><ul><li>To move faster </li></ul><ul><li>To easily maintain intellectual property </li></ul><ul><li>Only a private set of perspectives </li></ul>
  10. 10. Innovation Happens How does innovation get standardized? <ul><li>Sometimes tried out in a proprietary way first – like border-radius in Mozilla </li></ul><ul><li>Sometimes things start as proprietary and are donated to open efforts – but in the process, they are likely to change </li></ul><ul><li>Sometimes there are differences between the proprietary version and the de jure standard one – e.g. RSS and Atom </li></ul><ul><li>Sometimes the whole thing is done as an open effort from the beginning, like XML </li></ul>
  11. 11. What’s AJAX? And is it a standard? <ul><li>Shorthand for “Asynchronous JavaScript + XML” </li></ul><ul><li>“ Ajax isn’t a technology [or a standard]. It’s really several technologies [and standards], each flourishing in its own right, coming together in powerful new ways. Ajax incorporates: </li></ul><ul><ul><li>Standards-based presentation using XHTML and CSS; </li></ul></ul><ul><ul><li>Dynamic interaction using the Document Object Model; </li></ul></ul><ul><ul><li>Data interchange and manipulation using XML & XSLT; </li></ul></ul><ul><ul><li>Asynchronous data retrieval using XMLHttpRequest; </li></ul></ul><ul><ul><li>And JavaScript binding everything together.” </li></ul></ul>
  12. 12. Proprietary To De Facto XMLHttpRequest – An example <ul><li>In 1998, the core technology in AJAX was created and implemented by Microsoft – the XMLHttpRequest object </li></ul><ul><li>Other browsers have picked this up and implemented it, and now the W3C is creating a de jure standard around it </li></ul>
  13. 13. Principles of Our Standards Support Yes, we do have principles <ul><li>We have always responded to our customers’ needs </li></ul><ul><li>We are committed to making the world better by improving the quality of our support of open standards in IE </li></ul><ul><li>Balance with backward compatibility - not an excuse to not improve </li></ul><ul><li>We don’t pre-announce – but we are becoming more open in communications </li></ul>
  14. 14. This isn’t new In April 2000 we said: <ul><li>“ Since its genesis, Microsoft's Internet Explorer technology has been focused on providing customers with the best Internet browsing experience possible … </li></ul><ul><li>Microsoft is proud that the Internet Explorer 5.0 technologies in Windows are the most standards compliant browsing technology shipping today. This underscores the importance that standards have in the development of Internet browsing technologies.” </li></ul>
  15. 15. So Where’ve You Been? Since 2001… <ul><li>Security exploits grew more profitable– and therefore more sophisticated </li></ul><ul><ul><li>Feature-packed release of IE in Windows XP Service Pack 2 – focused on security </li></ul></ul><ul><li>Also recognized some shortcomings of DHTML as the foundation of the only client application platform – exploiting local resources, performance, security model, tools support </li></ul>
  16. 16. DHTML And WPF A comparison <ul><li>WPF designed as an integrated platform for Documents, UI, and Media (incl. anim and 3D) </li></ul><ul><ul><li>Integration across all media and app types </li></ul></ul><ul><ul><li>XAML is the declarative markup language </li></ul></ul><ul><ul><li>Can be in-browser or standalone – little change </li></ul></ul><ul><li>Ajax-style development uses current DHTML, but is missing some application constructs </li></ul><ul><ul><li>UI controls and layouts, application model, etc. </li></ul></ul><ul><ul><li>Two new W3C WGs to work on standards for this </li></ul></ul>
  17. 17. A Few Thoughts To Kick Off Discussion <ul><li>There are lots of formats that make up the web – not all of them are open </li></ul><ul><li>Open standards have always formed the interoperable core of the web </li></ul><ul><li>Over time interoperable core increases </li></ul><ul><ul><li>For example XML, XSLT, XMLHTTP, CSS, XHTML, SVG and more add to this core </li></ul></ul><ul><li>[email_address] </li></ul>
  18. 18. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

×