Re: Series

We could create Series as an Intangible base Type that could be used in combination with CreativeWork, Event etc. to produce the relevant series Type we are suggesting.

eg.  BroadcastSeries a subtype of CreativeWork & Series
       LiterarySeries a subtype of CreativeWork & Series
       BaseballSeries a subtype of SportsEvent & Series
       MovieSeries a subtype of Movie & Series
      etc.

As to properties for Series, seriesName would be an [optional] minimum, but not much else.

~Richard

On 13 Jun 2014, at 14:03, Gregg Kellogg <gregg@kellogg-assoc.com<mailto:gregg@kellogg-assoc.com>> wrote:

On Friday, June 13, 2014, Wallis,Richard <Richard.Wallis@oclc.org<mailto:Richard.Wallis@oclc.org>> wrote:
A couple of recent threads have highlighted the current very TV/Radio-ness of the Series<http://schema.org/Series> Type.  Hardly surprising considering the proposal it came from.

It seems that it would be better if Series became a generic Type with more focussed sub-types such as TVSeries, RadioSeries, GameSeries, MovieSeries, LiterarySeries, etc.

Looking at the current TV/Radio Series structure, this might be best handled by the introduction of a BroadcastSeries Type to serve the current purpose of Series, which then would be replaced by a more generic Series Type definition:

CreativeWork>Series>BroadcastSeries>TVSeries
CreativeWork>Series>BroadcastSeries>RadioSeries
CreativeWork>Series>LiterarySeries
CreativeWork>Series>MovieSeries
CreativeWork>Series>>GameSeries
etc.

I've long advocated this kind of abstraction. Taking it a step further, a Baseball Series is very similar, but, of course, is not a CreativeWork. These could also be considered Events, with an individual a Episode a sub-event.

There are other things that start out as CreativeWork classes, but become more abstract; an ItemList probably shouldn't be a kind of CreativeWork, IMO. Perhaps these are Intangeble?

Gregg

~Richard