<script type="application/ld+json">
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"description": "We hope you enjoyed your meal at Joe's Diner. Please rate your experience.",
"action": {
"@type": "ReviewAction",
"review": {
"@type": "Review",
"itemReviewed": {
"@type": "FoodEstablishment",
"name": "Joe's Diner"
},
"reviewRating": {
"@type": "Rating",
"bestRating": "5",
"worstRating": "1"
}
},
"handler": {
"@type": "HttpActionHandler",
"url": "http://reviews.com/review?id=123",
"requiredProperty": {
"@type": "Property",
"name": "review.reviewRating.ratingValue" <--- PROPERTY PATH
},
"method": "http://schema.org/HttpRequestMethod/POST"
}
}
}
</script>
Sam Goto raised concerns about the complexity of nested structures. We need to reduce the verbosity of operations expecting nested structures in which some of the properties in nested objects have, e.g., to be marked as required.
Actions in Gmail currently uses property paths to express such things: