ProtoXEP: Jingle Synchronized Real-Time Text#1541
Merged
Merged
Conversation
f2f6b44 to
1e219e2
Compare
2edc2a8 to
e3588b9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR submits a ProtoXEP draft for Jingle synchronized real-time text.
The draft defines a Jingle text content for Total Conversation use cases where audio, video and real-time text need to belong to the same conversational session. It explicitly distinguishes synchronized Jingle text from XEP-0301 fallback RTT.
Motivation
Implementation testing showed a practical gap: a browser client can establish a Jingle/WebRTC audio-video call while RTT still travels as ordinary chat outside the Jingle session. That works as live text, but it is not synchronized call media.
Main points
urn:xmpp:jingle:apps:rtt-sync:0.Validation
xmllintwas not available on the Windows test machine, so repository CI should perform the final canonical validation.IPR / process note
This is submitted as a discussion draft for the XSF standards process. The listed author is Edward Tie. Please indicate if any additional IPR confirmation or author metadata is required.