RE: ISSUE-122: consistency of ratio/resolution/origin/extent syntax [DFXP 1.0]

I concur with a minor caveat (nominator and denominator are not <length>, but just integers).
In fact I suggested the required denominator in a previous issue which was overruled :-)

Sean Hayes
Media Accessibility Strategist
Accessibility Business Unit
Microsoft

Office:  +44 118 909 5867,
Mobile: +44 7875 091385

-----Original Message-----
From: public-tt-request@w3.org [mailto:public-tt-request@w3.org] On Behalf Of Timed Text Working Group Issue Tracker
Sent: 09 June 2009 7:58 AM
To: public-tt@w3.org
Subject: ISSUE-122: consistency of ratio/resolution/origin/extent syntax [DFXP 1.0]


ISSUE-122: consistency of ratio/resolution/origin/extent syntax [DFXP 1.0]

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


Raised by: Glenn Adams
On product: DFXP 1.0

at present, ttp:cellResolution, ttp:frameRateMultiplier, ttp:pixelAspectRatio, tts:origin, and tts:extent express a ratio, a point (two coordinates), or a rectilinear area (two lengths) using varying syntax as follows:

ttp:cellResolution           : columns rows
ttp:frameRateMultiplier : numerator ( ':' denominator )?
ttp:pixelAspecRatio        : width ':' height
tts:origin                          : <length> <length>
tts:extent                         : <length> <length>

i propose that the syntax of these be more unified, and, in particular, that the ':' separator used in ttp:frameRateMultiplier and ttp:pixelAspectRatio be eliminated (using whitespace instead), and that the denominator be required on frameRateMultiplier;

with this minor change, all of these expressions will consist of two required terms separated by a whitespace separator

Received on Tuesday, 9 June 2009 17:33:46 UTC