Re: (off topic?) Docbook? Re: manlint?

[Marc Chantreux]

hello,

> XML is verbose, cumbersome to read and write, and has two different ways to
> express data structures

> <doc title="My stupid document" enabled="true"></doc>
> <doc>
>     <title>My stupid document</title>
>     <enabled>true</enabled>
>     <enabled />
> </doc>

this *isn't* the same to me: attributes are for metadata and tag
contents are for data. but the thing is: because xml is so painful
to edit, people (including me) started to abuse metadata.

pug (pugjs.org/) restored the balance in my xml galaxy:

    doc
        title My stupid document
        enabled/

seems ok to me.

> Conversely, JSON is more concise and predictable

json is more relevant than xml to store datastructures, right, but
i just said anything positive i can tell about JSON ...

> { "title": "My stupid document", "enabled": true }

how about the example that follows ?
regards
marc

<doc>
    <title>My stupid document</title>
    <enabled>true</enabled>
    <abstract>
    this is about trying to explain that <format id="json"/>
    is way inferior to
    <enum of="file-formats">
        <format>roff</format>
        <format>tex</format>
        <format>tex</format>
    </enum>
    in some situations. but when i want to store data, my first
    attempt  will be cbor to exchange and tsv to edit (or using ascii
    separators from 0x1c to 0x1f). another solution i like is the
    one i saw from time to time but don't know if it ever has a name.
    here is an example:
<snippet>
%T My stupid document
%E not sure anymore ...
</snippet>
    </abstract>
</doc>