[uf-new] Microformats for hidden data

[Fiann O'Hagan]

Brian, that's exactly what I am hoping to do, you have captured it precisely.

hAtom gives a lot but not all of what I am looking for (my baseline is
the fields that are common to all the major web analytics products).
hAtom is focussed on blog posts rather than generic website pages, and
I am not sure it is an exact fit, but the core concept is very
similar.

The reason I am interested in using microformats is that if by using a
standard, I can turn your suggestion of
var page = $('.entity-title');
into hAtom format
var page = $('.hfeed .hentry .entry-title');

and it will work across any site with that markup, which is much
better than defining our own POSH format specific to a single site.

Thanks again for all the detailed feedback and putting up with this long thread.

Fiann


2009/11/27 Brian Suda <brian.suda at gmail.com>:
> On Fri, Nov 27, 2009 at 2:12 PM, Fiann O'Hagan <fianno at jshub.org> wrote:
>> What typically happens on big enterprise sites is that they have an
>> analytics product which requires certain per-page metadata, such as a
>> page name and category.
>
> --- yup, I know them well. One solution would be to define your own
> POSH format and/or re-use something like hAtom.
>
> Then in the JS code for declaring variables for tracking you can
> reference the microformats, for instance:
>
> Instead of:
> var page = "news-index";
> var campaign = "news"
>
> you could replace the declared variables with references to the
> visible text such as:
> var page = $('.entity-title');
> var campaign = $('a[rel="tag"]');
>
> In the JS you are referencing visible data. As editors change fields
> in the CMS, the tracking codes, campaigns, sections, and other
> tracking is done automatically. What you need is the mapping between
> the visible parts of the page and your specific tracking variables. It
> also depends on how much you want to connect the two and/or allow
> editors to be changing these values.
>
> -brian
>
> --
> brian suda
> http://suda.co.uk
> _______________________________________________
> microformats-new mailing list
> microformats-new at microformats.org
> http://microformats.org/mailman/listinfo/microformats-new
>