- From: Jarno van Driel <jarnovandriel@gmail.com>
- Date: Mon, 19 May 2014 23:10:41 +0200
- To: Thad Guidry <thadguidry@gmail.com>
- Cc: Jarno van Driel <jarno@quantumspork.nl>, "martin.hepp@ebusiness-unibw.org" <martin.hepp@ebusiness-unibw.org>, Laura Dawson <Laura.Dawson@bowker.com>, Vicki Tardif Holland <vtardif@google.com>, W3C Web Schemas Task Force <public-vocabs@w3.org>
- Message-ID: <CADK2AU28h6ZqAOHUuRsrhXNixc4xn5PRMtVsSV-17PR4QoCTZg@mail.gmail.com>
Thad, if I get you right you suggest I write: <div itemscope itemtype="http://schema.org/VideoObject"> <meta itemprop="name" content="How to get a flat stomach? tummy tuck or exercise?"> <span itemprop="about" itemscope itemtype=" http://schema.org/MedicalProcedure"> [...] </span> </div> This makes the main-entity the VideoObject which, as a result, has Google render a VideoObject rich snippet. Yet in this case the main entity is a Product/MedicalProcedure and the aim is to get the Product rich snippets (which an MTE can have, as I have the examples for it). And therefor the main-entity can't be a VideoObject and has to be the Product/MedicalProcedure: <div itemscope itemtype="http://schema.org/Product http://schema.org/MedicalProcedure"> <meta itemprop="name" content="How to get a flat stomach? tummy tuck or exercise?"> <span itemprop="video" itemscope itemtype="http://schema.org/VideoObject "> [...] </span> </div> 2014-05-19 22:57 GMT+02:00 Thad Guidry <thadguidry@gmail.com>: > Jarno, > > It's simpler than that... just use: > > http://schema.org/about > > Someone's CreativeWork (a video somewhere out there) is ABOUT the subject > of "abdominoplasty". > Where that's CreativeWork is in video form...and might or might not have > an author, creator, and who knows...the video might even get an Award > someday, etc. which all of those are properties of CreativeWork. > > Happy hacking! > > > > On Mon, May 19, 2014 at 3:54 PM, Jarno van Driel <jarno@quantumspork.nl>wrote: > >> I wonder, if the 'itemprop-reverse' addon for Microdata gets accepted, >> would this than suffice: >> >> <span itemprop-reverse="about" itemscope itemtype=" >> http://schema.org/VideoObject"> >> <link itemprop="embedURL" href=" >> https://www.youtube.com/watch?v=xjC_dCvVB8s"> >> <meta itemprop="name" content="How to get a flat stomach? tummy tuck >> or exercise?"> >> ... >> </span> >> >> Because if so, than maybe we don't need to do anything at all. (thinking >> out loud, again) >> >> >> >> On Mon, May 19, 2014 at 10:45 PM, martin.hepp@ebusiness-unibw.org < >> martin.hepp@ebusiness-unibw.org> wrote: >> >>> I would not recommend using hasPart as a generic property for >>> relatedness. >>> >>> >>> On 19 May 2014, at 22:38, Jarno van Driel <jarno@quantumspork.nl> wrote: >>> >>> > It's more the other way around. So in this case I want to express the >>> main entity on a page, a MedicalProcedure, has a video giving additional >>> information about the procedure. Something like this: >>> > >>> > <div itemscope itemtype="http://schema.org/MedicalProcedure"> >>> > <link itemprop="sameAs" href="http://www.freebase.com/m/01_mbc"> >>> > <span itemprop="name">Tummy Tuck</span> (<span >>> itemrop="alternatename">abdominoplasty</span>) >>> > <span itemprop="description">A Tummy Tuck, or abdominoplasty, is >>> the most effective way to...</span> >>> > <span itemprop="howPerformed">In summary the Tummy Tuck procedure >>> takes 3-4 hours of...</span> >>> > >>> > <span itemprop="hasPart" itemscope itemtype=" >>> http://schema.org/VideoObject"> >>> > <link itemprop="embedURL" href=" >>> https://www.youtube.com/watch?v=xjC_dCvVB8s"> >>> > <meta itemprop="name" content="How to get a flat stomach? >>> tummy tuck or exercise?"> >>> > ... >>> > </span> >>> > </div> >>> > >>> > I started this thread by suggesting to add @video to Thing but that >>> quickly evolved in the idea for a 'general' or 'related' property instead, >>> and then halted. >>> > >>> > Now I have a website where many MedicalProcedure, Service and Article >>> entities have additional videos about those entities, yet only Article has >>> properties like @associatedMediao and @video. Both MedicalProcedure and >>> Service do not have the properties to express this. Which still leaves me >>> questioning what I should if I do not want the VideoObject to be main >>> entity. >>> > >>> >>> >> > > > -- > -Thad > +ThadGuidry <https://www.google.com/+ThadGuidry> > Thad on LinkedIn <http://www.linkedin.com/in/thadguidry/> >
Received on Monday, 19 May 2014 21:11:11 UTC