ABPSC — Need separate RFC process variant for breaking versions of existing specs

It's frequently the case that a new version of an existing OMG spec needs major, or breaking, changes. Where the needs are clear (e.g. incorporate industry changes or a new version of a base external spec such as OWL) we've successfully used the RFC process for this rather than a new round of RFI/RFP.
This, however, does not fit the P&P description of the RFC process as being an external spec brought into OMG. And there are several aspects that do not directly apply such as production usage, lack of competition etc. Though it as appropriate to give people the opportunity to object to proposed/lacking features.
Hence the P&P should be updated to encompass this RFC variant.