diff --git a/index.html b/index.html index 333859d..8c8e044 100644 --- a/index.html +++ b/index.html @@ -175,12 +175,21 @@ Github repo. Feel free to jump in and give us your 2 cents!

  • Ease of implementation
    • +
    +

    Compatibility with JSON and XML

    +

    There are two specifications for writing KDL that can be losslessly translated +between it and JSON or XML. These specifications define a stricter subset of +KDL that, even if not entirely idiomatic, is still valid and fits into the +data models of the other two languages:

    + +

    FAQ

    -

    How do you pronounce "KDL"?

    +

    How do you pronounce KDL?

    Same as "cuddle".

    -

    What is the expected file extension?

    -

    A file containing KDL should end with .kdl.

    Why yet another document language?

    Because nothing out there felt quite right. The closest one I found was SDLang, but that had some design choices I disagreed with.

    @@ -227,6 +236,9 @@ strict syntax, as well as its lack of support for comments.

    forgiving syntax without being so flexible as to allow certain classes of unfortunate mistakes. It also has much more flexibility around how to represent data.

    +

    If you need to interoperate with a service that consumes or emits JSON, or for +some other reason have need to write "JSON in KDL", we have JiK, an official +microsyntax for losslessly encoding JSON.

    What about TOML?

    It nests very poorly. It doesn't fare well with large files.

    What about XML?

    @@ -248,6 +260,9 @@ also less verbose when exchanging documents across APIs!

    "marking up" a text document with special tags, although KDL can still be useful for templating engines that want to be more strict about text fragments.

    +

    If you need to interoperate with a service that consumes or emits XML, or for +some other reason have need to write "XML in KDL", we have XiK, an official +microsyntax for losslessly encoding XML.