Hej,

I'm looking for a solution that my site is w3c XHTML + RDFa validate but at the moment they does not.

I have create a subtheme with the xhtml starterkit and I use teh newest version 7.x 2.1.

I become 10 errors and 1 warning. I'm looking all the day to find a way to validate this error messages but I can't find.

When I disable the search block then I have 1 error less before. It is a block problem?

can you explain me to solve this?

my site my site

kind regards
drew

Ps: sorry for my bad english

Comments

himerus’s picture

himerus commented

Check this issue on the Boron HTML5 theme regarding HTML5 validation with RDF: http://drupal.org/node/887600#comment-3350498

I have not personally tested turning off RDF to see if it would properly validate after that, but that would be my hope... the HTML5+RDFa stuff is still very unclear and beta for any theme trying to use it.

It will likely not be able to validate w3c standards for quite some time with RDFa on.

rowbotony’s picture

rowbotony commented
Version: 7.x-2.1 » 7.x-2.x-dev
Category: support » bug

Hi, I think I am having this issue to. I'm using the XHTML Starterkit, I created it with Drush and Omega Tools. I converted my home page to Omega and while validating at the W3C get the following errors. I don't know what it means, but here it is. My URL is www.groffweb.com if you want to check it out and validate it... or not, this doesn't seem to affect the functionality - in fact the theme renders properly even in IE6! :)

Errors found while checking this document as XHTML + RDFa!

Info No Character encoding declared at document level

Line 15, Column 17: there is no attribute "charset"

himerus’s picture

himerus commented

Ahh... I mistook the title of the issue as an HTML5+RDFa validation issue. I'll have to look further into this one. Thanks for the report(s).

drew29’s picture

drew29 commented

hello,

I'm again I wanted to ask carefully whether it might already have a solution. or I can somehow help to narrow down the problem.

Greetings!

himerus’s picture

himerus commented

did you look at this link? http://drupal.org/node/887600#comment-3350498

Currently the HTML5+RDFa doctype (when the RDF modules is enabled in D7) does not validate. (and might not for quite some time)

According to the link above, you can disable the RDF module, and check validation, and it "should" pass. (unless there is another issue or two in Omega) (I haven't tested validation in a while)

drew29’s picture

drew29 commented

Hello himerus,

for me it is a problem in the XHTML + RDFa doctype and not HTML5 #RDFa ;-)

greetings!
drew

citywizz’s picture

citywizz commented

Same pb for us. I'll try to debug it.

www.kabyle.com

drew29’s picture

drew29 commented

@kabyle.com

maybe have you found a solution?

kind regards
drew

citywizz’s picture

citywizz commented

You can find an early solution here I put the code in html.tpl.php

http://blog.3kbo.com/tag/drupal-7/

fubhy’s picture

fubhy commented
Status: Active » Fixed
Midas Man’s picture

Midas Man commented

I'm building my site using Drupal 7 and my theme is heavily based on Boron. I enable the RDF module and I get around 76 validation errors with 26 warnings. I turn it off and my page has perfect html5 validation.

I think the reason is down to the fact the HTML5 w3c recommendations are moving all the time with HTML5 and a decision has not been made on RDF yet as that is a new technology also. I could just be talking utter shash though. ;o)

rowbotony’s picture

rowbotony commented

I've just decided to disable the RDF module on my site for now, issue resolved for me.

himerus’s picture

himerus commented

Yeah, this does just fall back to HTML5 + RDFa not being a "truly" accepted doctype yet... it DOES work... but won't validate (as seen on other issue queues as well)

drew29’s picture

drew29 commented

sorry I do not think I'm smart enough. I do not solve the problem.

Encoding: UTF-8
Doctype: XHTML + RDFa
Root Element: html

if I disable the RDF module and delete the cache I have the same problem and although I like the doctype in Post # 9

<DOCTYPE html PUBLIC "- / / W3C / / DTD XHTML + RDFa 1.1 / / EN"
     "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd>
<html xmlns = "http://www.w3.org/1999/xhtml" xml: "? lang = php print $ language-> language> "version =" XHTML + RDFa 1.1 "dir ="<? php print $ language-> dir; ?>"<? php print $ rdf_namespaces; ?>>

:-( I can not change anything, because maybe help someone else. As I said, it's about xhtml + RDFa and HTML5

Kind regards
moved

drew29’s picture

drew29 commented
Status: Fixed » Needs work

Sorry forgot to change the status

fubhy’s picture

fubhy commented

Yeah, this does just fall back to HTML5 + RDFa not being a "truly" accepted doctype yet... it DOES work... but won't validate (as seen on other issue queues as well)

drew29’s picture

drew29 commented

sorry, i don't understand it i think my english is to bad :-( i use the omega xhtml starterkit.

use the xhtml starterkit html5 too?

i have test another template with XHTML + RDFa and this tempklate is valid i'm very confused about that.

can you explain me where is my mistake?

greetings
drew

fubhy’s picture

fubhy commented

drew29 I see that you are german. Please come to #drupal.de or #drupal-omega so I can help you in german. Maybe that solves our misunderstanding. I will ofc keep this Issue updated with the solutions that we find for you.

fubhy’s picture

fubhy commented

I fixed the double class attribute on zones and also changed hgroup to div in region--branding.tpl.php for the XHTML starterkit. The "placeholder" attribute validation error (on the search form) and the meta property (charset) error will have to be fixed by himerus as I don't want to fiddle with his code too much (the 2.x branch is out of my scope, actually). With the last changes (pushed into the dev version and also available here: https://github.com/ThemeGeeks/Omega/tree/7.x-2.x should give you 9 errors less. You also have a few minor errors that are related to the "map" HTML tag. This is not related to Omega.

fubhy’s picture

fubhy commented
Status: Needs work » Fixed

drew moved to 3.x

Status: Fixed » Closed (fixed)

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