<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.2.3) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-besleaga-agentic-knowledge-wellknown-02" category="info" version="3">
  <!-- xml2rfc v2v3 conversion 3.34.0 -->
  <front>
    <title abbrev="knowledge-linkset Well-Known URI">The 'knowledge-linkset' Well-Known URI for Publishing Knowledge Artefacts</title>
    <seriesInfo name="Internet-Draft" value="draft-besleaga-agentic-knowledge-wellknown-02"/>
    <author initials="A. N." surname="Besleaga" fullname="Andrei N. Besleaga">
      <organization>Independent</organization>
      <address>
        <email>andrei.besleaga.nicolae@gmail.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="15"/>
    <keyword>Internet-Draft</keyword>
    <keyword>Well-Known URI</keyword>
    <keyword>Linkset</keyword>
    <keyword>Link Set</keyword>
    <keyword>Knowledge Graph</keyword>
    <keyword>Discovery</keyword>
    <keyword>Integrity</keyword>
    <keyword>Agents</keyword>
    <abstract>

<t>This document defines the "knowledge-linkset" well-known URI, at which a
web origin publishes one link set describing the knowledge artefacts it
makes available: graph serializations, a JSON-LD context, an
agent-facing text file, a chunk export, a change ledger, and related
resources. Each artefact link may carry a SHA-256 digest, expressed with
the syntax of HTTP digest fields, so that a client can check that a
retrieved artefact is the one the publisher described. A profile URI
identifies the conventions the link set follows. The mechanism defines
no new media type and no new link relation type: a page points at the
resource with the existing "describedby" relation. The profile URI
is registered in the IANA "Profile URIs" registry. This document
requests no IANA action.</t>
    </abstract>
  </front>
  <middle>

<section anchor="introduction">
      <name>Introduction</name>
      <t>Software agents that read the Web need two different things. They need
to find out <em>who can act</em>: which agent, tool server, or service is
reachable, under what name, with what capabilities. A survey of that
field is available in <xref target="I-D.jimenez-dawn-discovery-landscape"/>. They
also need to find out <em>what is known</em>: which described, versioned,
checkable artefacts an origin publishes about its own subject matter --
a graph, a vocabulary, an index, a text rendering, a change ledger.
The first question has many answers. The second has partial ones: the
Vocabulary of Interlinked Datasets (VoID) <xref target="VOID"/>, at the registered
well-known URI <tt>void</tt>, and the Data Catalog Vocabulary (DCAT) <xref target="DCAT3"/>
describe datasets and their distributions as Resource Description
Framework data. None of them gives an origin one list, readable by any
Web Linking client, that names each of its knowledge artefacts, says
which serialization is which, and lets a client check that what it
fetched is what was published.</t>
      <t>This document defines that list. A web origin serves one resource at
<tt>/.well-known/knowledge-linkset</tt> <xref target="RFC8615"/>. The representation is a
link set <xref target="RFC9264"/> with one link context, anchored at the
Internationalized Resource Identifier (IRI) <xref target="RFC3987"/> of the
published knowledge Bundle. Its links name the artefacts, each with a
media type and optionally with a <tt>digest</tt> target attribute in the
syntax of HTTP digest fields <xref target="RFC9530"/>. A profile URI <xref target="RFC7284"/>,
carried on the media type or in a <tt>Link</tt> header field <xref target="RFC6906"/>,
tells a client which conventions the document follows.</t>
      <t>The design adds a path and a profile. Its extension relations
(<xref target="RFC8288"/>, Section 2.1.2) and extension target attributes
(<xref target="RFC9264"/>, Section 4.2.4.3) need no registry, <tt>digest</tt> reuses an
existing algorithm name and the structured-field value syntax
<xref target="RFC9651"/>, and no media type (<xref target="RFC6838"/>) or URI scheme is defined.
A generic link set client reads the document without knowing this
specification. The precedent is <tt>api-catalog</tt> <xref target="RFC9727"/>, a well-known
link set, identified by a profile URI, that lists an origin's APIs.</t>
      <t>The artefacts, the Bundle that contains them, and the bytes their
digests cover are defined by the AgenticSystemCore Specification
<xref target="AGSC-SPEC"/>. This document specifies the discovery resource and the
behaviour of a client that reads it. A client needs nothing else to read
a discovery document; a publisher needs <xref target="AGSC-SPEC"/> only to generate
the artefacts and the values of the bundle-fact attributes.</t>
      <t>This document defines no agent identity or authentication of fetchers,
no protocol, session, or transport between agents, no naming or
resolution layer for agents, no expression of preferences about how
content may be used, no read or write interface to an agent's memory,
and no artefact format. Publishing a discovery document grants no
rights or permissions, and asserts no property of the artefacts other
than that the origin published them. <xref target="relationship-to-other-work"/>
names the work that addresses each of these topics.</t>
    </section>
    <section anchor="conventions-and-terminology">
      <name>Conventions and Terminology</name>
      <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>

<t>Long lines in examples are folded as specified in <xref target="RFC8792"/>.</t>
      <dl spacing="compact">
        <dt>Bundle:</dt>
        <dd>
          <t>The set of items and generated artefacts that one origin publishes
under one anchor. The Bundle IRI is the origin's base URL with a
trailing solidus.</t>
        </dd>
        <dt>artefact:</dt>
        <dd>
          <t>One retrievable representation that belongs to a Bundle, such as a
graph serialization, a JSON-LD context, a vocabulary file, a text
rendering, a chunk export, a search index, a change ledger, or an
attachment.</t>
        </dd>
        <dt>discovery document:</dt>
        <dd>
          <t>The link set served at the well-known URI of <xref target="the-well-known-uri"/>.</t>
        </dd>
        <dt>profile:</dt>
        <dd>
          <t>A profile in the sense of <xref target="RFC6906"/>; the profile URI is given in
<xref target="the-profile-uri"/>.</t>
        </dd>
        <dt>node:</dt>
        <dd>
          <t>An origin that serves a conforming discovery document. Its operator
is the publisher.</t>
        </dd>
        <dt>peer:</dt>
        <dd>
          <t>A node that another node names in its discovery document with the
<tt>peer</tt> extension relation of <xref target="relations"/>.</t>
        </dd>
        <dt>gated:</dt>
        <dd>
          <t>Said of a node whose content is not public.</t>
        </dd>
      </dl>
    </section>
    <section anchor="the-well-known-uri">
      <name>The 'knowledge-linkset' Well-Known URI</name>
      <t>A node <bcp14>MUST</bcp14> serve its discovery document at the path
<tt>/.well-known/knowledge-linkset</tt> of its origin, over HTTPS. A node <bcp14>MUST</bcp14>
serve exactly one such document; it <bcp14>MUST NOT</bcp14> split the description of
one Bundle across several discovery resources, and it <bcp14>MUST NOT</bcp14> serve a
second, differently named manifest of the same artefacts. A copy of the
document <bcp14>MAY</bcp14> be distributed by other means, for example inside a
release archive, and a node <bcp14>MAY</bcp14> additionally serve the same bytes at a
path of its own choosing.</t>
      <section anchor="media-type-and-profile">
        <name>Media Type and Profile</name>
        <t>The representation <bcp14>MUST</bcp14> be a JSON link set, media type
<tt>application/linkset+json</tt> <xref target="RFC9264"/>. The profile URI of
<xref target="the-profile-uri"/> <bcp14>MUST</bcp14> be carried in at least one of two ways:</t>
        <ul spacing="normal">
          <li>
            <t>as the <tt>profile</tt> parameter of the media type (<xref target="RFC9264"/>,
Section 5), the default form:</t>
          </li>
        </ul>
        <figure>
          <name>The profile carried on the media type</name>
          <sourcecode type="http-message"><![CDATA[
NOTE: '\' line wrapping per RFC 8792

Content-Type: application/linkset+json; profile="https://w3id.\
org/agentic-system-core/profile/agentic-knowledge"
]]></sourcecode>
        </figure>
        <ul spacing="normal">
          <li>
            <t>or, where the hosting platform cannot attach a parameter to
<tt>Content-Type</tt>, as a response header field (<xref target="RFC6906"/>):</t>
          </li>
        </ul>
        <figure>
          <name>The profile carried in a Link header field</name>
          <sourcecode type="http-message"><![CDATA[
NOTE: '\' line wrapping per RFC 8792

Link: <https://w3id.org/agentic-system-core/profile/agentic-\
knowledge>; rel="profile"
]]></sourcecode>
        </figure>
        <t>A client <bcp14>MUST</bcp14> accept either form; whether it recognizes the profile
<bcp14>MUST NOT</bcp14> depend on whether it can read response header fields.</t>
      </section>
      <section anchor="caching">
        <name>Caching</name>
        <t>A node <bcp14>MUST</bcp14> send an <tt>ETag</tt> and <tt>Cache-Control: no-cache</tt> (<xref target="RFC9111"/>,
Section 5.2.2.4) on the discovery document. Where the publisher sets
the entity tag, it is the lowercase hexadecimal SHA-256 of the bytes
served, in double quotes (<xref target="RFC9110"/>, Section 8.8.3). A client <bcp14>SHOULD</bcp14>
make conditional requests (<xref target="RFC9110"/>, Section 13), and <bcp14>MUST NOT</bcp14> treat
an entity tag as an integrity statement: an intermediary may weaken or
replace it, and the <tt>digest</tt> attribute (<xref target="the-digest-attribute"/>) is
that statement.</t>
      </section>
      <section anchor="cross-origin-access">
        <name>Cross-Origin Access</name>
        <t>The header fields and terms of this section are those of Cross-Origin
