Hi,
Versioning gets revisited :)
I agree to the change, since explicit versioning has been deprecated by many.
We switch to spec soup with implicit versioning.
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.hanc...@access-company.com
-Original Message-
From: public-webapps-requ...@w3.org [mailto:public-webapps-requ...@w3.org] On
Behalf Of Marcos Caceres
Sent: Thursday, November 19, 2009 1:12 PM
To: Robin Berjon
Cc: Larry Masinter; public-webapps@w3.org
Subject: [widgets] The people say NO to 1.0, was Re: [public-webapps] Comment
on Widget URI (7)
On Thu, Nov 19, 2009 at 12:07 PM, Robin Berjon ro...@berjon.com wrote:
Dear Larry,
thank you for your comments.
On Oct 10, 2009, at 19:44 , Larry Masinter wrote:
7) ** EDITORIAL TITLE **
Widgets 1.0: Widget URIs the 1.0 might imply some kind of versioning,
but there is no versioning of URI schemes.
Suggestion: retitle Widget URIs
I have provisionally made this change. I agree with Marcos that it would be
good to do so throughout the widget family of specifications, especially
since there is no reason why versions of its various components need to
evolve in synchronised fashion — one could use P+C 4.2 with WARP 2.7.
Recommendation to the WG: apply the same change throughout.
I strongly agree (and have been pushing this for a long time)... Lets
drop the 1.0 everywhere in the widget family of specs.
--
Marcos Caceres
http://datadriven.com.au
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.
