On 21/05/2011 8:12 AM, Andy Lester wrote: >> My reason for raising this now is that the HTML5 spec elements are starting to appear on documents on the internet, and with these tags missing from HTML::Tagset, it impacts the effectiveness of other libraries that depend upon it. > Haven't looked at the patch, but I think we need to talk about high-level thoughts about handling HTML5. > > * Should we have separate sets of tags for HTML 4 and 5? > * If so, should it be handled be one module, or should it get split into to? > * Should we have strict and loose definitions of tags, going forward? One of the things I've run into is tag attributes that are recognized by browsers, but not in the spec. > Thoughts? I'm surprised that 5 months have slipped by and no one is interested in discussing adding HTML5 entities to HTML::TagSet library, and the large swathes of modules this will impact and/or (hopefully) improve. Right now, trying to use HTML::TreeBuilder::XPath is futile when processing HTML 5 documents, and there are probably other very good libraries out there that are similarly incapacitated. I'm not saying using HTML 5 now as a 'draft' is good practice, but browsers are implementing it, and sites are using it. Last draft was published 25 May 2011, current editors version is dated 21 Oct 2011 (so only 3 days ago). There's a core set of new elements that look like they are set to stay (section, canvas, etc), so should HTML::TagSet include them now, and be updated again for other major changes that come along? I suggest that the major elements of HTML 5 are added to HTML::Tagset as is. At least we get some immediate relief to a burning issue. HTML::TagSet can then be split at leisure into separate modules (HTML::TagSet::HTML5, HTML::TagSet::HTML4, HTML::TagSet::XHTML, etc) and a wrapper on top to combine them (and resolve conflicts between them) over the next few years if required. James -- /Mobile:/ +61 422 166 708, /Email:/ james_AT_rcpt.toThread Previous | Thread Next