1
Vote

(X)HTML expert system

description

A goal is to make it impossible to create invalid markup with Wing Beats. Find ways of making this a reality. Ideally intellisense also should provide helpful information about different (X)HTML elements.

comments

Jonsi wrote Feb 14, 2010 at 7:29 PM

  • I think every XhtmlElement method should have a good description available via intellisense.
  • Some way we should statically check if an attribute is valid for an element or not.
  • There should be functionality for validating the output.

mausch wrote Sep 1, 2010 at 11:12 PM

for reference, a discussion posted by Jonsi on statically checking XHTML as in Ocsigen's XHTML.M: http://stackoverflow.com/questions/2813743/f-and-statically-checked-union-cases

mausch wrote Oct 30, 2010 at 8:30 PM

On "An idiom's guide to formlets" (http://groups.inf.ed.ac.uk/links/formlets/) Wadler et al claim "Though well studied (*), static validity checking for XML is not a clear win. It can lead to large types, for instance, and handling polymorphism is challenging."

(*) The Design Space of Type Checkers for XML Transformation Languages, Anders Møller and Michael I. Schwartzbach, http://www.brics.dk/~amoeller/papers/xmltypes/