Web Content
Interoperability
Challenges

TPAC, 2 November 2011,
Santa Clara, CA

Bryan Sullivan, AT&T

Why worry about
interoperability?

There is a somewhat accurate perception among developers, that developing for the Web (especially for mobile devices) is freakin' hard, compared to developing for native platforms.

Web content renders the same in similar contexts
- different browsers in the same device
- the same browser in different devices with the same general capabilities
APIs work the same across similar contexts
this consistency is expected
- prior to specs achieving recommendation
- after specs achieve recommendation
ensuring that we meet these expectations
- requires verification at least once
- requires continual verification
- must be economically sustainable

it just works

What do you think are the key interoperability issues?
Which issues can be addressed by more/better testing?
Which issues can be addressed by better specs or improved W3C process?
Which issues can be addressed by supplemental approaches, e.g.
- JavaScript libraries - what is their role short/long term?
- Developer guidelines
- ...?