Bug 1028 – Using the RDFa attribute "content" is marked as an error

NOTE: The current preferred location for bug reports is the GitHub issue tracker.

Bug 1028 - Using the RDFa attribute "content" is marked as an error


Summary:	Using the RDFa attribute "content" is marked as an error

Status:	RESOLVED INTENTIONAL

Product:	Validator.nu
Classification:	Unclassified
Component:	General
Version:	HEAD
Hardware:	All All

Importance:	P2 minor
Assigned To:	Nobody

URL:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-12-16 12:38 CET by Jan Egil Kristiansen
Modified:	2015-12-16 12:45 CET (History)
CC List:	1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jan Egil Kristiansen 2015-12-16 12:38:17 CET

Using the content attribute as in http://www.w3.org/TR/xhtml-rdfa-primer/#using-the-content-attribute example 35 is marked as an error.

validator.w3.org/nu/ allows it, so I think maybe this is a bug?

Please compare 

https://html5.validator.nu/?doc=http://xn--sjnleikarhsi-7gb5a7i.com/productionlist/kardemomme2015-1/2016-01-12-ty/

with 

https://validator.w3.org/nu/?doc=http%3A%2F%2Fxn--sjnleikarhsi-7gb5a7i.com%2Fproductionlist%2Fkardemomme2015-1%2F2016-01-12-ty%2F

Comment 1 Michael[tm] Smith 2015-12-16 12:45:17 CET

Thanks for reporting this but the answer is that the behavior is intentional. It's not a bug.

The reason is that only the W3C instance of this checker has support for full RDFa. And  it's only supported their for political reasons. Otherwise, only RDFa Lite is supported and even then that's mostly just because of some much usage of Facebook's Open Graph stuff in the wild, and because of schema.org (which is limited to RDFa Lite by design).

So I am going to close this bug since we have no plans to enable full RDFa support anywhere else. But feel free to add further comments or questions here, or to re-open this if you think the resolution is unclear.