- From: <bugzilla@jessica.w3.org>
- Date: Mon, 29 Aug 2011 19:10:05 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13959
Summary: I think the change to dfn being the defining instance
of a term removes one previously solid use case for
dfn: defining unfamiliar terms that may make no sense
to define in context. For instance, use of "borrowed"
terms and phrases from other languages th
Product: HTML WG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-work/#the
-dfn-element
OS/Version: other
Status: NEW
Severity: normal
Priority: P3
Component: HTML5 spec (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: contributor@whatwg.org
QAContact: public-html-bugzilla@w3.org
CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
public-html@w3.org
Specification:
http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html
Multipage: http://www.whatwg.org/C#the-dfn-element
Complete: http://www.whatwg.org/c#the-dfn-element
Comment:
I think the change to dfn being the defining instance of a term removes one
previously solid use case for dfn: defining unfamiliar terms that may make no
sense to define in context. For instance, use of "borrowed" terms and phrases
from other languages that may be unfamiliar to the reader. In that case, a
simple dfn element with lang attribute and title to define the term or phrase
seems proper. Without that use available, there becomes a hole in HTML's
semantics that was previously plugged and there are no other elements that
make sense to replace dfn in that instance.
Posted from: 74.221.190.5
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.1
(KHTML, like Gecko) Chrome/13.0.782.215 Safari/535.1
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 29 August 2011 19:10:10 UTC