Subject: [storm] T10 Version Descriptors

From: Ralph Weber <[email-masked]>
Date: Tue, 16 Jun 2009 20:13:16 -0500

Ah! T10 Version Descriptors! Finally, a subject which I
know something about.

Allocating a T10 Version Descriptor is a cakewalk. All
you need to do is arrange for T10 to pass a motion that
makes a specific version of a specific working draft
(e.g., SAM-5 revision 44) a "committee draft". An
approved motion of that form will cause the assignment
of a Version Descriptor in the next SPC-4 revision.

Regarding the ability to calculate Version Descriptor
values ...

Kiss that notion goodbye.

Over the years I have become more and more whimsical
in the assignment of the "revision" component of version
descriptors (see SPC-4 r20a, citation below, annex D.8).
Some claim it is Alzheimer's setting in, and maybe they
know something I have missed. The truth is I did not follow
the "revision" algorithm back when I claimed there was one.

So, I have shed all pretense of there being any set formula.

All the best,

.Ralph
aka the SPC-4 editor

SPC-4 r20a reference
http://www.t10.org/cgi-bin/ac.pl?t=f&f=spc4r20a.pdf