Subject: OASIS TC Process Policy -- Precedence of separate text files overnormative specification text
In reviewing the updated TC Process, we made note that the new policy on precedence of separate text files over the specification text (Section 2.18) is inconsistent with what DPWS 1.1 and WS-Discovery 1.1 explicitly declare in the body of the specifications. For example, DPWS 1.1 Section 7 (Conformance) says “Normative text within this specification takes precedence over normative outlines, which in turn take precedence over the XML Schema [XML Schema Part 1, Part 2] descriptions, which in turn take precedence over examples.” This is exactly the opposite of the precedence declared in Section 2.18 of the updated TC Process.
In adopting the new Process, did the OASIS Board indicate whether the precedence specified in the Process is intended to override any other precedence declared within the body of approved OASIS Specifications? Or is the precedence in Section 2.18 intended only to be a “default” precedence when no other precedence is declared within the body of the specifications?
Thanks very much for helping us to understand the impact of this new policy on our specifications.
Co-Chairs, OASIS WS-DD TC
Toby Nixon | Senior Standards Program Manager | Windows Device and Storage Technologies | Microsoft Corporation