RE: [sdd-comment] VersionRangeType

[Julia McCarthy <julia@us.ibm.com>]

Use of a version in a version range implies that the values can be compared - even if the values are "Joe" and "Sam". Their use in a version range implies that it makes sense to think of those values as a range and that the runtime knows how to treat them as a range. In the Joe and Sam example, if Fred was the actual version, the runtime would know whether or not Fred fell within the Joe to Sam range.

I think what you are suggesting is that if a fix name is used in a range, then the semantics of the SDD are that the fixname can also be compared using range semantics.

It would clarify this discussion to have you (Jason and/or Randy) provide the specification text that explains what fix name and version name mean in the different contexts. More specifically, when is it assumed that the values provided have sequential semantics (i.e. it can be known that one value is greater than another) and when is this not assumed. Given your proposal, what would you tell people about how to express requirements on Windows service packs (as fix names) vs. Windows individual fixes (e.g. KB000059)? Both would be represented as fix names, but both could not be used in a version range.


Julia McCarthy
Install Strategy and Development
julia@us.ibm.com
877-261-0391



Randy George/Austin/IBM

Randy George/Austin/IBM

02/19/2008 01:36 PM

To	Jason Losh <Jason.Losh@sas.com>
cc	Julia McCarthy/Raleigh/IBM@IBMUS, "sdd-comment@lists.oasis-open.org" <sdd-comment@lists.oasis-open.org>
Subject	RE: [sdd-comment] VersionRangeType

Jason,
You are correct in that version is not a numeric that can be compared. We had this discussion at the F2F in FLA.

Regards,
Randy George

Senior Technical Staff Member
Tivoli Software, IBM Software Group
Austin, TX
(512) 838-0752 T/L 678-0752
Jason Losh <Jason.Losh@sas.com>

Jason Losh <Jason.Losh@sas.com>

02/19/08 10:58 AM

To	Julia McCarthy/Raleigh/IBM@IBMUS
cc	"sdd-comment@lists.oasis-open.org" <sdd-comment@lists.oasis-open.org>
Subject	RE: [sdd-comment] VersionRangeType

Hi Julia,

How are the semantics of FixName any different than the semantics associated with the VersionRangeType based upon my proposal? MinVersion and MaxVersion are of type VersionType which is xsd:string. FixName is also xsd:string. How are the greater than/less than comparison's semantically different? There is no rule that MinVersion and MaxVersion can't be "Joe" or "Sam" respectively and as such the comparison issue raised for FixName is also inherent in MinVersion/MaxVersion. I see no difference.

The issue you raised is why I recommend we revisit Version in the 1.1 version of the specification. For 1.0, however, I am looking for a tweak that gets us closer to having something that works and I think adding FixName to MinVersion/MaxVersion gets us much closer.

And I would like to amend my proposal based on Randy and I's exchange last night and state that we should remove FixName from VersionRangeType and only have FixName associated with MinVersion and MaxVersion.

Cheers,
-Jason


From: Julia McCarthy [mailto:julia@us.ibm.com]
Sent: Tuesday, February 19, 2008 10:17 AM
To: Jason Losh
Cc: sdd-comment@lists.oasis-open.org
Subject: Re: [sdd-comment] VersionRangeType

This proposal will not accomplish what you want. Fix name can only be compared for equality. Let's use your example of a min version of Windows 2000 with SP1 and max Version of Windows Vista with SP1. If the actual os is Windows 2000 with SP4, all you know is that it is not Windows 2000 with SP1. You do NOT know if it is within the required range. SP1 and SP42 are fix names and the semantics of fix name do not involve comparison for greater or less than. All you can know is that SP1 does not equal SP4.

Julia McCarthy
Install Strategy and Development
julia@us.ibm.com
877-261-0391



Jason Losh <Jason.Losh@sas.com>

Jason Losh <Jason.Losh@sas.com>

02/18/2008 04:33 PM

To	"sdd-comment@lists.oasis-open.org" <sdd-comment@lists.oasis-open.org>
cc
Subject	[sdd-comment] VersionRangeType

Hello SDD TC,

In the SDD schema posted for review, there is a complex type called VersionRangeType that includes an element called FixName. FixName in this case is associated with the range and not the MinVersion or MaxVersion elements. I suggest adding FixName to MinVersion and MaxVersion in addition to leaving FixName associated with the overall range. By adding FixName to MinVersion and MaxVersion, one can specify a minimum and maximum version that includes fix information specific to MinVersion and MaxVersion, for example, any Windows operating system between Windows 2000 SP1 and Windows Vista SP1.

Regards,
-Jason

_________________
Jason Losh
Software Manager, Installation Technologies
Release Management Division, SAS
Office: (919) 531-4759
Mobile: (919) 607-5709
Email: Jason.Losh@sas.com<mailto:Jason.Losh@sas.com>
http://www.sas.com

SAS ... THE POWER TO KNOW




--
This publicly archived list offers a means to provide input to the
OASIS Solution Deployment Descriptor (SDD) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: sdd-comment-subscribe@lists.oasis-open.org
Unsubscribe: sdd-comment-unsubscribe@lists.oasis-open.org
List help: sdd-comment-help@lists.oasis-open.org
List archive: http://lists.oasis-open.org/archives/sdd-comment/
Feedback License: http://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Committee: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sdd