Re: Mapping of draft WebRTC user requirements and RFC 5194 ToIP/RTT

On 01/07/2019 15:40, White, Jason J wrote:

> Also, did you search RFC5194 for requirements that aren't covered by any of the existing use cases? For example, the ability to switch between voice/video/real-time text at any point in a conversation, or to invite a relay service into the conversation at any time, seem significant to me and could perhaps be better brought to the fore.

Just to reply to this in more detail. Yes. I've been reviewing them to 
identify where RTT (for now) but potentially other user requirements are 
met. Specifically regarding the items you mention here. I think the 
relay case is well covered by RFC 5194 where they say:

"#Use Case:  R21: Communication between the end participants SHOULD 
continue after
    the addition or removal of a text relay service, and the effect of
    the change should be limited in the users' perception to the direct
    effect of having or not having the transcoding service in the
    connection."

"#User Needs/Scenario:  R22: When setting up a session, it MUST be 
possible for a user to
    specify the type of relay service requested (e.g., speech to text or
    text to speech).  The specification of a type of relay SHOULD include
    a language specifier."

"#User Needs/Scenario:   R23: It SHOULD be possible to route the session 
to a preferred relay
    service even if the user invokes the session from another region or
    network than that usually used.

But I'm happy to discuss if you think this isn't sufficient or if there 
is anything missing.

Regarding the 'Switch' use case, do you think this is potentially 
covered by our draft user requirement ""Simultaneous Voice, Text & 
Signing" This state a scenario where: "A deaf user wishes to both talk 
on a call, send and receive instant messages via a text interface and 
watch and/or communicate via sign language using a video stream." [1]

I do however, like your use of the active verb however, and calling out 
the ability to 'switch' between modes. We could add this description to 
the user requirement?

Thoughts welcome, thanks.

Josh

[1] 
https://www.w3.org/WAI/APA/wiki/WebRTC_next_version_use_cases#Simultaneous_Voice.2C_Text_.26_Signing 


-- 
Emerging Web Technology Specialist/A11y (WAI/W3C)