Mapping Guide - Revision history

Wladek92: obsolete url vladimiralexiev, similar solution

2022-03-14T21:47:53Z

obsolete url vladimiralexiev, similar solution

← Older revision		Revision as of 23:47, 14 March 2022
Line 64:		Line 64:
	DO NOT copy blindly.		DO NOT copy blindly.
	* Do not just copy and paste, but take a careful look at properties that are equal or similar to properties used in your infobox to map.		* Do not just copy and paste, but take a careful look at properties that are equal or similar to properties used in your infobox to map.
	* Your infobox may be different from the infobox of the mapping you're reusing. Read the documentation of your infobox. Especially check whether to map to OntologyProperties or DataProperties (see [~~http~~://~~vladimiralexiev.~~github.io/pres/20150209-dbpedia/dbpedia-problems-long.html#sec-3-2 Object/DataProp Dichotomy])		* Your infobox may be different from the infobox of the mapping you're reusing. Read the documentation of your infobox. Especially check whether to map to OntologyProperties or DataProperties (see [https://github.com/VladimirAlexiev/my/blob/master/pres/20150209-dbpedia/dbpedia-problems-long.html#sec-3-2 Object/DataProp Dichotomy])
	* Many mappings have various errors. Do not propagate the errors by copying uncritically. If you find (or even suspect) an error in the mapping you're reusing, [http://github.com/dbpedia/mappings-tracker/issues/new raise an issue]		* Many mappings have various errors. Do not propagate the errors by copying uncritically. If you find (or even suspect) an error in the mapping you're reusing, [http://github.com/dbpedia/mappings-tracker/issues/new raise an issue]

Wladek92: VladimirAlexiev url has changed, download the file, also available under github.com/gerardbdn/VladimirAlexiev.github.io/blo/master/pres/....

2022-03-14T21:39:35Z

VladimirAlexiev url has changed, download the file, also available under github.com/gerardbdn/VladimirAlexiev.github.io/blo/master/pres/....

← Older revision		Revision as of 23:39, 14 March 2022
Line 57:		Line 57:
	</pre>		</pre>

	See the presentation [~~http~~://~~vladimiralexiev.~~github.io/pres/20150209-dbpedia/add-mapping-long.html#sec-6 Adding a DBpedia Mapping] for more useful hints.		See the presentation [https://github.com/VladimirAlexiev/my/blob/master/pres/20150209-dbpedia/add-mapping-long.html#sec-6 Adding a DBpedia Mapping] for more useful hints.

	== Check for similar mappings ==		== Check for similar mappings ==

Wladek92: /* Comments */ typo

2022-02-28T16:56:02Z

Comments: typo

← Older revision		Revision as of 18:56, 28 February 2022
Line 111:		Line 111:
	The range of the property should be defined by considering the property values and the infobox definition. Some infobox properties hold different data types or patterns of values, because the infobox property is not clearly defined in the template documentation. Therefore, Wikipedia authors use that property as they want. That makes it difficult for us to define the property's range. If a range is defined in the infobox definition, generally stick to that range. I found infobox properties with a range defined, but as I checked the values, I had to discover that the property values mostly disagree with the defined range. In such a case, chose a range that covers the property values and leave a note in the property comment. If the infobox property has no range defined, you always have to look at the values. For example, you have to weigh up to chose between a strict [[Template:ObjectProperty\|object property]] with an ontology class as range or a [[Template:DatatypeProperty\|data type property]] with xsd:string as range. A string would catch more information, but a object property is the clearer definition. You can motivate your decision in the property comment.		The range of the property should be defined by considering the property values and the infobox definition. Some infobox properties hold different data types or patterns of values, because the infobox property is not clearly defined in the template documentation. Therefore, Wikipedia authors use that property as they want. That makes it difficult for us to define the property's range. If a range is defined in the infobox definition, generally stick to that range. I found infobox properties with a range defined, but as I checked the values, I had to discover that the property values mostly disagree with the defined range. In such a case, chose a range that covers the property values and leave a note in the property comment. If the infobox property has no range defined, you always have to look at the values. For example, you have to weigh up to chose between a strict [[Template:ObjectProperty\|object property]] with an ontology class as range or a [[Template:DatatypeProperty\|data type property]] with xsd:string as range. A string would catch more information, but a object property is the clearer definition. You can motivate your decision in the property comment.
	=== Comments ===		=== Comments ===
	'''YOU MUST''' add an English comment to the ontology property. And not just repeat the prop name, ~~butgive~~ some useful info on usage, and contrast to other similar props. If the template documentation has a definition of the property, use it as comment. A short description of the property or a definition of the property values is really helpful for other people, which have to decide whether this property can be used for their mapping.		'''YOU MUST''' add an English comment to the ontology property. And not just repeat the prop name, but give some useful info on usage, and contrast to other similar props. If the template documentation has a definition of the property, use it as comment. A short description of the property or a definition of the property values is really helpful for other people, which have to decide whether this property can be used for their mapping.

	The biggest complaint of your fellow ontology editors is that props are not documented. In the near bright future, new props and classes without comment will be ''deleted''.		The biggest complaint of your fellow ontology editors is that props are not documented. In the near bright future, new props and classes without comment will be ''deleted''.

VladimirAlexiev: /* Check for similar mappings */

2016-06-08T10:41:28Z

Check for similar mappings

@@ Line 39: / Line 39: @@
 === Read infobox template documentation ===
 Take the template documentation of the infobox that you want to map as your source for property definitions. It can be found at the Wikipedia page of the template. See at the template documentation of the [http://en.wikipedia.org/wiki/Template:Infobox_China_station Infobox China station] for instance. Of course, not all templates have a adequate documentation. So, if your infobox hasn't one, the following points become even more important.
 == Check for similar mappings ==

VladimirAlexiev: /* Merge redirected templates */

2015-08-14T12:28:14Z

Merge redirected templates

@@ Line 14: / Line 14: @@
 === Check redirects for your infobox ===
-If you have found an infobox that isn't mapped already, check whether the infobox is redirected to another. If it is so, check whether that infobox is already mapped. If it is not, '''only then''' create a mapping for the infobox to which is redirected, not for the one that redirects.
+If you have found an infobox that isn't mapped already, check whether the infobox is redirected to another. If it is, check whether that infobox is already mapped. If it is not, '''only then''' create a mapping for the target infobox, not for the redirected infobox.
 * If you don't, you will wonder as in [https://github.com/dbpedia/extraction-framework/issues/296 #296] Why Infobox_Geopolitical_organization (eg United_Nations) is mapped to Country?
 * Hopefully [https://github.com/dbpedia/mappings-tracker/issues/3 #3] "Statistics and Validator to check for redirected templates" will be done soon, to warn against problems like this
 === Read infobox template documentation ===

VladimirAlexiev at 20:37, 22 February 2015

2015-02-22T20:37:15Z

← Older revision		Revision as of 22:37, 22 February 2015
Line 1:		Line 1:
	Dear fellow Mappers,		Dear fellow Mappers,
	one benefit of the DBpedia ontology is to standardise and reduce the redundancy in properties used by entities. At the moment, the DBpedia ontology is starting to inflate with equal properties. The ontology is getting unclear and the benefits of standardisation get lost. For instance, there are the ontology properties: [[OntologyProperty:DateClosed\|dateClosed]], [[OntologyProperty:ClosingDate\|closingDate]], [[OntologyProperty:Closed\|closed]], [[OntologyProperty:DateOfAbandonment\|dateOfAbandonment]] and [[OntologyProperty:Dissolved\|dissolved]]. All these properties describe the same or at least nearly the same. For example a closure of a firm, closing a road, decommissioning of facilities, or an abandonment of a project.		one benefit of the DBpedia ontology is to standardise and reduce the redundancy in properties used by entities. At the moment, the DBpedia ontology is starting to inflate with equal properties. The ontology is getting unclear and the benefits of standardisation get lost. For instance, there are the ontology properties: [[OntologyProperty:DateClosed\|dateClosed]], [[OntologyProperty:ClosingDate\|closingDate]], [[OntologyProperty:Closed\|closed]], [[OntologyProperty:DateOfAbandonment\|dateOfAbandonment]] and [[OntologyProperty:Dissolved\|dissolved]]. All these properties describe the same or at least nearly the same. For example a closure of a firm, closing a road, decommissioning of facilities, or an abandonment of a project.
	It seems that there is a need for a short guide how to write mappings and take care of the usefulness of the ontology. The basic introductions for writting mappings ~~could be found~~ [[How_to_edit_DBpedia_Mappings~~\|here~~]].		It seems that there is a need for a short guide how to write mappings and take care of the usefulness of the ontology. The basic introductions for writting mappings are at [[How_to_edit_DBpedia_Mappings]].

	== General instructions ==		== General instructions ==
Line 10:		Line 10:
	Generally, if you found unclear or doubled ontology properties, do not hesitate to create a discussion page for this property and note your questions or objections about this property. Help us to keep the ontology clean and useful.		Generally, if you found unclear or doubled ontology properties, do not hesitate to create a discussion page for this property and note your questions or objections about this property. Help us to keep the ontology clean and useful.

	== Check the mapping statistics ==		=== Check the mapping statistics ===
	If you ask yourself "Where do I start mapping?", please check the [[Mapping_Statistics\|Mapping Statistics]]. They give you a good idea of where new mappings would make the biggest impact.		If you ask yourself "Where do I start mapping?", please check the [[Mapping_Statistics\|Mapping Statistics]]. They give you a good idea of where new mappings would make the biggest impact.

	== Check redirects for your infobox ==		=== Check redirects for your infobox ===
	If you have found an infobox that isn't mapped already, check whether the infobox is redirected to another. If it is so, check whether that infobox is already mapped. If it is not, create a mapping for the infobox to which is redirected, not for the one that redirects to ~~another~~.		If you have found an infobox that isn't mapped already, check whether the infobox is redirected to another. If it is so, check whether that infobox is already mapped. If it is not, '''only then''' create a mapping for the infobox to which is redirected, not for the one that redirects.
			* If you don't, you will wonder as in [https://github.com/dbpedia/extraction-framework/issues/296 #296] Why Infobox_Geopolitical_organization (eg United_Nations) is mapped to Country?
			* Hopefully [https://github.com/dbpedia/mappings-tracker/issues/3 #3] "Statistics and Validator to check for redirected templates" will be done soon, to warn against problems like this

	== Read infobox template documentation ==		=== Read infobox template documentation ===
	Take the template documentation of the infobox that you want to map as your source for property definitions. It can be found at the Wikipedia page of the template. See at the template documentation of the [http://en.wikipedia.org/wiki/Template:Infobox_China_station Infobox China station] for instance. Of course, not all templates have a adequate documentation. So, if your infobox hasn't one, the following points become even more important.		Take the template documentation of the infobox that you want to map as your source for property definitions. It can be found at the Wikipedia page of the template. See at the template documentation of the [http://en.wikipedia.org/wiki/Template:Infobox_China_station Infobox China station] for instance. Of course, not all templates have a adequate documentation. So, if your infobox hasn't one, the following points become even more important.

VladimirAlexiev: /* Naming conventions */

2015-02-22T20:32:45Z

Naming conventions

← Older revision		Revision as of 22:32, 22 February 2015
Line 51:		Line 51:
	== Create new ontology properties ==		== Create new ontology properties ==
	If you have an infobox property that definitely can not be mapped to an existing ontology property, you can [[Ontology_Editing#How_to_add_an_ontology_property\|create a new one]]. But please stick to some simple rules:		If you have an infobox property that definitely can not be mapped to an existing ontology property, you can [[Ontology_Editing#How_to_add_an_ontology_property\|create a new one]]. But please stick to some simple rules:
	=== Naming ~~conventions~~ ===		=== Naming Conventions ===
	The name of the new property should not just copied from the infobox. Better take a look at the template documentation and the property definition if there is one. If not, take a look at a few Wikipedia articles that uses the infobox you want to map, or revert to the SPARQL Query above, and check how the property is used. If the property is used for numbers, ~~it should be considered for the name of the new ontology property by adding a~~ prefix ~~like~~ "numberOf", ~~or if~~ the property is used for dates, ~~the term~~ "date" should be part of the new ~~ontology property~~ name~~. Generally~~, ~~the property name should be build from more than one word.~~		Generally, the property name is build from more than one word.
			* All props must use lowerCaseCamelCase names, while classes use UpperCaseCamelCase.
			** Casing is especially important when you use a prop (in rdfs:subPropertyOf) or class (in rdfs:domain, rdfs:range).
			** See what happens to those who're not careful:
			dbo:bronzeMedalist rdfs:subPropertyOf dbo:Medalist .
			* Use full US English words, this helps your fellow editors with searching. "eyeColor" & "hairColor" are ok, "colour" is not ok
			* The name of the new property should not just copied from the infobox
			** Garbage prop names like "appmag_v, dist_ly, names, size_v, Dist ly, Names, Dist pc, Credit, Dec, Ra" won't be tolerated. ¡No pasarán! ([https://github.com/dbpedia/mappings-tracker/issues/7 #7])
			** Better take a look at the template documentation and the property definition if there is one.
			** If not, take a look at a few Wikipedia articles that uses the infobox you want to map, or revert to the SPARQL Query above, and check how the property is used.
			* Specific data
			** If the property is used for numbers, use prefix "numberOf" or suffix "Number" (unfortunately whether to use prefix or suffix, is not yet standardized)
			** If the property is used for dates, "date" should be part of the new prop name, or use suffix "*AsOf"

	=== Domain ===		=== Domain ===
	Take care by defining a domain and a range of properties. Do not just define them as owl:Thing only because it is simple. If your property is especially for an [[Template:Class\|ontology class]], do not hesitate to define this class as domain. That will prevent people to reuse this property for other classes by mistake, especially if the property name is not unambiguous.		Take care by defining a domain and a range of properties. Do not just define them as owl:Thing only because it is simple. If your property is especially for an [[Template:Class\|ontology class]], do not hesitate to define this class as domain. That will prevent people to reuse this property for other classes by mistake, especially if the property name is not unambiguous.

VladimirAlexiev: /* Comments */

2015-02-22T20:21:08Z

Comments

← Older revision		Revision as of 22:21, 22 February 2015
Line 71:		Line 71:
	Bad examples of missing comments:		Bad examples of missing comments:
	* What's [[OntologyProperty:member]] vs [[OntologyProperty:membership]]?		* What's [[OntologyProperty:member]] vs [[OntologyProperty:membership]]?
	* When to use [[OntologyProperty:teamMember] vs [[OntologyProperty:currentTeamMember]] vs [[OntologyProperty:sportsTeamMember]]]?		* When to use [[OntologyProperty:teamMember]] vs [[OntologyProperty:currentTeamMember]] vs [[OntologyProperty:sportsTeamMember]]]?
	* What's [[OntologyProperty:event]]? We need to '''investigate''' to find out that it should be replaced by [[OntologyProperty:sportDiscipline]] ([https://github.com/dbpedia/mappings-tracker/issues/12 #12]). Not good!		* What's [[OntologyProperty:event]]? We need to '''investigate''' to find out that it should be replaced by [[OntologyProperty:sportDiscipline]] ([https://github.com/dbpedia/mappings-tracker/issues/12 #12]). Not good!

VladimirAlexiev: /* Validate the infobox mapping */

2015-02-22T20:20:48Z

Validate the infobox mapping

← Older revision		Revision as of 22:20, 22 February 2015
Line 77:		Line 77:
	Validate your mapping. Use the "Test this mapping"-link at the mapping page. Especially, check properties that you have created yourself.		Validate your mapping. Use the "Test this mapping"-link at the mapping page. Especially, check properties that you have created yourself.

	~~Go to the Discussion tab and add~~ a few example Wikipedia articles that use the infobox you just mapped as ~~*~~test cases~~*~~		Add a few example Wikipedia articles that use the infobox you just mapped as '''test cases'''
	* [http://mappings.dbpedia.org/server/extraction/en/] (Adjust the language tag in the end of the URL)		* Go to http://mappings.dbpedia.org/server/extraction/en/ (Adjust the language tag in the end of the URL)
			* Put the final test link(s) into the Discussion tab under heading "Testing"
	* Read more at [[Main_Page#Testing_Best_Practices]]		* Read more at [[Main_Page#Testing_Best_Practices]]

VladimirAlexiev: /* Comments */

2015-02-22T20:19:15Z

Comments

← Older revision		Revision as of 22:19, 22 February 2015
Line 63:		Line 63:

	Some examples for good comments:		Some examples for good comments:
	* [[OntologyProperty:isHandicappedAccessible]]		* [[OntologyProperty:sportDiscipline]]: the sport discipline the athlete practices, e.g. Diving, or that a board member of a sporting club is focussing at
	* [[OntologyProperty:effectiveRadiatedPower]]		* [[OntologyProperty:zodiacSign]]: Applies to persons, planets, etc
	* [[OntologyProperty:~~zodiacSign~~]]		* [[OntologyProperty:bustWaistHipSize]]: Use this property if all 3 sizes are given together (DBpedia cannot currently extract 3 Lengths out of a field). Otherwise use separate fields bustSize, waistSize, hipSize
	* [[OntologyProperty:~~bustWaistHipSize~~]]		* [[OntologyProperty:isHandicappedAccessible]]: True if the station is handicapped accessible.
			* [[OntologyProperty:effectiveRadiatedPower]]: In radio telecommunications, effective radiated power or equivalent radiated power (ERP) is a standardized theoretical measurement of radio frequency (RF) energy using the SI unit watts (http://en.wikipedia.org/wiki/Effective_radiated_power)

			Bad examples of missing comments:
			* What's [[OntologyProperty:member]] vs [[OntologyProperty:membership]]?
			* When to use [[OntologyProperty:teamMember] vs [[OntologyProperty:currentTeamMember]] vs [[OntologyProperty:sportsTeamMember]]]?
			* What's [[OntologyProperty:event]]? We need to '''investigate''' to find out that it should be replaced by [[OntologyProperty:sportDiscipline]] ([https://github.com/dbpedia/mappings-tracker/issues/12 #12]). Not good!

	== Validate the infobox mapping ==		== Validate the infobox mapping ==