teofili, I can put up a patch for this one. But, it'd convenient to change both suggestion and spellcheck result rows. Btw, I'm just planning to support 2 columns (which can probably be extended later as you hinted above) - rep:spellcheck and jcr:score (where I'm planning to put value of weight of each suggestion as jcr:score). Does that sound fine?
Also, this is clearly a backward compatibility issue. I'm not sure how we deal with that. Do we just document it? What our take usually about backporting (to say 1.2 or 1.0) for such issues?
+1 - Given we already have notion of row and column such data can be mapped to those constructs and not require user of API to parse them