This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10346 - Should define 'class' better
Summary: Should define 'class' better
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-11 15:32 UTC by contributor
Modified: 2010-10-04 14:47 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-08-11 15:32:07 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#classes

Comment:
Shoudl define clas better: "may be used for labelling, styling or indicating
meaning" c/f use of class in microformats

Posted from: 80.249.57.49
Comment 1 Andy Mabbett 2010-08-11 15:37:39 UTC 
For example: "may be used for labelling, styling or indicating meaning".

c/f use of class in microformats
Comment 2 Andy Mabbett 2010-08-11 15:50:17 UTC 
(In reply to comment #1)
> For example: "may be used for labelling, styling or indicating meaning".
> 
> c/f use of class in microformats

See also issues described in http://microformats.org/2005/10/19/more-than-styling

Perhaps the word "semantic" should be used? I've started a wiki page at 

http://wiki.whatwg.org/wiki/Class
Comment 3 Ian 'Hixie' Hickson 2010-09-21 18:04:47 UTC 
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: Did Not Understand Request
Change Description: no spec change
Rationale:

I don't understand the suggestions.

Is the "may" in "may be used" intended to have the RFC2119 meaning? If so, is it intended to restrict or to allow? Or is this suggestion supposed to just be a non-normative description of the purpose of the attribute?