Data Requirements

From SemWebQuality.org
(Difference between revisions)
Jump to: navigation, search
Line 4: Line 4:
 
!Example  
 
!Example  
 
![http://semwebquality.org/ontologies/dq-constraints# DQ-Constraint Lib] for [http://spinrdf.org SPIN]
 
![http://semwebquality.org/ontologies/dq-constraints# DQ-Constraint Lib] for [http://spinrdf.org SPIN]
 +
![http://purl.org/dqm-vocabulary/v1/dqm# DQM-Vocabulary
 
|-
 
|-
 
|'''Mandatory Property and Literal Rules'''  
 
|'''Mandatory Property and Literal Rules'''  
Line 10: Line 11:
 
|[[dqc:MissingElementConstraints]]
 
|[[dqc:MissingElementConstraints]]
 
[[dqc:FunctionalDependentEmptyValueAll]]
 
[[dqc:FunctionalDependentEmptyValueAll]]
 +
|[[dqm:MissingPropertyRule]]
 +
[[dqm:MissingValueRule]]
 
|-
 
|-
 
|'''Syntactic Rules '''  
 
|'''Syntactic Rules '''  
Line 15: Line 18:
 
|Literal values for the property foo:country-name must only contain letters.  
 
|Literal values for the property foo:country-name must only contain letters.  
 
|[[dqc:SyntaxConstraints]]
 
|[[dqc:SyntaxConstraints]]
 +
|[[dqm:SyntaxRule]]
 
|-
 
|-
 
|'''Functional Dependency Rules'''  
 
|'''Functional Dependency Rules'''  
Line 20: Line 24:
 
|The literal value for foo:city is always dependent to the literal value for foo:country, since certain city names only exist in certain countries.
 
|The literal value for foo:city is always dependent to the literal value for foo:country, since certain city names only exist in certain countries.
 
|[[dqc:FunctionalDependencyConstraints]]
 
|[[dqc:FunctionalDependencyConstraints]]
 +
|[[dqm:FuncDepValueRule]]
 +
[[dqm:FuncDepReferenceRule]]
 
|-
 
|-
 
|'''Legal Value Rules'''   
 
|'''Legal Value Rules'''   

Revision as of 20:40, 22 September 2011

Data Quality Rule Definition Example DQ-Constraint Lib for SPIN [http://purl.org/dqm-vocabulary/v1/dqm# DQM-Vocabulary
Mandatory Property and Literal Rules Properties and their literals become mandatory, if the data is required for the task at hand. The properties indicating the geographical coordinates must exist and have values for all instances of the class foo:Location to be able to navigate to each location. dqc:MissingElementConstraints

dqc:FunctionalDependentEmptyValueAll

dqm:MissingPropertyRule

dqm:MissingValueRule

Syntactic Rules Syntactic rules define the type of characters and/or the pattern of literal values. Literal values for the property foo:country-name must only contain letters. dqc:SyntaxConstraints dqm:SyntaxRule
Functional Dependency Rules Functional dependencies are dependencies between the values of two or more different properties. The literal value for foo:city is always dependent to the literal value for foo:country, since certain city names only exist in certain countries. dqc:FunctionalDependencyConstraints dqm:FuncDepValueRule

dqm:FuncDepReferenceRule

Legal Value Rules Legal value rules are the explicit definition of the allowed values for a certain property. The property foo:gender must only contain the values “male”, “female”, “m”, or “f”. dqc:LegalValueConstraints
Legal Value Range Rules Legal value range rules are the explicit definition of the allowed value range for properties holding numerical values. A value range contains an upper and/or lower limit. The property foo:population must only contain values greater than zero. dqc:ValueRangeConstraints
Illegal Value Rules Illegal value rules are the explicit definition of the values that may not be assigned to a certain property. The property foo:gender may never contain the value “mail”. dqc:LegalValueConstraints
Illegal Value Range Rules Illegal value range rules are the explicit definition of prohibited value ranges for properties holding numerical values. A value range contains an upper and/or lower limit. The property foo:population must not contain values less than one. dqc:ValueRangeConstraints
Unique Value Rules Unique value rules define properties that may contain each literal value not more than once within a defined collection of values. Each value for property foo:ISBN in instances of class foo:Book may not occur more than once. dqc:UniquenessConstraints
Outdated Value Rules Outdated value rules are rules that identify instances that represent an outdated state of the corresponding real world entity. Instances of the class foo:Offer are outdated, if its value for foo:validThrough is elder than the current date and time. Not covered yet
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox