Pith Number
pith:YMHZZUIM
pith:2018:YMHZZUIMTXGLU5KCNRJUFZG4CH
not attested
not anchored
not stored
refs pending
How practical is it? Machine Learning for Identifying Conceptual Interoperability Constraints in API Documents
arxiv:1812.02096 v1 · 2018-12-05 · cs.SE
Add to your LaTeX paper
\usepackage{pith}
\pithnumber{YMHZZUIMTXGLU5KCNRJUFZG4CH}
Prints a linked badge after your title and injects PDF metadata. Compiles on arXiv. Learn more · Embed verified badge
Record completeness
1
Bitcoin timestamp
2
Internet Archive
3
Author claim
· sign in to
claim
4
Citations
5
Replications
✓
Portable graph bundle live · download bundle · merged
state
The bundle contains the canonical record plus signed events. A mirror can host it anywhere and recompute the same
current state with the deterministic merge algorithm.
Receipt and verification
| First computed | 2026-05-17T23:58:59.726730Z |
|---|---|
| Builder | pith-number-builder-2026-05-17-v1 |
| Signature | Pith Ed25519
(pith-v1-2026-05) · public key |
| Schema | pith-number/v1.0 |
Canonical hash
c30f9cd10c9dccba75426c5342e4dc11dcc25bad3cb6f8fbbf548c2f617ad9ec
Aliases
· · · · ·Agent API
Verify this Pith Number yourself
curl -sH 'Accept: application/ld+json' https://pith.science/pith/YMHZZUIMTXGLU5KCNRJUFZG4CH \
| jq -c '.canonical_record' \
| python3 -c "import sys,json,hashlib; b=json.dumps(json.loads(sys.stdin.read()), sort_keys=True, separators=(',',':'), ensure_ascii=False).encode(); print(hashlib.sha256(b).hexdigest())"
# expect: c30f9cd10c9dccba75426c5342e4dc11dcc25bad3cb6f8fbbf548c2f617ad9ec
Canonical record JSON
{
"metadata": {
"abstract_canon_sha256": "b8ee1dde227e3d3f7421fe87f38a2bc8b0432e73fe9593877c465f47760d4d1e",
"cross_cats_sorted": [],
"license": "http://arxiv.org/licenses/nonexclusive-distrib/1.0/",
"primary_cat": "cs.SE",
"submitted_at": "2018-12-05T16:38:42Z",
"title_canon_sha256": "7adf13dc1b75529f19d200abf673006b94e58d882bddfafea1ae466342f9f3ae"
},
"schema_version": "1.0",
"source": {
"id": "1812.02096",
"kind": "arxiv",
"version": 1
}
}