Jump to: navigation, search
Community portal of Semantic MediaWiki

Welcome to the community portal. This is the place for general inquiries, your ideas or comments concerning this wiki. Here you may get in touch with one of the admins of this wiki, who also use this portal as a noticeboard.

If you are looking for support with problem about the software itself, please have a look at the info page on getting support.

We are always looking for ways to improve documentation and communication with the community therefore it would help us if you could take 5 minutes of your time and fill out the survey form. Thank you.

First page
First page
Previous page
Previous page
Last page
Last page

Guidance on creating an employee form?


I'm working on creating a single form that produces an infobox for applicant, freelancer and employee pages.

What I would like to do[edit]

These three types of pages share 90% of the same fields -- that's why I opted for a single class instead of 3 different classes. The issue is that the remainder 10% are fields that are exclusive to one or more of the aforementioned types of pages. For example: "Interview Date" should only be displayed in the infobox when the type of page is an applicant. Another example: "Join Date" should only display on employee type of pages (it would be silly to display "Join Date" on an applicant type of page -- as they're in the selection process).

What I have tried[edit]

So far I have modified the form to use "show on select". There is a field property called "Type" which allows the user to select between applicant, freelancer and employee. Depending on the selection, certain fields are shown and others are hidden (the 10% I talked about before). The majority of fields are shared by all three types.

The problem is that while these fields hide and show themselves correctly when editing a page with the form, they ALL display regardless on the template, e.g. "Join Date" and "Interview Date" shown up on all three types of pages.

What I need[edit]

I've been trying to figure out the ideal way to have the template (which controls the infobox display) to have the same hide and show functionality as the "show on select" option that the form provides.

These are the options I have considered:

  • Add an #ask query to the template which uses FULLPAGENAME and ?Has type to retrieve whether the page is of an applicant, freelancer or employee type. From there use IF statements on each of the fields that should be hidden/displayed according to the value of ?Has type. E.g., if the ?Has value = Applicant then display "Interview Date", else don't display it.
  • Create a template for each type of page to display only the appropriate fields, and then call the template by, again, using an #ask query and IF statements on the person page.

Both options seem messy and I doubt they'd update properly (due to asking for info that is on the same page where the value is set in order to display/hide fields ...). I also have the feeling I'm missing something obvious and it's doing my head in.

My questions[edit]

  • Has anyone tried to create a similar type of form in the past?
  • What's the best way of going about this?

Any guidance, tips or pointers in the right direction would be greatly appreciated.

If you need more information or clarification please let me know.

Thank you.

Optimae (talk)01:18, 18 January 2014

You may be missing something - in the template, you don't need to use a query to get the value of a field, if you already have that field. In other words, you could have something like "{{#ifeq:{{{Type|}}}|Employee|....}}".

Yaron Koren (talk)17:58, 19 January 2014

ParserFunctions and Templates and SMW???

I have some templates that use ParserFunctions (specifically #if, if that matters). How do I use SMW properties with those templates? For example, I have
| termend =

| termstart =

Where I have a property for term start (Term start) and one for term end (Term end). How do I tie these template items to those properties? (It's got to be possible, right?)

K llandon (talk)21:42, 22 April 2014

Okay, apparently it doesn't like my code, even inside code tags. See for example at - we're talking about the part with lots of {{{ for terms (I've pulled this template over from Wikipedia).

K llandon (talk)21:50, 22 April 2014

SRF / Jqplotchart - max parameter ?

A thread, portal/SRF / Jqplotchart - max parameter ?, was moved from here to Help talk:Jqplotchart format. This move was made by Kghbln (Talk | contribs) on 15 April 2014 at 17:11.

Not returning properties and/or categories in custom namespaces

A thread, portal/Not returning properties and/or categories in custom namespaces, was moved from here to Help talk:$smwgNamespacesWithSemanticLinks. This move was made by Kghbln (Talk | contribs) on 15 April 2014 at 17:10.

"sort" option in query does not include results that have no value in sorted field

Edited by another user.
Last edit: 22:23, 4 March 2014


The following query brings up no results (because Begin Date is blank):

{{#ask:[[Category:Market research]]

But this query brings up all results:

{{#ask:[[Category:Market research]]

I don't think that it logically follows that a "sort" option should exclude results where sorted field is blank.

Patelmm79 (talk)22:00, 4 March 2014

Well, if you do not query for a property you cannot sort by it since your printout statement cannot be fulfilled. Somehow you have to pick up the date from the pages/subobjects with the query. See sorting results. So your query should be

{{#ask:[[Category:Market research]]
[[kgh]] (talk)22:29, 4 March 2014

This is about sort statements that filter out the rows in which the sorted field is null, I think. An old and already reported problem of SMW.

Alexander Mashintalk03:42, 5 March 2014

How to delete pages that are not connected to a category... [SMW]


Could someone please explain to me how to delete pages in WIKI? The url is There are some old pages that are not connected to a category that need to be deleted.



Simone (talk)13:10, 15 January 2014

You will need access to the wiki and the "delete" permission which is usually connected to the "administrator" group. After that it is just a matter of clicking the right button in the action menu at the top of a page.

[[kgh]] (talk)14:40, 15 January 2014

Has anybody experience with the SemanticGraph extension and SMW versions > 1.7?

Hello all,

I'm new here. Perhaps this has been asked before, but I didn't find a possibility to search the forum for keywords. And I'm not sure if this is the right place for this question, should I use the mailing list instead? But anyway, here it is:

I want to present the relations in my knowledge base as navigable graphic. I have found the extension SemanticGraph [1] which looks quite nice. Unfortunately there is only a version available which works with SMW 1.5. I am working with SMW 1.7.1 and I couldn't get this to work.

Has anybody experience with this extension in combination with newer versions of SMW, particular 1.7.1 and can tell me what to do?

Thanks, Martin

Martinscm (talk)18:43, 10 January 2014

You can always use template format combined with GraphViz.

Alex Mashintalk10:10, 11 January 2014

css styling for <code> tags.

Hello. Templates can not be used between <source lang = "blabla"> tags but they can be used between <code> tags. Would it be possible to put the below css in MediaWiki:Common.css? This greatly improves readability of the text between <code> tags? Regards.

 * Redesigned <code>.
 * Should improve readability by not having the samples blend into the white background,
 * but by having a visible (though subtle) border around the code sample.
code {
  border: 1px solid #ddd;
  padding: 1px 4px;
  border-radius: 2px;
Jongfeli (talk)18:28, 8 January 2014

Heiya Jongfeli, I added this to Common.css. Didn't MediaWiki use this for a couple of months before it was dropped for some reason. Looks pretty familiar to me. Cheers

[[kgh]] (talk)21:39, 8 January 2014

Sorry, yes you are right, but I can't remember if I got it from MediaWiki or Wikipedia. This means I did not "write" the above css :). Thanks for putting it in common.css . Regards

Jongfeli (talk)22:16, 8 January 2014

Well, you never claimed that you were the author. :)

[[kgh]] (talk)22:24, 8 January 2014

Demos not working

Hi, I was searching for some result formats and I think some of them are broken or misconfigured, see:

Jaider Msg21:52, 2 January 2014

Thanks for reporting. I filed an issue about the fatal errors here

Jeroen De Dauw (talk)01:39, 3 January 2014

Fatal errors have been fixed.

Jeroen De Dauw (talk)01:56, 3 January 2014

Querying for non-zero values does not seem to work


The following query searches for all competitor in Mexico with a yield that is greater than zero. However, result does list competitors with zero yield. {{#ask:[[CompetitorlName::<q>[[Country::Mexico]]</q>]][[Yield::>0]] |?Date |?Yield |format=table }}

However, this query eliminates those competitors with zero yield {{#ask:[[CompetitorName::<q>[[Country::Mexico]]</q>]][[Yield::>0.000001]] |?Date |?Yield |format=table }}

Am I doing the first query incorrectly somehow?

Patelmm79 (talk)23:21, 20 December 2013

Use {{#ask:[[CompetitorlName::<q>[[Country::Mexico]]</q>]][[Yield::≥0]] |?Date |?Yield |format=table }}. Alternatively, set $smwStrictComparators to false.

Alex Mashintalk09:25, 21 December 2013

Querying for non-empty values


I'm trying to query those pages to count where a particular property is not empty. I've used as follows:

{{#ask:[[Competitor::! ]] |?Competitor |format=count }}

A number does result indicating how many pages have "Competitor" not null, but an error results as well: "Empty strings are not accepted".

Let me ask, is this the right way to query for non-empty properties? If this is the only possible way to do, is there a way to suppress the error?

Patelmm79 (talk)00:14, 4 December 2013

Have you tried {{#ask:[[Competitor::+]]|format=count}}?

Alex Mashintalk04:43, 4 December 2013

Thanks, that works great! And how about those situations where the field IS empty?

I tried [[Competitor::-]], but did not work.

Patelmm79 (talk)21:47, 12 December 2013

This is not covered by SMW. You can only query for existing property values. Probably you may do a {{#if: {{{Competitor}}} | | {{#set:Competitor provided=No}} }} with the property "Competitor provided" is of data type "boolean" and then query for pages with the "No" boolean.

[[kgh]] (talk)22:42, 12 December 2013

Thanks for that!

Patelmm79 (talk)22:15, 20 December 2013

Form Driven Knowledge Base


I am looking for an open source solution that would allow me to create an internal knowledge base for our customer service team.

What I want to do is be able to populate the knowledge base using forms. I want to capture and maintain information in a standardized way. For instance, our customer service team wants to document certain characteristics and FAQs on the customers we service so that all representatives can reference it without having to ask the same questions over and over again. In the ideal case, the customer service reps would go to the knowledge base, search for the customer they wanted the information on, and then receive a knowledge base article on that customer with a variety of different types of information - a table of key customer contacts and their contact information, notes on the client, any relevant documents, FAQs with answers, etc. Furthermore, when a customer service rep creates a knowledge base article on a customer, I'd like for them to input these values through a form (with text fields, drop down boxes, data pickers, etc.).

I came close to accomplishing this with MediaWiki and the Semantic Forms add-on, however, I'm having trouble creating constructs for arrays of information. For instance, I want our reps to be able to add multiple contacts for a customer. I created a form per the example provided in the documentation, however, adding the contacts via contact names doesn't seem to allow for multiple contacts with the same name stored independently per customer. I hope that makes sense.

Can anyone help point me in the right direction to accomplish this?

Thanks in advance.

Mabraham77 (talk)18:57, 9 December 2013

You can't store different contacts (or more generally, entities) with the same name. If you have two different contacts named "John Smith" (I assume that's the kind of thing you're asking about), you'll have to use some kind of disambiguation scheme - like including the middle name, or company name, or something. If you're creating contact pages via a form, you could do it by using the "one-step process" and including "unique ID" in the page name formula.

Yaron Koren (talk)20:58, 9 December 2013

[Closed] Stumped by some weird problem.

Edited by author.
Last edit: 01:04, 27 August 2013


I'm kinda stumped by some problem at a mediawiki-site.

I'm not sure what's up here, what might be the root of the problem, or how to describe/report it.


Site background: Game relate, and game-user driven content and code(templates).

  • Recently update (by site owner) from MediaWiki v1.18(if I'm correct) to MediaWiki v1.21.1
  • Also using Semantic MediaWiki V1.8.0.5. (RoB-site relies heavy on this one.)
  • Additional site wiki setup info:

Main template used on most, and related problem pages.

General rundown:
There is this page . On that page the "Object(s) Required" infobox field list the objects/pages that are needed for this "Running_Rabbit_Sausage". These needed objects/pages are set by the "objectsreq" setting. Those needed objects/pages in turn pickup this information again, and display it in there "Required By" field.

Related setting on that page: "|objectsreq = [[requires::Fox Meat]] x2, [[requires::Intestines]], [[requires::Rabbit Meat]]"

As is one of the required items of Running_Rabbit_Sausage, it displays Running_Rabbit_Sausage as one of its required items ... and here is also the problem I'm looking at. Its displaying two Running_Rabbit_Sausage source related pages, and we at the RoB wiki site are unable to remove the second one, or figuring out whats up here.

Note that the currently second listed page "Running Rabbit Sausage(backup)" is related to trying to fix the problem by moving the source page, and than deleting it. (which did not work)

Anyone might have some additional ideas what up here?


Also asked at [1]

MvGulik (talk)08:55, 26 August 2013

Please. Even some general ideas on what might be triggering something like this are welcome.

One idea was that it might be that there where two active pages with slightly different file-names. File-names that are seen as identical names by the wiki system. Although I think this is highly unlikely. The real problem with this idea is that I don't know how to test, or verify, that. If even possible.

Note: I only have wiki-admin rights. So I have no access to the core wiki system stuff. (Never have setup a wiki-system myself, so would not even know what to do at that level.)

MvGulik (talk)18:17, 29 August 2013

It looks like you've run into some issue with "phantom properties". I would try recreating that "Running Rabbit Sausage(backup)" page, this time without any properties - maybe that will get rid of the phantom property. If that works, you can delete it again.

Yaron Koren (talk)00:56, 30 August 2013

At first, it looked as this was a manifestation of the old MW and SMW bug: both SMW and MW logs use the title under which the article was accessed to edit it rather than the proper article title to record changes into logs and semantic properties into SQL storage. The "proper" title and the title the article was accessed by may differ if they are considered the same by the database collation.

But in your case, it seems that you had somehow managed to create two articles called Running Rabbit Sausage (nbsp, perhaps?), one of which was later renamed into Running Rabbit Sausage (backup). In this case, {{#ask::}} worked correctly. Just remove Running Rabbit Sausage (backup).

Alex Mashintalk16:57, 30 August 2013

I still have to give the replies a closer look and some additional thoughts (+ taking a look at the SMW user mailing list.)

But on the subject of removing the "Running Rabbit Sausage (backup)" page. That page was removed/deleted. And when it was deleted, it had its original content already cleared/replaced with a local {{delete-tag}}.

I just restored that page today (for history restoration reasons). But before doing so I checked if that unwanted second/double linkup was still there, and it was (in this case a link to the, at that moment deleted and cleared, "Running Rabbit Sausage (backup)" page.

Or: Just deleting that page did not work (yet).

I'm getting some additional ideas here. Time to work them out a bit more. ...

MvGulik (talk)18:11, 30 August 2013

Perhaps, you could try to rebuild SMW data for the page Running Rabbit Sausage (backup) (by id).

Alex Mashintalk18:33, 30 August 2013

Shorty after the recent MediaWiki version update of the RoB-wiki site, both the "Database installation and upgrade" and "Data repair and upgrade" where run. (Its unknown if at that point this problem was already there. Although I think it probably was already there, just not spotted yet.)

Those problem pages where also saved without making any changes. Which generally fixes most problems. But that unfortunate did nothing in this case. (Although I'm planning on doing that on all related pages again. Just in case I mist one, and to see if something changes. ... I might get lucky. ;) )

MvGulik (talk)21:01, 30 August 2013

After reading up on MediaWiki ghost pages. I don't see any way a ghost page can be removed/modified by any normal wiki-actions. So I called-in the RoB-wiki owner/bureaucrat to look for, and deleted, the actual ghost file.

Some additional data on the ghost page. (for those interested)

The related page was original create on a other wiki site, and imported to the RoB-wiki. (On the original site there where no signs of the existing of a similar ghost page.)
Considering the ghost page was generating duplicate template output. It was not empty. Which makes sens if the ghost page was created when it was imported.
I tried to check this by modifying the (old)templates it might be using/calling. But after 6 hours that did not resulted in the expected change.
Either the wiki needed more time to auto update, the change would never show this way for ghost pages, or the ghost page was using/calling the Infobox_metaobj template (which I considered implausible).

I think that about reps it up. (unless no ghost page can be found by the RoB-wiki owner.)

Thanks so far for the additional help and information.

MvGulik (talk)13:51, 31 August 2013

Semantic properties cannot be queried unless page is re-saved

I'm running MediaWiki with the Semantic MediaWiki and LinkedWiki extensions. Semantic MediaWiki is configured to store semantic data in 4store and I can query 4store with SPARQL and show the results on the wiki using LinkedWiki extension.

I also have a form that I use to create technology roadmaps and each technology roadmap contains sub-objects that store semantic properties for a particular technology such as support status, start and end dates, and version.

When I save the page, the SPARQL query that queries those semantic properties doesn't return anything because it doesn't see the semantic properties I just saved for the technology roadmap page I created. One way I can make it work it to click on edit and then click on save. I don't have to make any changes, I just re-save the page and it works. Another way to make it work it to run the SMW_refreshData.php script to refresh the page that I just created.

I read about this issue and I tried using extensions that disable cache on a per page basis (MagicNoCache) and I also tried using hooks to run the refresh data script after the page is created (super slow and it didn't work).

Has anyone ever run into a similar problem?

Do you have any ideas on how I can solve this?

Thank you.

Carlosc (talk)16:37, 22 November 2013

Documentation for properties - how do you do that ?

Hello, Hi, how would you efficiently create a document that describes a larger list of properties like this:

property name - type (including enumerations) - optional description

The rationale for this question is that I started worrying that we are too messy, e.g. I would like to make sure that similar properties are not duplicated, insure some kind of naming convention, find the right property names for writing query forms, .... in other words I'd like move from a disorganized folksonomy towards a somewhat controlled vocabulary.

I am just asking for some sort of efficient workflow. Since I use semantic forms I can extract lists with emacs (or another good editor) from the templates, but then I'd still have to add values manually.... unless I overlooked some trick to automatize :)

Btw. this would be nice little extension: user provides either a list of template names or a list of property names or a list of pages. The extension then would generate the "manual". Could be a form or some parser extension or whatever, e.g. some light-weight DPL ?

Good example: Guildwars2 wiki (subpages describe properties)

PS: My Example: list of properties - Most are used in a SF "application"

Daniel K. Schneider (talk)19:05, 17 October 2013

How to create advanced queries with a series of AND/OR's?

How would one create a query like this: get a list of persons where the hair color is brown or black and eye color is blue or green?

The reason im asking this is because im unsure of how precedence is handled in these queries. For example if i wrote:

#ask: [[Category:Person]] [[Hair color::brown]] OR [[Hair color::black]] [[Eye color::blue]] OR [[Eye color::green]]

Would the above query actually be correct? would smw group the logic as: ((hair = brown or black) and (eyes = blue or green)) or would the logic be grouped as: (hair = brown or (hair=black and eyes=blue) or eyes = green)?

Netbrain (talk)08:46, 14 October 2013

On IRC you said you found the answer; for completeness an answer here as well:

  • Firstly, you can combine OR for property values: [[<property>::<value1>||<value2>||.....]]
  • Secondly, you cannot use brackets to group unions/disjoints, so grouping selection criteria works standard left-to-right, with AND stronger than OR.

Therefore, your question could be answered
[[Category:Person]][[Hair color::brown||black]] OR [[Category:Person]][[Eye color::blue||green]]
You can read this as
( [[Category:Person]][[Hair color::brown||black]] ) OR ( [[Category:Person]][[Eye color::blue||green]] )
Since you can't actually use the brackets, you need to repeat the common part for every disjoint selection, as shown with the Category selector.

Jan "Saruman!" S. (talk)13:28, 14 October 2013

You can also use sub queries

<q>[[Category:Person]] [[Hair color::brown]]</q> OR <q>[[Hair color::black]] [[Eye color::blue]]</q> OR [[Eye color::green]]

Not sure which forms are the most efficient. Probably not this one.

Jeroen De Dauw (talk)02:10, 16 October 2013

Thanks, Jeroen, for showing us another method, although I'm not sure I quite understand. The only use case of ... I was previously aware of is the one outlined in this section: [1]. If you're suggesting that ... can also be used in the same way as the rounded brackets above, then it would be powerful piece of syntax that is worth documenting.

Cavila (talk)15:35, 16 October 2013

Template and link=none

I have a small problem with

  • "{{{KWLand}}}" cannot be used as a page name in this wiki.
  • The part "....." of the query was not understood. Results might not be as expected.

my output is ( )

    Teamname             Nation    Points

1. Gipfelstürmer#_rang Flagpicture 60 Points 2. RZKKC#_rang Flagpicture 51 Points 3. Oepfelbaum#_rang Flagpicture 50 Points ....

Question: How i can cut #_rang ? I need only the Frontname like Gipfelstürmer , RZKKC.

I can't change |link=none Option , because I create the flagname, portalname with the data.

Although I change this command, then correct the first Teamname as Link without #_rang, but I can not create correct flagname etc.

Does anyone have a tip for me?

Thanks Bastor

Bastor (talk)19:39, 27 September 2013

enableSemantics("localhost"); breaks my code. cant setup semanticwiki. please help

Hello everyone:

I'm stuck and can't advance at all. When i execute the fourth line, my code breaks

require_once( "$IP/extensions/Validator/Validator.php" );

require_once( "$IP/extensions/DataValues/DataValues.php" );

include_once( "$IP/extensions/SemanticMediaWiki/SemanticMediaWiki.php" ); <---------- no metter what string i put as argument, the program executes??!!??

enableSemantics("localhost"); <------------ breaks my code no metter what string I put there (that i can think of)

Please help me set up my semantic wiki. Thanks you for your time and kind concern.

Jenia (talk)18:11, 8 September 2013

actually its the third line that breaks my code: include_once( "$IP/extensions/SemanticMediaWiki/SemanticMediaWiki.php" );

if i change it to require_once, the server immediately gives me 500 error.

Jenia (talk)22:00, 8 September 2013

What version of the software are you using? 1.9 alpha? If so, you can omit the "enableSemantics" part. And you can omit the first two lines as well, as those libraries will be loaded automatically. You now have the loading in the wrong order, which should not cause any issues, though might - so removing it altogether is definitely good.

Jeroen De Dauw (talk)00:16, 19 September 2013

Please help: No page properties in custom namespace


I'm running Semantic Mediawiki version 1.8 (in a version 1.20.2 Mediawiki). Extensions installed: Semantic Drilldown (1.2.5), Semantic Forms (2.5.1), Semantic Forms Input (0.7), Semantic Internal Objects (0.7.1).

My goal is generating a training overview in a custom namespace 'Training' by querying pages with category 'Training' (which are all in this namespace). However, the pages which are within the namespace don't show up as results, whereas pages with the same content but outside the namespace (i.e. without a namespace, in (Main)) do show up. Looking at the properties of both pages show that properties for the page in the Training-namespace are not applied.

The overview lives in the same namespace under index.php?title=Training:Start with the following query:

{{#ask: [[Category:Training]] |?day }}

I have two pages in the Training category, one inside and one outside the namespace. Only the one outside the namespace is shown as a result to the query above. Content for both is the same:

[[Day::Weekday]] [[Category:Training]]

When I open the 'Browse properties' on both pages I get the following:

Is it an SMW configuration setting? I tried several options from like:

  • $wgNamespacesToBeSearchedDefault
  • $smwgNamespaceIndex
  • $smwgNamespacesWithSemanticLinks
  • $smwgQDefaultNamespaces

but none seem to work. Does anyone have a clue what could be the problem?

Thanks much!

I also asked this question at stackoverflow

Ontzettend (talk)20:46, 30 August 2013

Well, in the meantime you got an answer over there. However, asking via the mailing list is a much faster way to get an answer, even faster than posting here. I am a bit surprised that this does not work for you since this thread really covers everything that may go wrong here.

[[kgh]] (talk)18:04, 11 September 2013

How to design a Semantic Wiki to best understand the concept of Time

My example would be something like the Land Area of Serbia over time. It gets confusing when you add in the concept of Successor States etc but I'm trying to test my understanding of the Semantic Concept through various challenging scenarios.

What would be the ideal way to design the ontology so that I can do a query on different dates for the total Land Area say in 1990, 2005, 2010, 2013.

The last time I used Semantic Wiki was a few years ago but I ended up making the Wiki too confusing and unable to adapt to changes in time without losing previous information. Ie in 2008 Kosovo declared independence so pre 2008 the query should respond with the land area of Serbia+Kosovo but post 2008 it should respond with just the land area of Serbia.

To make it even more complicated, how do you then take in the concept of sovereignity recognition? For example the above scenario is valid for a person from the UK (me) as the UK has full diplomatic recognition of Kosovo, but Spain for example does not. So if I ran the query above but from the viewpoint of Spain then post 2008 it would respond with the land area of Serbia+Kosovo.

Best Regards,


Byb3 (talk)23:55, 24 July 2013

I have pondered on similar subject in the course of designing Summary II. Storing historical data can be done with subobjects. They can be organised to store pages' properties together with context: time when valid, viewpoint etc.

Another theoretically possible but impractical solution is completely rewriting Semantic MediaWiki to allow, in addition to existing statements of the = value form, something like page.propertyvalue, (was equal in 1913) value, (some people say equals) value, etc.

Alex Mashintalk06:43, 25 July 2013

What you're talking about at the end is, essentially, three-dimensional data: land area for country, for year, for viewpoint. SMW can only handle up to two-dimensional data per page, using the #subobject function. (Or you could use the Semantic Internal Objects extension, which does the same thing but with different syntax.) You could still store three-dimensional data, but you would need to use different pages for it: instead of just a page called "Kosovo", you would need pages like "Kosovo/2008" or "Kosovo/for Spain", or even "Kosovo/2008/for Spain". However, for your case you would presumably want the system to find the nearest year and that sort of thing, not just an exact year match; and I don't think there's any way to do that. So if you really wanted to get this working, you would have to create a page or subobject for every year and maybe even every viewpoint, even though it would involved a tremendous amount of redundancy.

Yaron Koren (talk)14:43, 25 July 2013
What you're talking about at the end is, essentially, three-dimensional data: land area for country, for year, for viewpoint. 
Not really. I mean that the metaproperties for context (time and viewpoint) should be included in the same subobject as the properties. This allows any number of dimensions.
you would presumably want the system to find the nearest year 
I can record intervals: '''Kosovo''' ... {{#subobject:__since = 2008|__until = 2015|__who thinks so = Spain|legal status = Independent state}}.
Alex Mashintalk15:48, 25 July 2013

Ah, yes, that's true. It would be somewhat awkward, but doable.

Yaron Koren (talk)19:05, 25 July 2013
First page
First page
Previous page
Previous page
Last page
Last page