Re: [Json] JSON files in old-time DOS 8.3 file system, proposed extension "JON".

Phillip Hallam-Baker <ietf@hallambaker.com> Sun, 21 May 2017 21:41 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DCD9128B37 for <json@ietfa.amsl.com>; Sun, 21 May 2017 14:41:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level:
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 IxylmWdlYK8h for <json@ietfa.amsl.com>; Sun, 21 May 2017 14:41:50 -0700 (PDT)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (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 096A412420B for <json@ietf.org>; Sun, 21 May 2017 14:41:50 -0700 (PDT)
Received: by mail-oi0-x231.google.com with SMTP id w10so141654723oif.0 for <json@ietf.org>; Sun, 21 May 2017 14:41:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=TD/qyVqfHNrt9LOie+9anAO5ed4LtHcGQ2yHG/phEI0=; b=eU4Pym68VP/lyICgtpuWhcBrxG1m8VDzifTRSfrOgvolCwkyqxb4t5f4ekyk6llBQH psBzpX/CGW/LjuarxYzoEcEy6EooyOLLQI9K6wZRlJUD9Zr40QumIdg0IjLIODIb4xeM C0ru1k3gGey2eWZ77hwZiA6riyZkWAbwEX9/+3EabdydTXuYLnyd6G7rhMrYroZL8B/E 15NlybO1RbfusDlh9L2kYdoEENRDVQv5lYdFqakQYAqam2CKgjcB+rb9myx7giEF+Rbj XqRGSg2w5yugldmy/y/FFB0+jNO6eCR+XXr5mD4Ia02JuaQuX0jWQi25LlZrJU25iRvI MHhA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=TD/qyVqfHNrt9LOie+9anAO5ed4LtHcGQ2yHG/phEI0=; b=Vi8m6bJNktXb/pw2LTvwpDFUJNDlAa2+A00+jt1nDlw2LdR64KadnWVnvhg0uCC/jt KFN1f0TT3s6r0I4vD1Eno6SSJUmxoLT/CW0lLjLnkqGDoqVoEjYfv6cARLw0TLo3TEJl CkReYcKxWG/2k1/7ZGg/L2dYgPYeLcKwZIQhJlFeQ8YzmEqJO6DmCrwN99sdBCMjuGFJ bHj7hMqpFg4CXffDeEDL6S5WjlgJDDjs3S/pVXMW/NMOSVORrjb05Klq+wFwMz/X0+p6 Kaa6Yiq0n6T/+kKZt/Yr7eAV0Ct/+y75Ix+XXzxOn1T4dwnRFaYkBf4jQujF1t0dLrbG +cvg==
X-Gm-Message-State: AODbwcDp6asDeQHReZ6bFY7Upr79y0LQvjxXzI8zOkpE+y3nEyBE+OhZ 7sxjW0NkXaUtrwKJaHFsGBtNErrSBg==
X-Received: by 10.202.212.205 with SMTP id l196mr10515676oig.4.1495402909313; Sun, 21 May 2017 14:41:49 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.17.34 with HTTP; Sun, 21 May 2017 14:41:48 -0700 (PDT)
In-Reply-To: <20669.80.212.78.253.1495399193.squirrel@epost.powertech.no>
References: <56979.80.212.78.253.1495263849.squirrel@epost.powertech.no> <CAD2gp_QJ=o2jGQuqhLK1+PdfOuBKd7b2_0voWqQ73ufefLEGVQ@mail.gmail.com> <CAMm+Lwio2Cin_iDExm1BiRyiOj8CxN1O5_GuQFGs8iMU12EiFg@mail.gmail.com> <20669.80.212.78.253.1495399193.squirrel@epost.powertech.no>
From: Phillip Hallam-Baker <ietf@hallambaker.com>
Date: Sun, 21 May 2017 17:41:48 -0400
X-Google-Sender-Auth: nBIJ8pNZieXmRFVqB3KrbQr93MY
Message-ID: <CAMm+LwgNbg_uA5CwXLid-dNVa0WCGkQbG5GukMZNfBjZG+B24A@mail.gmail.com>
To: bnossum@norwia.no
Cc: John Cowan <cowan@ccil.org>, JSON WG <json@ietf.org>
Content-Type: multipart/alternative; boundary="001a113d3c6a34b03505500f9f20"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/mtBIXPGN6x9NAfnkyRNSMNcY8aY>
Subject: Re: [Json] JSON files in old-time DOS 8.3 file system, proposed extension "JON".
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 May 2017 21:41:52 -0000

Back in the day I worked in the HEP community. One of the constraints on
writing code for many experiments was that it had to run on CERNVM which
was limited to eight letter variables due to the linker and compiler being
obsolete.

At the time pretty much every other FORTRAN compiler/linker could handle 32
character variables. The constraint was having real impact on code quality.

I think that this is one of those instances where the IETF as a standards
body should set a precedent and tell people to just fix their systems
rather than suggest fixes for something that would be better left to die.
8.3 letter filenames were made obsolete in Windows 95. The FAT filesystem
is incompatible with the vast majority of storage media made today.




On Sun, May 21, 2017 at 4:39 PM, <bnossum@norwia.no> wrote:

> Dear Mr. Hallam-Baker,
>
> Like it or not, many embedded devices have the perhaps unfortunate
> combination of a FAT file system and an Ethernet MAC. You may think that
> qualifies as "retro computing", I could not possibly comment.
>
> It is no problem for me to name a file "SOMETHNG.TXT" and let it in fact
> describe json objects. But because JSON is an open-standard file format I
> find it advantageous that it should have a distinct file extension, hence
> my proposal. ".JSN" is a good proposal, (fr prhps bvs rsns), the exact
> extension is a minor matter.
>
> Respectfully,
> Baard Nossum
>
>
> > ​If you are doing retro computing then you shouldn't be using JSON at
> > all.
> >
> > ​
> >
> > On Sun, May 21, 2017 at 11:43 AM, John Cowan <cowan@ccil.org> wrote:
> >
> >>
> >> On Sat, May 20, 2017 at 3:04 AM, <bnossum@norwia.no> wrote:
> >>
> >> I wonder if it would be worthwhile to specify the file extension ".JON"
> >>> for old FAT file systems?  I realize that this problem will eventually
> >>> go
> >>> away, but probably not for a good many years.
> >>>
> >>
> >> I think "JSN" would be better because more recognizable (cnsnnts r mr
> >> rcgnzbl thn vwels).  In OS/8, a good extension would be JN, to avoid
> >> collision with JS for JavaScript.
> >>
> >> --
> >> John Cowan          http://vrici.lojban.org/~cowan
> cowan@ccil.org
> >> It was dreary and wearisome.  Cold clammy winter still held sway in this
> >> forsaken country.  The only green was the scum of livid weed on the dark
> >> greasy surfaces of the sullen waters.  Dead grasses and rotting reeds
> >> loomed
> >> up in the mists like ragged shadows of long-forgotten summers.
> >>         --LOTR, "The Passage of the Marshes"
> >>
> >>
> >>
> >> _______________________________________________
> >> json mailing list
> >> json@ietf.org
> >> https://www.ietf.org/mailman/listinfo/json
> >>
> >>
> >
>
>
> Best regards,
> Baard Nossum, +47 92409073
>
>
>