Re: [clue] Participant info/type followup

Christian Groves <Christian.Groves@nteczone.com> Wed, 19 March 2014 03:16 UTC

Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A574A1A034F for <clue@ietfa.amsl.com>; Tue, 18 Mar 2014 20:16:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Imk3EvVlpRxM for <clue@ietfa.amsl.com>; Tue, 18 Mar 2014 20:16:44 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7DA71A04A4 for <clue@ietf.org>; Tue, 18 Mar 2014 20:16:40 -0700 (PDT)
Received: from ppp118-209-41-35.lns20.mel4.internode.on.net ([118.209.41.35]:59135 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1WQ6zW-0005os-P4 for clue@ietf.org; Wed, 19 Mar 2014 14:16:30 +1100
Message-ID: <53290C0B.8010805@nteczone.com>
Date: Wed, 19 Mar 2014 14:16:27 +1100
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: clue@ietf.org
References: <5318809E.2030204@nteczone.com> <531A0A3E.8060904@unina.it>
In-Reply-To: <531A0A3E.8060904@unina.it>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/y-EamJhQX7e1qj-76f1gu8cRlr4
Subject: Re: [clue] Participant info/type followup
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Mar 2014 03:16:50 -0000

Hello Roberta,

Please see my comments below.

Regards, Christian

On 8/03/2014 5:04 AM, Roberta Presta wrote:
> Hello Christian,
>
> if we want to distinguish between the owner of the device that is 
> generating the capture and the person that is represented in the 
> capture, a possible solution could be the following:
> - having a <participants> section within the adv
[CNG] I think this is probably a good idea. I thought this was a way to 
minimize duplication rather than being related to distinguishing between 
the owner and who is viewed.

> - re-define the <view> attribute (which is already used to specify 
> what is represented in the capture - and which can be used also for 
> audio capture), so that the view attribute can contain the 
> reference(s) to the represented participants, or define a new 
> attribute dedicated to the represented participants
[CNG] I'm not sure we need to re-define view. I think we just need to be 
more specific on the scope of the existing participant attributes.
> - define a new attribute saying that a certain capture comes from the 
> some participant's device
[CNG] We could do this. I'm not sure its strictly needed however I'm not 
against it. I'd like to hear other opinions.
> What is your feeling about it?
>
> Roberta
>
>
>
> Il 06/03/2014 15:05, Christian Groves ha scritto:
>> Hello all,
>>
>> To follow up on Jonathon's comments on participant info/type and the 
>> semantics and particularly how it relates to a presentation. Here's a 
>> first stab at some text to stimulate some discussions.
>>
>>
>> "The participant info attribute allows a provider to associate 
>> participant information with the capture source. When used in an 
>> individual capture it indicates that the captured content (e.g. 
>> video/audio/text etc.) as opposed to the actual media streams is 
>> generated from the entity described. How the generated content 
>> relates to the entity described in the participant info is dependent 
>> on media type and and the presentation attribute.
>>
>> For example:
>> - a video capture with participant info would indicate that the video 
>> contains a picture of the entity associated with the information 
>> provided.
>> - a video capture with participant info and the presentation 
>> attribute would indicate that the presentation video is associated 
>> with the participant but could contain any video content.
>> - a text capture with participant info would indicate that the text 
>> is generated from the actual participant.
>> - a text capture with participant info and the presentation attribute 
>> would indicate that the text is associated with the participant but 
>> could contain any text content."
>>
>> Comments?
>>
>>
>> Regards, Christian
>>
>> _______________________________________________
>> clue mailing list
>> clue@ietf.org
>> https://www.ietf.org/mailman/listinfo/clue
>>
>
> _______________________________________________
> clue mailing list
> clue@ietf.org
> https://www.ietf.org/mailman/listinfo/clue
>