https://mediawiki1.informatik.uni-mannheim.de/api.php?action=feedcontributions&feedformat=atom&user=Chrisahn 2026-05-13T21:10:06Z User contributions MediaWiki 1.39.3 https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Mapping_ro:Infocaseta_Pap%C4%83&diff=45499 2015-03-04T01:03:23Z

<p>Chrisahn: moved Mapping ro:Papă to Mapping ro:Infocaseta Papă: renamed in rowiki</p> <hr /> <div>{{TemplateMapping<br /> | mapToClass = ChristianBishop<br /> | mappings = <br /> {{ PropertyMapping | templateProperty = data-naștere | ontologyProperty = birthYear }}<br /> {{ PropertyMapping | templateProperty = nume-botez | ontologyProperty = child }}<br /> {{ PropertyMapping | templateProperty = data-naștere | ontologyProperty = birthDate }}<br /> {{ PropertyMapping | templateProperty = predecesor | ontologyProperty = veneratedIn }}<br /> {{ PropertyMapping | templateProperty = predecesor | ontologyProperty = canonizedBy }}<br /> {{ PropertyMapping | templateProperty = nume-botez | ontologyProperty = parent }}<br /> {{ PropertyMapping | templateProperty = sfârșit-pontificat | ontologyProperty = deathYear }}<br /> {{ PropertyMapping | templateProperty = nume | ontologyProperty = beatifiedBy }}<br /> {{ PropertyMapping | templateProperty = predecesor | ontologyProperty = predecessor }}<br /> {{ PropertyMapping | templateProperty = predecesor | ontologyProperty = title }}<br /> {{ PropertyMapping | templateProperty = succesor | ontologyProperty = office }}<br /> {{ PropertyMapping | templateProperty = nume-botez | ontologyProperty = birthName }}<br /> {{ PropertyMapping | templateProperty = sfârșit-pontificat | ontologyProperty = deathDate }}<br /> {{ PropertyMapping | templateProperty = data-naștere | ontologyProperty = deathPlace }}<br /> {{ PropertyMapping | templateProperty = nume | ontologyProperty = subtitle }}<br /> {{ PropertyMapping | templateProperty = data-naștere | ontologyProperty = birthPlace }}<br /> {{ PropertyMapping | templateProperty = succesor | ontologyProperty = successor }}<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Mapping_ro:Infocaseta_Pap%C4%83&diff=45498 2015-03-04T01:01:29Z

<p>Chrisahn: Created page with '{{TemplateMapping | mapToClass = ChristianBishop | mappings = {{ PropertyMapping | templateProperty = data-naștere | ontologyProperty = birthYear }} {{ PropertyMapping | temp...'</p> <hr /> <div>{{TemplateMapping<br /> | mapToClass = ChristianBishop<br /> | mappings = <br /> {{ PropertyMapping | templateProperty = data-naștere | ontologyProperty = birthYear }}<br /> {{ PropertyMapping | templateProperty = nume-botez | ontologyProperty = child }}<br /> {{ PropertyMapping | templateProperty = data-naștere | ontologyProperty = birthDate }}<br /> {{ PropertyMapping | templateProperty = predecesor | ontologyProperty = veneratedIn }}<br /> {{ PropertyMapping | templateProperty = predecesor | ontologyProperty = canonizedBy }}<br /> {{ PropertyMapping | templateProperty = nume-botez | ontologyProperty = parent }}<br /> {{ PropertyMapping | templateProperty = sfârșit-pontificat | ontologyProperty = deathYear }}<br /> {{ PropertyMapping | templateProperty = nume | ontologyProperty = beatifiedBy }}<br /> {{ PropertyMapping | templateProperty = predecesor | ontologyProperty = predecessor }}<br /> {{ PropertyMapping | templateProperty = predecesor | ontologyProperty = title }}<br /> {{ PropertyMapping | templateProperty = succesor | ontologyProperty = office }}<br /> {{ PropertyMapping | templateProperty = nume-botez | ontologyProperty = birthName }}<br /> {{ PropertyMapping | templateProperty = sfârșit-pontificat | ontologyProperty = deathDate }}<br /> {{ PropertyMapping | templateProperty = data-naștere | ontologyProperty = deathPlace }}<br /> {{ PropertyMapping | templateProperty = nume | ontologyProperty = subtitle }}<br /> {{ PropertyMapping | templateProperty = data-naștere | ontologyProperty = birthPlace }}<br /> {{ PropertyMapping | templateProperty = succesor | ontologyProperty = successor }}<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Mapping_ro:Discografie&diff=45497 2015-03-04T00:59:45Z

<p>Chrisahn: Created page with '{{TemplateMapping | mapToClass = Agent | mappings = {{ PropertyMapping | templateProperty = artist | ontologyProperty = alias }} }}'</p> <hr /> <div>{{TemplateMapping<br /> | mapToClass = Agent<br /> | mappings = <br /> {{ PropertyMapping | templateProperty = artist | ontologyProperty = alias }}<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Mapping_ro:Carte&diff=45496 2015-03-04T00:57:51Z

<p>Chrisahn: Created page with '{{TemplateMapping | mapToClass = Book | mappings = {{ PropertyMapping | templateProperty = urmată_de | ontologyProperty = subsequentWork }} {{ PropertyMapping | templatePrope...'</p> <hr /> <div>{{TemplateMapping<br /> | mapToClass = Book<br /> | mappings = <br /> {{ PropertyMapping | templateProperty = urmată_de | ontologyProperty = subsequentWork }}<br /> {{ PropertyMapping | templateProperty = isbn | ontologyProperty = isbn }}<br /> {{ PropertyMapping | templateProperty = data_apariției | ontologyProperty = description }}<br /> {{ PropertyMapping | templateProperty = țara_de_apariție | ontologyProperty = country }}<br /> {{ PropertyMapping | templateProperty = autor_copertă | ontologyProperty = coverArtist }}<br /> {{ PropertyMapping | templateProperty = titlu | ontologyProperty = characterInPlay }}<br /> {{ PropertyMapping | templateProperty = data_apariției | ontologyProperty = publicationDate }}<br /> {{ PropertyMapping | templateProperty = autor_ilustrații | ontologyProperty = illustrator }}<br /> {{ PropertyMapping | templateProperty = titlu_original | ontologyProperty = settingOfPlay }}<br /> {{ PropertyMapping | templateProperty = subiect | ontologyProperty = nonFictionSubject }}<br /> {{ PropertyMapping | templateProperty = precedată_de | ontologyProperty = predecessor }}<br /> {{ PropertyMapping | templateProperty = data_apariției | ontologyProperty = activeYearsStartYear }}<br /> {{ PropertyMapping | templateProperty = limba | ontologyProperty = language }}<br /> {{ PropertyMapping | templateProperty = număr_pagini | ontologyProperty = numberOfPages }}<br /> {{ PropertyMapping | templateProperty = data_apariției | ontologyProperty = lcc }}<br /> {{ PropertyMapping | templateProperty = autor | ontologyProperty = author }}<br /> {{ PropertyMapping | templateProperty = țara_de_apariție | ontologyProperty = dcc }}<br /> {{ PropertyMapping | templateProperty = titlu_original | ontologyProperty = subtitle }}<br /> {{ PropertyMapping | templateProperty = data_apariției | ontologyProperty = activeYearsEndYear }}<br /> {{ PropertyMapping | templateProperty = urmată_de | ontologyProperty = successor }}<br /> {{ PropertyMapping | templateProperty = seria | ontologyProperty = series }}<br /> {{ PropertyMapping | templateProperty = editura | ontologyProperty = publisher }}<br /> {{ PropertyMapping | templateProperty = oclc | ontologyProperty = oclc }}<br /> {{ PropertyMapping | templateProperty = precedată_de | ontologyProperty = previousWork }}<br /> {{ PropertyMapping | templateProperty = gen | ontologyProperty = literaryGenre }}<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Mapping_id:Infobox_building&diff=45495 2015-03-04T00:49:42Z

<p>Chrisahn: Created page with '{{ TemplateMapping | mapToClass = Building | mappings = {{ PropertyMapping | ontologyProperty = foaf:name | templateProperty = name }} }}'</p> <hr /> <div>{{ TemplateMapping | mapToClass = Building | mappings = <br /> {{ PropertyMapping | ontologyProperty = foaf:name | templateProperty = name }}<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Mapping_es:Ficha_de_pel%C3%ADcula&diff=45494 2015-03-04T00:48:57Z

<p>Chrisahn: Undo revision 45493 by Chrisahn (Talk)</p> <hr /> <div>{{TemplateMapping<br /> | mapToClass = Film<br /> | mappings =<br /> {{PropertyMapping | templateProperty = título original | ontologyProperty = foaf:name }}<br /> {{PropertyMapping | templateProperty = título | ontologyProperty = foaf:name }}<br /> <br /> {{PropertyMapping | templateProperty = dirección | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = dirección2 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = dirección3 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = dirección4 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = dirección5 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = dirección6 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = dirección7 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = dirección8 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = dirección9 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = producción | ontologyProperty = producer }}<br /> {{PropertyMapping | templateProperty = guión | ontologyProperty = writer }} <br /> {{PropertyMapping | templateProperty = guion | ontologyProperty = writer }}<br /> {{PropertyMapping | templateProperty = reparto | ontologyProperty = starring }}<br /> {{PropertyMapping | templateProperty = música | ontologyProperty = musicComposer }}<br /> {{PropertyMapping | templateProperty = escenografía | ontologyProperty = cinematography }}<br /> {{PropertyMapping | templateProperty = edición | ontologyProperty = editing }}<br /> {{PropertyMapping | templateProperty = montaje | ontologyProperty = editing }}<br /> {{PropertyMapping | templateProperty = distribución | ontologyProperty = distributor }}<br /> {{PropertyMapping | templateProperty = país | ontologyProperty = country }}<br /> {{PropertyMapping | templateProperty = país2 | ontologyProperty = country }}<br /> {{PropertyMapping | templateProperty = país3 | ontologyProperty = country }}<br /> {{PropertyMapping | templateProperty = país4 | ontologyProperty = country }}<br /> {{PropertyMapping | templateProperty = presupuesto | ontologyProperty = budget | unit = Currency }}<br /> {{PropertyMapping | templateProperty = imdb | ontologyProperty = imdbId }}<br /> {{PropertyMapping | templateProperty = estreno | ontologyProperty = releaseDate }}<br /> {{PropertyMapping | templateProperty = duración | ontologyProperty = runtime | unit = Time }}<br /> {{PropertyMapping | templateProperty = idioma | ontologyProperty = language }}<br /> {{PropertyMapping | templateProperty = idioma2 | ontologyProperty = language }}<br /> {{PropertyMapping | templateProperty = idioma3 | ontologyProperty = language }}<br /> {{PropertyMapping | templateProperty = idioma4 | ontologyProperty = language }}<br /> {{PropertyMapping | templateProperty = género | ontologyProperty = genre }}<br /> {{PropertyMapping | templateProperty = fotografía | ontologyProperty = cinematography }}<br /> {{PropertyMapping | templateProperty = precedida_por | ontologyProperty = previousWork }}<br /> {{PropertyMapping | templateProperty = sucedida_por | ontologyProperty = subsequentWork }}<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Mapping_es:Ficha_de_pel%C3%ADcula&diff=45493 2015-03-04T00:47:56Z

<p>Chrisahn: </p> <hr /> <div>{{TemplateMapping<br /> | mapToClass = Film<br /> | mappings =<br /> {{PropertyMapping | templateProperty = título original | ontologyProperty = foaf:name }}<br /> {{PropertyMapping | templateProperty = título | ontologyProperty = foaf:name }}<br /> {{PropertyMapping | templateProperty = dirección | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = dirección2 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = dirección3 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = dirección4 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = dirección5 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = dirección6 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = dirección7 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = dirección8 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = dirección9 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = producción | ontologyProperty = producer }}<br /> {{PropertyMapping | templateProperty = guión | ontologyProperty = writer }}<br /> {{PropertyMapping | templateProperty = reparto | ontologyProperty = starring }}<br /> {{PropertyMapping | templateProperty = música | ontologyProperty = musicComposer }}<br /> {{PropertyMapping | templateProperty = escenografía | ontologyProperty = cinematography }}<br /> {{PropertyMapping | templateProperty = edición | ontologyProperty = editing }}<br /> {{PropertyMapping | templateProperty = montaje | ontologyProperty = editing }}<br /> {{PropertyMapping | templateProperty = distribución | ontologyProperty = distributor }}<br /> {{PropertyMapping | templateProperty = país | ontologyProperty = country }}<br /> {{PropertyMapping | templateProperty = país2 | ontologyProperty = country }}<br /> {{PropertyMapping | templateProperty = país3 | ontologyProperty = country }}<br /> {{PropertyMapping | templateProperty = país4 | ontologyProperty = country }}<br /> {{PropertyMapping | templateProperty = presupuesto | ontologyProperty = budget | unit = Currency }}<br /> {{PropertyMapping | templateProperty = imdb | ontologyProperty = imdbId }}<br /> {{PropertyMapping | templateProperty = estreno | ontologyProperty = releaseDate }}<br /> {{PropertyMapping | templateProperty = duración | ontologyProperty = runtime | unit = Time }}<br /> {{PropertyMapping | templateProperty = idioma | ontologyProperty = language }}<br /> {{PropertyMapping | templateProperty = idioma2 | ontologyProperty = language }}<br /> {{PropertyMapping | templateProperty = idioma3 | ontologyProperty = language }}<br /> {{PropertyMapping | templateProperty = idioma4 | ontologyProperty = language }}<br /> {{PropertyMapping | templateProperty = precedida_por | ontologyProperty = previousWork }}<br /> {{PropertyMapping | templateProperty = sucedida_por | ontologyProperty = subsequentWork }}<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Mapping_ca:Partit_pol%C3%ADtic&diff=45491 2015-03-04T00:43:22Z

<p>Chrisahn: </p> <hr /> <div>{{TemplateMapping<br /> | mapToClass = PoliticalParty<br /> | mappings =<br /> {{PropertyMapping | templateProperty = nom | ontologyProperty = foaf:name }}<br /> {{PropertyMapping | templateProperty = fundació | ontologyProperty = formationDate }}<br /> {{PropertyMapping | templateProperty = desaparició | ontologyProperty = extinctionDate }}<br /> <br /> {{PropertyMapping | templateProperty = president | ontologyProperty = president}}<br /> {{PropertyMapping | templateProperty = secretari_general | ontologyProperty = person}}<br /> {{PropertyMapping | templateProperty = líder | ontologyProperty = leader}}<br /> <br /> {{PropertyMapping | templateProperty = seu | ontologyProperty = headquarter }}<br /> {{PropertyMapping | templateProperty = web | ontologyProperty = foaf:homepage }}<br /> <br /> {{PropertyMapping | templateProperty = partit_europeu | ontologyProperty = party }}<br /> {{PropertyMapping | templateProperty = partit_juvenil | ontologyProperty = party }}<br /> &lt;!--<br /> {{PropertyMapping | templateProperty = ideologia | ontologyProperty = ? }}<br /> {{PropertyMapping | templateProperty = publicació | ontologyProperty = ? }}<br /> {{PropertyMapping | templateProperty = parlament | ontologyProperty = ? }}<br /> --&gt;<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Mapping_ca:Infotaula_Llibre&diff=45490 2015-03-04T00:42:17Z

<p>Chrisahn: Undo revision 45489 by Chrisahn (Talk)</p> <hr /> <div>{{TemplateMapping<br /> | mapToClass = Book<br /> | mappings = <br /> {{PropertyMapping | templateProperty = nom | ontologyProperty = foaf:name }}<br /> {{PropertyMapping | templateProperty = títol_orig | ontologyProperty = foaf:name }}<br /> {{PropertyMapping | templateProperty = traductor | ontologyProperty = translator }}<br /> {{PropertyMapping | templateProperty = autor | ontologyProperty = author }}<br /> {{PropertyMapping | templateProperty = dibuixant | ontologyProperty = illustrator }}<br /> {{PropertyMapping | templateProperty = artista_portada | ontologyProperty = coverArtist }}<br /> {{PropertyMapping | templateProperty = país | ontologyProperty = country }}<br /> {{PropertyMapping | templateProperty = ciutat | ontologyProperty = city }}<br /> {{PropertyMapping | templateProperty = idioma | ontologyProperty = language }}<br /> {{PropertyMapping | templateProperty = sèrie | ontologyProperty = series }}<br /> {{PropertyMapping | templateProperty = tema | ontologyProperty = nonFictionSubject }}<br /> {{PropertyMapping | templateProperty = gènere | ontologyProperty = literaryGenre }}<br /> &lt;!-- use dc:publisher instead --&gt;<br /> {{PropertyMapping | templateProperty = editorial | ontologyProperty = publisher }}<br /> {{PropertyMapping | templateProperty = data_pub | ontologyProperty = publicationDate }}<br /> {{PropertyMapping | templateProperty = data_pub_català | ontologyProperty = publicationDate }}<br /> {{PropertyMapping | templateProperty = format | ontologyProperty = mediaType }}<br /> {{PropertyMapping | templateProperty = pàgines | ontologyProperty = numberOfPages }}<br /> {{PropertyMapping | templateProperty = isbn | ontologyProperty = isbn }}<br /> {{PropertyMapping | templateProperty = precedit_per | ontologyProperty = previousWork }}<br /> {{PropertyMapping | templateProperty = seguit_per | ontologyProperty = subsequentWork }}<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Mapping_ca:Infotaula_Llibre&diff=45489 2015-03-04T00:41:21Z

<p>Chrisahn: </p> <hr /> <div>{{TemplateMapping<br /> | mapToClass = Book<br /> | mappings = <br /> {{PropertyMapping | templateProperty = nom | ontologyProperty = foaf:name }}<br /> {{PropertyMapping | templateProperty = títol_orig | ontologyProperty = foaf:name }}<br /> {{PropertyMapping | templateProperty = traductor | ontologyProperty = translator }}<br /> {{PropertyMapping | templateProperty = autor | ontologyProperty = author }}<br /> {{PropertyMapping | templateProperty = dibuixant | ontologyProperty = illustrator }}<br /> {{PropertyMapping | templateProperty = artista_portada | ontologyProperty = coverArtist }}<br /> {{PropertyMapping | templateProperty = país | ontologyProperty = country }}<br /> {{PropertyMapping | templateProperty = ciutat | ontologyProperty = city }}<br /> {{PropertyMapping | templateProperty = idioma | ontologyProperty = language }}<br /> {{PropertyMapping | templateProperty = sèrie | ontologyProperty = series }}<br /> {{PropertyMapping | templateProperty = tema | ontologyProperty = subject }}<br /> {{PropertyMapping | templateProperty = gènere | ontologyProperty = genre }}<br /> &lt;!-- use dc:publisher instead --&gt;<br /> {{PropertyMapping | templateProperty = editorial | ontologyProperty = publisher }}<br /> {{PropertyMapping | templateProperty = data_pub | ontologyProperty = publicationDate }}<br /> {{PropertyMapping | templateProperty = data_pub_català | ontologyProperty = publicationDate }}<br /> {{PropertyMapping | templateProperty = format | ontologyProperty = mediaType }}<br /> {{PropertyMapping | templateProperty = pàgines | ontologyProperty = pages }}<br /> {{PropertyMapping | templateProperty = isbn | ontologyProperty = isbn }}<br /> {{PropertyMapping | templateProperty = precedit_per | ontologyProperty = previousWork }}<br /> {{PropertyMapping | templateProperty = seguit_per | ontologyProperty = subsequentWork }}<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Mapping_ca:Fitxa_de_pel%C2%B7l%C3%ADcula&diff=45488 2015-03-04T00:39:32Z

<p>Chrisahn: </p> <hr /> <div>{{TemplateMapping<br /> | mapToClass = Film<br /> | mappings =<br /> {{PropertyMapping | templateProperty = títol original | ontologyProperty = foaf:name }}<br /> {{PropertyMapping | templateProperty = títol | ontologyProperty = foaf:name }}<br /> {{PropertyMapping | templateProperty = direcció | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = direcció2 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = direcció3 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = direcció4 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = direcció5 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = direcció6 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = direcció7 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = direcció8 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = direcció9 | ontologyProperty = director }}<br /> {{PropertyMapping | templateProperty = producció | ontologyProperty = producer }}<br /> {{PropertyMapping | templateProperty = guió | ontologyProperty = writer }}<br /> {{PropertyMapping | templateProperty = repartiment | ontologyProperty = starring }}<br /> {{PropertyMapping | templateProperty = música | ontologyProperty = musicComposer }}<br /> {{PropertyMapping | templateProperty = escenografía | ontologyProperty = cinematography }}<br /> {{PropertyMapping | templateProperty = edició | ontologyProperty = editing }}<br /> {{PropertyMapping | templateProperty = muntatge | ontologyProperty = editing }}<br /> {{PropertyMapping | templateProperty = distribució | ontologyProperty = distributor }}<br /> {{PropertyMapping | templateProperty = país | ontologyProperty = country }}<br /> {{PropertyMapping | templateProperty = país2 | ontologyProperty = country }}<br /> {{PropertyMapping | templateProperty = país3 | ontologyProperty = country }}<br /> {{PropertyMapping | templateProperty = país4 | ontologyProperty = country }}<br /> {{PropertyMapping | templateProperty = pressupost | ontologyProperty = budget | unit = Currency }}<br /> {{PropertyMapping | templateProperty = imdb | ontologyProperty = imdbId }}<br /> {{PropertyMapping | templateProperty = estrena | ontologyProperty = releaseDate }}<br /> {{PropertyMapping | templateProperty = duració | ontologyProperty = runtime | unit = Time }}<br /> {{PropertyMapping | templateProperty = idioma | ontologyProperty = language }}<br /> {{PropertyMapping | templateProperty = idioma2 | ontologyProperty = language }}<br /> {{PropertyMapping | templateProperty = idioma3 | ontologyProperty = language }}<br /> {{PropertyMapping | templateProperty = idioma4 | ontologyProperty = language }}<br /> {{PropertyMapping | templateProperty = precedida_per | ontologyProperty = previousWork }}<br /> {{PropertyMapping | templateProperty = seguida_de | ontologyProperty = subsequentWork }}<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Mapping_ca:Actor&diff=45487 2015-03-04T00:36:58Z

<p>Chrisahn: </p> <hr /> <div>{{TemplateMapping<br /> | mapToClass = Actor<br /> | mappings =<br /> {{PropertyMapping | templateProperty = name | ontologyProperty = foaf:name }}<br /> {{PropertyMapping | templateProperty = nom de naixença | ontologyProperty = foaf:givenName }}<br /> {{PropertyMapping | templateProperty = data de naixença | ontologyProperty = birthDate }}<br /> {{PropertyMapping | templateProperty = indret de naixença | ontologyProperty = birthPlace }}<br /> {{PropertyMapping | templateProperty = data de defunció | ontologyProperty = deathDate }}<br /> {{PropertyMapping | templateProperty = lloc de defunció | ontologyProperty = deathPlace }}<br /> {{PropertyMapping | templateProperty = cònjuge | ontologyProperty = spouse }}<br /> <br /> {{PropertyMapping | templateProperty = premis oscar | ontologyProperty = academyAward }}<br /> {{PropertyMapping | templateProperty = premis bafta | ontologyProperty = baftaAward }}<br /> {{PropertyMapping | templateProperty = premis cesar | ontologyProperty = cesarAward }}<br /> {{PropertyMapping | templateProperty = premis emmy | ontologyProperty = emmyAward }}<br /> {{PropertyMapping | templateProperty = filmfare awards | ontologyProperty = filmFareAward }}<br /> {{PropertyMapping | templateProperty = premis golden globe | ontologyProperty = goldenGlobeAward }}<br /> {{PropertyMapping | templateProperty = altres premis | ontologyProperty = award }}<br /> {{PropertyMapping | templateProperty = premis goya | ontologyProperty = goyaAward }}<br /> {{PropertyMapping | templateProperty = premis grammy | ontologyProperty = grammyAward }}<br /> {{PropertyMapping | templateProperty = premis tony | ontologyProperty = tonyAward }}<br /> {{PropertyMapping | templateProperty = premis gaudí | ontologyProperty = gaudiAward }}<br /> <br /> {{PropertyMapping | templateProperty = pàgina web | ontologyProperty = foaf:homepage }}<br /> {{PropertyMapping | templateProperty = imdb | ontologyProperty = imdbId }}<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Mapping_ca:Infotaula_d%27artista_musical&diff=45486 2015-03-04T00:14:57Z

<p>Chrisahn: </p> <hr /> <div>&lt;!-- Docs are listed in Catalan, but all usages are in English, the same as on en.wikipedia --&gt;<br /> {{ConditionalMapping<br /> | cases =<br /> {{Condition<br /> | templateProperty = Current_members<br /> | operator = isSet<br /> | mapping = {{TemplateMapping<br /> | mapToClass = Band<br /> }}<br /> }}<br /> <br /> {{Condition<br /> | templateProperty = Past_members<br /> | operator = isSet<br /> | mapping = {{TemplateMapping<br /> | mapToClass = Band<br /> }}<br /> }}<br /> <br /> {{Condition<br /> | templateProperty = Background<br /> | operator = equals<br /> | value = group_or_band<br /> | mapping = {{TemplateMapping<br /> | mapToClass = Band<br /> }}<br /> }}<br /> <br /> {{Condition<br /> | templateProperty = Background<br /> | operator = equals<br /> | value = cover_band<br /> | mapping = {{TemplateMapping<br /> | mapToClass = Band<br /> }}<br /> }}<br /> <br /> {{Condition<br /> | templateProperty = Background<br /> | operator = equals<br /> | value = classical_ensemble<br /> | mapping = {{TemplateMapping<br /> | mapToClass = Band<br /> }}<br /> }}<br /> <br /> {{Condition<br /> | operator = otherwise<br /> | mapping = {{TemplateMapping<br /> | mapToClass = MusicalArtist<br /> }}<br /> }}<br /> <br /> | defaultMappings =<br /> {{PropertyMapping | templateProperty = Name | ontologyProperty = foaf:name }}<br /> {{PropertyMapping | templateProperty = Background | ontologyProperty = background }}<br /> {{PropertyMapping | templateProperty = Birth_name | ontologyProperty = foaf:givenName }}<br /> {{PropertyMapping | templateProperty = Alias | ontologyProperty = alias }}<br /> {{PropertyMapping | templateProperty = Born | ontologyProperty = birthDate }}<br /> {{PropertyMapping | templateProperty = Born | ontologyProperty = birthPlace }}<br /> {{PropertyMapping | templateProperty = Died | ontologyProperty = deathDate }}<br /> {{PropertyMapping | templateProperty = Died | ontologyProperty = deathPlace }}<br /> {{PropertyMapping | templateProperty = Origin | ontologyProperty = hometown }}<br /> {{PropertyMapping | templateProperty = Instrument | ontologyProperty = instrument }}<br /> {{PropertyMapping | templateProperty = Genre | ontologyProperty = genre }}<br /> {{PropertyMapping | templateProperty = Occupation | ontologyProperty = occupation }}<br /> {{DateIntervalMapping<br /> | templateProperty = Years_active<br /> | startDateOntologyProperty = activeYearsStartYear<br /> | endDateOntologyProperty = activeYearsEndYear<br /> }}<br /> {{PropertyMapping | templateProperty = Label | ontologyProperty = recordLabel}}<br /> {{PropertyMapping | templateProperty = Associated_acts | ontologyProperty = associatedBand }}<br /> {{PropertyMapping | templateProperty = Associated_acts | ontologyProperty = associatedMusicalArtist }}<br /> {{PropertyMapping | templateProperty = URL | ontologyProperty = foaf:homepage }}<br /> {{PropertyMapping | templateProperty = Notable_instruments | ontologyProperty = instrument }}<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Rewriting_templateProperty&diff=45467 2015-02-25T20:44:36Z

<p>Chrisahn: /* Intro */</p> <hr /> <div>'''WARNING: Work in progess. The content of this page is largely incorrect.'''<br /> <br /> TODO: Make an EN example using Infobox Politician<br /> --[[User:VladimirAlexiev|VladimirAlexiev]] 12:12, 25 February 2015 (UTC)<br /> <br /> == Intro ==<br /> The basic way the extractor works is like this:<br /> <br /> * data is extracted from template props<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> &lt;s&gt;* the raw data is passed through mappings templateProperty -&gt; ontologyProperty&lt;/s&gt;<br /> <br /> &lt;s&gt;You'd think that templateProperty is the same as the raw prop name. Yeah but not always.&lt;/s&gt;<br /> <br /> The last part (''data is passed through mappings'') is wrong. The mapping based extractor processes the Wikitext source, '''not''' the output of the InfoboxExtractor. A pipeline architecture would make a lot of sense, but that's not how DBpedia works. [[User:Chrisahn|Chrisahn]] 17:54, 25 February 2015 (UTC)<br /> <br /> Here's what actually happens:<br /> <br /> * Wikitext is parsed into an AST (abstract syntax tree)<br /> * The AST is passed to several different extractors according to the configuration<br /> * Each extractor processes the AST and produces triples<br /> * The triples are not used as input for any other extractors.<br /> <br /> Here's what the [http://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/InfoboxExtractor.scala InfoboxExtractor] does:<br /> <br /> * data is extracted from template props in the AST<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> <br /> Here's what the [http://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/MappingExtractor.scala MappingExtractor] does:<br /> <br /> * data is extracted from template props in the AST and passed through mappings templateProperty -&gt; ontologyProperty<br /> * these are emitted as generic mapping-based props, eg<br /> ** http://dbpedia.org/ontology/parent for EN, BG and any other language (usual prefix dbo:)<br /> <br /> == Wikipedia Prop Structures ==<br /> Many Wikipedia templates allow creating '''several''' instances of something. <br /> Eg [https://en.wikipedia.org/wiki/Template:Listen Listen] allows a Wikipedia editor to attach up to 11 soundRecording to the subject,<br /> using &quot;parallel&quot; arrays of properties:<br /> * filename, filename1... filename10<br /> * title, title1... title10<br /> * description, description1.. description10<br /> The parallelism is reflected in a numeric suffix.<br /> <br /> Good maps take care of this, by grouping the &quot;parallel props&quot; in separate IntermediateNodeMappings or a similar structure that can produce an &quot;array&quot;.<br /> Eg [http://mappings.dbpedia.org/index.php?title=Mapping_en:Listen&amp;action=edit mapping Listen] has this 11 times:<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = Sound | correspondingProperty = soundRecording | mappings =<br /> {{ PropertyMapping | templateProperty = type | ontologyProperty = dc:type }}<br /> {{ PropertyMapping | templateProperty = filename1 | ontologyProperty = filename }}<br /> {{ PropertyMapping | templateProperty = title1 | ontologyProperty = title }}<br /> {{ PropertyMapping | templateProperty = description1 | ontologyProperty = description }}<br /> }}<br /> &lt;/pre&gt;<br /> <br /> Now consider Politicians. They may hold several Positions, each over several Mandates (they are nasty that way).<br /> For each Position&gt;Mandate (say 5*3=15), there's a bunch of props such as<br /> party, predecessor, successor, colleagues (eg vicePresident, governor...), years the subject came to that position,<br /> years the colleagues came to their respective positions, etc.<br /> <br /> Eg see prop names of [https://bg.wikipedia.org/wiki/Шаблон:Държавник_инфо Държавник_инфо], but that's not the complete story: there's also трети_мандат_* (&quot;third mandate&quot; fields) etc.<br /> * If the 2D data arrays below the photos of Rosen Plevneliev and Angela Merkel don't strike your fancy, check out one of them Socialists that ruled for 40 years: [https://bg.wikipedia.org/wiki/Тодор_Живков Тодор_Живков]<br /> See a full list of props and an incomplete attempt to group them all at [http://mappings.dbpedia.org/index.php?title=Mapping_bg:Държавник_инфо&amp;action=edit Mapping Държавник_инфо].<br /> <br /> Wikidata editors were at a loss to create meaningful two-dimensional parallel arrays of names, so they created parasitc prefixes &amp; suffixes that are not so easy to match up. Eg there are 10 props &quot;предшестванОт&quot;, all mapped to &quot;predecessor&quot; but in different groups:<br /> &lt;pre&gt;<br /> предшестван от<br /> предшестван от2<br /> предшестван от3<br /> втори_мандат_предшестван от<br /> втори_мандат_предшестван от2<br /> втори_мандат_предшестван от3<br /> трети_мандат_предшестван от<br /> ...<br /> &lt;/pre&gt;<br /> <br /> * The prefixes may have any form<br /> * The suffixes are digits, optionally followed by letters<br /> <br /> == Rewriting templateProperty ==<br /> <br /> The parasitic prefixes/suffixes encode important info about the grouping of props,<br /> but that info is not transmitted in any clear way.<br /> <br /> Assume a mapping fragment like this, extracting data for resource bgdbr:Тодор_Живков<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = CareerStation | correspondingProperty = careerStation | mappings = <br /> {{ PropertyMapping | templateProperty = втори_мандат_предшестван от3 | ontologyProperty = predecessor }}<br /> &lt;/pre&gt;<br /> What the extractor '''really''' does is:<br /> <br /> : No it doesn't. See above. [[User:Chrisahn|Chrisahn]] 18:06, 25 February 2015 (UTC)<br /> <br /> * Takes data from the templateProperty provided (as expected)<br /> * Strips parasitic prefixes &amp; suffixes from the templateProperty (maybe unexpected) and converts to camelCase<br /> * Emits the data using the original subject and this '''rewritten''' templateProperty, eg:<br /> bgdbr:Тодор_Живков bgdbp:предшестванОт &lt;data&gt;<br /> * Makes an IntermediateNode and connects it with correspondingProperty (as expected), eg:<br /> bgdbr:Тодор_Живков dbo:careerStation bgdbr:Тодор_Живков__1<br /> * Emits the data using the IntermediateNode and the ontologyProperty as provided (as expected), eg;<br /> bgdbr:Тодор_Живков__1 dbo:predeccessor &lt;data&gt;<br /> <br /> This achieves several goals:<br /> * the general semantics of the raw property is preserved, but not its grouping<br /> * the grouping is preserved by the creation of IntermediateNodes that use mapped properties (if the mapping is good)<br /> <br /> This allows you to make queries such as:<br /> * all predecessors of Тодор_Живков lumped together (regardless of the position). This works even if these raw props are not mapped!<br /> select * {bgdbr:Тодор_Живков bgdbp:предшестванОт ?pred}<br /> * all predecessors of Тодор_Живков, paired with successors, and the corresponding position name (office). (Note: you may want to throw in some OPTIONALs)<br /> select * {bgdbr:Тодор_Живков dbo:careerStation<br /> [dbo:predecessor ?pred; dbo:successor ?succ; dbo:office ?office]}<br /> <br /> Neat!<br /> <br /> '''NOTE''' Currently only purely numeric parasitic suffixes are stripped.<br /> Prefixes and alphanumeric suffixes would be stripped after [https://github.com/dbpedia/extraction-framework/issues/317 issue #317] is implemented</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Rewriting_templateProperty&diff=45466 2015-02-25T20:44:12Z

<p>Chrisahn: /* Intro */</p> <hr /> <div>'''WARNING: Work in progess. The content of this page is largely incorrect.'''<br /> <br /> TODO: Make an EN example using Infobox Politician<br /> --[[User:VladimirAlexiev|VladimirAlexiev]] 12:12, 25 February 2015 (UTC)<br /> <br /> == Intro ==<br /> The basic way the extractor works is like this:<br /> <br /> * data is extracted from template props<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> &lt;s&gt;* the raw data is passed through mappings templateProperty -&gt; ontologyProperty&lt;/s&gt;<br /> <br /> &lt;s&gt;You'd think that templateProperty is the same as the raw prop name. Yeah but not always.&lt;/s&gt;<br /> <br /> The last part (''data is passed through mappings'') is wrong. The mapping based extractor processes the Wikitext source, '''not''' the output of the InfoboxExtractor. A pipeline architecture would make a lot of sense, but that's not how DBpedia works. [[User:Chrisahn|Chrisahn]] 17:54, 25 February 2015 (UTC)<br /> <br /> Here's what actually happens:<br /> <br /> * Wikitext is parsed into an AST (abstract syntax tree)<br /> * The AST is passed to several different extractors according to the configuration<br /> * Each extractor processes the AST and produces triples<br /> * The triples are not used as input for any other extractors.<br /> <br /> Here's what the [https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/InfoboxExtractor.scala InfoboxExtractor] does:<br /> <br /> * data is extracted from template props in the AST<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> <br /> Here's what the [https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/MappingExtractor.scala MappingExtractor] does:<br /> <br /> * data is extracted from template props in the AST and passed through mappings templateProperty -&gt; ontologyProperty<br /> * these are emitted as generic mapping-based props, eg<br /> ** http://dbpedia.org/ontology/parent for EN, BG and any other language (usual prefix dbo:)<br /> <br /> == Wikipedia Prop Structures ==<br /> Many Wikipedia templates allow creating '''several''' instances of something. <br /> Eg [https://en.wikipedia.org/wiki/Template:Listen Listen] allows a Wikipedia editor to attach up to 11 soundRecording to the subject,<br /> using &quot;parallel&quot; arrays of properties:<br /> * filename, filename1... filename10<br /> * title, title1... title10<br /> * description, description1.. description10<br /> The parallelism is reflected in a numeric suffix.<br /> <br /> Good maps take care of this, by grouping the &quot;parallel props&quot; in separate IntermediateNodeMappings or a similar structure that can produce an &quot;array&quot;.<br /> Eg [http://mappings.dbpedia.org/index.php?title=Mapping_en:Listen&amp;action=edit mapping Listen] has this 11 times:<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = Sound | correspondingProperty = soundRecording | mappings =<br /> {{ PropertyMapping | templateProperty = type | ontologyProperty = dc:type }}<br /> {{ PropertyMapping | templateProperty = filename1 | ontologyProperty = filename }}<br /> {{ PropertyMapping | templateProperty = title1 | ontologyProperty = title }}<br /> {{ PropertyMapping | templateProperty = description1 | ontologyProperty = description }}<br /> }}<br /> &lt;/pre&gt;<br /> <br /> Now consider Politicians. They may hold several Positions, each over several Mandates (they are nasty that way).<br /> For each Position&gt;Mandate (say 5*3=15), there's a bunch of props such as<br /> party, predecessor, successor, colleagues (eg vicePresident, governor...), years the subject came to that position,<br /> years the colleagues came to their respective positions, etc.<br /> <br /> Eg see prop names of [https://bg.wikipedia.org/wiki/Шаблон:Държавник_инфо Държавник_инфо], but that's not the complete story: there's also трети_мандат_* (&quot;third mandate&quot; fields) etc.<br /> * If the 2D data arrays below the photos of Rosen Plevneliev and Angela Merkel don't strike your fancy, check out one of them Socialists that ruled for 40 years: [https://bg.wikipedia.org/wiki/Тодор_Живков Тодор_Живков]<br /> See a full list of props and an incomplete attempt to group them all at [http://mappings.dbpedia.org/index.php?title=Mapping_bg:Държавник_инфо&amp;action=edit Mapping Държавник_инфо].<br /> <br /> Wikidata editors were at a loss to create meaningful two-dimensional parallel arrays of names, so they created parasitc prefixes &amp; suffixes that are not so easy to match up. Eg there are 10 props &quot;предшестванОт&quot;, all mapped to &quot;predecessor&quot; but in different groups:<br /> &lt;pre&gt;<br /> предшестван от<br /> предшестван от2<br /> предшестван от3<br /> втори_мандат_предшестван от<br /> втори_мандат_предшестван от2<br /> втори_мандат_предшестван от3<br /> трети_мандат_предшестван от<br /> ...<br /> &lt;/pre&gt;<br /> <br /> * The prefixes may have any form<br /> * The suffixes are digits, optionally followed by letters<br /> <br /> == Rewriting templateProperty ==<br /> <br /> The parasitic prefixes/suffixes encode important info about the grouping of props,<br /> but that info is not transmitted in any clear way.<br /> <br /> Assume a mapping fragment like this, extracting data for resource bgdbr:Тодор_Живков<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = CareerStation | correspondingProperty = careerStation | mappings = <br /> {{ PropertyMapping | templateProperty = втори_мандат_предшестван от3 | ontologyProperty = predecessor }}<br /> &lt;/pre&gt;<br /> What the extractor '''really''' does is:<br /> <br /> : No it doesn't. See above. [[User:Chrisahn|Chrisahn]] 18:06, 25 February 2015 (UTC)<br /> <br /> * Takes data from the templateProperty provided (as expected)<br /> * Strips parasitic prefixes &amp; suffixes from the templateProperty (maybe unexpected) and converts to camelCase<br /> * Emits the data using the original subject and this '''rewritten''' templateProperty, eg:<br /> bgdbr:Тодор_Живков bgdbp:предшестванОт &lt;data&gt;<br /> * Makes an IntermediateNode and connects it with correspondingProperty (as expected), eg:<br /> bgdbr:Тодор_Живков dbo:careerStation bgdbr:Тодор_Живков__1<br /> * Emits the data using the IntermediateNode and the ontologyProperty as provided (as expected), eg;<br /> bgdbr:Тодор_Живков__1 dbo:predeccessor &lt;data&gt;<br /> <br /> This achieves several goals:<br /> * the general semantics of the raw property is preserved, but not its grouping<br /> * the grouping is preserved by the creation of IntermediateNodes that use mapped properties (if the mapping is good)<br /> <br /> This allows you to make queries such as:<br /> * all predecessors of Тодор_Живков lumped together (regardless of the position). This works even if these raw props are not mapped!<br /> select * {bgdbr:Тодор_Живков bgdbp:предшестванОт ?pred}<br /> * all predecessors of Тодор_Живков, paired with successors, and the corresponding position name (office). (Note: you may want to throw in some OPTIONALs)<br /> select * {bgdbr:Тодор_Живков dbo:careerStation<br /> [dbo:predecessor ?pred; dbo:successor ?succ; dbo:office ?office]}<br /> <br /> Neat!<br /> <br /> '''NOTE''' Currently only purely numeric parasitic suffixes are stripped.<br /> Prefixes and alphanumeric suffixes would be stripped after [https://github.com/dbpedia/extraction-framework/issues/317 issue #317] is implemented</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Mapping_ca:Actor&diff=45464 2015-02-25T20:20:03Z

<p>Chrisahn: moved Mapping ca:Actor TEMPORARY SUFFIX to Mapping ca:Actor</p> <hr /> <div>{{TemplateMapping<br /> | mapToClass = Actor<br /> | mappings =<br /> {{PropertyMapping | templateProperty = name | ontologyProperty = foaf:name }}<br /> {{PropertyMapping | templateProperty = nom de naixença | ontologyProperty = foaf:givenName }}<br /> <br /> {{PropertyMapping | templateProperty = data de naixença | ontologyProperty = birthDate }}<br /> {{PropertyMapping | templateProperty = indret de naixença | ontologyProperty = birthPlace }}<br /> {{PropertyMapping | templateProperty = data de defunció | ontologyProperty = deathDate }}<br /> {{PropertyMapping | templateProperty = lloc de defunció | ontologyProperty = deathPlace }}<br /> {{PropertyMapping | templateProperty = cònjuge | ontologyProperty = spouse }}<br /> <br /> {{PropertyMapping | templateProperty = premis oscar | ontologyProperty = academyAward }}<br /> {{PropertyMapping | templateProperty = premis bafta | ontologyProperty = baftaAward }}<br /> {{PropertyMapping | templateProperty = premis cesar | ontologyProperty = cesarAward }}<br /> {{PropertyMapping | templateProperty = premis emmy | ontologyProperty = emmyAward }}<br /> {{PropertyMapping | templateProperty = filmfare awards | ontologyProperty = filmFareAward }}<br /> {{PropertyMapping | templateProperty = premis golden globe | ontologyProperty = goldenGlobeAward }}<br /> {{PropertyMapping | templateProperty = altres premis | ontologyProperty = award }}<br /> {{PropertyMapping | templateProperty = premis goya | ontologyProperty = goyaAward }}<br /> {{PropertyMapping | templateProperty = premis grammy | ontologyProperty = grammyAward }}<br /> {{PropertyMapping | templateProperty = premis tony | ontologyProperty = tonyAward }}<br /> {{PropertyMapping | templateProperty = premis gaudí | ontologyProperty = gaudiAward }}<br /> <br /> {{PropertyMapping | templateProperty = pàgina web | ontologyProperty = foaf:homepage }}<br /> {{PropertyMapping | templateProperty = imdb | ontologyProperty = imdbId }}<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Mapping_ca:Actor&diff=45461 2015-02-25T20:15:27Z

<p>Chrisahn: moved Mapping ca:Actor to Mapping ca:Actor TEMPORARY SUFFIX</p> <hr /> <div>{{TemplateMapping<br /> | mapToClass = Actor<br /> | mappings =<br /> {{PropertyMapping | templateProperty = name | ontologyProperty = foaf:name }}<br /> {{PropertyMapping | templateProperty = nom de naixença | ontologyProperty = foaf:givenName }}<br /> <br /> {{PropertyMapping | templateProperty = data de naixença | ontologyProperty = birthDate }}<br /> {{PropertyMapping | templateProperty = indret de naixença | ontologyProperty = birthPlace }}<br /> {{PropertyMapping | templateProperty = data de defunció | ontologyProperty = deathDate }}<br /> {{PropertyMapping | templateProperty = lloc de defunció | ontologyProperty = deathPlace }}<br /> {{PropertyMapping | templateProperty = cònjuge | ontologyProperty = spouse }}<br /> <br /> {{PropertyMapping | templateProperty = premis oscar | ontologyProperty = academyAward }}<br /> {{PropertyMapping | templateProperty = premis bafta | ontologyProperty = baftaAward }}<br /> {{PropertyMapping | templateProperty = premis cesar | ontologyProperty = cesarAward }}<br /> {{PropertyMapping | templateProperty = premis emmy | ontologyProperty = emmyAward }}<br /> {{PropertyMapping | templateProperty = filmfare awards | ontologyProperty = filmFareAward }}<br /> {{PropertyMapping | templateProperty = premis golden globe | ontologyProperty = goldenGlobeAward }}<br /> {{PropertyMapping | templateProperty = altres premis | ontologyProperty = award }}<br /> {{PropertyMapping | templateProperty = premis goya | ontologyProperty = goyaAward }}<br /> {{PropertyMapping | templateProperty = premis grammy | ontologyProperty = grammyAward }}<br /> {{PropertyMapping | templateProperty = premis tony | ontologyProperty = tonyAward }}<br /> {{PropertyMapping | templateProperty = premis gaudí | ontologyProperty = gaudiAward }}<br /> <br /> {{PropertyMapping | templateProperty = pàgina web | ontologyProperty = foaf:homepage }}<br /> {{PropertyMapping | templateProperty = imdb | ontologyProperty = imdbId }}<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=User:Chrisahn/Sandbox&diff=45458 2015-02-25T19:01:58Z

<p>Chrisahn: </p> <hr /> <div>[[Mapping ro:Papă]]<br /> [[:Mapping ro:Papă]]</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Rewriting_templateProperty&diff=45457 2015-02-25T18:44:56Z

<p>Chrisahn: /* Intro */</p> <hr /> <div>'''WARNING: Work in progess. The content of this page is largely incorrect.'''<br /> <br /> TODO: Make an EN example using Infobox Politician<br /> --[[User:VladimirAlexiev|VladimirAlexiev]] 12:12, 25 February 2015 (UTC)<br /> <br /> == Intro ==<br /> The basic way the extractor works is like this:<br /> <br /> * data is extracted from template props<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> &lt;s&gt;* the raw data is passed through mappings templateProperty -&gt; ontologyProperty&lt;/s&gt;<br /> <br /> &lt;s&gt;You'd think that templateProperty is the same as the raw prop name. Yeah but not always.&lt;/s&gt;<br /> <br /> The last part (''data is passed through mappings'') is wrong. The mapping based extractor processes the Wikitext source, '''not''' the output of the InfoboxExtractor. A pipeline architecture would make a lot of sense, but that's not how DBpedia works. [[User:Chrisahn|Chrisahn]] 17:54, 25 February 2015 (UTC)<br /> <br /> Here's what actually happens:<br /> <br /> * Wikitext is parsed into an AST (abstract syntax tree)<br /> * The AST is passed to several different extractors according to the configuration<br /> * Each extractor processes the AST and produces triples<br /> * The triples are not used as input for any other extractors.<br /> <br /> Here's what the [InfoboxExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/InfoboxExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> <br /> Here's what the [MappingExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/MappingExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST and passed through mappings templateProperty -&gt; ontologyProperty<br /> * these are emitted as generic mapping-based props, eg<br /> ** http://dbpedia.org/ontology/parent for EN, BG and any other language (usual prefix dbo:)<br /> <br /> == Wikipedia Prop Structures ==<br /> Many Wikipedia templates allow creating '''several''' instances of something. <br /> Eg [https://en.wikipedia.org/wiki/Template:Listen Listen] allows a Wikipedia editor to attach up to 11 soundRecording to the subject,<br /> using &quot;parallel&quot; arrays of properties:<br /> * filename, filename1... filename10<br /> * title, title1... title10<br /> * description, description1.. description10<br /> The parallelism is reflected in a numeric suffix.<br /> <br /> Good maps take care of this, by grouping the &quot;parallel props&quot; in separate IntermediateNodeMappings or a similar structure that can produce an &quot;array&quot;.<br /> Eg [http://mappings.dbpedia.org/index.php?title=Mapping_en:Listen&amp;action=edit mapping Listen] has this 11 times:<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = Sound | correspondingProperty = soundRecording | mappings =<br /> {{ PropertyMapping | templateProperty = type | ontologyProperty = dc:type }}<br /> {{ PropertyMapping | templateProperty = filename1 | ontologyProperty = filename }}<br /> {{ PropertyMapping | templateProperty = title1 | ontologyProperty = title }}<br /> {{ PropertyMapping | templateProperty = description1 | ontologyProperty = description }}<br /> }}<br /> &lt;/pre&gt;<br /> <br /> Now consider Politicians. They may hold several Positions, each over several Mandates (they are nasty that way).<br /> For each Position&gt;Mandate (say 5*3=15), there's a bunch of props such as<br /> party, predecessor, successor, colleagues (eg vicePresident, governor...), years the subject came to that position,<br /> years the colleagues came to their respective positions, etc.<br /> <br /> Eg see prop names of [https://bg.wikipedia.org/wiki/Шаблон:Държавник_инфо Държавник_инфо], but that's not the complete story: there's also трети_мандат_* (&quot;third mandate&quot; fields) etc.<br /> * If the 2D data arrays below the photos of Rosen Plevneliev and Angela Merkel don't strike your fancy, check out one of them Socialists that ruled for 40 years: [https://bg.wikipedia.org/wiki/Тодор_Живков Тодор_Живков]<br /> See a full list of props and an incomplete attempt to group them all at [http://mappings.dbpedia.org/index.php?title=Mapping_bg:Държавник_инфо&amp;action=edit Mapping Държавник_инфо].<br /> <br /> Wikidata editors were at a loss to create meaningful two-dimensional parallel arrays of names, so they created parasitc prefixes &amp; suffixes that are not so easy to match up. Eg there are 10 props &quot;предшестванОт&quot;, all mapped to &quot;predecessor&quot; but in different groups:<br /> &lt;pre&gt;<br /> предшестван от<br /> предшестван от2<br /> предшестван от3<br /> втори_мандат_предшестван от<br /> втори_мандат_предшестван от2<br /> втори_мандат_предшестван от3<br /> трети_мандат_предшестван от<br /> ...<br /> &lt;/pre&gt;<br /> <br /> * The prefixes may have any form<br /> * The suffixes are digits, optionally followed by letters<br /> <br /> == Rewriting templateProperty ==<br /> <br /> The parasitic prefixes/suffixes encode important info about the grouping of props,<br /> but that info is not transmitted in any clear way.<br /> <br /> Assume a mapping fragment like this, extracting data for resource bgdbr:Тодор_Живков<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = CareerStation | correspondingProperty = careerStation | mappings = <br /> {{ PropertyMapping | templateProperty = втори_мандат_предшестван от3 | ontologyProperty = predecessor }}<br /> &lt;/pre&gt;<br /> What the extractor '''really''' does is:<br /> <br /> : No it doesn't. See above. [[User:Chrisahn|Chrisahn]] 18:06, 25 February 2015 (UTC)<br /> <br /> * Takes data from the templateProperty provided (as expected)<br /> * Strips parasitic prefixes &amp; suffixes from the templateProperty (maybe unexpected) and converts to camelCase<br /> * Emits the data using the original subject and this '''rewritten''' templateProperty, eg:<br /> bgdbr:Тодор_Живков bgdbp:предшестванОт &lt;data&gt;<br /> * Makes an IntermediateNode and connects it with correspondingProperty (as expected), eg:<br /> bgdbr:Тодор_Живков dbo:careerStation bgdbr:Тодор_Живков__1<br /> * Emits the data using the IntermediateNode and the ontologyProperty as provided (as expected), eg;<br /> bgdbr:Тодор_Живков__1 dbo:predeccessor &lt;data&gt;<br /> <br /> This achieves several goals:<br /> * the general semantics of the raw property is preserved, but not its grouping<br /> * the grouping is preserved by the creation of IntermediateNodes that use mapped properties (if the mapping is good)<br /> <br /> This allows you to make queries such as:<br /> * all predecessors of Тодор_Живков lumped together (regardless of the position). This works even if these raw props are not mapped!<br /> select * {bgdbr:Тодор_Живков bgdbp:предшестванОт ?pred}<br /> * all predecessors of Тодор_Живков, paired with successors, and the corresponding position name (office). (Note: you may want to throw in some OPTIONALs)<br /> select * {bgdbr:Тодор_Живков dbo:careerStation<br /> [dbo:predecessor ?pred; dbo:successor ?succ; dbo:office ?office]}<br /> <br /> Neat!<br /> <br /> '''NOTE''' Currently only purely numeric parasitic suffixes are stripped.<br /> Prefixes and alphanumeric suffixes would be stripped after [https://github.com/dbpedia/extraction-framework/issues/317 issue #317] is implemented</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Rewriting_templateProperty&diff=45456 2015-02-25T18:44:30Z

<p>Chrisahn: /* Intro */</p> <hr /> <div>'''WARNING: Work in progess. The content of this page is largely incorrect.'''<br /> <br /> TODO: Make an EN example using Infobox Politician<br /> --[[User:VladimirAlexiev|VladimirAlexiev]] 12:12, 25 February 2015 (UTC)<br /> <br /> == Intro ==<br /> The basic way the extractor works is like this:<br /> <br /> * data is extracted from template props<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> &lt;s&gt;* the raw data is passed through mappings templateProperty -&gt; ontologyProperty&lt;/s&gt;<br /> <br /> &lt;s&gt;You'd think that templateProperty is the same as the raw prop name. Yeah but not always.&lt;/s&gt;<br /> <br /> The last part (''data is passed through mappings'') is wrong. The mapping based extractor processes the Wikitext source, '''not''' the output of the InfoboxExtractor. A pipeline architecture would make a lot of sense, but that's not how DBpedia works. [[User:Chrisahn|Chrisahn]] 17:54, 25 February 2015 (UTC)<br /> <br /> Here's what actually happens:<br /> <br /> * Wikitext is parsed into an AST (abstract syntax tree)<br /> * The AST is passed to several different extractors according to the configuration<br /> * Each extractor consumes AST and produces triples. The triples are not used as input for any other extractors.<br /> <br /> Here's what the [InfoboxExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/InfoboxExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> <br /> Here's what the [MappingExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/MappingExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST and passed through mappings templateProperty -&gt; ontologyProperty<br /> * these are emitted as generic mapping-based props, eg<br /> ** http://dbpedia.org/ontology/parent for EN, BG and any other language (usual prefix dbo:)<br /> <br /> == Wikipedia Prop Structures ==<br /> Many Wikipedia templates allow creating '''several''' instances of something. <br /> Eg [https://en.wikipedia.org/wiki/Template:Listen Listen] allows a Wikipedia editor to attach up to 11 soundRecording to the subject,<br /> using &quot;parallel&quot; arrays of properties:<br /> * filename, filename1... filename10<br /> * title, title1... title10<br /> * description, description1.. description10<br /> The parallelism is reflected in a numeric suffix.<br /> <br /> Good maps take care of this, by grouping the &quot;parallel props&quot; in separate IntermediateNodeMappings or a similar structure that can produce an &quot;array&quot;.<br /> Eg [http://mappings.dbpedia.org/index.php?title=Mapping_en:Listen&amp;action=edit mapping Listen] has this 11 times:<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = Sound | correspondingProperty = soundRecording | mappings =<br /> {{ PropertyMapping | templateProperty = type | ontologyProperty = dc:type }}<br /> {{ PropertyMapping | templateProperty = filename1 | ontologyProperty = filename }}<br /> {{ PropertyMapping | templateProperty = title1 | ontologyProperty = title }}<br /> {{ PropertyMapping | templateProperty = description1 | ontologyProperty = description }}<br /> }}<br /> &lt;/pre&gt;<br /> <br /> Now consider Politicians. They may hold several Positions, each over several Mandates (they are nasty that way).<br /> For each Position&gt;Mandate (say 5*3=15), there's a bunch of props such as<br /> party, predecessor, successor, colleagues (eg vicePresident, governor...), years the subject came to that position,<br /> years the colleagues came to their respective positions, etc.<br /> <br /> Eg see prop names of [https://bg.wikipedia.org/wiki/Шаблон:Държавник_инфо Държавник_инфо], but that's not the complete story: there's also трети_мандат_* (&quot;third mandate&quot; fields) etc.<br /> * If the 2D data arrays below the photos of Rosen Plevneliev and Angela Merkel don't strike your fancy, check out one of them Socialists that ruled for 40 years: [https://bg.wikipedia.org/wiki/Тодор_Живков Тодор_Живков]<br /> See a full list of props and an incomplete attempt to group them all at [http://mappings.dbpedia.org/index.php?title=Mapping_bg:Държавник_инфо&amp;action=edit Mapping Държавник_инфо].<br /> <br /> Wikidata editors were at a loss to create meaningful two-dimensional parallel arrays of names, so they created parasitc prefixes &amp; suffixes that are not so easy to match up. Eg there are 10 props &quot;предшестванОт&quot;, all mapped to &quot;predecessor&quot; but in different groups:<br /> &lt;pre&gt;<br /> предшестван от<br /> предшестван от2<br /> предшестван от3<br /> втори_мандат_предшестван от<br /> втори_мандат_предшестван от2<br /> втори_мандат_предшестван от3<br /> трети_мандат_предшестван от<br /> ...<br /> &lt;/pre&gt;<br /> <br /> * The prefixes may have any form<br /> * The suffixes are digits, optionally followed by letters<br /> <br /> == Rewriting templateProperty ==<br /> <br /> The parasitic prefixes/suffixes encode important info about the grouping of props,<br /> but that info is not transmitted in any clear way.<br /> <br /> Assume a mapping fragment like this, extracting data for resource bgdbr:Тодор_Живков<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = CareerStation | correspondingProperty = careerStation | mappings = <br /> {{ PropertyMapping | templateProperty = втори_мандат_предшестван от3 | ontologyProperty = predecessor }}<br /> &lt;/pre&gt;<br /> What the extractor '''really''' does is:<br /> <br /> : No it doesn't. See above. [[User:Chrisahn|Chrisahn]] 18:06, 25 February 2015 (UTC)<br /> <br /> * Takes data from the templateProperty provided (as expected)<br /> * Strips parasitic prefixes &amp; suffixes from the templateProperty (maybe unexpected) and converts to camelCase<br /> * Emits the data using the original subject and this '''rewritten''' templateProperty, eg:<br /> bgdbr:Тодор_Живков bgdbp:предшестванОт &lt;data&gt;<br /> * Makes an IntermediateNode and connects it with correspondingProperty (as expected), eg:<br /> bgdbr:Тодор_Живков dbo:careerStation bgdbr:Тодор_Живков__1<br /> * Emits the data using the IntermediateNode and the ontologyProperty as provided (as expected), eg;<br /> bgdbr:Тодор_Живков__1 dbo:predeccessor &lt;data&gt;<br /> <br /> This achieves several goals:<br /> * the general semantics of the raw property is preserved, but not its grouping<br /> * the grouping is preserved by the creation of IntermediateNodes that use mapped properties (if the mapping is good)<br /> <br /> This allows you to make queries such as:<br /> * all predecessors of Тодор_Живков lumped together (regardless of the position). This works even if these raw props are not mapped!<br /> select * {bgdbr:Тодор_Живков bgdbp:предшестванОт ?pred}<br /> * all predecessors of Тодор_Живков, paired with successors, and the corresponding position name (office). (Note: you may want to throw in some OPTIONALs)<br /> select * {bgdbr:Тодор_Живков dbo:careerStation<br /> [dbo:predecessor ?pred; dbo:successor ?succ; dbo:office ?office]}<br /> <br /> Neat!<br /> <br /> '''NOTE''' Currently only purely numeric parasitic suffixes are stripped.<br /> Prefixes and alphanumeric suffixes would be stripped after [https://github.com/dbpedia/extraction-framework/issues/317 issue #317] is implemented</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Rewriting_templateProperty&diff=45455 2015-02-25T18:39:46Z

<p>Chrisahn: </p> <hr /> <div>'''WARNING: Work in progess. The content of this page is largely incorrect.'''<br /> <br /> TODO: Make an EN example using Infobox Politician<br /> --[[User:VladimirAlexiev|VladimirAlexiev]] 12:12, 25 February 2015 (UTC)<br /> <br /> == Intro ==<br /> The basic way the extractor works is like this:<br /> <br /> * data is extracted from template props<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> &lt;s&gt;* the raw data is passed through mappings templateProperty -&gt; ontologyProperty&lt;/s&gt;<br /> <br /> &lt;s&gt;You'd think that templateProperty is the same as the raw prop name. Yeah but not always.&lt;/s&gt;<br /> <br /> The last part (''data is passed through mappings'') is wrong. The mapping based extractor processes the Wikitext source, '''not''' the output of the InfoboxExtractor. A pipeline architecture would make a lot of sense, but that's not how DBpedia works. [[User:Chrisahn|Chrisahn]] 17:54, 25 February 2015 (UTC)<br /> <br /> Here's what actually happens:<br /> <br /> * Wikitext is parsed into an AST<br /> * The AST is passed to several different extractors according to the configuration<br /> * Each extractor consumes AST and produces triples. The triples are not used as input for any other extractors.<br /> <br /> Here's what the [InfoboxExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/InfoboxExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> <br /> Here's what the [MappingExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/MappingExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST and passed through mappings templateProperty -&gt; ontologyProperty<br /> * these are emitted as generic mapping-based props, eg<br /> ** http://dbpedia.org/ontology/parent for EN, BG and any other language (usual prefix dbo:)<br /> <br /> == Wikipedia Prop Structures ==<br /> Many Wikipedia templates allow creating '''several''' instances of something. <br /> Eg [https://en.wikipedia.org/wiki/Template:Listen Listen] allows a Wikipedia editor to attach up to 11 soundRecording to the subject,<br /> using &quot;parallel&quot; arrays of properties:<br /> * filename, filename1... filename10<br /> * title, title1... title10<br /> * description, description1.. description10<br /> The parallelism is reflected in a numeric suffix.<br /> <br /> Good maps take care of this, by grouping the &quot;parallel props&quot; in separate IntermediateNodeMappings or a similar structure that can produce an &quot;array&quot;.<br /> Eg [http://mappings.dbpedia.org/index.php?title=Mapping_en:Listen&amp;action=edit mapping Listen] has this 11 times:<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = Sound | correspondingProperty = soundRecording | mappings =<br /> {{ PropertyMapping | templateProperty = type | ontologyProperty = dc:type }}<br /> {{ PropertyMapping | templateProperty = filename1 | ontologyProperty = filename }}<br /> {{ PropertyMapping | templateProperty = title1 | ontologyProperty = title }}<br /> {{ PropertyMapping | templateProperty = description1 | ontologyProperty = description }}<br /> }}<br /> &lt;/pre&gt;<br /> <br /> Now consider Politicians. They may hold several Positions, each over several Mandates (they are nasty that way).<br /> For each Position&gt;Mandate (say 5*3=15), there's a bunch of props such as<br /> party, predecessor, successor, colleagues (eg vicePresident, governor...), years the subject came to that position,<br /> years the colleagues came to their respective positions, etc.<br /> <br /> Eg see prop names of [https://bg.wikipedia.org/wiki/Шаблон:Държавник_инфо Държавник_инфо], but that's not the complete story: there's also трети_мандат_* (&quot;third mandate&quot; fields) etc.<br /> * If the 2D data arrays below the photos of Rosen Plevneliev and Angela Merkel don't strike your fancy, check out one of them Socialists that ruled for 40 years: [https://bg.wikipedia.org/wiki/Тодор_Живков Тодор_Живков]<br /> See a full list of props and an incomplete attempt to group them all at [http://mappings.dbpedia.org/index.php?title=Mapping_bg:Държавник_инфо&amp;action=edit Mapping Държавник_инфо].<br /> <br /> Wikidata editors were at a loss to create meaningful two-dimensional parallel arrays of names, so they created parasitc prefixes &amp; suffixes that are not so easy to match up. Eg there are 10 props &quot;предшестванОт&quot;, all mapped to &quot;predecessor&quot; but in different groups:<br /> &lt;pre&gt;<br /> предшестван от<br /> предшестван от2<br /> предшестван от3<br /> втори_мандат_предшестван от<br /> втори_мандат_предшестван от2<br /> втори_мандат_предшестван от3<br /> трети_мандат_предшестван от<br /> ...<br /> &lt;/pre&gt;<br /> <br /> * The prefixes may have any form<br /> * The suffixes are digits, optionally followed by letters<br /> <br /> == Rewriting templateProperty ==<br /> <br /> The parasitic prefixes/suffixes encode important info about the grouping of props,<br /> but that info is not transmitted in any clear way.<br /> <br /> Assume a mapping fragment like this, extracting data for resource bgdbr:Тодор_Живков<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = CareerStation | correspondingProperty = careerStation | mappings = <br /> {{ PropertyMapping | templateProperty = втори_мандат_предшестван от3 | ontologyProperty = predecessor }}<br /> &lt;/pre&gt;<br /> What the extractor '''really''' does is:<br /> <br /> : No it doesn't. See above. [[User:Chrisahn|Chrisahn]] 18:06, 25 February 2015 (UTC)<br /> <br /> * Takes data from the templateProperty provided (as expected)<br /> * Strips parasitic prefixes &amp; suffixes from the templateProperty (maybe unexpected) and converts to camelCase<br /> * Emits the data using the original subject and this '''rewritten''' templateProperty, eg:<br /> bgdbr:Тодор_Живков bgdbp:предшестванОт &lt;data&gt;<br /> * Makes an IntermediateNode and connects it with correspondingProperty (as expected), eg:<br /> bgdbr:Тодор_Живков dbo:careerStation bgdbr:Тодор_Живков__1<br /> * Emits the data using the IntermediateNode and the ontologyProperty as provided (as expected), eg;<br /> bgdbr:Тодор_Живков__1 dbo:predeccessor &lt;data&gt;<br /> <br /> This achieves several goals:<br /> * the general semantics of the raw property is preserved, but not its grouping<br /> * the grouping is preserved by the creation of IntermediateNodes that use mapped properties (if the mapping is good)<br /> <br /> This allows you to make queries such as:<br /> * all predecessors of Тодор_Живков lumped together (regardless of the position). This works even if these raw props are not mapped!<br /> select * {bgdbr:Тодор_Живков bgdbp:предшестванОт ?pred}<br /> * all predecessors of Тодор_Живков, paired with successors, and the corresponding position name (office). (Note: you may want to throw in some OPTIONALs)<br /> select * {bgdbr:Тодор_Живков dbo:careerStation<br /> [dbo:predecessor ?pred; dbo:successor ?succ; dbo:office ?office]}<br /> <br /> Neat!<br /> <br /> '''NOTE''' Currently only purely numeric parasitic suffixes are stripped.<br /> Prefixes and alphanumeric suffixes would be stripped after [https://github.com/dbpedia/extraction-framework/issues/317 issue #317] is implemented</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Rewriting_templateProperty&diff=45454 2015-02-25T18:39:00Z

<p>Chrisahn: /* Intro */</p> <hr /> <div>TODO: Make an EN example using Infobox Politician<br /> --[[User:VladimirAlexiev|VladimirAlexiev]] 12:12, 25 February 2015 (UTC)<br /> <br /> == Intro ==<br /> The basic way the extractor works is like this:<br /> <br /> * data is extracted from template props<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> &lt;s&gt;* the raw data is passed through mappings templateProperty -&gt; ontologyProperty&lt;/s&gt;<br /> <br /> &lt;s&gt;You'd think that templateProperty is the same as the raw prop name. Yeah but not always.&lt;/s&gt;<br /> <br /> The last part (''data is passed through mappings'') is wrong. The mapping based extractor processes the Wikitext source, '''not''' the output of the InfoboxExtractor. A pipeline architecture would make a lot of sense, but that's not how DBpedia works. [[User:Chrisahn|Chrisahn]] 17:54, 25 February 2015 (UTC)<br /> <br /> Here's what actually happens:<br /> <br /> * Wikitext is parsed into an AST<br /> * The AST is passed to several different extractors according to the configuration<br /> * Each extractor consumes AST and produces triples. The triples are not used as input for any other extractors.<br /> <br /> Here's what the [InfoboxExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/InfoboxExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> <br /> Here's what the [MappingExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/MappingExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST and passed through mappings templateProperty -&gt; ontologyProperty<br /> * these are emitted as generic mapping-based props, eg<br /> ** http://dbpedia.org/ontology/parent for EN, BG and any other language (usual prefix dbo:)<br /> <br /> == Wikipedia Prop Structures ==<br /> Many Wikipedia templates allow creating '''several''' instances of something. <br /> Eg [https://en.wikipedia.org/wiki/Template:Listen Listen] allows a Wikipedia editor to attach up to 11 soundRecording to the subject,<br /> using &quot;parallel&quot; arrays of properties:<br /> * filename, filename1... filename10<br /> * title, title1... title10<br /> * description, description1.. description10<br /> The parallelism is reflected in a numeric suffix.<br /> <br /> Good maps take care of this, by grouping the &quot;parallel props&quot; in separate IntermediateNodeMappings or a similar structure that can produce an &quot;array&quot;.<br /> Eg [http://mappings.dbpedia.org/index.php?title=Mapping_en:Listen&amp;action=edit mapping Listen] has this 11 times:<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = Sound | correspondingProperty = soundRecording | mappings =<br /> {{ PropertyMapping | templateProperty = type | ontologyProperty = dc:type }}<br /> {{ PropertyMapping | templateProperty = filename1 | ontologyProperty = filename }}<br /> {{ PropertyMapping | templateProperty = title1 | ontologyProperty = title }}<br /> {{ PropertyMapping | templateProperty = description1 | ontologyProperty = description }}<br /> }}<br /> &lt;/pre&gt;<br /> <br /> Now consider Politicians. They may hold several Positions, each over several Mandates (they are nasty that way).<br /> For each Position&gt;Mandate (say 5*3=15), there's a bunch of props such as<br /> party, predecessor, successor, colleagues (eg vicePresident, governor...), years the subject came to that position,<br /> years the colleagues came to their respective positions, etc.<br /> <br /> Eg see prop names of [https://bg.wikipedia.org/wiki/Шаблон:Държавник_инфо Държавник_инфо], but that's not the complete story: there's also трети_мандат_* (&quot;third mandate&quot; fields) etc.<br /> * If the 2D data arrays below the photos of Rosen Plevneliev and Angela Merkel don't strike your fancy, check out one of them Socialists that ruled for 40 years: [https://bg.wikipedia.org/wiki/Тодор_Живков Тодор_Живков]<br /> See a full list of props and an incomplete attempt to group them all at [http://mappings.dbpedia.org/index.php?title=Mapping_bg:Държавник_инфо&amp;action=edit Mapping Държавник_инфо].<br /> <br /> Wikidata editors were at a loss to create meaningful two-dimensional parallel arrays of names, so they created parasitc prefixes &amp; suffixes that are not so easy to match up. Eg there are 10 props &quot;предшестванОт&quot;, all mapped to &quot;predecessor&quot; but in different groups:<br /> &lt;pre&gt;<br /> предшестван от<br /> предшестван от2<br /> предшестван от3<br /> втори_мандат_предшестван от<br /> втори_мандат_предшестван от2<br /> втори_мандат_предшестван от3<br /> трети_мандат_предшестван от<br /> ...<br /> &lt;/pre&gt;<br /> <br /> * The prefixes may have any form<br /> * The suffixes are digits, optionally followed by letters<br /> <br /> == Rewriting templateProperty ==<br /> <br /> The parasitic prefixes/suffixes encode important info about the grouping of props,<br /> but that info is not transmitted in any clear way.<br /> <br /> Assume a mapping fragment like this, extracting data for resource bgdbr:Тодор_Живков<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = CareerStation | correspondingProperty = careerStation | mappings = <br /> {{ PropertyMapping | templateProperty = втори_мандат_предшестван от3 | ontologyProperty = predecessor }}<br /> &lt;/pre&gt;<br /> What the extractor '''really''' does is:<br /> <br /> : No it doesn't. See above. [[User:Chrisahn|Chrisahn]] 18:06, 25 February 2015 (UTC)<br /> <br /> * Takes data from the templateProperty provided (as expected)<br /> * Strips parasitic prefixes &amp; suffixes from the templateProperty (maybe unexpected) and converts to camelCase<br /> * Emits the data using the original subject and this '''rewritten''' templateProperty, eg:<br /> bgdbr:Тодор_Живков bgdbp:предшестванОт &lt;data&gt;<br /> * Makes an IntermediateNode and connects it with correspondingProperty (as expected), eg:<br /> bgdbr:Тодор_Живков dbo:careerStation bgdbr:Тодор_Живков__1<br /> * Emits the data using the IntermediateNode and the ontologyProperty as provided (as expected), eg;<br /> bgdbr:Тодор_Живков__1 dbo:predeccessor &lt;data&gt;<br /> <br /> This achieves several goals:<br /> * the general semantics of the raw property is preserved, but not its grouping<br /> * the grouping is preserved by the creation of IntermediateNodes that use mapped properties (if the mapping is good)<br /> <br /> This allows you to make queries such as:<br /> * all predecessors of Тодор_Живков lumped together (regardless of the position). This works even if these raw props are not mapped!<br /> select * {bgdbr:Тодор_Живков bgdbp:предшестванОт ?pred}<br /> * all predecessors of Тодор_Живков, paired with successors, and the corresponding position name (office). (Note: you may want to throw in some OPTIONALs)<br /> select * {bgdbr:Тодор_Живков dbo:careerStation<br /> [dbo:predecessor ?pred; dbo:successor ?succ; dbo:office ?office]}<br /> <br /> Neat!<br /> <br /> '''NOTE''' Currently only purely numeric parasitic suffixes are stripped.<br /> Prefixes and alphanumeric suffixes would be stripped after [https://github.com/dbpedia/extraction-framework/issues/317 issue #317] is implemented</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Rewriting_templateProperty&diff=45453 2015-02-25T18:38:22Z

<p>Chrisahn: </p> <hr /> <div>TODO: Make an EN example using Infobox Politician<br /> --[[User:VladimirAlexiev|VladimirAlexiev]] 12:12, 25 February 2015 (UTC)<br /> <br /> == Intro ==<br /> The basic way the extractor works is like this:<br /> <br /> * data is extracted from template props<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> &lt;s&gt;* the raw data is passed through mappings templateProperty -&gt; ontologyProperty&lt;/s&gt;<br /> <br /> &lt;s&gt;You'd think that templateProperty is the same as the raw prop name. Yeah but not always.&lt;/s&gt;<br /> <br /> The last part (''data is passed through mappings'') is wrong. The mapping based extractor processes the Wikitext source, '''not''' the output of the InfoboxExtractor. A pipeline architecture would make a lot of sense, but that's not how DBpedia works. [[User:Chrisahn|Chrisahn]] 17:54, 25 February 2015 (UTC)<br /> <br /> Here's what actually happens:<br /> <br /> * Wikitext is parsed into an AST<br /> * The AST is passed to several different extractors according to the configuration<br /> * Each extractor consumes AST and produces triples. The triples are not used as input for any other extractors.<br /> <br /> Here's what the [InfoboxExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/InfoboxExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> <br /> Here's what the [MappingExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/MappingExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST and passed through mappings templateProperty -&gt; ontologyProperty<br /> * these are emitted as generic mapping-based props, eg<br /> ** http://dbpedia.org/ontology/parent for EN, BG and any other language (usual prefix dbo:)<br /> <br /> '''Because it is based on incorrect assumptions, the rest of this page is also largely incorrect.'''<br /> <br /> == Wikipedia Prop Structures ==<br /> Many Wikipedia templates allow creating '''several''' instances of something. <br /> Eg [https://en.wikipedia.org/wiki/Template:Listen Listen] allows a Wikipedia editor to attach up to 11 soundRecording to the subject,<br /> using &quot;parallel&quot; arrays of properties:<br /> * filename, filename1... filename10<br /> * title, title1... title10<br /> * description, description1.. description10<br /> The parallelism is reflected in a numeric suffix.<br /> <br /> Good maps take care of this, by grouping the &quot;parallel props&quot; in separate IntermediateNodeMappings or a similar structure that can produce an &quot;array&quot;.<br /> Eg [http://mappings.dbpedia.org/index.php?title=Mapping_en:Listen&amp;action=edit mapping Listen] has this 11 times:<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = Sound | correspondingProperty = soundRecording | mappings =<br /> {{ PropertyMapping | templateProperty = type | ontologyProperty = dc:type }}<br /> {{ PropertyMapping | templateProperty = filename1 | ontologyProperty = filename }}<br /> {{ PropertyMapping | templateProperty = title1 | ontologyProperty = title }}<br /> {{ PropertyMapping | templateProperty = description1 | ontologyProperty = description }}<br /> }}<br /> &lt;/pre&gt;<br /> <br /> Now consider Politicians. They may hold several Positions, each over several Mandates (they are nasty that way).<br /> For each Position&gt;Mandate (say 5*3=15), there's a bunch of props such as<br /> party, predecessor, successor, colleagues (eg vicePresident, governor...), years the subject came to that position,<br /> years the colleagues came to their respective positions, etc.<br /> <br /> Eg see prop names of [https://bg.wikipedia.org/wiki/Шаблон:Държавник_инфо Държавник_инфо], but that's not the complete story: there's also трети_мандат_* (&quot;third mandate&quot; fields) etc.<br /> * If the 2D data arrays below the photos of Rosen Plevneliev and Angela Merkel don't strike your fancy, check out one of them Socialists that ruled for 40 years: [https://bg.wikipedia.org/wiki/Тодор_Живков Тодор_Живков]<br /> See a full list of props and an incomplete attempt to group them all at [http://mappings.dbpedia.org/index.php?title=Mapping_bg:Държавник_инфо&amp;action=edit Mapping Държавник_инфо].<br /> <br /> Wikidata editors were at a loss to create meaningful two-dimensional parallel arrays of names, so they created parasitc prefixes &amp; suffixes that are not so easy to match up. Eg there are 10 props &quot;предшестванОт&quot;, all mapped to &quot;predecessor&quot; but in different groups:<br /> &lt;pre&gt;<br /> предшестван от<br /> предшестван от2<br /> предшестван от3<br /> втори_мандат_предшестван от<br /> втори_мандат_предшестван от2<br /> втори_мандат_предшестван от3<br /> трети_мандат_предшестван от<br /> ...<br /> &lt;/pre&gt;<br /> <br /> * The prefixes may have any form<br /> * The suffixes are digits, optionally followed by letters<br /> <br /> == Rewriting templateProperty ==<br /> <br /> The parasitic prefixes/suffixes encode important info about the grouping of props,<br /> but that info is not transmitted in any clear way.<br /> <br /> Assume a mapping fragment like this, extracting data for resource bgdbr:Тодор_Живков<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = CareerStation | correspondingProperty = careerStation | mappings = <br /> {{ PropertyMapping | templateProperty = втори_мандат_предшестван от3 | ontologyProperty = predecessor }}<br /> &lt;/pre&gt;<br /> What the extractor '''really''' does is:<br /> <br /> : No it doesn't. See above. [[User:Chrisahn|Chrisahn]] 18:06, 25 February 2015 (UTC)<br /> <br /> * Takes data from the templateProperty provided (as expected)<br /> * Strips parasitic prefixes &amp; suffixes from the templateProperty (maybe unexpected) and converts to camelCase<br /> * Emits the data using the original subject and this '''rewritten''' templateProperty, eg:<br /> bgdbr:Тодор_Живков bgdbp:предшестванОт &lt;data&gt;<br /> * Makes an IntermediateNode and connects it with correspondingProperty (as expected), eg:<br /> bgdbr:Тодор_Живков dbo:careerStation bgdbr:Тодор_Живков__1<br /> * Emits the data using the IntermediateNode and the ontologyProperty as provided (as expected), eg;<br /> bgdbr:Тодор_Живков__1 dbo:predeccessor &lt;data&gt;<br /> <br /> This achieves several goals:<br /> * the general semantics of the raw property is preserved, but not its grouping<br /> * the grouping is preserved by the creation of IntermediateNodes that use mapped properties (if the mapping is good)<br /> <br /> This allows you to make queries such as:<br /> * all predecessors of Тодор_Живков lumped together (regardless of the position). This works even if these raw props are not mapped!<br /> select * {bgdbr:Тодор_Живков bgdbp:предшестванОт ?pred}<br /> * all predecessors of Тодор_Живков, paired with successors, and the corresponding position name (office). (Note: you may want to throw in some OPTIONALs)<br /> select * {bgdbr:Тодор_Живков dbo:careerStation<br /> [dbo:predecessor ?pred; dbo:successor ?succ; dbo:office ?office]}<br /> <br /> Neat!<br /> <br /> '''NOTE''' Currently only purely numeric parasitic suffixes are stripped.<br /> Prefixes and alphanumeric suffixes would be stripped after [https://github.com/dbpedia/extraction-framework/issues/317 issue #317] is implemented</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Rewriting_templateProperty&diff=45452 2015-02-25T18:37:12Z

<p>Chrisahn: /* Intro */</p> <hr /> <div>TODO: Make an EN example using Infobox Politician<br /> --[[User:VladimirAlexiev|VladimirAlexiev]] 12:12, 25 February 2015 (UTC)<br /> <br /> == Intro ==<br /> The basic way the extractor works is like this:<br /> <br /> * data is extracted from template props<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> &lt;s&gt;* the raw data is passed through mappings templateProperty -&gt; ontologyProperty&lt;/s&gt;<br /> <br /> &lt;s&gt;You'd think that templateProperty is the same as the raw prop name. Yeah but not always.&lt;/s&gt;<br /> <br /> The last part (''data is passed through mappings'') is wrong. The mapping based extractor processes the Wikitext source, '''not''' the output of the InfoboxExtractor. A pipeline architecture would make a lot of sense, but that's not how DBpedia works. [[User:Chrisahn|Chrisahn]] 17:54, 25 February 2015 (UTC)<br /> <br /> Here's what actually happens:<br /> <br /> * Wikitext is parsed into an AST<br /> * The AST is passed to several different extractors according to the configuration<br /> * Each extractor consumes AST and produces triples. The triples are not used as input for any other extractors.<br /> <br /> Here's what the [InfoboxExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/InfoboxExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> <br /> Here's what the [MappingExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/MappingExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST and passed through mappings templateProperty -&gt; ontologyProperty<br /> * these are emitted as generic mapping-based props, eg<br /> ** http://dbpedia.org/ontology/parent for EN, BG and any other language (usual prefix dbo:)<br /> <br /> == Wikipedia Prop Structures ==<br /> Many Wikipedia templates allow creating '''several''' instances of something. <br /> Eg [https://en.wikipedia.org/wiki/Template:Listen Listen] allows a Wikipedia editor to attach up to 11 soundRecording to the subject,<br /> using &quot;parallel&quot; arrays of properties:<br /> * filename, filename1... filename10<br /> * title, title1... title10<br /> * description, description1.. description10<br /> The parallelism is reflected in a numeric suffix.<br /> <br /> Good maps take care of this, by grouping the &quot;parallel props&quot; in separate IntermediateNodeMappings or a similar structure that can produce an &quot;array&quot;.<br /> Eg [http://mappings.dbpedia.org/index.php?title=Mapping_en:Listen&amp;action=edit mapping Listen] has this 11 times:<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = Sound | correspondingProperty = soundRecording | mappings =<br /> {{ PropertyMapping | templateProperty = type | ontologyProperty = dc:type }}<br /> {{ PropertyMapping | templateProperty = filename1 | ontologyProperty = filename }}<br /> {{ PropertyMapping | templateProperty = title1 | ontologyProperty = title }}<br /> {{ PropertyMapping | templateProperty = description1 | ontologyProperty = description }}<br /> }}<br /> &lt;/pre&gt;<br /> <br /> Now consider Politicians. They may hold several Positions, each over several Mandates (they are nasty that way).<br /> For each Position&gt;Mandate (say 5*3=15), there's a bunch of props such as<br /> party, predecessor, successor, colleagues (eg vicePresident, governor...), years the subject came to that position,<br /> years the colleagues came to their respective positions, etc.<br /> <br /> Eg see prop names of [https://bg.wikipedia.org/wiki/Шаблон:Държавник_инфо Държавник_инфо], but that's not the complete story: there's also трети_мандат_* (&quot;third mandate&quot; fields) etc.<br /> * If the 2D data arrays below the photos of Rosen Plevneliev and Angela Merkel don't strike your fancy, check out one of them Socialists that ruled for 40 years: [https://bg.wikipedia.org/wiki/Тодор_Живков Тодор_Живков]<br /> See a full list of props and an incomplete attempt to group them all at [http://mappings.dbpedia.org/index.php?title=Mapping_bg:Държавник_инфо&amp;action=edit Mapping Държавник_инфо].<br /> <br /> Wikidata editors were at a loss to create meaningful two-dimensional parallel arrays of names, so they created parasitc prefixes &amp; suffixes that are not so easy to match up. Eg there are 10 props &quot;предшестванОт&quot;, all mapped to &quot;predecessor&quot; but in different groups:<br /> &lt;pre&gt;<br /> предшестван от<br /> предшестван от2<br /> предшестван от3<br /> втори_мандат_предшестван от<br /> втори_мандат_предшестван от2<br /> втори_мандат_предшестван от3<br /> трети_мандат_предшестван от<br /> ...<br /> &lt;/pre&gt;<br /> <br /> * The prefixes may have any form<br /> * The suffixes are digits, optionally followed by letters<br /> <br /> == Rewriting templateProperty ==<br /> <br /> The parasitic prefixes/suffixes encode important info about the grouping of props,<br /> but that info is not transmitted in any clear way.<br /> <br /> Assume a mapping fragment like this, extracting data for resource bgdbr:Тодор_Живков<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = CareerStation | correspondingProperty = careerStation | mappings = <br /> {{ PropertyMapping | templateProperty = втори_мандат_предшестван от3 | ontologyProperty = predecessor }}<br /> &lt;/pre&gt;<br /> What the extractor '''really''' does is:<br /> <br /> : No it doesn't. See above. [[User:Chrisahn|Chrisahn]] 18:06, 25 February 2015 (UTC)<br /> <br /> * Takes data from the templateProperty provided (as expected)<br /> * Strips parasitic prefixes &amp; suffixes from the templateProperty (maybe unexpected) and converts to camelCase<br /> * Emits the data using the original subject and this '''rewritten''' templateProperty, eg:<br /> bgdbr:Тодор_Живков bgdbp:предшестванОт &lt;data&gt;<br /> * Makes an IntermediateNode and connects it with correspondingProperty (as expected), eg:<br /> bgdbr:Тодор_Живков dbo:careerStation bgdbr:Тодор_Живков__1<br /> * Emits the data using the IntermediateNode and the ontologyProperty as provided (as expected), eg;<br /> bgdbr:Тодор_Живков__1 dbo:predeccessor &lt;data&gt;<br /> <br /> This achieves several goals:<br /> * the general semantics of the raw property is preserved, but not its grouping<br /> * the grouping is preserved by the creation of IntermediateNodes that use mapped properties (if the mapping is good)<br /> <br /> This allows you to make queries such as:<br /> * all predecessors of Тодор_Живков lumped together (regardless of the position). This works even if these raw props are not mapped!<br /> select * {bgdbr:Тодор_Живков bgdbp:предшестванОт ?pred}<br /> * all predecessors of Тодор_Живков, paired with successors, and the corresponding position name (office). (Note: you may want to throw in some OPTIONALs)<br /> select * {bgdbr:Тодор_Живков dbo:careerStation<br /> [dbo:predecessor ?pred; dbo:successor ?succ; dbo:office ?office]}<br /> <br /> Neat!<br /> <br /> '''NOTE''' Currently only purely numeric parasitic suffixes are stripped.<br /> Prefixes and alphanumeric suffixes would be stripped after [https://github.com/dbpedia/extraction-framework/issues/317 issue #317] is implemented</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Rewriting_templateProperty&diff=45451 2015-02-25T18:27:16Z

<p>Chrisahn: /* Intro */</p> <hr /> <div>TODO: Make an EN example using Infobox Politician<br /> --[[User:VladimirAlexiev|VladimirAlexiev]] 12:12, 25 February 2015 (UTC)<br /> <br /> == Intro ==<br /> The basic way the extractor works is like this:<br /> <br /> * data is extracted from template props<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> &lt;s&gt;* the raw data is passed through mappings templateProperty -&gt; ontologyProperty&lt;/s&gt;<br /> <br /> &lt;s&gt;You'd think that templateProperty is the same as the raw prop name. Yeah but not always.&lt;/s&gt;<br /> <br /> The last part (''data is passed through mappings'') is wrong. The mapping based extractor processes the Wikitext source, '''not''' the output of the InfoboxExtractor. A pipeline architecture would make a lot of sense, but that's not how DBpedia works [[User:Chrisahn|Chrisahn]] 17:54, 25 February 2015 (UTC)<br /> <br /> Here's what actually happens:<br /> <br /> * Wikitext is parsed into an AST<br /> * The AST is passed to several different extractors according to the configuration<br /> * Each extractor consumes AST and produces triples. The triples are not used as input for any other extractors.<br /> <br /> Here's what the [InfoboxExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/InfoboxExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> <br /> Here's what the [MappingExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/MappingExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST and passed through mappings templateProperty -&gt; ontologyProperty<br /> * these are emitted as generic mapping-based props, eg<br /> ** http://dbpedia.org/ontology/parent for EN, BG and any other language (usual prefix dbo:)<br /> <br /> == Wikipedia Prop Structures ==<br /> Many Wikipedia templates allow creating '''several''' instances of something. <br /> Eg [https://en.wikipedia.org/wiki/Template:Listen Listen] allows a Wikipedia editor to attach up to 11 soundRecording to the subject,<br /> using &quot;parallel&quot; arrays of properties:<br /> * filename, filename1... filename10<br /> * title, title1... title10<br /> * description, description1.. description10<br /> The parallelism is reflected in a numeric suffix.<br /> <br /> Good maps take care of this, by grouping the &quot;parallel props&quot; in separate IntermediateNodeMappings or a similar structure that can produce an &quot;array&quot;.<br /> Eg [http://mappings.dbpedia.org/index.php?title=Mapping_en:Listen&amp;action=edit mapping Listen] has this 11 times:<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = Sound | correspondingProperty = soundRecording | mappings =<br /> {{ PropertyMapping | templateProperty = type | ontologyProperty = dc:type }}<br /> {{ PropertyMapping | templateProperty = filename1 | ontologyProperty = filename }}<br /> {{ PropertyMapping | templateProperty = title1 | ontologyProperty = title }}<br /> {{ PropertyMapping | templateProperty = description1 | ontologyProperty = description }}<br /> }}<br /> &lt;/pre&gt;<br /> <br /> Now consider Politicians. They may hold several Positions, each over several Mandates (they are nasty that way).<br /> For each Position&gt;Mandate (say 5*3=15), there's a bunch of props such as<br /> party, predecessor, successor, colleagues (eg vicePresident, governor...), years the subject came to that position,<br /> years the colleagues came to their respective positions, etc.<br /> <br /> Eg see prop names of [https://bg.wikipedia.org/wiki/Шаблон:Държавник_инфо Държавник_инфо], but that's not the complete story: there's also трети_мандат_* (&quot;third mandate&quot; fields) etc.<br /> * If the 2D data arrays below the photos of Rosen Plevneliev and Angela Merkel don't strike your fancy, check out one of them Socialists that ruled for 40 years: [https://bg.wikipedia.org/wiki/Тодор_Живков Тодор_Живков]<br /> See a full list of props and an incomplete attempt to group them all at [http://mappings.dbpedia.org/index.php?title=Mapping_bg:Държавник_инфо&amp;action=edit Mapping Държавник_инфо].<br /> <br /> Wikidata editors were at a loss to create meaningful two-dimensional parallel arrays of names, so they created parasitc prefixes &amp; suffixes that are not so easy to match up. Eg there are 10 props &quot;предшестванОт&quot;, all mapped to &quot;predecessor&quot; but in different groups:<br /> &lt;pre&gt;<br /> предшестван от<br /> предшестван от2<br /> предшестван от3<br /> втори_мандат_предшестван от<br /> втори_мандат_предшестван от2<br /> втори_мандат_предшестван от3<br /> трети_мандат_предшестван от<br /> ...<br /> &lt;/pre&gt;<br /> <br /> * The prefixes may have any form<br /> * The suffixes are digits, optionally followed by letters<br /> <br /> == Rewriting templateProperty ==<br /> <br /> The parasitic prefixes/suffixes encode important info about the grouping of props,<br /> but that info is not transmitted in any clear way.<br /> <br /> Assume a mapping fragment like this, extracting data for resource bgdbr:Тодор_Живков<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = CareerStation | correspondingProperty = careerStation | mappings = <br /> {{ PropertyMapping | templateProperty = втори_мандат_предшестван от3 | ontologyProperty = predecessor }}<br /> &lt;/pre&gt;<br /> What the extractor '''really''' does is:<br /> <br /> : No it doesn't. See above. [[User:Chrisahn|Chrisahn]] 18:06, 25 February 2015 (UTC)<br /> <br /> * Takes data from the templateProperty provided (as expected)<br /> * Strips parasitic prefixes &amp; suffixes from the templateProperty (maybe unexpected) and converts to camelCase<br /> * Emits the data using the original subject and this '''rewritten''' templateProperty, eg:<br /> bgdbr:Тодор_Живков bgdbp:предшестванОт &lt;data&gt;<br /> * Makes an IntermediateNode and connects it with correspondingProperty (as expected), eg:<br /> bgdbr:Тодор_Живков dbo:careerStation bgdbr:Тодор_Живков__1<br /> * Emits the data using the IntermediateNode and the ontologyProperty as provided (as expected), eg;<br /> bgdbr:Тодор_Живков__1 dbo:predeccessor &lt;data&gt;<br /> <br /> This achieves several goals:<br /> * the general semantics of the raw property is preserved, but not its grouping<br /> * the grouping is preserved by the creation of IntermediateNodes that use mapped properties (if the mapping is good)<br /> <br /> This allows you to make queries such as:<br /> * all predecessors of Тодор_Живков lumped together (regardless of the position). This works even if these raw props are not mapped!<br /> select * {bgdbr:Тодор_Живков bgdbp:предшестванОт ?pred}<br /> * all predecessors of Тодор_Живков, paired with successors, and the corresponding position name (office). (Note: you may want to throw in some OPTIONALs)<br /> select * {bgdbr:Тодор_Живков dbo:careerStation<br /> [dbo:predecessor ?pred; dbo:successor ?succ; dbo:office ?office]}<br /> <br /> Neat!<br /> <br /> '''NOTE''' Currently only purely numeric parasitic suffixes are stripped.<br /> Prefixes and alphanumeric suffixes would be stripped after [https://github.com/dbpedia/extraction-framework/issues/317 issue #317] is implemented</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Rewriting_templateProperty&diff=45450 2015-02-25T18:27:02Z

<p>Chrisahn: /* Intro */</p> <hr /> <div>TODO: Make an EN example using Infobox Politician<br /> --[[User:VladimirAlexiev|VladimirAlexiev]] 12:12, 25 February 2015 (UTC)<br /> <br /> == Intro ==<br /> The basic way the extractor works is like this:<br /> <br /> * data is extracted from template props<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> &lt;s&gt;* the raw data is passed through mappings templateProperty -&gt; ontologyProperty&lt;/s&gt;<br /> <br /> &lt;s&gt;You'd think that templateProperty is the same as the raw prop name. Yeah but not always.&lt;/s&gt;<br /> <br /> : The last part (''data is passed through mappings'') is wrong. The mapping based extractor processes the Wikitext source, '''not''' the output of the InfoboxExtractor. A pipeline architecture would make a lot of sense, but that's not how DBpedia works [[User:Chrisahn|Chrisahn]] 17:54, 25 February 2015 (UTC)<br /> <br /> Here's what actually happens:<br /> <br /> * Wikitext is parsed into an AST<br /> * The AST is passed to several different extractors according to the configuration<br /> * Each extractor consumes AST and produces triples. The triples are not used as input for any other extractors.<br /> <br /> Here's what the [InfoboxExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/InfoboxExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> <br /> Here's what the [MappingExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/MappingExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST and passed through mappings templateProperty -&gt; ontologyProperty<br /> * these are emitted as generic mapping-based props, eg<br /> ** http://dbpedia.org/ontology/parent for EN, BG and any other language (usual prefix dbo:)<br /> <br /> == Wikipedia Prop Structures ==<br /> Many Wikipedia templates allow creating '''several''' instances of something. <br /> Eg [https://en.wikipedia.org/wiki/Template:Listen Listen] allows a Wikipedia editor to attach up to 11 soundRecording to the subject,<br /> using &quot;parallel&quot; arrays of properties:<br /> * filename, filename1... filename10<br /> * title, title1... title10<br /> * description, description1.. description10<br /> The parallelism is reflected in a numeric suffix.<br /> <br /> Good maps take care of this, by grouping the &quot;parallel props&quot; in separate IntermediateNodeMappings or a similar structure that can produce an &quot;array&quot;.<br /> Eg [http://mappings.dbpedia.org/index.php?title=Mapping_en:Listen&amp;action=edit mapping Listen] has this 11 times:<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = Sound | correspondingProperty = soundRecording | mappings =<br /> {{ PropertyMapping | templateProperty = type | ontologyProperty = dc:type }}<br /> {{ PropertyMapping | templateProperty = filename1 | ontologyProperty = filename }}<br /> {{ PropertyMapping | templateProperty = title1 | ontologyProperty = title }}<br /> {{ PropertyMapping | templateProperty = description1 | ontologyProperty = description }}<br /> }}<br /> &lt;/pre&gt;<br /> <br /> Now consider Politicians. They may hold several Positions, each over several Mandates (they are nasty that way).<br /> For each Position&gt;Mandate (say 5*3=15), there's a bunch of props such as<br /> party, predecessor, successor, colleagues (eg vicePresident, governor...), years the subject came to that position,<br /> years the colleagues came to their respective positions, etc.<br /> <br /> Eg see prop names of [https://bg.wikipedia.org/wiki/Шаблон:Държавник_инфо Държавник_инфо], but that's not the complete story: there's also трети_мандат_* (&quot;third mandate&quot; fields) etc.<br /> * If the 2D data arrays below the photos of Rosen Plevneliev and Angela Merkel don't strike your fancy, check out one of them Socialists that ruled for 40 years: [https://bg.wikipedia.org/wiki/Тодор_Живков Тодор_Живков]<br /> See a full list of props and an incomplete attempt to group them all at [http://mappings.dbpedia.org/index.php?title=Mapping_bg:Държавник_инфо&amp;action=edit Mapping Държавник_инфо].<br /> <br /> Wikidata editors were at a loss to create meaningful two-dimensional parallel arrays of names, so they created parasitc prefixes &amp; suffixes that are not so easy to match up. Eg there are 10 props &quot;предшестванОт&quot;, all mapped to &quot;predecessor&quot; but in different groups:<br /> &lt;pre&gt;<br /> предшестван от<br /> предшестван от2<br /> предшестван от3<br /> втори_мандат_предшестван от<br /> втори_мандат_предшестван от2<br /> втори_мандат_предшестван от3<br /> трети_мандат_предшестван от<br /> ...<br /> &lt;/pre&gt;<br /> <br /> * The prefixes may have any form<br /> * The suffixes are digits, optionally followed by letters<br /> <br /> == Rewriting templateProperty ==<br /> <br /> The parasitic prefixes/suffixes encode important info about the grouping of props,<br /> but that info is not transmitted in any clear way.<br /> <br /> Assume a mapping fragment like this, extracting data for resource bgdbr:Тодор_Живков<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = CareerStation | correspondingProperty = careerStation | mappings = <br /> {{ PropertyMapping | templateProperty = втори_мандат_предшестван от3 | ontologyProperty = predecessor }}<br /> &lt;/pre&gt;<br /> What the extractor '''really''' does is:<br /> <br /> : No it doesn't. See above. [[User:Chrisahn|Chrisahn]] 18:06, 25 February 2015 (UTC)<br /> <br /> * Takes data from the templateProperty provided (as expected)<br /> * Strips parasitic prefixes &amp; suffixes from the templateProperty (maybe unexpected) and converts to camelCase<br /> * Emits the data using the original subject and this '''rewritten''' templateProperty, eg:<br /> bgdbr:Тодор_Живков bgdbp:предшестванОт &lt;data&gt;<br /> * Makes an IntermediateNode and connects it with correspondingProperty (as expected), eg:<br /> bgdbr:Тодор_Живков dbo:careerStation bgdbr:Тодор_Живков__1<br /> * Emits the data using the IntermediateNode and the ontologyProperty as provided (as expected), eg;<br /> bgdbr:Тодор_Живков__1 dbo:predeccessor &lt;data&gt;<br /> <br /> This achieves several goals:<br /> * the general semantics of the raw property is preserved, but not its grouping<br /> * the grouping is preserved by the creation of IntermediateNodes that use mapped properties (if the mapping is good)<br /> <br /> This allows you to make queries such as:<br /> * all predecessors of Тодор_Живков lumped together (regardless of the position). This works even if these raw props are not mapped!<br /> select * {bgdbr:Тодор_Живков bgdbp:предшестванОт ?pred}<br /> * all predecessors of Тодор_Живков, paired with successors, and the corresponding position name (office). (Note: you may want to throw in some OPTIONALs)<br /> select * {bgdbr:Тодор_Живков dbo:careerStation<br /> [dbo:predecessor ?pred; dbo:successor ?succ; dbo:office ?office]}<br /> <br /> Neat!<br /> <br /> '''NOTE''' Currently only purely numeric parasitic suffixes are stripped.<br /> Prefixes and alphanumeric suffixes would be stripped after [https://github.com/dbpedia/extraction-framework/issues/317 issue #317] is implemented</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Rewriting_templateProperty&diff=45449 2015-02-25T18:06:55Z

<p>Chrisahn: /* Rewriting templateProperty */</p> <hr /> <div>TODO: Make an EN example using Infobox Politician<br /> --[[User:VladimirAlexiev|VladimirAlexiev]] 12:12, 25 February 2015 (UTC)<br /> <br /> == Intro ==<br /> The basic way the extractor works is like this:<br /> <br /> * data is extracted from template props<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> &lt;s&gt;* the raw data is passed through mappings templateProperty -&gt; ontologyProperty&lt;/s&gt;<br /> <br /> You'd think that templateProperty is the same as the raw prop name. Yeah but not always.<br /> <br /> : The last part (''data is passed through mappings'') is wrong. The mapping based extractor processes the Wikitext source, '''not''' the output of the InfoboxExtractor. A pipeline architecture would make a lot of sense, but that's not how DBpedia works [[User:Chrisahn|Chrisahn]] 17:54, 25 February 2015 (UTC)<br /> <br /> Here's what actually happens:<br /> <br /> * Wikitext is parsed into an AST<br /> * The AST is passed to several different extractors according to the configuration<br /> * Each extractor consumes AST and produces triples. The triples are not used as input for any other extractors.<br /> <br /> Here's what the [InfoboxExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/InfoboxExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> <br /> Here's what the [MappingExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/MappingExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST and passed through mappings templateProperty -&gt; ontologyProperty<br /> * these are emitted as generic mapping-based props, eg<br /> ** http://dbpedia.org/ontology/parent for EN, BG and any other language (usual prefix dbo:)<br /> <br /> == Wikipedia Prop Structures ==<br /> Many Wikipedia templates allow creating '''several''' instances of something. <br /> Eg [https://en.wikipedia.org/wiki/Template:Listen Listen] allows a Wikipedia editor to attach up to 11 soundRecording to the subject,<br /> using &quot;parallel&quot; arrays of properties:<br /> * filename, filename1... filename10<br /> * title, title1... title10<br /> * description, description1.. description10<br /> The parallelism is reflected in a numeric suffix.<br /> <br /> Good maps take care of this, by grouping the &quot;parallel props&quot; in separate IntermediateNodeMappings or a similar structure that can produce an &quot;array&quot;.<br /> Eg [http://mappings.dbpedia.org/index.php?title=Mapping_en:Listen&amp;action=edit mapping Listen] has this 11 times:<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = Sound | correspondingProperty = soundRecording | mappings =<br /> {{ PropertyMapping | templateProperty = type | ontologyProperty = dc:type }}<br /> {{ PropertyMapping | templateProperty = filename1 | ontologyProperty = filename }}<br /> {{ PropertyMapping | templateProperty = title1 | ontologyProperty = title }}<br /> {{ PropertyMapping | templateProperty = description1 | ontologyProperty = description }}<br /> }}<br /> &lt;/pre&gt;<br /> <br /> Now consider Politicians. They may hold several Positions, each over several Mandates (they are nasty that way).<br /> For each Position&gt;Mandate (say 5*3=15), there's a bunch of props such as<br /> party, predecessor, successor, colleagues (eg vicePresident, governor...), years the subject came to that position,<br /> years the colleagues came to their respective positions, etc.<br /> <br /> Eg see prop names of [https://bg.wikipedia.org/wiki/Шаблон:Държавник_инфо Държавник_инфо], but that's not the complete story: there's also трети_мандат_* (&quot;third mandate&quot; fields) etc.<br /> * If the 2D data arrays below the photos of Rosen Plevneliev and Angela Merkel don't strike your fancy, check out one of them Socialists that ruled for 40 years: [https://bg.wikipedia.org/wiki/Тодор_Живков Тодор_Живков]<br /> See a full list of props and an incomplete attempt to group them all at [http://mappings.dbpedia.org/index.php?title=Mapping_bg:Държавник_инфо&amp;action=edit Mapping Държавник_инфо].<br /> <br /> Wikidata editors were at a loss to create meaningful two-dimensional parallel arrays of names, so they created parasitc prefixes &amp; suffixes that are not so easy to match up. Eg there are 10 props &quot;предшестванОт&quot;, all mapped to &quot;predecessor&quot; but in different groups:<br /> &lt;pre&gt;<br /> предшестван от<br /> предшестван от2<br /> предшестван от3<br /> втори_мандат_предшестван от<br /> втори_мандат_предшестван от2<br /> втори_мандат_предшестван от3<br /> трети_мандат_предшестван от<br /> ...<br /> &lt;/pre&gt;<br /> <br /> * The prefixes may have any form<br /> * The suffixes are digits, optionally followed by letters<br /> <br /> == Rewriting templateProperty ==<br /> <br /> The parasitic prefixes/suffixes encode important info about the grouping of props,<br /> but that info is not transmitted in any clear way.<br /> <br /> Assume a mapping fragment like this, extracting data for resource bgdbr:Тодор_Живков<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = CareerStation | correspondingProperty = careerStation | mappings = <br /> {{ PropertyMapping | templateProperty = втори_мандат_предшестван от3 | ontologyProperty = predecessor }}<br /> &lt;/pre&gt;<br /> What the extractor '''really''' does is:<br /> <br /> : No it doesn't. See above. [[User:Chrisahn|Chrisahn]] 18:06, 25 February 2015 (UTC)<br /> <br /> * Takes data from the templateProperty provided (as expected)<br /> * Strips parasitic prefixes &amp; suffixes from the templateProperty (maybe unexpected) and converts to camelCase<br /> * Emits the data using the original subject and this '''rewritten''' templateProperty, eg:<br /> bgdbr:Тодор_Живков bgdbp:предшестванОт &lt;data&gt;<br /> * Makes an IntermediateNode and connects it with correspondingProperty (as expected), eg:<br /> bgdbr:Тодор_Живков dbo:careerStation bgdbr:Тодор_Живков__1<br /> * Emits the data using the IntermediateNode and the ontologyProperty as provided (as expected), eg;<br /> bgdbr:Тодор_Живков__1 dbo:predeccessor &lt;data&gt;<br /> <br /> This achieves several goals:<br /> * the general semantics of the raw property is preserved, but not its grouping<br /> * the grouping is preserved by the creation of IntermediateNodes that use mapped properties (if the mapping is good)<br /> <br /> This allows you to make queries such as:<br /> * all predecessors of Тодор_Живков lumped together (regardless of the position). This works even if these raw props are not mapped!<br /> select * {bgdbr:Тодор_Живков bgdbp:предшестванОт ?pred}<br /> * all predecessors of Тодор_Живков, paired with successors, and the corresponding position name (office). (Note: you may want to throw in some OPTIONALs)<br /> select * {bgdbr:Тодор_Живков dbo:careerStation<br /> [dbo:predecessor ?pred; dbo:successor ?succ; dbo:office ?office]}<br /> <br /> Neat!<br /> <br /> '''NOTE''' Currently only purely numeric parasitic suffixes are stripped.<br /> Prefixes and alphanumeric suffixes would be stripped after [https://github.com/dbpedia/extraction-framework/issues/317 issue #317] is implemented</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Rewriting_templateProperty&diff=45448 2015-02-25T18:05:47Z

<p>Chrisahn: /* Intro */</p> <hr /> <div>TODO: Make an EN example using Infobox Politician<br /> --[[User:VladimirAlexiev|VladimirAlexiev]] 12:12, 25 February 2015 (UTC)<br /> <br /> == Intro ==<br /> The basic way the extractor works is like this:<br /> <br /> * data is extracted from template props<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> &lt;s&gt;* the raw data is passed through mappings templateProperty -&gt; ontologyProperty&lt;/s&gt;<br /> <br /> You'd think that templateProperty is the same as the raw prop name. Yeah but not always.<br /> <br /> : The last part (''data is passed through mappings'') is wrong. The mapping based extractor processes the Wikitext source, '''not''' the output of the InfoboxExtractor. A pipeline architecture would make a lot of sense, but that's not how DBpedia works [[User:Chrisahn|Chrisahn]] 17:54, 25 February 2015 (UTC)<br /> <br /> Here's what actually happens:<br /> <br /> * Wikitext is parsed into an AST<br /> * The AST is passed to several different extractors according to the configuration<br /> * Each extractor consumes AST and produces triples. The triples are not used as input for any other extractors.<br /> <br /> Here's what the [InfoboxExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/InfoboxExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> <br /> Here's what the [MappingExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/MappingExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST and passed through mappings templateProperty -&gt; ontologyProperty<br /> * these are emitted as generic mapping-based props, eg<br /> ** http://dbpedia.org/ontology/parent for EN, BG and any other language (usual prefix dbo:)<br /> <br /> == Wikipedia Prop Structures ==<br /> Many Wikipedia templates allow creating '''several''' instances of something. <br /> Eg [https://en.wikipedia.org/wiki/Template:Listen Listen] allows a Wikipedia editor to attach up to 11 soundRecording to the subject,<br /> using &quot;parallel&quot; arrays of properties:<br /> * filename, filename1... filename10<br /> * title, title1... title10<br /> * description, description1.. description10<br /> The parallelism is reflected in a numeric suffix.<br /> <br /> Good maps take care of this, by grouping the &quot;parallel props&quot; in separate IntermediateNodeMappings or a similar structure that can produce an &quot;array&quot;.<br /> Eg [http://mappings.dbpedia.org/index.php?title=Mapping_en:Listen&amp;action=edit mapping Listen] has this 11 times:<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = Sound | correspondingProperty = soundRecording | mappings =<br /> {{ PropertyMapping | templateProperty = type | ontologyProperty = dc:type }}<br /> {{ PropertyMapping | templateProperty = filename1 | ontologyProperty = filename }}<br /> {{ PropertyMapping | templateProperty = title1 | ontologyProperty = title }}<br /> {{ PropertyMapping | templateProperty = description1 | ontologyProperty = description }}<br /> }}<br /> &lt;/pre&gt;<br /> <br /> Now consider Politicians. They may hold several Positions, each over several Mandates (they are nasty that way).<br /> For each Position&gt;Mandate (say 5*3=15), there's a bunch of props such as<br /> party, predecessor, successor, colleagues (eg vicePresident, governor...), years the subject came to that position,<br /> years the colleagues came to their respective positions, etc.<br /> <br /> Eg see prop names of [https://bg.wikipedia.org/wiki/Шаблон:Държавник_инфо Държавник_инфо], but that's not the complete story: there's also трети_мандат_* (&quot;third mandate&quot; fields) etc.<br /> * If the 2D data arrays below the photos of Rosen Plevneliev and Angela Merkel don't strike your fancy, check out one of them Socialists that ruled for 40 years: [https://bg.wikipedia.org/wiki/Тодор_Живков Тодор_Живков]<br /> See a full list of props and an incomplete attempt to group them all at [http://mappings.dbpedia.org/index.php?title=Mapping_bg:Държавник_инфо&amp;action=edit Mapping Държавник_инфо].<br /> <br /> Wikidata editors were at a loss to create meaningful two-dimensional parallel arrays of names, so they created parasitc prefixes &amp; suffixes that are not so easy to match up. Eg there are 10 props &quot;предшестванОт&quot;, all mapped to &quot;predecessor&quot; but in different groups:<br /> &lt;pre&gt;<br /> предшестван от<br /> предшестван от2<br /> предшестван от3<br /> втори_мандат_предшестван от<br /> втори_мандат_предшестван от2<br /> втори_мандат_предшестван от3<br /> трети_мандат_предшестван от<br /> ...<br /> &lt;/pre&gt;<br /> <br /> * The prefixes may have any form<br /> * The suffixes are digits, optionally followed by letters<br /> <br /> == Rewriting templateProperty ==<br /> <br /> The parasitic prefixes/suffixes encode important info about the grouping of props,<br /> but that info is not transmitted in any clear way.<br /> <br /> Assume a mapping fragment like this, extracting data for resource bgdbr:Тодор_Живков<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = CareerStation | correspondingProperty = careerStation | mappings = <br /> {{ PropertyMapping | templateProperty = втори_мандат_предшестван от3 | ontologyProperty = predecessor }}<br /> &lt;/pre&gt;<br /> What the extractor '''really''' does is:<br /> * Takes data from the templateProperty provided (as expected)<br /> * Strips parasitic prefixes &amp; suffixes from the templateProperty (maybe unexpected) and converts to camelCase<br /> * Emits the data using the original subject and this '''rewritten''' templateProperty, eg:<br /> bgdbr:Тодор_Живков bgdbp:предшестванОт &lt;data&gt;<br /> * Makes an IntermediateNode and connects it with correspondingProperty (as expected), eg:<br /> bgdbr:Тодор_Живков dbo:careerStation bgdbr:Тодор_Живков__1<br /> * Emits the data using the IntermediateNode and the ontologyProperty as provided (as expected), eg;<br /> bgdbr:Тодор_Живков__1 dbo:predeccessor &lt;data&gt;<br /> <br /> This achieves several goals:<br /> * the general semantics of the raw property is preserved, but not its grouping<br /> * the grouping is preserved by the creation of IntermediateNodes that use mapped properties (if the mapping is good)<br /> <br /> This allows you to make queries such as:<br /> * all predecessors of Тодор_Живков lumped together (regardless of the position). This works even if these raw props are not mapped!<br /> select * {bgdbr:Тодор_Живков bgdbp:предшестванОт ?pred}<br /> * all predecessors of Тодор_Живков, paired with successors, and the corresponding position name (office). (Note: you may want to throw in some OPTIONALs)<br /> select * {bgdbr:Тодор_Живков dbo:careerStation<br /> [dbo:predecessor ?pred; dbo:successor ?succ; dbo:office ?office]}<br /> <br /> Neat!<br /> <br /> '''NOTE''' Currently only purely numeric parasitic suffixes are stripped.<br /> Prefixes and alphanumeric suffixes would be stripped after [https://github.com/dbpedia/extraction-framework/issues/317 issue #317] is implemented</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Rewriting_templateProperty&diff=45447 2015-02-25T18:05:01Z

<p>Chrisahn: /* Intro */</p> <hr /> <div>TODO: Make an EN example using Infobox Politician<br /> --[[User:VladimirAlexiev|VladimirAlexiev]] 12:12, 25 February 2015 (UTC)<br /> <br /> == Intro ==<br /> The basic way the extractor works is like this:<br /> <br /> * data is extracted from template props<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> * the raw data is passed through mappings templateProperty -&gt; ontologyProperty<br /> <br /> You'd think that templateProperty is the same as the raw prop name. Yeah but not always.<br /> <br /> : The last part (''data is passed through mappings'') is wrong. The mapping based extractor processes the Wikitext source, '''not''' the output of the InfoboxExtractor. A pipeline architecture would make a lot of sense, but that's not how DBpedia works [[User:Chrisahn|Chrisahn]] 17:54, 25 February 2015 (UTC)<br /> <br /> Here's what actually happens:<br /> <br /> * Wikitext is parsed into an AST<br /> * The AST is passed to several different extractors according to the configuration<br /> * Each extractor consumes AST and produces triples. The triples are not used as input for any other extractors.<br /> <br /> Here's what the [InfoboxExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/InfoboxExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> <br /> Here's what the [MappingExtractor https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/mappings/MappingExtractor.scala] does:<br /> <br /> * data is extracted from template props in the AST and passed through mappings templateProperty -&gt; ontologyProperty<br /> * these are emitted as generic mapping-based props, eg<br /> ** http://dbpedia.org/ontology/parent for EN, BG and any other language (usual prefix dbo:)<br /> <br /> == Wikipedia Prop Structures ==<br /> Many Wikipedia templates allow creating '''several''' instances of something. <br /> Eg [https://en.wikipedia.org/wiki/Template:Listen Listen] allows a Wikipedia editor to attach up to 11 soundRecording to the subject,<br /> using &quot;parallel&quot; arrays of properties:<br /> * filename, filename1... filename10<br /> * title, title1... title10<br /> * description, description1.. description10<br /> The parallelism is reflected in a numeric suffix.<br /> <br /> Good maps take care of this, by grouping the &quot;parallel props&quot; in separate IntermediateNodeMappings or a similar structure that can produce an &quot;array&quot;.<br /> Eg [http://mappings.dbpedia.org/index.php?title=Mapping_en:Listen&amp;action=edit mapping Listen] has this 11 times:<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = Sound | correspondingProperty = soundRecording | mappings =<br /> {{ PropertyMapping | templateProperty = type | ontologyProperty = dc:type }}<br /> {{ PropertyMapping | templateProperty = filename1 | ontologyProperty = filename }}<br /> {{ PropertyMapping | templateProperty = title1 | ontologyProperty = title }}<br /> {{ PropertyMapping | templateProperty = description1 | ontologyProperty = description }}<br /> }}<br /> &lt;/pre&gt;<br /> <br /> Now consider Politicians. They may hold several Positions, each over several Mandates (they are nasty that way).<br /> For each Position&gt;Mandate (say 5*3=15), there's a bunch of props such as<br /> party, predecessor, successor, colleagues (eg vicePresident, governor...), years the subject came to that position,<br /> years the colleagues came to their respective positions, etc.<br /> <br /> Eg see prop names of [https://bg.wikipedia.org/wiki/Шаблон:Държавник_инфо Държавник_инфо], but that's not the complete story: there's also трети_мандат_* (&quot;third mandate&quot; fields) etc.<br /> * If the 2D data arrays below the photos of Rosen Plevneliev and Angela Merkel don't strike your fancy, check out one of them Socialists that ruled for 40 years: [https://bg.wikipedia.org/wiki/Тодор_Живков Тодор_Живков]<br /> See a full list of props and an incomplete attempt to group them all at [http://mappings.dbpedia.org/index.php?title=Mapping_bg:Държавник_инфо&amp;action=edit Mapping Държавник_инфо].<br /> <br /> Wikidata editors were at a loss to create meaningful two-dimensional parallel arrays of names, so they created parasitc prefixes &amp; suffixes that are not so easy to match up. Eg there are 10 props &quot;предшестванОт&quot;, all mapped to &quot;predecessor&quot; but in different groups:<br /> &lt;pre&gt;<br /> предшестван от<br /> предшестван от2<br /> предшестван от3<br /> втори_мандат_предшестван от<br /> втори_мандат_предшестван от2<br /> втори_мандат_предшестван от3<br /> трети_мандат_предшестван от<br /> ...<br /> &lt;/pre&gt;<br /> <br /> * The prefixes may have any form<br /> * The suffixes are digits, optionally followed by letters<br /> <br /> == Rewriting templateProperty ==<br /> <br /> The parasitic prefixes/suffixes encode important info about the grouping of props,<br /> but that info is not transmitted in any clear way.<br /> <br /> Assume a mapping fragment like this, extracting data for resource bgdbr:Тодор_Живков<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = CareerStation | correspondingProperty = careerStation | mappings = <br /> {{ PropertyMapping | templateProperty = втори_мандат_предшестван от3 | ontologyProperty = predecessor }}<br /> &lt;/pre&gt;<br /> What the extractor '''really''' does is:<br /> * Takes data from the templateProperty provided (as expected)<br /> * Strips parasitic prefixes &amp; suffixes from the templateProperty (maybe unexpected) and converts to camelCase<br /> * Emits the data using the original subject and this '''rewritten''' templateProperty, eg:<br /> bgdbr:Тодор_Живков bgdbp:предшестванОт &lt;data&gt;<br /> * Makes an IntermediateNode and connects it with correspondingProperty (as expected), eg:<br /> bgdbr:Тодор_Живков dbo:careerStation bgdbr:Тодор_Живков__1<br /> * Emits the data using the IntermediateNode and the ontologyProperty as provided (as expected), eg;<br /> bgdbr:Тодор_Живков__1 dbo:predeccessor &lt;data&gt;<br /> <br /> This achieves several goals:<br /> * the general semantics of the raw property is preserved, but not its grouping<br /> * the grouping is preserved by the creation of IntermediateNodes that use mapped properties (if the mapping is good)<br /> <br /> This allows you to make queries such as:<br /> * all predecessors of Тодор_Живков lumped together (regardless of the position). This works even if these raw props are not mapped!<br /> select * {bgdbr:Тодор_Живков bgdbp:предшестванОт ?pred}<br /> * all predecessors of Тодор_Живков, paired with successors, and the corresponding position name (office). (Note: you may want to throw in some OPTIONALs)<br /> select * {bgdbr:Тодор_Живков dbo:careerStation<br /> [dbo:predecessor ?pred; dbo:successor ?succ; dbo:office ?office]}<br /> <br /> Neat!<br /> <br /> '''NOTE''' Currently only purely numeric parasitic suffixes are stripped.<br /> Prefixes and alphanumeric suffixes would be stripped after [https://github.com/dbpedia/extraction-framework/issues/317 issue #317] is implemented</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Rewriting_templateProperty&diff=45446 2015-02-25T17:57:26Z

<p>Chrisahn: /* Intro */</p> <hr /> <div>TODO: Make an EN example using Infobox Politician<br /> --[[User:VladimirAlexiev|VladimirAlexiev]] 12:12, 25 February 2015 (UTC)<br /> <br /> == Intro ==<br /> The basic way the extractor works is like this:<br /> <br /> * data is extracted from template props<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> * the raw data is passed through mappings templateProperty -&gt; ontologyProperty<br /> <br /> You'd think that templateProperty is the same as the raw prop name. Yeah but not always.<br /> <br /> The last part (''data is passed through mappings'') is wrong. The mapping based extractor processes the Wikitext source, '''not''' the output of the InfoboxExtractor. A pipeline architecture would make a lot of sense, but that's not how DBpedia works [[User:Chrisahn|Chrisahn]] 17:54, 25 February 2015 (UTC)<br /> <br /> == Wikipedia Prop Structures ==<br /> Many Wikipedia templates allow creating '''several''' instances of something. <br /> Eg [https://en.wikipedia.org/wiki/Template:Listen Listen] allows a Wikipedia editor to attach up to 11 soundRecording to the subject,<br /> using &quot;parallel&quot; arrays of properties:<br /> * filename, filename1... filename10<br /> * title, title1... title10<br /> * description, description1.. description10<br /> The parallelism is reflected in a numeric suffix.<br /> <br /> Good maps take care of this, by grouping the &quot;parallel props&quot; in separate IntermediateNodeMappings or a similar structure that can produce an &quot;array&quot;.<br /> Eg [http://mappings.dbpedia.org/index.php?title=Mapping_en:Listen&amp;action=edit mapping Listen] has this 11 times:<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = Sound | correspondingProperty = soundRecording | mappings =<br /> {{ PropertyMapping | templateProperty = type | ontologyProperty = dc:type }}<br /> {{ PropertyMapping | templateProperty = filename1 | ontologyProperty = filename }}<br /> {{ PropertyMapping | templateProperty = title1 | ontologyProperty = title }}<br /> {{ PropertyMapping | templateProperty = description1 | ontologyProperty = description }}<br /> }}<br /> &lt;/pre&gt;<br /> <br /> Now consider Politicians. They may hold several Positions, each over several Mandates (they are nasty that way).<br /> For each Position&gt;Mandate (say 5*3=15), there's a bunch of props such as<br /> party, predecessor, successor, colleagues (eg vicePresident, governor...), years the subject came to that position,<br /> years the colleagues came to their respective positions, etc.<br /> <br /> Eg see prop names of [https://bg.wikipedia.org/wiki/Шаблон:Държавник_инфо Държавник_инфо], but that's not the complete story: there's also трети_мандат_* (&quot;third mandate&quot; fields) etc.<br /> * If the 2D data arrays below the photos of Rosen Plevneliev and Angela Merkel don't strike your fancy, check out one of them Socialists that ruled for 40 years: [https://bg.wikipedia.org/wiki/Тодор_Живков Тодор_Живков]<br /> See a full list of props and an incomplete attempt to group them all at [http://mappings.dbpedia.org/index.php?title=Mapping_bg:Държавник_инфо&amp;action=edit Mapping Държавник_инфо].<br /> <br /> Wikidata editors were at a loss to create meaningful two-dimensional parallel arrays of names, so they created parasitc prefixes &amp; suffixes that are not so easy to match up. Eg there are 10 props &quot;предшестванОт&quot;, all mapped to &quot;predecessor&quot; but in different groups:<br /> &lt;pre&gt;<br /> предшестван от<br /> предшестван от2<br /> предшестван от3<br /> втори_мандат_предшестван от<br /> втори_мандат_предшестван от2<br /> втори_мандат_предшестван от3<br /> трети_мандат_предшестван от<br /> ...<br /> &lt;/pre&gt;<br /> <br /> * The prefixes may have any form<br /> * The suffixes are digits, optionally followed by letters<br /> <br /> == Rewriting templateProperty ==<br /> <br /> The parasitic prefixes/suffixes encode important info about the grouping of props,<br /> but that info is not transmitted in any clear way.<br /> <br /> Assume a mapping fragment like this, extracting data for resource bgdbr:Тодор_Живков<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = CareerStation | correspondingProperty = careerStation | mappings = <br /> {{ PropertyMapping | templateProperty = втори_мандат_предшестван от3 | ontologyProperty = predecessor }}<br /> &lt;/pre&gt;<br /> What the extractor '''really''' does is:<br /> * Takes data from the templateProperty provided (as expected)<br /> * Strips parasitic prefixes &amp; suffixes from the templateProperty (maybe unexpected) and converts to camelCase<br /> * Emits the data using the original subject and this '''rewritten''' templateProperty, eg:<br /> bgdbr:Тодор_Живков bgdbp:предшестванОт &lt;data&gt;<br /> * Makes an IntermediateNode and connects it with correspondingProperty (as expected), eg:<br /> bgdbr:Тодор_Живков dbo:careerStation bgdbr:Тодор_Живков__1<br /> * Emits the data using the IntermediateNode and the ontologyProperty as provided (as expected), eg;<br /> bgdbr:Тодор_Живков__1 dbo:predeccessor &lt;data&gt;<br /> <br /> This achieves several goals:<br /> * the general semantics of the raw property is preserved, but not its grouping<br /> * the grouping is preserved by the creation of IntermediateNodes that use mapped properties (if the mapping is good)<br /> <br /> This allows you to make queries such as:<br /> * all predecessors of Тодор_Живков lumped together (regardless of the position). This works even if these raw props are not mapped!<br /> select * {bgdbr:Тодор_Живков bgdbp:предшестванОт ?pred}<br /> * all predecessors of Тодор_Живков, paired with successors, and the corresponding position name (office). (Note: you may want to throw in some OPTIONALs)<br /> select * {bgdbr:Тодор_Живков dbo:careerStation<br /> [dbo:predecessor ?pred; dbo:successor ?succ; dbo:office ?office]}<br /> <br /> Neat!<br /> <br /> '''NOTE''' Currently only purely numeric parasitic suffixes are stripped.<br /> Prefixes and alphanumeric suffixes would be stripped after [https://github.com/dbpedia/extraction-framework/issues/317 issue #317] is implemented</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Rewriting_templateProperty&diff=45445 2015-02-25T17:54:15Z

<p>Chrisahn: /* Intro */</p> <hr /> <div>TODO: Make an EN example using Infobox Politician<br /> --[[User:VladimirAlexiev|VladimirAlexiev]] 12:12, 25 February 2015 (UTC)<br /> <br /> == Intro ==<br /> The basic way the extractor works is like this:<br /> <br /> * data is extracted from template props<br /> * these are emitted as language-specific '''raw''' props, eg<br /> ** http://dbpedia.org/property/parent for EN (usual prefix [http://prefix.cc/dbp dbp:])<br /> ** http://bg.dbpedia.org/property/родител for BG (usual prefix [http://prefix.cc/bgdbp bgdbp:]<br /> * the raw data is passed through mappings templateProperty -&gt; ontologyProperty<br /> <br /> The last part is wrong. [[User:Chrisahn|Chrisahn]] 17:54, 25 February 2015 (UTC)<br /> <br /> You'd think that templateProperty is the same as the raw prop name. Yeah but not always.<br /> <br /> == Wikipedia Prop Structures ==<br /> Many Wikipedia templates allow creating '''several''' instances of something. <br /> Eg [https://en.wikipedia.org/wiki/Template:Listen Listen] allows a Wikipedia editor to attach up to 11 soundRecording to the subject,<br /> using &quot;parallel&quot; arrays of properties:<br /> * filename, filename1... filename10<br /> * title, title1... title10<br /> * description, description1.. description10<br /> The parallelism is reflected in a numeric suffix.<br /> <br /> Good maps take care of this, by grouping the &quot;parallel props&quot; in separate IntermediateNodeMappings or a similar structure that can produce an &quot;array&quot;.<br /> Eg [http://mappings.dbpedia.org/index.php?title=Mapping_en:Listen&amp;action=edit mapping Listen] has this 11 times:<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = Sound | correspondingProperty = soundRecording | mappings =<br /> {{ PropertyMapping | templateProperty = type | ontologyProperty = dc:type }}<br /> {{ PropertyMapping | templateProperty = filename1 | ontologyProperty = filename }}<br /> {{ PropertyMapping | templateProperty = title1 | ontologyProperty = title }}<br /> {{ PropertyMapping | templateProperty = description1 | ontologyProperty = description }}<br /> }}<br /> &lt;/pre&gt;<br /> <br /> Now consider Politicians. They may hold several Positions, each over several Mandates (they are nasty that way).<br /> For each Position&gt;Mandate (say 5*3=15), there's a bunch of props such as<br /> party, predecessor, successor, colleagues (eg vicePresident, governor...), years the subject came to that position,<br /> years the colleagues came to their respective positions, etc.<br /> <br /> Eg see prop names of [https://bg.wikipedia.org/wiki/Шаблон:Държавник_инфо Държавник_инфо], but that's not the complete story: there's also трети_мандат_* (&quot;third mandate&quot; fields) etc.<br /> * If the 2D data arrays below the photos of Rosen Plevneliev and Angela Merkel don't strike your fancy, check out one of them Socialists that ruled for 40 years: [https://bg.wikipedia.org/wiki/Тодор_Живков Тодор_Живков]<br /> See a full list of props and an incomplete attempt to group them all at [http://mappings.dbpedia.org/index.php?title=Mapping_bg:Държавник_инфо&amp;action=edit Mapping Държавник_инфо].<br /> <br /> Wikidata editors were at a loss to create meaningful two-dimensional parallel arrays of names, so they created parasitc prefixes &amp; suffixes that are not so easy to match up. Eg there are 10 props &quot;предшестванОт&quot;, all mapped to &quot;predecessor&quot; but in different groups:<br /> &lt;pre&gt;<br /> предшестван от<br /> предшестван от2<br /> предшестван от3<br /> втори_мандат_предшестван от<br /> втори_мандат_предшестван от2<br /> втори_мандат_предшестван от3<br /> трети_мандат_предшестван от<br /> ...<br /> &lt;/pre&gt;<br /> <br /> * The prefixes may have any form<br /> * The suffixes are digits, optionally followed by letters<br /> <br /> == Rewriting templateProperty ==<br /> <br /> The parasitic prefixes/suffixes encode important info about the grouping of props,<br /> but that info is not transmitted in any clear way.<br /> <br /> Assume a mapping fragment like this, extracting data for resource bgdbr:Тодор_Живков<br /> &lt;pre&gt;<br /> {{IntermediateNodeMapping | nodeClass = CareerStation | correspondingProperty = careerStation | mappings = <br /> {{ PropertyMapping | templateProperty = втори_мандат_предшестван от3 | ontologyProperty = predecessor }}<br /> &lt;/pre&gt;<br /> What the extractor '''really''' does is:<br /> * Takes data from the templateProperty provided (as expected)<br /> * Strips parasitic prefixes &amp; suffixes from the templateProperty (maybe unexpected) and converts to camelCase<br /> * Emits the data using the original subject and this '''rewritten''' templateProperty, eg:<br /> bgdbr:Тодор_Живков bgdbp:предшестванОт &lt;data&gt;<br /> * Makes an IntermediateNode and connects it with correspondingProperty (as expected), eg:<br /> bgdbr:Тодор_Живков dbo:careerStation bgdbr:Тодор_Живков__1<br /> * Emits the data using the IntermediateNode and the ontologyProperty as provided (as expected), eg;<br /> bgdbr:Тодор_Живков__1 dbo:predeccessor &lt;data&gt;<br /> <br /> This achieves several goals:<br /> * the general semantics of the raw property is preserved, but not its grouping<br /> * the grouping is preserved by the creation of IntermediateNodes that use mapped properties (if the mapping is good)<br /> <br /> This allows you to make queries such as:<br /> * all predecessors of Тодор_Живков lumped together (regardless of the position). This works even if these raw props are not mapped!<br /> select * {bgdbr:Тодор_Живков bgdbp:предшестванОт ?pred}<br /> * all predecessors of Тодор_Живков, paired with successors, and the corresponding position name (office). (Note: you may want to throw in some OPTIONALs)<br /> select * {bgdbr:Тодор_Живков dbo:careerStation<br /> [dbo:predecessor ?pred; dbo:successor ?succ; dbo:office ?office]}<br /> <br /> Neat!<br /> <br /> '''NOTE''' Currently only purely numeric parasitic suffixes are stripped.<br /> Prefixes and alphanumeric suffixes would be stripped after [https://github.com/dbpedia/extraction-framework/issues/317 issue #317] is implemented</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Template:DisclaimerMapping&diff=45417 2015-02-23T14:07:45Z

<p>Chrisahn: Reverted edits by Chrisahn (Talk) to last revision by Gaurav</p> <hr /> <div>This is the mapping for the Wikipedia template [http://{{#replace:{{NAMESPACEE}}|Mapping_|}}.wikipedia.org/wiki/Template:{{PAGENAMEE}} {{PAGENAME}}]. Find usages of this Wikipedia template [http://{{#replace:{{NAMESPACEE}}|Mapping_|}}.wikipedia.org/wiki/Special:WhatLinksHere/Template:{{PAGENAMEE}}?limit=500&amp;namespace=0 here].<br /> <br /> [http://{{SERVERNAME}}/server/mappings/{{#replace:{{NAMESPACEE}}|Mapping_|}}/extractionSamples/{{FULLPAGENAMEE}} Test this mapping] (or in namespace [http://{{SERVERNAME}}/server/mappings/{{#replace:{{NAMESPACEE}}|Mapping_|}}/extractionSamples/{{FULLPAGENAMEE}}?namespace=File File] or [http://{{SERVERNAME}}/server/mappings/{{#replace:{{NAMESPACEE}}|Mapping_|}}/extractionSamples/{{FULLPAGENAMEE}}?namespace=Creator Creator]) with some example Wikipedia pages. Check which [http://{{SERVERNAME}}/server/templatestatistics/{{#replace:{{NAMESPACEE}}|Mapping_|}}/?template={{PAGENAMEE}} properties are not mapped yet].<br /> <br /> [[Writing_Mappings/Templates|Read more]] about mapping Wikipedia templates.</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=OntologyProperty:HasAnnotation&diff=45416 2015-02-23T13:53:30Z

<p>Chrisahn: '''{{Reserved for DBpedia}}'''</p> <hr /> <div>'''{{Reserved for DBpedia}}'''<br /> <br /> {{ObjectProperty<br /> | labels=<br /> {{label|en|Indicates an annotation associated with this document}}<br /> | rdfs:domain = Document<br /> | rdfs:range = Annotation<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=OntologyProperty:HasKMLData&diff=45415 2015-02-23T13:53:15Z

<p>Chrisahn: '''{{Reserved for DBpedia}}'''</p> <hr /> <div>'''{{Reserved for DBpedia}}'''<br /> <br /> {{DatatypeProperty<br /> | labels=<br /> {{label|en|Has KML data associated with it (usually because of [https://commons.wikimedia.org/wiki/Commons:Geocoding/Overlay KML overlays])}}<br /> | rdfs:domain = File<br /> | rdfs:range = xsd:string<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=OntologyProperty:AsWikiText&diff=45414 2015-02-23T13:52:51Z

<p>Chrisahn: '''{{Reserved for DBpedia}}'''</p> <hr /> <div>'''{{Reserved for DBpedia}}'''<br /> <br /> {{DatatypeProperty<br /> | labels=<br /> {{label|en|Contains a [https://www.mediawiki.org/wiki/Wikitext WikiText] representation of this thing}}<br /> | rdfs:domain = <br /> | rdfs:range = xsd:string<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Template:DisclaimerMapping&diff=45413 2015-02-23T13:03:21Z

<p>Chrisahn: Reverted edits by Gaurav (Talk) to last revision by Chrisahn</p> <hr /> <div>This is the mapping for the Wikipedia template [http://{{#replace:{{NAMESPACEE}}|Mapping_|}}.wikipedia.org/wiki/Template:{{PAGENAMEE}} {{PAGENAME}}]. Find usages of this Wikipedia template [http://{{#replace:{{NAMESPACEE}}|Mapping_|}}.wikipedia.org/wiki/Special:WhatLinksHere/Template:{{PAGENAMEE}}?limit=500&amp;namespace=0 here].<br /> <br /> [http://{{SERVERNAME}}/server/mappings/{{#replace:{{NAMESPACEE}}|Mapping_|}}/extractionSamples/{{FULLPAGENAMEE}} Test this mapping] with some example Wikipedia pages. Check which [http://{{SERVERNAME}}/server/templatestatistics/{{#replace:{{NAMESPACEE}}|Mapping_|}}/?template={{PAGENAMEE}} properties are not mapped yet].<br /> <br /> [[Writing_Mappings/Templates|Read more]] about mapping Wikipedia templates.</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=How_to_add_a_mapping_namespace&diff=38912 2014-12-21T13:50:45Z

<p>Chrisahn: /* Get language code and rank */ Don't use namespace numbers &gt;= 400</p> <hr /> <div>As an example, we use the fictitious language ''Xxyzish'' with Wikipedia domain ''xx'' and Wikipedia rank 44.<br /> <br /> '''CAUTION''': several subtle code changes will be needed to accomodate '''language codes that contain a dash''' (e.g. ''roa-rup'' or ''be-x-old''), especially in regard to URLs, file names and other identifiers, also in parts of the code base not listed here. In this case, please update the code and this guide.<br /> <br /> === Get language code and rank ===<br /> <br /> Get the wiki language code and rank from [http://s23.org/wikistats/wikipedias_html.php the list of Wikipedias].<br /> <br /> Namespace number: multiply the rank by 2 and add 200<br /> <br /> Example: language code &quot;xx&quot;, rank 44, namespace number 288.<br /> <br /> '''CAUTION''': If the calculated namespace number already exists for another language (because the ranking has changed) do '''not''' change the existing namespace number. Please find a neighboring or close enough number that works.<br /> <br /> Example: If 288 is in use, we choose some other number that is not used, let's say 298.<br /> <br /> '''CAUTION''': Do not use namespace numbers &gt;= 400. Namespaces 400 and above are used by MediaWiki. Please find a number between 200 and 398 that is not yet used.<br /> <br /> Example: If the language rank is 100, the formula above would yield namespace number 400. Instead, we choose some other number that is not used, let's say 398.<br /> <br /> === Update mappings wiki ===<br /> <br /> ==== Update MediaWiki settings ====<br /> <br /> Log onto the machine that is running this mappings wiki, i.e. serving http://mappings.dbpedia.org/index.php URLs.<br /> <br /> Open LocalSettings.php. Add the following snippet in the correct alphabetical position in the map defining the extra namespaces:<br /> <br /> &lt;pre&gt;<br /> &quot;xx&quot;=&gt;288,<br /> &lt;/pre&gt;<br /> <br /> Restart the Apache server.<br /> <br /> ==== Add the mappings main page ====<br /> <br /> Edit {{fullurl:Mapping xx}}. The page content should be the following, where ''Xxyzish'' is the English name of the language:<br /> <br /> &lt;pre&gt;<br /> {{Mapping main page|xx|Xxyzish}}<br /> &lt;/pre&gt;<br /> <br /> ==== Update [[MediaWiki:Sidebar|mappings wiki sidebar]] ====<br /> <br /> Edit [[MediaWiki:Sidebar]]. Add a link for the new language in the correct alphabetical position:<br /> <br /> &lt;pre&gt;<br /> ** Mapping xx|Mappings (xx)<br /> &lt;/pre&gt;<br /> <br /> ==== Update [[DBpedia datasets|datasets overview]] ====<br /> <br /> Edit [[DBpedia datasets]]. Add a column for the new language in the correct alphabetical position and update all rows according to the settings in [https://github.com/dbpedia/extraction-framework/blob/master/dump/extraction.default.properties dump/extraction.default.properties]. This is probably the most tedious part...<br /> <br /> === Update the extraction framework ===<br /> <br /> ==== Edit Namespace.scala ====<br /> <br /> Edit your copy of [https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/wikiparser/Namespace.scala core/src/main/scala/org/dbpedia/extraction/wikiparser/Namespace.scala]. Add something like this in the correct alphabetical position:<br /> <br /> &lt;pre&gt;<br /> &quot;xx&quot;-&gt;288,<br /> &lt;/pre&gt;<br /> <br /> ==== Edit extraction.default.properties ====<br /> <br /> Edit your copy of [https://github.com/dbpedia/extraction-framework/blob/master/dump/extraction.default.properties dump/extraction.default.properties]. Add something like this in the correct alphabetical position:<br /> <br /> &lt;pre&gt;<br /> extractors.xx=MappingExtractor<br /> &lt;/pre&gt;<br /> <br /> You can add more extractors, but make sure that the required configuration exists for the new language.<br /> <br /> ==== Update namespace settings for mappings wiki ====<br /> <br /> To update the namespace settings for the mappings wiki, cd to core/ and run<br /> <br /> &lt;pre&gt;<br /> ../clean-install-run generate-settings<br /> &lt;/pre&gt;<br /> <br /> ==== Commit changes ====<br /> <br /> Commit and push the changes to default branch.<br /> <br /> === Update and restart the mapping server ===<br /> <br /> Log onto the machine that is running the mapping server, i.e. serving http://mappings.dbpedia.org/server/ URLs.<br /> <br /> Stop the server:<br /> <br /> &lt;pre&gt;<br /> sudo /etc/init.d/mappings-server stop<br /> &lt;/pre&gt;<br /> <br /> Or, if there's no start/stop script:<br /> <br /> &lt;pre&gt;<br /> ps axfu | grep java<br /> &lt;/pre&gt;<br /> <br /> Look for class ...server.Server, and then:<br /> <br /> &lt;pre&gt;<br /> kill &lt;process id&gt;<br /> &lt;/pre&gt;<br /> <br /> Add a dummy file extraction_framework/server/src/main/statistics/mappingstats_xx.txt with the following content (make sure there are '''two empty lines''' at the end!): <br /> <br /> &lt;pre&gt;<br /> wikiStats|xx<br /> <br /> redirects|0<br /> <br /> templates|0<br /> <br /> <br /> &lt;/pre&gt;<br /> <br /> Then update and compile the server:<br /> <br /> &lt;pre&gt;<br /> cd extraction_framework<br /> git pull<br /> mvn clean install --projects core,server<br /> &lt;/pre&gt;<br /> <br /> Finally, start the server:<br /> <br /> &lt;pre&gt;<br /> sudo /etc/init.d/mappings-server start<br /> &lt;/pre&gt;<br /> <br /> Or, if there's no start/stop script:<br /> <br /> &lt;pre&gt;<br /> cd extraction_framework/server<br /> ../run server &amp;&gt;server-&lt;YYYY&gt;-&lt;MM&gt;-&lt;DD&gt;.01.log &amp;<br /> &lt;/pre&gt;<br /> <br /> === Generate and deploy statistics ===<br /> <br /> ==== Extract data from Wikipedia dump file ====<br /> <br /> Download the latest dump for language xx. [https://github.com/dbpedia/extraction-framework/wiki/Extraction-Instructions see here for details]<br /> &lt;pre&gt;<br /> dump&gt; ../run download config={download-config-file}<br /> &lt;/pre&gt;<br /> <br /> Run RedirectExtractor, InfoboxExtractor and TemplateParameterExtractor. [https://github.com/dbpedia/extraction-framework/blob/master/dump/extraction.stats.properties dump/extraction.stats.properties] should already contain the correct settings. cd into directory dump/ and execute<br /> <br /> &lt;pre&gt;<br /> dump&gt; ../run stats-extraction extraction.stats.properties<br /> &lt;/pre&gt;<br /> <br /> ==== Extract statistics from triples files ====<br /> <br /> cd into directory server/, modify the path to the dump base dir in pom.xml if necessary and run<br /> <br /> &lt;pre&gt;<br /> server&gt; ../run stats<br /> &lt;/pre&gt;<br /> <br /> Copy src/main/statistics/mappingstatistics_xx.txt to same folder on the mappings server.<br /> <br /> === Update and deploy sprint stuff ===<br /> <br /> Ask Pablo how to do that...</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=How_to_add_a_mapping_namespace&diff=38911 2014-12-21T13:44:56Z

<p>Chrisahn: sourceforge -&gt; github correct section name</p> <hr /> <div>As an example, we use the fictitious language ''Xxyzish'' with Wikipedia domain ''xx'' and Wikipedia rank 44.<br /> <br /> '''CAUTION''': several subtle code changes will be needed to accomodate '''language codes that contain a dash''' (e.g. ''roa-rup'' or ''be-x-old''), especially in regard to URLs, file names and other identifiers, also in parts of the code base not listed here. In this case, please update the code and this guide.<br /> <br /> === Get language code and rank ===<br /> <br /> Get the wiki language code and rank from [http://s23.org/wikistats/wikipedias_html.php the list of Wikipedias].<br /> <br /> Namespace number: multiply the rank by 2 and add 200<br /> <br /> Example: language code &quot;xx&quot;, rank 44, namespace number 288.<br /> <br /> '''CAUTION''': If the calculated namespace number already exists for another language (because the ranking has changed) do '''not''' change the existing namespace number. Please find a neighboring or close enough number that works.<br /> <br /> Example: if 288 is in use, we choose some other number that is not used, let's say 298.<br /> <br /> === Update mappings wiki ===<br /> <br /> ==== Update MediaWiki settings ====<br /> <br /> Log onto the machine that is running this mappings wiki, i.e. serving http://mappings.dbpedia.org/index.php URLs.<br /> <br /> Open LocalSettings.php. Add the following snippet in the correct alphabetical position in the map defining the extra namespaces:<br /> <br /> &lt;pre&gt;<br /> &quot;xx&quot;=&gt;288,<br /> &lt;/pre&gt;<br /> <br /> Restart the Apache server.<br /> <br /> ==== Add the mappings main page ====<br /> <br /> Edit {{fullurl:Mapping xx}}. The page content should be the following, where ''Xxyzish'' is the English name of the language:<br /> <br /> &lt;pre&gt;<br /> {{Mapping main page|xx|Xxyzish}}<br /> &lt;/pre&gt;<br /> <br /> ==== Update [[MediaWiki:Sidebar|mappings wiki sidebar]] ====<br /> <br /> Edit [[MediaWiki:Sidebar]]. Add a link for the new language in the correct alphabetical position:<br /> <br /> &lt;pre&gt;<br /> ** Mapping xx|Mappings (xx)<br /> &lt;/pre&gt;<br /> <br /> ==== Update [[DBpedia datasets|datasets overview]] ====<br /> <br /> Edit [[DBpedia datasets]]. Add a column for the new language in the correct alphabetical position and update all rows according to the settings in [https://github.com/dbpedia/extraction-framework/blob/master/dump/extraction.default.properties dump/extraction.default.properties]. This is probably the most tedious part...<br /> <br /> === Update the extraction framework ===<br /> <br /> ==== Edit Namespace.scala ====<br /> <br /> Edit your copy of [https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/wikiparser/Namespace.scala core/src/main/scala/org/dbpedia/extraction/wikiparser/Namespace.scala]. Add something like this in the correct alphabetical position:<br /> <br /> &lt;pre&gt;<br /> &quot;xx&quot;-&gt;288,<br /> &lt;/pre&gt;<br /> <br /> ==== Edit extraction.default.properties ====<br /> <br /> Edit your copy of [https://github.com/dbpedia/extraction-framework/blob/master/dump/extraction.default.properties dump/extraction.default.properties]. Add something like this in the correct alphabetical position:<br /> <br /> &lt;pre&gt;<br /> extractors.xx=MappingExtractor<br /> &lt;/pre&gt;<br /> <br /> You can add more extractors, but make sure that the required configuration exists for the new language.<br /> <br /> ==== Update namespace settings for mappings wiki ====<br /> <br /> To update the namespace settings for the mappings wiki, cd to core/ and run<br /> <br /> &lt;pre&gt;<br /> ../clean-install-run generate-settings<br /> &lt;/pre&gt;<br /> <br /> ==== Commit changes ====<br /> <br /> Commit and push the changes to default branch.<br /> <br /> === Update and restart the mapping server ===<br /> <br /> Log onto the machine that is running the mapping server, i.e. serving http://mappings.dbpedia.org/server/ URLs.<br /> <br /> Stop the server:<br /> <br /> &lt;pre&gt;<br /> sudo /etc/init.d/mappings-server stop<br /> &lt;/pre&gt;<br /> <br /> Or, if there's no start/stop script:<br /> <br /> &lt;pre&gt;<br /> ps axfu | grep java<br /> &lt;/pre&gt;<br /> <br /> Look for class ...server.Server, and then:<br /> <br /> &lt;pre&gt;<br /> kill &lt;process id&gt;<br /> &lt;/pre&gt;<br /> <br /> Add a dummy file extraction_framework/server/src/main/statistics/mappingstats_xx.txt with the following content (make sure there are '''two empty lines''' at the end!): <br /> <br /> &lt;pre&gt;<br /> wikiStats|xx<br /> <br /> redirects|0<br /> <br /> templates|0<br /> <br /> <br /> &lt;/pre&gt;<br /> <br /> Then update and compile the server:<br /> <br /> &lt;pre&gt;<br /> cd extraction_framework<br /> git pull<br /> mvn clean install --projects core,server<br /> &lt;/pre&gt;<br /> <br /> Finally, start the server:<br /> <br /> &lt;pre&gt;<br /> sudo /etc/init.d/mappings-server start<br /> &lt;/pre&gt;<br /> <br /> Or, if there's no start/stop script:<br /> <br /> &lt;pre&gt;<br /> cd extraction_framework/server<br /> ../run server &amp;&gt;server-&lt;YYYY&gt;-&lt;MM&gt;-&lt;DD&gt;.01.log &amp;<br /> &lt;/pre&gt;<br /> <br /> === Generate and deploy statistics ===<br /> <br /> ==== Extract data from Wikipedia dump file ====<br /> <br /> Download the latest dump for language xx. [https://github.com/dbpedia/extraction-framework/wiki/Extraction-Instructions see here for details]<br /> &lt;pre&gt;<br /> dump&gt; ../run download config={download-config-file}<br /> &lt;/pre&gt;<br /> <br /> Run RedirectExtractor, InfoboxExtractor and TemplateParameterExtractor. [https://github.com/dbpedia/extraction-framework/blob/master/dump/extraction.stats.properties dump/extraction.stats.properties] should already contain the correct settings. cd into directory dump/ and execute<br /> <br /> &lt;pre&gt;<br /> dump&gt; ../run stats-extraction extraction.stats.properties<br /> &lt;/pre&gt;<br /> <br /> ==== Extract statistics from triples files ====<br /> <br /> cd into directory server/, modify the path to the dump base dir in pom.xml if necessary and run<br /> <br /> &lt;pre&gt;<br /> server&gt; ../run stats<br /> &lt;/pre&gt;<br /> <br /> Copy src/main/statistics/mappingstatistics_xx.txt to same folder on the mappings server.<br /> <br /> === Update and deploy sprint stuff ===<br /> <br /> Ask Pablo how to do that...</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=How_to_add_a_mapping_namespace&diff=38910 2014-12-21T13:44:19Z

<p>Chrisahn: sourceforge -&gt; github correct link</p> <hr /> <div>As an example, we use the fictitious language ''Xxyzish'' with Wikipedia domain ''xx'' and Wikipedia rank 44.<br /> <br /> '''CAUTION''': several subtle code changes will be needed to accomodate '''language codes that contain a dash''' (e.g. ''roa-rup'' or ''be-x-old''), especially in regard to URLs, file names and other identifiers, also in parts of the code base not listed here. In this case, please update the code and this guide.<br /> <br /> === Get language code and rank ===<br /> <br /> Get the wiki language code and rank from [http://s23.org/wikistats/wikipedias_html.php the list of Wikipedias].<br /> <br /> Namespace number: multiply the rank by 2 and add 200<br /> <br /> Example: language code &quot;xx&quot;, rank 44, namespace number 288.<br /> <br /> '''CAUTION''': If the calculated namespace number already exists for another language (because the ranking has changed) do '''not''' change the existing namespace number. Please find a neighboring or close enough number that works.<br /> <br /> Example: if 288 is in use, we choose some other number that is not used, let's say 298.<br /> <br /> === Update mappings wiki ===<br /> <br /> ==== Update MediaWiki settings ====<br /> <br /> Log onto the machine that is running this mappings wiki, i.e. serving http://mappings.dbpedia.org/index.php URLs.<br /> <br /> Open LocalSettings.php. Add the following snippet in the correct alphabetical position in the map defining the extra namespaces:<br /> <br /> &lt;pre&gt;<br /> &quot;xx&quot;=&gt;288,<br /> &lt;/pre&gt;<br /> <br /> Restart the Apache server.<br /> <br /> ==== Add the mappings main page ====<br /> <br /> Edit {{fullurl:Mapping xx}}. The page content should be the following, where ''Xxyzish'' is the English name of the language:<br /> <br /> &lt;pre&gt;<br /> {{Mapping main page|xx|Xxyzish}}<br /> &lt;/pre&gt;<br /> <br /> ==== Update [[MediaWiki:Sidebar|mappings wiki sidebar]] ====<br /> <br /> Edit [[MediaWiki:Sidebar]]. Add a link for the new language in the correct alphabetical position:<br /> <br /> &lt;pre&gt;<br /> ** Mapping xx|Mappings (xx)<br /> &lt;/pre&gt;<br /> <br /> ==== Update [[DBpedia datasets|datasets overview]] ====<br /> <br /> Edit [[DBpedia datasets]]. Add a column for the new language in the correct alphabetical position and update all rows according to the settings in [https://github.com/dbpedia/extraction-framework/blob/master/dump/extraction.default.properties dump/extraction.default.properties]. This is probably the most tedious part...<br /> <br /> === Update the extraction framework ===<br /> <br /> ==== Edit Namespace.scala ====<br /> <br /> Edit your copy of [https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/wikiparser/Namespace.scala core/src/main/scala/org/dbpedia/extraction/wikiparser/Namespace.scala]. Add something like this in the correct alphabetical position:<br /> <br /> &lt;pre&gt;<br /> &quot;xx&quot;-&gt;288,<br /> &lt;/pre&gt;<br /> <br /> ==== Edit extract.default.properties ====<br /> <br /> Edit your copy of [https://github.com/dbpedia/extraction-framework/blob/master/dump/extraction.default.properties dump/extraction.default.properties]. Add something like this in the correct alphabetical position:<br /> <br /> &lt;pre&gt;<br /> extractors.xx=MappingExtractor<br /> &lt;/pre&gt;<br /> <br /> You can add more extractors, but make sure that the required configuration exists for the new language.<br /> <br /> ==== Update namespace settings for mappings wiki ====<br /> <br /> To update the namespace settings for the mappings wiki, cd to core/ and run<br /> <br /> &lt;pre&gt;<br /> ../clean-install-run generate-settings<br /> &lt;/pre&gt;<br /> <br /> ==== Commit changes ====<br /> <br /> Commit and push the changes to default branch.<br /> <br /> === Update and restart the mapping server ===<br /> <br /> Log onto the machine that is running the mapping server, i.e. serving http://mappings.dbpedia.org/server/ URLs.<br /> <br /> Stop the server:<br /> <br /> &lt;pre&gt;<br /> sudo /etc/init.d/mappings-server stop<br /> &lt;/pre&gt;<br /> <br /> Or, if there's no start/stop script:<br /> <br /> &lt;pre&gt;<br /> ps axfu | grep java<br /> &lt;/pre&gt;<br /> <br /> Look for class ...server.Server, and then:<br /> <br /> &lt;pre&gt;<br /> kill &lt;process id&gt;<br /> &lt;/pre&gt;<br /> <br /> Add a dummy file extraction_framework/server/src/main/statistics/mappingstats_xx.txt with the following content (make sure there are '''two empty lines''' at the end!): <br /> <br /> &lt;pre&gt;<br /> wikiStats|xx<br /> <br /> redirects|0<br /> <br /> templates|0<br /> <br /> <br /> &lt;/pre&gt;<br /> <br /> Then update and compile the server:<br /> <br /> &lt;pre&gt;<br /> cd extraction_framework<br /> git pull<br /> mvn clean install --projects core,server<br /> &lt;/pre&gt;<br /> <br /> Finally, start the server:<br /> <br /> &lt;pre&gt;<br /> sudo /etc/init.d/mappings-server start<br /> &lt;/pre&gt;<br /> <br /> Or, if there's no start/stop script:<br /> <br /> &lt;pre&gt;<br /> cd extraction_framework/server<br /> ../run server &amp;&gt;server-&lt;YYYY&gt;-&lt;MM&gt;-&lt;DD&gt;.01.log &amp;<br /> &lt;/pre&gt;<br /> <br /> === Generate and deploy statistics ===<br /> <br /> ==== Extract data from Wikipedia dump file ====<br /> <br /> Download the latest dump for language xx. [https://github.com/dbpedia/extraction-framework/wiki/Extraction-Instructions see here for details]<br /> &lt;pre&gt;<br /> dump&gt; ../run download config={download-config-file}<br /> &lt;/pre&gt;<br /> <br /> Run RedirectExtractor, InfoboxExtractor and TemplateParameterExtractor. [https://github.com/dbpedia/extraction-framework/blob/master/dump/extraction.stats.properties dump/extraction.stats.properties] should already contain the correct settings. cd into directory dump/ and execute<br /> <br /> &lt;pre&gt;<br /> dump&gt; ../run stats-extraction extraction.stats.properties<br /> &lt;/pre&gt;<br /> <br /> ==== Extract statistics from triples files ====<br /> <br /> cd into directory server/, modify the path to the dump base dir in pom.xml if necessary and run<br /> <br /> &lt;pre&gt;<br /> server&gt; ../run stats<br /> &lt;/pre&gt;<br /> <br /> Copy src/main/statistics/mappingstatistics_xx.txt to same folder on the mappings server.<br /> <br /> === Update and deploy sprint stuff ===<br /> <br /> Ask Pablo how to do that...</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=How_to_add_a_mapping_namespace&diff=38909 2014-12-21T13:42:47Z

<p>Chrisahn: sourceforge -&gt; github</p> <hr /> <div>As an example, we use the fictitious language ''Xxyzish'' with Wikipedia domain ''xx'' and Wikipedia rank 44.<br /> <br /> '''CAUTION''': several subtle code changes will be needed to accomodate '''language codes that contain a dash''' (e.g. ''roa-rup'' or ''be-x-old''), especially in regard to URLs, file names and other identifiers, also in parts of the code base not listed here. In this case, please update the code and this guide.<br /> <br /> === Get language code and rank ===<br /> <br /> Get the wiki language code and rank from [http://s23.org/wikistats/wikipedias_html.php the list of Wikipedias].<br /> <br /> Namespace number: multiply the rank by 2 and add 200<br /> <br /> Example: language code &quot;xx&quot;, rank 44, namespace number 288.<br /> <br /> '''CAUTION''': If the calculated namespace number already exists for another language (because the ranking has changed) do '''not''' change the existing namespace number. Please find a neighboring or close enough number that works.<br /> <br /> Example: if 288 is in use, we choose some other number that is not used, let's say 298.<br /> <br /> === Update mappings wiki ===<br /> <br /> ==== Update MediaWiki settings ====<br /> <br /> Log onto the machine that is running this mappings wiki, i.e. serving http://mappings.dbpedia.org/index.php URLs.<br /> <br /> Open LocalSettings.php. Add the following snippet in the correct alphabetical position in the map defining the extra namespaces:<br /> <br /> &lt;pre&gt;<br /> &quot;xx&quot;=&gt;288,<br /> &lt;/pre&gt;<br /> <br /> Restart the Apache server.<br /> <br /> ==== Add the mappings main page ====<br /> <br /> Edit {{fullurl:Mapping xx}}. The page content should be the following, where ''Xxyzish'' is the English name of the language:<br /> <br /> &lt;pre&gt;<br /> {{Mapping main page|xx|Xxyzish}}<br /> &lt;/pre&gt;<br /> <br /> ==== Update [[MediaWiki:Sidebar|mappings wiki sidebar]] ====<br /> <br /> Edit [[MediaWiki:Sidebar]]. Add a link for the new language in the correct alphabetical position:<br /> <br /> &lt;pre&gt;<br /> ** Mapping xx|Mappings (xx)<br /> &lt;/pre&gt;<br /> <br /> ==== Update [[DBpedia datasets|datasets overview]] ====<br /> <br /> Edit [[DBpedia datasets]]. Add a column for the new language in the correct alphabetical position and update all rows according to the settings in [https://github.com/dbpedia/extraction-framework/blob/master/dump/extraction.default.properties dump/extraction.default.properties]. This is probably the most tedious part...<br /> <br /> === Update the extraction framework ===<br /> <br /> ==== Edit Namespace.scala ====<br /> <br /> Edit your copy of [https://github.com/dbpedia/extraction-framework/blob/master/core/src/main/scala/org/dbpedia/extraction/wikiparser/Namespace.scala core/src/main/scala/org/dbpedia/extraction/wikiparser/Namespace.scala]. Add something like this in the correct alphabetical position:<br /> <br /> &lt;pre&gt;<br /> &quot;xx&quot;-&gt;288,<br /> &lt;/pre&gt;<br /> <br /> ==== Edit extract.default.properties ====<br /> <br /> Edit your copy of [https://github.com/dbpedia/extraction-framework/blob/master/dump/extract.default.properties dump/extract.default.properties]. Add something like this in the correct alphabetical position:<br /> <br /> &lt;pre&gt;<br /> extractors.xx=MappingExtractor<br /> &lt;/pre&gt;<br /> <br /> You can add more extractors, but make sure that the required configuration exists for the new language.<br /> <br /> ==== Update namespace settings for mappings wiki ====<br /> <br /> To update the namespace settings for the mappings wiki, cd to core/ and run<br /> <br /> &lt;pre&gt;<br /> ../clean-install-run generate-settings<br /> &lt;/pre&gt;<br /> <br /> ==== Commit changes ====<br /> <br /> Commit and push the changes to default branch.<br /> <br /> === Update and restart the mapping server ===<br /> <br /> Log onto the machine that is running the mapping server, i.e. serving http://mappings.dbpedia.org/server/ URLs.<br /> <br /> Stop the server:<br /> <br /> &lt;pre&gt;<br /> sudo /etc/init.d/mappings-server stop<br /> &lt;/pre&gt;<br /> <br /> Or, if there's no start/stop script:<br /> <br /> &lt;pre&gt;<br /> ps axfu | grep java<br /> &lt;/pre&gt;<br /> <br /> Look for class ...server.Server, and then:<br /> <br /> &lt;pre&gt;<br /> kill &lt;process id&gt;<br /> &lt;/pre&gt;<br /> <br /> Add a dummy file extraction_framework/server/src/main/statistics/mappingstats_xx.txt with the following content (make sure there are '''two empty lines''' at the end!): <br /> <br /> &lt;pre&gt;<br /> wikiStats|xx<br /> <br /> redirects|0<br /> <br /> templates|0<br /> <br /> <br /> &lt;/pre&gt;<br /> <br /> Then update and compile the server:<br /> <br /> &lt;pre&gt;<br /> cd extraction_framework<br /> git pull<br /> mvn clean install --projects core,server<br /> &lt;/pre&gt;<br /> <br /> Finally, start the server:<br /> <br /> &lt;pre&gt;<br /> sudo /etc/init.d/mappings-server start<br /> &lt;/pre&gt;<br /> <br /> Or, if there's no start/stop script:<br /> <br /> &lt;pre&gt;<br /> cd extraction_framework/server<br /> ../run server &amp;&gt;server-&lt;YYYY&gt;-&lt;MM&gt;-&lt;DD&gt;.01.log &amp;<br /> &lt;/pre&gt;<br /> <br /> === Generate and deploy statistics ===<br /> <br /> ==== Extract data from Wikipedia dump file ====<br /> <br /> Download the latest dump for language xx. [https://github.com/dbpedia/extraction-framework/wiki/Extraction-Instructions see here for details]<br /> &lt;pre&gt;<br /> dump&gt; ../run download config={download-config-file}<br /> &lt;/pre&gt;<br /> <br /> Run RedirectExtractor, InfoboxExtractor and TemplateParameterExtractor. [https://github.com/dbpedia/extraction-framework/blob/master/dump/extraction.stats.properties dump/extraction.stats.properties] should already contain the correct settings. cd into directory dump/ and execute<br /> <br /> &lt;pre&gt;<br /> dump&gt; ../run stats-extraction extraction.stats.properties<br /> &lt;/pre&gt;<br /> <br /> ==== Extract statistics from triples files ====<br /> <br /> cd into directory server/, modify the path to the dump base dir in pom.xml if necessary and run<br /> <br /> &lt;pre&gt;<br /> server&gt; ../run stats<br /> &lt;/pre&gt;<br /> <br /> Copy src/main/statistics/mappingstatistics_xx.txt to same folder on the mappings server.<br /> <br /> === Update and deploy sprint stuff ===<br /> <br /> Ask Pablo how to do that...</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Mapping_hy&diff=38861 2014-12-09T19:44:40Z

<p>Chrisahn: There is no namespace Mapping_hy yet, a developer has to install it first</p> <hr /> <div>Please don't add pages named '''Mapping hy:Xyz'''. There is no namespace Mapping_hy yet, a developer has to install it first. Adding pages whose names start with Mapping_hy will lead to problems later. Please write to dbpedia-discussion. Thanks.</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=MediaWiki:Sidebar&diff=28398 2013-09-18T11:02:13Z

<p>Chrisahn: fixed order of eo</p> <hr /> <div>* navigation<br /> ** mainpage|mainpage-description<br /> ** recentchanges-url|recentchanges<br /> ** randompage-url|randompage<br /> ** helppage|help<br /> * DBpedia<br /> ** {{fullurl:Special:AllPages|namespace=200}}|Ontology Classes<br /> ** {{fullurl:Special:AllPages|namespace=206}}|Ontology Dataypes<br /> ** {{fullurl:Special:AllPages|namespace=202}}|Ontology Properties<br /> ** Mapping ar|Mappings (ar)<br /> ** Mapping bg|Mappings (bg)<br /> ** Mapping bn|Mappings (bn)<br /> ** Mapping ca|Mappings (ca)<br /> ** Mapping cs|Mappings (cs)<br /> ** Mapping de|Mappings (de)<br /> ** Mapping el|Mappings (el)<br /> ** Mapping en|Mappings (en)<br /> ** Mapping eo|Mappings (eo)<br /> ** Mapping es|Mappings (es)<br /> ** Mapping et|Mappings (et)<br /> ** Mapping eu|Mappings (eu)<br /> ** Mapping fr|Mappings (fr)<br /> ** Mapping ga|Mappings (ga)<br /> ** Mapping hi|Mappings (hi)<br /> ** Mapping hr|Mappings (hr)<br /> ** Mapping hu|Mappings (hu)<br /> ** Mapping id|Mappings (id)<br /> ** Mapping it|Mappings (it)<br /> ** Mapping ja|Mappings (ja)<br /> ** Mapping ko|Mappings (ko)<br /> ** Mapping nl|Mappings (nl)<br /> ** Mapping pl|Mappings (pl)<br /> ** Mapping pt|Mappings (pt)<br /> ** Mapping ru|Mappings (ru)<br /> ** Mapping sk|Mappings (sk)<br /> ** Mapping sl|Mappings (sl)<br /> ** Mapping tr|Mappings (tr)<br /> ** Mapping ur|Mappings (ur)<br /> ** Mapping zh|Mappings (zh)<br /> * SEARCH<br /> * TOOLBOX<br /> * LANGUAGES</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=OntologyProperty:Country&diff=28127 2013-08-29T15:00:23Z

<p>Chrisahn: | owl:equivalentProperty = wikidata:P17</p> <hr /> <div>{{ObjectProperty<br /> |labels=<br /> {{label|en|country}}<br /> {{label|de|Land}}<br /> {{label|pt|país}}<br /> {{label|el|χώρα}}<br /> {{label|nl|land}}<br /> {{label|fr|pays}}<br /> {{label|es|país}}<br /> | rdfs:range = Country<br /> | owl:equivalentProperty = wikidata:P17<br /> }}</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Template:ObjectProperty&diff=28126 2013-08-29T13:43:54Z

<p>Chrisahn: use Template:LinkProperties</p> <hr /> <div>&lt;includeonly&gt;{{DisclaimerOntologyProperty}} <br /> <br /> &lt;table class=&quot;wikitable&quot;&gt;<br /> &lt;tr&gt;<br /> &lt;th colspan=&quot;2&quot; style=&quot;text-align:left&quot;&gt;Ontology object property &lt;small&gt;([[Template:ObjectProperty|&lt;span style=&quot;cursor:help;&quot;&gt;help&lt;/span&gt;]])&lt;/small&gt;&lt;/th&gt;<br /> &lt;/tr&gt;<br /> {{#if:{{{labels|}}}|{{{labels}}}|<br /> {{#if:{{{rdfs:label@en|}}}|&lt;!-- no message --&gt;|<br /> &lt;tr&gt;<br /> &lt;td colspan=&quot;2&quot;&gt;please define an English label: &lt;code&gt;&lt;nowiki&gt;labels = {{label|en|...}} ...&lt;/nowiki&gt;&lt;/code&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> }}<br /> }}<br /> {{#if:{{{rdfs:label@ar|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ar&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ar}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@bg|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@bg&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@bg}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@bn|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@bn&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@bn}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ca|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ca&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ca}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@cs|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@cs&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@cs}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@de|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@de&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@de}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@el|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@el&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@el}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@en|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@en&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@en}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@es|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@es&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@es}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@fr|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@fr&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@fr}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ga|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ga&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ga}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@hi|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@hi&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@hi}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@hr|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@hr&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@hr}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@hu|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@hu&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@hu}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@it|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@it&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@it}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ja|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ja&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ja}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ko|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ko&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ko}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@nl|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@nl&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@nl}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@pl|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@pl&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@pl}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@pt|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@pt&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@pt}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ru|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ru&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ru}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@sl|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@sl&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@sl}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@tr|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@tr&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@tr}}}&lt;/td&gt;&lt;/tr&gt;}}<br /> {{{comments|}}}<br /> {{#if:{{{rdfs:comment@en|}}}|<br /> &lt;tr&gt;<br /> &lt;td&gt;rdfs:comment@en&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:comment@en}}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> }}<br /> &lt;tr&gt;<br /> &lt;td&gt;rdfs:domain&lt;/td&gt;<br /> &lt;td&gt;{{linkClasses|{{{rdfs:domain|}}}|owl:Thing}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;rdfs:range&lt;/td&gt;<br /> &lt;td&gt;{{linkClasses|{{{rdfs:range|}}}|owl:Thing}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;rdf:type&lt;/td&gt;<br /> &lt;td&gt;{{{rdf:type|}}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;rdfs:subPropertyOf&lt;/td&gt;<br /> &lt;td&gt;{{linkProperties|{{{rdfs:subPropertyOf|}}}}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;owl:equivalentProperty&lt;/td&gt;<br /> &lt;td&gt;{{linkProperties|{{{owl:equivalentProperty|}}}}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;owl:propertyDisjointWith&lt;/td&gt;<br /> &lt;td&gt;{{linkProperties|{{{owl:propertyDisjointWith|}}}}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> &lt;/includeonly&gt;<br /> &lt;noinclude&gt;The '''&lt;nowiki&gt;{{ObjectProperty}}&lt;/nowiki&gt;''' template can be used to define ontology object properties. <br /> <br /> === Usage ===<br /> <br /> &lt;pre&gt;<br /> {{ObjectProperty<br /> | labels =<br /> {{label|en|...}}<br /> {{label|..|...}}<br /> | comments =<br /> {{comment|en|...}}<br /> {{comment|..|...}}<br /> | rdfs:domain = <br /> | rdfs:range =<br /> | rdf:type = [ owl:FunctionalProperty | owl:InverseFunctionalProperty | owl:TransitiveProperty | owl:SymmetricProperty | owl:ReflexiveObjectProperty | owl:IrreflexiveObjectProperty ]<br /> | rdfs:subPropertyOf =<br /> | owl:equivalentProperty = <br /> | owl:propertyDisjointWith =<br /> }}<br /> &lt;/pre&gt;<br /> <br /> ==== Details ====<br /> <br /> * '''labels''': should be defined to provide a human-readable version of a property's name. Use ISO language code 639-1 (e.g. &lt;nowiki&gt;{{label|en|...}}&lt;/nowiki&gt;).<br /> * '''comments''': should be defined to provide a human-readable description of a property. Use ISO language code 639-1 (e.g. &lt;nowiki&gt;{{comment|en|...}}&lt;/nowiki&gt;).<br /> * '''rdfs:domain''': is used to state that any resource that has a given property is an instance of the stated class. If left empty, owl:Thing is assumed.<br /> * '''rdfs:range''': is used to state that the values of a property are instances of the stated class. If left empty, owl:Thing is assumed.<br /> * '''rdf:type''': currently, only [http://www.w3.org/TR/owl-ref/#FunctionalProperty-def owl:FunctionalProperty], [http://www.w3.org/TR/owl-ref/#InverseFunctionalProperty-def owl:InverseFunctionalProperty], [http://www.w3.org/TR/owl-ref/#TransitiveProperty-def owl:TransitiveProperty], [http://www.w3.org/TR/owl-ref/#SymmetricProperty-def owl:SymmetricProperty], [http://www.w3.org/2007/OWL/wiki/Syntax#Reflexive_Object_Properties owl:ReflexiveProperty] and [http://www.w3.org/2007/OWL/wiki/Syntax#Irreflexive_Object_Properties owl:IrreflexiveProperty] are supported.<br /> * '''rdfs:subPropertyOf''': defines that the property is a subproperty of some other property. Formally this means that if P1 is a subproperty of P2, then the property values of P1 are a subset of the property values of P2.<br /> * '''owl:equivalentProperty''':<br /> * '''owl:propertyDisjointWith''':<br /> <br /> For backwards compatibilty, the following format for labels and comments is also possible but '''deprecated''':<br /> <br /> &lt;pre&gt;<br /> {{ObjectProperty<br /> | rdfs:label@en =<br /> | rdfs:label@.. =<br /> | rdfs:comment@en =<br /> &lt;/pre&gt;<br /> <br /> === Example ===<br /> <br /> The definition of the DBpedia ontology property [[OntologyProperty:doctoralAdvisor|doctoralAdvisor]]:<br /> &lt;pre&gt;<br /> {{ObjectProperty<br /> | labels = <br /> {{label|en|doctoral advisor}}<br /> | comments =<br /> | rdfs:domain = Scientist<br /> | rdfs:range = Person<br /> }}<br /> &lt;/pre&gt;<br /> <br /> It will be rendered to this table:<br /> <br /> <br /> {{ObjectProperty<br /> | labels = <br /> {{label|en|doctoral advisor}}<br /> | comments =<br /> | rdfs:domain@en = Scientist<br /> | rdfs:range = Person<br /> }}<br /> &lt;/noinclude&gt;</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Template:DatatypeProperty&diff=28125 2013-08-29T13:43:43Z

<p>Chrisahn: added owl:propertyDisjointWith</p> <hr /> <div>&lt;includeonly&gt;{{DisclaimerOntologyProperty}}<br /> <br /> &lt;table class=&quot;wikitable&quot;&gt;<br /> &lt;tr&gt;<br /> &lt;th colspan=&quot;2&quot; style=&quot;text-align:left&quot;&gt;Ontology datatype property &lt;small&gt;([[Template:DatatypeProperty|&lt;span style=&quot;cursor:help;&quot;&gt;help&lt;/span&gt;]])&lt;/small&gt;&lt;/th&gt;<br /> &lt;/tr&gt;<br /> {{#if:{{{labels|}}}|{{{labels}}}|<br /> {{#if:{{{rdfs:label@en|}}}|&lt;!-- no message --&gt;|<br /> &lt;tr&gt;<br /> &lt;td colspan=&quot;2&quot;&gt;please define an English label: &lt;nowiki&gt;labels = {{label|en|...}} ...&lt;/nowiki&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> }}<br /> }}<br /> {{#if:{{{rdfs:label@ar|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ar&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ar}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@bg|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@bg&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@bg}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@bn|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@bn&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@bn}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ca|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ca&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ca}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@cs|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@cs&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@cs}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@de|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@de&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@de}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@el|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@el&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@el}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@en|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@en&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@en}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@es|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@es&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@es}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@fr|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@fr&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@fr}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ga|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ga&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ga}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@hi|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@hi&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@hi}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@hr|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@hr&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@hr}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@hu|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@hu&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@hu}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@it|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@it&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@it}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ja|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ja&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ja}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ko|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ko&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ko}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@nl|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@nl&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@nl}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@pl|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@pl&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@pl}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@pt|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@pt&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@pt}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ru|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ru&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ru}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@sl|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@sl&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@sl}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@tr|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@tr&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@tr}}}&lt;/td&gt;&lt;/tr&gt;}}<br /> {{{comments|}}}<br /> {{#if:{{{rdfs:comment@en|}}}|<br /> &lt;tr&gt;<br /> &lt;td&gt;rdfs:comment@en&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:comment@en}}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> }}<br /> &lt;tr&gt;<br /> &lt;td&gt;rdfs:domain&lt;/td&gt;<br /> &lt;td&gt;{{linkClasses|{{{rdfs:domain|}}}|owl:Thing}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;rdfs:range&lt;/td&gt;<br /> &lt;td&gt;{{#if:{{{rdfs:range|}}}|[[Datatype:{{{rdfs:range}}}|{{{rdfs:range}}}]]|&lt;span style=&quot;color:red&quot;&gt;please define range&lt;/span&gt;}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;rdf:type&lt;/td&gt;<br /> &lt;td&gt;{{#if:{{{rdf:type|}}}|{{{rdf:type}}}}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;rdfs:subPropertyOf&lt;/td&gt;<br /> &lt;td&gt;{{linkProperties|{{{rdfs:subPropertyOf|}}}}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;owl:equivalentProperty&lt;/td&gt;<br /> &lt;td&gt;{{linkProperties|{{{owl:equivalentProperty|}}}}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;owl:propertyDisjointWith&lt;/td&gt;<br /> &lt;td&gt;{{linkProperties|{{{owl:propertyDisjointWith|}}}}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> &lt;/includeonly&gt;<br /> &lt;noinclude&gt;The '''&lt;nowiki&gt;{{DatatypeProperty}}&lt;/nowiki&gt;''' template can be used to define ontology datatype properties.<br /> <br /> === Usage ===<br /> <br /> &lt;pre&gt;<br /> {{DatatypeProperty <br /> | labels =<br /> {{label|en|...}}<br /> {{label|..|...}}<br /> | comments =<br /> {{comment|en|...}}<br /> {{comment|..|...}}<br /> | rdfs:domain =<br /> | rdfs:range =<br /> | rdf:type =<br /> | rdfs:subPropertyOf =<br /> | owl:equivalentProperty =<br /> }}<br /> &lt;/pre&gt;<br /> <br /> ==== Details ====<br /> <br /> * '''labels''': should be defined to provide a human-readable version of a property's name. Use ISO language code 639-1 (e.g. &lt;nowiki&gt;{{label|en|...}}&lt;/nowiki&gt;).<br /> * '''comments''': should be defined to provide a human-readable description of a property. Use ISO language code 639-1 (e.g. &lt;nowiki&gt;{{comment|en|...}}&lt;/nowiki&gt;).<br /> * '''rdfs:domain''': is used to state that any resource that has a given property is an instance of the stated class. If left empty, owl:Thing is assumed.<br /> * '''rdfs:range''': is used to state that the values of a property are instances of the stated class. <br /> ** XSD Datatypes: xsd:date, xsd:time, xsd:dateTime, xsd:gYear, xsd:gYearMonth, xsd:gMonth, xsd:gMonthDay, xsd:gDay, xsd:boolean, xsd:string, xsd:integer, xsd:double, xsd:float<br /> ** [[DBpedia Datatypes]]<br /> * '''rdf:type''': currently, only [http://www.w3.org/TR/owl-ref/#FunctionalProperty-def owl:FunctionalProperty] is supported.<br /> * '''rdfs:subPropertyOf''': defines that the property is a subproperty of some other property. Formally this means that if P1 is a subproperty of P2, then the property values of P1 are a subset of the property values of P2.<br /> * '''owl:equivalentProperty''':<br /> <br /> For backwards compatibilty, the following format for labels and comments is also possible but '''deprecated''':<br /> <br /> &lt;pre&gt;<br /> {{DatatypeProperty<br /> | rdfs:label@en =<br /> | rdfs:label@.. =<br /> | rdfs:comment@en =<br /> &lt;/pre&gt;<br /> <br /> === Example ===<br /> <br /> The definition of the DBpedia ontology property [[OntologyProperty:height|height]]:<br /> &lt;pre&gt;<br /> {{DatatypeProperty <br /> | labels = <br /> {{label|en|height}}<br /> | comments =<br /> | rdfs:range = Length<br /> }}<br /> &lt;/pre&gt;<br /> <br /> It will be rendered to this table:<br /> <br /> <br /> {{DatatypeProperty <br /> | labels = <br /> {{label|en|height}}<br /> | comments =<br /> | rdfs:range = Length<br /> }}<br /> &lt;/noinclude&gt;</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Template:DatatypeProperty&diff=28124 2013-08-29T13:38:34Z

<p>Chrisahn: use Template:LinkProperties also for rdfs:subPropertyOf</p> <hr /> <div>&lt;includeonly&gt;{{DisclaimerOntologyProperty}}<br /> <br /> &lt;table class=&quot;wikitable&quot;&gt;<br /> &lt;tr&gt;<br /> &lt;th colspan=&quot;2&quot; style=&quot;text-align:left&quot;&gt;Ontology datatype property &lt;small&gt;([[Template:DatatypeProperty|&lt;span style=&quot;cursor:help;&quot;&gt;help&lt;/span&gt;]])&lt;/small&gt;&lt;/th&gt;<br /> &lt;/tr&gt;<br /> {{#if:{{{labels|}}}|{{{labels}}}|<br /> {{#if:{{{rdfs:label@en|}}}|&lt;!-- no message --&gt;|<br /> &lt;tr&gt;<br /> &lt;td colspan=&quot;2&quot;&gt;please define an English label: &lt;nowiki&gt;labels = {{label|en|...}} ...&lt;/nowiki&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> }}<br /> }}<br /> {{#if:{{{rdfs:label@ar|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ar&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ar}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@bg|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@bg&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@bg}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@bn|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@bn&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@bn}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ca|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ca&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ca}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@cs|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@cs&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@cs}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@de|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@de&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@de}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@el|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@el&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@el}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@en|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@en&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@en}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@es|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@es&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@es}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@fr|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@fr&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@fr}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ga|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ga&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ga}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@hi|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@hi&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@hi}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@hr|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@hr&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@hr}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@hu|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@hu&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@hu}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@it|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@it&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@it}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ja|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ja&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ja}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ko|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ko&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ko}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@nl|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@nl&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@nl}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@pl|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@pl&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@pl}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@pt|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@pt&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@pt}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ru|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ru&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ru}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@sl|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@sl&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@sl}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@tr|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@tr&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@tr}}}&lt;/td&gt;&lt;/tr&gt;}}<br /> {{{comments|}}}<br /> {{#if:{{{rdfs:comment@en|}}}|<br /> &lt;tr&gt;<br /> &lt;td&gt;rdfs:comment@en&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:comment@en}}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> }}<br /> &lt;tr&gt;<br /> &lt;td&gt;rdfs:domain&lt;/td&gt;<br /> &lt;td&gt;{{linkClasses|{{{rdfs:domain|}}}|owl:Thing}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;rdfs:range&lt;/td&gt;<br /> &lt;td&gt;{{#if:{{{rdfs:range|}}}|[[Datatype:{{{rdfs:range}}}|{{{rdfs:range}}}]]|&lt;span style=&quot;color:red&quot;&gt;please define range&lt;/span&gt;}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;rdf:type&lt;/td&gt;<br /> &lt;td&gt;{{#if:{{{rdf:type|}}}|{{{rdf:type}}}}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;rdfs:subPropertyOf&lt;/td&gt;<br /> &lt;td&gt;{{linkProperties|{{{rdfs:subPropertyOf|}}}}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;owl:equivalentProperty&lt;/td&gt;<br /> &lt;td&gt;{{linkProperties|{{{owl:equivalentProperty|}}}}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> &lt;/includeonly&gt;<br /> &lt;noinclude&gt;The '''&lt;nowiki&gt;{{DatatypeProperty}}&lt;/nowiki&gt;''' template can be used to define ontology datatype properties.<br /> <br /> === Usage ===<br /> <br /> &lt;pre&gt;<br /> {{DatatypeProperty <br /> | labels =<br /> {{label|en|...}}<br /> {{label|..|...}}<br /> | comments =<br /> {{comment|en|...}}<br /> {{comment|..|...}}<br /> | rdfs:domain =<br /> | rdfs:range =<br /> | rdf:type =<br /> | rdfs:subPropertyOf =<br /> | owl:equivalentProperty =<br /> }}<br /> &lt;/pre&gt;<br /> <br /> ==== Details ====<br /> <br /> * '''labels''': should be defined to provide a human-readable version of a property's name. Use ISO language code 639-1 (e.g. &lt;nowiki&gt;{{label|en|...}}&lt;/nowiki&gt;).<br /> * '''comments''': should be defined to provide a human-readable description of a property. Use ISO language code 639-1 (e.g. &lt;nowiki&gt;{{comment|en|...}}&lt;/nowiki&gt;).<br /> * '''rdfs:domain''': is used to state that any resource that has a given property is an instance of the stated class. If left empty, owl:Thing is assumed.<br /> * '''rdfs:range''': is used to state that the values of a property are instances of the stated class. <br /> ** XSD Datatypes: xsd:date, xsd:time, xsd:dateTime, xsd:gYear, xsd:gYearMonth, xsd:gMonth, xsd:gMonthDay, xsd:gDay, xsd:boolean, xsd:string, xsd:integer, xsd:double, xsd:float<br /> ** [[DBpedia Datatypes]]<br /> * '''rdf:type''': currently, only [http://www.w3.org/TR/owl-ref/#FunctionalProperty-def owl:FunctionalProperty] is supported.<br /> * '''rdfs:subPropertyOf''': defines that the property is a subproperty of some other property. Formally this means that if P1 is a subproperty of P2, then the property values of P1 are a subset of the property values of P2.<br /> * '''owl:equivalentProperty''':<br /> <br /> For backwards compatibilty, the following format for labels and comments is also possible but '''deprecated''':<br /> <br /> &lt;pre&gt;<br /> {{DatatypeProperty<br /> | rdfs:label@en =<br /> | rdfs:label@.. =<br /> | rdfs:comment@en =<br /> &lt;/pre&gt;<br /> <br /> === Example ===<br /> <br /> The definition of the DBpedia ontology property [[OntologyProperty:height|height]]:<br /> &lt;pre&gt;<br /> {{DatatypeProperty <br /> | labels = <br /> {{label|en|height}}<br /> | comments =<br /> | rdfs:range = Length<br /> }}<br /> &lt;/pre&gt;<br /> <br /> It will be rendered to this table:<br /> <br /> <br /> {{DatatypeProperty <br /> | labels = <br /> {{label|en|height}}<br /> | comments =<br /> | rdfs:range = Length<br /> }}<br /> &lt;/noinclude&gt;</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Template:DatatypeProperty&diff=28123 2013-08-29T13:36:13Z

<p>Chrisahn: use Template:LinkProperties</p> <hr /> <div>&lt;includeonly&gt;{{DisclaimerOntologyProperty}}<br /> <br /> &lt;table class=&quot;wikitable&quot;&gt;<br /> &lt;tr&gt;<br /> &lt;th colspan=&quot;2&quot; style=&quot;text-align:left&quot;&gt;Ontology datatype property &lt;small&gt;([[Template:DatatypeProperty|&lt;span style=&quot;cursor:help;&quot;&gt;help&lt;/span&gt;]])&lt;/small&gt;&lt;/th&gt;<br /> &lt;/tr&gt;<br /> {{#if:{{{labels|}}}|{{{labels}}}|<br /> {{#if:{{{rdfs:label@en|}}}|&lt;!-- no message --&gt;|<br /> &lt;tr&gt;<br /> &lt;td colspan=&quot;2&quot;&gt;please define an English label: &lt;nowiki&gt;labels = {{label|en|...}} ...&lt;/nowiki&gt;&lt;/td&gt;<br /> &lt;/tr&gt;<br /> }}<br /> }}<br /> {{#if:{{{rdfs:label@ar|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ar&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ar}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@bg|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@bg&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@bg}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@bn|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@bn&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@bn}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ca|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ca&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ca}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@cs|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@cs&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@cs}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@de|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@de&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@de}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@el|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@el&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@el}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@en|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@en&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@en}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@es|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@es&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@es}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@fr|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@fr&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@fr}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ga|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ga&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ga}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@hi|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@hi&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@hi}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@hr|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@hr&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@hr}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@hu|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@hu&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@hu}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@it|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@it&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@it}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ja|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ja&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ja}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ko|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ko&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ko}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@nl|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@nl&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@nl}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@pl|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@pl&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@pl}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@pt|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@pt&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@pt}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@ru|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@ru&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@ru}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@sl|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@sl&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@sl}}}&lt;/td&gt;&lt;/tr&gt;}} {{#if:{{{rdfs:label@tr|}}}|&lt;tr&gt;<br /> &lt;td width=&quot;150px&quot;&gt;rdfs:label@tr&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:label@tr}}}&lt;/td&gt;&lt;/tr&gt;}}<br /> {{{comments|}}}<br /> {{#if:{{{rdfs:comment@en|}}}|<br /> &lt;tr&gt;<br /> &lt;td&gt;rdfs:comment@en&lt;/td&gt;<br /> &lt;td&gt;{{{rdfs:comment@en}}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> }}<br /> &lt;tr&gt;<br /> &lt;td&gt;rdfs:domain&lt;/td&gt;<br /> &lt;td&gt;{{linkClasses|{{{rdfs:domain|}}}|owl:Thing}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;rdfs:range&lt;/td&gt;<br /> &lt;td&gt;{{#if:{{{rdfs:range|}}}|[[Datatype:{{{rdfs:range}}}|{{{rdfs:range}}}]]|&lt;span style=&quot;color:red&quot;&gt;please define range&lt;/span&gt;}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;rdf:type&lt;/td&gt;<br /> &lt;td&gt;{{#if:{{{rdf:type|}}}|{{{rdf:type}}}}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;rdfs:subPropertyOf&lt;/td&gt;<br /> &lt;td&gt;{{#if:{{{rdfs:subPropertyOf|}}}|{{{rdfs:subPropertyOf}}}}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;tr&gt;<br /> &lt;td&gt;owl:equivalentProperty&lt;/td&gt;<br /> &lt;td&gt;{{linkProperties|{{{owl:equivalentProperty|}}}}}&lt;/td&gt;<br /> &lt;/tr&gt;<br /> &lt;/table&gt;<br /> &lt;/includeonly&gt;<br /> &lt;noinclude&gt;The '''&lt;nowiki&gt;{{DatatypeProperty}}&lt;/nowiki&gt;''' template can be used to define ontology datatype properties.<br /> <br /> === Usage ===<br /> <br /> &lt;pre&gt;<br /> {{DatatypeProperty <br /> | labels =<br /> {{label|en|...}}<br /> {{label|..|...}}<br /> | comments =<br /> {{comment|en|...}}<br /> {{comment|..|...}}<br /> | rdfs:domain =<br /> | rdfs:range =<br /> | rdf:type =<br /> | rdfs:subPropertyOf =<br /> | owl:equivalentProperty =<br /> }}<br /> &lt;/pre&gt;<br /> <br /> ==== Details ====<br /> <br /> * '''labels''': should be defined to provide a human-readable version of a property's name. Use ISO language code 639-1 (e.g. &lt;nowiki&gt;{{label|en|...}}&lt;/nowiki&gt;).<br /> * '''comments''': should be defined to provide a human-readable description of a property. Use ISO language code 639-1 (e.g. &lt;nowiki&gt;{{comment|en|...}}&lt;/nowiki&gt;).<br /> * '''rdfs:domain''': is used to state that any resource that has a given property is an instance of the stated class. If left empty, owl:Thing is assumed.<br /> * '''rdfs:range''': is used to state that the values of a property are instances of the stated class. <br /> ** XSD Datatypes: xsd:date, xsd:time, xsd:dateTime, xsd:gYear, xsd:gYearMonth, xsd:gMonth, xsd:gMonthDay, xsd:gDay, xsd:boolean, xsd:string, xsd:integer, xsd:double, xsd:float<br /> ** [[DBpedia Datatypes]]<br /> * '''rdf:type''': currently, only [http://www.w3.org/TR/owl-ref/#FunctionalProperty-def owl:FunctionalProperty] is supported.<br /> * '''rdfs:subPropertyOf''': defines that the property is a subproperty of some other property. Formally this means that if P1 is a subproperty of P2, then the property values of P1 are a subset of the property values of P2.<br /> * '''owl:equivalentProperty''':<br /> <br /> For backwards compatibilty, the following format for labels and comments is also possible but '''deprecated''':<br /> <br /> &lt;pre&gt;<br /> {{DatatypeProperty<br /> | rdfs:label@en =<br /> | rdfs:label@.. =<br /> | rdfs:comment@en =<br /> &lt;/pre&gt;<br /> <br /> === Example ===<br /> <br /> The definition of the DBpedia ontology property [[OntologyProperty:height|height]]:<br /> &lt;pre&gt;<br /> {{DatatypeProperty <br /> | labels = <br /> {{label|en|height}}<br /> | comments =<br /> | rdfs:range = Length<br /> }}<br /> &lt;/pre&gt;<br /> <br /> It will be rendered to this table:<br /> <br /> <br /> {{DatatypeProperty <br /> | labels = <br /> {{label|en|height}}<br /> | comments =<br /> | rdfs:range = Length<br /> }}<br /> &lt;/noinclude&gt;</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Template:LinkProperty&diff=28122 2013-08-29T13:33:24Z

<p>Chrisahn: Created page with '&lt;includeonly&gt;{{#switch:{{#explode:{{item|{{{1|}}}|{{{2|}}}}}|:|0}} |schema\ =[http://schema.org/{{#explode:{{item|{{{1|}}}|{{{2|}}}}}|:|1}} {{item|{{{1|}}}|{{{2|}}}}}] |bibo\ =[h...'</p> <hr /> <div>&lt;includeonly&gt;{{#switch:{{#explode:{{item|{{{1|}}}|{{{2|}}}}}|:|0}}<br /> |schema\ =[http://schema.org/{{#explode:{{item|{{{1|}}}|{{{2|}}}}}|:|1}} {{item|{{{1|}}}|{{{2|}}}}}]<br /> |bibo\ =[http://purl.org/ontology/bibo/{{#explode:{{item|{{{1|}}}|{{{2|}}}}}|:|1}} {{item|{{{1|}}}|{{{2|}}}}}]<br /> |wikidata\ =[http://www.wikidata.org/wiki/Property:{{#explode:{{item|{{{1|}}}|{{{2|}}}}}|:|1}} {{item|{{{1|}}}|{{{2|}}}}}]<br /> |[[OntologyProperty:{{item|{{{1|}}}|{{{2|}}}}}|{{item|{{{1|}}}|{{{2|}}}}}]]}}&lt;/includeonly&gt;&lt;noinclude&gt;<br /> &lt;!--<br /> Explanation of what's going on above:<br /> If the item with index {{{2}}} in list {{{1}}}<br /> has a part before the colon &quot;:&quot; (see note 1)<br /> and that part is equal to &quot;schema&quot;, &quot;bibo&quot;, &quot;wikidata&quot; (see note 2)<br /> then we use the part after the colon and genereate a link to schema.org, bibo, wikidata.<br /> Otherwise, we generate an internal link.<br /> Notes: <br /> (1) This #ifeq would also be true if the item was<br /> just &quot;schema\&quot;, but that's almost impossible.<br /> (2) #explode adds a backslash when dealing with colons,<br /> that's why we use the string &quot;schema\&quot;, not &quot;schema&quot;.<br /> TODO: add more targets besides schema.org, bibo, wikidata<br /> --&gt;<br /> Generates a link to a class from a list. First parameter is the list (comma-separated strings), second parameter is the index (zero-based).<br /> &lt;/noinclude&gt;</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Template:LinkProperties&diff=28121 2013-08-29T13:27:04Z

<p>Chrisahn: adapted copy of Template:LinkClasses</p> <hr /> <div>&lt;includeonly&gt;{{#if:{{item|{{{1|}}}|0}}|{{linkProperty|{{{1}}}|0}}{{#if:{{item|{{{1}}}|1}}|, {{linkProperty|{{{1}}}|1}}{{#if:{{item|{{{1}}}|2}}|, {{linkProperty|{{{1}}}|2}}{{#if:{{item|{{{1}}}|3}}|, {{linkProperty|{{{1}}}|3}}{{#if:{{item|{{{1}}}|4}}|, {{linkProperty|{{{1}}}|4}}|}}|}}|}}|}}|{{{2|}}}}}&lt;/includeonly&gt;&lt;noinclude&gt;<br /> Generates links to properties in a list. First parameter is the list (comma-separated strings), second parameter is the default value (may be empty, will not become a link).<br /> &lt;/noinclude&gt;</div>

Chrisahn https://mediawiki1.informatik.uni-mannheim.de/index.php?title=Template:LinkClass&diff=28120 2013-08-29T13:23:03Z

<p>Chrisahn: comment: bibo</p> <hr /> <div>&lt;includeonly&gt;{{#switch:{{#explode:{{item|{{{1|}}}|{{{2|}}}}}|:|0}}<br /> |schema\ =[http://schema.org/{{#explode:{{item|{{{1|}}}|{{{2|}}}}}|:|1}} {{item|{{{1|}}}|{{{2|}}}}}]<br /> |bibo\ =[http://purl.org/ontology/bibo/{{#explode:{{item|{{{1|}}}|{{{2|}}}}}|:|1}} {{item|{{{1|}}}|{{{2|}}}}}]<br /> |[[OntologyClass:{{item|{{{1|}}}|{{{2|}}}}}|{{item|{{{1|}}}|{{{2|}}}}}]]}}&lt;/includeonly&gt;&lt;noinclude&gt;<br /> &lt;!--<br /> Explanation of what's going on above:<br /> If the item with index {{{2}}} in list {{{1}}}<br /> has a part before the colon &quot;:&quot; (see note 1)<br /> and that part is equal to &quot;schema&quot; (see note 2)<br /> then we use the part after the colon and genereate a link to schema.org or bibo.<br /> Otherwise, we generate an internal link.<br /> Notes: <br /> (1) This #ifeq would also be true if the item was<br /> just &quot;schema\&quot;, but that's almost impossible.<br /> (2) #explode adds a backslash when dealing with colons,<br /> that's why we use the string &quot;schema\&quot;, not &quot;schema&quot;.<br /> TODO: add more targets besides schema.org and bibo<br /> --&gt;<br /> Generates a link to a class from a list. First parameter is the list (comma-separated strings), second parameter is the index (zero-based).<br /> &lt;/noinclude&gt;</div>

Chrisahn