Difference between revisions of "Semantic Wiki"

From BattleMaster Wiki
Jump to navigation Jump to search
Line 32: Line 32:
 
= TODO / Questions =
 
= TODO / Questions =
 
* Do we want to add [http://www.mediawiki.org/wiki/Extension:Halo_Extension Halo] ?
 
* Do we want to add [http://www.mediawiki.org/wiki/Extension:Halo_Extension Halo] ?
 +
**Interesting. The properties and categories editor looks helpful. It was hard to find, though, as their demo wiki is a spam linkfarm. For those interested in checking it out: [http://halowiki.ontoprise.de/halowiki/index.php?title=Ketene&action=edit take a look here]. Also, the annotate tab on the pages lists all links/properties on a page.

Revision as of 16:16, 5 February 2009

Introduction

The BattleMaster Wiki uses Semantic MediaWiki to turn itself into a full-blown Semantic Web.

What does that mean when we strip out the buzzwords?

It means that - with proper markup - the wiki "understands" its own content, and can generate answers to fairly complicated questions such as "which realms (on any island) have the highest population-to-nobles ratios?" - not because any human has actually done the math, but because the wiki contains information about the realms, their populations and the number of nobles in them, and can do the math itself.

Yes, we can use external data sources and with time the game will be extended to offer them. That means that Semantic Web also means you do not have to hand-craft (and update constantly) the boxes that contain basic realm data such as name, regions, population, etc.


Scope

We are not aiming for the big thing, or integration with a world-wide semantic web. BattleMaster is it's own small world, with more well-defined terms and boundaries than the real world (where, for example, it isn't always clear what exactly a "realm" even is). As such, it is well-suited to using the Semantic Web technology.


Supporting Templates

The subpage /Templates discusses templates you can use to make use of Semantic Web functions with minimal additional hassle.


Ontology

This is where we define what is and what isn't, i.e. the semantic relations that we want to use. This is necessary or useful because it avoids duplications that would really mess things up. For example, if we call the game worlds "islands" in some cases and "continents" in others, that will make a lot of queries faulty, as their results will only show those instances that were annotated one way or the other.

Below are the terms that are set and fixed. Please do not modify this list - put new suggestions on the talk page.

Property:located on 
denotes the game-world the item can be found on, e.g. [[located on::Atamara]] tells us this realm, region, religion or whatever can be found on the island/continent Atamara
Property:population 
denotes the population of an item, usually a region or a realm. This is a number type, so it must contain a valid number, even if that is a guess or approximation. Terms like "ca. 1 mio" are invalid, use "1000000" instead. Example: [[population::5200]]
Property:part of 
is for general parent/child relations between items and places. It is mostly used to note on region pages which realm and duchy they belong to, for example: [[part of::Sirion]]. This should be used in all the region infobox templates.
Property:member of 
is for general parent/child relations of characters and persons. It denotes which realms, but also which family a character belongs to, e.g. [[member of::Hawk Family]] or [[member of::Outer Tilog]]

Further terms will be added as we discuss and agree on them.


TODO / Questions

  • Do we want to add Halo ?
    • Interesting. The properties and categories editor looks helpful. It was hard to find, though, as their demo wiki is a spam linkfarm. For those interested in checking it out: take a look here. Also, the annotate tab on the pages lists all links/properties on a page.