RE: ISSUE-4: Versioning Straw Poll

Hi All,

I am sorry for my delayed answer and missing the deadline.
I am in the comfortable situation of replying after the others have done it already.

I do not want to disagree, I try to care.

I accept the fact that the versioning - as principle - will be implicit and/or realized by different means than version identifiers.
I can live with it.
So I agree.

Thanks,
Marcin

Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452  |  Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanclik@access-company.com

-----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 2:49 PM
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/



________________________________________

Access Systems Germany GmbH
Essener Strasse 5  |  D-46047 Oberhausen
HRB 13548 Amtsgericht Duisburg
Geschaeftsfuehrer: Michel Piquemal, Tomonori Watanabe, Yusuke Kanda

www.access-company.com

CONFIDENTIALITY NOTICE
This e-mail and any attachments hereto may contain information that is privileged or confidential, and is intended for use only by the
individual or entity to which it is addressed. Any disclosure, copying or distribution of the information by anyone else is strictly prohibited.
If you have received this document in error, please notify us promptly by responding to this e-mail. Thank you.

Received on Wednesday, 2 September 2009 14:08:38 UTC