XHTML Ruby specification error handling rules


I have been looking at the Ruby specification:


...with the intent of writing test cases and adding Ruby support to the 
HTML5 specification [1], as a step towards encouraging implementations of 
Ruby in Web browsers.

However, I have run into a problem. In the conformance section, it states 
that an interpreter must reject non-conformant Ruby markup, but Web 
browsers are effectively unable to do this, primarily because Web authors 
have been conditioned to expect browsers to handle errors, but also 
because conformance checking is an expensive operation, and rendering is a 
performance-sensitive operation.

To be able to put Ruby in HTML5, therefore, I need a Ruby processing model 
that is well-defined even in the face of bogus markup, yet does not 
require careful checking of the document conformance, and does not involve 
having to reject documents that have non-conforming markup. (Such a model 
would also, ideally, be compatible with the CSS Ruby model.)

Unfortunately I am not well-versed in Ruby matters and therefore do not 
know how to write such a processing model.

Would anyone be able to write such a processing model, or give me enough 
informantion on typical use cases, typical authoring mistakes, and the 
like, to enable me to do so?

Incidentally, is there a document somewhere where I can read the CR 
implementation report for Ruby? I would be interested in examining the 
test suite that was used to verify interoperability, as well as testing 
the implementations that were found to be interoperable to see how they 
handle various error conditions.

-- Footnotes --
[1] http://whatwg.org/specs/web-apps/current-work/

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

Received on Saturday, 2 July 2005 16:17:43 UTC