Data Requirements
From SemWebQuality.org
(Difference between revisions)
| Line 12: | Line 12: | ||
|- | |- | ||
|'''Syntactic Rules ''' | |'''Syntactic Rules ''' | ||
| − | |Syntactic rules define the type of | + | |Syntactic rules define the type of characters and/or the pattern of literal values. |
| − | characters and/or the pattern of literal | + | |Literal values for the property foo:country-name must only contain letters. |
| − | values. | + | |
| − | |Literal values for the property | + | |
| − | foo:country-name must only | + | |
| − | contain letters. | + | |
|[[dqc:SyntaxConstraints]] | |[[dqc:SyntaxConstraints]] | ||
|- | |- | ||
|'''Functional Dependency Rules''' | |'''Functional Dependency Rules''' | ||
| − | |Functional dependencies are | + | |Functional dependencies are dependencies between the values of two or more different properties. |
| − | dependencies between the values of two | + | |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. |
| − | 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]] | |[[dqc:FunctionalDependencyConstraints]] | ||
|- | |- | ||
|'''Legal Value Rules''' | |'''Legal Value Rules''' | ||
| − | |Legal value rules are the explicit | + | |Legal value rules are the explicit definition of the allowed values for a certain property. |
| − | definition of the allowed values for a | + | |The property foo:gender must only contain the values “male”, “female”, “m”, or “f”. |
| − | certain property. | + | |
| − | |The property foo:gender must only | + | |
| − | contain the values “male”, “female”, | + | |
| − | “m”, or “f”. | + | |
|[[dqc:LegalValueConstraints]] | |[[dqc:LegalValueConstraints]] | ||
|- | |- | ||
|'''Legal Value Range Rules''' | |'''Legal Value Range Rules''' | ||
| − | |Legal value range 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 value range for | + | |The property foo:population must only contain values greater than zero. |
| − | 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]] | |[[dqc:ValueRangeConstraints]] | ||
|- | |- | ||
|'''Illegal Value Rules''' | |'''Illegal Value Rules''' | ||
| − | |Illegal value 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 values that may not be | + | |The property foo:gender may never contain the value “mail”. |
| − | assigned to a certain property. | + | |
| − | |The property foo:gender may never | + | |
| − | contain the value “mail”. | + | |
|[[dqc:LegalValueConstraints]] | |[[dqc:LegalValueConstraints]] | ||
|- | |- | ||
|'''Illegal Value Range Rules''' | |'''Illegal Value Range Rules''' | ||
| − | |Illegal value range 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 prohibited value ranges for | + | |The property foo:population must not contain values less than one. |
| − | 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]] | |[[dqc:ValueRangeConstraints]] | ||
|- | |- | ||
|'''Unique Value Rules''' | |'''Unique Value Rules''' | ||
| − | |Unique value rules define properties that | + | |Unique value rules define properties that may contain each literal value not more than once within a defined collection of values. |
| − | may contain each literal value not more | + | |Each value for property foo:ISBN in instances of class foo:Book may not occur more than once. |
| − | 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]] | |[[dqc:UniquenessConstraints]] | ||
|- | |- | ||
|'''Outdated Value Rules''' | |'''Outdated Value Rules''' | ||
| − | |Outdated value rules are rules that | + | |Outdated value rules are rules that identify instances that represent an outdated state of the corresponding real world entity. |
| − | identify instances that represent an | + | |Instances of the class foo:Offer are outdated, if its value for foo:validThrough is elder than the current date and time. |
| − | 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 | |Not covered yet | ||
|} | |} | ||
Revision as of 19:07, 9 August 2011
| Data Quality Rule | Definition | Example | DQ-Constraint Lib for SPIN |
|---|---|---|---|
| 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 |
| 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 |
| 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 |
| 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 |
