Extension talk:Semantic Internal Objects

Property type for the 'first argument'?
The first argument, "a property pointing from the object, to the page", is a property like any other in the wiki. What property type should it be? By default it's page, which means it's values are links to non-existent pages. Should it be changed to string? Does the setting have any effect? It's a bit confusing, so perhaps some recommendation should be made on the page. Cheers, --Dan Bolser 14:06, 14 January 2012 (UTC)
 * Could we even consider a special type for the property? i.e. by default it could be a property of type SIO or something? --Dan Bolser 14:07, 14 January 2012 (UTC)


 * It should just be a property of type "page". The documentation could probably be clearer about that. Yaron Koren 05:30, 15 January 2012 (UTC)

Semantic Mediawiki 1.7
Hello,

I saw that the 1.7 version of Semantic Mediawiki includes SIO natively through the #subobject perser function. Does it have all the same functionalities and query syntax ? Regarding bugs, which version of SIO got into SMW ?


 * Actually, what's included isn't SIO, but similar functionality. That's a good question, though - I just added a section to the documentation that tries to explain this; hopefully it makes sense. Yaron Koren 13:54, 20 January 2012 (UTC)

set_internal_recurring_event, unit=year
I want to do

but all instances are on the same date. The same behaviour for unit=month, but unit=day and unit=week behave as expected. What is wrong? I use Semantic Internal Objects (Versie 0.6.8), Semantic MediaWiki (Versie 1.7.1) and MediaWiki (Versie 1.18.1) --Egel (talk) 22:40, 23 March 2012 (UTC)


 * That's pretty bad - this turned out to be a bug in Semantic MediaWiki itself, since January. I just fixed it in SVN. If you don't have SVN, you can duplicate the fix yourself, here. Yaron Koren (talk) 15:02, 25 March 2012 (UTC)


 * Hello, I still have problems setting recurring events with Internal Objects (Versie 0.6.8), Semantic MediaWiki (Versie 1.7.1). What I see is that when I run the query the event as not repeated, while if I just use #set_recurring_event everything works normally. This happens with the same example reported in the wiki page. Does anybody have a clue? I am quite newbie so I could be missing something obvious. Paolo


 * Is this happening on a public wiki? If not, could you try to reproduce it on scratchpad.referata.com? Yaron Koren (talk) 02:21, 22 May 2012 (UTC)


 * Hi Yaron. Thank you for the reply. The wiki is not public yet. I tried to reproduce the problem here.
 * Ok, I fixed the problem. There was a php error when running the database update. I saw it enabling error_reporting( E_ALL ); ini_set( 'display_errors', 1 ); in the LocalSettings.php file. However I have another issue: when I ask for a property based on its value, the query returns all the pages containing that property, watever value is specified. I saw that on on scratchpad.referata.com it is the same. Is this related with the InternalOnject extension? (I fixed this by defining the property of type string and adding '~' to the query) Paolo

Using set_internal_recurring_events for date ranges
Dear Yaron. There are at least two different types of date ranges that are standard fare in historical research:


 * 1. (c.) A – (c.) B: meaning that something, e.g. a war or a person’s floruit, lasted from (circa) start date A to (circa) start date B
 * 2. A x B: meaning that something took place sometime between A (terminus post quem) and B (terminus ante quem).

I presume that SIO storage and querying can be used for a continuum like #1, although it's not an actual continuum in semantic terms and approximate dates can be tricky, and probably #2, as long as it’s clear that searching for matches in a given date range can only produce tentative results.

The main problem I had is that the span of such a range can be well over a century. If I understand things correctly, SIO would then store a value for every day that falls within the range until a maximum is reached, at the risk of overloading the database. That doesn’t seem to me like a very efficient way of handling date ranges.

Do you have suggestions or know of any alternative approaches? Cavila MW 1.17, MySQL 5.5.16, Php 5.3.8 22:55, 21 May 2012 (UTC)


 * Hi - yes, indeed that's not efficient; I wouldn't use recurring events for historical stuff. Can't you just store a start date and end date (pretending that these are exact dates, and not just "circa"), and then query on those? Yaron Koren (talk) 02:23, 22 May 2012 (UTC)


 * Well, the main objection to that approach would be that a query could be skipping over relevant data. For instance, if you need to query on organisations that were active between 1920 and 1950, but one organisation was founded in 1910 and discontinued in 1960, it will not be included in your results. I know you can keep overload to a minimum by changing the unit in SIO from "day" to "year" or even 20 years (unit=year, period=20). Since these are ad hoc solutions that could work in certain situations but not in others, maybe the safest solutions is to restrict the possible date ranges that are used in queries in advance and use that as the basis for a SIO storage plan. So if you decide beforehand that for certain data, queried ranges should not be below 20 years, it would be enough to create intervals of 20 years (in the example above, you would get 1910, 1930, 1950 and 1960). It may not be an ideal solution and won’t work for calendar and eventline outputs, but it should be feasible. Cavila MW 1.17, MySQL 5.5.16, Php 5.3.8 13:51, 22 May 2012 (UTC)


 * I still think you could do it with just queries. In your case, I'm not sure whether you mean organizations that were active in any year between 1920 and 1950, or all the years. If it's the first one, you could query on (start date <= 1950 AND end date >= 1920), while if it's the second one, you could query on (start date <= 1920 AND end date >= 1950). Yaron Koren (talk) 14:23, 22 May 2012 (UTC)


 * Thanks, I hadn't thought of using comparators like that (obvious as it may seem to you)! Yes, I did mean any year and it works as expected. The only mystery now remaining is that values of date-type properties get subtracted, e.g. "1500" is stored as "1499", but I guess that's for a different forum. Cavila MW 1.17, MySQL 5.5.16, Php 5.3.8 23:45, 22 May 2012 (UTC)
 * FYI: Filed as bug 37038 Cavila MW 1.17, MySQL 5.5.23, Php 5.3.10, SMW 1.7.1 07:17, 23 May 2012 (UTC)

