Definition
Functional Requirements
Syntax
Semantics
Conformance Testing
Performance Assessment
Definition
BKN-PRC (PGM-KPR): The Data Type exchanged between Basic Knowledge and Prompt Creation through the Model Context Protocol, during the dialogue that the PC Prompt opens. It has two modes, told apart by Mode: Request (RQ), sent by Basic Knowledge, that asks for additional context or a clarification, and Response (RS), sent by Prompt Creation, that returns a more complete or different representation of the understanding of the context. The exchanges of one dialogue are told apart by TurnIndex within the DialogID.
Functional Requirements
- Header: The Data shall have Header “PGM-KPR-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.
- 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).
- Correlation: A Response shall carry the identifier (RequestID) of the Request that it answers.
- Dialogue: The Data shall carry the DialogID of the dialogue (the Model Context Protocol session opened by the PC Prompt) and the TurnIndex of the exchange; a Response shall have the TurnIndex of its Request.
- Request: A Request shall state its Kind and may carry the question of Basic Knowledge and the Entities concerned.
- Response: A Response shall state the Outcome and may carry a more complete or different representation of the understanding of the context (text, Intent, Propositions, resolved referents, goal constraints, expressive configuration, Action context).
- Metadata: The Data shall include DataXMData and may include DescrMetadata.
Syntax
https://schemas.mpai.community/PGM1/V1.0/data/BKNPRC.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-PRC
| 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 |
| Kind | What Basic Knowledge asks for. One of: more_context, clarification, referents, intent, propositions, goal_constraints, action_context. |
| Question | The question of Basic Knowledge, in natural language. |
| EntityIDs | Identifiers of the Entities and Items 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. |
| Representation | A more complete or different representation of the understanding of the context, as appropriate to the Kind of the Request. |
| – Text | Text. |
| – Intent | Intent. |
| – Propositions | Propositions. |
| –– Subject | Subject. (required) |
| –– Predicate | Predicate. (required) |
| –– Object | Object. |
| –– Spatial | Spatial. |
| –– Temporal | Temporal. |
| – ResolvedReferents | Resolved Referents. |
| –– Expression | Expression. (required) |
| –– EntityID | Identifier of the Entity concerned. |
| –– Confidence | Confidence, 0 to 1. |
| – GoalConstraints | Request: whether the production of the constraints on the goal is required, optional or not_requested. Response: fulfilment of the production of the constraints on the goal (produced, partial, missing or not_requested). |
| – ExpressiveConfiguration | The expressive configuration of the A-User. |
| –– Personality | Personality. |
| –– Role | Role of the A-User to apply. |
| –– Locale | Locale to apply. |
| –– Constraints | Constraints, as strings. |
| – ActionContext | The context that Basic Knowledge needs to produce Process Actions and Action Objects. |
| –– Repertoire | The Process Actions that may be used. |
| –– Vocabularies | The vocabularies in which the actions of the Portable Avatar may be expressed (the identifiers named by the Qualifier of the Action Objects). |
| –– MaxSteps | Maximum number of Process Actions in the sequence. |
| –– MLocations | MLocations. |
| –– RightsRefs | Identifiers of the Rights that the A-User holds. |
| –– WalletLimit | Maximum amount that may be spent from the Wallet. |
| –– Rules | Rules of the M-Instance that apply. |
| –– Affordances | Affordances of the Space, obtained from Domain Access. |
Conformance Testing
Data conforms with BKN-PRC 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.
