Data Requirements

From SemWebQuality.org
(Difference between revisions)
Jump to: navigation, search
 
(21 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{|border="1"
+
'''<span style="color:red">This site is currently under construction!</span>'''
 +
 
 +
A data requirement is a prescribed directive or consensual agreement that defines the content and/or structure that constitute high quality data instances and values. The following table contains different types of data requirements that can be expressed via the [http://semwebquality.org/ontologies/dq-constraints# DQ-Constraint Library] or the [http://purl.org/dqm-vocabulary/v1/dqm# DQM-Vocabulary].
 +
 
 +
 
 +
{|class="wikitable sortable"
 +
|+ Types of Data Requirements
 +
|-
 
!Data Quality Rule   
 
!Data Quality Rule   
 
!Definition   
 
!Definition   
 
!Example  
 
!Example  
!DQ-Constraint
+
![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'''
 +
|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:PropertyCompletenessRule]]
 +
[[dqm:ConditionalPropertyCompletenessRule]]
 
|-
 
|-
|Mandatory Property and Literal Rules  
+
|'''Syntactic Rules '''
|Properties and their literals become
+
|Syntactic rules define the type of characters and/or the pattern of literal values.
mandatory, if the data is required for the
+
|Literal values for the property foo:country-name must only contain letters.  
task at hand.  
+
|[[dqc:SyntaxConstraints]]
|The properties indicating the
+
|[[dqm:SyntaxRule]]
geographical coordinates must exist
+
[[dqm:ConditionalSyntaxRule]]
and have values for all instances of the  
+
class foo:Location to be able to
+
navigate to each location.  
+
 
|-
 
|-
|Syntactic Rules
+
|'''Functional Dependency Rules'''
|Syntactic rules define the type of  
+
|Functional dependencies are dependencies between the values of two or more different properties.  
characters and/or the pattern of literal
+
|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.
values.
+
|[[dqc:FunctionalDependencyConstraints]]
|Literal values for the property
+
|[[dqm:FuncDepValueRule]]
foo:country-name must only  
+
[[dqm:FuncDepReferenceRule]]
contain letters.  
+
[[dqm:CustomRequirement]]
 
|-
 
|-
|Functional Dependency Rules  
+
|'''Legal Value Rules''' 
|Functional dependencies are  
+
|Legal value rules are the explicit definition of the allowed values for a certain property.  
dependencies between the values of two
+
|The property foo:gender must only contain the values “male”, “female”, “m”, or “f”.
or more different properties.  
+
|[[dqc:LegalValueConstraints]]
|The literal value for foo:city is
+
|[[dqm:LegalValueRule]]
always dependent to the literal value
+
for foo:country, since certain city
+
names only exist in certain countries.
+
 
|-
 
|-
|Legal Value Rules
+
|'''Legal Value Range Rules'''
|Legal value rules are the explicit  
+
|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.  
definition of the allowed values for a
+
|The property foo:population must only contain values greater than zero.
certain property.  
+
|[[dqc:ValueRangeConstraints]]
|The property foo:gender must only  
+
|[[dqm:LegalValueRangeRule]]
contain the values “male”, “female”,
+
“m”, or “f”.  
+
 
|-
 
|-
|Legal Value Range Rules  
+
|'''Illegal Value Rules''' 
|Legal value range rules are the explicit  
+
|Illegal value rules are the explicit definition of the values that may not be assigned to a certain property.  
definition of the allowed value range for
+
|The property foo:gender may never contain the value “mail”.
properties holding numerical values. A
+
|[[dqc:LegalValueConstraints]]
value range contains an upper and/or
+
|[[dqm:IllegalValueRule]]
lower limit.  
+
|The property foo:population
+
must only contain values greater than
+
zero.
+
 
|-
 
|-
|Illegal Value Rules
+
|'''Illegal Value Range Rules'''
|Illegal value rules are the explicit  
+
|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.  
definition of the values that may not be
+
|The property foo:population must not contain values less than one.
assigned to a certain property.  
+
|[[dqc:ValueRangeConstraints]]
|The property foo:gender may never
+
|[[dqm:IllegalValueRangeRule]]
contain the value “mail”.  
+
 
|-
 
|-
|Illegal Value Range Rules  
+
|'''Unique Value Rules'''
|Illegal value range rules are the explicit
+
|Unique value rules define properties that may contain each literal value not more than once within a defined collection of values.  
definition of prohibited value ranges for
+
|Each value for property foo:ISBN in instances of class foo:Book may not occur more than once.  
properties holding numerical values. A
+
|[[dqc:UniquenessConstraints]]
value range contains an upper and/or
+
|[[dqm:UniqueValueRule]]
lower limit.  
+
|The property foo:population
+
must not contain values less than one.  
+
 
|-
 
|-
|Unique Value Rules
+
|'''Outdated Value Rules'''
|Unique value rules define properties that  
+
|Outdated value rules are rules that identify instances that represent an outdated state of the corresponding real world entity.  
may contain each literal value not more
+
|Instances of the class foo:Offer are outdated, if its value for foo:validThrough is elder than the current date and time.
than once within a defined collection of  
+
|Not covered yet
values.  
+
|[[dqm:UpdateRule]]
|Each value for property foo:ISBN in
+
[[dqm:ExpiryRule]]
instances of class foo:Book may not
+
occur more than once. 
+
 
|-
 
|-
|Outdated Value Rules
+
|'''Duplicate Instance Rules'''
|Outdated value rules are rules that
+
|
identify instances that represent an
+
|
outdated state of the corresponding real
+
|Not covered yet
world entity.
+
|[[dqm:DuplicateInstanceRule]]
|Instances of the class foo:Offer are
+
outdated, if its value for foo:validThrough is elder than
+
the current date and time.
+
 
|}
 
|}

Latest revision as of 20:46, 10 October 2011

This site is currently under construction!

A data requirement is a prescribed directive or consensual agreement that defines the content and/or structure that constitute high quality data instances and values. The following table contains different types of data requirements that can be expressed via the DQ-Constraint Library or the DQM-Vocabulary.


Types of Data Requirements
Data Quality Rule Definition Example DQ-Constraint Lib for SPIN 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:PropertyCompletenessRule

dqm:ConditionalPropertyCompletenessRule

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

dqm:ConditionalSyntaxRule

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 dqm:CustomRequirement

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 dqm:LegalValueRule
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 dqm:LegalValueRangeRule
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 dqm:IllegalValueRule
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 dqm:IllegalValueRangeRule
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 dqm:UniqueValueRule
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 dqm:UpdateRule

dqm:ExpiryRule

Duplicate Instance Rules Not covered yet dqm:DuplicateInstanceRule
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox