Oops, I forgot about that.

The guys at work do this, but they don't use a dtd and in fact don't 
even use a doctype and clearly don't validate. Oh well, it was a 
thought, if only half baked. :)

-Steve

Ⓙⓐⓚⓔ wrote:
> sure, slip in a different namespace and you can make your own tags
> .... but it won't validate unless you do the dtd for it too.
> 
> 
> On 11/1/06, Stephen Woodbridge <[EMAIL PROTECTED]> wrote:
>> Or just adding an xml data island to your document that has everything
>> you want it it and then parsing that using xpath. This is approach is
>> much cleaner, should validate, and we already have the tools to parse it.
>>
>> -Steve W.
>>
>>
>> Erik Beeson wrote:
>>> In the case of adding metedata to divs, are these approaches any better
>>> than just using nested hidden spans?
>>>
>>> --Erik
>>>
>>> On 10/31/06, *John Resig* < [EMAIL PROTECTED]
>>> <mailto:[EMAIL PROTECTED]>> wrote:
>>>
>>>     Hi Everyone -
>>>
>>>     I just finished reading over the massive thread that discusses
>>>     embedding metadata into elements for later extraction. Well, I just
>>>     finished a plugin to handle all three metadata-extraction methods.
>>>
>>>     You can see a demo here: (Uses Firebug debug statements!)
>>>     http://john.jquery.com/plugins/meta/
>>>
>>>     It's capable of extracting metadata from classes, random attributes,
>>>     and child elements.
>>>
>>>     For example, you can do:
>>>     <li data="{some:'random', json: 'data'}">...</li>
>>>     OR
>>>     <li class="someclass {some: 'data'} anotherclass">...</li>
>>>     OR
>>>     <li><script type="sometype">{some:"json",data:true}</script> ...</li>
>>>
>>>     The default is the first method, but you can always change it but
>>>     twiddling the options. This means that there is at least one option
>>>     here to appease you.
>>>
>>>     There's also a bunch of options (like loading data into a single
>>>     property and the ability to ignore braces {}). Let me know what you
>>>     think of this - I know that I'll probably be using it very soon.
>>>
>>>     --John
>>>
>>>     _______________________________________________
>>>     jQuery mailing list
>>>     discuss@jquery.com <mailto:discuss@jquery.com>
>>>     http://jquery.com/discuss/
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> jQuery mailing list
>>> discuss@jquery.com
>>> http://jquery.com/discuss/
>>
>> _______________________________________________
>> jQuery mailing list
>> discuss@jquery.com
>> http://jquery.com/discuss/
>>
> 
> 


_______________________________________________
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/

Reply via email to