- From: Thad Guidry <thadguidry@gmail.com>
- Date: Mon, 19 May 2014 15:57:54 -0500
- To: Jarno van Driel <jarno@quantumspork.nl>
- Cc: "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: <CAChbWaME+N70JcgKWiquGpv9rEuROk2x0keHQaJUmZd_EOg4vA@mail.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 20:58:21 UTC