Resource Sharing (CORS) in the Fetch Standard <xref target="FETCH"/>. The discovery
document, and every artefact it names that the node serves publicly,
<bcp14>MUST</bcp14> be served with <tt>Access-Control-Allow-Origin: *</tt> and
<tt>Access-Control-Expose-Headers: Link, ETag, Content-Type</tt>, and <bcp14>MUST NOT</bcp14>
be served with <tt>Access-Control-Allow-Credentials</tt>. A node <bcp14>MUST NOT</bcp14> require any request
header field outside the CORS-safelisted set for the discovery document
or any public artefact.</t>
        <t>A gated node <bcp14>MUST</bcp14> still serve the discovery document publicly and with
the wildcard above. It declares itself with the <tt>agsc-visibility</tt>
attribute (<xref target="declaration-attributes"/>) and names where a reader obtains
credentials with the <tt>access</tt> extension relation (<xref target="relations"/>).</t>
      </section>
    </section>
    <section anchor="the-link-set">
      <name>The Link Set</name>
      <section anchor="top-level-structure">
        <name>Top-Level Structure</name>
        <t>The document is a JSON object (<xref target="RFC8259"/>) whose sole top-level member
is <tt>linkset</tt> (<xref target="RFC9264"/>, Section 4.2.1). A node that produces
canonical bytes serializes the document with the JSON Canonicalization
Scheme <xref target="RFC8785"/>, followed by one line feed; a node that does not
<bcp14>MUST</bcp14> at least produce Internet JSON (I-JSON) <xref target="RFC7493"/>.</t>
        <t>The <tt>linkset</tt> array holds exactly one link context object, whose
<tt>anchor</tt> is the Bundle IRI, for example <tt>https://example.org/</tt>. A
client <bcp14>MUST</bcp14> ignore an additional link context object it does not
understand. A client <bcp14>MUST NOT</bcp14> take a document whose <tt>anchor</tt> is not on
the origin of the URL it finally retrieved the document from, after
redirects, as that origin's discovery document (<xref target="RFC8615"/>, Section
4.3).</t>
        <t>Every link object <bcp14>MUST</bcp14> carry <tt>href</tt>, and every <tt>href</tt> <bcp14>MUST</bcp14> be a URI
(<xref target="RFC3986"/>, Section 3), not a relative reference. Within one relation's array, link
objects are ordered by <tt>href</tt> in code point order.</t>
      </section>
      <section anchor="relations">
        <name>Relations</name>
        <t>A relation name <bcp14>MUST</bcp14> be either a registered short name from the "Link
Relation Types" registry or an extension relation expressed as a URI
(<xref target="RFC8288"/>, Section 2.1.2). The registered short names used are
<tt>describedby</tt>, <tt>alternate</tt>, <tt>license</tt>, <tt>service-doc</tt>, and <tt>author</tt>, and,
in related-system links, those of <xref target="related-system-links"/>.</t>
        <t>The extension relations form a closed set. Each is the URI
<tt>https://w3id.org/agentic-system-core/rel#&lt;name&gt;</tt>, where <tt>&lt;name&gt;</tt> and
the target are one of:</t>
        <dl spacing="compact">
          <dt><tt>graph</tt>:</dt>
          <dd>
            <t>a further serialization of the Bundle's graph</t>
          </dd>
          <dt><tt>ontology</tt>:</dt>
          <dd>
            <t>the vocabulary the graph uses</t>
          </dd>
          <dt><tt>context</tt>:</dt>
          <dd>
            <t>the JSON-LD context of the graph</t>
          </dd>
          <dt><tt>now</tt>:</dt>
          <dd>
            <t>the generated state page of the Bundle</t>
          </dd>
          <dt><tt>skills</tt>:</dt>
          <dd>
            <t>the index of exported procedure packages</t>
          </dd>
          <dt><tt>ledger</tt>:</dt>
          <dd>
            <t>the derived change ledger of the Bundle</t>
          </dd>
          <dt><tt>peer</tt>:</dt>
          <dd>
            <t>another node's discovery document</t>
          </dd>
          <dt><tt>surface</tt>:</dt>
          <dd>
            <t>an agent-facing surface this node serves</t>
          </dd>
          <dt><tt>contribute</tt>:</dt>
          <dd>
            <t>an endpoint that accepts contributions</t>
          </dd>
          <dt><tt>access</tt>:</dt>
          <dd>
            <t>a page that says how to obtain credentials</t>
          </dd>
          <dt><tt>signature</tt>:</dt>
          <dd>
            <t>a detached signature over the discovery document</t>
          </dd>
          <dt><tt>boards</tt>:</dt>
          <dd>
            <t>the index of the Bundle's project boards</t>
          </dd>
        </dl>
        <t>A client <bcp14>MUST</bcp14> ignore a relation name it does not recognize. A node <bcp14>MUST
NOT</bcp14> invent a further extension relation under the same base; a new
member is added only by a later version of <xref target="AGSC-SPEC"/> (<xref target="versions"/>).</t>
      </section>
      <section anchor="target-attributes">
        <name>Target Attributes</name>
        <t>A link object <bcp14>MAY</bcp14> carry the target attributes <tt>type</tt>, <tt>title</tt>, and
<tt>hreflang</tt> (<xref target="RFC8288"/>, Section 3.4.1; <xref target="RFC9264"/>, Section 4.2.4.1),
and the extension target attribute <tt>profile</tt>, whose values are profile
URIs (<xref target="RFC6906"/>). A client <bcp14>MUST NOT</bcp14> depend on <tt>type</tt>, and <bcp14>MUST</bcp14> use
the media type of the response it actually receives.</t>
        <t>Every extension target attribute value, <tt>profile</tt> included, is an array
of strings (<xref target="RFC9264"/>, Section 4.2.4.3). A client <bcp14>MUST</bcp14> ignore an
extension target attribute it does not recognize.</t>
        <section anchor="the-digest-attribute">
          <name>The digest Attribute</name>
          <t>A link object <bcp14>MAY</bcp14> carry the target attribute <tt>digest</tt>. Its value is an
array holding one string, the serialization (<xref target="RFC9651"/>, Section 4.1)
of a Dictionary (<xref target="RFC9651"/>, Section 3.2) with a single member. The
member's key is the algorithm name <tt>sha-256</tt> from the "Hash Algorithms
for HTTP Digest Fields" registry (<xref target="RFC9530"/>, Section 7.2), and its
value is a Byte Sequence (<xref target="RFC9651"/>, Section 3.3.5):</t>
          <sourcecode type="json"><![CDATA[
"digest": [
  "sha-256=:JeigkAtOPS9f9BzKym+X6J2O4awt53GEua1AhIAiLfE=:"
]
]]></sourcecode>
          <t>The digest is taken over the canonical bytes of the target, as the
publisher generated and serves them, before any content coding. A
client compares it with the decoded representation data of the target.</t>
        </section>
        <section anchor="bundle-fact-attributes">
          <name>Bundle-Fact Attributes</name>
          <t>Facts about the Bundle as a whole ride only on the anchor's
<tt>describedby</tt> link whose target is the Bundle's JSON-LD graph:</t>
          <dl spacing="compact">
            <dt><tt>agsc-spec-version</tt>:</dt>
            <dd>
              <t>one value, the version of <xref target="AGSC-SPEC"/> the node publishes against.</t>
            </dd>
            <dt><tt>agsc-generated-at</tt>:</dt>
            <dd>
              <t>one value, the instant the artefacts were generated, as
<tt>YYYY-MM-DDTHH:MM:SSZ</tt> (UTC, second precision, no offset). A node
that supports reproducible builds derives it from the build's source
date.</t>
            </dd>
            <dt><tt>agsc-counts</tt>:</dt>
            <dd>
              <t>one string per item type, of the form <tt>&lt;type-plural&gt;=&lt;n&gt;</tt>, in code
point order of the type name, counted over the published set.</t>
            </dd>
            <dt><tt>agsc-bundle-hash</tt>:</dt>
            <dd>
              <t>one value, the digest of the Bundle's canonical N-Quads
serialization, in the syntax of <xref target="the-digest-attribute"/>. It equals
the <tt>digest</tt> of the <tt>graph</tt> link to that serialization.</t>
            </dd>
            <dt><tt>agsc-bundle-version</tt>:</dt>
            <dd>
              <t>one value, the publisher's content version for the state the
artefacts were generated from, a short name a person can read and
cite. It is derived by the publisher and is opaque to a client,
which <bcp14>MUST NOT</bcp14> order two values or infer a sequence from them.</t>
            </dd>
          </dl>
          <t>Two attributes ride on the <tt>ledger</tt> link and nowhere else; the second
is optional:</t>
          <dl spacing="compact">
            <dt><tt>agsc-ledger-head</tt>:</dt>
            <dd>
              <t>one value, the chain hash of the last entry of the derived change
ledger (<xref target="AGSC-SPEC"/>), in lowercase hexadecimal.</t>
            </dd>
            <dt><tt>agsc-ledger-length</tt>:</dt>
            <dd>
              <t>one value, the number of entries of the derived change ledger, in
decimal.</t>
            </dd>
          </dl>
          <t>Two attributes ride, beside the <tt>digest</tt>, on the <tt>surface</tt> link whose
<tt>agsc-surface</tt> value is <tt>chunks</tt>, and nowhere else. That link names the
chunk export's main file, which lists the other files when the export
is split; the <tt>digest</tt> covers that file.</t>
          <dl spacing="compact">
            <dt><tt>agsc-chunk-count</tt>:</dt>
            <dd>
              <t>one value, the number of chunk records in the export, across all of
its files, in decimal.</t>
            </dd>
            <dt><tt>agsc-chunk-set</tt>:</dt>
            <dd>
              <t>one value, in the syntax of <xref target="the-digest-attribute"/>, the SHA-256 of
the identifiers of all chunk records, in file order and record order,
each written as 64 lowercase hexadecimal characters followed by one
line feed; for an export with no record, the SHA-256 of no bytes.</t>
            </dd>
          </dl>
          <t>The ledger length and the chunk attributes exist from version 1.1.0 of
