- From: <bugzilla@jessica.w3.org>
- Date: Mon, 12 Sep 2011 08:30:15 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14114
Summary: HTML+RDFa should extend flow content to include link
and meta elements
Product: HTML WG
Version: unspecified
Platform: PC
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: HTML+RDFa (editor: Manu Sporny)
AssignedTo: msporny@digitalbazaar.com
ReportedBy: jeni@jenitennison.com
QAContact: public-html-bugzilla@w3.org
CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
public-html@w3.org, msporny@digitalbazaar.com
To make it easier to convert microdata to RDFa and vice versa, <link> and
<meta> elements should be permitted within flow content and phrasing content
when they have RDFa attributes.
I'd suggest using wording in HTML+RDFa 1.1 similar to that used within Section
4.1 (Content models) of the current HTML Microdata Editors Draft [2] which
states:
If the itemprop attribute is present on link or meta, they are flow
content and phrasing content. The link and meta elements may be used
where phrasing content is expected if the itemprop attribute is present.
This kind of wording might fit nicely within Section 4 (Extensions to the HTML5
Syntax) [3] of the current HTML+RDFa 1.1 Editors Draft.
The RDFWA WG supports this change [1].
Jeni
[1]: http://lists.w3.org/Archives/Public/public-rdfa-wg/2011Sep/0038.html
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 12 September 2011 08:30:20 UTC