David Legg wrote:
> David Huynh wrote:
>
>> Search engines are only interested in crawling (probably) visible HTML
>> content, so anything to be crawled must be in HTML, and that spoils the
>> whole point of separating data from presentation.
>>
>
> I think you have this a little skewed ;-)
>
> Just because your data is stored as HTML doesn't mean it's not separated
> from presentation... that's why CSS was born!
>
> I think the answer is you should encode your data as semantic HTML
> markup or POSH[1] as it's known. This has a lot of advantages; Google
> can 'see' your data, Browsers without Javascript enabled can see your
> data AND exhibit then becomes a method for progressively enhancing the
> display of the data.
>
> This technique fits well with the current idea of 'progressive
> enhancement' expounded by people like Jeremy Keith [2]. Currently if
> you don't have Javascript enabled then an Exhibit page is useless.
>
> Of course you also have to ask yourself... do you care if Google indexes
> your data. If not then you can continue as before.
>
> Regards,
> David Legg
>
> [1] http://microformats.org/wiki/posh
> [2] http://domscripting.com/author/
>
Thanks for the links, although looking at [1], I can't find any example
of what POSH looks like.
Anyway, POSH and the likes--microformats, RDFa--should work for simple
cases in which the data consists of relatively unconnected items. As
soon as you have more than one types of items and relationships between
them (e.g., papers and authors), then these formats start to break down
because you can't flatten a graph into a tree (HTML) without duplicating
data or repeating data. Consider wanting to present 2 papers with a
common author
Paper 1's title, by John Doe (University X) and Jane Smith
(University Y)
Paper 2's title, by Joe Anderson (University Z) and John Doe
(University X)
If you model John Doe as a first-class entity, then in POSH,
microformats, RDFa, you have to repeat that information about him being
affiliated with University X. And whenever you have copies of data, you
run the risk of updating one copy and forgetting about the other copies.
Furthermore, sometimes you actually don't want to keep your data in
POSH, microformats, RDFa, etc., because they are hard to write and
manage. You might prefer to keep your data in a Google spreadsheet
(which Exhibit can access), or maybe you already have your data in a
conventional database. Or maybe your data comes from a web service
(e.g., your Del.icio.us bookmarks coming from a JSON feed). Etc. etc.
David
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"SIMILE Widgets" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/simile-widgets?hl=en
-~----------~----~----~----~------~----~------~--~---
