Today the 3 big search engines, Google, Bing, Yahoo, they announced http://schema.org.

They decided to use microdata as a common rich snippets format.
Neither RDF, nor microformats.

Since, semantic web is the most important topic of the coming web evolution, it is absolutely necessary drupal 7 to put at it's core microdata support.

Ideally giving the ability to choose microdata for each field of each content type.

Please do not let it for Drupal 8, it will be late.
We need for Drupal 7, so Drupal has advantage and not stay behind in the evolution.

Thanks

Comments

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

Microdata is based on the RDF model. It is very easy to translate between RDFa and Microdata... so easy that schema.org has instructions for how to use the models with RDFa 1.1.

Google supports microformats, microdata, and RDFa for their Rich Snippets.

jpstrikesback’s picture

jpstrikesback CreditAttribution: jpstrikesback commented

Sub.

dropbydrop’s picture

dropbydrop CreditAttribution: dropbydrop commented

@linclark thanks for the info.
Do bing and yahoo also support this?

The output code would be more clear if we would just have microdata, and since this is the future, then why not.
Since google, bing, yahoo chose microdata, I don't think there a lot that we can do about other choices.

nandotinoco’s picture

nandotinoco CreditAttribution: nandotinoco commented

Sub

RdeBoer’s picture

RdeBoer
Location Melbourne
CreditAttribution: RdeBoer commented

To elaborate on comment #1.

... all of Schema.org can be used with the RDFa 1.1 syntax as is.
The RDFa 1.1 version of the markup looks almost isomorphic to the Microdata version...

Coverting Microdata to RDFa in a nutshell:

"itemprop is replaced by either property or rel depending on whether the value is literal or another entity.
itemscope is dropped and itemtype is replaced with typeof.
vocab="http://schema.org/" is added to the body or some other enclosing tag."

"Microdata does not have analogs for RDFa features such as CURIES, Turtles, Chaining, Typed vs Plain literals, etc."

RdeBoer’s picture

RdeBoer
Location Melbourne
CreditAttribution: RdeBoer commented

The FAQ's are particularly good, explaining why the Big Three went for microdata over microformat, Facebook's OpenGraph and RDFa (which they'll continue to support also).
See http://schema.org/docs/faq.html

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented
Title: Microdata in Core. schema.org. » Microdata support in core
Version: 7.x-dev » 8.x-dev
Priority: Major » Normal

This can't go into core for Drupal 7, it would be an introduction of a new API which just doesn't happen after the release. It also doesn't need to be in core to work.

Microdata is extremely close to RDF in its data model, and very close to RDFa in the way it inserts the model into HTML. This is good because it means we can use the thinking that already went into RDF in core. I have started a module in contrib that leverages that work for Microdata support.

It is still in the extremely early stages, but this is the plan:

  • It will provide an API like RDF module does.
  • It will provide a user interface for creating mappings.
  • If RDF module is turned on, it will strip out as much RDFa from the HTMLas it can and will save the Microdata mappings as RDF mappings. This will enable output using other formats, such as RDF/XML or Turtle, if the client requests it.

As I said, it is still in the very early stages, but I hope to be able to get further tomorrow.

dropbydrop’s picture

dropbydrop CreditAttribution: dropbydrop commented

where is this module?

mariomaric’s picture

mariomaric CreditAttribution: mariomaric commented

@dropbydrop: http://drupal.org/project/microdata :D

dropbydrop’s picture

dropbydrop CreditAttribution: dropbydrop commented

thanks for starting a new module.
I hope to see it developed soon.

barbi’s picture

barbi CreditAttribution: barbi commented

Sub

sonicthoughts’s picture

sonicthoughts CreditAttribution: sonicthoughts commented

sub

tdiepiv’s picture

tdiepiv CreditAttribution: tdiepiv commented

sub

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

Just to update, the W3C and WHATWG are forming a task force to figure out how the microdata and RDFa standards should be made more compatible. This might mean merging the two or it might mean making it easier to use them independently and then combine the data later.

The microdata module needs to go through a developer experience review before the API is stable. I will not be putting out the call for this review until it is more clear what the recommendation of the task force will be. Fortunately, almost everything is in place in the module to move into DX review as soon as the direction is more clear.

ELS Landscape’s picture

ELS Landscape CreditAttribution: ELS Landscape commented

My 2 cents in reading all I could about this.

OPG is in the head and should be a Global site description.

RFDa should be a global page description and canonical link in head

Microdata is about specific items on the page.

I can see how metatags will not do this task in it's current state but can help with the OGP

Thank you linclark for taking this up. Wish I was smart enough to help but Drupal is a tool for me. I do appreciate all the hard work by the contributors.

kolafson’s picture

kolafson CreditAttribution: kolafson commented

sub

mariomaric’s picture

mariomaric CreditAttribution: mariomaric commented

@kolafson: Stop subscribing, start following, please. :)

hgceballos’s picture

hgceballos CreditAttribution: hgceballos commented

sub

mgifford’s picture

mgifford
he/him
Primary language English
CreditAttribution: mgifford commented
Issue tags: +semantics

Link to the competition #1365654: RDFa 1.1 Lite in D8 core

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

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.

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

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should 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.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should 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.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should 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.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should 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.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should 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.

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

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should 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.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.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: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should 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: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

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

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

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should 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.

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

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.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

smustgrave CreditAttribution: smustgrave at Mobomo commented
Issue summary: View changes
Status: Active » Postponed (maintainer needs more info)

Wonder after so many years if this is still needed for D10?

longwave’s picture

longwave
he/him
Primary language English
Location UK
CreditAttribution: longwave at Full Fat Things commented
Status: Postponed (maintainer needs more info) » Closed (outdated)

We have removed RDF from core, and I am not sure microdata was ever successfully implemented in D8+. JSON+LD seems to be the current favourite approach and this is handled well in contrib via https://www.drupal.org/project/schema_metatag - I don't think this should be added to core directly though.

Therefore closing this issue as outdated.