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

Hbbtv mpeg2ts 3 #6

Open
wants to merge 39 commits into
base: master
Choose a base branch
from
Open

Conversation

c-alpha
Copy link

@c-alpha c-alpha commented Sep 16, 2014

This is pull request 5 out of 9 and it contains updates proposed by HbbTV for the section on MPEG2-TS. See the visual diff to silviapfeiffer/HTMLSourcingInbandTracks:master for a better overview than the diffs. Please ignore the (many) individual diffs contained in this request, and focus on the diffs (source and visual) alone.

Change notes and rationale:

  • Added new columns to make room for DVB and ISDB in the table for track attributes for sourced text tracks.
  • Again quoting style fix in the ATSC row to be in-line with the rest of the document.
  • Added rules on populating the track attributes for DVB TS.
  • ISDB needs to be filled in by someone knowledgeable.

c-alpha and others added 30 commits June 25, 2014 16:12
rest of the world, DVB and ISDB systems need to be taken into account,
too.
(spoken word only);
almost done with captions cues
clarified container format for subtitles and captions
…we need to make use of the triplet, and where possible of the component_tag.
…ngInbandTracks

# By Silvia Pfeiffer
# Via boblund (2) and Silvia Pfeiffer (1)
* 'master' of https://github.com/silviapfeiffer/HTMLSourcingInbandTracks:
  Clarify how CEA708 captions are exposed in MPEG-2.
  Clarify the possibilities of exposing in-band MPEG-2 SCTE 27 subtitles.
  Fix typo s/TextTrackCue/TextTrackCue/
  Make document more readable and fix captionservice link.

Conflicts:
	index.html
Merge commit '81c4b26e5735fbe3e374ab6ba52e438a81ba5b14'

* commit '81c4b26e5735fbe3e374ab6ba52e438a81ba5b14':
  Removed DASH-AVC-TT in localBiblio
  Acknowledge the origins of this spec in the HTML WG and WHATWG.
  Fix duplicate definitions.
  ISOBMFF TTML as DataCue
  Added alternatie VTTCue mapping for ISOBMFF TTML and 3GPP
  Fixed up <p> comments
  Explicitly stated how WebVTT and TTML text tracks are identified
  ISOBMFF text tracks and captions
  DASH TTML file as DataCue
  Added alternative VTTCue mapping for DASH file TTML
  Fixed up <p> tags
  Exposing DASH text tracks as cues
  mpeg2ts: 708 captions in AVC video
  MPEG-2 TS: Fixed @language for descriptions and added ref for @kind descriptions
  Add text to set @Label from mpeg-2ts data.
* removed metadata tracks as not needed
* removed subtitles and captions cues as not use-case
* editorial tidy up
c-alpha and others added 9 commits August 27, 2014 11:55
* added notes to indicate that 'namespace' needs discussion
* isobmff:
  2014-08-27 telechat: * added notes to indicate that 'namespace' needs discussion
  isobmff: current state of discussions with Nigel
* dash:
  2014-08-27 telechat: * editorial tidy up
  dash: fix angle brackets and unneeded <p> tags
  Jon's CR r01
  starting changes to DASH section

Conflicts:
	index.html
* mpeg2-dvb: separated audio and video
* mpeg2-dvb: deferring to annex J of DVB-SI for supplementary audio
* mpeg2: text tracks only ever use one component
<p>
In the case of CEA 708 closed captions, decimal representation of the 'caption_service_number' in the 'Caption Service Descriptor' in the PMT.
</p>
<p>
Copy link
Owner

Choose a reason for hiding this comment

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

Whitespace issues in this paragraph.

@silviapfeiffer
Copy link
Owner

I'm beginning to think that the different types of MPEG2-TS files need completely different sections. This is starting to become unreadable.

@c-alpha
Copy link
Author

c-alpha commented Sep 22, 2014

Frankly, I thought about a different way of laying it out initially too. Having separate sections dedicated to ATSC, DVB, etc. would likely be more in line with the needs of a browser implementer. On the other hand, the spec text may be easier to maintain and keep consistent if the criteria for the different broadcast standards are side by side. Looking at it from the HTML diff, dedicated sections might seem easier to digest. Using the visual diff, the side-by-side in a table might seem more readable. Finally, for an application author (and I think that would be the majority of readers?) it would seem beneficial to see at a glance how his application will behave/perform when used with different broadcast standards? With separate sections, that could seem more difficult to figure out.

Overall, I'm honestly pretty passionless on what way to structure this. Whatever works best for you and your audience.

@silviapfeiffer
Copy link
Owner

The majority of readers should be browser and other UA developers. Application authors should not need to understand this as browsers will simply provide the support.

Let's see how the discussion on the mailing list goes. But I'm pretty keen to have this as a separate section.

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