- From: Nigel Megitt via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Dec 2022 12:45:28 +0000
- To: public-tt@w3.org
nigelmegitt has just created a new issue for https://github.com/w3c/ttml2: == No feature to indicate TTML2 profile attribute vocabulary _only_ == While working on w3c/dapt#43 I noticed that there's no feature that allows _only_ the TTML2 profile attribute vocabulary to be specified, without also requiring support for the TTML1-defined `#profile`. I expected to see this in `#profile-version-2` but that's defined as an extension to `#profile` and declares it to be an error to prohibit use of `#profile` and require or permit `#profile-version-2`. The possible options are: 1. Define some new feature, excluding `#profile`, e.g. `#profile-exclusive-version-2` 2. Just use `#contentProfiles` and `#processorProfiles` independently, without also supporting `#profile`. This probably doesn't have a very high priority to fix, but I'm raising it because I think in time we should be helping folk move away from `tt@ttp:profile` usage (i.e. `ttp:profile` attribute on the `tt` element), in favour of the newer vocabulary, and the current arrangement only goes half-way, in that it allows people to use both, but not to define a requirement that excludes the older vocabulary. Please view or discuss this issue at https://github.com/w3c/ttml2/issues/1261 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 20 December 2022 12:45:30 UTC