slug: stardog provider: Stardog generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Software & Technology min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 4 edges: - tag: Permissions spec_file: stardog-permissions-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.92 evidence: GET /admin/permissions/effective/user/{user} getEffectiveUserPermissions; PUT /admin/permissions/role/{role} addRolePermission; GET /admin/permissions/check checkUserPermission reason: Grants, revokes and checks permissions for users and roles with PERMISSION schemas — plainly authorisation/access administration, which is Identity & Access Management. - tag: Users spec_file: stardog-users-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.92 evidence: POST /admin/users addUser "Add user"; PUT /admin/users/{user}/pwd "Change user's password"; PUT /admin/users/{user}/roles setUserRoles; schemas USER_CREATE, SUPERUSER reason: Account creation, enable/disable, password change and role assignment are user identity and access administration, not HR employee records — Identity & Access Management. - tag: Roles spec_file: stardog-roles-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.9 evidence: POST /admin/roles addRole "Add role"; GET /admin/roles/{role}/users getUsersWithRole; ROLE_LIST_DETAILED, PERMISSION_WITH_EXPLICIT reason: Role creation/deletion and role-to-user assignment with associated permissions is role-based access control administration — Identity & Access Management. - tag: Integrity Constraints / SHACL spec_file: stardog-integrity-constraints-shacl-api-openapi.yml capability_id: BC-610.30 capability_id_l1: BC-610 capability_name: Data Quality Management confidence: 0.7 evidence: POST /{db}/icv/validate 'Validate constraints'; POST /{db}/icv/report 'SHACL validation report'; schema ICV_VALIDATION reason: Declaring integrity constraints and producing validation reports against stored data is data quality monitoring and remediation support. The SHACL validation report schema grounds this clearly, though it sits close to data governance as well.