Yair – (see my other email proposing)
The definition of the variable is not the place to make those distinctions. The state diagram defines that you don’t set these variables true except when you’ve passed through detection and classification.
From: Yair Darshan [mailto:YDarshan@xxxxxxxxxxxxx]
Sent: Thursday, October 19, 2017 6:21 AM
To: STDS-802-3-4PPOE@xxxxxxxxxxxxxxxxx
Subject: Re: [802.3_4PPOE] Definition of alt_pwrd_pri
Hi Lennart,
I understand the principle you want to follow. Please note that the additional description in the TRUE case of detection and classification was added due to the importance of not power unless these action where done while in the FALSE case
obviously they are not required.
Logically there is no reason to make the changes you propose.
The question is now if to have for that matter short description or clear description. In this case I preffer clear description i.e. keep it as is but to clean the “will” issue.
Yair
From: Lennart Yseboodt [mailto:lennartyseboodt@xxxxxxxxx]
Sent: Thursday, October 19, 2017 10:27 AM
To: STDS-802-3-4PPOE@xxxxxxxxxxxxxxxxx
Subject: [802.3_4PPOE] Definition of alt_pwrd_pri
EXTERNAL EMAIL
Hi all,
We discussed this at the last meeting and I feel we did not end up with a good solution.
The definition of variables should be restricted to what the variable does or represents.
These variables' "TRUE" description includes behaviour that (should have) happened in the past, as well as making a forward looking statement.
If we look at how these variables are actually used, the definition really is very simple:
FALSE = The PSE is not to apply power to the XYZ Alternative.
TRUE = The PSE is to apply power to the XYZ Alternative.
Objections ?
Lennart