[Data-modeling] Made-for-TV Movies

[Ed Laurent]

You might want to take a look at the types within the Publishing
domain<http://www.freebase.com/view/book>when you eventually refactor
these video types. It's been slow going and
difficult to grasp just what the heck is going on at times but Jeff et al.
have really done a great job of distilling print media into elemental
co-types.  There is still a lot of work to be done, but some of the
redundancies you are encountering (e.g., _performer_) have analogous
properties in the Publishing domain that have already been refactored onto
generic types such as Written
work<http://www.freebase.com/view/book/written_work>(e.g., _author_).
While there's probably lots of ways to model both well,
describing video media is not that different from describing print media.

-Ed


On Wed, Apr 30, 2008 at 11:49 AM, Robert Cook <robert at metaweb.com> wrote:

> I'm most intrigued by Tim's solution.  Film and TV as media are morphing
> rapidly right now and I suspect will become less distinguished from each
> other over time.  They really are historical points on a spectrum that is
> becoming filled in.  This "video production" type could hold properties for:
> /film/film
> /tv/tv_program
> /tv/tv_episode
>
> Unfortunately, with our current system of "supporting types" we can't
> handle this situation well.  For instance, if the apparent "director"
> property of film really comes from the supporting type *
> /media/video_productio**n*, its expected type would be */media/director*rather than
> */film/director*.  This would mean that if you entered a director into a
> film in the freebase interface, it the instance on the other end would be
> typed */media/director* not* /film/director* as you would expect.
>
> We're about to roll out a new feature called "property delegation" that
> will replace the supporting types mechanism and will handle the expected
> types correctly.  I suspect that this video jumble might be one of the first
> things we fix.
>
> R
>
>
> On Apr 29, 2008, at 6:56 PM, Tim Kientzle wrote:
>
> Sounds like there's confusion between "what something is"  (video
> production?) versus "how it's distributed" (TV, DVD, movie theater,
> streaming video).  Perhaps we need to add /media/video_production to
> hold the information common to all types of video (who was in it, who
> paid for it, who scripted it, who filmed it, who edited it, when it
> was filmed, when it was released, what book it's based on)?
>
>
> On Apr 29, 2008, at 6:45 PM, Faye Li wrote:
>
> Hi,
>
>
> There are about 200 topics in Freebase that are typed as both /film/
>
> film
>
> and /tv/tv_program, a co-typing that was previously deemed
>
> incompatible.
>
> Bryan Cheung and I looked through a few instances of them, and some
>
> are
>
> clearly mistyped, some are feature-length TV episodes or miniseries
>
> arguably marketed as movies, while others are made-for-TV movies that
>
> qualify for both types.
>
>
> So, does the co-typing of /film/film and /tv/tv_program make sense?
>
> Does
>
> it apply to feature-length TV episodes and miniseries in addition to
>
> made-for-TV movies, or only some of the above? Should there emerge a
>
> new
>
> type altogether (/film/tv_movie? /tv/tv_movie?) for it?
>
>
> The problem of cotyping is that the two types, for obvious reasons,
>
> have
>
> overlapping properties: producers, actors, etc. I'm not as concerned
>
> about having to enter the same data twice as I am about the type
>
> implication of doing so, where the same actor then gets cotyped as
>
> both
>
> /tv/actor and /film/actor, just for being in a TV movie! Ditto for the
>
> producer. On the other hand, /tv/tv_program has no director property,
>
> which is attached to /tv/tv_series_episode, and /film/film has no TV
>
> channel property that is part of the data about a TV movie. So
>
> without a
>
> new type, both types are needed to capture all the data. And by the
>
> way,
>
> when I say I'm not *as* concerned about having to enter the same data
>
> twice, I mean I am concerned. ;)
>
>
> Examples:
>
> 1) The three-hour miniseries "Battlestar Galactica" that was a pilot
>
> to
>
> the new series, co-typed with the unholy combo of /film/film,
>
> /tv/tv_program, and tv/tv_series_episode:
>
> http://freebase.com/view/guid/9202a8c04000641f80000000009aaffd
>
>
> 2) "Love Comes Softly", a Hallmark Channel movie original starring
>
> Katherine Heigl, poster child (the movie, not her) for the new TV
>
> Movie
>
> type if there would be one, currently typed as /film/film:
>
> http://freebase.com/view/en/love_comes_softly
>
>
> 3) Too many BBC drama series of "Jane Eyre", such as this one, cotyped
>
> as both /film/film and /tv/tv_program:
>
> http://freebase.com/view/guid/9202a8c04000641f8000000000c551bf
>
>
> -- Faye
>
> _______________________________________________
>
> Data-modeling mailing list
>
> Data-modeling at freebase.com
>
> http://lists.freebase.com/mailman/listinfo/data-modeling
>
>
> _______________________________________________
> Data-modeling mailing list
> Data-modeling at freebase.com
> http://lists.freebase.com/mailman/listinfo/data-modeling
>
>
>
> _______________________________________________
> Data-modeling mailing list
> Data-modeling at freebase.com
> http://lists.freebase.com/mailman/listinfo/data-modeling
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freebase.com/pipermail/data-modeling/attachments/20080430/c2cb0249/attachment-0001.htm