How should Shindig handle invalid gadget specs?

[Tim Moore]

I've been trying to debug a problem with a Shindig-based Java gadget  
container we're building, and the todo gadget at http://www.labpixies.com/campaigns/todo/todo.xml 
 that is used as an example throughout Shindig.

Long story short, I noticed that the todo gadget spec contains a head  
end tag and a body start tag. These are forbidden by the gadget spec <http://code.google.com/apis/gadgets/docs/fundamentals.html#Content_Type 
> because the gadget renderer generates its own head and body tags,  
but since they're in there, the generated HTML ends up containing  
malformed HTML.

So I have two thoughts: first, maybe this isn't the ideal example  
gadget to use; second, maybe Shindig should catch this when parsing  
the gadget spec file and either fail fast or strip the tags out  
instead of producing invalid HTML.

What do you think?

The reason this is a problem for me specifically is that we have a  
filter set up (sitemesh) that parses all HTML output, and its choking  
on this due to having two closing head tags.

--
Tim Moore