Re: [Slim] Issue #27 on draft-ietf-slim-negotiating-human-language
Gunnar Hellström <gunnar.hellstrom@omnitor.se> Thu, 27 April 2017 15:20 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 BA294129AAD for <slim@ietfa.amsl.com>; Thu, 27 Apr 2017 08:20:20 -0700 (PDT)
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 xXQeziA9ipb8 for <slim@ietfa.amsl.com>; Thu, 27 Apr 2017 08:20:16 -0700 (PDT)
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 63DF0129AD2 for <slim@ietf.org>; Thu, 27 Apr 2017 08:19:25 -0700 (PDT)
X-Halon-ID: e3427082-2b5c-11e7-b152-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; Thu, 27 Apr 2017 17:19:19 +0200 (CEST)
To: Bernard Aboba <bernard.aboba@gmail.com>, slim@ietf.org
References: <CAOW+2dtU+sbM=7tYYr0m8t3D6eyKiKo_ShVhoAjaKOBuJYpdNw@mail.gmail.com>
From: Gunnar Hellström <gunnar.hellstrom@omnitor.se>
Message-ID: <2c2a6785-38e0-64df-753f-dd461108af08@omnitor.se>
Date: Thu, 27 Apr 2017 17:19:17 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAOW+2dtU+sbM=7tYYr0m8t3D6eyKiKo_ShVhoAjaKOBuJYpdNw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------874BE354808375F3C3623CD6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/slim/m4XekumyscPES6jPeZBtE3UEo8M>
Subject: Re: [Slim] Issue #27 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: Thu, 27 Apr 2017 15:20:21 -0000
The text in draft version -08 related to issue #27 has changed a lot since the version commented in LC. It is currently: "5.4. Undefined Combinations With the exception of the case mentioned in Section 5.2 (a spoken language tag for a video stream in parallel with an audio stream with the same spoken language tag), the behavior when specifying a spoken/ written language tag for a video media stream, or a signed language tag for an audio or text media stream, is not defined." The referenced part of section 5.2 says: " Note that while signed language tags are used with a video stream to indicate sign language, a spoken language tag for a video stream in parallel with an audio stream with the same spoken language tag indicates a request for a supplemental video stream to see the speaker." I think that is close to what we want. But we need to have decisions on if it is exactly what we want. Points for decision: 1. Can we use the term "a spoken/written language tag" in 5.4? Addison Phillips did not like our use of that term in another paragraph, now reworded. I suggest to replace it with "a language tag used for a spoken or written language" and hope that is easier to accept. However with my solution proposal for point 3 below, this problem disappears. 2. Are we satisfied with the solution that we cannot indicate use of text captions embedded in the video stream? It was long ago that I saw conversational products placing the text captions or text dialogue overlayed in the video stream. It is still in heavy use for streaming. So, if we do not believe that our specification will be used for streaming services, I think we are satisfied with the current limitation. We had a proposal to always use the -Zxxx script subtag when we mean spoken modality, and usually no script subtag (or a specific script subtag when motivated for the languag when we mean a written modality, but there were some reluctance to that use of the -Zxxx script subtag for this purpose. I suggest that we are happy with the current limitation, but want to hear others' views. 3. Are we satisfied with the limitation described in the section 5.2 citation, requiring a spoken language tag used for the video stream to mean a view of a speaking person only if an audio stream has the same language tag assigned. I think that limitation is not needed and complicates the use. Conclusion: With my proposed resolutions on these points, we should change the two paragraphs cited above to: "5.4. Undefined Combinations The behavior when specifying a language tag for a written language for a video media stream, or a signed language tag for an audio or text media stream, is not defined." The referenced part of section is then proposed to be: " Note that while signed language tags are used with a video stream to indicate sign language, a spoken language tag for a video stream indicates the view of a speaking person in the video stream." If other than my proposals on the points are decided, the wording needs to be adjusted accordingly. /Gunnar Den 2017-04-25 kl. 20:25, skrev Bernard Aboba: > Currently 10 Issues remain open from IETF Last Call: > https://trac.ietf.org/trac/slim/report/1 > > These include: > Ticket > <https://trac.ietf.org/trac/slim/report/1?sort=ticket&asc=1&page=1> > Summary > <https://trac.ietf.org/trac/slim/report/1?sort=summary&asc=1&page=1> > Component > <https://trac.ietf.org/trac/slim/report/1?sort=component&asc=1&page=1> > Version > <https://trac.ietf.org/trac/slim/report/1?sort=version&asc=1&page=1> > Milestone > <https://trac.ietf.org/trac/slim/report/1?sort=milestone&asc=1&page=1> > Type > <https://trac.ietf.org/trac/slim/report/1?sort=type&asc=1&page=1> > Owner > <https://trac.ietf.org/trac/slim/report/1?sort=owner&asc=1&page=1> > Status > <https://trac.ietf.org/trac/slim/report/1?sort=status&asc=1&page=1> > Created > <https://trac.ietf.org/trac/slim/report/1?sort=created&asc=1&page=1> > #27 <https://trac.ietf.org/trac/slim/ticket/27> The cases in the > "Silly states" section 5.4 are not all silly. > <https://trac.ietf.org/trac/slim/ticket/27> > negotiating-human-language 2.0 milestone1 > <https://trac.ietf.org/trac/slim/milestone/milestone1> defect > gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se> new > Mar 22, 2017 > #19 <https://trac.ietf.org/trac/slim/ticket/19> Use Media Type > registration template <https://trac.ietf.org/trac/slim/ticket/19> > multilangcontent > > enhancement rfc.nik.tomkinson@gmail.com > <mailto:rfc.nik.tomkinson@gmail.com> assigned Aug 17, 2016 > #28 <https://trac.ietf.org/trac/slim/ticket/28> Examples section 5.5 > requires expansion <https://trac.ietf.org/trac/slim/ticket/28> > negotiating-human-language 2.0 milestone1 > <https://trac.ietf.org/trac/slim/milestone/milestone1> defect > rg+ietf@randy.pensive.org <mailto:rg%2Bietf@randy.pensive.org> > assigned Mar 22, 2017 > #32 <https://trac.ietf.org/trac/slim/ticket/32> Audio/Video > Coordination <https://trac.ietf.org/trac/slim/ticket/32> > negotiating-human-language 2.0 milestone1 > <https://trac.ietf.org/trac/slim/milestone/milestone1> defect > rg+ietf@randy.pensive.org <mailto:rg%2Bietf@randy.pensive.org> new > Mar 22, 2017 > #34 <https://trac.ietf.org/trac/slim/ticket/34> Use the > Accept-Language syntax <https://trac.ietf.org/trac/slim/ticket/34> > negotiating-human-language 2.0 milestone1 > <https://trac.ietf.org/trac/slim/milestone/milestone1> defect > rg+ietf@randy.pensive.org <mailto:rg%2Bietf@randy.pensive.org> > assigned Mar 22, 2017 > #35 <https://trac.ietf.org/trac/slim/ticket/35> Have an attribute to > abbreviate the bidirectionally-symmetric case > <https://trac.ietf.org/trac/slim/ticket/35> > negotiating-human-language 2.0 milestone1 > <https://trac.ietf.org/trac/slim/milestone/milestone1> defect > rg+ietf@randy.pensive.org <mailto:rg%2Bietf@randy.pensive.org> > assigned Mar 22, 2017 > #38 <https://trac.ietf.org/trac/slim/ticket/38> Routing out of scope > <https://trac.ietf.org/trac/slim/ticket/38> > negotiating-human-language 1.0 milestone1 > <https://trac.ietf.org/trac/slim/milestone/milestone1> defect > draft-ietf-slim-negotiating-human-language@ietf.org > <mailto:draft-ietf-slim-negotiating-human-language@ietf.org> new Apr > 25, 2017 > #39 <https://trac.ietf.org/trac/slim/ticket/39> Syntax Collapse > <https://trac.ietf.org/trac/slim/ticket/39> > negotiating-human-language 1.0 milestone1 > <https://trac.ietf.org/trac/slim/milestone/milestone1> defect > draft-ietf-slim-negotiating-human-language@ietf.org > <mailto:draft-ietf-slim-negotiating-human-language@ietf.org> new Apr > 25, 2017 > #26 <https://trac.ietf.org/trac/slim/ticket/26> Make use of the > asterisk modifier on media level with session scope also for media > level purposes <https://trac.ietf.org/trac/slim/ticket/26> > negotiating-human-language 2.0 milestone1 > <https://trac.ietf.org/trac/slim/milestone/milestone1> enhancement > gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se> new > Mar 22, 2017 > #29 <https://trac.ietf.org/trac/slim/ticket/29> Include more fields > for attribute registration from 4566bis > <https://trac.ietf.org/trac/slim/ticket/29> > > > > _______________________________________________ > 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] Open Issues on draft-ietf-slim-negotiating… Bernard Aboba
- Re: [Slim] Open Issues on draft-ietf-slim-negotia… Gunnar Hellström
- Re: [Slim] Open Issues on draft-ietf-slim-negotia… Adam Roach
- Re: [Slim] Open Issues on draft-ietf-slim-negotia… Bernard Aboba
- Re: [Slim] Open Issues on draft-ietf-slim-negotia… Gunnar Hellström
- Re: [Slim] Issue #27 on draft-ietf-slim-negotiati… Gunnar Hellström
- Re: [Slim] Open Issue #35 on draft-ietf-slim-nego… Gunnar Hellström
- Re: [Slim] Open Issue #34 on draft-ietf-slim-nego… Gunnar Hellström
- Re: [Slim] Open Issue #32 on draft-ietf-slim-nego… Gunnar Hellström
- Re: [Slim] Open Issue #28 on draft-ietf-slim-nego… Gunnar Hellström
- Re: [Slim] Open Issue #26 on draft-ietf-slim-nego… Gunnar Hellström
- Re: [Slim] Open Issue #26 on draft-ietf-slim-nego… Gunnar Hellström
- Re: [Slim] Open Issues on draft-ietf-slim-negotia… Randall Gellens
- Re: [Slim] Open Issues on draft-ietf-slim-negotia… Gunnar Hellström
- Re: [Slim] Open Issues on draft-ietf-slim-negotia… Randall Gellens
- Re: [Slim] Open Issues on draft-ietf-slim-negotia… Natasha Rooney
- Re: [Slim] Open Issues on draft-ietf-slim-negotia… Randall Gellens
- Re: [Slim] Open Issues on draft-ietf-slim-negotia… Natasha Rooney
- Re: [Slim] Open Issues on draft-ietf-slim-negotia… Gunnar Hellström
- Re: [Slim] Open Issues on draft-ietf-slim-negotia… Randall Gellens
- Re: [Slim] Open Issues on draft-ietf-slim-negotia… Randall Gellens