RE: The Extensible Web Manifesto [feedly]

Hi Simon,

Thanks for bringing this up. I think we should make sure that our definition of extensions for "Limited Conformance for Extensions" (http://www.w3.org/WAI/UA/IMPLEMENTING-UAAG20/#conformance-limited) covers polyfill and any other mechanisms a developer might use to change the behaviour of user agents.

And maybe the WCAG-WG needs a pointer to UAAG somewhere since it is content doing the extending.

-Jan

> -----Original Message-----
> From: Simon Harper [mailto:simon.harper@manchester.ac.uk]
> Sent: June-12-13 4:18 AM
> To: Judy Brewer; Shadi Abou-Zahra; UAWG list
> Subject: Fwd: The Extensible Web Manifesto [feedly]
> 
> Hi everyone,
> 
> The extensible web returns from one of our own community groups.
> 
> Extensibility worries me - for many many reasons. But wrt UAAG does a
> non standard extension not using the open web platform need to pass uaag
> as it isn't technically a Web standard?
> 
> Also, in more general terms is this kind of extensibility something we
> should be worried about.
> 
> Cheers
> 
> 
> -------- Original Message --------
> Subject:  The Extensible Web Manifesto [feedly]
> Date:  Tue, 11 Jun 2013 22:52:28 +0100
> From:  Simon Harper <simon.harper@manchester.ac.uk>
> To:  Simon Harper <simon.harper@manchester.ac.uk>
> 
> 
> 
> 
> 
> 
> Shared via feedly <http://bit.ly/SA6Efh> // published on Community and
> Business Groups // visit site
> <http://www.w3.org/community/nextweb/2013/06/11/the-extensible-

> web-manifesto/>
> 
> *The Extensible Web Manifesto*
> 
> *Yesterday, it was made official that our group, by the intermediate of
> his founders, co-signed a manifesto <http://extensiblewebmanifesto.org>
> for a more extensible web.*
> 
> Some of you may ask yourself what it may actually mean, and why this is
> important. This is for this reason we decided to write this blog post.
> 
> An extensible web is a web where web developers are totally incorporated
> in the innovation scheme of the web platform, and can actually build new
> features instead of just relying on the ones browser vendors could agree
> on.
> 
> *Being able to extend the browser means many things.* Firstly, it
> means you can provide a new feature to older versions of a browser, by
> implementing it in JavaScript. Currently, this approach (called
> polyfilling) requires a lot of hacking knowledge because web developers
> are not granted the same access to the browser features than browser
> vendors itself. One of our goal is too make surthat, when possible, web
> browsers leave a little bit of room to web developers to extend the
> browser features, without requiring us to reimplement them from scratch.
> 
> The second reason an extensible web is more beautiful is that, when APIs
> are created inside the walled gardens of the standards committees,
> sometimes mistakes can be made. Mistakes are normal. No process can be
> free of mistakes. However, the problem with the current standards
> process is that it’s slow and irreversible.
> 
> *Once something shipped in a browser, removing it is painful (at least)
> and often impossible. *This is why this process is taking so much time:
> we have to be sure we’re doing the right thing. But, sometimes, web
> developers can’t wait. By shipping a very minimal set of features that
> allow web developers to build libraries around low-level features, we
> can see what works and what doesn’t work and take that in consideration
> when designing the final version of the API. This helps creating better
> in-browser features, and it also helps shipping early implementations
> faster. This approach is called prollyfilling.
> 
> *In short, an extensible web leaves more room for short-term innovation
> and experiments, without compromising a stable and harmonious future.*
> 
> In case you didn’t already, I invite you to read (and sign) the
> manifesto, and look at some of the links provided from there.
> 
> In the name of this community group,
> François REMY
> 
> 
> Visit website
> <http://www.w3.org/community/nextweb/2013/06/11/the-extensible-

> web-manifesto/>
> 
> Sent via feedly <http://bit.ly/SA6Efh> // A news reader for creative minds.
> 
> 
> Also, sorry if this message is brief it's sent from my mobile device.
> 
> Cheers
> 
> --
> Si.
> 
> PS I check my email at 08:00 <x-apple-data-detectors://26> and 17:00 GMT
> <x-apple-data-detectors://27>. If you require a faster
> response please include the word 'fast' in the subject line.
> 
> =======================
> Simon Harper
> My Business Card   - http://simon.harper.name/about/card/

> Schedule a Meeting - http://doodle.com/simon.harper.name

> 
> University of Manchester (UK)
> Web Ergonomics Lab - Information Management Group
> http://wel.cs.manchester.ac.uk <http://wel.cs.manchester.ac.uk/>
> 
> --
> Si.
> 
> PS I check my email at 08:00 and 17:00 GMT. If you require a faster
> response please include the word 'fast' in the subject line.
> 
> =======================
> Simon Harper
> My Business Card   - http://simon.harper.name/about/card/

> Schedule a Meeting - http://doodle.com/simon.harper.name

> 
> University of Manchester (UK)
> Web Ergonomics Lab - Information Management Group
> http://wel.cs.manchester.ac.uk

> 
>

Received on Wednesday, 12 June 2013 20:48:49 UTC