ISSUE-30: The hasFeature() RDFa API call should be further clarified

clarify hasFeature support

State:

CLOSED

Product:

RDFa 1.1 API

Raised by:

Mark Birbeck

Opened on:

2010-07-05

Description:

The hasFeature() RDFa API call should be further clarified based on
Mark's feedback:

http://lists.w3.org/Archives/Public/public-rdfa-wg/2010Jun/0053.html

Related Actions Items:

No related actions

Related emails:

Comments on RDFa Core 1.1 Working Draft (from david@3roundstones.com on 2012-01-11)
Re: longdesc URLs and RDFa (from shane@aptest.com on 2010-08-16)
Re: longdesc URLs and RDFa (from xn--mlform-iua@xn--mlform-iua.no on 2010-08-16)
Re: longdesc URLs and RDFa (from martin@weborganics.co.uk on 2010-08-16)
RDFa WG telecon minutes for 2010-08-05 (from msporny@digitalbazaar.com on 2010-08-05)
Telecon Agenda - August 5th 2010, 1400 UTC (from msporny@digitalbazaar.com on 2010-08-01)
Re: Telecon Agenda - July 29th 2010, 1400 UTC (from ivan@w3.org on 2010-07-29)
Re: Telecon Agenda - July 29th 2010, 1400 UTC (from knud.moeller@deri.org on 2010-07-28)
Telecon Agenda - July 29th 2010, 1400 UTC (from msporny@digitalbazaar.com on 2010-07-26)
ISSUE-30 (clarify hasFeature support): The hasFeature() RDFa API call should be further clarified [RDFa 1.1 API] (from sysbot+tracker@w3.org on 2010-07-05)

RESOLVED: Bring hasFeature() in line with the DOMImplementation interface, use "RDFaAPI" as the feature string, and "1.1" as the version.

http://www.w3.org/2010/02/rdfa/meetings/2010-08-05#resolution_2

Manu Sporny, 5 Aug 2010, 15:43:27