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

Extensions should be easier to identify #260

Closed
cconcolato opened this issue Oct 10, 2017 · 2 comments
Closed

Extensions should be easier to identify #260

cconcolato opened this issue Oct 10, 2017 · 2 comments
Assignees
Labels
Milestone

Comments

@cconcolato
Copy link

In general, it is hard to identify the differences between IMSC1 and IMSCvNext.

Section F defining extension fragment identifiers is a copy of the one in IMSC1. It should either indicate that:

  • the extensions designators of IMSC1 are used (full URL)
  • it defines the same identifiers but with the IMSCvNext base URL
  • it reuses the designators defined in TTML2
  • or the section should be removed

Similarly, the first 4 subsections of Section 7 are copy/paste of IMSC1.0.1. I understand the need to have a self-contained document (although that's not the case regarding TTML2). I would suggest adding a sentence in each subsection indicating whether the text for each extension is identical to the one in IMSC1 or not.

@palemieux
Copy link
Contributor

@cconcolato The provisions are intended to be substantively identical unless noted otherwise in Annex L.

@palemieux
Copy link
Contributor

Section F indicates that:

The following sections define extension designations, expressed as relative URIs (fragment identifiers) relative to the IMSC 1.0 Extension Namespace base URI.

Propose to add note that this is specifically not IMSCvNEXT namespace.

@palemieux palemieux self-assigned this Oct 11, 2017
@palemieux palemieux added this to the imscvNEXT FPWD milestone Oct 12, 2017
@palemieux palemieux modified the milestones: imsc1.1 FPWD, imsc1.1 WD2 Oct 20, 2017
@palemieux palemieux removed the pr open label Jan 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants