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: Sat, 10 Dec 2011 19:51:35 +0000
Message-ID: <CAA2+3GJ0mgC-5zsTka9jv5oWAOLAPZ_Y3ER8yvwSWEXhWc=BFg@mail.gmail.com>
To: Gregg Kellogg <gregg@kellogg-assoc.com>
Cc: Dan Brickley <danbri@danbri.org>, public-vocabs <public-vocabs@w3.org>, "Evain, Jean-Pierre" <evain@ebu.ch>
Hello Gregg!

First of all, thanks for the detailed comments!

On Fri, Dec 9, 2011 at 10:30 PM, Gregg Kellogg <gregg@kellogg-assoc.com> wrote:
> 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".

The wording isn't quite right, you're absolutely right. Basically, we
need to express that it is the start of the first broadcast of the
last episode within that series/season. If the last episode keeps on
being repeated, we don't want want the series end date to change. So
perhaps something like 'start of first publication of the last episode
within that series/season' would work better?
>
> 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.

Yes, and same thing for RadioSeries (a bit further down the page)

>
> 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]:
>

Right, so that's indeed an issue I had when reading the current spec.
It  is not clear what the object of those plural properties is. If it
is a list, a plural is fine (but it makes it hard to map to other
vocabularies). However, it points to episode that also have an episode
number, so I assumed it pointed to individual episodes, that are then
ordered using this property. So really not sure! The spec definitely
doesn't make it clear. The example at http://schema.org/TVEpisode
seems to suggest the latter.

Does anyone from schema.org has more information about that? I guess
we should at least aim at making the range of such properties clear.

> 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.
>

Best,
Yves

> Gregg
>
> [1] https://dvcs.w3.org/hg/htmldata/raw-file/default/microdata-rdf/index.html#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
>>
>
>
Received on Saturday, 10 December 2011 20:16:59 GMT

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