ISSUE-34
HREF attribute on elements other than A and LINK
- State:
- CLOSED
- Product:
- RDFa
- Raised by:
- Ben Adida
- Opened on:
- 2007-04-10
- Description:
Should XHTML1.1+RDFa allow for HREF on elements other than A and LINK, where XHTML1.1 does not? If so, should conforming agents make those elements clickable links? When considering XHTML2, the task force had the following discussion: http://www.w3.org/2006/02/06-htmltf-minutes#item03 In a recent telecon, this was brought up, too: http://www.w3.org/2007/04/02-rdfa-minutes.html#item03
- Related emails:
- ISSUE-34: HREF attribute on elements other than A and LINK (from dean+cgi@w3.org on 2007-04-10)
- [RDFa] ISSUE-34: @href everywhere and non-information resources (from ben@adida.net on 2007-07-09)
- [RDFa] ISSUE-34: partial resolution to @href everywhere (from ben@adida.net on 2007-07-12)
- Re: [RDFa] ISSUE-34: partial resolution to @href everywhere (from ivan@w3.org on 2007-07-14)
- Re: [RDFa] ISSUE-8: RDF containers in RDFa (from connolly@w3.org on 2007-07-17)
Related notes:
2007-04-15: approved as an OPEN issue on 2007-04-11 telecon.
2007-06-13: This issue is intimately tied with, and thus should include, the discussion of adding a @RESOURCE attribute that is like @HREF except not navigable, even in XHTML2 and beyond. http://lists.w3.org/Archives/Public/public-rdf-in-xhtml-tf/2007May/0020.html
2007-07-23: @href and @resource appear on every element, and @resource overrides @href, as per: http://www.w3.org/2007/07/19-rdfa-minutes.html
2008-02-06: additional related resolution from 2008-01-24: "@href/@resource complete hanging @rel's." as per http://www.w3.org/2008/01/24-rdfa-minutes.html