RE: [wsdm][UPlat] Simplifying Versioning Definition

["Jeff Bohren" <jbohren@opennetwork.com>]

We seem to be recomending a three level version number of the form
major.minor.revision. The MS recommended practice for defining .NET web
services is a four level version number. That is not a requirement, but
most web services developed in VS.NET (whether VB.NET, C#, Managed-C++,
or something else) will have a four level version (e.g. 5.0.1.0).

I would recommend that we either be agnostic on the number levels in a
version and to what their meaning is, or define a set that has at least
4 levels.

Jeff Bohren
Product Architect
OpenNetwork Technologies, Inc
 
Try the industry's only 100% .NET-enabled identity management software.
Download your free copy of Universal IdP Standard Edition today. Go to
www.opennetwork.com/eval.
 


-----Original Message-----
From: Mark Ellison [mailto:ellison@ieee.org] 
Sent: Tuesday, November 11, 2003 5:00 PM
To: Andreas Dharmawan
Cc: wsdm@lists.oasis-open.org
Subject: Re: [wsdm][UPlat] Simplifying Versioning Definition


Hi Andreas,

The text below describes "version" as consisting of a "major version 
number", a "minor version number", and, the "revision number".

para 2 of the "How" sxn mentions the "minor revision", and, later, the 
"revision number".  Possibly the "minor revision" term in para2 should 
read "minor version number"?

In para 3 of "How", possible wording change:

"...version successor pointing to the new version..."  could be 
"...version successor pointing to the [successive | next]  version..."

I think "successive" (or, "next")  would agree more with "previous" than

"new" does.  Of course, I may have misunderstood the text- possibly the 
version successor pointer always points to the "newest" version?

Regards,

Mark

Andreas Dharmawan wrote:

>Versioning:
>-----------
>
>What?
>-----
>Version is an attribute of a Webservice infrastructure components 
>(service, interface, endpoint) identifying a sequence of copies of the 
>components incorporating new modifications.
>
>The following will be moved to the "How" section:
>-----------------------------------------------
>Each version is identified by the version information, following a 
>certain specified format signifying the major version number, minor 
>version number, and the revision number.
>
>Typically an increment in the major version signifies a substantial 
>increase in the function of the Webservice or partial or total 
>re-implementation. An increment of the minor revision signifies a small

>increase in the functions of the Webservice such as an extension to the

>existing functionality. The revision number increases each time the 
>Webservice is changed in any way such as bug fixes or patches.
>
>Version number is accompanied by other version attributes; change 
>description describing what has changed in a revision compared to the 
>previous one, version predeccesor pointing to the previous version, 
>version successor pointing to the new version, etc.
>
><followed by using namespace and targetNamespace discussion> ...
>
>Feedback?
>
>Thanks.
>
>Andreas
>
>
>To unsubscribe from this mailing list (and be removed from the roster 
>of the OASIS TC), go to 
>http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgro
>up.php.
>
>
>  
>


To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgrou
p.php.