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

Add clipBegin and clipEnd parameter attributes #486

Closed
wants to merge 4 commits into from

Conversation

nigelmegitt
Copy link
Contributor

@nigelmegitt nigelmegitt commented Nov 7, 2017

Closes #483.

Semantics defined but ISD generation algorithm not updated yet
because there’s an issue note there saying that it needs to be revised
for other reasons. I’ve added a similar note for #483 to include the
ISD pruning/truncation/extension semantics when that is done.

Also added to schemas and regenerated ED.

#483 Semantics defined but ISD generation algorithm not updated yet
because there’s an issue note there saying that it needs to be revised
for other reasons. I’ve added a similar note for #483 to include the
ISD pruning/truncation/extension semantics when that is done.

Also added to schemas and regenerated ED.
clipEnd should not be called clipBegin where it isn't supposed to be.
@palemieux
Copy link
Contributor

What problem is this intended to solve? It is not clear from #483

@nigelmegitt
Copy link
Contributor Author

<p>When revising, also include truncation/pruning/extension to deal with the
<loc href="#parameter-attribute-clipBegin">ttp:clipBegin</loc> and
<loc href="#parameter-attribute-clipEnd">ttp:clipEnd</loc> semantics.</p>
</issue>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

clipBegin and clipEnd should be authorial hints only and not affect processing. More specifically, it is not clear why they need to affect processing since the application already controls presentation of the document, including starting and stopping presentation/processing at timeline locations outside of ISD boundaries.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I disagree. This needs to be normative and to affect processing. It has no effect when the attributes are absent, so it has no backward compatibility issue.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You have simply not motivated at all whatsoever why the processing model needs to be modified. The TTWG really needs to stop modifying TTML2 unless necessary.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I have, at https://github.com/w3c/ttml2/issues/483#issuecomment-345283633 perhaps you did not spot that?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@palemieux ping?

Copy link
Contributor

@palemieux palemieux Dec 21, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nigelmegitt Thanks for the reminder. See additional thoughts in the ticket. For the record, you have not (yet) convinced me that creating additional ISDs is necessary.

@nigelmegitt nigelmegitt changed the base branch from gh-pages to master December 15, 2017 22:22
Copy link
Collaborator

@skynavga skynavga left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why would one want to author a document and then say that only part of the document applies? Clip begin and end sound a lot like query parameters one might find on an HTTP request on a media resource where one is asking the server to deliver a segment from a larger resource. It doesn't make sense to me to put such parameters into the larger resource, which is what you are asking for here.

@nigelmegitt
Copy link
Contributor Author

Clip begin and end sound a lot like query parameters

@skynavga They're nothing to do with query parameters. See the issue for the use case and motivation - in summary it's about the ability for a document author to define the temporal period during which the document defines behaviour.

If the parameter attribute names seem misleading, could you please propose alternative names?

@nigelmegitt
Copy link
Contributor Author

In order to make progress on TTML2, in the absence of a clear consensus, I'm closing this pull request, which can be reopened or moved to another repo if we want to pick it up again in the future.

@skynavga skynavga deleted the issue-0483-temporal-extent-params branch March 9, 2018 21:09
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

Successfully merging this pull request may close these issues.

3 participants