Media Objects: Replace SRT with WebVTT Support

1 Initial Problem

Subtitles for video objects currently must be uploaded in srt format. However this format is outdated and has been replaced by WebVTT, see https://www.w3.org/TR/webvtt1/

2 Conceptual Summary

The subtitle uploads should support WebVTT files. Depending on funding, we might support srt for one ILIAS release in parallel.

3 User Interface Modifications

3.1 List of Affected Views

• Media Object: Subtitle Uploads

3.2 User Interface Details

User Interface should not change that much.

3.3 New User Interface Concepts

No new user interface concepts.

3.4 Accessibility Implications

WebVTT should support accessibility needs in the same was srt did. There are different kinds of use cases. We will implement the "subtitle" kind of case. Others like "caption" or "chapters" may follow.

4 Technical Information

No technical issues.

5 Privacy

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Killing, Alexander [alex]
• Maintainer: Killing, Alexander [alex]
• Implementation of the feature is done by: tbd

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• …

9 Discussion

10 Implementation

{ The maintainer has to give a description of the final implementation and add screenshots if possible. }

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Privacy

Information in privacy.md of component: updated on {date} by {user} | no change required

Approval

Approved at {date} by {user}.