Currently, Xorg consists of multiple pieces, xserver being just one of them, using the X11 protocol. X RandR is another component.
Let's just take x.org 7.6 for example, which has in it xserver 1.9, xrandr (it was version 1.2 IIRC), and other pieces - piece3, piece4, piece5, etc.
A new X12 would consist of wayland, xrandr, and other pieces. piece3, piece4, piece5, etc.
Now, I realize that all of these said pieces would most likely be re-written from scratch, with whole new parts. But all I'm asking is why could not Wayland sit at the heart of the new X12 considering how far along it already is? Especially considering that Xwayland (should) come along nicely as a good X11 compatibility layer.
It doesn't have to be called x-anything..... ever. But with continued advancements, as the X.org crew creates what it sees as its new vision for a new X12 protocol, they could bolt on/bolt in the new pieces onto the already completed Wayland.
I think the right question to ask is who will work on it, in case it exists. I mean, the experienced X guys are mostly centered on working on Wayland, and that's their bet for the future. X12 would probably require a development time similar (greater, actually, because even when they have most of the infrastructure done and most of the work is shrinking the protocol, it still requires some protocol design, and THEN actual coding) to the one Wayland still needs to be mainstream.
On the Wayland as heart of X12, I think if it would exist (is there any need for it?) it would make sense to reuse the Wayland protocol (and library) as the buffer manager of the X12 protocol. Of course, an X12 would require more than just Wayland, as it's proposer said.
Why? Who cares? Who needs? What developer talked about it in this week?We Have Mir & Wayland, But There Still Could Be X12