schema.org - remove AggregateOffer, itemOffered; add price=0.00

Bug #1337550 reported by Dan Scott
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Undecided
Unassigned

Bug Description

As our record details page lists each copy as a separate Offer (well, in many cases anyway, unless paging gets invoked), the AggregateOffer entity is not really necessary--and using it on the same page as separate Offer entities is not recommended by at least one search engine (per Google https://support.google.com/webmasters/answer/146750?hl=en says a given page should include "_one_ of the following: Offer or Offer-aggregate", and indeed the Google Structured Data testing tool gets confused when both are included).

We use the "offers" property to link the Product to the Offer, so there is no reason to use a reciprocal "itemOffered" property to link back to the Product from the Offer. The circular reference confuses some tools (http://rdfa.info/play) and may complicate general processing, so let's simply remove it.

Tags: pullrequest
Revision history for this message
Dan Scott (denials) wrote :
tags: added: pullrequest
Revision history for this message
Ben Shum (bshum) wrote :

Works for me. Thanks Dan, pushed to master for 2.7!

Changed in evergreen:
milestone: 2.next → 2.7.0-alpha
status: New → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.