Writing Mappings/Tables: Difference between revisions
From DBpedia Mappings
Jump to navigationJump to search
(Created page with 'The full [http://dbpedia.svn.sourceforge.net/viewvc/dbpedia/trunk/extraction/doc/mapping%20language/DBpedia%20Mapping%20Language.docx documentation] on writing mappings can be fo...') |
No edit summary |
||
| Line 1: | Line 1: | ||
The full [http://dbpedia.svn.sourceforge.net/viewvc/dbpedia/trunk/extraction/doc/mapping%20language/DBpedia%20Mapping%20Language.docx documentation] on writing mappings can be found via the DBpedia SVN Repository. | The full [http://dbpedia.svn.sourceforge.net/viewvc/dbpedia/trunk/extraction/doc/mapping%20language/DBpedia%20Mapping%20Language.docx documentation] on writing mappings can be found via the DBpedia SVN Repository. | ||
Table mappings can be added [[ | Table mappings can be added [[Mapping:Table/Automobile|here]]. | ||
If a table mapping is defined, all rows of the table are mapped to instances of an ontology class, all of its columns are be mapped to ontology properties. | If a table mapping is defined, all rows of the table are mapped to instances of an ontology class, all of its columns are be mapped to ontology properties. | ||
Revision as of 17:36, 3 March 2010
The full documentation on writing mappings can be found via the DBpedia SVN Repository.
Table mappings can be added here.
If a table mapping is defined, all rows of the table are mapped to instances of an ontology class, all of its columns are be mapped to ontology properties. A table mapping applies to a table if a set of keywords occurs in the table header.
The DBpediaTableMapping template offers the following template parameters:
- mapToClass
- Table rows are mapped to ontology classes. The template parameter mapToClass allows one DBpedia ontology class as a value.
- correspondingClass, correspondingProperty
- If an instance of type correspondingClass is found in the same section as the table, it will be connected to the instances extracted from the table rows by correspondingProperty.
- keywords
- Keywords define mandatory table column headers or parts of them. Keywords can be separated by semicolons meaning they have to occur in different column headers. Alternatives of keywords can be separated by colons.
- header
- Lists all mapped table column headers, separated by semicolons. Each column definition can contain alternative definitions, separated by colons. If the column is defined by several keywords, the keywords have to be separated by & in the order of their appearance.
- mappings
- Mappings map table columns to ontology properties, they have to be defined by using the same templates as in mappings on DBpediaTemplateMapping. A separate mapping for each alternative column header definition has to be specified.
