I find sometimes the arguments go round-and-round and maybe seeing something like this could help focus minds.
We have guidance that outlines why we need a P/P service specification. This WG is about determining what ought to be included, at minimum. And with consensus.
This goes to the idea of a best practice, otherwise called Copy Shamelessly.
Fact is there isn't a whole lot of 'new' in this universe. So it would save us a lot of to-and-froing if we co-opt and use this one as a template, look at every clause and establish from them the attributes or principle we want to endorse for the [P/P] specification. If the clause fits we go with it.
-Carlton