For a Review where the itemReviewed is most typically a Product, it is common for sites to use organized lists of "pros" and "cons" to show summaries the positive and negative aspects.

This is a proposal from Google to add a structure that makes this kind of data explicit. If adopted by schema.org and publishers we consider it likely that we could improve search experience by making use of such markup.

Proposal

• add a pair of properties, /positiveNotes and /negativeNotes, applicable on /Review, with /ListItem and /Text values.
• typical usage would be an order-preserving list of short sentences. Let's start with an ItemList of strings.
• Potentially could be more structured (add a WebContent node, so variants of each pro/con could be represented with different properties.
• Complex comparisons of characteristics of products could be modeled with a /PropertyValue structure, but that would be more challenging.
• Let's acknowledge that ItemList is not a work of beauty, but it is our current main structure for representing order within the graph.

Example usage (simplified, showing "PROs" only):

This example skips any description of Product, and any example of /negativeNotes.

{
  "@context": "https://schema.org",
  "@type": "Review",
  "name": "Megaphone 11 review",
  "description": "blah blah",
  "positiveNotes": 
  {
    "@type": "ItemList",
    "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "item": "Tougher and water resistant design."
    },
    {
      "@type": "ListItem",
      "position": 2,
      "item": "Cheery bright colours and solid feel."
    },
    {
      "@type": "ListItem",
      "position": 3,
      "item": "Excellent amplification."    
    }
  ]
 }
}