HTML5ify this file. Refer to #1036406: Keep an eye on the spec: HTML5 DOCTYPE for RDFa for discussion of the doctype. This issue is for all the other stuff, besides the doctype.

CommentFileSizeAuthor
#5 1036406-ab-1.patch737 bytesalanburke

Comments

tim.plunkett’s picture

Version: 6.x-1.x-dev » 7.x-2.x-dev
Anonymous’s picture

Version: 7.x-2.x-dev » 6.x-1.x-dev

xmlns is kinda sorta deprecated in RDFa 1.1... it still needs to be supported by user agents, but it is not recommended for authors to use.

HTML + RDFa Working Draft

The RDFa Core 1.1 [RDFA-CORE] specification effectively deprecates the use of the xmlns: mechanism to declare CURIE prefix mappings in favor of the prefix attribute. While utilizing xmlns: is now frowned upon

This would change the following markup in D7

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" version="XHTML+RDFa 1.0" dir="ltr"
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:dc="http://purl.org/dc/terms/">

to:

<html xmlns="http://www.w3.org/1999/xhtml"
  prefix="content: http://purl.org/rss/1.0/modules/content/
                 dc: http://purl.org/dc/terms/">
Anonymous’s picture

hmmm, I have no 7.x version tag available

tim.plunkett’s picture

Version: 6.x-1.x-dev » 7.x-2.x-dev
alanburke’s picture

Status: Active » Needs review
StatusFileSize
new737 bytes

So here's a start.
We strip out the XHTML stuff from the doctype declaration.

Anonymous’s picture

Status: Needs review » Needs work

As we were talking about in the discussion, should there be a configurable option that allows you to switch between doctypes? Since XHTML5 is a subset of HTML5, would there be anything that would prevent us from making things like the lang attribute a variable? This would allow to switch from lang to xml:lang

This would probably have repercussions throughout the rest of the system though. For instance, anything that puts lang attributes in elements would need to be addressed.

alanburke’s picture

Status: Needs work » Needs review

So, leaving aside of the question of whether we allow xml to be configurable, is the proposed markup good to go?

Anonymous’s picture

I think so.

One thing to note, the version attribute that @alanburke removed is deprecated in HTML5, according to HTML5 Now.

alanburke’s picture

Title: HTML5ify html.tpl.php » HTML5ify html.tpl.php [Doctype]
Status: Needs review » Fixed

Just to note that the patch in comment 5 has been committed.
I'm not sure what else need to be done with this one.
Marking fixed - a new issue can be opened for further changes.

Anonymous’s picture

Sounds good :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.