Re: Why is the video property bound to creative work?

I would not recommend using hasPart as a generic property for relatedness.

On 19 May 2014, at 22:38, Jarno van Driel <> 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="">
>     <link itemprop="sameAs" href="">
>     <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="">
>         <link itemprop="embedURL" href="">
>         <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.

Received on Monday, 19 May 2014 20:54:09 UTC