W3C home > Mailing lists > Public > public-vocabs@w3.org > December 2011

Re: Schema.org TV vocabulary - opening discussion

From: Yves Raimond <Yves.Raimond@bbc.co.uk>
Date: Tue, 13 Dec 2011 10:05:18 +0000
To: Alexander Shubin <ajax@yandex-team.ru>
Cc: Gregg Kellogg <gregg@kellogg-assoc.com>, Dan Brickley <danbri@danbri.org>, public-vocabs <public-vocabs@w3.org>, "Evain, Jean-Pierre" <evain@ebu.ch>
Message-ID: <20111213100517.GB20206@dvbstreamer.national.core.bbc.co.uk>
Hello!

> 
> >>Add Thing > CreativeWork > Programme
> > Don't we want to add some special properties for programme? Smth like anchorperson, duration, ...
> >
> > Yes, that's the point of the "Move all properties" item in the list of proposed changes.
> 
> Am I right that you are going to add new Programme type without any specific properties (director, actor, ...)? So it would have only properties inherited from CreativeWork?
> For me it seems like unfinished task. BTW new type may be inherited from more than one parent (see LocalBusiness inherited from Organization and Place). Maybe we should inherit Programme from Series as well (just my guess)? 
> 

The proposal says "Move all properties on TVSeries, TVSeason and TVEpisode to their direct parent (Series, Season, Episode) so that their radio counterparts inherit them as well" - so not at the CreativeWork level - at the Series/Season/Episode level.

> > * > Add contentTimePeriod, range 'TimePeriod'
> > The same question. Is it different from 'period' property of 'broadcastOn' (Service)?
> >
> > Yes - see above.
> 
> Sorry, didn't get it. :( Could you explain a bit detailed?

That I'd be happy with ISO8601 :-)

Best,
y

