The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Michael Kjörling" <michael@kjorling.se>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] A question about ls(1)
Date: Tue, 30 Apr 2019 06:44:08 +0000	[thread overview]
Message-ID: <20190430064408.ry56lmufdgq7uaut@h-174-65.A328.priv.bahnhof.se> (raw)
In-Reply-To: <CAFNqd5UPm_U22wYda5HjVQRQiM_85fq5JLR+24Y0NteipQ99Og@mail.gmail.com>

On 29 Apr 2019 16:44 -0400, from cbbrowne@gmail.com (Christopher Browne):
> He also contended that the world might be a better place if LibreOffice
> documents were captured as SQLite databases rather than being bundles of
> XML stored in a .zip archive.  That's a nice lively argument to have.
> Actually poke at the slides at PGCon 2014; he makes similar arguments
> about git repos (what if metadata were in a database?) and ePub book
> files.

At least OpenDocument is an ISO standard; and while it looks at a
glance like the Zip file format and compression themselves aren't
specified in it (at eight pages, there isn't a lot of room for
detailed technical descriptions), ISO/IEC 21320-1:2015 "normatively
references the Zip File Format Specification version 6.3.3 of PKWARE®
Inc", stating that "[d]ocument container files are conforming Zip
files as specified by that document". (Quoted from the summary page.)

https://www.iso.org/standard/60101.html

https://standards.iso.org/ittf/PubliclyAvailableStandards/c060101_ISO_IEC_21320-1_2015.zip

I could be wrong, but I don't _think_ that SQLite has reached quite
that level of adoption.

Also, relational databases have their advantages (I work with them
myself), but lots of office-type documents (word processing documents,
spreadsheets, presentations, etc.) inherently have a somewhat
hierarchical or run-on data structure, lending themselves well to a
hierarchical format. Whether we like it or not, XML also has the
advantage of being a well-established standard for data serialization,
and _with a schema_, can be readily validated.

And if you don't like the outer Zip file container, at least
OpenDocument also allows for single flat XML files. (Typical file name
extension .fo[dt][gpst], as opposed to .o[dt][gpst] for the Zip
container counterpart.) I'm pretty sure LibreOffice can be set up to
save as such files even by default, if that's your cup of tea. Those
get awfully big the moment you start including any non-trivial
content, though.

-- 
Michael Kjörling • https://michael.kjorling.se • michael@kjorling.se
  “The most dangerous thought that you can have as a creative person
              is to think you know what you’re doing.” (Bret Victor)

  reply	other threads:[~2019-04-30  6:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-28 16:54 Norman Wilson
2019-04-28 19:45 ` Jon Forrest
2019-04-28 20:00   ` Bakul Shah
2019-04-29 18:05     ` Michael Kjörling
2019-04-29 20:37       ` Warner Losh
2019-04-29 20:44       ` Christopher Browne
2019-04-30  6:44         ` Michael Kjörling [this message]
2019-04-30  7:24           ` Kurt H Maier
2019-04-30 10:35             ` Wesley Parish
2019-04-29 22:32       ` Bakul Shah
2019-04-30 11:52         ` Theodore Ts'o
2019-04-28 22:16   ` Thoma Paulsen
2019-04-29  0:53     ` John P. Linderman
  -- strict thread matches above, loose matches on Subject: below --
2019-04-27 23:03 Noel Chiappa
2019-04-27 20:11 Norman Wilson
2019-04-27 14:16 Anthony Martin
2019-04-27 15:38 ` Warner Losh
2019-04-27 15:42   ` Larry McVoy
2019-04-28 23:59   ` Warner Losh
2019-04-28 11:47 ` Dan Cross
2019-04-28 12:00   ` arnold
2019-04-28 14:44   ` jcs
2019-04-28 16:15   ` Bakul Shah

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190430064408.ry56lmufdgq7uaut@h-174-65.A328.priv.bahnhof.se \
    --to=michael@kjorling.se \
    --cc=tuhs@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).