title: What's the best HTML attribute to use to store information for jQuery to parse?
body: <p><strong>Must Support IE6 and must Validate vs XHTML Strict 1.0!</strong></p>
  
  <p>This is tricky to explain...</p>
  
  <p>I'm using a generic class name to initiate a plugin feature on an associated element. 
  I also want to have options associated with the element stored in an attribute as well.</p>
  
  <pre><code>&lt;a href="url.com" class="popup" rel="900x900" &gt;My Link&lt;/a&gt;
  </code></pre>
  
  <p>With this, jQuery will look for all elements that have 'popup' and parse the rel value for the dimensions of the popup and initiate the popup() function whenever this link is clicked with a window the size w=900 h=900</p>
  
  <p>but I need to take this a step further because I want to have more options...</p>
  
  <pre><code>&lt;a href="url.com" class="popup" rel="900x900_scroll_tool_menu" &gt;My Link&lt;/a&gt;
  </code></pre>
  
  <p>I'm not sure if using the rel attribute is the place for this because I also want to use this on other elements that dont have a rel= attribute.</p>
  
  <p>So I was thinking using classes for this too... I came up with this:</p>
  
  <pre><code> &lt;a href="url.com" class="popup opt_dim-900x900_scroll_tool_menu" &gt;My Link&lt;/a&gt;
   &lt;img src="pic.gif" class="popup opt_dim-150x200_location" &gt;My Link&lt;/a&gt;
  </code></pre>
  
  <p>From the looks of this the <strong>options can get VERY long</strong>, using class seems ok, but maybe there's something better..</p>
  
  <p>Which way do you think is better? Do you have another idea for this? I want to store the options in some html attribute.</p>
  
  <p>Thanks!</p>
  
  <p><strong>UPDATE</strong></p>
  
  <p>I am continually reminded that there are a dozen ways to do anything in Javascript, in terms of the solutions here I later changed the correct answer to the html5 data attribute, which now that ie6 isnt an issue, seems like the best method. </p>
  
  <p>Best, because it uses standard features and avoids any of the hackery I was trying to do with class names. Sure classnames are extremely flexible still, but that solution isn't semantic, nor does it follow best practice of separating views from behavior.</p>