<- Go to Data Types    Go to ToC

1. Definition 2. Functional Requirements 3. Syntax 4. Semantics

1 Definition

A Profile defines how subsets and usage modes of the PTF trust framework are configured for different purposes, including deployment, capability description, verification behaviour, and policy constraints.

2 Functional Requirements

A Profile shall:

  • Include a Header identifying the version of the Profile structure.
  • Include a ProfileID identifying the Profile.
  • Optionally include ProfileTime indicating when the Profile was defined or updated.
  • Include a ProfileType indicating which kind of Profile is defined.
  • For ProfileType = DeploymentProfile, include a DeploymentProfile definition.
  • For ProfileType = CapabilityProfile, include a CapabilityProfile definition.
  • For ProfileType = VerificationProfile, include a VerificationProfile definition.
  • For ProfileType = PolicyProfile, include a PolicyProfile definition.
  • Optionally include DataXMData and DescrMetadata.
  • Use only the keys defined in this Data Type.

3 Syntax

https://schemas.mpai.community/PTF/V1.0/data/Profile.json

4 Semantics

Label Description
Header Profile Header — Standard “PTF-PRF-V”.
ProfileID Identifier of the Profile.
ProfileTime Time at which the Profile was defined or last updated.
ProfileType Type of Profile (“DeploymentProfile”, “CapabilityProfile”, “VerificationProfile”, “PolicyProfile”).
DeploymentProfile Deployment profile definition.
– Name Human‑readable name of the deployment profile.
– Description Description of the deployment environment and intended use.
– RequiredIdentities Required identity structures.
– RequiredCredentials Required credential types.
– RequiredEvidence Required evidence types.
– RequiredAlgorithms Required or allowed algorithms.
  – SignatureAlgorithms Required or allowed signature algorithms.
  – HashAlgorithms Required or allowed hash algorithms.
– RequiredPolicies Required policy bindings or identifiers.
– FreshnessRequirements Requirements on evidence freshness.
CapabilityProfile Capability profile definition.
– Name Human‑readable name of the capability profile.
– Description Description of supported PTF capabilities.
– SupportedIdentities Supported identity structures.
– SupportedCredentials Supported credential types.
– SupportedEvidence Supported evidence types.
– SupportedAlgorithms Supported algorithms.
  – SignatureAlgorithms Supported signature algorithms.
  -HashAlgorithms Supported hash algorithms.
– SupportedPolicies Supported policy identifiers or classes.
– SupportedComponents Supported PTF components or roles.
VerificationProfile Verification profile definition.
– Name Human‑readable name of the verification profile.
– Description Description of verification behaviour and guarantees.
– RequiredChecks Required verification checks.
– RequiredEvidenceValidation Required validation steps for evidence.
– RequiredPolicyEvaluation Required policy evaluation steps or rules.
– FreshnessChecks Requirements on checking evidence freshness.
PolicyProfile Policy profile definition.
– Name Human‑readable name of the policy profile.
– Description Description of policy constraints and trust model.
– RequiredTrustAnchors Required or allowed trust anchors.
– RequiredAlgorithms Required or allowed algorithms.
PolicyProfile  – SignatureAlgorithms Required or allowed signature algorithms.
  – HashAlgorithms Required or allowed hash algorithms.
– RequiredEvidence Required evidence types.
– RequiredAttributes Required peer instance attributes.
  – InstanceType Required instance type, if any.
  – Implementation Required implementation or vendor identifier, if any.
  – InstanceClass Required logical or functional class, if any.
– RequiredPolicies Required policy identifiers or classes.
DataXMData Metadata that the Process/AIM exchanges with other Process/AIM.
DescrMetadata Descriptive metadata (max length 2048).

<- Go to Data Types    Go to ToC