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.