From: Markus Elfring Date: Fri, 28 Feb 2020 14:05:42 +0000 Subject: Re: [v2 0/1] Documentation: bootconfig: Documentation updates Message-Id: <0d7d201c-e313-6129-7cfa-4e61eb31342d@web.de> List-Id: References: <158287861133.18632.12035327305997207220.stgit@devnote2> <957cef56-04b0-3889-6c95-a8ed7606b68d@web.de> <20200228222311.f5b9448027031b16a3be372a@kernel.org> In-Reply-To: <20200228222311.f5b9448027031b16a3be372a@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: Masami Hiramatsu , linux-doc@vger.kernel.org Cc: Jonathan Corbet , Steven Rostedt , Randy Dunlap , linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org > Didn't you read the article I shared? I read also the article “Don’t Use ISO/IEC 14977 Extended Backus-Naur Form (EBNF)” by David A. Wheeler. Some possibilities were pointed out as desirable improvements. > I actually wrote up the EBNF (ISO/IEC 14977) that was a good pazzle, > but just a toy. I hope that this contribution can help to become more productive in the discussed application domain. https://lkml.org/lkml/2020/2/27/72 https://lore.kernel.org/patchwork/patch/1200987/ https://lore.kernel.org/linux-doc/158278836196.14966.3881489301852781521.stgit@devnote2/ > I found no one use it to define their data format, according to the article, > including ISO itself (lol!) and there are many local extension, > including W3C EBNF, and those say "I'm EBNF". I suggest to reconsider the current situation. > Well, to say the least, I feel it is quite confused. Such a view is reasonable. > So, if you are interested in it, I don't stop you to write it up. Will the collaboration continue anyhow? > I just keep away from it. This is a pity. Will the clarification become more constructive for remaining challenges? Regards, Markus