It's one feature as well as an incrementing of the standard revision header. I honestly don't really care what this spec is called, but having it match the revision header makes the most sense to me.
Well, that header field is there to indicate which version of the Z-Machine Standard the interpreter implements, so if you increment that number, you're making a new revision of that standard. My objection is not that this proposal is called "The Z-Machine Standard 1.2" -- that's what it should be called -- but that it isn't addressing the things that a standard revision ought to address.
(I'm also not sure what the purpose of selector $01 is, since the standard revision number is already stored in the header, and any game that uses @gestalt will have read it from there.)
Further clarifications could be made by a 1.1.1 spec, or even a 1.3 spec (whether or not that would entail incrementing the revision header again.)
It would have to be 1.3, since the header field only has room to store two parts of the version number.
How strongly do people feel the need for a further set of clarifications? It might be helpful to collect a list of issues, even if there isn't consensus on all of them. What I don't want is to tie them all to my spec. I'd like to be able to introduce some function acceleration to Parchment in time for the next I7 release and would prefer the spec to be finalised by then.
Have you had any luck with pattern matching?