On 16.05.2025 17:22, Salz, Rich wrote:
An additional reason why I think that English sentences are better than ABNF or
any other formalism as the normative part of a standard track RFC: most people
understand what an English sentence means,
Can you imagine defining HTTP without ABNF? Or any
On 17. May 2025, at 03:50, Paul Kyzivat
wrote:
>
> So you are still saying that the RFCs that use ABNF normatively would have
> been better if they had not?
I have a little demonstration, not for ABNF but for the related data definition
language CDDL.
Section 6.2.2 of RFC 7071 in conjunction
On 5/16/25 6:59 PM, Marc Petit-Huguenin wrote:
On 5/16/25 7:33 AM, Paul Kyzivat wrote:
On 5/15/25 8:37 PM, Marc Petit-Huguenin wrote:
3) How would you deal with something like:
"Each message MUST conform to the syntax specified by ABNF
rule 'Message' defined in Appendix Z."
That
On 5/16/25 7:33 AM, Paul Kyzivat wrote:
> On 5/15/25 8:37 PM, Marc Petit-Huguenin wrote:
>
>>> 3) How would you deal with something like:
>>>
>>> "Each message MUST conform to the syntax specified by ABNF
>>> rule 'Message' defined in Appendix Z."
>>
>> That would be trying to make a nor
On 17-May-25 03:22, Salz, Rich wrote:
An additional reason why I think that English sentences are better than ABNF or
any other formalism as the normative part of a standard track RFC: most people
understand what an English sentence means,
Can you imagine defining HTTP without ABNF? Or any
> An additional reason why I think that English sentences are better than ABNF
> or any other formalism as the normative part of a standard track RFC: most
> people understand what an English sentence means,
Can you imagine defining HTTP without ABNF? Or any other text-based protocol
that the
On Fri, May 16, 2025 at 7:59 AM Paul Kyzivat wrote:
> On 5/16/25 8:45 AM, Marc Petit-Huguenin wrote:
>
> > An additional reason why I think that English sentences are better than
> ABNF or any other formalism as the normative part of a standard track RFC:
> most people understand what an English
On 5/16/25 8:45 AM, Marc Petit-Huguenin wrote:
An additional reason why I think that English sentences are better than ABNF or
any other formalism as the normative part of a standard track RFC: most people
understand what an English sentence means,
Most people *in the world* don't understan
On 5/15/25 8:37 PM, Marc Petit-Huguenin wrote:
3) How would you deal with something like:
"Each message MUST conform to the syntax specified by ABNF
rule 'Message' defined in Appendix Z."
That would be trying to make a normative paragraph referencing an informative
section (because
>> I don’t know why this means it can’t be normative — it just describes a
>> superset, and the remaining details can then be supplied in English (rule
>> “verbatim” in 7.1, I think).
>
> Yes, but also the quoted-string, hexadecimal, and base-64 rules, when they
> start with a number.
There i
On 5/15/25 9:39 PM, Carsten Bormann wrote:
> On 14. May 2025, at 17:41, Marc Petit-Huguenin
> wrote:
>>
>> https://datatracker.ietf.org/doc/draft-rivest-sexp/ is a good example of a
>> language whose ABNF cannot be normative (that's because the s-exp variant
>> described in it is non-context fr
On Fri, May 16, 2025, at 15:52, Michael Richardson wrote:
> Additionally, I have yet to find an obvious way to display just a diagram
> itself. Both so that I can zoom better, but also so that I can extract the
> diagram for a slide, etc. I usually wind up diving into the XML or HTML and
> yankin
On 16. May 2025, at 07:52, Michael Richardson wrote:
>
> Additionally, I have yet to find an obvious way to display just a diagram
> itself. Both so that I can zoom better, but also so that I can extract the
> diagram for a slide, etc. I usually wind up diving into the XML or HTML and
> yanking
StJohns, Michael wrote:
> AFAICT, the scaling of the SVG is based on the rendered width of the page.
> And that appears fixed even when you yank your browser wide. Acrobat
I've also been frustrated by this.
Additionally, I have yet to find an obvious way to display just a diagram
itself
14 matches
Mail list logo