<xref target="AGSC-SPEC"/> and are absent from a document that states an earlier
<tt>agsc-spec-version</tt>. A client <bcp14>MUST NOT</bcp14> read an attribute of this
section from a link other than the one named for it.</t>
        </section>
        <section anchor="declaration-attributes">
          <name>Declaration Attributes</name>
          <t>The extension target attributes below declare what a node is. They
appear in the full and in the reduced form (<xref target="the-reduced-form"/>).</t>
          <dl spacing="compact">
            <dt><tt>agsc-surface</tt> and <tt>agsc-surface-version</tt>:</dt>
            <dd>
              <t>on a <tt>surface</tt> link, one value each: the kind of agent-facing surface
the node serves, and, where an external specification defines the
surface, the revision of that specification the node targets.</t>
            </dd>
            <dt><tt>agsc-access</tt>:</dt>
            <dd>
              <t>on a <tt>surface</tt> link or the <tt>access</tt> link, one value: <tt>none</tt>,
<tt>consent</tt>, or <tt>credential</tt>.</t>
            </dd>
            <dt><tt>agsc-visibility</tt>:</dt>
            <dd>
              <t>on the anchor's <tt>describedby</tt> link, the single value <tt>restricted</tt>,
emitted only by a gated node.</t>
            </dd>
            <dt><tt>agsc-contribute-mode</tt>:</dt>
            <dd>
              <t>on a <tt>contribute</tt> link, one value naming how contributions are
accepted.</t>
            </dd>
            <dt><tt>agsc-tombstone</tt>:</dt>
            <dd>
              <t>on the anchor's <tt>describedby</tt> link, one instant in the form of
<tt>agsc-generated-at</tt>, present only on a node that has stopped
publishing (<xref target="tombstones"/>).</t>
            </dd>
          </dl>
          <t>A client that meets a value it does not know in <tt>agsc-visibility</tt>,
<tt>agsc-access</tt>, <tt>agsc-surface</tt>, or <tt>agsc-contribute-mode</tt> <bcp14>MUST NOT</bcp14> fail.
It <bcp14>MUST</bcp14> treat the value as the most restrictive one: <tt>restricted</tt>,
<tt>credential</tt>, a surface the node does not serve, and a mode that
accepts no contribution, respectively.</t>
        </section>
      </section>
      <section anchor="the-reduced-form">
        <name>The Reduced Form</name>
        <t>A publisher without a build engine, such as a content management system
or a wiki that exports static files, publishes the same link set with
every <tt>digest</tt> attribute and every attribute of
<xref target="bundle-fact-attributes"/> omitted. Such a publisher has no ledger. A
client
<bcp14>MUST</bcp14> treat a link without a <tt>digest</tt> attribute as <em>unverified</em>, never
as <em>invalid</em>.</t>
      </section>
      <section anchor="related-system-links">
        <name>Related-System Links</name>
        <t>A node <bcp14>MAY</bcp14> carry, in the same link context, links to other discovery
documents and to related systems: an agent-facing text file, a dataset
description, a catalogue entry, an agent card, a tool server's
description, a query endpoint. Such links use registered short names
only, each with its registered meaning: <tt>describedby</tt>, <tt>alternate</tt>,
<tt>related</tt>, <tt>service-desc</tt>, <tt>service-doc</tt>, <tt>service-meta</tt>, <tt>collection</tt>,
<tt>item</tt>, and <tt>cite-as</tt> (<xref target="RFC8574"/>). A link whose relation is
<tt>related</tt>, <tt>service-desc</tt>, <tt>service-meta</tt>, <tt>collection</tt>, <tt>item</tt>, or
<tt>cite-as</tt> is always a related-system link; a <tt>describedby</tt>,
<tt>alternate</tt>, or <tt>service-doc</tt> link is one when its target is not one of
the node's own artefacts or pages. Each <bcp14>MUST</bcp14> carry <tt>type</tt> and <bcp14>MAY</bcp14> carry
<tt>profile</tt> and <tt>title</tt>.</t>
        <t>A client <bcp14>MUST</bcp14> ignore a related-system link it does not understand. No
related-system link affects any digest, and none is followed by the
walk of <xref target="following-peers"/>.</t>
      </section>
    </section>
    <section anchor="discovery-from-a-page">
      <name>Discovery from a Page</name>
      <t>A node <bcp14>SHOULD</bcp14> place, in the <tt>head</tt> element of every HTML page it
generates:</t>
      <sourcecode type="html"><![CDATA[
<link rel="describedby"
      href="/.well-known/knowledge-linkset"
      type="application/linkset+json">
]]></sourcecode>
      <t>and <bcp14>SHOULD</bcp14> send, at least on the origin's root route, the equivalent
response header field:</t>
      <sourcecode type="http-message"><![CDATA[
NOTE: '\' line wrapping per RFC 8792

Link: </.well-known/knowledge-linkset>; rel="describedby"; \
type="application/linkset+json"
]]></sourcecode>
      <t>On the root route, the same header field may also name the discovery
document with the <tt>linkset</tt> relation (<xref target="RFC9264"/>, Section 6).</t>
      <t><tt>describedby</tt> is defined in Appendix D of <xref target="POWDER-DR"/>, which
registers it, and <xref target="RFC6892"/> registers its inverse, <tt>describes</tt>. The
target's media type and profile URI say what kind of description it is.
A page may carry other <tt>describedby</tt> links, such as one to an
<xref target="LLMSTXT"/> file. A client selects this one by
<tt>type="application/linkset+json"</tt> and, having fetched it, confirms the
profile (<xref target="media-type-and-profile"/>). Where several candidates remain,
a client <bcp14>SHOULD</bcp14> fetch the one whose <tt>href</tt> resolves to
<tt>/.well-known/knowledge-linkset</tt> on the origin.</t>
    </section>
    <section anchor="the-profile-uri">
      <name>The Profile URI</name>
      <t>The profile URI of the discovery document is
<tt>https://w3id.org/agentic-system-core/profile/agentic-knowledge</tt>.</t>
      <section anchor="what-the-profile-fixes">
        <name>What the Profile Fixes</name>
        <t>A client that ignores the profile reads the document as a link set
(<xref target="RFC6906"/>, Section 3). A client that recognizes it may rely on the
single link context anchored at the Bundle IRI
(<xref target="top-level-structure"/>), the closed set of relations (<xref target="relations"/>),
the form of <tt>digest</tt> (<xref target="the-digest-attribute"/>), the links that carry
the bundle-fact, ledger, and chunk attributes
(<xref target="bundle-fact-attributes"/>), and extension target attribute values
that are arrays of strings (<xref target="target-attributes"/>).</t>
      </section>
      <section anchor="carriage-and-resolution">
        <name>Resolution</name>
        <t>The profile URI, and every extension relation URI of <xref target="relations"/>,
resolves through w3id.org, a persistent-identifier service, with an
HTTP 303 redirect (<xref target="RFC9110"/>, Section 15.4.4) to a published
specification page. That page carries one fragment identifier for the
list of relations and one per relation name, so every extension
relation URI dereferences to its own documentation (<xref target="RFC8288"/>,
Section 2.1.2).</t>
      </section>
      <section anchor="versions">
        <name>Versions</name>
        <t>The profile URI carries no version number. It names the same profile
for every version of <xref target="AGSC-SPEC"/> that has the same major version
number. A document in the full form states its version in
<tt>agsc-spec-version</tt> (<xref target="bundle-fact-attributes"/>).</t>
        <t>A later minor version of <xref target="AGSC-SPEC"/> only adds:</t>
        <ul spacing="compact">
          <li>
            <t>extension relations under the same base URI, each with its own
fragment on the specification page;</t>
          </li>
          <li>
            <t>extension target attributes with the <tt>agsc-</tt> prefix;</t>
          </li>
          <li>
            <t>related-system relations, once they are registered;</t>
          </li>
          <li>
            <t>values of the declaration attributes.</t>
          </li>
        </ul>
        <t>The client rules of <xref target="relations"/>, <xref target="target-attributes"/>,
<xref target="declaration-attributes"/>, and <xref target="related-system-links"/> let a client
read such a document without error and without change. Any other change
is made only in a new major version of <xref target="AGSC-SPEC"/>.</t>
      </section>
    </section>
    <section anchor="client-behaviour">
      <name>Client Behaviour</name>
      <t>A client that fetches one document from an origin it was given applies
<xref target="fetch-safety"/> and <xref target="untrusted-content"/>. A client that follows
<tt>peer</tt> links applies all of this section.</t>
      <section anchor="fetch-safety">
        <name>Fetch Safety</name>
        <ul spacing="compact">
          <li>
            <t>A client <bcp14>MUST</bcp14> refuse any URL that is not an absolute <tt>https</tt> URL,
except an <tt>http</tt> URL to a loopback address when the client has been
explicitly placed in a development mode.</t>
          </li>
          <li>
            <t>Before connecting, a client <bcp14>MUST</bcp14> resolve the host and <bcp14>MUST</bcp14> refuse any
resolved address that is not globally reachable according to the
IANA IPv4 <xref target="IANA-IPV4-SPECIAL"/> or IPv6 <xref target="IANA-IPV6-SPECIAL"/>
Special-Purpose Address Registry, other than a loopback address in
the development mode above. A client <bcp14>MUST</bcp14> equally refuse any IPv6
address that embeds an IPv4 address -- IPv4-mapped, IPv4-compatible,
NAT64 (IPv6-to-IPv4 translation), Teredo, and 6to4 addresses --
whatever IPv4 address it embeds, and any multicast address. A host
that resolves to several addresses <bcp14>MUST</bcp14> be refused if any one of them
is refused.</t>
          </li>
          <li>
            <t>A client <bcp14>MUST</bcp14> give every textual form of one address the same
classification: compressed or expanded, and with an embedded IPv4
address written as a dotted quad or in hexadecimal.</t>
          </li>
          <li>
            <t>A client <bcp14>MUST</bcp14> connect to one of the addresses it classified, <bcp14>MUST NOT</bcp14>
