Register format with IANA and IETF

[Saklad5]

I feel adoption would be greatly improved if JSON Feed was formally standardized. The easiest way to do this would be to draft an IETF RFC that describes the standard and makes the necessary registry entries.

[Saklad5]

I could write up a draft, if no one is interested.

[manton]

Thank you, I'd appreciate any help with this. I submitted a request last year and it was not accepted because it didn't have the backing of an official standards body. I also think we could follow a path of the Markdown spec, which while not an official recognized standard, does have an RFC just for the MIME type: https://www.rfc-editor.org/rfc/rfc7763

[Saklad5]

When they say you should go through an official standards body, they mean something like an RFC.

[Saklad5]

Take the current specification, make it use RFC 2119, and you'll be most of the way there.

Of note: for each requirement, you should clarify what happens if it isn't followed. For the sake of making implementation easier, what should happen is usually the feed being rejected as invalid.

This is worth a read, though it's still a draft: https://datatracker.ietf.org/doc/draft-iab-protocol-maintenance/

[kurtmckee]

I think #110 needs to be solved first -- cloning the repo is currently a violation of copyright law because there is no license, so no one is allowed to do anything. It's not possible to clone the repo, transform the docs into an RFC style, nor to send the transformed document to anyone.

[manton]

No one should have any concerns about cloning the repo or sharing the spec, and in fact a bunch of people have forked it. But yeah, this effort to formalize the license as public domain did get derailed. I'll officially round up approval from everyone and update it.

[kurtmckee]

Thanks Manton!!

[dylmye]

FYI The spec has now been licenced CC0 in 7fed762