Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare CR draft ready for publication #268

Open
5 tasks done
nigelmegitt opened this issue Oct 16, 2024 · 7 comments · May be fixed by #269
Open
5 tasks done

Prepare CR draft ready for publication #268

nigelmegitt opened this issue Oct 16, 2024 · 7 comments · May be fixed by #269

Comments

@nigelmegitt
Copy link
Contributor

nigelmegitt commented Oct 16, 2024

  • Add Exit Criteria
  • Create Implementation Report page
  • Reference Implementation Report in SOTD
  • Add acknowledgements
  • Change maturity stage to CRS (CR Snapshot)
@nigelmegitt
Copy link
Contributor Author

I propose to set the Exit Criteria to be:

For this specification to exit the CR stage,
at least 2 independent implementations of every feature defined in this specification
but not already present in [TTML2] need to be documented in the implementation report.
The Working Group does not require that implementations are publicly available but encourages them to be so.

@nigelmegitt
Copy link
Contributor Author

I have created the Implementation Report page.

@nigelmegitt nigelmegitt linked a pull request Oct 16, 2024 that will close this issue
@nigelmegitt
Copy link
Contributor Author

Pull request prepared for this at #269.

@nigelmegitt
Copy link
Contributor Author

I checked the TTWG Charter's Success Criteria which says:

When considering suitability to advance any feature beyond Candidate Recommendation, at least two independent factors of verification for each normative requirement MUST be demonstrated, which may come, as relevant for that requirement, from any of:

  • Presentation implementation
  • Content-producing implementation
  • Validating implementation

I think my proposed CR Exit Criteria are compatible with that, without needing a change to be more specific.

@himorin
Copy link
Contributor

himorin commented Oct 18, 2024

I'm somehow curious about which DAPT feature is in TTML or not, in the implementation report.
It is clear that all tt/ttp/tta are TTML and daptm are DAPT, but I suppose we may be better to have some more text than every feature defined in this specification but not already present in [TTML2] in the report, since the report is to be checked by non-familiar colleagues from TTML world..

@nigelmegitt
Copy link
Contributor Author

@himorin the DAPT features are those defined as feature extensions at https://www.w3.org/TR/dapt/#extensions

@himorin
Copy link
Contributor

himorin commented Oct 21, 2024

@nigelmegitt Ahhh, I totally forgot about that section... Thank you for reminding!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants