Template:PropertyMapping: Difference between revisions

From DBpedia Mappings
Jump to navigationJump to search
No edit summary
No edit summary
Line 10: Line 10:
{{#if:{{{unit|}}}|<tr>
{{#if:{{{unit|}}}|<tr>
<td>unit</td><td>[[Datatype:{{{unit}}}|{{{unit}}}]]</td>
<td>unit</td><td>[[Datatype:{{{unit}}}|{{{unit}}}]]</td>
</tr>}}
{{#if:{{{factor|}}}|<tr>
<td>factor</td><td>[[Datatype:{{{factor}}}|{{{factor}}}]]</td>
</tr>}}
</tr>}}
</table></includeonly>
</table></includeonly>
Line 21: Line 24:
| ontologyProperty =
| ontologyProperty =
| unit =
| unit =
| factor =
}}
}}
</pre>
</pre>
Line 29: Line 33:
* '''ontologyProperty''': A template property to ontology property mapping should list one ontology property.
* '''ontologyProperty''': A template property to ontology property mapping should list one ontology property.
* '''unit''': If a template property containing a numerical value and a unit is mapped, the unit has to be defined (Please use only values from [http://mappings.dbpedia.org/index.php/DBpedia_Datatypes DBpedia unit and dimensions]). If a template property has no default unit defined, e.g. its values can contain different units of the same dimension, the dimension has to be defined for usability as well as validation reasons. Possible dimensions are Length or Mass.
* '''unit''': If a template property containing a numerical value and a unit is mapped, the unit has to be defined (Please use only values from [http://mappings.dbpedia.org/index.php/DBpedia_Datatypes DBpedia unit and dimensions]). If a template property has no default unit defined, e.g. its values can contain different units of the same dimension, the dimension has to be defined for usability as well as validation reasons. Possible dimensions are Length or Mass.
* '''factor''': Multiplication factor that is applied for numeral data.


=== Example ===
=== Example ===
Line 38: Line 43:
| templateProperty = birth_date  
| templateProperty = birth_date  
| ontologyProperty = birthDate  
| ontologyProperty = birthDate  
}}
</pre>
The property mapping from the template property birth_date to the ontology property birthDate:
<pre>
{{PropertyMapping
| templateProperty = visitors_mio
| ontologyProperty = visitors
| factor = 1000000
}}
}}
</pre>
</pre>
</noinclude>
</noinclude>

Revision as of 15:35, 14 July 2011

{{PropertyMapping}} maps template properties to ontology properties.

Usage

{{PropertyMapping 
| templateProperty =
| ontologyProperty =
| unit =
| factor =
}}

Meanings

  • templateProperty: A template property to ontology property mapping should list one template property which is to be mapped.
  • ontologyProperty: A template property to ontology property mapping should list one ontology property.
  • unit: If a template property containing a numerical value and a unit is mapped, the unit has to be defined (Please use only values from DBpedia unit and dimensions). If a template property has no default unit defined, e.g. its values can contain different units of the same dimension, the dimension has to be defined for usability as well as validation reasons. Possible dimensions are Length or Mass.
  • factor: Multiplication factor that is applied for numeral data.

Example

The property mapping from the template property birth_date to the ontology property birthDate:

{{PropertyMapping 
| templateProperty = birth_date 
| ontologyProperty = birthDate 
}}

The property mapping from the template property birth_date to the ontology property birthDate:

{{PropertyMapping 
| templateProperty = visitors_mio
| ontologyProperty = visitors
| factor = 1000000
}}