Re: ISSUE-402 (Ambiguous delimiter requirements for two value attributes): The permitted delimiters for two value attributes like cellResolution and frameRateMultiplier are undefined [TTML 1.0]

Thanks Glenn, you're right, I had missed the LWSP (linear white space) requirement. Apologies for the noise.

Nigel


From: Glenn Adams <glenn@skynav.com<mailto:glenn@skynav.com>>
Date: Monday, 17 August 2015 16:15
To: Timed Text Working Group <public-tt@w3.org<mailto:public-tt@w3.org>>
Subject: Re: ISSUE-402 (Ambiguous delimiter requirements for two value attributes): The permitted delimiters for two value attributes like cellResolution and frameRateMultiplier are undefined [TTML 1.0]
Resent-From: <public-tt@w3.org<mailto:public-tt@w3.org>>
Resent-Date: Monday, 17 August 2015 16:16

I just closed this. See the comments I added.

On Mon, Aug 17, 2015 at 4:58 AM, Timed Text Working Group Issue Tracker <sysbot+tracker@w3.org<mailto:sysbot+tracker@w3.org>> wrote:
ISSUE-402 (Ambiguous delimiter requirements for two value attributes): The permitted delimiters for two value attributes like cellResolution and frameRateMultiplier are undefined [TTML 1.0]

http://www.w3.org/AudioVideo/TT/tracker/issues/402


Raised by: Nigel Megitt
On product: TTML 1.0

The specification of attributes like tts:cellResolution and tts:frameRateMultiplier omits a required delimiter between the two values in the attribute value string. Instead of e.g.

ttp:frameRateMultiplier
  : numerator denominator

 which looks as though there must be no white space separating the values, it should say something like

ttp:frameRateMultiplier
  : numerator whitespace denominator

 with whitespace defined somewhere.

Taken literally the specification does not match the examples and is unparseable. Also it is unclear which whitespace delimiters are permitted - is it a single space character only, or should any other XML whitespace be parsed as a delimiter?

Received on Monday, 17 August 2015 15:31:11 UTC