kdl
kdl copied to clipboard
kdl-org
the kdl document language specifications
As I read the grammar in the spec, `"//"` wouldn't parse as a single-line-comment as it requires as least one non-newline character after the slashes.
Currently, idents [disallow](https://github.com/kdl-org/kdl/blob/main/SPEC.md#non-identifier-characters) a few characters from being expressed literally, requiring they be escaped if authors want to include them: * codepoints < 0x20 (control characters) * codepoints > 0x10FFFF...
I'm wondering, what is the expected _input_ for any of the internationalized email/hostname/url types? I'm busy building the [type annotation parsing for kdl-rb](https://github.com/danini-the-panini/kdl-rb/pull/6) and I'm not really sure how to...
I know I've already been doing some of this, by including maintainer/authors like @larsgw and @shieldo, but I know there's a lot of you who have been super active and...
Rather than banning `#` in idents altogether, as #204 does, this takes the same approach as our number-like handling, and just bans idents from looking like a raw string *in...
KDL Schema Specification includes `format` for string and number validation to control the "Intended data format" but KDL does not know the concept of data formats. What should a validator...
### Discussed in https://github.com/kdl-org/kdl/discussions/200 Originally posted by **garrisonhh** September 23, 2021 As far as I can tell from the spec, `r#####` is a perfectly valid identifier. At the moment, given...
Thanks for discussion (). In addition to further changes to the specification of KDL Data model, the document should be referenced from other documents in this repository.
KDL specification does not explicitly define a data model but only a syntax that implies some data model of KDL. As long as you parse from KDL syntax into some...
I don't believe `/` need to be escaped in strings. This may be considered a breaking change now that we've reached 1.0, so another solution might be to allow it...