Re: [Slim] How to know modality in draft-ietf-slim-negotiating-human-language
Gunnar Hellström <gunnar.hellstrom@omnitor.se> Fri, 13 October 2017 12:21 UTC
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: slim@ietfa.amsl.com
Delivered-To: slim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16F0B132705 for <slim@ietfa.amsl.com>; Fri, 13 Oct 2017 05:21:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 jUeDzl9-flg0 for <slim@ietfa.amsl.com>; Fri, 13 Oct 2017 05:21:44 -0700 (PDT)
Received: from bin-vsp-out-02.atm.binero.net (bin-mail-out-05.binero.net [195.74.38.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 334F913213D for <slim@ietf.org>; Fri, 13 Oct 2017 05:21:44 -0700 (PDT)
X-Halon-ID: 067c3223-b011-11e7-99c0-005056917f90
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [87.96.178.34]) by bin-vsp-out-02.atm.binero.net (Halon) with ESMTPSA id 067c3223-b011-11e7-99c0-005056917f90; Fri, 13 Oct 2017 14:21:23 +0200 (CEST)
To: Randall Gellens <rg+ietf@randy.pensive.org>, "slim@ietf.org" <slim@ietf.org>
References: <376ade2a-be29-33a6-b539-5cab2b847fcd@omnitor.se> <8233c526-f66d-041e-e4eb-cad6c22b8a73@omnitor.se> <p06240623d6065b412f8c@[99.111.97.136]>
From: Gunnar Hellström <gunnar.hellstrom@omnitor.se>
Message-ID: <127db3d4-910b-f8f9-2c34-9c9d2f928d35@omnitor.se>
Date: Fri, 13 Oct 2017 14:21:38 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <p06240623d6065b412f8c@[99.111.97.136]>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/slim/jlo7Ukkslg2qdp_Hku4hFjfwCFw>
Subject: Re: [Slim] How to know modality in draft-ietf-slim-negotiating-human-language
X-BeenThere: slim@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Selection of Language for Internet Media <slim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/slim>, <mailto:slim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/slim/>
List-Post: <mailto:slim@ietf.org>
List-Help: <mailto:slim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/slim>, <mailto:slim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Oct 2017 12:21:46 -0000
Den 2017-10-13 kl. 14:01, skrev Randall Gellens: > At 12:46 AM +0200 7/30/17, Gunnar Hellström wrote: > >> The review comment on this topic was from Dale Worley and is found >> in section B of: >> >> >> <https://www.ietf.org/mail-archive/web/slim/current/msg00766.html>https://www.ietf.org/mail-archive/web/slim/current/msg00766.html >> >> >> by the sentence about specifying a view of the speaker in video: " >> >> I think this mechanism needs to be described more exactly, and in >> particular, it should not depend on the UA understanding which >> language tags are spoken language tags." >> >> It is this part we have not handled: " it should not depend on the >> UA understanding which language tags are spoken language tags" >> That is a general issue, not really linked to the issue of the view >> of a speaker in the video stream. > > Dale's suggestion of clarifying that it is the use of the exact same > language tag in both the audio and video stream, rather than just a > spoken tag on the video stream, is a good one. I'll add that. <GH>We already have that as a valid combination. But you may if you want add that it is the way to know that video is used for a view of a talking person. > >> >> >> Den 2017-07-28 kl. 14:12, skrev Gunnar Hellström: >> >>> I remember a comment in one of the reviews (maybe from Adam ?) >>> mentioning that it would be good if there was a simple way to decide >>> if a language tag is a sign language or a written or spoken language. >>> We have not responded to that comment. >>> >>> I know one application scanning the IANA language registry at >>> startup for that purpose and scanning for the word "sign" in the tag >>> description. But that might be seen as an inappropriate way to use >>> IANA registers if it get used by every phone in the future. >>> >>> What can we say about this review comment? Do we need to add a >>> modality indication parameter in the syntax? Or shall we strictly >>> limit audio to have spoken languages, video to have signed languages >>> and text and webrtc data channels to have written languages? Or >>> shall we leave this problem to implementation? >>> >>> /Gunnar >>> >> >> -- >> ----------------------------------------- >> Gunnar Hellström >> Omnitor >> <mailto:gunnar.hellstrom@omnitor.se>gunnar.hellstrom@omnitor.se >> +46 708 204 288 >> >> _______________________________________________ >> SLIM mailing list >> SLIM@ietf.org >> https://www.ietf.org/mailman/listinfo/slim > > -- ----------------------------------------- Gunnar Hellström Omnitor gunnar.hellstrom@omnitor.se +46 708 204 288
- [Slim] How to know modality in draft-ietf-slim-ne… Gunnar Hellström
- Re: [Slim] How to know modality in draft-ietf-sli… Gunnar Hellström
- Re: [Slim] How to know modality in draft-ietf-sli… Randall Gellens
- Re: [Slim] How to know modality in draft-ietf-sli… Randall Gellens
- Re: [Slim] How to know modality in draft-ietf-sli… Gunnar Hellström