public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Pandoc JSON schema
Date: Wed, 25 Oct 2017 09:47:35 +0200	[thread overview]
Message-ID: <877evjd5yg.fsf@zeitkraut.de> (raw)
In-Reply-To: <20171024165310.GA94787@protagoras> (John MACFARLANE's message of "Tue, 24 Oct 2017 09:53:10 -0700")

John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> writes:

> PS. I wonder if there is any way to autogenerate this from the
> FromJSON/ToJSON instances for pandoc types?  That would
> allow us to ensure that this is always in sync with changes.

Autogeneration is the reason why I didn't open a PR for this yet. I'm
planning to experiment with generics and alternative JSON
representations, this schema was merely created to get me started.

It was also suggested to me to use the [Concise Data Definition
Language] instead, which is currently in I-D status, *much* less
verbose, and actually readable. I may try to use generics to generate a
CDDL definition, which could then be translated into a JSON schema. That
is going to take me a while, though.

Long story short: I'll open a PR on jgm/pandoc-website for now, if
that's ok with you. I don't think it's ready for the other repos yet,
neither for pandoc nor pandoc-types.

[Concise Data Definition Language]: https://datatracker.ietf.org/doc/draft-ietf-cbor-cddl/


  reply	other threads:[~2017-10-25  7:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 11:16 Albert Krewinkel
     [not found] ` <87bmkwdcdr.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2017-10-24 16:47   ` John MACFARLANE
2017-10-24 16:53     ` John MACFARLANE
2017-10-25  7:47       ` Albert Krewinkel [this message]
     [not found]         ` <877evjd5yg.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-02 14:41           ` Harsh Donga
     [not found]             ` <8d53751b-a59c-43fb-a7e1-4f5079903e28n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-02 15:11               ` Albert Krewinkel
     [not found]                 ` <87pme55qyx.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-02 15:24                   ` Harsh Donga
     [not found]                     ` <81054dc7-a893-4f84-9ce4-ea90f997b12fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-02 15:58                       ` Albert Krewinkel
     [not found]                         ` <87leot5otd.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-12-06  1:04                           ` John MacFarlane
     [not found]                             ` <AC7F0C0B-122B-4BF6-BC02-81FC4BA4B37C-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-12-06 15:44                               ` Albert Krewinkel
     [not found]                                 ` <874ju8wn22.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-12-28  9:44                                   ` Harsh Donga
     [not found]                                     ` <4e6dd89d-1dd0-40bb-a760-e3468c5b2403n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-12-29 20:37                                       ` John MacFarlane
     [not found]                                         ` <CE12DC92-2BD1-429F-B266-EF9D3231A982-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-06-19  9:32                                           ` Jörn K

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=877evjd5yg.fsf@zeitkraut.de \
    --to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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).