Re: [Slim] Moving forward on draft-ietf-slim-negotiating-human-language

Brian Rosen <br@brianrosen.net> Mon, 20 November 2017 19:20 UTC

Return-Path: <br@brianrosen.net>
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 6368612EA42 for <slim@ietfa.amsl.com>; Mon, 20 Nov 2017 11:20:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20150623.gappssmtp.com
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 Kv7wI8MESiuV for <slim@ietfa.amsl.com>; Mon, 20 Nov 2017 11:20:03 -0800 (PST)
Received: from mail-yb0-x235.google.com (mail-yb0-x235.google.com [IPv6:2607:f8b0:4002:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 921CE12E957 for <slim@ietf.org>; Mon, 20 Nov 2017 11:20:03 -0800 (PST)
Received: by mail-yb0-x235.google.com with SMTP id d59so3461393ybi.7 for <slim@ietf.org>; Mon, 20 Nov 2017 11:20:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=o3o+gOgoEAeUOF17ZVqda2itFFCN7YcnQlhNlniWMwg=; b=Nt6Mm4jAj1fBrV0HvfMQuEkqX00L3RS4ZcMn/6c2rAUcpdaoEyf6x1OYWm5Wkb2zbe CBdfLEyB5GHb/6t+ytIA5Js2xmWLvfF9bjUdnzPpZznUgX2h1IdKIQsfDauf7KEXxy9t LErrwF0We5gpbdw6JqkTZdQw4VHGBTlzdFHV/wIXumsNvHL3VQyb5/ZJXaDgdn0ZSwe0 urtNhALI6s1CagScODQIpYUNfDbEYo6Ry3KMxVzJcucbmVtEQNycI3vdP2uHOmLM+n25 25MqO9q38u51cHaio0ANMPvt0sXXso9fhZYemjiribqQUipMpYkV9CBSmhpo3TmqpCmH gcIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=o3o+gOgoEAeUOF17ZVqda2itFFCN7YcnQlhNlniWMwg=; b=fJ5d64J0iAaaxK/nHsJ6ORu5sH0FTnA4mrip73CEoe/m1M6pzIskIK4orsNbpLznrf GSeX79tjJ6COF8hFEii0z46B5kdhJ3BWn9ffviaQGmFrHFmgcXP2QgeE9w43tg4chmUo rErAnss2KPfHMXu95vg6wWmjMrbNicHbGveyOOCS7I33p+g9TJeDOdrzKj5g22vPfyjK MnHKaBy8g0PxsrsF5VJ9ZfeHhZnALPWYw8bGfwOx1QFWc92wRHW07ZWeocen4CXRB4Xr pu9czo/7Wu4R5FeODMfmxo8/ZRDi6Ci9AKsD8rXMvJIDJ0nNy6vChPPfinavyhvm1aTC POuQ==
X-Gm-Message-State: AJaThX70B5uGG6CpDQ4zzxjcNYnq0wVCJNOgiKDXs7gwm6JuhMZsVknk ICaW01brAJ/Wgne+1pxAjbotXg==
X-Google-Smtp-Source: AGs4zMbyReGCXxwN/sqrsnidMRlk8DFBeAKpyjB68MmRv+4rVAq98soyQMd1m1txAVMXMMBk5ri33w==
X-Received: by 10.37.139.133 with SMTP id j5mr9277673ybl.4.1511205602624; Mon, 20 Nov 2017 11:20:02 -0800 (PST)
Received: from [10.33.193.2] (neustar-sthide-nat1.neustar.biz. [156.154.81.54]) by smtp.gmail.com with ESMTPSA id n187sm4901076ywd.89.2017.11.20.11.20.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Nov 2017 11:20:01 -0800 (PST)
From: Brian Rosen <br@brianrosen.net>
Message-Id: <E83689D8-DF61-4A3A-A5B2-8B3C05AFFB1E@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FDF83877-1275-46EA-9ADF-B8DB41478AB8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Mon, 20 Nov 2017 14:19:59 -0500
In-Reply-To: <CAOW+2dtodRVOyGg_Q83TCPXwL3jBccA-hpBhYfrPCAUjSm5zkQ@mail.gmail.com>
Cc: Paul Kyzivat <paul.kyzivat@comcast.net>, slim@ietf.org
To: Bernard Aboba <bernard.aboba@gmail.com>
References: <CAOW+2dsZtuciPiKMfif=ZmUqBcUd9TyYtL5gPYDp7ZfLOHHDBA@mail.gmail.com> <p06240600d637c6f98ecc@99.111.97.136> <CAOW+2dv5NSiCbW=p1exvPV=PF8YCVdiz2gi-OCxmaUB-jGe22w@mail.gmail.com> <p06240600d6389cd2043f@99.111.97.136> <97d9a6b8-de3b-9f79-483b-18376fcf0ced@omnitor.se> <CAOW+2dtpRoeYkMJzX9vyNUojJDax4DQUU2F4PauBwt1sm-83Hg@mail.gmail.com> <6812d89a-ba10-0947-5320-07374b8c071d@comcast.net> <CAOW+2dtodRVOyGg_Q83TCPXwL3jBccA-hpBhYfrPCAUjSm5zkQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/slim/tgLrx7iCa2_6P3H2-8EGKFMG_ds>
Subject: Re: [Slim] Moving forward on 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: Mon, 20 Nov 2017 19:20:08 -0000

We’re not chartered to solve a problem like “what kind of information is in a video: lip motion, sign language, captions?”
I think when you signal a sign language in a language tag, we all know what to expect.  If you put anything else in a video stream, we don’t know what to expect, and this working group isn’t chartered to fix that.

So, say that, and only that: “Use of a language selection in a video stream could have several meanings, including the use of sign language and visible captions.  If a sign language is signaled in a video stream, it is interpreted as the indicated sign language will appear in the video .  This document does not define any other use for language tags in video media.”


> On Nov 20, 2017, at 2:10 PM, Bernard Aboba <bernard.aboba@gmail.com> wrote:
> 
> Paul said: 
> 
> "ISTM the real problem is with language tags in video media. These could indicate that the lip motions of people in the video reflect speakers of the tagged language. Or they could indicate written text in the specified language is embedded in the video. (Could be closed caption text or just signage.) Or (in the case of signed language tags) it could indicate use of sign language in the video.
> 
> But in the end, if this is declarative about what is being sent then it isn't clear whether it is important. If it is an indication of what is being requested, then it is more important."
> 
> [BA] Yes, that is the core of the problem.  As has been noted earlier, the modality isn't indicated explicitly. I'm not sure whether we have enough experience to know whether this represents an important deficit.  But we could indicate that the problem potentially exists and that further work might be needed.
> 
> On Mon, Nov 20, 2017 at 10:53 AM, Paul Kyzivat <paul.kyzivat@comcast.net <mailto:paul.kyzivat@comcast.net>> wrote:
> On 11/20/17 1:41 PM, Bernard Aboba wrote:
> 
> [BA]  This is where the ground gets less solid - we don't really have a general mechanism for distinguishing spoken and written modality among non-signed languages. Perhaps we should just say "language tags in audio media indicate spoken modality and language tags in text media indicate written modality".
> 
> ISTM the real problem is with language tags in video media. These could indicate that the lip motions of people in the video reflect speakers of the tagged language. Or they could indicate written text in the specified language is embedded in the video. (Could be closed caption text or just signage.) Or (in the case of signed language tags) it could indicate use of sign language in the video.
> 
> But in the end, if this is declarative about what is being sent then it isn't clear whether it is important. If it is an indication of what is being requested, then it is more important.
> 
>         Thanks,
>         Paul
> 
> 
> _______________________________________________
> SLIM mailing list
> SLIM@ietf.org <mailto:SLIM@ietf.org>
> https://www.ietf.org/mailman/listinfo/slim <https://www.ietf.org/mailman/listinfo/slim>
> 
> _______________________________________________
> SLIM mailing list
> SLIM@ietf.org
> https://www.ietf.org/mailman/listinfo/slim