- From: Ennals, Robert <robert.ennals@intel.com>
- Date: Thu, 3 Sep 2009 22:23:25 +0100
- To: Robin Berjon <robin@robineko.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
I agree. -----Original Message----- From: public-device-apis-request@w3.org [mailto:public-device-apis-request@w3.org] On Behalf Of Robin Berjon Sent: Thursday, August 27, 2009 5:49 AM To: public-device-apis@w3.org Subject: ISSUE-4: Versioning Straw Poll Hi, I'd like to get a rough view of where people stand with respect to API versioning, so here's a straw poll. Straw polls are different from formal votes in that they aren't binding for the WG - they just provide for a quick snapshot to get a feel for the state of a debate. Also, answers are per participant, not per company (though we'll notice ballot stuffing of course). Here's the SP: This house believes that explicit version mechanisms on an API, such as have been done elsewhere using for instance hasFeature(), a version attribute on interface object, or a version parameter passed to a constructor are not useful in a web context and should be forsaken. Future revisions to given interfaces should either be strictly additive, change names, or ensure that what limited deltas are made do not break real-world code. Answers can be: - I Agree - I Disagree - I Don't Care Please reply by September 1st. Thanks! -- Robin Berjon robineko - setting new standards http://robineko.com/
Received on Thursday, 3 September 2009 21:24:12 UTC