<insert XKCD comic about standards>
XFN has been around forever and uses link rel to define the relationship between two URLs, which typically represent humans.
The relationship semantics are orthogonal (I suppose) to the purpose of human.json, but since the current spec only defines a unidirectional relationship, it misses the chance to detect bi-directional claims, e.g. where two links point to each other with the 'friend' relationship.
"Vouch" is also exceedingly vague and subjective, lacking domain specificity.
For this effort to be truly useful, reusing existing/established conventions could help advance its utility and adoption, and insisting on clarity around the relationship semantic (i.e. I would propose using "knows" instead of "vouches") would reduce the likelihood of implied transitive assumptions (e.g. if I vouch for Rob, and Rob vouches for Mike, we shouldn't assume that I vouch for Mike, and that should be clarified in the spec).
Anyway — I like the idea of humans.txt (which already exists!) or humans.json, but what I like even more is widespread adoption and use of these protocols!
<insert [XKCD comic about standards](https://xkcd.com/927/)>
[XFN](https://gmpg.org/xfn/) has been around forever and uses `link rel` to define the relationship between two URLs, which typically represent humans.
The [relationship semantics](https://gmpg.org/xfn/11) are orthogonal (I suppose) to the purpose of `human.json`, but since the [current spec](https://codeberg.org/robida/human.json/src/branch/main/schema/0.1.1.json) only defines a unidirectional relationship, it misses the chance to detect bi-directional claims, e.g. where two links point to each other with the 'friend' relationship.
"Vouch" is also exceedingly vague and subjective, lacking domain specificity.
For this effort to be truly useful, [reusing](https://microformats.org/wiki/reuse) existing/established conventions could help advance its utility and adoption, and insisting on clarity around the relationship semantic (i.e. I would propose using "knows" instead of "vouches") would reduce the likelihood of implied transitive assumptions (e.g. if I _vouch_ for Rob, and Rob _vouches_ for Mike, we shouldn't assume that I _vouch_ for Mike, and that should be clarified in the spec).
Anyway — I like the idea of [humans.txt](https://humanstxt.org/) (which already exists!) or `humans.json`, but what I like even more is widespread adoption and use of these protocols!