You are never going to agree here, because there is a fundamental philosophical difference between you.
Without wishing to side with either, it seems to be that BAS takes the position that what is written in print in the BS document defines what the actual regulations are, and that no-one other than BS themselves have any power to vary, modify, update or interpret that wording.
Therefore in order to comply with the standard, you have to take it completely literally and all words, unless there is statement in the BS document to the contrary, take their normal meaning in English.
It does not matter that what is printed in the BS doc may not be what those writing the doc intended - that is a different issue. The regs are what they are until amended by the BSI. Therefore anything in any document from any other organisation, regardless of the fact that the people writing it may be some of the SAME people who wrote the standard, cannot be taken to override what is actually written in the BS document, as they are writing with a non-BSI hat on.
Spark123 on the the other hand, takes a more pragmatic and some would argue, more reasonable, approach, which allows commentary on the BS document by people who most (even BAS I suspect) would acknowlege to have a level of knowlege/competence to make such comments, to modify what is stated in the regs, and in Spark's opinion this would not, if implemented in an installation, result in non-compliance.
There is no real way to resolve this difference. In practice, unless there is a court case as a result of someone being injured due to some event in an installation that complies with the regs as interpreted by the OSG, or unless BSI issues amendments to the regs that incorporate changes from the OSG, no-one will ever be know if that installation might be able to be deemed to comply with the regs or not.
But following this discussion helps pass the time, so don't stop
Without wishing to side with either, it seems to be that BAS takes the position that what is written in print in the BS document defines what the actual regulations are, and that no-one other than BS themselves have any power to vary, modify, update or interpret that wording.
Therefore in order to comply with the standard, you have to take it completely literally and all words, unless there is statement in the BS document to the contrary, take their normal meaning in English.
It does not matter that what is printed in the BS doc may not be what those writing the doc intended - that is a different issue. The regs are what they are until amended by the BSI. Therefore anything in any document from any other organisation, regardless of the fact that the people writing it may be some of the SAME people who wrote the standard, cannot be taken to override what is actually written in the BS document, as they are writing with a non-BSI hat on.
Spark123 on the the other hand, takes a more pragmatic and some would argue, more reasonable, approach, which allows commentary on the BS document by people who most (even BAS I suspect) would acknowlege to have a level of knowlege/competence to make such comments, to modify what is stated in the regs, and in Spark's opinion this would not, if implemented in an installation, result in non-compliance.
There is no real way to resolve this difference. In practice, unless there is a court case as a result of someone being injured due to some event in an installation that complies with the regs as interpreted by the OSG, or unless BSI issues amendments to the regs that incorporate changes from the OSG, no-one will ever be know if that installation might be able to be deemed to comply with the regs or not.
But following this discussion helps pass the time, so don't stop