> MK> PID: TPCS .89c
 >
 > MK> I think that my PID is OK?  Isn't it?  :-)
 >
 > FSC-46 does not cover version identifiers below 1.00, so ".89" may be
 > considered non-conformant.

No, I don't think so.  If you look at FSC-0046.005:


    version     The version of the product including any alpha, beta, or
                gamma status. Only the relevant part of the version should
                be included. I.e. 1.00 should be expressed as 1, 1.10 as
                1.1 and 1.01 as 1.01. Alpha, beta, or gamma status should
                be expressed by appending a / or . followed by a, b, or g
                and optionally a revision indicator, such as a1, b2, etc.
                The maximum length for this field is 10 characters.

Note the part that states: "Only the relevant part of the version
should be included".  So I think that I follow the spec on that
account.


 > Your "c" suffix is non-conformant as it does not designate
alpha, beta or
 > gamma status.

That's right.  I'm going to fix it soon.  If I understand the FSC-0046.005
right, the following PID would be correct:

^APID: TPCS .89b5

It translates to:

TPCS version 0.89beta build 5.

Just one problem though, How should I create a correct PID when my program
goes out of BETA?

Hmm, I think that I'm going to use my format I'm using right now a bit
longer until I have figured something out.

---


 602 610