See also: IRC log
<trackbot> Date: 05 June 2014
<scribe> scribeNick: nigel
nigel: Philippe told us this week that we can't meet on Monday and Friday as requested but could do Monday and Thursday
tmichel: It's due to lack of meeting room space.
RESOLUTION: We will meet at TPAC on the Monday and Thursday
action-232?
<trackbot> action-232 -- Glenn Adams to Consider also defining @validation on ttp:profile, in addition to (override) tt:tt -- due 2014-04-01 -- PENDINGREVIEW
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/232
glenn: I added a validation and validationAction attribute.
nigel: We had discussion about the default value being warn instead of abort
glenn: I still prefer it to be abort.
nigel: I have in mind the case that the user wishes to present a document of unknown provenance but the default validationAction causes an abort
close action-232
<trackbot> Closed action-232.
<glenn> action glenn to define default for @validationAction to be warn if @validation is optional; otherwise, default is abort
<trackbot> Created ACTION-296 - Define default for @validationACTION to be warn if @validation is optional; otherwise, default is abort [on Glenn Adams - due 2014-06-12].
action-254?
<trackbot> action-254 -- Glenn Adams to Add errata note for ttml1 pointing at constraint in smil prohibiting dur of zero, add normative text to ttml2 -- due 2014-04-01 -- PENDINGREVIEW
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/254
glenn: There's still an action to avoid using 'wilful violation' wording
close action-254?
<trackbot> Closed action-254.
<glenn> ACTION glenn to soften language about 'willful violation' regarding treatment of duration zero
<trackbot> Created ACTION-297 - Soften language about 'willful violation' regarding treatment of duration zero [on Glenn Adams - due 2014-06-12].
action-284?
<trackbot> action-284 -- Glenn Adams to Create the registry page -- due 2014-05-01 -- PENDINGREVIEW
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/284
close action-284?
<trackbot> Closed action-284.
action-291?
<trackbot> action-291 -- Nigel Megitt to Find the related issue that describes the need to restrict or extend individual profile features -- due 2014-05-29 -- PENDINGREVIEW
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/actions/291
close action-291
<trackbot> Closed action-291.
https://www.w3.org/wiki/TTML/changeProposal012
<glenn> https://dvcs.w3.org/hg/ttml/raw-file/default/ttml2/design/TPAC2013-TTMLProfiles.pdf
glenn: describes changes made for issues in change proposal 12 by reference to page 8 of the pdf presentation
dsinger: I think combination content profiles inferred within a document is a mistake and we should only have the OR expression not the AND, i.e. those wishing to use an alternate profile should define it separately.
glenn: There are multiple uses of this, either externally in defining a profile and within a specific document for 'on the fly' processing.
dsinger: It's the second of those, the 'on the fly' that I think is a mistake.
glenn: We should think about that some more and think about if we want to make it asymmetrical, with respect to content profile combinations as opposed to processor profile combinations.
nigel: I believe the combination of profiles is described in issue-206.
glenn: I think david's raising a new issue
<Dsinger_> Issue-206
<trackbot> Issue-206 -- Add ttp:profileCombination parameter -- pending review
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/206
glenn: It's that the complexity
of supporting on the fly combination of content profiles is too
complex and not needed.
... I've added two editors notes, the second it in 5.2.4.2 that
describes the content profile combination semantics
... If a receiving processor is able to do validation and it's
required then it would use the content profiles otherwise
there's no other use for content profiles. If we define
validation processing well even in the context of content
profiles then that leaves the judgement of complexity to the
reader.
... I would like to propose that we discuss profiles further at
the upcoming F2F in September, and that I write some
explanatory documentation, both in the spec and for the
meeting.
close issue-206
<trackbot> Closed issue-206.
issue-261?
<trackbot> issue-261 -- signaling document profile conformance is separate from decoder presentation requirements -- pending review
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/261
close issue-261
<trackbot> Closed issue-261.
issue-266?
<trackbot> issue-266 -- add ability for instance documents to declare what profile(s) it conforms to -- pending review
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/266
close issue-266
<trackbot> Closed issue-266.
issue-280?
<trackbot> issue-280 -- Add ability to define a profile from multiple profiles. -- pending review
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/280
close issue-280
<trackbot> Closed issue-280.
issue-263?
<trackbot> issue-263 -- profile feature set may not match intended feature constraints -- pending review
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/263
glenn: ttp:feature can now be specified with either an extends or a restricts (or both, currently) attribute.
<glenn> action glenn to either proscribe or define semantics on specifying both @extends and @restricts on a ttp:{feature,ext3ension}
<trackbot> Created ACTION-298 - Either proscribe or define semantics on specifying both @extends and @restricts on a ttp:{feature,ext3ension} [on Glenn Adams - due 2014-06-12].
<glenn> dsinger: mea culpa
nigel: an example for this may be extending or restricting permitted values e.g. for the tts:color attribute.
glenn: ttp:permitFeatureNarrowing
and ttp:permitFeatureWidening are attributes that describe
whether or not processors that implement narrower/wider
versions to claim support.
... It's not predictable what the author wants so I added the
attributes to cover those cases specifically.
nigel: Can we leave that open until there are some examples e.g. SDP-US color space.
issue-299?
<trackbot> issue-299 -- dur must be greater than zero -- pending review
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/299
close issue-299
<trackbot> Closed issue-299.
issue-318?
<trackbot> issue-318 -- Hypothetical Render Model glyph copy assumes no sub-pixel positioning -- pending review
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/318
close issue-318
<trackbot> Closed issue-318.
issue-320?
<trackbot> issue-320 -- Is normative SMPTE 2052 reference okay? -- pending review
<trackbot> http://www.w3.org/AudioVideo/TT/tracker/issues/320
close issue-320
<trackbot> Closed issue-320.
nigel: I will send regrets for 26th June and 3rd July
This is scribe.perl Revision: 1.138 of Date: 2013-04-25 13:59:11 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/action/ACTION/ Succeeded: s/action/ACTION/ Succeeded: s/rrsagent. generate minutes// Succeeded: s/Resolution/RESOLUTION/ Found ScribeNick: nigel Inferring Scribes: nigel Default Present: +44.192.341.aaaa, nigel, +1.720.897.aabb, glenn, +41.22.717.aacc, Frans-EBU, jdsmith, pal, tmichel, Plh, dsinger Present: Frans-EBU Plh dsinger glenn jdsmith nigel pal plh tmichel Regrets: mdolan Found Date: 05 Jun 2014 Guessing minutes URL: http://www.w3.org/2014/06/05-tt-minutes.html People with action items:[End of scribe.perl diagnostic output]