Services.xsd

[Cantor, Scott]

On 12/17/13, 12:14 PM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:

>> I don't know what Chad had done, but I've always used the schema version
>> attribute to track the software version in which I shipped a particular
>> version of the schema, just for tracking purposes.
>
>Any suggestions for a version number to start with?  I'm inclined to
>introduce this as "3.0.0" - a number which is note zero or one and could
>be
>implied as having something to do with V3 of the IdP...

Yes, I use the full version (though historically I tended not to use the
third digit, but that wasn't really wise of me).

I think it would be fairly confusing to start our versioning for the
actual jar artifacts we create as 1.0.0 at this point, even though that's
technically possible to do.

I have done it: I labeled the SP's core library as V1.0 when I shipped SP
V2.0, but library versions in C/C++ matter a little more than in Java.

-- Scott