re-resolve the host between classification and connection, and <bcp14>MUST</bcp14>
re-verify the remote address of the established connection against
the same rules, closing the connection on a mismatch.</t>
          </li>
          <li>
            <t>A client <bcp14>MUST</bcp14> bound the number of redirects it follows, <bcp14>MUST</bcp14> re-apply
the rules above to every hop, and <bcp14>MUST NOT</bcp14> follow a redirect to a
non-<tt>https</tt> URL other than the development loopback case. The final
URL of a redirected fetch is not substituted for the URL that was
declared.</t>
          </li>
          <li>
            <t>A client <bcp14>MUST</bcp14> bound the size of a discovery document it reads,
measured after content decoding, and treat a larger response as
unreadable without buffering it; one mebibyte suffices for the
documents this document describes.</t>
          </li>
          <li>
            <t>A client <bcp14>SHOULD</bcp14> bound the time it waits for a response.</t>
          </li>
        </ul>
      </section>
      <section anchor="following-peers">
        <name>Following Peers</name>
        <t>The target of a <tt>peer</tt> link is the peer's discovery document URL. Two
nodes are peers of each other when each names the other; nothing else
establishes the relation.</t>
        <t>A client that walks from a starting node <bcp14>MUST</bcp14>:</t>
        <ul spacing="compact">
          <li>
            <t>bound the depth of the walk, the starting node being depth zero;</t>
          </li>
          <li>
            <t>consider at most a fixed number of <tt>peer</tt> links per discovery
document, in document order, ignoring the rest;</t>
          </li>
          <li>
            <t>issue at most a fixed number of requests per walk, counting every
request including redirects;</t>
          </li>
          <li>
            <t>keep a visited set keyed by the canonical well-known URL, and never
fetch a member of it twice;</t>
          </li>
          <li>
            <t>treat a peer whose fetch times out, returns a non-2xx status, exceeds
the size bound, or yields a document that is not a conformant
discovery document as unreachable: record it, skip it, and never
retry it within the walk.</t>
          </li>
        </ul>
        <t>A client that stops because a bound was reached, or that ignored links
beyond its per-document bound, <bcp14>MUST</bcp14> report the result as partial, with
the set of nodes it did visit. A client that completes without touching
any bound <bcp14>MUST</bcp14> report the result as complete.</t>
        <t>Suggested defaults, which a deployment may lower: depth three, fifty
<tt>peer</tt> links per document, five hundred requests per walk, ten seconds
per request, three redirects per fetch.</t>
      </section>
      <section anchor="untrusted-content">
        <name>Untrusted Content</name>
        <t>Everything a client obtains from a node other than the one it is acting
for is untrusted data. A client <bcp14>MUST</bcp14> carry that fact with the data: a
search hit, a retrieved item, a chunk, or a quotation derived from
another node <bcp14>MUST</bcp14> be labelled untrusted and <bcp14>MUST</bcp14> name the origin it
came from, through every interface the client offers and every export
it produces. A client <bcp14>MUST NOT</bcp14> merge another node's prose into its own
published artefacts other than through a reviewed proposal that records
the other node's IRI as the source.</t>
      </section>
      <section anchor="federation-is-client-side">
        <name>Federation Is Client-Side</name>
        <t>A node's query surface is the set of artefacts it publishes. A node
<bcp14>MUST NOT</bcp14> fetch another node while building its own artefacts, and <bcp14>MUST
NOT</bcp14> expose an endpoint that fetches another node on a caller's behalf.</t>
      </section>
    </section>
    <section anchor="relationship-to-other-work">
      <name>Relationship to Other Work</name>
      <t>This section is informative.</t>
      <t><tt>llms.txt</tt> <xref target="LLMSTXT"/> is a community convention for a Markdown file at
<tt>/llms.txt</tt> that presents an origin's content to language models. Its
version 2 recommends <tt>rel="describedby"</tt> for the file and
<tt>rel="alternate"</tt> with <tt>type="text/markdown"</tt> for a page's Markdown
rendering; a node may name such a file with <tt>alternate</tt>.
<xref target="I-D.arsentev-llm-context-discovery"/> defines the discovery of one
such publisher-curated context file through a well-known URI, a link
relation, and a <tt>robots.txt</tt> record.</t>
      <t><xref target="I-D.serra-mcp-discovery-uri"/> defines an <tt>mcp</tt> URI scheme and the
discovery of Model Context Protocol servers through a well-known path
and DNS TXT records. <xref target="MCP"/> defines a protocol between a client and a
tool server, and <xref target="A2A"/> an agent card, served at a well-known path,
that describes an agent's capabilities and interfaces; a node may
declare either as one of its surfaces (<xref target="declaration-attributes"/>).</t>
      <t>The <tt>dawn</tt> working group <xref target="DAWN-CHARTER"/> addresses the discovery of
agents by name, and <xref target="I-D.jimenez-dawn-discovery-landscape"/>
catalogues the mechanisms in that space. The <tt>agentproto</tt> working
group <xref target="AGENTPROTO-CHARTER"/> addresses the management of dialogs
between users, agents, and tools. The W3C AI Agent Memory
Interoperability Community Group <xref target="AIMEM-CG"/> addresses the
interoperability of protocols for AI agent memory.</t>
      <t><xref target="I-D.ietf-aipref-vocab"/> defines a vocabulary for preferences about
AI usage of content, and <xref target="I-D.ietf-aipref-attach"/> the means of
attaching them in HTTP; a publisher attaches preferences to the
artefacts a discovery document names by those means and by
<tt>robots.txt</tt> <xref target="RFC9309"/>. HTTP message signatures for automated traffic
<xref target="I-D.ietf-webbotauth-httpsig-protocol"/> identify the client making a
request.</t>
      <t>The "Knowledge Bundle" of the Open Knowledge Format <xref target="OKF"/>, a set of
Markdown files with front matter and an index file, is a different
object from the Bundle of this document. A VoID or DCAT description
(<xref target="introduction"/>) is named with a further <tt>describedby</tt> link
(<xref target="related-system-links"/>).</t>
      <t><xref target="I-D.aiendpoint-ai-discovery"/> requests the well-known URI suffix <tt>ai</tt>
(or <tt>ai-discovery</tt>) for a description of a service's capabilities, and
<xref target="I-D.car-ai-txt-wellknown"/> requests <tt>ai.txt</tt> and <tt>ai.json</tt> for
declarations of AI usage preferences and licensing. The suffix used
here names the class of resource served (<xref target="iana-well-known-uri"/>) and
does not begin with <tt>ai</tt> or <tt>agent</tt>.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document requests no IANA action. It creates no registry, and
requests no media type, no URI scheme, no link relation type, and no
well-known URI registration.</t>
      <section anchor="iana-well-known-uri">
        <name>Well-Known URI</name>
        <t>No registration of the "knowledge-linkset" suffix in the "Well-Known
URIs" registry is requested at this time. A later request would use
the template of <xref target="RFC8615"/>, Section 3.1, with these values:</t>
        <ul spacing="normal">
          <li>
            <t><strong>URI suffix</strong>: knowledge-linkset</t>
          </li>
          <li>
            <t><strong>Change controller</strong>: Andrei N. Besleaga
(andrei.besleaga.nicolae@gmail.com)</t>
          </li>
          <li>
            <t><strong>Specification document(s)</strong>: This document.</t>
          </li>
          <li>
            <t><strong>Status</strong>: provisional</t>
          </li>
          <li>
            <t><strong>Related information</strong>: Used with the "https" URI scheme. The
resource is an <tt>application/linkset+json</tt> document <xref target="RFC9264"/>
carrying the profile URI
<tt>https://w3id.org/agentic-system-core/profile/agentic-knowledge</tt>,
whose registration is described in <xref target="iana-profile-uri"/>.</t>
          </li>
        </ul>
        <t>The suffix names the class of resource served -- a link set of the
knowledge artefacts an origin publishes -- rather than a subject area,
in keeping with the precision <xref target="RFC8615"/>, Section 3, expects of a
registered name.</t>
      </section>
      <section anchor="iana-profile-uri">
        <name>Profile URI</name>
        <t>The following profile URI was registered in the "Profile URIs"
registry (<xref target="RFC7284"/>, Section 4) on 2026-10-05; that registry's
policy is First Come First Served. The fields are given here so that
this document, which specifies the profile, records them:</t>
        <ul spacing="normal">
          <li>
            <t><strong>Profile URI</strong>:
<tt>https://w3id.org/agentic-system-core/profile/agentic-knowledge</tt></t>
          </li>
          <li>
            <t><strong>Common Name</strong>: AgenticSystemCore knowledge link set profile</t>
          </li>
          <li>
            <t><strong>Description</strong>: Identifies an <tt>application/linkset+json</tt> document
<xref target="RFC9264"/> that describes a published knowledge Bundle: one link
context whose anchor is the Bundle IRI, links to the Bundle's
artefacts -- graph serializations, a JSON-LD context, a vocabulary, a
chunk export, an agent-facing text file, a change ledger -- each
optionally carrying a <tt>digest</tt> target attribute in the syntax of
<xref target="RFC9530"/>, and the bundle-fact and declaration target attributes
this document defines. Served at <tt>/.well-known/knowledge-linkset</tt>;
linked from pages with <tt>rel="describedby"</tt> and
<tt>type="application/linkset+json"</tt>.</t>
          </li>
          <li>
            <t><strong>Reference</strong>: This document; and <xref target="AGSC-SPEC"/>, which defines the
artefacts and their canonical bytes.</t>
          </li>
          <li>
            <t><strong>Notes</strong>: The profile does not change the semantics of
