Academic paper citing TypeID specification. feedback welcome

[rrrodzilla]

Hi,
I recently published a paper on arXiv proposing a URI scheme for decentralized agent identity in multi-agent systems: https://arxiv.org/abs/2601.14567

TypeID is a core component of the design. The scheme uses TypeID as the agent identifier, exploiting three of its properties:

1.	Unique identification via the UUIDv7 suffix
2.	Semantic classification via structured prefixes (e.g., llm_chat_, rule_fsm_, composite_pipeline_)
3.	Temporal ordering via the embedded timestamp for sorting agents by creation time

The URI structure follows the pattern:

agent://trust-root/capability-path/agent-typeid

For example:

agent://anthropic.com/assistant/chat/llm_chat_01h455vb4pex5vsknk084sn02q agent://acme.corp/workflow/approval/rule_fsm_01h5fskfsk4fpeqwnsyz5hj55t

The ABNF grammar in the paper references the TypeID v0.3.0 specification.

For context, I maintain mti, a Rust implementation of TypeID, so I’ve spent time with the spec details; the three-capability framing in the paper came directly from that implementation work.

I wanted to share this in case it’s of interest, and I’d welcome any feedback on whether the design aligns well with TypeID’s intended use or if there are considerations I may have missed.

Thanks for building TypeID—the combination of semantic prefixes with sortable UUIDs turned out to be exactly what was needed for this problem space.