Bug Fixed Move to Schema.org from data-vocabulary.org

[twisted_melon]

Hi,
I have set two prefixes as this is a bug and a suggestion aswell.
The DM now triggers errors in Google Structured Data due to using data-vocabulary.org instead of Schema.org - notably for ratings and reviews.
In our case I am getting pages of errors for the following;
A value for the rating field is required.

When you do some looking into it, Google dropped data-vocabulary.org in place of Schema.org after much collaboration.
It would be great if this microdata was migrated to the Schema one to remain inline with Google and their content pulling techniques. This is pretty important for correct listing information and reviews etc.
Thanks very much.

 

[twisted_melon]

Hi,
I have set two prefixes as this is a bug and a suggestion aswell.
The DM now triggers errors in Google Structured Data due to using data-vocabulary.org instead of Schema.org - notably for ratings and reviews.
In our case I am getting pages of errors for the following;
A value for the rating field is required.

When you do some looking into it, Google dropped data-vocabulary.org in place of Schema.org after much collaboration.
It would be great if this microdata was migrated to the Schema one to remain inline with Google and their content pulling techniques. This is pretty important for correct listing information and reviews etc.
Thanks very much.

Bump

 

[Clement]

In fact calling data-vocabulary is not an issue.

I was calling the wrong one.

It's now fixed in upcoming version.

 

[twisted_melon]

In fact calling data-vocabulary is not an issue.

I was calling the wrong one.

It's now fixed in upcoming version.

Fantastic! That's superb news, thank you.