Recipe example seems flawed
The documentation states:
 * Internal objects, once stored, can be queried as if they were wiki pages. So the following query would show a table of all the recipes that contain more than 1/2 a cup of flour, and the number of cups they contain.

Perhaps I'm missing something but the query doesn't actually show a table of recipes as stated. Rather, it displays a table of recipe components without links back to the page which defines them. As such, the recipe example seems fundamentally flawed. A query for recipes containing 0.5/cup of flour doesn't return the recipes which require 0.5/cup of flour, but rather simply all recipe line-items for 0.5/cup of flour. It provides no means to connect these line-items to the recipe, does it? Is mainlabel=- is omitted, somewhat ugly links are added to the subobjects themselves (and thus the page containing them), but as far as I can see there is no way to output a link to the page which defines that object.

This could be worked around by, for example, adding the property Is part of recipe= . Is this necessary for the recipe example to function as intended, or am I missing something? Thanks :) Andru


 * Yes, you're missing something - the first parameter to #set_internal - "Part of recipe", in the case of the example - is set to point to the page that it's on; so it's implicitly calling "Part of recipe= ". Yaron Koren (talk) 02:21, 8 June 2012 (UTC)


 * Superb. Not sure how I missed that. Thanks for the help :) - Andru

Question concerning special character sequences
Hi Yaron,

thanks for your outstanding work. One Question: On http://semantic-mediawiki.org/wiki/Help:Type_String they say:
 * If you want to store special character sequences like "::", you need to store them using the parser function #set, instead of with the more standard "property::value" notation. 

Question: Does SIO act likewise, is it possible to store special character sequences?

--163.244.24.4 13:05, 26 June 2012 (UTC)


 * Hi, thanks. I think so, yes. Yaron Koren (talk) 14:40, 26 June 2012 (UTC)

SIO Inserted Repeatedly (Object Duplication)
I appear to be having this problem, referenced in archived talk pages:
 * 2011
 * 2009 to 2010

It appears to be related to my use of the Text data type. SIO is set using a template: ! style="vertical-align:top;" |
 * - class="zebra-row"
 * style="vertical-align:top;" |
 * From page: Sidenote: I think this might be excessive, and there may be a better way to point to the page the SIO was created on
 * Has date: Need to be able to query SIOs and sort by date...have to duplicate date here
 * Has related subject: List of wiki pages that this SIO is related to. The contents of this SIO are auto-populated on these pages using Extension:Header Footer.
 * Has significance: This is the property I'm seeing duplicated. It is currently set as a Text property.

On each page the the SIO is retrieved using the following query:

My stack is:
 * Windows NT 6.1 build 7601 with Microsoft-IIS/7.5
 * MW: 1.17.0
 * PHP: 5.2.14 (cgi-fcgi)
 * MySQL 5.5.25-log
 * SMW 1.7.1
 * Semantic Compound Queries 0.3.2
 * Semantic Forms 2.4.2
 * SIO 0.6.8
 * WhoIsWatching 0.10
 * CharInsert
 * Cite
 * DynamicPageList
 * External Data
 * LabeledSectionTransclusion
 * ParserFunctions
 * Pipe Escape
 * HeaderFooter
 * StubManager
 * Validator
 * Vector extension


 * That's unfortunate. Yes, "From page" is unnecessary - that first value you passed in, "Subject significant to mission", is already the name of a property that points back to that page. Maybe simplifying that will fix the problem? Who knows. Yaron Koren (talk) 00:24, 6 July 2012 (UTC)

--188.195.59.3 18:10, 6 July 2012 (UTC) Same duplication with my installation. (Downloaded latest versions (one week ago) and mediawiki 1.18 Every page reload of very simple SIO duplicates the TEXT properties Nothing complicated At 'save' it's ok again. But: Thanks for the great work! Norbert

queries on values in multiple use templates
I have tasks that are being tracked on a client form.

My client wants a list of tasks that are assigned to herself. Of course the task form is an embedded template and can be used multiple times. This creates multiple task values. Some of those values are my clients and some are her employees.

When I use the table format query all the items display in the table center justified and you can't clearly see what Task Due date lines up with Task. Plus the query doesn't filter out the task assignment. It shows all the task not just Task Assignment property.

Is there a solution here to query on multiple values? Thanks again for any help you can offer. --Amblerllc (talk) 23:53, 27 October 2012 (UTC)


 * You should switch that multiple-instance template to use Semantic Internal Objects to store its data. Yaron Koren (talk) 22:00, 28 October 2012 (UTC)
 * OH. I was afraid you might say that. I hope I can figure that out in the next 8 hours! :) Thank you so much! --Amblerllc (talk) 15:33, 29 October 2012 (UTC)
 * Am I understanding this... if I remove the multiple templates statement then I am generating multiple pages through a querylink and the pages are the "object"? such as carrotcake in the example? Is there a good display for the use of semantic internal objects? --Amblerllc (talk) 22:30, 29 October 2012 (UTC)


 * No, you should keep it as a multiple-instance template - you just need to modify the template itself. Here is an example of a template that uses SIO. Yaron Koren (talk) 22:52, 29 October 2012 (UTC)
 * I thought I would move this article here. This link was very helpful. I have it working. Just in time for the install tomorrow. Thank you again. Also, I ran into the problem where I ran runJobs.php and my {{#ask calls disappeared. As soon as I saved the pages it viewed just fine.

--66.41.96.6 08:55, 30 October 2012 (UTC)