I like the terminology change from "constraints" to "interdependencies".
The new term is much clearer what is meant, since the concept is about the
relationship between the values of several attributes, not the list of
possible values for a single attribute.
From: Norbert Schade [mailto:email@example.com]
Sent: Thursday, July 12, 2001 13:52
To: UPD group
Subject: UPD> constraints -> interdependencies
In the sample implementation group we are close to constraints handling.
That is the right time to make a simple change I've in mind for quite a
We will change the wording in the whole constraints area.
To speak of 'constraints' the way we do it is not correct.
Constraints are describing the available entries of a list or so. See some
of the XML tools. The term is exactly used in that way. So other than the
fact we are doing it wrong, it is also confusing.
From now on we speak of interdependencies between features and mean the same
This will require some renaming of files, elements and attributes, not to
speak of the documentation.
<ftp://ftp.pwg.org/pub/pwg/upd/Current_Version/> you can find a temporary
documentation document 'UPDF Constraints.doc'. This is supposed to disappear
soon, while the content is moving to the 'UPDF Functional Specification'
(the big document growing these days step by step). In this final document
it will be referred to as interdependencies only.
We are not changing any structure nor any other design rules because of
this. It's only a name change!
I will start with the changes on Monday, 7/16/01. If you have any concern,
let me know before.
Principle Software Engineer
Host Software Group
Oak Technology, Inc.
10 Presidential Way
Woburn, MA 01801
email: firstname.lastname@example.org <mailto:email@example.com>
This archive was generated by hypermail 2b29 : Mon Jul 16 2001 - 13:29:28 EDT