<tt>application/linkset+json</tt> for a client that ignores it (<xref target="RFC6906"/>,
Section 3); it adds integrity, bundle-fact, and declaration target
attributes that a client <bcp14>MAY</bcp14> use. The same profile URI serves every
version of the AgenticSystemCore specification with the same major
version number; a document in the full form states the version it
follows in its <tt>agsc-spec-version</tt> attribute. Change controller:
Andrei N. Besleaga, Independent, andrei.besleaga.nicolae@gmail.com.</t>
          </li>
        </ul>
      </section>
    </section>
    <section anchor="implementation-status">
      <name>Implementation Status</name>
      <ul empty="true">
        <li>
          <t>[Note to the RFC Editor: please remove this section before
publication.]</t>
        </li>
      </ul>
      <t>This section records the status of known implementations of the
protocol defined by this specification at the time of posting of
this Internet-Draft, and is based on a proposal described in
<xref target="RFC7942"/>.  The description of implementations in this section is
intended to assist the IETF in its decision processes in
progressing drafts to RFCs.  Please note that the listing of any
individual implementation here does not imply endorsement by the
IETF.  Furthermore, no effort has been spent to verify the
information presented here that was supplied by IETF contributors.
This is not intended as, and must not be construed to be, a
catalog of available implementations or their features.  Readers
are advised to note that other implementations may exist.</t>
      <t>According to <xref target="RFC7942"/>, "this will allow reviewers and working
groups to assign due consideration to documents that have the
benefit of running code, which may serve as evidence of valuable
experimentation and feedback that have made the implemented
protocols more mature.  It is up to the individual working groups
to use this information as they see fit".
      </t>
      <t>The implementations below are the author's (Independent), who is the
contact for each; the information is as of 15 November 2026. All
implement this revision and version 1.1.0 of <xref target="AGSC-SPEC"/>.</t>
      <dl>
        <dt>Reference node:</dt>
        <dd>
          <t><tt>https://agenticsystemcore.com/</tt>, a static site that serves a
discovery document in the full form, its artefacts, and the
specification page that the profile URI and the extension relation
URIs resolve to. A second node, <tt>https://patterns.agenticsystemcore.com/</tt>,
is built by the same engine; each node names the other as a peer.
Working implementation; the engine is the npm package
<tt>agentic-system-core</tt>. Coverage: <xref target="the-well-known-uri"/> to
<xref target="the-profile-uri"/>. Licensing: the site's own terms.</t>
        </dd>
        <dt>Validator:</dt>
        <dd>
          <t><tt>validate-wellknown</tt>, a command-line tool in the npm and the PyPI
package named <tt>agentic-system-core</tt>. It checks a URL or a local file against
<xref target="the-well-known-uri"/> and <xref target="the-link-set"/>: the reduced form where it
is claimed, otherwise with the digests, the bundle facts, and the
chunk count and set recomputed. With <tt>--peer</tt> it performs the mutual
test of <xref target="following-peers"/>, also on local files without network
access. Working implementation; Apache-2.0.</t>
        </dd>
        <dt>Conformance vectors:</dt>
        <dd>
          <t>JSON test vectors for <xref target="the-link-set"/>, including
<xref target="the-reduced-form"/>, and for <xref target="following-peers"/>, each naming the
rule it proves, against which any implementation can be run.
Fixtures, released with the engine; Apache-2.0.</t>
        </dd>
      </dl>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <section anchor="what-a-digest-proves">
        <name>What a Digest Proves</name>
        <t>A <tt>digest</tt> attribute binds an artefact to the discovery document. It
lets a client detect that the artefact it retrieved is not the one the
publisher described: a truncated file, a cache that served an older
copy, a mirror that altered the bytes, a transfer that corrupted them.
It proves nothing else: neither the mechanisms of this document nor a
digest prove safety or the absence of a novel attack carried in the
content of an artefact, and an implementation <bcp14>MUST NOT</bcp14> claim more.</t>
        <t>A <tt>digest</tt> attribute does not bind the discovery document to an author.
An attacker who controls the origin controls the discovery document and
the artefacts together, and can make them agree. A client obtains the
identity of the publisher only from the TLS certificate and the DNS
name of the origin. A publisher who needs authorship verified
independently of the origin signs the responses, for example with
<xref target="RFC9421"/>, or names a detached signature with the <tt>signature</tt>
extension relation (<xref target="relations"/>). This document defines no signature
format: a client <bcp14>MUST</bcp14> ignore that link if it does not understand the
target, and the link affects no digest and no walk.</t>
        <t>A client that keeps the <tt>agsc-ledger-head</tt> value it saw on an earlier
retrieval, and that later reads a head that does not extend the earlier
one, has observed a rollback or a replacement of the ledger, and <bcp14>SHOULD</bcp14>
treat it as such rather than as an ordinary update.</t>
        <t>The only digest algorithm is <tt>sha-256</tt>; another algorithm needs a new
major version (<xref target="versions"/>). The considerations of <xref target="RFC9530"/>,
Section 6, apply.</t>
      </section>
      <section anchor="fetching-security">
        <name>Fetching</name>
        <t>A discovery document is a list of URLs supplied by a third party.
Without the rules of <xref target="fetch-safety"/>, any origin a client reads can
direct it at any address its network can reach, use it to probe an
internal address space, or hold it open. The re-verification of the
established connection guards against DNS rebinding. Measuring the size
after content decoding guards against compressed responses that expand
without bound.</t>
        <t>Because no node fetches another node (<xref target="federation-is-client-side"/>),
naming a node as a peer cannot turn it into a request forwarder. The
risk is on the client side, where the size, time, and request bounds of
<xref target="fetch-safety"/> and <xref target="following-peers"/> apply. A publisher <bcp14>SHOULD</bcp14> keep
a discovery document small: it describes a Bundle's artefacts, not its
items.</t>
      </section>
      <section anchor="content-is-data">
        <name>Content Is Data</name>
        <t>A client that passes retrieved prose to a language model, a shell, a
query engine, or any other interpreter <bcp14>MUST</bcp14> treat it as data: never
executed, never interpolated into a path, a URL, or a command string,
never resolved as an identifier, and never read as an instruction to
the client. Prose retrieved from another node carries the untrusted
label of <xref target="untrusted-content"/> to every place it is used.</t>
      </section>
      <section anchor="exposure">
        <name>Exposure</name>
        <t>A discovery document is public. A publisher <bcp14>MUST NOT</bcp14> name in it any
resource that is not intended to be public, and <bcp14>MUST NOT</bcp14> let the set of
links reveal the existence of resources it does not serve publicly. A
gated node still serves the discovery document publicly
(<xref target="cross-origin-access"/>), which discloses that the node exists.</t>
        <t>A gated node <bcp14>MUST</bcp14> omit the <tt>agsc-counts</tt>, <tt>agsc-bundle-hash</tt>,
<tt>agsc-bundle-version</tt>, <tt>agsc-chunk-count</tt> and <tt>agsc-chunk-set</tt>
attributes and the <tt>ledger</tt> link, and <bcp14>MUST</bcp14> omit every <tt>digest</tt> whose
target it does not serve without authentication: a digest over a gated
artefact lets anyone confirm a guess of its content, and the counts and
the content version disclose activity. It still carries
<tt>agsc-spec-version</tt> and <tt>agsc-generated-at</tt>, which say only that the
node exists and is current.</t>
        <t>The path <tt>/.well-known/</tt> on an origin <bcp14>MUST</bcp14> be under the publisher's
control (<xref target="RFC8615"/>, Section 4.1). On static hosting, the file is
produced by the publisher's build and upload path and by nothing else.</t>
      </section>
      <section anchor="tombstones">
        <name>Tombstones</name>
        <t>A node that stops publishing <bcp14>MUST</bcp14> keep serving a valid discovery
document whose anchor's <tt>describedby</tt> link carries the
<tt>agsc-tombstone</tt> attribute of <xref target="declaration-attributes"/>, <bcp14>MAY</bcp14> carry an
<tt>alternate</tt> link to a successor node's discovery document, and <bcp14>MAY</bcp14> omit
every other artefact link.</t>
        <t>A client <bcp14>MUST NOT</bcp14> treat a successor named that way as the same node. It
<bcp14>MUST</bcp14> establish the peer relation with the successor afresh before
following it, and everything it derives from the successor carries the
successor's own Bundle IRI as its origin (<xref target="untrusted-content"/>). A walk
(<xref target="following-peers"/>) does not descend into a tombstoned node.</t>
      </section>
    </section>
    <section anchor="privacy-considerations">
      <name>Privacy Considerations</name>
      <t>Serving a discovery document collects nothing, sets no cookie, carries
no identifier of a reader, and requires no request header field beyond
those of a simple cross-origin request (<xref target="cross-origin-access"/>). A
retrieval appears in the publisher's server logs like any other request
for a static file.</t>
      <t>The document may name an <tt>author</tt> link, and the artefacts it points at
may contain personal data chosen by the publisher. This document
requires no personal data anywhere in the discovery document. A
publisher <bcp14>SHOULD</bcp14> use a role rather than a personal contact where one
will do.</t>
      <t>A client <bcp14>SHOULD NOT</bcp14> send identifying header fields beyond those
