Re: [Cellar] Matroska document titles

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Tue, 17 March 2020 00:19 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: cellar@ietfa.amsl.com
Delivered-To: cellar@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D831F3A1417 for <cellar@ietfa.amsl.com>; Mon, 16 Mar 2020 17:19:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 jQSTgtM6vI3m for <cellar@ietfa.amsl.com>; Mon, 16 Mar 2020 17:19:18 -0700 (PDT)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (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 704A63A1416 for <cellar@ietf.org>; Mon, 16 Mar 2020 17:19:12 -0700 (PDT)
Received: by mail-lf1-x130.google.com with SMTP id 5so8548202lfr.2 for <cellar@ietf.org>; Mon, 16 Mar 2020 17:19:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CoHaby3zwl8f8XLlUk/UlZEjvGM/4TndXYku/+hFatQ=; b=MNfCQHJ3n/fMJ3rIxdiNC5ddXcrRc5+lC1i2XCLftEAyaap3z2qm8FqI3VklACBb9X N3ucsH4etw6pQ8mDCUq2T4Zum+gE58Z3w+TF8WaUn+OOc4WvnV8hl3GZ5j0qDV5Mi8Zz /jn3ypNZCKL+F/f6nGgro8CGnOhJitWAqozlXK1ZwL6IJchvEFZD5pzNvM6Rpa6olPyv ZIWBsBkcbO4iK2o1HW/9R9F5ObIfbxEgHcPq9sbgwIgsBufnZL92j2xIdLuQcVMkuZx4 y3VoDcakXlkH0Rqfecc+j9k0idZiY6+LGzh+ElZbgVWT6YO8HhUzfJNXPBUW4F3PcIb1 W+uw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CoHaby3zwl8f8XLlUk/UlZEjvGM/4TndXYku/+hFatQ=; b=Qzrj3p1KhtG6b7yxqUeipWbY0TZWtbQi6f/1E8Cj9+iLgAYREHJxvTXLPgvdb2Hqf9 1oJhgEOcl3R3FHCALOEJYhI5h63hku3WWOdsKP7Iz6qQ8WUh+NYbgMEXNQcjTgWXQGbW bYTp3FuUDt9T8vhHYa1FQOyr6lsbdRfWEkFK5HOIOdunQxwz976CRXawGXLYuOZxGox0 yC4vvPfhufbzYTyqQrSzYg4Vo2I8l/DU2Dm0+veCoSoH/wbt4V2Ki2mxI7ivY2Fn75IV U4yJgR8x4fa9wWn+e6i9T48HyB/OGovW3HkzX7SiUkjUOoA98VqHocRNu28wbId5Z8cp WM9A==
X-Gm-Message-State: ANhLgQ3lcthB2vMabeiWCtMxu3oGJkbhcwaiUGwUGZn5tJSAvSaXq7c5 tCoclACDxBSgjXgRXwrUB4VPPiOz7+56uESpSuL5gYvkLcM=
X-Google-Smtp-Source: ADFU+vvtl97aoNPdyu6Ozwha6J63l3oyuU1sdDAbA3IleqIVNi9yxIH0IK7Fmw64EbT7WyF5xO7LSZPulzCQ3czkrLM=
X-Received: by 2002:ac2:5f58:: with SMTP id 24mr87042lfz.81.1584404350104; Mon, 16 Mar 2020 17:19:10 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-cNS38Vn6KvRM6SKfc8Bqu5J+PpS9z78kKK=rzq1H+fug@mail.gmail.com> <CAOXsMFL+yHgWBK4AK5E1pzZLovLgMHvXxioTCODAS-QE5r6zww@mail.gmail.com> <CAKKJt-f_fYiRSsOZR95B3_m_qWr4P1PXf-nqBkGbijOAwfSTxA@mail.gmail.com> <D2F39CE7-F9A3-4962-B8F4-AE7E42A4B54F@dericed.com>
In-Reply-To: <D2F39CE7-F9A3-4962-B8F4-AE7E42A4B54F@dericed.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 16 Mar 2020 19:18:43 -0500
Message-ID: <CAKKJt-eZQd65kEhF0fnRLk29Kb1TESmwwi_ob1+pke-3j4kNZQ@mail.gmail.com>
To: Dave Rice <dave@dericed.com>
Cc: Steve Lhomme <slhomme@matroska.org>, Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000077f90905a101e2b8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/qFNPooRjPtpX3e_Lal_iqIiOOyM>
Subject: Re: [Cellar] Matroska document titles
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <cellar.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cellar>, <mailto:cellar-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cellar/>
List-Post: <mailto:cellar@ietf.org>
List-Help: <mailto:cellar-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cellar>, <mailto:cellar-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Mar 2020 00:19:20 -0000

Hi, Dave,

On Mon, Mar 16, 2020 at 6:00 PM Dave Rice <dave@dericed.com> wrote:

>
>
> On Mar 9, 2020, at 9:01 PM, Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
>
> Hi, Steve,
>
> Thanks very much for following up on this.
>
> For the purpose of this note, please consider that I'm not replying as one
> of the co-chairs.
>
> [deleted down to]

> And I really want to defer to the working group about the actual titles,
> so please do the right thing.
>
> So, here's what I've seen people do with multi-document specifications at
> the IETF.
>
>    - People use common title prefixes in Internet Drafts and RFCs to make
>    it easier to find stuff that is part of the specification, and to not find
>    things that aren't. If something like "Matroska Media Container" as a
>    prefix would apply to any of the specifications you're working on now or
>    thinking about in the future, that would be helpful to your readers. I
>    assumed that form in the following suggestions, so if you can think of a
>    better prefix, please use it to improve the following suggestions!
>    - For "Matroska Tags", that's pretty close to what I'd hope for. If it
>    was "Matroska Media Container Tags", would that work?
>    - For "Matroska Codec" - the abstract says this is actually "Matroska
>    Codec Mappings", so that seems like the title needs to change a bit more.
>    If the document title was something like "Matroska Media Container Codec
>    Mappings", would that work?
>    - For "Matroska Specifications", that probably is too broad (because
>    there are two other Matroska specifications in the working group now). You
>    used the term "core" in your reply, and I know the working group has been
>    considering whether to publish chapters in a separate document, so it seems
>    possible that there will be at least one non-core specification at some
>    point. Would it be accurate to use something like "Matroska Media Container
>    Core Specification" for this one?
>
> I’m not sure about the word ‘Media’, how about:
> Matroska File Format Specification
> Matroska File Format Codec Mappings
> Matroska File Format Metadata Tags
>
> I think the term “File Format” is a bit more accessible than “Container”.
> Also I see that MXF uses similar wording at
> http://web.archive.org/web/20051210203751/http://www.smpte.org/smpte_store/standards/pdf/s377m.pdf
> .
>
> There are (many) other titles that would work for me, so please don't
> focus on the details.
>
> I still want to defer to the working group on the exact titles, but your
proposals capture the ideas I was trying to convey in my proposals (looks
like a document set, clearer what the relationship between the documents
is, and titles seem clear to me).

And thanks for the pointer to the MXF document. It may be useful to match
their terminology, given an opportunity to do so.

Do The Right Thing, of course :-)

Best,

Spencer