specs/vta/memory/delete/v0_3/payload
library
Typedefs
-
Ext
= Map<String, dynamic>
-
Vendor-namespaced extension object per SPEC.md §4.5.1. Each immediate key MUST be a
reverse-DNS namespace; structure under each namespace is opaque to the framework.
-
MemoryKey
= String
-
Agent-chosen identifier for an item within a context. Opaque to the maintainer: it
MUST NOT be parsed, normalized, or case-folded, and prefix matching in
vta/memory/list is a byte-prefix comparison over the UTF-8 encoding. Agents
SHOULD use /-delimited hierarchical keys (contact/billing,
preference/timezone) so that prefix can address a family of items, but the
delimiter is a convention between an agent and itself. A key is content as well as
an address: a key naming a person, a condition or a dispute discloses something to
anyone who can list the context, even without its value.
-
MemoryPurpose
= Purpose
-
The one purpose for which the caller will use the memory content a request
discloses (VTI-ACL-103): a name registered in the VTI specification's purpose
registry (
personalisation, taskExecution, analytics, modelTraining) or an
absolute IRI. The VTA grants it only if the caller's ACL entry does — any grants
every purpose but modelTraining — refuses it otherwise (purposeNotGranted), and
records it in the audit record of the read. Optional where the entry lists exactly
one purpose (that one applies) or states any (the read is recorded as for no
stated purpose).
-
MemoryVersion
= int
-
A value of the context's monotonic write counter (see this schema's description).
Server-assigned; a producer never chooses one.
-
Purpose
= String
-
What content is used for: a lowerCamelCase name registered in the VTI
specification's purpose registry (Appendix H) —
personalisation, taskExecution,
analytics, modelTraining at the time of writing — or an absolute IRI naming a
purpose defined elsewhere, such as a purpose of the W3C Data Privacy Vocabulary
(https://w3id.org/dpv#ServicePersonalisation). Compared by exact string equality:
a consumer MUST NOT treat a purpose it does not recognise as equal to any other,
and grants only a request naming exactly a listed purpose (VTI-ACL-109). A
registered name is never an IRI, because it contains no :.