Definition
Functional Requirements
Syntax
Semantics
Conformance Testing
Performance Assessment
Definition
PC Prompt (PGM-PCP): The structured prompt that Prompt Creation submits to Basic Knowledge to open the Model Context Protocol session. It carries the representation of the scene context, of the Intent of the User, of the resolved referents, of the constraints of the Goal and of the expressive configuration of the A-User and, when A-User Control so requires, the Action context that Basic Knowledge needs to produce Process Actions and Action Objects.
Functional Requirements
- Header: The Data shall have Header “PGM-PCP-V1.0”.
- 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 (PCPromptID, PCPromptTime).
- DialogID: The Data shall include identifier of the dialogue (the Model Context Protocol session) that the PC Prompt opens.
- Prompt: The Data shall include the prompt, in natural language.
- SceneContext: The Data may include the scene context, as given by the Context Descriptors.
- Intent: The Data may include the Intent of the User.
- Propositions: The Data may include propositions linking subjects, predicates and objects with their spatial and temporal context.
- ResolvedReferents: The Data may include referring expressions resolved to Entities of the scene.
- GoalConstraints: The Data may include constraints that the Goal imposes on the response.
- ExpressiveConfiguration: The Data may include the expressive configuration of the A-User.
- ActionContext: The Data may include the context that Basic Knowledge needs to produce Process Actions and Action Objects.
- Metadata: The Data shall include DataXMData and may include DescrMetadata.
Syntax
https://schemas.mpai.community/PGM1/V1.0/data/PCPrompt.json
Semantics
Table 1 – Semantics of PC Prompt
| Label | Description |
| Header | Header of the Data Type, with the version. (required) |
| MInstance | Identifier of the M-Instance. (required) |
| UEnvironment | Identifier of the U-Environment. (required) |
| SessionID | Identifier of the A-User session. (required) |
| PCPromptID | Identifier of this instance. (required) |
| PCPromptTime | Time at which the Data was produced. (required) |
| DialogID | Identifier of the dialogue (the Model Context Protocol session) that the PC Prompt opens. (required) |
| Prompt | The prompt, in natural language. (required) |
| SceneContext | The scene context, as given by the Context Descriptors. |
| Intent | The Intent of the User. |
| Propositions | Propositions linking subjects, predicates and objects with their spatial and temporal context. |
| – Subject | Subject. (required) |
| – Predicate | Predicate. (required) |
| – Object | Object. |
| – Spatial | Spatial. |
| – Temporal | Temporal. |
| ResolvedReferents | Referring expressions resolved to Entities of the scene. |
| – Expression | Expression. (required) |
| – EntityID | Identifier of the Entity concerned. |
| – Confidence | Confidence, 0 to 1. |
| GoalConstraints | Constraints that the Goal imposes on the response. |
| 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. |
| DataXMData | Data Exchange Metadata of MPAI-PTF: provenance, authorisation, security and confidence of the Data. |
| DescrMetadata | Descriptive metadata (plain text, at most 2048 characters). |
Conformance Testing
Data conforms with PC Prompt if it validates against the schema of Section 3. 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.
