New feature requests - working group process

The thread re Issue-286 has apparently come full circle, in an attempt to reach a resolution. This raises the possibility that we may be about to enter an infinite loop, which wouldn't be ideal.

Here's an explanation for this loop: For TTML1SE the TTWG made mainly non-substantive, editorial, edits to clarify meaning and usage based on the requirements met by TTML1. For TTML2 the scope has increased to include features that meet new requirements or requirements not fully met by TTML1SE. The Issue-286 discussion has highlighted to me that the requirements can sometimes be equated with their implementation, which can lead to difficulties in understanding and generate solution proposals that might make sense in their own right but don't meet the intended requirements, probably because they haven't been communicated well enough.

Proposal 1: for new features the proposer should initially draft the requirements and add them to the wiki with an associated change proposal.

Proposal 2: edits to TTML2 to meet new features should be verified against those requirement, and the extent to which they are wholly or partially met should be recorded against the change proposal, alongside the impact of the proposed edit. This may be used to update the existing documentation that currently reflects TTML1, or a new TTML2 requirements document should be forked for the purpose.

New change proposals and/or requirements may continue to have associated Issues against the relevant Product in the tracker, i.e. I am not proposing to add TTML2_Requirements or TTML2_ChangeProposals products.

It may be that process issues like this have been discussed before within the WG, in which case I'd appreciate a pointer to resolutions or agreed approaches that we can reuse, as they would have been before I joined the group.

Kind regards,

Nigel




----------------------------

http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

---------------------