- From: Jim Saiya <jsaiya@formatdata.com>
- Date: Thu, 11 Aug 2016 00:03:04 -0500
- To: public-schemaorg@w3.org, Eric Theise <erictheise@gmail.com>
- Message-ID: <20160811000304.4mjyc0lxa8isocgk@webmail.hosting.earthlink.net>
Eric,
>> sounds as if prepTime plus cookTime is supposed to equal totalTime
I'd say, "maybe." Maybe totalTime includes both of those plus any
"standing" times like the ones you gave as examples.
In real-world recipes I've seen, if both prepTime and cookTime
are represented in the data, typically totalTime is *not* present.
The totalTime property is most likely useful in receipes where the
time is not broken down into "prep" and "cook".
Jim Saiya
Software Developer / Information Architect
Wichita, KS
✆ 703.731.5119
✉ jsaiya@formatdata.com
[in] www.linkedin.com/in/jimsaiya
On Tue, 9 Aug 2016 16:10:52 -0700, Eric Theise wrote:
Hello,
I'm trying to get my head around the prepTime, cookTime, and totalTime
properties of Recipe. totalTime is defined as the time it takes to
prepare and cook the recipe, which sure sounds as if prepTime plus
cookTime is supposed to equal totalTime.
I don't know the recommended way to categorize a post-cooking "let sit
for about 10 minutes before slicing, then slice and serve" or
post-baking "transfer to rack and cool. Chill until cold, about 2
hours. Cover and chill overnight." Are there more detailed guidelines
to the use of these properties somewhere?
I was also wondering if anyone on this list could say why the Google
Structured Data Testing Tool throws errors on suitableForDiet, e.g.,
"http://schema.org/VeganDiet (The property suitableForDiet is not
recognized by Google for an object of type Recipe.)"
Thanks, just joined the list, hope these questions are appropriate here.
Eric
Received on Thursday, 11 August 2016 05:03:36 UTC