12363 2011-03-22 08:27:45 +0000 Include @longdesc in Microdata 2011-08-04 05:05:27 +0000 1 1 1 Unclassified HTML WG LC1 HTML Microdata (editor: Ian Hickson) unspecified PC All RESOLVED WONTFIX http://dev.w3.org/html5/md/#rdf a11y, a11y_text-alt, TrackerIssue P3 normal --- 10455 1 xn--mlform-iua ian ayg ian jfoliot julian.reschke laura.lee.carlson mike public-html-a11y public-html-admin public-html-wg-issue-tracking w3c xn--mlform-iua public-html-bugzilla oldest_to_newest 46907 0 xn--mlform-iua 2011-03-22 08:27:45 +0000 Add this step to the RDF section: ]] For each img and iframe element in the Document that has a longdesc attribute that resolves successfully relative to the element, generate the following triple: subject the document's current address predicate http://www.w3.org/2007/05/powder-s#describedby object the absolute URL that results from resolving the value of the element's longdesc attribute relative to the element [[ describedby will be included in XHTML+RDFa: http://lists.w3.org/Archives/Public/public-rdfa-wg/2011Jan/0086.html Citing POWDER: ]] 2.2.8 Property describedby RDF Property Label: described by Defined in: http://www.w3.org/TR/powder-dr/#semlink An RDF property to exactly match the describedby relationship type introduced in http://www.w3.org/TR/powder-dr/#assoc-linking and formally defined in appendix D of the same document, i.e. the relationship A 'describedby' B asserts that resource B provides a description of resource A. There are no constraints on the format or representation of either A or B, neither are there any further constraints on either resource [[ 46943 1 ayg 2011-03-23 22:33:03 +0000 This seems like a peculiar thing to do while longdesc remains non-conforming. 48321 2 ian 2011-05-08 03:58:09 +0000 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: Rejected Change Description: no spec change Rationale: This would be utterly wrong. longdesc="" is not a description of the current document. It would also be a waste of time, since longdesc="" values are almost uniformly either bogus or useless, and the element is non-conforming so new valid documents won't use it. 48327 3 xn--mlform-iua 2011-05-08 11:06:34 +0000 (In reply to comment #2) > Status: Rejected > Change Description: no spec change > Rationale: This would be utterly wrong. longdesc="" is not a description of the > current document. An empty cite="" should be just as utterly wrong as an empty longdesc="" is. Thus, if this is a problem, the Microdata estraction algorithm needs to change - to cater for empty longdesc="" and empty cite="". > It would also be a waste of time, since longdesc="" values > are almost uniformly either bogus or useless, and the element is non-conforming > so new valid documents won't use it. That is true. Hence I liked this issue to Bug 10455, which seems to be the one that best tracks ISSUE-30. 48437 4 w3c 2011-05-10 15:24:57 +0000 The bug-triage sub-team thinks this is an issue of metadata, not of real people accessing information, thus we decided not to add the a11yTF keyword. 52933 5 mike 2011-08-04 05:05:27 +0000 mass-move component to LC1