The Epiarc is a Web consensus system for discovering how we name things.
It is made of:
The Epiarc is built on the Web, which makes it:
Private Epiarcs may emerge in private networks with no Internet access.
The Archetypal Resource Identifier (ARI) is the principal identifier of a resource or link on the Epiarc. It is the most common natural name for something — with some extra features.
The ARI is usually expressed as a link, pointing to a URI, for example.
The ARI may be hierarchical, so that producers can organise their links underneath another link. This is supported by concatenating a parent ARI and a child ARI with the forward slash character: “Parent ARI / Child ARI”.
The ARI is:
A good ARI is also memorable, obvious, and concise — but not so compressed that it invents a new naming scheme.
The ARI does not need a formal structure when spoken aloud. Computers can serialize an ARI in many formats.
The ARI is a more natural and capable name format than its predecessors like URIs, domain names, or hashtags.
The linkbase is the principal repository of ARIs on the Epiarc. It is simply a data structure, or a representation of one, that contains one or more ARIs.
The personal linkbase is the user’s own linkbase. It is the most local and contextual linkbase, as it is formed and developed by the user.
An Epiarc User Agent can subscribe to shared linkbases. The user may assign a name to a linkbase when they subscribe to it. The linkbase name can be used as the parent ARI for child ARIs inside it.
“genbank” (NCBI Genbank linkbase):
“wiki” (Wikipedia linkbase):
When a User Agent subscribes to shared linkbases, the entries in each linkbase are archetypal for their context, and can be resolved as hierarchical ARIs.
Global linkbases may emerge over time to answer more generalized queries.
Computers can serialize a linkbase in many formats.
The Epiarc User Agent is the client software that interacts with the Epiarc on behalf of a user.
A User Agent can subscribe to and manage linkbases.
A User Agent can perform ARI resolution (ARI → URI).
A User Agent can perform reverse resolution (URI → ARIs).
A User Agent follows rules to resolve an ARI in context.
If a User Agent shows a more expansive list of results, it may have its own rules to rank and tie-break results from multiple subscribed linkbases.