Re: [clue] Participant info/type followup
Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 19 March 2014 19:46 UTC
Return-Path: <pkyzivat@alum.mit.edu>
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 70C181A07A1 for <clue@ietfa.amsl.com>; Wed, 19 Mar 2014 12:46:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
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 hpH4sIJJLtVO for <clue@ietfa.amsl.com>; Wed, 19 Mar 2014 12:46:16 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 94D671A0454 for <clue@ietf.org>; Wed, 19 Mar 2014 12:46:16 -0700 (PDT)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta03.westchester.pa.mail.comcast.net with comcast id fS4B1n0081ei1Bg53Xm7fK; Wed, 19 Mar 2014 19:46:07 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta24.westchester.pa.mail.comcast.net with comcast id fXm71n00Q3ZTu2S3kXm7Cb; Wed, 19 Mar 2014 19:46:07 +0000
Message-ID: <5329F3FF.7090606@alum.mit.edu>
Date: Wed, 19 Mar 2014 15:46:07 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Christian Groves <Christian.Groves@nteczone.com>, "clue@ietf.org" <clue@ietf.org>
References: <5318809E.2030204@nteczone.com> <5318AE5E.4050404@alum.mit.edu> <5318B0C9.1050603@nteczone.com> <5318B48E.3090300@alum.mit.edu> <53290C9B.6090106@nteczone.com>
In-Reply-To: <53290C9B.6090106@nteczone.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1395258367; bh=Pjq+w/rZ/rijZV1HHiJJEJiZLM9yrfxHSAkaInmb1Hk=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=k5aqvpCO+lpYVJLOeT/3pCjaswGxd/rnTEzwssF63fGWXOs97gl7fMrISH9X3/QZG KiLciVmI8ZNE0lQBrBWi3Fq6Eou6UvCH+fzxi8oM3gPgln8gSS/AA81tCutfrrib9+ ZJsGyQzc++x/p9JNlX3uZd1nfuPQXkFKgzNbC1bj8fRgZkcWDRj/CzrLBo5eaFwa2s SSSD05t2DEG+/QU77LF1GdB2oSPRUTz2jLd0QeoCbPJz9DBnDmNopchcsKckV1KQf+ K7DHE42D1hlzkqWzOs2aF1QIueGYGogxkNtfNZWNeRhlpl2I+v+QeOeogrZCRxxUll +aGPGH45NXq+Q==
Archived-At: http://mailarchive.ietf.org/arch/msg/clue/Ye13VJ_cJLvFcfzSMOgua4CEd_g
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 19:46:18 -0000
On 3/18/14 11:18 PM, Christian Groves wrote: > Hello Paul, > > "How" they differ is given by the example bullets below the sentence. If > you want something more normative we could remove the "For example". Yeah, I don't believe in specification by example. :-) IMO it is a bit dicey to base this distinction on the type of capture. I'm more comfortable with an explicit syntactic indication of the distinction, such as proposed by Roberta. Thanks, Paul > Regards, Christian > > On 7/03/2014 4:46 AM, Paul Kyzivat wrote: >> On 3/6/14 5:30 PM, Christian Groves wrote: >>> Hello Paul, >>> >>> The text says media type and presentation attribute. Is that the >>> relationship you're talking about? >> >> "How the generated content relates to the entity described in the >> participant info is dependent on media type and and the presentation >> attribute." >> >> I take that to mean that the relationship may be different for >> presentation streams than non-presentation streams. But it doesn't say >> *how* they differ. >> >> Thanks, >> Paul >> >>> Regards, Christian >>> >>> On 7/03/2014 4:20 AM, Paul Kyzivat wrote: >>>> Christian, >>>> >>>> I've read the quoted text several times, and I cannot figure out how >>>> to *derive* your example conclusions from it. The text says the >>>> relationship is dependent on the presentation attribute, but not how. >>>> >>>> AFAICT I could make a new definition where the a participant attached >>>> to a presentation capture means that the participant is shown in the >>>> presentation, and that would be equally compatible with the text. >>>> >>>> ISTM that more text is required to actually specify the relationships. >>>> >>>> Thanks, >>>> Paul >>>> >>>> On 3/6/14 2:05 PM, Christian Groves wrote: >>>>> 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 >>>> >>> >>> _______________________________________________ >>> clue mailing list >>> clue@ietf.org >>> https://www.ietf.org/mailman/listinfo/clue >>> >> >> > >
- Re: [clue] Participant info/type followup Christian Groves
- [clue] Participant info/type followup Christian Groves
- Re: [clue] Participant info/type followup Paul Kyzivat
- Re: [clue] Participant info/type followup Roberta Presta
- Re: [clue] Participant info/type followup Christian Groves
- Re: [clue] Participant info/type followup Christian Groves
- Re: [clue] Participant info/type followup Paul Kyzivat
- Re: [clue] Participant info/type followup Christian Groves
- Re: [clue] Participant info/type followup Roberta Presta
- Re: [clue] Participant info/type followup Christian Groves
- Re: [clue] Participant info/type followup Paul Kyzivat
- Re: [clue] Participant info/type followup Christian Groves
- Re: [clue] Participant info/type followup Duckworth, Mark
- Re: [clue] Participant info/type followup Christian Groves