Better module description for the core RDF module

Thanks for bringing this up at the meeting, Lin! I would word it something like this:

Adds metadata to your website that search engines can find and use when displaying advanced search results. This not only helps search engines better understand the content that your site contains, it also helps people learn more about the structure of your website when using those search engines.

I'm not so sure about including the word "advanced" but it's technically true and is a good selling point.

Nothing quite clicked for me with any of the examples but it took me a week to come up with my own:

RDFa makes the data of your site more available and understandable to other applications, including search engines, which can make your site stand out from the crowd with richer display of its information.

I guess dropping the opening RDFa if we have to fit with the "X module" setup.

Here are my stabs. Given that it has to be a short description, I tried to focus on the big gains of using the module:

By adding behind-the-scenes context to your content, this module allows search engines to provide better search results.

Allows search engines and other websites to better understand the relationships within your content and between web pages.

And all together now:

Adds context to your content, such as explaining the topic of a web page or relationships between web pages, leading to richer results in search engines and reusable content for other websites.

Makes other applications (like search engines) better understand the relationships within your content and between web pages.

edit: I only have a vague understanding of what RDFa does. The search engine example is good to have in there, it can trigger people to look further into it because everybody is into SEO, right? :-). Otherwise, I tried to make the shortest posible variant that captures most of the proposals so far. 'Applications' is better than web sites in this context (the search engine example tells you it's still about *web* applications/sites).

How about:

Tags HTML structures on your website with metadata so that they can be identified and leveraged by other systems (e.g. to enhance search engine results, to allow site interoperability and improved aggregation).

Too many and too difficult words. "Tags with metadata" is quite explicit and good though.

Tags your content with metadata to let other applications (like search engines) better understand relationships within your content.

(It'd be good to start working on refining one proposal instead of coming up with totally new ones each time, try to build off of the given variations.)

Okay, yoroy, points taken.

It's not just relationships (e.g. replies) but also attributes (dates, titles, etc.) - also, I didn't like most of the previous ones that focused on just search engines. It's good to highlight that, but it's not the sole advantage.

Thanks,

John.
--

How about (revising yoroy's):

Tags your content with metadata to let other applications (e.g. search engines, aggregators) better understand relationships (e.g. reply structures, categories) and attributes (e.g. dates, titles) within your content.

Could even leave out some of the bracketed stuff...

Enriches your content with metadata to let other applications (e.g. search engines, aggregators) better understand its relationships and attributes.

Sounds great - thanks yoroy!

Great. Thanks for playing along Cloud! :-)

Committed to HEAD. Thanks! Welcome to the core team, Cloud. :)

This removes the extra period in the patch that was committed.

Oops, I patched against the wrong version. I second the RTBC of #21.

Oh, no! :) Good catch.

Committed to HEAD. Thanks!