This specification defines the Qualia SHACL Extension Vocabulary, a set of SHACL (Shapes Constraint Language) extensions for validating configuration parameters across the Qualia Protocol Ecosystem. These extensions provide constraints for client features, specialized libraries, core modalities, and infrastructure components, ensuring data integrity, security, and regulatory compliance across distributed semantic graph operations.

This document is an editor's draft and does not carry the endorsement of any standards body. It is intended for review and feedback within the Qualia Protocol Ecosystem community.

Introduction

SHACL (Shapes Constraint Language) is a W3C recommendation for validating RDF graphs against shapes. The Qualia Protocol Ecosystem extends SHACL with domain-specific constraints for scientific computing, financial modeling, medical data processing, and quantum computing operations.

A conforming implementation MUST:

• Support all required constraint types defined in this specification
• Generate appropriate SlgOpcode sequences for constraint validation
• Support the three severity levels: Violation, Warning, and Info
• Provide opcode generation functions for all constraint types

The following terms are used in this specification:

Constraint Type

A SHACL shape definition that validates specific configuration parameters

SlgOpcode

A low-level operation code for the SLG (Semantic Logic Graph) Virtual Machine

Severity Level

The classification of constraint violations: Violation (critical), Warning (non-critical), Info (informational)

Opcode Generation

The process of converting high-level SHACL constraints into executable SlgOpcode sequences

Client Feature Constraints

Client feature constraints validate parameters for the Qualia Client application including logging, system tray, and settings.

Specialized Library Constraints

Specialized library constraints validate parameters for scientific and engineering libraries including linear algebra, machine learning, physics simulation, chemistry modeling, medical computing, financial modeling, engineering analysis, statistical computing, cryptographic library, QPU bridge, and quantum biology.

Core Modality Constraints

Core modality constraints validate parameters for logical reasoning modalities including epistemic logic, paraconsistent logic, temporal LTL, spatio-temporal reasoning, graph theory, calculus, argumentation, dialectical logic, ASP, probabilistic reasoning, description logic, diffusion, linear logic, control feedback, and interval reasoning.

Computational Mathematics Constraints

The computational-mathematics engine — units & dimensional analysis, number theory, special functions, interpolation, integral transforms, vector calculus, arbitrary-precision exact arithmetic, the symbolic CAS, and general-dimension numerical methods — carries a SHACL q42:*ConfigurationShape per capability. Each shape bounds the capability's resource parameters (compiled to a bounded Vec<SlgOpcode> at config time, off the hot path) and restricts its operation set with sh:in. Namespace q42: <https://webizen.org/q42#>. The normative shapes are emitted by get_computational_maths_shacl_ttl() in crates/qualia-core-db/src/modalities/logic/computational_maths_shacl.rs (mirrors the in-browser computational engine — see the Computational Engine demo).

Infrastructure Constraints

Infrastructure constraints validate parameters for domain-specific engines, obfuscation, solvers, and geometric algebra.

Opcode Generation

All constraint types implement a to_opcodes() method that generates appropriate SlgOpcode sequences for validation in the SLG Virtual Machine.

impl ConstraintType {
    pub fn to_opcodes(&self) -> Vec<SlgOpcode> {
        vec![
            SlgOpcode::CheckMaxInclusive(self.max_value as f64),
            SlgOpcode::CheckMinInclusive(self.min_value as f64),
        ]
    }
}

Common opcode types include:

• CheckMaxInclusive - Validates upper bounds
• CheckMinInclusive - Validates lower bounds
• CheckHasValue - Validates enumeration membership
• CheckMaxLength - Validates string length limits
• CheckMinCount - Validates minimum occurrence requirements

Severity Levels

Constraints use three severity levels to classify validation failures:

Violation

Critical validation failure. Data is rejected and not processed. Used for security-critical validations, data integrity checks, and regulatory compliance requirements.

Warning

Non-critical issue. Data is accepted but a warning is logged. Used for configuration recommendations, deprecated features, and non-critical safety checks.

Info

Informational validation. No action required. Used for informational constraints and validation metadata.

Security Considerations

Implementation Considerations

References

• SHACL (Shapes Constraint Language): http://www.w3.org/ns/shacl
• W3C SHACL Recommendation: https://www.w3.org/TR/shacl/
• Qualia Protocol Ecosystem: https://webizen.org/
• QualiaDB Repository: https://github.com/qualia-network/qualiaDB

Acknowledgements

This specification was developed by the Qualia Protocol Ecosystem community with contributions from the QualiaDB development team.