<xref target="RFC9110"/> makes ordinary when fetching a discovery document, and a
client walking peers <bcp14>SHOULD NOT</bcp14> disclose to one node which other nodes
it has visited.</t>
    </section>
  </middle>
  <back>
    <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="FETCH" target="https://fetch.spec.whatwg.org/">
          <front>
            <title>Fetch Standard</title>
            <author>
              <organization>WHATWG</organization>
            </author>
            <date year="2026" month="November" day="14"/>
          </front>
          <seriesInfo name="WHATWG" value="Living Standard"/>
        </reference>
        <reference anchor="IANA-IPV4-SPECIAL" target="https://www.iana.org/assignments/iana-ipv4-special-registry/">
          <front>
            <title>IANA IPv4 Special-Purpose Address Registry</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="IANA-IPV6-SPECIAL" target="https://www.iana.org/assignments/iana-ipv6-special-registry/">
          <front>
            <title>IANA IPv6 Special-Purpose Address Registry</title>
            <author>
              <organization>IANA</organization>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="POWDER-DR" target="https://www.w3.org/TR/2009/REC-powder-dr-20090901/">
          <front>
            <title>Protocol for Web Description Resources (POWDER): Description Resources</title>
            <author initials="P." surname="Archer" fullname="Phil Archer">
              <organization/>
            </author>
            <author initials="K." surname="Smith" fullname="Kevin Smith">
              <organization/>
            </author>
            <author initials="A." surname="Perego" fullname="Andrea Perego">
              <organization/>
            </author>
            <date year="2009" month="September" day="01"/>
          </front>
          <seriesInfo name="W3C" value="Recommendation"/>
        </reference>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC3986" target="https://www.rfc-editor.org/info/rfc3986" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml">
          <front>
            <title>Uniform Resource Identifier (URI): Generic Syntax</title>
            <author fullname="T. Berners-Lee" initials="T." surname="Berners-Lee"/>
            <author fullname="R. Fielding" initials="R." surname="Fielding"/>
            <author fullname="L. Masinter" initials="L." surname="Masinter"/>
            <date month="January" year="2005"/>
          </front>
          <seriesInfo name="STD" value="66"/>
          <seriesInfo name="RFC" value="3986"/>
          <seriesInfo name="DOI" value="10.17487/RFC3986"/>
        </reference>
        <reference anchor="RFC6906" target="https://www.rfc-editor.org/info/rfc6906" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6906.xml">
          <front>
            <title>The 'profile' Link Relation Type</title>
            <author fullname="E. Wilde" initials="E." surname="Wilde"/>
            <date month="March" year="2013"/>
          </front>
          <seriesInfo name="RFC" value="6906"/>
          <seriesInfo name="DOI" value="10.17487/RFC6906"/>
        </reference>
        <reference anchor="RFC7284" target="https://www.rfc-editor.org/info/rfc7284" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7284.xml">
          <front>
            <title>The Profile URI Registry</title>
            <author fullname="M. Lanthaler" initials="M." surname="Lanthaler"/>
            <date month="June" year="2014"/>
          </front>
          <seriesInfo name="RFC" value="7284"/>
          <seriesInfo name="DOI" value="10.17487/RFC7284"/>
        </reference>
        <reference anchor="RFC7493" target="https://www.rfc-editor.org/info/rfc7493" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7493.xml">
          <front>
            <title>The I-JSON Message Format</title>
            <author fullname="T. Bray" initials="T." role="editor" surname="Bray"/>
            <date month="March" year="2015"/>
          </front>
          <seriesInfo name="RFC" value="7493"/>
          <seriesInfo name="DOI" value="10.17487/RFC7493"/>
        </reference>
        <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <date month="May" year="2017"/>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>
        <reference anchor="RFC8288" target="https://www.rfc-editor.org/info/rfc8288" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8288.xml">
          <front>
            <title>Web Linking</title>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <date month="October" year="2017"/>
          </front>
          <seriesInfo name="RFC" value="8288"/>
          <seriesInfo name="DOI" value="10.17487/RFC8288"/>
        </reference>
        <reference anchor="RFC8615" target="https://www.rfc-editor.org/info/rfc8615" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8615.xml">
          <front>
            <title>Well-Known Uniform Resource Identifiers (URIs)</title>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <date month="May" year="2019"/>
          </front>
          <seriesInfo name="RFC" value="8615"/>
          <seriesInfo name="DOI" value="10.17487/RFC8615"/>
        </reference>
        <reference anchor="RFC8785" target="https://www.rfc-editor.org/info/rfc8785" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8785.xml">
          <front>
            <title>JSON Canonicalization Scheme (JCS)</title>
            <author fullname="A. Rundgren" initials="A." surname="Rundgren"/>
            <author fullname="B. Jordan" initials="B." surname="Jordan"/>
            <author fullname="S. Erdtman" initials="S." surname="Erdtman"/>
            <date month="June" year="2020"/>
          </front>
          <seriesInfo name="RFC" value="8785"/>
          <seriesInfo name="DOI" value="10.17487/RFC8785"/>
        </reference>
        <reference anchor="RFC9110" target="https://www.rfc-editor.org/info/rfc9110" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9110.xml">
          <front>
            <title>HTTP Semantics</title>
            <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/>
            <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/>
            <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/>
            <date month="June" year="2022"/>
          </front>
          <seriesInfo name="STD" value="97"/>
          <seriesInfo name="RFC" value="9110"/>
          <seriesInfo name="DOI" value="10.17487/RFC9110"/>
        </reference>
        <reference anchor="RFC9111" target="https://www.rfc-editor.org/info/rfc9111" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9111.xml">
          <front>
            <title>HTTP Caching</title>
            <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/>
            <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/>
            <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/>
            <date month="June" year="2022"/>
          </front>
          <seriesInfo name="STD" value="98"/>
          <seriesInfo name="RFC" value="9111"/>
          <seriesInfo name="DOI" value="10.17487/RFC9111"/>
        </reference>
        <reference anchor="RFC9264" target="https://www.rfc-editor.org/info/rfc9264" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9264.xml">
          <front>
            <title>Linkset: Media Types and a Link Relation Type for Link Sets</title>
            <author fullname="E. Wilde" initials="E." surname="Wilde"/>
            <author fullname="H. Van de Sompel" initials="H." surname="Van de Sompel"/>
            <date month="July" year="2022"/>
          </front>
          <seriesInfo name="RFC" value="9264"/>
          <seriesInfo name="DOI" value="10.17487/RFC9264"/>
        </reference>
        <reference anchor="RFC9530" target="https://www.rfc-editor.org/info/rfc9530" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9530.xml">
          <front>
            <title>Digest Fields</title>
            <author fullname="R. Polli" initials="R." surname="Polli"/>
            <author fullname="L. Pardue" initials="L." surname="Pardue"/>
            <date month="February" year="2024"/>
          </front>
          <seriesInfo name="RFC" value="9530"/>
          <seriesInfo name="DOI" value="10.17487/RFC9530"/>
        </reference>
        <reference anchor="RFC9651" target="https://www.rfc-editor.org/info/rfc9651" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9651.xml">
          <front>
            <title>Structured Field Values for HTTP</title>
            <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
            <author fullname="P-H. Kamp" surname="P-H. Kamp"/>
            <date month="September" year="2024"/>
          </front>
          <seriesInfo name="RFC" value="9651"/>
          <seriesInfo name="DOI" value="10.17487/RFC9651"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="A2A" target="https://a2a-protocol.org/latest/specification/">
          <front>
            <title>Agent2Agent (A2A) Protocol Specification, version 1.0</title>
            <author>
              <organization>Agentic AI Foundation</organization>
            </author>
            <date year="2026" month="May" day="28"/>
          </front>
        </reference>
        <reference anchor="AGENTPROTO-CHARTER" target="https://datatracker.ietf.org/doc/charter-ietf-agentproto/">
          <front>
            <title>Agent Communication Protocols (agentproto) -- working group charter</title>
            <author>
              <organization>IETF</organization>
            </author>
            <date year="2026" month="October" day="08"/>
          </front>
        </reference>
        <reference anchor="AGSC-SPEC" target="https://agenticsystemcore.com/specs/">
          <front>
            <title>AgenticSystemCore Specification, version 1.1.0</title>
            <author initials="A. N." surname="Besleaga" fullname="Andrei N. Besleaga">
              <organization/>
            </author>
            <date year="2026" month="November" day="13"/>
          </front>
          <seriesInfo name="DOI" value="10.5281/zenodo.23233817"/>
        </reference>
        <reference anchor="AIMEM-CG" target="https://www.w3.org/community/ai-agent-memory-interop/">
          <front>
            <title>AI Agent Memory Interoperability Community Group</title>
            <author>
              <organization>W3C</organization>
            </author>
            <date>n.d.</date>
          </front>
        </reference>
        <reference anchor="DAWN-CHARTER" target="https://datatracker.ietf.org/doc/charter-ietf-dawn/">
          <front>
            <title>Discovery of Agents With Names (dawn) -- working group charter</title>
            <author>
              <organization>IETF</organization>
            </author>
            <date year="2026" month="October" day="22"/>
          </front>
        </reference>
        <reference anchor="DCAT3" target="https://www.w3.org/TR/vocab-dcat-3/">
          <front>
            <title>Data Catalog Vocabulary (DCAT) -- Version 3</title>
            <author>
              <organization>W3C Dataset Exchange Working Group</organization>
            </author>
            <date year="2024" month="August" day="22"/>
          </front>
          <seriesInfo name="W3C" value="Recommendation"/>
        </reference>
        <reference anchor="I-D.aiendpoint-ai-discovery" target="https://datatracker.ietf.org/doc/html/draft-aiendpoint-ai-discovery-01">
          <front>
            <title>The AI Discovery Endpoint: A Structured Mechanism for AI Agent Service Discovery and Capability Exposure</title>
            <author>
              <organization>AIEndpoint</organization>
            </author>
            <date year="2026" month="July" day="28"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-aiendpoint-ai-discovery-01"/>
        </reference>
        <reference anchor="I-D.arsentev-llm-context-discovery" target="https://datatracker.ietf.org/doc/html/draft-arsentev-llm-context-discovery-01" xml:base="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.arsentev-llm-context-discovery.xml">
          <front>
            <title>Discovery and Retrieval of Publisher-Curated Context Files for Large Language Model Consumers</title>
            <author fullname="Evgenii Arsentev" initials="E." surname="Arsentev">
              <organization>Independent</organization>
            </author>
            <date day="5" month="October" year="2026"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-arsentev-llm-context-discovery-01"/>
        </reference>
        <reference anchor="I-D.car-ai-txt-wellknown" target="https://datatracker.ietf.org/doc/html/draft-car-ai-txt-wellknown-00">
          <front>
            <title>AI.TXT: A Declaration File for AI Usage Preferences, Licensing, and Policy</title>
            <author initials="K." surname="Cardillo" fullname="Kayla Cardillo">
              <organization/>
            </author>
            <date year="2026" month="June" day="12"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-car-ai-txt-wellknown-00"/>
        </reference>
        <reference anchor="I-D.ietf-aipref-attach" target="https://datatracker.ietf.org/doc/html/draft-ietf-aipref-attach-05" xml:base="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-aipref-attach.xml">
          <front>
            <title>Associating AI Usage Preferences with Content in HTTP</title>
            <author fullname="Gary Illyes" initials="G." surname="Illyes">
              <organization>Google</organization>
            </author>
            <author fullname="Martin Thomson" initials="M." surname="Thomson">
              <organization>Mozilla</organization>
            </author>
            <date day="18" month="August" year="2026"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-aipref-attach-05"/>
        </reference>
        <reference anchor="I-D.ietf-aipref-vocab" target="https://datatracker.ietf.org/doc/html/draft-ietf-aipref-vocab-08" xml:base="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-aipref-vocab.xml">
          <front>
            <title>A Vocabulary For Expressing AI Usage Preferences</title>
            <author fullname="Paul Keller" initials="P." surname="Keller">
              <organization>Open Future</organization>
            </author>
            <author fullname="Martin Thomson" initials="M." surname="Thomson">
              <organization>Mozilla</organization>
            </author>
            <date day="13" month="September" year="2026"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-aipref-vocab-08"/>
        </reference>
        <reference anchor="I-D.ietf-webbotauth-httpsig-protocol" target="https://datatracker.ietf.org/doc/html/draft-ietf-webbotauth-httpsig-protocol-01" xml:base="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-webbotauth-httpsig-protocol.xml">
          <front>
            <title>HTTP Message Signatures for automated traffic</title>
            <author fullname="Thibault Meunier" initials="T." surname="Meunier">
              <organization>Cloudflare</organization>
            </author>
            <author fullname="Sandor Major" initials="S." surname="Major">
              <organization>Google</organization>
            </author>
            <date day="29" month="October" year="2026"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-ietf-webbotauth-httpsig-protocol-01"/>
        </reference>
        <reference anchor="I-D.jimenez-dawn-discovery-landscape" target="https://datatracker.ietf.org/doc/html/draft-jimenez-dawn-discovery-landscape-00">
          <front>
            <title>A Survey of AI Agent Discovery Mechanisms</title>
            <author initials="J." surname="Jimenez" fullname="Jaime Jimenez">
              <organization/>
            </author>
            <author initials="J." surname="Feng" fullname="Jim Feng">
              <organization/>
            </author>
            <author initials="J." surname="Arkko" fullname="Jari Arkko">
              <organization/>
            </author>
            <author initials="M." surname="Kuehlewind" fullname="Mirja Kuehlewind">
              <organization/>
            </author>
            <author initials="R." surname="Kandoi" fullname="Rajat Kandoi">
              <organization/>
            </author>
            <date year="2026" month="July" day="03"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-jimenez-dawn-discovery-landscape-00"/>
        </reference>
        <reference anchor="I-D.serra-mcp-discovery-uri" target="https://datatracker.ietf.org/doc/html/draft-serra-mcp-discovery-uri-04" xml:base="https://bib.ietf.org/public/rfc/bibxml3/reference.I-D.serra-mcp-discovery-uri.xml">
          <front>
            <title>The "mcp" URI Scheme and MCP Server Discovery Mechanism</title>
            <author fullname="marco serra" initials="M." surname="serra">
              <organization>Mumble Group</organization>
            </author>
            <date day="26" month="March" year="2026"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-serra-mcp-discovery-uri-04"/>
        </reference>
        <reference anchor="LLMSTXT" target="https://llmstxt.org/">
          <front>
            <title>The /llms.txt file, version 2</title>
            <author initials="J." surname="Howard" fullname="Jeremy Howard">
              <organization/>
            </author>
            <date year="2026" month="August" day="10"/>
          </front>
        </reference>
        <reference anchor="MCP" target="https://modelcontextprotocol.io/specification/2026-07-28">
          <front>
            <title>Model Context Protocol Specification, revision 2026-07-28</title>
            <author>
              <organization>Model Context Protocol, a Series of LF Projects, LLC</organization>
            </author>
            <date year="2026" month="July" day="28"/>
          </front>
        </reference>
        <reference anchor="OKF" target="https://github.com/GoogleCloudPlatform/open-knowledge-format">
          <front>
            <title>Open Knowledge Format, version 0.2</title>
            <author>
              <organization>Google Cloud</organization>
            </author>
            <date year="2026"/>
          </front>
        </reference>
        <reference anchor="RFC3987" target="https://www.rfc-editor.org/info/rfc3987" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3987.xml">
          <front>
            <title>Internationalized Resource Identifiers (IRIs)</title>
            <author fullname="M. Duerst" initials="M." surname="Duerst"/>
            <author fullname="M. Suignard" initials="M." surname="Suignard"/>
            <date month="January" year="2005"/>
          </front>
          <seriesInfo name="RFC" value="3987"/>
          <seriesInfo name="DOI" value="10.17487/RFC3987"/>
        </reference>
        <reference anchor="RFC6838" target="https://www.rfc-editor.org/info/rfc6838" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6838.xml">
          <front>
            <title>Media Type Specifications and Registration Procedures</title>
            <author fullname="N. Freed" initials="N." surname="Freed"/>
            <author fullname="J. Klensin" initials="J." surname="Klensin"/>
            <author fullname="T. Hansen" initials="T." surname="Hansen"/>
            <date month="January" year="2013"/>
          </front>
          <seriesInfo name="BCP" value="13"/>
          <seriesInfo name="RFC" value="6838"/>
          <seriesInfo name="DOI" value="10.17487/RFC6838"/>
        </reference>
        <reference anchor="RFC6892" target="https://www.rfc-editor.org/info/rfc6892" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6892.xml">
          <front>
            <title>The 'describes' Link Relation Type</title>
            <author fullname="E. Wilde" initials="E." surname="Wilde"/>
            <date month="March" year="2013"/>
          </front>
          <seriesInfo name="RFC" value="6892"/>
          <seriesInfo name="DOI" value="10.17487/RFC6892"/>
        </reference>
        <reference anchor="RFC7942" target="https://www.rfc-editor.org/info/rfc7942" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7942.xml">
          <front>
            <title>Improving Awareness of Running Code: The Implementation Status Section</title>
            <author fullname="Y. Sheffer" initials="Y." surname="Sheffer"/>
            <author fullname="A. Farrel" initials="A." surname="Farrel"/>
            <date month="July" year="2016"/>
          </front>
          <seriesInfo name="BCP" value="205"/>
          <seriesInfo name="RFC" value="7942"/>
          <seriesInfo name="DOI" value="10.17487/RFC7942"/>
        </reference>
        <reference anchor="RFC8259" target="https://www.rfc-editor.org/info/rfc8259" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8259.xml">
          <front>
            <title>The JavaScript Object Notation (JSON) Data Interchange Format</title>
            <author fullname="T. Bray" initials="T." role="editor" surname="Bray"/>
            <date month="December" year="2017"/>
          </front>
          <seriesInfo name="STD" value="90"/>
          <seriesInfo name="RFC" value="8259"/>
          <seriesInfo name="DOI" value="10.17487/RFC8259"/>
        </reference>
        <reference anchor="RFC8574" target="https://www.rfc-editor.org/info/rfc8574" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8574.xml">
          <front>
            <title>cite-as: A Link Relation to Convey a Preferred URI for Referencing</title>
            <author fullname="H. Van de Sompel" initials="H." surname="Van de Sompel"/>
            <author fullname="M. Nelson" initials="M." surname="Nelson"/>
            <author fullname="G. Bilder" initials="G." surname="Bilder"/>
            <author fullname="J. Kunze" initials="J." surname="Kunze"/>
            <author fullname="S. Warner" initials="S." surname="Warner"/>
            <date month="April" year="2019"/>
          </front>
          <seriesInfo name="RFC" value="8574"/>
          <seriesInfo name="DOI" value="10.17487/RFC8574"/>
        </reference>
        <reference anchor="RFC8792" target="https://www.rfc-editor.org/info/rfc8792" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8792.xml">
          <front>
            <title>Handling Long Lines in Content of Internet-Drafts and RFCs</title>
            <author fullname="K. Watsen" initials="K." surname="Watsen"/>
            <author fullname="E. Auerswald" initials="E." surname="Auerswald"/>
            <author fullname="A. Farrel" initials="A." surname="Farrel"/>
            <author fullname="Q. Wu" initials="Q." surname="Wu"/>
            <date month="June" year="2020"/>
          </front>
          <seriesInfo name="RFC" value="8792"/>
          <seriesInfo name="DOI" value="10.17487/RFC8792"/>
        </reference>
        <reference anchor="RFC9309" target="https://www.rfc-editor.org/info/rfc9309" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9309.xml">
          <front>
            <title>Robots Exclusion Protocol</title>
            <author fullname="M. Koster" initials="M." surname="Koster"/>
            <author fullname="G. Illyes" initials="G." surname="Illyes"/>
            <author fullname="H. Zeller" initials="H." surname="Zeller"/>
            <author fullname="L. Sassman" initials="L." surname="Sassman"/>
            <date month="September" year="2022"/>
          </front>
          <seriesInfo name="RFC" value="9309"/>
          <seriesInfo name="DOI" value="10.17487/RFC9309"/>
        </reference>
        <reference anchor="RFC9421" target="https://www.rfc-editor.org/info/rfc9421" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9421.xml">
          <front>
            <title>HTTP Message Signatures</title>
            <author fullname="A. Backman" initials="A." role="editor" surname="Backman"/>
            <author fullname="J. Richer" initials="J." role="editor" surname="Richer"/>
            <author fullname="M. Sporny" initials="M." surname="Sporny"/>
            <date month="February" year="2024"/>
          </front>
          <seriesInfo name="RFC" value="9421"/>
          <seriesInfo name="DOI" value="10.17487/RFC9421"/>
        </reference>
        <reference anchor="RFC9727" target="https://www.rfc-editor.org/info/rfc9727" xml:base="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9727.xml">
          <front>
            <title>api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs</title>
            <author fullname="K. Smith" initials="K." surname="Smith"/>
            <date month="June" year="2025"/>
          </front>
          <seriesInfo name="RFC" value="9727"/>
          <seriesInfo name="DOI" value="10.17487/RFC9727"/>
        </reference>
        <reference anchor="VOID" target="https://www.w3.org/TR/void/">
          <front>
            <title>Describing Linked Datasets with the VoID Vocabulary</title>
            <author>
              <organization>W3C Semantic Web Interest Group</organization>
            </author>
            <date year="2011" month="March" day="03"/>
          </front>
          <seriesInfo name="W3C" value="Interest Group Note"/>
        </reference>
      </references>

