W3C home > Mailing lists > Public > public-device-apis@w3.org > August 2009

RE: ISSUE-4: Versioning Straw Poll

From: Soonho Lee <soonho@sktelecom.com>
Date: Mon, 31 Aug 2009 14:28:03 +0900
To: Robin Berjon <robin@robineko.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <490BF875279F7549BEBA47ADC8F369DB6AA7313B77@SKT-MBXA.SKT.AD>
I Agree.
(We should consider the efficient mechanism for the API versioning based on JavaScript.)

Soonho Lee
   (Lee, Soon-Ho), Ph.D,
Manager, Application Development Team,
Next Internet R&D Center, SK Telecom,
mobile: 010-3128-1483, email: soonho@sktelecom.com
phone: +82-2-6100-2633, fax: +82-2-6100-7807

-----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 9:49 PM
To: public-device-apis@w3.org
Subject: ISSUE-4: Versioning Straw Poll


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
   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
   change names, or ensure that what limited deltas are made do not
   real-world code.

Answers can be:

   - I Agree
   - I Disagree
   - I Don't Care

Please reply by September 1st.


Robin Berjon
   robineko - setting new standards

Received on Monday, 31 August 2009 05:28:48 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:38 UTC