See also: IRC log
<trackbot> Date: 29 November 2012
Chair Sean Hayes
plh: Reply by Dec 15.
... charset parametre
... RFC3023 and diff
<plh> "If supplied, the charset parameter must match the XML encoding declaration."
plh: Remove all references.
mike: Detailed reply by
... Talk about this sentence.
If supplied, the charset parameter must match the XML encoding declaration, or if absent, the actual encoding
scribe: Filed a new Issue-197 on
... If supplied, the charset parameter must match the XML encoding declaration, or if absent, the actual encoding.
plh: Check XML spec.
plh: UTF-8 or 16 or you have to have a XML declaration.
mike: Even if only UTF-8 or 16, you still have issues.
plh: What is actual encoding definition?
mike: TTML 1.0 is silent. XML 1.0 is unclear.
<plh> [[ parsed entities which are stored in an encoding other than UTF-8 or UTF-16 MUST begin with a text declaration (see 4.3.1 The Text Declaration) containing an encoding declaration ]]
glenn: Discusses what XML 1.0 says.
sean: TTML doesn't specify this.
Is it premature to register a MIME type at this time.
... If we tackle all the issues for XML, we need to have a note on application of TTML using XML encoding.
glenn: Could have a TTML 1.0 SE appendix that defines a wire encoding.
mike: We are left with the specification telling us to do something without a MIME type.
mike: People are using dxfp.
[Discuss what we do in testing.]
mike: Let lapse. We can start over.
sean: Lapse and get ducks in a row with a new note and then re-register.
glenn: Still wish to put an annex in SE.
sean: Complete by next week's call.
Action Glenn Create an Annex on using of XML wire encoding in TTML 1.0 SE.
<trackbot> Created ACTION-132 - Create an Annex on using of XML wire encoding in TTML 1.0 SE. [on Glenn Adams - due 2012-12-06].
plh: Respond to IANA we won't be ready by Dec 15.
mike: We have most of the bits to redo a submisson that is acceptable to IANA.
Resolution: Agreed to give Glenn 1 week to write an Annex. If this doesn't materialize, send email to IANA on the expiration of the request.
<trackbot> ISSUE-182 -- Allow more than one profile to be used in the SDP-US. Add use of ttp:profile element. -- open
mmartin3: Added namespace.
... Can close.
<trackbot> ISSUE-182 Allow more than one profile to be used in the SDP-US. Add use of ttp:profile element. closed
<trackbot> ISSUE-190 -- Background vs Window Color -- pending review
mmartin3: Added example 2.
... Explanatory text.
glenn: Need colorization.
... copy into Visual Studio.
mike: On Issue-182, we don't address multiple profiles.
glenn: Strange to be different than TTML 1.0.
mmartin3: See also Conformance. [TTML10] allows zero or more profiles (ttp:profile in the head element) to be specified and used simultaneously. A presentation processor may reject documents it does not understand.
sean: Close on SE on Issue-183.
glenn: TTML 1.0 talks about semantically additive profiles.
sean: Algorithm exists.
sean: Have implemented TTML 1.0
and it gave me an answer using the algorithm.
... May need more text to describe.
mike: Agreed it should be in TTML
... DXFP 1.0 + SDP-US profile is the issue.
... Deal with in TTML 1.0.
glenn: How does ttp:profile constrain processor or content.
<trackbot> ISSUE-190 -- Background vs Window Color -- pending review
<trackbot> ISSUE-190 Background vs Window Color closed
<trackbot> ISSUE-188 -- Bounding SDP-US rendering complexity -- open
mmartin3: Descriptive text in
... Section A.3 http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10-sdp-us/Overview.html#Section4
Text: Consideration may be given to defining a rendering model that accounts for drawing performance.
mike: Need to capture for future?
sean: Create an issue on v.next.
pal: Change target for
deliverable for Issue-188.
... Add comment on why target was changed.
<trackbot> ISSUE-194 -- root container needs better definition -- open
mmartin3: Glenn added information in 7.4.2: http://dvcs.w3.org/hg/ttml/raw-file/tip/ttml10-sdp-us/Overview.html#constraints-8
mike: Why did you choose a note rather than a requirement?
glenn: Use SE terminology.
mike: Why not include in R0021 or R0022?
glenn: Clarification of what media object means in this context.
mike: OK with text.
<trackbot> ISSUE-194 root container needs better definition closed
<trackbot> ISSUE-196 -- Constraining encoding to UTF-8 -- open
mmartin3: 2 reqts Section
A TTML document must be concretely represented as a well-formed [XML10] entity. A TTML document must be concretely represented using the UTF-8 character encoding [UNICODE].
glenn: Describes reqts.
... Add normative references.
... document representation in table
<trackbot> ISSUE-196 Constraining encoding to UTF-8 closed
glenn: Added prose before
... Content Authors must adhere to and Presentation processors must support the following constraints:....
<trackbot> ISSUE-189 -- do regions scroll their flowed content? -- open
mmartin3: Example SE, text SDP-US pointed to it.
Asked a question about displayAlign.
scribe: Defer to Glenn on his questions.
glenn: Didn't know where to add
the example in SE.
... Discusses his concerns.
... Synchronic documents, no animation of the content.
... What is the need for this?
mike: Has alluded many experts how to simulate a scrolling region using synchronic timing is critical.
sean: This uses overflow to implement what looks like a roll-up.
glenn: For users' needs.
... Suggest an appendix to show applications of TTML.
sean: Put in new section after 1.2.
mike: Need to simulate where captions is an application.
Add empty section in SE as placeholder and point to it from SDP-US.
sean: Put all examples in an annex?
glenn: Add empty subsection
... Put in rough content in SE and then reference in SDP-US.
sean: We should close all issues and then agree to publish to Working Group Note.
pal: Read through document and then publish.
glenn: Editorial issues - need to
do some formating and text cleanup.
... Rewrite Conformance and Error Handling
... Publish as Last Call
... 2-4 week review
Resolution: To publish as Last Call this week with changes.
Final at New Year.
trackbot, end meeting
This is scribe.perl Revision: 1.137 of Date: 2012/09/20 20:19:01 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: mmartin3 Inferring Scribes: mmartin3 Default Present: [Microsoft], +1.408.771.aaaa, +1.425.658.aabb, Plh, +1.310.210.aacc, glenn, +1.858.847.aadd, Sean WARNING: No "Present: ... " found! Possibly Present: Microsoft Sean Text aaaa aacc aadd courtney glenn mike mike2 mmartin3 pal plh trackbot You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy Regrets: Frans and Andreas Found Date: 29 Nov 2012 Guessing minutes URL: http://www.w3.org/2012/11/29-tt-minutes.html People with action items:[End of scribe.perl diagnostic output]