Re: [Slim] I-D Action: draft-ietf-slim-negotiating-human-language-07.txt

Gunnar Hellström <gunnar.hellstrom@omnitor.se> Wed, 01 March 2017 16:05 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 920271295BC for <slim@ietfa.amsl.com>; Wed, 1 Mar 2017 08:05:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=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 7hanTAcJSAsT for <slim@ietfa.amsl.com>; Wed, 1 Mar 2017 08:05:29 -0800 (PST)
Received: from bin-vsp-out-02.atm.binero.net (bin-mail-out-06.binero.net [195.74.38.229]) (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 59DCF1294ED for <slim@ietf.org>; Wed, 1 Mar 2017 08:05:29 -0800 (PST)
X-Halon-ID: e0362c64-fe98-11e6-af93-005056917f90
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [77.53.231.21]) by bin-vsp-out-02.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Wed, 1 Mar 2017 17:05:22 +0100 (CET)
To: Brian Rosen <br@brianrosen.net>
References: <148782279664.31054.8793649134696520241.idtracker@ietfa.amsl.com> <p0624060cd4d4111cd79a@[99.111.97.136]> <49fd730e-6e90-1a49-eae8-80f8b1285a76@omnitor.se> <p06240604d4d6169921b5@[99.111.97.136]> <83152ba7-c3fb-25d8-f97d-59c7840cad56@omnitor.se> <p06240601d4d790fb8bb3@[99.111.97.136]> <4b36f347-955e-e2b9-12f2-f426d47d3d33@omnitor.se> <p06240608d4d927eaec67@[99.111.97.136]> <7f844aaa-17ce-2ab7-0602-a999a40235de@omnitor.se> <p06240600d4d9f6705416@[99.111.97.136]> <825fa638-b223-d716-6a3c-238903a37b92@omnitor.se> <p06240609d4dbcec4bcbf@[99.111.97.136]> <dba331e9-1075-5091-4f62-88a136049ab5@omnitor.se> <3710F834-0FB4-4D17-8E91-043624EF73E8@brianrosen.net>
From: Gunnar Hellström <gunnar.hellstrom@omnitor.se>
Message-ID: <f67ad4a2-35c1-5079-609e-98de19e6ff08@omnitor.se>
Date: Wed, 01 Mar 2017 17:05:20 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <3710F834-0FB4-4D17-8E91-043624EF73E8@brianrosen.net>
Content-Type: multipart/alternative; boundary="------------DADA6B61A8A7766607F3E1BC"
Archived-At: <https://mailarchive.ietf.org/arch/msg/slim/OCQBlQcysL4P-mRmSBxzAuPpg4c>
Cc: slim@ietf.org, Bernard Aboba <bernard.aboba@gmail.com>, Randall Gellens <rg+ietf@randy.pensive.org>, Natasha Rooney <nrooney@gsma.com>, "Phillips, Addison" <addison@lab126.com>
Subject: Re: [Slim] I-D Action: draft-ietf-slim-negotiating-human-language-07.txt
X-BeenThere: slim@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 01 Mar 2017 16:05:32 -0000

Den 2017-03-01 kl. 14:34, skrev Brian Rosen:

> I haven’t commented on this thread much, but I agree with Randall.
>
> I am opposed to a protocol document saying anything about human 
> interface.  The answering device may be an automaton, and there could 
> be very good reasons to not tell the human which languages/media are 
> not the least preferred.
Yes, we discussed this before and limited us to expressions like the one 
in chapter 1. " Both sides
    should be aware of which language was negotiated. "

That is as much as we need to say. The need is equal for the languages, 
the modalities and the preferences.
If the answering instance has registered capability in spoken English, 
French or Greek, and only Greek matches what the caller has indicated, 
the answering instance need to become aware of that so that the call can 
be started in the proper way in spoken Greek.
Also if the caller indicates a preference for receiving written English, 
or at lower preference spoken English, and the answering instance is 
capable of both, the answering instance need to become aware of the 
preferenceso that the call can be started in the way that results in the 
most successful start in written English.

My minimal wording proposal in issue 12 was:

"The asterisk should be attached to attributes with languages of lower
   preference to be matched if such difference can be specified. Thereby
   the location of the asterisk can be used to support the decision on
   which languages to use in the call."

This is not user interface specification, and likely as far as we should 
go in order to not specify user interface more for this preference 
indication than we do for the other language and preference indicators.

I wonder what Randall had in mind by the recent question about what my 
words meant.

Regards
Gunnar

>
> Designing good user interfaces is very hard, the participants on this 
> list are not experts, and we should not offer advice on human factors 
> in our documents.  It is sufficient to transport the information 
> across the wire.
>
> Brian
>
>> On Mar 1, 2017, at 2:26 AM, Gunnar Hellström 
>> <gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>> wrote:
>>
>> Hi Randall,
>> Den 2017-03-01 kl. 02:08, skrev Randall Gellens:
>>> Hi Gunnar,
>>>
>>> I'm starting a new message to cut out the huge amount of quoting.
>>>
>>> Your proposal is that text be added that advises the calling client 
>>> to place an asterisk on the least-preferred language/media, and 
>>> advises the answering client to indicate to the answering human 
>>> which language/media is not the least preferred (did not have an 
>>> asterisk in the offer), is that accurate?
>> Yes, with slight rewording to:
>> "text that advises the *offering* client to place an asterisk on the 
>> least-preferred language/media *indications*, and advises the 
>> answering client to indicate to the answering human which 
>> language/media are not the least preferred (did not have an asterisk 
>> in the offer)"
>>
>> The inclusion of the "indications" is just to assure that it is clear 
>> that it does not need to be just one indication that gets the asterisk .
>> The last part sounds awkward, but matches technically what the lack 
>> of an asterisk means. I inherited the inverted logic for the asterisk 
>> from its already defined non-denial meaning.
>> If you are considering wording for the draft, I suggest that you 
>> straighten the logic to say "*which language/media are most preferred 
>> (did not have an asterisk in the offer)*"
>>
>> It does also not need to be an "answering human" that gets this 
>> indication and makes use of it for guidance on how to answer the 
>> call. It can just as well be e.g. a multi-modal answering machine or 
>> some other application interacting with human language. I am not sure 
>> if "*answering party*" is more appropriate and can be considered 
>> including such automata.
>>
>> Thanks,
>> Gunnar
>>
>>
>> _______________________________________________
>> SLIM mailing list
>> SLIM@ietf.org <mailto:SLIM@ietf.org>
>> https://www.ietf.org/mailman/listinfo/slim
>
>
>
> _______________________________________________
> 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