<section anchor="a-complete-example">
      <name>A Complete Example</name>
      <t>A complete discovery document for <tt>https://example.org/</tt> in the full
form is shown below, pretty-printed. Its canonical bytes
(<xref target="top-level-structure"/>) order the members by name, have no whitespace
between tokens, and end with one line feed. The <tt>type</tt> value
<tt>application/jsonl</tt>, used for the ledger and the chunk export, is not a
registered media type; a client does not depend on <tt>type</tt>
(<xref target="target-attributes"/>).</t>
      <figure>
        <name>A complete discovery document</name>
        <sourcecode type="json"><![CDATA[
NOTE: '\' line wrapping per RFC 8792

{
  "linkset": [
    {
      "anchor": "https://example.org/",
      "alternate": [
        {
          "href": "https://example.org/llms-full.txt",
          "type": "text/plain",
          "digest": [
            "sha-256=:Nfm1AxNikrZAb82mhnWgjpi3i8rGJa9K64wnI0ZiJY0=:"
          ]
        },
        {
          "href": "https://example.org/llms.txt",
          "type": "text/plain",
          "digest": [
            "sha-256=:QjxPZtSHNKLvYtiXXCOwnjJn+fYmfqkRYmash8n7+O0=:"
          ]
        }
      ],
      "author": [
        {
          "href": "https://example.org/about/",
          "type": "text/html"
        }
      ],
      "describedby": [
        {
          "href": "https://example.org/graph.jsonld",
          "type": "application/ld+json",
          "agsc-bundle-hash": [
            "sha-256=:/WQyaCbIwaeGFFMAFw/eMonm8tK+F7amphaKNT4BpB0=:"
          ],
          "agsc-bundle-version": ["v1.4.0"],
          "agsc-counts": [
            "clusters=6", "concepts=142", "episodes=17", "gates=4",
            "lessons=39", "procedures=28"
          ],
          "agsc-generated-at": ["2026-10-09T08:15:00Z"],
          "agsc-spec-version": ["1.1.0"],
          "digest": [
            "sha-256=:JeigkAtOPS9f9BzKym+X6J2O4awt53GEua1AhIAiLfE=:"
          ]
        }
      ],
      "license": [
        {
          "href": "https://example.org/legal/",
          "type": "text/html"
        }
      ],
      "service-doc": [
        {
          "href": "https://example.org/specs/",
          "type": "text/html"
        }
      ],
      "https://w3id.org/agentic-system-core/rel#context": [
        {
          "href": "https://example.org/ns/context.jsonld",
          "type": "application/ld+json",
          "digest": [
            "sha-256=:Dv8ogyqhEZ0jxdWQj0FkVfpXbuTnyfvWEFNwtbRTSEA=:"
          ]
        }
      ],
      "https://w3id.org/agentic-system-core/rel#graph": [
        {
          "href": "https://example.org/graph.nq",
          "type": "application/n-quads",
          "digest": [
            "sha-256=:/WQyaCbIwaeGFFMAFw/eMonm8tK+F7amphaKNT4BpB0=:"
          ]
        },
        {
          "href": "https://example.org/graph.ttl",
          "type": "text/turtle",
          "digest": [
            "sha-256=:SylBDgXPkysmlRZkx+BvHSxVTbm3ZWGzFXskHf+kH80=:"
          ]
        }
      ],
      "https://w3id.org/agentic-system-core/rel#ledger": [
        {
          "href": "https://example.org/ledger.jsonl",
          "type": "application/jsonl",
          "agsc-ledger-head": [
            "6acd55d78bf24c2b7866c0e46a3bb88a4b7259cea9ca0bfa6263\
81068b0d56ed"
          ],
          "agsc-ledger-length": ["48"],
          "digest": [
            "sha-256=:mIn5HVeWxmn0Ecmh5Qwkc3doL+0fdO+Z7HieEDozhz0=:"
          ]
        }
      ],
      "https://w3id.org/agentic-system-core/rel#now": [
        {
          "href": "https://example.org/now.md",
          "type": "text/markdown",
          "digest": [
            "sha-256=:cJvRMVgkkW5Usdn/z0q1iNxyBErb59kLWRv83qvpx8A=:"
          ]
        }
      ],
      "https://w3id.org/agentic-system-core/rel#ontology": [
        {
          "href": "https://example.org/ns/agsc.ttl",
          "type": "text/turtle",
          "digest": [
            "sha-256=:kjVLSaNilITtebImxe9J+ukr7UOdmTG+NAtppRjsrH8=:"
          ]
        }
      ],
      "https://w3id.org/agentic-system-core/rel#peer": [
        {
          "href": "https://b.example/.well-known/knowledge-linkset",
          "type": "application/linkset+json"
        }
      ],
      "https://w3id.org/agentic-system-core/rel#skills": [
        {
          "href": "https://example.org/skills/index.json",
          "type": "application/json",
          "digest": [
            "sha-256=:NnyPQz+rxvP/Zl9ja4+0xRSCpb7gdArcAVXlAG5IoU0=:"
          ]
        }
      ],
      "https://w3id.org/agentic-system-core/rel#surface": [
        {
          "href": "https://example.org/chunks.jsonl",
          "type": "application/jsonl",
          "agsc-access": ["none"],
          "agsc-chunk-count": ["517"],
          "agsc-chunk-set": [
            "sha-256=:7EWtxSlfY5u7jm7lsHVF/l/5X1a73Ueu3kVJhavUdsU=:"
          ],
          "agsc-surface": ["chunks"],
          "digest": [
            "sha-256=:vAlDuXGRaRPyTeeRfLAFWa7acFyOL3Y7o+vbywRofDk=:"
          ]
        },
        {
          "href": "https://example.org/llms.txt",
          "type": "text/plain",
          "agsc-access": ["none"],
          "agsc-surface": ["llms-txt"]
        }
      ]
    }
  ]
}
]]></sourcecode>
      </figure>
      <t>The same node without a build engine serves the reduced form:</t>
      <figure>
        <name>The same document in the reduced form</name>
        <sourcecode type="json"><![CDATA[
{
  "linkset": [
    {
      "anchor": "https://example.org/",
      "alternate": [
        {
          "href": "https://example.org/llms.txt",
          "type": "text/plain"
        }
      ],
      "describedby": [
        {
          "href": "https://example.org/graph.jsonld",
          "type": "application/ld+json"
        }
      ],
      "license": [
        {
          "href": "https://example.org/legal/"
        }
      ]
    }
  ]
}
]]></sourcecode>
      </figure>
    </section>
    <section anchor="change-log">
      <name>Change Log</name>
      <ul empty="true">
        <li>
          <t>[Note to the RFC Editor: please remove this appendix before
publication.]</t>
        </li>
      </ul>
      <t>Since -00: the header is that of an ordinary individual
