Difference between revisions of "Semantic Wiki/Concepts"

From BattleMaster Wiki
Jump to navigation Jump to search
 
(9 intermediate revisions by one other user not shown)
Line 1: Line 1:
Concepts are much like Categories, except that they are computed dynamically from semantic information. As such, they are more flexible and can replace categories in many cases.
+
Concepts are much like Categories, except that they are computed dynamically from semantic information. As such, they are more flexible and can replace categories in many cases. In addition, they can be nested, i.e. a concept can be used in a semantic query. This often simplifies queries a lot.
  
For example, "Regions of Atamara" could be implemented as a category. But so could "Cities", and "Regions on the coast" and "Regions of the Caligan Empire" and so forth. In fact, we're already drowning in categories like that.
+
Using the most base category only, e.g. "Region" and putting all the details into semantics, allows us to form '''concepts'''. For most contributors, that means simply using <nowiki>[[Concept:(something)]]</nowiki> instead of <nowiki>[[Category:(something)]]</nowiki>.
  
Using the most base category only, e.g. "Region" and putting all the details into semantics, allows us to form '''concepts'''. The result would be the same, we can find all regions of Atamara by saying:
+
New concepts are easily defined as well:
 
+
<pre>
<nowiki>
+
{{#concept:  [[Category:Regions]] [[located on::Atamara]]
{{#concept:  [[Category:Region]] [[located on::Atamara]]
 
 
| Regions of Atamara
 
| Regions of Atamara
 
}}
 
}}
</nowiki>
+
</pre>
 +
 
 +
Not only can "Regions of Atamara" be implemented as a concept, but so could "Cities", and "Regions on the coast", etc.
 +
 
 +
Once a concept is created, you can use <nowiki>[[Concept:Regions of Atamara]]</nowiki> in your queries like you would a category or property, and it will all automagically be updated with changes, etc.
 +
For example: We have defined a concept "Duchies" below (a region that is of type city or stronghold). Now we do not have to update a potentially large number of pages when the concept of a duchy changes (e.g. when for some reason we make it possible for townslands to be a duchy center, or if a new region type is introduced, etc.)
 +
 
 +
 
 +
= Concept or Category ? =
 +
We also implement a lot of things as categories, because that gives nice auto-generated page links. And Categories can also be used like Concepts in queries. And then we have the same thing again as [[Semantic Wiki/Lists|Lists]].
 +
 
 +
The strength of Concepts is that they can be defined from virtually anything, which is a bit more difficult for categories. [[:Category:Atamara Regions]] is probably more useful than and fulfills the same purpose as [[Concept:Regions of Atamara]].
 +
However, [[Concept:Duchies]] is a little more difficult to replicate as a Category. And a concept of, say, "big cities" where the actual definition of "big" differs from island to island, would be much easier defined as a concept.
 +
 
 +
The main advantage of a concept is that it relies entirely on semantic data and requires no changes to the pages involved. Where we strictly use a low number of templates, i.e. where updating a large number of pages is trivial, like in the regions, a category is easy to add. But if you have all the semantics in place already, and then decide you'd like to add a new category and it's not easy to do it via a change to a template or two, then you will probably want a concept.
 +
 
 +
Another advantage of concepts is that they have a description, which is being used in inline queries or RDF output.
 +
 
  
  
 
= Concept Pages =
 
= Concept Pages =
 +
(these are still being experimented with and not all work correctly)
  
* [[Concept:Realms by Island]]
+
* Realms by Island
** [[Concept:Realms of the East Island]]
+
** [[Concept:Realms of East Island]]
 
** [[Concept:Realms of Atamara]]
 
** [[Concept:Realms of Atamara]]
 
** [[Concept:Realms of Beluaterra]]
 
** [[Concept:Realms of Beluaterra]]
** [[Concept:Realms of the Far East]]
+
** [[Concept:Realms of Far East]]
 
** [[Concept:Realms of Dwilight]]
 
** [[Concept:Realms of Dwilight]]
  
* [[Concept:Regions by Island]]
+
* Regions by Island
** [[Concept:Regions of the East Island]]
+
** [[Concept:Regions of East Island]]
** [[Concept:Regions of Atamara]]
+
** [[Concept:Regions of Atamara]] (also available as a category: [[:Category:Atamara Regions]])
 
** [[Concept:Regions of Beluaterra]]
 
** [[Concept:Regions of Beluaterra]]
** [[Concept:Regions of the Far East]]
+
** [[Concept:Regions of Far East]]
 
** [[Concept:Regions of Dwilight]]
 
** [[Concept:Regions of Dwilight]]
 +
 +
* Regions by other properties
 +
** [[Concept:Regions without a lord]]
 +
** [[Concept:Strongholds]]
 +
** [[Concept:Duchies]]
 +
 +
* Unique Items
 +
** [[Concept:Unique Items]]

Latest revision as of 16:28, 3 September 2009

Concepts are much like Categories, except that they are computed dynamically from semantic information. As such, they are more flexible and can replace categories in many cases. In addition, they can be nested, i.e. a concept can be used in a semantic query. This often simplifies queries a lot.

Using the most base category only, e.g. "Region" and putting all the details into semantics, allows us to form concepts. For most contributors, that means simply using [[Concept:(something)]] instead of [[Category:(something)]].

New concepts are easily defined as well:

{{#concept:  [[Category:Regions]] [[located on::Atamara]]
| Regions of Atamara
}}

Not only can "Regions of Atamara" be implemented as a concept, but so could "Cities", and "Regions on the coast", etc.

Once a concept is created, you can use [[Concept:Regions of Atamara]] in your queries like you would a category or property, and it will all automagically be updated with changes, etc. For example: We have defined a concept "Duchies" below (a region that is of type city or stronghold). Now we do not have to update a potentially large number of pages when the concept of a duchy changes (e.g. when for some reason we make it possible for townslands to be a duchy center, or if a new region type is introduced, etc.)


Concept or Category ?

We also implement a lot of things as categories, because that gives nice auto-generated page links. And Categories can also be used like Concepts in queries. And then we have the same thing again as Lists.

The strength of Concepts is that they can be defined from virtually anything, which is a bit more difficult for categories. Category:Atamara Regions is probably more useful than and fulfills the same purpose as Concept:Regions of Atamara. However, Concept:Duchies is a little more difficult to replicate as a Category. And a concept of, say, "big cities" where the actual definition of "big" differs from island to island, would be much easier defined as a concept.

The main advantage of a concept is that it relies entirely on semantic data and requires no changes to the pages involved. Where we strictly use a low number of templates, i.e. where updating a large number of pages is trivial, like in the regions, a category is easy to add. But if you have all the semantics in place already, and then decide you'd like to add a new category and it's not easy to do it via a change to a template or two, then you will probably want a concept.

Another advantage of concepts is that they have a description, which is being used in inline queries or RDF output.


Concept Pages

(these are still being experimented with and not all work correctly)