Format and profile have different roles
The W3C TTML 2 recommendation defines a broad timed-text language. IMSC Text Profile 1.3 is a separate W3C recommendation dated 21 May 2026. A conformance statement needs to identify the applicable profile rather than treating every TTML feature as required by every IMSC receiver.
For an illustrative workflow, a subtitle producer exports a rich timed-text document and a receiver expects a narrower interchange profile. Both can use XML syntax while disagreeing about permitted features or presentation. The common file shape does not establish interoperability.
Conversion needs semantic review
Turning one timed-text format into another can affect styling, positioning and other supported information. A successful file conversion is not proof that the intended viewing experience is preserved. Check timing, readable presentation and meaningful content through the actual supported renderer.
Imagine two simultaneous speakers are distinguished by positioning in the source. A conversion that flattens both into one unlabelled line can lose useful meaning even if its output parses. This is an original quality example, not a claim that a named converter or service has that defect.
Retain an accountable handover
For a publisher or developer, record source format, claimed profile, export tool version, receiving implementation and observed result. A viewer can instead provide the programme, selected language, device and content position. Keep those roles clear rather than expecting viewers to edit protected subtitle XML.
The existence of a W3C recommendation does not prove every browser or television implements it. Verify the receiving product's current documentation and a relevant observed playback task. This reference does not assert that IPTV Australia supplies TTML or IMSC tracks or that a real conversion test was run; it explains the profile boundary and a concrete meaning-preservation check.
Questions about this guide
Is all XML subtitle text interchangeable?
No. Format, conformance profile and implementation matter.
Does parsing after conversion prove equivalent accessibility?
No. Meaning, timing and presentation still need review.