W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2011

Query: What does "context" mean in the context (sic) of requirement A15? [ACTION-6]

From: Harald Alvestrand <harald@alvestrand.no>
Date: Sat, 20 Aug 2011 18:54:43 +0200
Message-ID: <4E4FE6D3.3000409@alvestrand.no>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
Hello,

this is a promised action from Quebec:

in draft-ietf-rtcweb-use-cases-and-requirements-02, the following 
sentence occurs:

    ----------------------------------------------------------------
    A15             The web application MUST be able to identify the
                    context of a stream.
    ----------------------------------------------------------------

I indicated I had problems seeing a definition for the word "context", 
and found it hard to suggest implementations for it when I didn't know 
what it was.

The driving scenarios are the hockey game viewer, the multiparty on-line 
game with voice communication, the distributed music band and the video 
conferencing system with central server.

One of the possible interpretations of "context" is that the Web 
application MUST be able to associate an identifier with the stream 
(label, CNAME or "something else") that can be shared over a channel 
outside the media channel (for instance over the signalling path), so 
that  both ends of the media stream know that they're talking about "the 
same stream".

Another interpretation is that there has to be a set of information that 
one can gather from the media stream (for example - remote partner, 
format, identifier and so on) that together forms the context.

So - to the authors:

What did you intend when you wrote "context"?

And to the group:

What does the group think this requirement should be?

                   Harald (declaring action 6 discharged by the sending 
of this message)
Received on Saturday, 20 August 2011 16:55:12 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:25 UTC