> 
> ----
> Best Regards,
> Alex
> Yandex.com
> 
> 
> -----Original Message-----
> From: yves.raimond@gmail.com [mailto:yves.raimond@gmail.com] On Behalf Of Yves Raimond
> Sent: Saturday, December 10, 2011 11:58 PM
> To: Alexander Shubin
> Cc: Gregg Kellogg; Dan Brickley; public-vocabs; Evain, Jean-Pierre
> Subject: Re: Schema.org TV vocabulary - opening discussion
> 
> Hello Alexander!
> 
> Thanks for all the detailed comments!
> 
> > Hi Dan, all,
> >
> > Some questions:
> > *
> >>In Series:
> >>Rename 'episodes' into 'episode' (object is a single Episode with a 
> >>position, not a list - confusing in the current spec) Rename 'seasons' into 'season'
> >>
> >>In Season:
> >>Rename 'episodes' to 'episode'
> >
> > Could you explain why should we rename these properties? As far as I understand it may be several seasons in series and several episodes in series and season as well? Am I mistaken?
> 
> See my email to Gregg. The spec, at the moment, doesn't make it clear what the range of those properties is supposed to be (a list? a individual episode?)
> 
> >
> > *
> >>Add Thing > CreativeWork > Programme
> >
> > Don't we want to add some special properties for programme? Smth like anchorperson, duration, ...
> >
> 
> Yes, that's the point of the "Move all properties" item in the list of proposed changes.
> 
> > * Add Thing > CreativeWork > Clip
> >
> > The same question. Can we add some specific properties for Clip type?
> >
> > * > Add Thing > TimePeriod
> >
> > What is TimePeriod? I mean is it smth more than mere ISO 8601 Time Intervals (http://en.wikipedia.org/wiki/ISO_8601#Time_intervals)?
> >
> 
> Agreed - that's one for Jean-Pierre. I would be happy with an ISO time interval on the service.
> 
> > * > Add 'broadcastOf' property, range 'Clip' or 'Episode', (JP) or 
> > Programme (also rename broadcastOf in 'source')
> >
> > Agree with renaming.
> >
> > *
> >> Add Thing > Event > Broadcast
> >> Add 'broadcastOn' property, range 'Service'
> >> Add 'broadcastOf' property, range 'Clip' or 'Episode', (JP) or 
> >> Programme (also rename broadcastOf in 'source') Add 'start', range 
> >> date Add 'end', range date
> >
> > What is the semantic of new 'start' and 'end' properties? We already have 'startDate' and 'endDate' in Event and 'period' property in Service. What is the difference from them?
> 
> You're right - we should use the properties inherited from Event. I removed those two lines from the proposal.
> 
> >
> > * > Add contentTimePeriod, range 'TimePeriod'
> >
> > The same question. Is it different from 'period' property of 'broadcastOn' (Service)?
> 
> Yes - see above.
> 
> Best,
> y
> 
> > ----
> > Best Regards,
> > Alex
> > Yandex.com
> >
> >
> > -----Original Message-----
> > From: Gregg Kellogg [mailto:gregg@kellogg-assoc.com]
> > Sent: Saturday, December 10, 2011 2:31 AM
> > To: Dan Brickley
> > Cc: public-vocabs; Evain, Jean-Pierre; Yves Raimond
> > Subject: Re: Schema.org TV vocabulary - opening discussion
> >
> > In Series/Season:
> >
> > [[[
> > Modify 'endDate' description to be 'start of the last first publication of an episode within that series/season'
> > ]]]
> >
> > "last first publication"? Perhaps just "last publication".
> >
> > Regarding moving TVSeries (for example) under Series. Do you expect to publish schema:TVSeries rdfs:subClassOf schema:Series? This is really a broad question for all hierarchical classes.
> >
> > Also, is it expected that the range of schema:episode is an rdf:List? How about an OWL restriction on the cardinality of schema:episode? What is the strategy for indicating that some properties really relate to an ordered collection? This was suggested in the Microdata to RDF mapping for the following properties as well [1]:
> >
> > blogPosts, breadcrumb, episodes, events, itemListElement, musicGroupMember, seasons, ...
> >
> > Really, just an example for how to treat properties that should take an RDF Collection, as this is the data-model that the microdata JSON encoding would take.
> >
> > Gregg
> >
> > [1] 
> > https://dvcs.w3.org/hg/htmldata/raw-file/default/microdata-rdf/index.h
> > tml#example-registry
> >
> > On Dec 9, 2011, at 9:09 AM, Dan Brickley wrote:
> >
> >> Following up on the discussion here a few weeks ago, around 
> >> Schema.org's TV vocabulary (see 
> >> http://lists.w3.org/Archives/Public/public-vocabs/2011Oct/0095.html
> >> and nearby)
> >>
> >> This work has moved along a bit, many thanks to Jean-Pierre (EBU) and 
> >> to Yves and others at the BBC for their investigations and 
> >> collaboration.
> >>
> >> The work-in-progress results are linked from our Wiki homepage 
> >> http://www.w3.org/wiki/WebSchemas as 
> >> http://www.w3.org/wiki/TVRadioSchema and are a set of additions and 
> >> edits that would help improve this area of schema.org.  While it's 
> >> not a fully polished proposal with use cases and explanations for 
> >> everything, I think it's worth drawing wider attention to it at this 
> >> point.
> >>
> >> The first thing it does is provide a home for radio alongside TV, as 
> >> well as basics for better supporting description of clips, and 
> >> broadcasts. Yves and Jean-Pierre might want to say more.
> >>
> >> If you're interested in helping improve schema.org's coverage of 
> >> these topics, do please take a look at 
> >> http://www.w3.org/wiki/TVRadioSchema
> >> and comment here or in the wiki...
> >>
> >> cheers,
> >>
> >> Dan
> >>
> >
> >
> >
> 
> http://www.bbc.co.uk/
> This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
> If you have received it in error, please delete it from your system.
> Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.
> 					
Received on Tuesday, 13 December 2011 10:05:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 May 2012 06:48:58 GMT