Use Cases
From RDF Data Shapes Working Group
Contents
- 1 Status of this Document
- 2 Use Cases
- 2.1 UC1: Validate an RDF graph
- 2.2 UC2: Use shape definitions as descriptions of the shape of expected data
- 2.3 UC3: Define constraints for properties
- 2.4 UC4: Define constraints between different properties
- 2.5 UC4: Define nuanced error-conditions
- 2.6 UC5: Explicitely define scope of validation
- 2.7 UC6: Encapsulate complex shape definitions into reusable templates
- 2.8 UC7: Checking multiple constraints for a given resource
Status of this Document
Under Construction
Use Cases
UC1: Validate an RDF graph
overall UC for structural constraint validation of RDF graphs
UC2: Use shape definitions as descriptions of the shape of expected data
overall UC for scenarios using shapes to describe nature of exptected data
UC3: Define constraints for properties
general UC for restricting values of properties, includes sh:allowedValues, sh:datatype, sh:directValueType, sh:hasValue, sh:minCount, sh:maxCount, sh:nodeKind, sh:valueClass, sh:valueShape
UC4: Define constraints between different properties
e.g. begin date before end date
UC4: Define nuanced error-conditions
general UC for validation messages, includes different levels of severity, sh:message
UC5: Explicitely define scope of validation
Individual scopes (sh:nodeShape), Class-based Scopes (sh:scopeClass and rdf:type), General scopes (sh:scope)
UC6: Encapsulate complex shape definitions into reusable templates
general UC for templating mechanism, includes ConstraintTemplates, ScopeTemplates (+ Functions?)
UC7: Checking multiple constraints for a given resource
not,and,xor,or,closed
