When the SWG decided to not call the ModSpec a Policy, the SWG members introduced a strange semantic twist that causes ambiguities and confusion. Further, this linguistic artifact is inconsistently implemented in the ModSpec, causing additional confusion.
In this standard, other documents which may be standards but are being tested for conformance to this standard are referred to as “specifications.” The purpose of this linguistic artifact is to prevent confusion between this standard and the standardization targets of its requirements
If we agree that the ModSpec is a Policy, then this linguistic artifact is no longer required. Therefore:
Recommendation: In this document, OGC Standards shall be referred to as "standards" or "candidate standards" or "draft standards" and not "specifications".
When the SWG decided to not call the ModSpec a Policy, the SWG members introduced a strange semantic twist that causes ambiguities and confusion. Further, this linguistic artifact is inconsistently implemented in the ModSpec, causing additional confusion.
In this standard, other documents which may be standards but are being tested for conformance to this standard are referred to as “specifications.” The purpose of this linguistic artifact is to prevent confusion between this standard and the standardization targets of its requirements
If we agree that the ModSpec is a Policy, then this linguistic artifact is no longer required. Therefore:
Recommendation: In this document, OGC Standards shall be referred to as "standards" or "candidate standards" or "draft standards" and not "specifications".