now that schema.org supports RDFa 1.1 Lite, can the module produce nice code like in this URL?

http://www.w3.org/QA/2011/11/schemaorg_and_rdfa_11_lite_how.html

Comments

scor’s picture

Project: Schema.org » Drupal core
Version: 7.x-1.x-dev » 8.x-dev
Component: Code » markup

This is definitely ideal, but too late for Drupal 7, given that it would require updating the theme functions which generate the HTML markup (in both core and contrib). This is on Drupal 8's plate so moving to the appropriate issue queue.

dropbydrop’s picture

Why not developing a module that can override drupal 7 RDF output?

For example the html5 tools module, makes drupal 7 output html5.

It's a pity to wait 2-3 year from now for Drupal 8, to arrive to the same point where Drupal 7 is.
(for example 1 year has passed and many major modules are still not final).

We have to support RDFa 1.1 Lite according to the following:
The False Choice of Schema.org
which talks about the freedom in RDF, and we can encourage users to use RDFa by using the 1.1 Lite version which is more clean and readable
AND
http://openspring.net/blog/2011/06/10/microdata-multiple-vocabularies
which proves that combining vocabularies in microdata is not so good/easy.

You'll tell me that existing RDFa support already do the things mentioned in the two articles above.
Yes, I agree. But only RDFa is simple enough for the simple drupal user, so he does not use microdata.
What I mean simple is that the output code is more readable with RDFa 1.1 Lite, and with it the novice template themer can write custom code more easy in situation where he needs custom rdf for fields that do not provide, like fivestar-agregaterating.

I had to write code for agregaterating, so that Google rich snippet test tool, shows stars at rich snippets.
It was much easier to do it in microdata because of its clean code.

On the other hand, I would feel better to do it with RDFa 1.1 it after reading the two articles above, hence I opened this issue.

scor’s picture

Issue tags: +RDFa 1.1

@dropbydrop Good point. In fact html5_tools ships with the appropriate doctype and will most likely get the HTML5 backports from Drupal 8, so we can build on that. I've created http://drupal.org/project/rdfa for the RDFa 1.1 specific markup in Drupal 7.

I'm leaving this issue open so we can track progress in core.

dropbydrop’s picture

congratulations! please post here when you have the first version, so we download. thanks!

klonos’s picture

Title: RDFa 1.1 Lite » RDFa 1.1 Lite in D8 core

...just a less vague title for the dashboard.

dropbydrop’s picture

mgifford’s picture

Issue tags: +semantics

Link to the competition #1177156: Microdata support in core

But also this comparison of the two (from a RDFa perspective) - http://manu.sporny.org/2012/mythical-differences/

Anonymous’s picture

PLEASE do not frame this as a competition.

As I said in my DrupalEasy Podcast, RDFa 1.1 Lite copies the processing model of microdata. They are fundamentally the same except for attribute names and the fact that you can use CURIEs in RDFa.

joelpittet’s picture

Version: 8.0.x-dev » 8.1.x-dev
Component: markup » rdf.module
Issue summary: View changes
Status: Active » Postponed

Not sure how far this feature got in the D8 lifecycle. I'm triaging and since this is a feature it will need to be done in 8.1.x if at all.

Postponing till that branch opens.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

joelpittet’s picture

Status: Postponed » Active

Postponed isn't the right status for this, moving back to active. It was really postponed on the release.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

Status: Active » Closed (outdated)

Closing out as outdated as RDF is moving out core into https://www.drupal.org/project/rdf

If still a valid request please reopen under the contrib page with an updated issue summary

Thanks!