This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Microdata supports @cite: ]] 1. For each blockquote and q element in the Document that has a cite attribute that resolves successfully relative to the element, generate the following triple: subject the document's current address predicate http://purl.org/dc/terms/source object the absolute URL that results from resolving the value of the element's cite attribute relative to the element [[ [*] http://www.w3.org/TR/microdata/#extracting-rdf HTML+RDFa should support @cite as well. @cite (and @longdesc) was meant to be supported in in XHTML2 as well, and it si simple to support.
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: Won't Fix Technical Description: The submitter is requesting that the Processing Rules for HTML+RDFa be modified such that an element containing the @cite attribute generates a triple for all conforming RDFa processors. Rationale: While the RDFa WG is receptive to the concept of processing @cite, feature parity with Microdata is not a design goal for RDFa. An argument that resonated with the group when this was discussed over the past year was the one of providing good a11y support in RDFa. As the submitter may know, the PFWG stated that the @role attribute MAY be processed by Host Languages or RDFa Processors that choose to support @role: http://www.w3.org/WAI/PF/role-attribute/#using-role-in-conjunction-with-rdfa We believe that the proper way to support @cite at this time is in the same manner - as an optional triple that MAY be produced by a @cite-aware RDFa processor, but not in the default graph. The current RDFa Core specification allows this behavior and thus HTML+RDFa 1.1 does not need to change to support the optional generation of @cite triples. It is noted that the submitter was requesting that mandatory support for @cite be included in the HTML+RDFa specification. The rules for processing @cite are more complicated than what is presented above as the current subject set via @about (or chained from a parent element via @href or @resource) needs to be taken into account. The current subject may often corrupt the meaning of @cite. @href must be taken into account, but additionally @resource would have to be taken into account as well as the object of the triple. Rules to establish processing priority on @property, @typeof and @datatype would also have to be considered. It is debatable whether or not @src should be taken into account. These are just a few of the issues that would have to be tackled in the RDFa WG and HTML WG. The RDFa WG decided to pass on this particular feature as it would take more time than was available to us to formulate the rules for @cite. The RDFa WG is also under the impression that many HTML page authors do not use the @cite attribute, resulting in a catch-22 - implementing the feature would add complexity to the processing rules without providing a good return on investment. The RDFa WG leaves open the opportunity for the submitter to write a Note that clearly explains the processing of the @cite attribute. The RDFa WG may then consider sending the document to a straw-poll on whether or not the WG would like to publish the processing of @cite as a Note - an optional feature that RDFa Processors MAY want to support in an a11y-specific graph. However, this approach may be best undertaken by the PFWG and not only cover @cite, but all other a11y attributes of interest.
mass-move component to LC1