Re: [widgets] Version string
On Tue, Oct 28, 2008 at 11:00 AM, Marcos Caceres [EMAIL PROTECTED] wrote: Hi Thomas, On Mon, Oct 27, 2008 at 6:13 PM, Thomas Roessler [EMAIL PROTECTED] wrote: You'll want to define what it means for one version string to be greater than another one. We decided a while back that we would not bother doing this. Version are just different. This avoids all the mess that Arve alluded to, and also avoids the Unicode collation mess when of non-ASCII version strings. Right. It's just like an etag, only not an etag 8-) Mark.
Re: [widgets] Version string
On Tue, Oct 28, 2008 at 3:29 PM, Mark Baker [EMAIL PROTECTED] wrote: Right. It's just like an etag, only not an etag 8-) LOL! right :) -- Marcos Caceres http://datadriven.com.au
[widgets] Version string
Hi All, I would like to relax a valid version string to be any string. The reason I want to do this is to make it easier to parse a version string without requiring any special processing (any string will do). We will still recommend the MIDlet Suite Versioning where Version numbers have the format Major.Minor[.Micro] (X.X[.X]). This affects the widget element's version attribute and parts of the Updates spec in a minor way. Kind regards, Marcos -- Marcos Caceres http://datadriven.com.au
Re: [widgets] Version string
You'll want to define what it means for one version string to be greater than another one. -- Thomas Roessler, W3C [EMAIL PROTECTED] On 27 Oct 2008, at 17:27, Marcos Caceres wrote: Hi All, I would like to relax a valid version string to be any string. The reason I want to do this is to make it easier to parse a version string without requiring any special processing (any string will do). We will still recommend the MIDlet Suite Versioning where Version numbers have the format Major.Minor[.Micro] (X.X[.X]). This affects the widget element's version attribute and parts of the Updates spec in a minor way. Kind regards, Marcos -- Marcos Caceres http://datadriven.com.au
Re: [widgets] Version string
We came up with an approach at OpenAjax Alliance for version strings where the string must begin with N.N (or N.N.N or N.N.N.N) but can contain arbitrary alpha text after the number value. Then we defined how to do numeric comparisons between the leading numeric parts of two different version strings. * http://www.openajax.org/member/wiki/OpenAjax_Hub_1.0_Specification_Libraries Jon Thomas Roessler [EMAIL PROTECTED] Sent by: To public-webapps-re Marcos Caceres [EMAIL PROTECTED] [EMAIL PROTECTED] cc public-webapps 10/27/2008 11:13 public-webapps@w3.org AMSubject Re: [widgets] Version string You'll want to define what it means for one version string to be greater than another one. -- Thomas Roessler, W3C [EMAIL PROTECTED] On 27 Oct 2008, at 17:27, Marcos Caceres wrote: Hi All, I would like to relax a valid version string to be any string. The reason I want to do this is to make it easier to parse a version string without requiring any special processing (any string will do). We will still recommend the MIDlet Suite Versioning where Version numbers have the format Major.Minor[.Micro] (X.X[.X]). This affects the widget element's version attribute and parts of the Updates spec in a minor way. Kind regards, Marcos -- Marcos Caceres http://datadriven.com.au inline: graycol.gifinline: pic20792.gifinline: ecblank.gif
Re: [widgets] Version string
On Mon, 27 Oct 2008 20:11:20 +0100, Jon Ferraiolo [EMAIL PROTECTED] wrote: We came up with an approach at OpenAjax Alliance for version strings where the string must begin with N.N (or N.N.N or N.N.N.N) but can contain arbitrary alpha text after the number value. Then we defined how to do numeric comparisons between the leading numeric parts of two different version strings. So, you are allowing something like 2.6.27.4-foo3 and 2.6.27.4-foo4 or 1.2.3.gcc4.qt3 1.2.3.gcc4.qt4 Is any judgment whether one version in these cases is newer than the other? If so, which is newer of the following? 1.2.☺ 1.2.☻ -- Arve Bersvendsen Developer, Opera Software ASA, http://www.opera.com/
