This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section 3.2 User Agent Conformance says HTML+RDFa UAs must: "Implement all of the features required by this specification. Implement all of the features specified in the XHTML+RDFa specification, excluding those features which are specifically overridden by this specification as detailed in the Modifications to XHTML+RDFa." However, I could not find any features in these specifications that are specifically required for user agents, as opposed to for RDFa processors. Is there a difference between being a conforming HTML+RDFa processor and a conforming HTML+RDFa user agent?
RDFA-SPEC-SECTIONS [user-agent-conformance]
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Fixed Change Description: Added opening paragraph to User Agent Conformance section: http://dev.w3.org/html5/rdfa/drafts/ED-rdfa-in-html-20100502/#user-agent-conformance A User Agent is considered to be a type of RDFa Processor when the User Agent stores or processes RDFa attributes and their values. The reason there are separate RDFa Processor Conformance and a User Agent Conformance sections is because one can be a valid HTML5 RDFa Processor but not a valid HTML5 User Agent (for example, by only providing a very small subset of rendering functionality). Rationale: Explained the difference between an RDFa Processor and a User Agent. The example isn't as good as I'd like it to be... perhaps there is a better example of something that is capable of processing an HTML+RDFa document, but is not seen as a conforming HTML5 User Agent?
Diff-marked version: http://dev.w3.org/html5/rdfa/drafts/ED-rdfa-in-html-20100502/diff-20100304.html##user-agent-conformance
mass-move component to LC1