Requirement 2.1.5.2

["Josh Allen" <jallen@macrovision.com>]

I had an action item to send a rewording of requirement 2.1.5.2 which
relates to superseded & obsoleted fixes.

The text currently reads: "The SDD specification must support the
ability for the author to define information about the fixes superseded
or obsoleted by the deployment of a fix or fixes."

First, I agree with the definitions that Debra sent in her recent
document of superseded (replaced by approximate functionality) and
obsoleted (no longer necessary at all).  I wonder if we need both
concepts for fixes.  It seems that they may have the same semantics:
"this fix has what you need."  I'd recommend that we only have the
concept of superseded fixes.  I think obsoletion is a great concept to
apply to other things than fixes (like package content).

Second, my issue with this requirement was that I felt it was too
restrictive.  By saying "...by the deployment of a fix or fixes," we
imply that past fixes can only be superseded/obsoleted by other fixes
(as opposed to new versions).  I don't think we want that.

I would recommend that the phrase read:
"The SDD specification must support the ability for the author to define
information about the fixes superseded or obsoleted by the deployment of
fix(es) or updated versions."

Would love to know the thoughts of the group.

Thanks,
Josh

________________________________________________________

Josh Allen
Manager, Software Development
Zero G - a Macrovision company
w: 415.512.7771 | f: 415.723.7244
jallen@macrovision.com
www.ZeroG.com | www.macrovision.com
 
Zero G is now part of Macrovision Corporation, offering 
a combined suite of products to help software publishers and 
IT departments maximize the value of their software.
________________________________________________________