[Slim] How to know modality in draft-ietf-slim-negotiating-human-language

Gunnar Hellström <gunnar.hellstrom@omnitor.se> Fri, 28 July 2017 12:12 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 C9FCB131C29 for <slim@ietfa.amsl.com>; Fri, 28 Jul 2017 05:12:59 -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 mRDGiYtUFv_o for <slim@ietfa.amsl.com>; Fri, 28 Jul 2017 05:12:56 -0700 (PDT)
Received: from bin-vsp-out-02.atm.binero.net (vsp-unauthed02.binero.net [195.74.38.227]) (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 41A85131FE4 for <slim@ietf.org>; Fri, 28 Jul 2017 05:12:48 -0700 (PDT)
X-Halon-ID: 0e72f6f5-738e-11e7-ba9c-005056917f90
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [172.20.7.164] (unknown [65.216.242.51]) by bin-vsp-out-02.atm.binero.net (Halon) with ESMTPSA id 0e72f6f5-738e-11e7-ba9c-005056917f90; Fri, 28 Jul 2017 14:12:43 +0200 (CEST)
To: "slim@ietf.org" <slim@ietf.org>
From: Gunnar Hellström <gunnar.hellstrom@omnitor.se>
Message-ID: <376ade2a-be29-33a6-b539-5cab2b847fcd@omnitor.se>
Date: Fri, 28 Jul 2017 14:12:42 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/slim/sId_afw1w6LjH9InzaU-w6V8c0Q>
Subject: [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, 28 Jul 2017 12:13:00 -0000

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
gunnar.hellstrom@omnitor.se