DBpedia Datatypes - Revision history

VladimirAlexiev: /* XML Schema Datatypes */

2015-01-20T10:16:13Z

XML Schema Datatypes

← Older revision		Revision as of 12:16, 20 January 2015
Line 13:		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 32:		Line 33:
	* [[Datatype:xsd:string]]		* [[Datatype:xsd:string]]
	* [[Datatype:xsd:time]]		* [[Datatype:xsd:time]]

	= [[Datatype:Area\|Area]] =		= [[Datatype:Area\|Area]] =
	* [[Datatype:squareNauticalMile]]		* [[Datatype:squareNauticalMile]]

VladimirAlexiev at 11:01, 19 January 2015

2015-01-19T11:01:27Z

← Older revision		Revision as of 13:01, 19 January 2015
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]]:
	<pre>{{PropertyMapping \| templateProperty = altura \| ontologyProperty = height \| unit = Length }}		<pre>{{PropertyMapping \| templateProperty = altura \| ontologyProperty = height \| unit = Length }}
	</pre>		</pre>
	* 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]:		* 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>{{PropertyMapping \| templateProperty = length_ft \| ontologyProperty = length \| unit = foot}}
	</pre>		</pre>

VladimirAlexiev at 11:00, 19 January 2015

2015-01-19T11:00:35Z

← Older revision		Revision as of 13:00, 19 January 2015
Line 3:		Line 3:
	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 }}
			</pre>
	* 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]:		* 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}}		<pre>{{PropertyMapping \| templateProperty = length_ft \| ontologyProperty = length \| unit = foot}}
			</pre>

	In both cases:		In both cases:

VladimirAlexiev at 11:00, 19 January 2015

2015-01-19T11:00:00Z

← Older revision		Revision as of 13:00, 19 January 2015
Line 3:		Line 3:
	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 }}		{{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]:		* 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}}		{{PropertyMapping \| templateProperty = length_ft \| ontologyProperty = length \| unit = foot}}

	In both cases:		In both cases:

VladimirAlexiev at 10:59, 19 January 2015

2015-01-19T10:59:30Z

← Older revision		Revision as of 12:59, 19 January 2015
Line 1:		Line 1:
	DBpedia defines datatypes for units and dimensions. The ~~following~~ datatypes ~~are available~~:		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 [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]:
			{{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:
			* The number is converted to SI units (eg meters for Length)
			* 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 Schema Datatypes =

VladimirAlexiev: /* Power */

2015-01-19T10:43:39Z

Power

← Older revision		Revision as of 12:43, 19 January 2015
Line 296:		Line 296:
	* [[Datatype:peoplePerSquareKilometer]]: '''duplicate, should be deleted'''		* [[Datatype:peoplePerSquareKilometer]]: '''duplicate, should be deleted'''
	= [[Datatype:Power\|Power]] =		= [[Datatype:Power\|Power]] =
	* [[Datatype:brakeHorsepower]]		* [[Datatype:brakeHorsepower]], see [https://en.wikipedia.org/wiki/Horsepower#Brake_horsepower en.wikipedia]. This is like horsepower but of an engine stripped from auxiliary components, so as to maximize the measurement.
	* [[Datatype:pferdestaerke]]		* [[Datatype:pferdestaerke]], see [https://de.wikipedia.org/wiki/Pferdestärke de.wikipedia]. '''I think should be merged with horsepower'''
	* [[Datatype:horsepower]]		* [[Datatype:horsepower]], see [https://en.wikipedia.org/wiki/Horsepower en.wikipedia]
	* [[Datatype:gigawatt]]		* [[Datatype:gigawatt]]
	* [[Datatype:megawatt]]		* [[Datatype:megawatt]]
Line 304:		Line 304:
	* [[Datatype:kilowatt]]		* [[Datatype:kilowatt]]
	* [[Datatype:watt]]		* [[Datatype:watt]]

	= [[Datatype:ElectricCurrent\|ElectricCurrent]] =		= [[Datatype:ElectricCurrent\|ElectricCurrent]] =
	* [[Datatype:ampere]]		* [[Datatype:ampere]]

VladimirAlexiev at 15:24, 13 January 2015

2015-01-13T15:24:15Z

Show changes

VladimirAlexiev at 15:20, 13 January 2015

2015-01-13T15:20:21Z

Show changes

VladimirAlexiev at 15:11, 13 January 2015

2015-01-13T15:11:19Z

Show changes

JosephineReuer: Undo revision 14678 by JosephineReuer (Talk)

2011-07-29T15:31:24Z

Undo revision 14678 by JosephineReuer (Talk)

← Older revision		Revision as of 17:31, 29 July 2011
Line 1:		Line 1:
	DBpedia defines datatypes for units and dimensions. The following datatypes are available:		DBpedia defines datatypes for units and dimensions. The following datatypes are available:

	* [[Datatype:Acceleration]]
	** [[Datatype:metrePerSecondSquared]]
	* [[Datatype:Area]]		* [[Datatype:Area]]
	** [[Datatype:squareNauticalMile]]		** [[Datatype:squareNauticalMile]]