spec: Add "AI Actor Naming Standard" specification#19
Closed
mindpower wants to merge 1 commit into
Closed
Conversation
darrelmiller
added a commit
to darrelmiller/ai-card
that referenced
this pull request
Apr 1, 2026
Rename Catalog Entry fields per AI Actor Naming Standard (PR Agent-Card#19): - id -> identifier (globally unique logical address) - name -> displayName (human-readable label) Updated in: field definitions, CDDL schema, Mermaid diagram, multi-version rules, trust identity binding, conformance levels, all JSON examples, and OCI/MCP/Claude mapping tables. HostInfo, Publisher, CollectionRef, and TrustSchema retain their existing id/name fields (not agent naming fields). Also updated publish-spec skill to reference renamed markdown file (draft-ai-card.md -> ai-catalog.md). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
|
||
| | Field Name | Conceptual Name | Type | Description / Format | | ||
| | :---- | :---- | :---- | :---- | | ||
| | identifier | **Agent Identifier** | string | **Logical Name / Handle:** A globally unique, stable logical address. It MUST follow the URN convention (e.g., urn:agent:google:tax-bot). | |
Contributor
There was a problem hiding this comment.
Doesn't this example violate the rule that "google" is not a verifiable domain?
Member
Author
There was a problem hiding this comment.
Updated the example (publisher should be a verifier domain name)
| **Format:** urn:agent:\<publisher-domain\>:\<namespace\>:\<agent-name\> | ||
|
|
||
| * **urn**: The fixed prefix required by IETF RFC 8141\. | ||
| * **agent**: The Namespace Identifier (NID). Other collections in the registry may use different NIDs (e.g., mcp, interactions). |
Contributor
There was a problem hiding this comment.
If we are to create an "agent" NID then we should include a registration template in this document e.g. https://www.rfc-editor.org/rfc/rfc8141#appendix-A
How do we define "agent"? What is or isn't an agent?
This puts a burden on each ai artifact to go register a new URN namespace.
|
Can we close this now as superceeded by PR36? |
Member
Author
|
Closing this once since it's covered in #36 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces the "AI Actor Naming Standard," a foundational specification for ensuring interoperability, discovery within the AI agent ecosystem.
Summary
As AI agents begin to interact across organizational boundaries, the lack of a common naming protocol creates ambiguity and hinders discovery. This standard solves this by defining a secure, multi-layer naming system that separates an agent's human-readable name from its stable, machine-readable logical address.
Core ### Concepts
The standard is built on two primary fields:
displayName(Short Name): A human-readable name used for discovery in UIs (e.g., "Google Tax Bot"). This name can be simple, intuitive, and is not required to be unique.identifier(Agent Identifier): A globally unique, immutable logical address that follows a URN (Uniform Resource Name) convention. This acts as the permanent handle that developers use to reference the agent, ensuring stability even if underlying infrastructures change.The URN Specification (identifier)
The
identifierprovides a verifiable and hierarchical naming structure. It MUST follow the format:urn:agent:<publisher-domain>:<namespace>:<agent-name>urn:agent:salesforce.com:productivity:slide-generator