Re: [91attendees] New draft offers suggestions/guidance for Jabber scribes...

Tom Pusateri <pusateri@bangj.com> Fri, 07 November 2014 20:27 UTC

Return-Path: <pusateri@bangj.com>
X-Original-To: 91attendees@ietfa.amsl.com
Delivered-To: 91attendees@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 417621A1ADD for <91attendees@ietfa.amsl.com>; Fri, 7 Nov 2014 12:27:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.862
X-Spam-Level:
X-Spam-Status: No, score=0.862 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 0-JlL8rW6hii for <91attendees@ietfa.amsl.com>; Fri, 7 Nov 2014 12:27:12 -0800 (PST)
Received: from oj.bangj.com (amt0.gin.ntt.net [129.250.11.170]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 971CD1A1AB4 for <91attendees@ietf.org>; Fri, 7 Nov 2014 12:27:12 -0800 (PST)
Received: from [172.16.10.140] (gw.mountain2sea.com [71.70.135.90]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id 0F9D6274F; Fri, 7 Nov 2014 15:25:02 -0500 (EST)
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
Content-Type: multipart/signed; boundary="Apple-Mail=_C7E2B63E-6E09-408C-BD01-FE489BC02E05"; protocol="application/pgp-signature"; micalg=pgp-sha1
X-Pgp-Agent: GPGMail 2.5b1
From: Tom Pusateri <pusateri@bangj.com>
In-Reply-To: <52756D3E-D2A9-4535-9F50-4E04DB1F4411@isoc.org>
Date: Fri, 7 Nov 2014 15:27:10 -0500
Message-Id: <4204ABC5-0EFC-44F6-8698-95E57D23554A@bangj.com>
References: <52756D3E-D2A9-4535-9F50-4E04DB1F4411@isoc.org>
To: Dan York <york@isoc.org>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/91attendees/F6qXCrsYkx2eU4DIU_GO-4TLj0U
Cc: "91attendees@ietf.org" <91attendees@ietf.org>
Subject: Re: [91attendees] New draft offers suggestions/guidance for Jabber scribes...
X-BeenThere: 91attendees@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list of IETF 91 attendees that have opted in on this list." <91attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/91attendees>, <mailto:91attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/91attendees/>
List-Post: <mailto:91attendees@ietf.org>
List-Help: <mailto:91attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/91attendees>, <mailto:91attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Nov 2014 20:27:14 -0000

> On Nov 7, 2014, at 11:13 AM, Dan York <york@isoc.org> wrote:
> 
> IETF 91 attendees,
> 
> If you are going to serve as a "Jabber scribe" in meetings next week at IETF 91 (or wind up being asked to do that), Peter St. Andre and I tried to capture some of the experiences we and others have had as Jabber scribes and advice we've received from others in a new draft:
> 
> https://tools.ietf.org/html/draft-saintandre-chatroom-relay-02 <https://tools.ietf.org/html/draft-saintandre-chatroom-relay-02>
> 
> Our hope is that this can be helpful to people who might get tasked with performing this role that is so VERY critical for remote attendees.
> 
> ...
> 
> Anyway... the draft is out there and we would welcome any feedback that people have.  If you are doing jabber scribing (or what we called "chatroom relay" to be product-neutral) next week at IETF 91 and come up with any additional tips or tricks, please do let us know.  The goal is to help provide suggestions that can make this role work smoother and easier and through that to help improve the experience for remote attendees.
> 
> Dan
> 

I have been searching for a way to synchronize the slides with the audio for a better playback experience after the session. A few releases ago, I started parsing the jabber logs and displaying them time synchronized with the audio playback. This is a good start but you still have to page through the slides manually. At least now, you get some hints as to when to advance if someone or Meetecho puts the slide number or title in the jabber chatroom.

But the format of the slide info varies from jabber session to session and the slide filename isn’t always apparent so it is difficult to automate this.

Adobe suggested a URL format to reference a file and page number here: http://helpx.adobe.com/acrobat/kb/link-html-pdf-page-acrobat.html <http://helpx.adobe.com/acrobat/kb/link-html-pdf-page-acrobat.html>
Example: <A HREF="http://www.example.com/myfile.pdf#page=4”>

This would make the jabber logs machine parseable if the format was consistently followed. But the Meetecho guys said they tried URLs in the jabber sessions and got complaints about the links from remote participants and so they stopped.

Maybe we need a machine parseable chatroom and one for human consumption.

And defining a format isn’t enough to track the actual slide changes. That still has to be done manually. But if we could get events from Powerpoint, Keynote, or Adobe Reader, maybe we could automate that too and have the presenter’s machine send the jabber messages as the slides change.

I’m willing to work on this but I need some help from people knowledgable about the hooks in these tools. Anyone from Adobe, Apple, & Microsoft want to help? Anyone else have some good ideas to make this better?

Thanks,
Tom