cabo

> @cabo/@timbray what is the typical IETF approach to this sort of thing? Generally, the IETF is not in the business of providing or maintaining such resources. The IETF does...

I agree with using Accept: to specify the desired response format (we could even give application/json a specific meaning in this context); application/jsonpath is fine as a query content type.

> [@timbray](https://github.com/timbray) [@cabo](https://github.com/cabo) - I need help with getting the syntax correct. What tool should I use? Is https://jsonpath.com/ ok? FWIW, the sample data is https://www.rfc-editor.org/errata.json I use a simple...

> jpt seems to use the same parser as https://jsonpath.com/... > > I should have been more precise on what problems I encountered: > > Escaping "-" in names. The...

JSONPath does not specify an output format, just saying that this could be a list of normalized paths and/or the values at these paths. The reply at line 896 looks...

``` name-segment = ("[" name-selector "]") / ("." member-name-shorthand) member-name-shorthand = name-first *name-char name-selector = string-literal string-literal = %x22 *double-quoted %x22 / ; "string" %x27 *single-quoted %x27 ; 'string' ```...

Hi Björn, thank you very much! > The current version of `svgcheck` has a rather odd bug where it attempts to read from a "stdin" file in the current directory...

So how do you actually build cutycapt? I don't know what a .pro file is. Would it make sense to port the source from sourceforge to github?

Thanks! Two citations of the same reference, one of which is normative with the other one informative is not an error, the actual reference then simply is normative. Conflicting info...

Should be fixed by 4f64679 Message now looks like: ``` ** (normative reference RFC9595 is both inline and in YAML header) ```