Internet-Draft; <xref target="AGSC-SPEC"/> cites the released version 1.0.0; the
profile URI is registered (<xref target="iana-profile-uri"/>); no well-known URI
registration is requested (<xref target="iana-considerations"/>,
<xref target="carriage-and-resolution"/>); <xref target="I-D.arsentev-llm-context-discovery"/> is
cited at its current revision. Nothing on the wire changed.</t>
      <t>Since -01:</t>
      <t>A document valid under -01 is valid under -02. The path, the media
type, the profile URI and the extension relations are unchanged.</t>
      <ul spacing="compact">
        <li>
          <t><xref target="AGSC-SPEC"/> is version 1.1.0: the <tt>ledger</tt> link may carry
<tt>agsc-ledger-length</tt>; the <tt>chunks</tt> surface link carries <tt>digest</tt>,
<tt>agsc-chunk-count</tt> and <tt>agsc-chunk-set</tt>, which a gated node omits;
the <tt>access</tt> link carries <tt>agsc-access</tt>.</t>
        </li>
        <li>
          <t>Client rules match the specification: the anchor is on the retrieval
origin; an IPv6 address that embeds an IPv4 address is refused
whole; development mode admits loopback; every textual form of an
address is classified alike; the size bound applies after content
decoding; unknown declaration values have named defaults; recognizing
the profile does not depend on header access; an entity tag is not an
integrity statement.</t>
        </li>
        <li>
          <t>Stated exactly: the publisher-set entity tag, the line feed after
canonical bytes, the ledger head, the chunk set of a split export, and
the related-system links. <xref target="discovery-from-a-page"/> names the
<tt>linkset</tt> relation.</t>
        </li>
        <li>
          <t>References: <xref target="RFC7493"/> and <xref target="FETCH"/> added; <xref target="RFC9111"/> and the
IANA address registries normative; <tt>dawn</tt> and <tt>agentproto</tt> cited by
their charters.</t>
        </li>
        <li>
          <t>Condensed: requirements stated twice are stated once, four
subsections are merged into their neighbours, and IANA Considerations
precede Security Considerations.</t>
        </li>
      </ul>
    </section>
  </back>

</rfc>
