DBpedia Datatypes: Difference between revisions

From DBpedia Mappings
Jump to navigationJump to search
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 2: Line 2:


The page below shows a "hierarchy" of datatypes, although there's no such thing as subClassOf for datatypes (see [https://github.com/dbpedia/mappings-tracker/issues/22 #22]). In [[Template:PropertyMapping|PropertyMapping]].unit you can specify:
The page below shows a "hierarchy" of datatypes, although there's no such thing as subClassOf for datatypes (see [https://github.com/dbpedia/mappings-tracker/issues/22 #22]). In [[Template:PropertyMapping|PropertyMapping]].unit you can specify:
* Either a super-datatype, in which case the templateProperty is expected to have an explicit unit. Eg in [Mapping_pt:Info/Futebolista]:
* Either a super-datatype, in which case the templateProperty is expected to have an explicit unit. Eg in [[Mapping_pt:Info/Futebolista]]:
        {{PropertyMapping | templateProperty = altura | ontologyProperty = height | unit = Length }}
<pre>{{PropertyMapping | templateProperty = altura | ontologyProperty = height | unit = Length }}
* Or a specific datatype, in which case the templateProperty carries a pure number, which is interpreted as the provided unit. Eg in [Mapping_en:Infobox_street]:
</pre>
        {{PropertyMapping | templateProperty = length_ft | ontologyProperty = length | unit = foot}}
* Or a specific datatype, in which case the templateProperty carries a pure number, which is interpreted as the provided unit. Eg in [[Mapping_en:Infobox_street]]:
<pre>{{PropertyMapping | templateProperty = length_ft | ontologyProperty = length | unit = foot}}
</pre>


In both cases:
In both cases:
Line 11: Line 13:
* In some cases, a specific property with a more appropriate unit is also created. Eg http://dbpedia.org/ontology/Person/height is in centimeters
* In some cases, a specific property with a more appropriate unit is also created. Eg http://dbpedia.org/ontology/Person/height is in centimeters


= XML Schema Datatypes =
= XML and RDF Datatypes =
* [[Datatype:rdf:langString]]
* [[Datatype:xsd:anyURI]]
* [[Datatype:xsd:anyURI]]
* [[Datatype:xsd:boolean]]
* [[Datatype:xsd:boolean]]
Line 30: Line 33:
* [[Datatype:xsd:string]]
* [[Datatype:xsd:string]]
* [[Datatype:xsd:time]]
* [[Datatype:xsd:time]]
= [[Datatype:Area|Area]] =
= [[Datatype:Area|Area]] =
* [[Datatype:squareNauticalMile]]
* [[Datatype:squareNauticalMile]]

Latest revision as of 12:16, 20 January 2015

DBpedia defines datatypes for units and dimensions.

The page below shows a "hierarchy" of datatypes, although there's no such thing as subClassOf for datatypes (see #22). In PropertyMapping.unit you can specify:

{{PropertyMapping | templateProperty = altura | ontologyProperty = height | unit = Length }}
  • Or a specific datatype, in which case the templateProperty carries a pure number, which is interpreted as the provided unit. Eg in Mapping_en:Infobox_street:
{{PropertyMapping | templateProperty = length_ft | ontologyProperty = length | unit = foot}}

In both cases:

XML and RDF Datatypes

Area

Currency

Density

Energy

FlowRate

Force

FuelEfficiency

Frequency

InformationUnit

Length

LinearMassDensity

Mass

PopulationDensity

Power

ElectricCurrent

Voltage

Pressure

Speed

Temperature

Time

Torque

Volume

Other

Unknown

I think should be deleted