[00:08:00] (PS4) Cicalese: first commit [extensions/SemanticDependency] - https://gerrit.wikimedia.org/r/168591 [00:30:34] (PS5) Cicalese: first commit [extensions/SemanticDependency] - https://gerrit.wikimedia.org/r/168591 [00:33:10] (CR) Mwjames: first commit (6 comments) [extensions/SemanticDependency] - https://gerrit.wikimedia.org/r/168591 (owner: Cicalese) [01:09:43] (CR) Mwjames: "Also no need for `*.class.php`, just use `.php`." [extensions/SemanticDependency] - https://gerrit.wikimedia.org/r/168591 (owner: Cicalese) [01:09:52] (PS6) Cicalese: first commit [extensions/SemanticDependency] - https://gerrit.wikimedia.org/r/168591 [01:28:42] (CR) Cicalese: "mwjames, thank you for your thorough review! Your input has made a significant improvement to the extension." [extensions/SemanticDependency] - https://gerrit.wikimedia.org/r/168591 (owner: Cicalese) [01:47:01] (CR) Mwjames: first commit (1 comment) [extensions/SemanticDependency] - https://gerrit.wikimedia.org/r/168591 (owner: Cicalese) [01:49:05] (CR) Mwjames: "> The reason for the .class in the filename is, of course, because the main file is already named SemanticDependency.php. Would it be pref" [extensions/SemanticDependency] - https://gerrit.wikimedia.org/r/168591 (owner: Cicalese) [02:12:05] [SemanticMediaWiki] mwjames pushed 1 new commit to sparql-queryengine: http://git.io/b9BNLg [02:12:05] SemanticMediaWiki/sparql-queryengine 7e4aa91 mwjames: Add PropertyConditionBuilder... [02:37:28] [SemanticMediaWiki] mwjames pushed 1 new commit to master: http://git.io/jxT3nQ [02:37:28] SemanticMediaWiki/master fa30c6a mwjames: Merge pull request #590 from SemanticMediaWiki/sparql-queryengine... [05:43:31] (CR) Siebrand: [C: -1] "i18n/L10n reviewed." (1 comment) [extensions/SemanticDependency] - https://gerrit.wikimedia.org/r/168591 (owner: Cicalese) [08:36:30] * dreamer still trying to wrap his head around not being able to generate the 'has values' in a property. anyone with experience on this? [10:36:25] dreamer, have you described this question somewhere in more detail? [10:48:51] further up [10:49:11] I believe last thursday. let me come back to you after lunch [10:49:30] (basically I want to generate the 'has values' list using an {{#ask:}}) [10:51:20] ok [10:51:37] sounds like an information model challeng [11:23:14] ok, yeah. so [11:24:01] we have a bunch of servers described on our internal wiki. and we have a number of virtual machines being hosted by those servers. so in the template for the VMs I want to be able to select those hosts [11:24:23] being able to generate this list so we can select them from the dropdown would be nice [11:25:06] otherwise we'll have to maintain this list manually, which isn't horrible since we don't change these servers all that often, but it would be a nice feature if this was generated [11:29:07] (PS7) Cicalese: first commit [extensions/SemanticDependency] - https://gerrit.wikimedia.org/r/168591 [11:29:54] (CR) Cicalese: "Thank you, Siebrand!" [extensions/SemanticDependency] - https://gerrit.wikimedia.org/r/168591 (owner: Cicalese) [11:30:31] (CR) Cicalese: [C: 2 V: 2] first commit [extensions/SemanticDependency] - https://gerrit.wikimedia.org/r/168591 (owner: Cicalese) [12:40:15] [SemanticResultFormats] kghbln created 69 from master (+0 new commits): http://git.io/YJiHzw [12:49:56] [SemanticResultFormats] kghbln pushed 1 new commit to 69: http://git.io/d2sIDA [12:49:56] SemanticResultFormats/69 ecab34f Karsten Hoffmeyer: Update en.json... [12:57:01] [SemanticResultFormats] kghbln pushed 1 new commit to 69: http://git.io/w2ev0Q [12:57:01] SemanticResultFormats/69 933d492 Karsten Hoffmeyer: Update qqq.json... [12:59:14] [SemanticResultFormats] kghbln opened pull request #70: Add missing system message (master...69) http://git.io/ER0k8g [13:08:11] hey dreamer, so I gather you've already chosen to create separate pages per VM. [13:08:48] Presumably you also already have separate pages for each individual virtual host. [13:10:31] If these virtual hosts are distinguishable by a unique trait (e.g. belong to category "virtual host") then it's trivial to have Semantic Forms provide a dropdown on the form for a VM, and you could easily model a relation [13:10:33] Saruman: yes I do. hence I want to ask for all pages in that category (and some other fancy shmancy) [13:10:47] within SF? [13:11:12] {{#ask: [[Category:Servers]] [[ServerType::Host]]|format=template|template=VMHostList|link=none}} [13:11:30] and the list does get generated, however the dropdown doesn't work [13:11:47] I just get a text-field [13:12:07] so, this template it uses for the ask is: * [[Allows value::{{#titleparts: {{{1}}} | |2}}]] [13:12:08] First of all, are you sure you want to model VMs by having a ServerType property? [13:12:24] not the VMs, the servers [13:12:31] sorry, meant that [13:12:36] because we have host-servers, and we have servers running a service [13:12:44] First of all, are you sure you want to model servers by having a ServerType property? [13:12:51] yes [13:13:09] Since servers can do more than a single thing, it seems to make more sence to have a category for each type of service that the server provides. [13:13:09] the naming is maybe a bit confusing, but in our setup it makes sense [13:13:14] ok if you say so [13:13:19] no, in our case the servers do one thing [13:13:39] either they host VMs or they run their own service (fileserver, backups, etc.) [13:13:59] this is just to make this distinction, so I can ask for only the servers that are host for VMs [13:14:09] heh... well my dayjob interferes with my thinking here (i'm infrastructure architect) [13:14:16] I'll try to step over it though [13:14:40] so, what is your dropdown need? [13:14:43] is it in SF? [13:14:47] yes [13:15:17] so when you make a VM-page you can select one of the available hosts [13:17:09] Well I have dropdowns on forms that look a bit like this: [13:17:28] {{{field|sector|default=Infrastructure Sector Undefined|autocomplete on category=Infrastructure Sector|mandatory}}} [13:17:40] They're category based, but that shouldn'tmatter much [13:17:51] lemme see if I have something with a tighter fit [13:18:21] hmm, so in this case you don't have any 'Allows value::' entries, but just request all pages in the category? [13:19:47] yes [13:19:55] Another exampel reads: [13:19:56] {{{field|sector|mandatory|size=25|autocomplete on property=Belongs to infrastructure sector}}} [13:20:41] That one has Allows value:: entries on the property page [13:21:32] but that only puts a value on a page, not a pagename [13:21:47] hmm [13:22:06] yeah I still don't get why I can't generate an Allows value:: list on a property-page [13:23:08] huh? [13:23:16] how could you generate such a list? Makes no semantic sense [13:23:31] like I explained earlier [13:23:31] values are allowed or not [13:24:37] I can't wrap my head around that. Allows value shouldn't be generated. [13:24:44] why not? [13:25:00] ok ok, I get why it makes sense to keep them 'static' [13:25:05] because it's meant to limit choice. [13:25:21] you're working it the opposite way: as some sort of list of existing choices [13:27:26] [SemanticResultFormats] JeroenDeDauw deleted 69 at 933d492: http://git.io/FchnVQ [13:28:06] Saruman: hmmmmmmok, but I don't really see how I could use your examples to do this [13:28:21] welp... I can't see an easy solution to your question within the information model you've chosen to implement [13:28:44] I just want a dropdown based on the pages I have in a category with a property-value [13:30:44] semantically I strongly feel that the task that a server is assigned to puts it in a category (semantically: a class of objects) [13:31:17] well this doesn't work: {{{field|Host|default=proxmox-node1|autocomplete on category=Servers|mandatory}}} [13:31:20] if one wouldn't want to use category, the 2nd best thing would be to create pages out of the tasks, and relate servers to tasks with a Executes task:: relation [13:31:31] your model goes to the third option [13:31:44] I just get a text-field with 'proxmox-node1' filled in [13:32:00] Saruman: even when I disregard the property, it still doesn't work [13:32:32] and I have no idea what you are talking about just now [13:32:42] have you typed your field? Sounds like SF is seeing it as a generic text field [13:33:18] well ther you have it: SMW is a semantic modelling tool [13:33:38] oh, I still had the semantic query in there, lets remove that [13:33:45] This is a property of type [[Has type::Page]]. [13:33:45] if you don't know semantics, it becomes a quirky programming environment [13:34:05] Saruman: I've never heard of 'Executes task::' [13:34:17] that'd be a relation, a property of type Page [13:34:31]