Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify audio and video "clips" with startTime/endTime properties on MediaObject #2021

Closed
earljwagner opened this issue Jul 24, 2018 · 8 comments

Comments

@earljwagner
Copy link
Contributor

The associatedMedia for a CreativeWork may actually be just a part of an AudioObject or VideoObject. For example, an anthology film may depict several short stories. We want each story to be associated with just its segment, not the entire film.

We should allow the segments or clips to be specified by adding startTime and endTime properties on MediaObject of type DateTime.

@martinbean
Copy link

I second this. I have a video on demand site that carries professional wrestling content, so it would be good if I had some way to mark up each match (as content providers can create “chapters” for individual matches).

@danbri
Copy link
Contributor

danbri commented Nov 30, 2018

Makes sense (and merged), but perhaps there's a role for adapting https://schema.org/Clip maybe as a second type on these objects too?

@danbri
Copy link
Contributor

danbri commented Nov 30, 2018

/cc @vholland

@vholland
Copy link
Contributor

http://schema.org/startTime and http://schema.org/endTime both expect ISO 8601 strings. As it is difficult to specify an offset in ISO 8601, I suggest building off @danbri 's suggest of using https://schema.org/Clip.

We can then add the following properties to Clip:
startOffset: The start time of the clip expressed as the number of seconds from the beginning of the longer work.

endOffset: The start time of the clip expressed as the number of seconds from the beginning of the longer work.

An example of this new markup would be:

{
  "@context": "http://schema.org/",
  "@type": "VideoObject",
  "name": "Cat video",
  "duration": "P10M",
  "hasPart": {
    "@type": "Clip",
    "name": "Segment where cat jumps",
    "startOffset": 30,
    "endOffset": 45
  }
}

@vholland vholland reopened this Dec 20, 2018
vholland added a commit to vholland/schemaorg that referenced this issue Jan 18, 2019
@vholland
Copy link
Contributor

I didn't see objections, so implemented PR #2127

@RichardWallis
Copy link
Contributor

Implemented in release 3.5

@martinbean
Copy link

martinbean commented Apr 10, 2019

Just seen the comments on this.

As it is difficult to specify an offset in ISO 8601

Would an offset not just be a duration?
https://en.wikipedia.org/wiki/ISO_8601#Durations

It just seems weird that in the example given:

{
  "@context": "http://schema.org/",
  "@type": "VideoObject",
  "name": "Cat video",
  "duration": "P10M",
  "hasPart": {
    "@type": "Clip",
    "name": "Segment where cat jumps",
    "startOffset": 30,
    "endOffset": 45
  }
}

We now have a mixture of an ISO-style duration value (P10M) and seconds values in startOffset and endOffset.

@Downchuck
Copy link

We now have a mixture of an ISO-style duration value (P10M) and seconds values in startOffset and endOffset.

In addition, the example suggests startOffset and endOffset are integers - and while the spec is clear that it's numeric, implementations may not follow it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants