Go to PGM-AUA V1.0 Data Types

Definition
Functional Requirements
Syntax
Semantics
Conformance Testing
Performance Assessment

Definition

BKN-USR (PGM-KUS): The Data Type exchanged between Basic Knowledge and User State Refinement through the Model Context Protocol. It has two modes, told apart by Mode: Request (RQ), sent by Basic Knowledge, that carries the deliberation feedback, and Response (RS), sent by User State Refinement, that returns the refined User State for the next deliberation cycle. The exchanges of one dialogue are told apart by TurnIndex within the DialogID.

Functional Requirements

  1. Header: The Data shall have Header “PGM-KUS-V1.0” and Mode equal to RQ for a Request and to RS for a Response; the properties that belong to the other mode shall not be present.
  2. Identification: The Data shall carry the identifiers of the M‑Instance, of the U‑Environment and of the session, and a unique identifier and a time (QueryID, QueryTime).
  3. Correlation: A Response shall carry the identifier (RequestID) of the Request that it answers.
  4. Dialogue: The Data shall carry the DialogID of the dialogue and the TurnIndex of the exchange; a Response shall have the TurnIndex of its Request.
  5. Request: A Request may carry the deliberation feedback of Basic Knowledge (its hypothesis, the evidence that conflicts with it and a question) and the User concerned.
  6. Response: A Response shall state the Outcome and may carry the refined User State for the next deliberation cycle, the engagement and the provenance of the refinement.
  7. Metadata: The Data shall include DataXMData and may include DescrMetadata.

Syntax

https://schemas.mpai.community/PGM1/V1.0/data/BKNUSR.json

Semantics

Table 1 gives the properties common to the two modes, Table 2 those of the Request and Table 3 those of the Response.

Table 1 – Properties common to the Request and the Response of BKN-USR

Label Description
Header Header of the Data Type, with the version. (required)
Mode RQ for a Request, RS for a Response. One of: RQ, RS. (required)
MInstance Identifier of the M-Instance. (required)
UEnvironment Identifier of the U-Environment. (required)
SessionID Identifier of the A-User session. (required)
QueryID Identifier of this Request or Response. (required)
QueryTime Time at which the Data was produced. (required)
DialogID Identifier of the dialogue (the Model Context Protocol session) to which the exchange belongs. (required)
TurnIndex Ordinal position of the exchange in the dialogue, starting from 0. A Response has the TurnIndex of its Request. (required)
DataXMData Data Exchange Metadata of MPAI-PTF: provenance, authorisation, security and confidence of the Data.
DescrMetadata Descriptive metadata (plain text, at most 2048 characters).

Table 2 – Properties of the Request (Mode RQ)

Label Description
Feedback The deliberation feedback of Basic Knowledge: what it assumes about the User, the evidence that conflicts with it, and what it asks.
– Hypothesis Hypothesis.
– Conflicts Conflicts.
– Question Question.
UserID Identifier of the User the Request concerns.

Table 3 – Properties of the Response (Mode RS)

Label Description
RequestID ID of the Request this Response answers.
Outcome The outcome. One of: answered, partially_answered, not_answered.
RefinedUserState The refined User State, for the next deliberation cycle.
Engagement The engagement of the User.
– Level Level, between 0 and 1.
– Mode RQ for a Request, RS for a Response.
Provenance The provenance of the refinement.

Conformance Testing

Data conforms with BKN-USR if it validates against the schema of Section 3 and, if the Mode is RQ, contains the properties required for a Request and none of those of a Response, and vice versa. If a schema contains references to other schemas, conformance of data for the primary schema implies that any data referencing a secondary schema shall also validate against the relevant schema.

Performance Assessment

Not part of this specification.

Go to PGM-AUA V1.0 Data Types