From: Rolf L. <rol...@ri...> - 2008-05-30 08:51:04
|
The documentation says that parameters can NOT be used in queries, not in "any case. See this page http://semantic-mediawiki.org/wiki/Help:Semantic_search#Using_templates_and_variables The text doesn't seem to reveal the whole truth, though. The text says: >> == Using templates and variables == >> >> Within a query, arbitrary templates and variables can be used. >> This can be used to create a standard query that displays all >> future events (where "future" gets its meaning from the current date): <snip> It goes on to say: >> Many other uses are possible, especially when using queries inline. >> However, it is in *no case possible* to use template parameters (the >> things in {{{ }}}) within a query. *Sorry*. But, parameters /can/ be used in a query, although not directly. I suggest assigning parameter values to temporary variables, and then use the variables in the query instead, like so: // 1. Assign {{{param values}}} to temp variables : {{#vardefine: tmp_pageclass | {{{1|}}} }} {{#vardefine: tmp_property | {{{2|}}} }} // 2. In this way the variables (params) actually /can/ be used in the query: {{#ask: [[Category:{{#var:tmp_pageclass}}]] | [[{{#var:tmp_property}}::+]] [[{{#var:tmp_property}}::*]] }} Tested, and it works. Perhaps a hint to use "param-variables" like this should be added to the documentation as well. Regards, // Rolf Lampa |
From: Sergey C. <sem...@an...> - 2008-05-30 17:49:45
|
Actually, this problem went away once ASK was rewritten as parser function and you can use it all as with any other parser function. Basically, that was the main reason for parser function development. Sergey On Fri, May 30, 2008 at 4:50 AM, Rolf Lampa <rol...@ri...> wrote: > The documentation says that parameters can NOT be used in queries, > not in "any case. See this page > > http://semantic-mediawiki.org/wiki/Help:Semantic_search#Using_templates_and_variables > > The text doesn't seem to reveal the whole truth, though. The text says: > > >> == Using templates and variables == > >> > >> Within a query, arbitrary templates and variables can be used. > >> This can be used to create a standard query that displays all > >> future events (where "future" gets its meaning from the current date): > > <snip> It goes on to say: > > >> Many other uses are possible, especially when using queries inline. > >> However, it is in *no case possible* to use template parameters (the > >> things in {{{ }}}) within a query. *Sorry*. > > But, parameters /can/ be used in a query, although not directly. I suggest > assigning parameter values to temporary variables, and then use the > variables in the query instead, like so: > > // 1. Assign {{{param values}}} to temp variables : > > {{#vardefine: tmp_pageclass | {{{1|}}} }} > {{#vardefine: tmp_property | {{{2|}}} }} > > // 2. In this way the variables (params) actually /can/ be used in the > query: > > {{#ask: [[Category:{{#var:tmp_pageclass}}]] > | [[{{#var:tmp_property}}::+]] [[{{#var:tmp_property}}::*]] > }} > > Tested, and it works. Perhaps a hint to use "param-variables" like this > should be added to the documentation as well. > > Regards, > > // Rolf Lampa > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > -- Sergey Chernyshev http://www.sergeychernyshev.com/ |
From: Sergey C. <sem...@an...> - 2008-05-30 17:53:54
|
I updated documentation removing template parameter restriction. On Fri, May 30, 2008 at 1:49 PM, Sergey Chernyshev < sem...@an...> wrote: > Actually, this problem went away once ASK was rewritten as parser function > and you can use it all as with any other parser function. Basically, that > was the main reason for parser function development. > > Sergey > > > > On Fri, May 30, 2008 at 4:50 AM, Rolf Lampa <rol...@ri...> wrote: > >> The documentation says that parameters can NOT be used in queries, >> not in "any case. See this page >> >> http://semantic-mediawiki.org/wiki/Help:Semantic_search#Using_templates_and_variables >> >> The text doesn't seem to reveal the whole truth, though. The text says: >> >> >> == Using templates and variables == >> >> >> >> Within a query, arbitrary templates and variables can be used. >> >> This can be used to create a standard query that displays all >> >> future events (where "future" gets its meaning from the current date): >> >> <snip> It goes on to say: >> >> >> Many other uses are possible, especially when using queries inline. >> >> However, it is in *no case possible* to use template parameters (the >> >> things in {{{ }}}) within a query. *Sorry*. >> >> But, parameters /can/ be used in a query, although not directly. I suggest >> assigning parameter values to temporary variables, and then use the >> variables in the query instead, like so: >> >> // 1. Assign {{{param values}}} to temp variables : >> >> {{#vardefine: tmp_pageclass | {{{1|}}} }} >> {{#vardefine: tmp_property | {{{2|}}} }} >> >> // 2. In this way the variables (params) actually /can/ be used in the >> query: >> >> {{#ask: [[Category:{{#var:tmp_pageclass}}]] >> | [[{{#var:tmp_property}}::+]] [[{{#var:tmp_property}}::*]] >> }} >> >> Tested, and it works. Perhaps a hint to use "param-variables" like this >> should be added to the documentation as well. >> >> Regards, >> >> // Rolf Lampa >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Semediawiki-user mailing list >> Sem...@li... >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >> > > > > -- > Sergey Chernyshev > http://www.sergeychernyshev.com/ -- Sergey Chernyshev http://www.sergeychernyshev.com/ |
From: Robert M. <mra...@gm...> - 2008-05-30 18:18:10
|
So -is- there a way to pass an additional bit of data in a query? Sifting through n-ary data could be a lot easier if you could just pass even one value along with each template call in an #ask: On Fri, May 30, 2008 at 10:49 AM, Sergey Chernyshev <sem...@an...> wrote: > Actually, this problem went away once ASK was rewritten as parser function > and you can use it all as with any other parser function. Basically, that > was the main reason for parser function development. > > Sergey > > > On Fri, May 30, 2008 at 4:50 AM, Rolf Lampa <rol...@ri...> wrote: >> >> The documentation says that parameters can NOT be used in queries, >> not in "any case. See this page >> >> http://semantic-mediawiki.org/wiki/Help:Semantic_search#Using_templates_and_variables >> >> The text doesn't seem to reveal the whole truth, though. The text says: >> >> >> == Using templates and variables == >> >> >> >> Within a query, arbitrary templates and variables can be used. >> >> This can be used to create a standard query that displays all >> >> future events (where "future" gets its meaning from the current date): >> >> <snip> It goes on to say: >> >> >> Many other uses are possible, especially when using queries inline. >> >> However, it is in *no case possible* to use template parameters (the >> >> things in {{{ }}}) within a query. *Sorry*. >> >> But, parameters /can/ be used in a query, although not directly. I suggest >> assigning parameter values to temporary variables, and then use the >> variables in the query instead, like so: >> >> // 1. Assign {{{param values}}} to temp variables : >> >> {{#vardefine: tmp_pageclass | {{{1|}}} }} >> {{#vardefine: tmp_property | {{{2|}}} }} >> >> // 2. In this way the variables (params) actually /can/ be used in the >> query: >> >> {{#ask: [[Category:{{#var:tmp_pageclass}}]] >> | [[{{#var:tmp_property}}::+]] [[{{#var:tmp_property}}::*]] >> }} >> >> Tested, and it works. Perhaps a hint to use "param-variables" like this >> should be added to the documentation as well. >> >> Regards, >> >> // Rolf Lampa >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Semediawiki-user mailing list >> Sem...@li... >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > -- > Sergey Chernyshev > http://www.sergeychernyshev.com/ > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > -- Roses are red,Violets are blue,I'm schizophrenic,and so am I. |
From: Sergey C. <sem...@an...> - 2008-05-30 18:33:07
|
Hmm. I think I'll need to see an example of the problem you're trying to solve to understand your question - it seems that there might be several issues - some connected with passing parameters and some connected with multi-value properties (they are not really n-ary relations). Sergey On Fri, May 30, 2008 at 2:18 PM, Robert Murphy <mra...@gm...> wrote: > So -is- there a way to pass an additional bit of data in a query? > Sifting through n-ary data could be a lot easier if you could just > pass even one value along with each template call in an #ask: > > > On Fri, May 30, 2008 at 10:49 AM, Sergey Chernyshev > <sem...@an...> wrote: > > Actually, this problem went away once ASK was rewritten as parser > function > > and you can use it all as with any other parser function. Basically, that > > was the main reason for parser function development. > > > > Sergey > > > > > > On Fri, May 30, 2008 at 4:50 AM, Rolf Lampa <rol...@ri...> > wrote: > >> > >> The documentation says that parameters can NOT be used in queries, > >> not in "any case. See this page > >> > >> > http://semantic-mediawiki.org/wiki/Help:Semantic_search#Using_templates_and_variables > >> > >> The text doesn't seem to reveal the whole truth, though. The text says: > >> > >> >> == Using templates and variables == > >> >> > >> >> Within a query, arbitrary templates and variables can be used. > >> >> This can be used to create a standard query that displays all > >> >> future events (where "future" gets its meaning from the current > date): > >> > >> <snip> It goes on to say: > >> > >> >> Many other uses are possible, especially when using queries inline. > >> >> However, it is in *no case possible* to use template parameters (the > >> >> things in {{{ }}}) within a query. *Sorry*. > >> > >> But, parameters /can/ be used in a query, although not directly. I > suggest > >> assigning parameter values to temporary variables, and then use the > >> variables in the query instead, like so: > >> > >> // 1. Assign {{{param values}}} to temp variables : > >> > >> {{#vardefine: tmp_pageclass | {{{1|}}} }} > >> {{#vardefine: tmp_property | {{{2|}}} }} > >> > >> // 2. In this way the variables (params) actually /can/ be used in the > >> query: > >> > >> {{#ask: [[Category:{{#var:tmp_pageclass}}]] > >> | [[{{#var:tmp_property}}::+]] [[{{#var:tmp_property}}::*]] > >> }} > >> > >> Tested, and it works. Perhaps a hint to use "param-variables" like this > >> should be added to the documentation as well. > >> > >> Regards, > >> > >> // Rolf Lampa > >> > >> > ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> Semediawiki-user mailing list > >> Sem...@li... > >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > > > > -- > > Sergey Chernyshev > > http://www.sergeychernyshev.com/ > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Semediawiki-user mailing list > > Sem...@li... > > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > > > > -- > Roses are red,Violets are blue,I'm schizophrenic,and so am I. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > -- Sergey Chernyshev http://www.sergeychernyshev.com/ |
From: Robert M. <mra...@gm...> - 2008-05-30 19:20:43
|
OK. I can't think of an example other than my own stuff, so here goes: Imagine a gazillion sentences made up of Greek words. Each word has a dictionary form and a particular way it's used in each instances. Each sentence has a page, full of [[Uses Parsed Greek::Greek:Word; Greek:Parsing]] (each word and each parsing have an individual page in the Greek namespace). If I want to query against my data for all the ways Greek:One is used in each sentence, I {{#ask: [[Category:Greek sentence]] [[Uses Parsed Greek::Greek:One; ?]] |?Uses Parsed Greek }} This, unfortunately, returns a huge swath of other data, namely, how each and every other word is used (it is, however, limited to sentences that use Greek:One). There's seems to be no easy way to limit what is returned. So, I made a monster-bloated template that parses over the n-ary data and finds the Greek:Parsing for Greek:One. This template is the template= from an #ask query. However, I didn't want to hard-code in "Greek:One", so I did the only variable I could think of {{BASEPAGENAME}}. Now, this template can only be called as part of an #ask from the Greek:Word page to find out how that word is used. If #ask when format=template could just pass an extra variable, then my elaborate template could look for usages of that word and not have to be bound to use {{MAGIC_WORDS}}. -Robert http://reformedword.org/Greek:One - example page http://reformedword.org/Template:Greek_Chopper - my twisted template On Fri, May 30, 2008 at 11:33 AM, Sergey Chernyshev <sem...@an...> wrote: > Hmm. I think I'll need to see an example of the problem you're trying to > solve to understand your question - it seems that there might be several > issues - some connected with passing parameters and some connected with > multi-value properties (they are not really n-ary relations). > > Sergey > > > On Fri, May 30, 2008 at 2:18 PM, Robert Murphy <mra...@gm...> > wrote: >> >> So -is- there a way to pass an additional bit of data in a query? >> Sifting through n-ary data could be a lot easier if you could just >> pass even one value along with each template call in an #ask: >> >> >> On Fri, May 30, 2008 at 10:49 AM, Sergey Chernyshev >> <sem...@an...> wrote: >> > Actually, this problem went away once ASK was rewritten as parser >> > function >> > and you can use it all as with any other parser function. Basically, >> > that >> > was the main reason for parser function development. >> > >> > Sergey >> > >> > >> > On Fri, May 30, 2008 at 4:50 AM, Rolf Lampa <rol...@ri...> >> > wrote: >> >> >> >> The documentation says that parameters can NOT be used in queries, >> >> not in "any case. See this page >> >> >> >> >> >> http://semantic-mediawiki.org/wiki/Help:Semantic_search#Using_templates_and_variables >> >> >> >> The text doesn't seem to reveal the whole truth, though. The text says: >> >> >> >> >> == Using templates and variables == >> >> >> >> >> >> Within a query, arbitrary templates and variables can be used. >> >> >> This can be used to create a standard query that displays all >> >> >> future events (where "future" gets its meaning from the current >> >> date): >> >> >> >> <snip> It goes on to say: >> >> >> >> >> Many other uses are possible, especially when using queries inline. >> >> >> However, it is in *no case possible* to use template parameters >> >> (the >> >> >> things in {{{ }}}) within a query. *Sorry*. >> >> >> >> But, parameters /can/ be used in a query, although not directly. I >> >> suggest >> >> assigning parameter values to temporary variables, and then use the >> >> variables in the query instead, like so: >> >> >> >> // 1. Assign {{{param values}}} to temp variables : >> >> >> >> {{#vardefine: tmp_pageclass | {{{1|}}} }} >> >> {{#vardefine: tmp_property | {{{2|}}} }} >> >> >> >> // 2. In this way the variables (params) actually /can/ be used in the >> >> query: >> >> >> >> {{#ask: [[Category:{{#var:tmp_pageclass}}]] >> >> | [[{{#var:tmp_property}}::+]] [[{{#var:tmp_property}}::*]] >> >> }} >> >> >> >> Tested, and it works. Perhaps a hint to use "param-variables" like this >> >> should be added to the documentation as well. >> >> >> >> Regards, >> >> >> >> // Rolf Lampa >> >> >> >> >> >> ------------------------------------------------------------------------- >> >> This SF.net email is sponsored by: Microsoft >> >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> _______________________________________________ >> >> Semediawiki-user mailing list >> >> Sem...@li... >> >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >> > >> > >> > >> > -- >> > Sergey Chernyshev >> > http://www.sergeychernyshev.com/ >> > >> > ------------------------------------------------------------------------- >> > This SF.net email is sponsored by: Microsoft >> > Defy all challenges. Microsoft(R) Visual Studio 2008. >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> > _______________________________________________ >> > Semediawiki-user mailing list >> > Sem...@li... >> > https://lists.sourceforge.net/lists/listinfo/semediawiki-user >> > >> > >> >> >> >> -- >> Roses are red,Violets are blue,I'm schizophrenic,and so am I. >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Semediawiki-user mailing list >> Sem...@li... >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > -- > Sergey Chernyshev > http://www.sergeychernyshev.com/ -- Roses are red,Violets are blue,I'm schizophrenic,and so am I. |
From: Sergey C. <sem...@an...> - 2008-06-02 18:45:46
|
OK, so you're talking about formatting templates that transform the results of the query, not the templates that just have queries within them. I didn't work that much with formatting templates, but in general, as I understand, you get results as numbered parameters - then in there, you can use them to trigger logic. If you need MW variables to be run in context of specific page rather then default (which is meaningless since template is called by ASK parser function and not just being inserted into the page), then you might want to write your own parser functions or reuse existing ones that match MW variables - here's the example: http://www.mediawiki.org/wiki/Extension:PathFunctions Hope this helps. Sergey On Fri, May 30, 2008 at 3:20 PM, Robert Murphy <mra...@gm...> wrote: > OK. I can't think of an example other than my own stuff, so here goes: > > Imagine a gazillion sentences made up of Greek words. Each word has a > dictionary form and a particular way it's used in each instances. > Each sentence has a page, full of [[Uses Parsed Greek::Greek:Word; > Greek:Parsing]] (each word and each parsing have an individual page in > the Greek namespace). If I want to query against my data for all the > ways Greek:One is used in each sentence, I > > {{#ask: [[Category:Greek sentence]] [[Uses Parsed Greek::Greek:One; ?]] > |?Uses Parsed Greek > }} > > This, unfortunately, returns a huge swath of other data, namely, how > each and every other word is used (it is, however, limited to > sentences that use Greek:One). There's seems to be no easy way to > limit what is returned. > So, I made a monster-bloated template that parses over the n-ary data > and finds the Greek:Parsing for Greek:One. This template is the > template= from an #ask query. However, I didn't want to hard-code in > "Greek:One", so I did the only variable I could think of > {{BASEPAGENAME}}. Now, this template can only be called as part of an > #ask from the Greek:Word page to find out how that word is used. > If #ask when format=template could just pass an extra variable, then > my elaborate template could look for usages of that word and not have > to be bound to use {{MAGIC_WORDS}}. > > -Robert > http://reformedword.org/Greek:One - example page > http://reformedword.org/Template:Greek_Chopper - my twisted template > > On Fri, May 30, 2008 at 11:33 AM, Sergey Chernyshev > <sem...@an...> wrote: > > Hmm. I think I'll need to see an example of the problem you're trying to > > solve to understand your question - it seems that there might be several > > issues - some connected with passing parameters and some connected with > > multi-value properties (they are not really n-ary relations). > > > > Sergey > > > > > > On Fri, May 30, 2008 at 2:18 PM, Robert Murphy <mra...@gm... > > > > wrote: > >> > >> So -is- there a way to pass an additional bit of data in a query? > >> Sifting through n-ary data could be a lot easier if you could just > >> pass even one value along with each template call in an #ask: > >> > >> > >> On Fri, May 30, 2008 at 10:49 AM, Sergey Chernyshev > >> <sem...@an...> wrote: > >> > Actually, this problem went away once ASK was rewritten as parser > >> > function > >> > and you can use it all as with any other parser function. Basically, > >> > that > >> > was the main reason for parser function development. > >> > > >> > Sergey > >> > > >> > > >> > On Fri, May 30, 2008 at 4:50 AM, Rolf Lampa <rol...@ri...> > >> > wrote: > >> >> > >> >> The documentation says that parameters can NOT be used in queries, > >> >> not in "any case. See this page > >> >> > >> >> > >> >> > http://semantic-mediawiki.org/wiki/Help:Semantic_search#Using_templates_and_variables > >> >> > >> >> The text doesn't seem to reveal the whole truth, though. The text > says: > >> >> > >> >> >> == Using templates and variables == > >> >> >> > >> >> >> Within a query, arbitrary templates and variables can be used. > >> >> >> This can be used to create a standard query that displays all > >> >> >> future events (where "future" gets its meaning from the current > >> >> date): > >> >> > >> >> <snip> It goes on to say: > >> >> > >> >> >> Many other uses are possible, especially when using queries > inline. > >> >> >> However, it is in *no case possible* to use template parameters > >> >> (the > >> >> >> things in {{{ }}}) within a query. *Sorry*. > >> >> > >> >> But, parameters /can/ be used in a query, although not directly. I > >> >> suggest > >> >> assigning parameter values to temporary variables, and then use the > >> >> variables in the query instead, like so: > >> >> > >> >> // 1. Assign {{{param values}}} to temp variables : > >> >> > >> >> {{#vardefine: tmp_pageclass | {{{1|}}} }} > >> >> {{#vardefine: tmp_property | {{{2|}}} }} > >> >> > >> >> // 2. In this way the variables (params) actually /can/ be used in > the > >> >> query: > >> >> > >> >> {{#ask: [[Category:{{#var:tmp_pageclass}}]] > >> >> | [[{{#var:tmp_property}}::+]] [[{{#var:tmp_property}}::*]] > >> >> }} > >> >> > >> >> Tested, and it works. Perhaps a hint to use "param-variables" like > this > >> >> should be added to the documentation as well. > >> >> > >> >> Regards, > >> >> > >> >> // Rolf Lampa > >> >> > >> >> > >> >> > ------------------------------------------------------------------------- > >> >> This SF.net email is sponsored by: Microsoft > >> >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> >> _______________________________________________ > >> >> Semediawiki-user mailing list > >> >> Sem...@li... > >> >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user > >> > > >> > > >> > > >> > -- > >> > Sergey Chernyshev > >> > http://www.sergeychernyshev.com/ > >> > > >> > > ------------------------------------------------------------------------- > >> > This SF.net email is sponsored by: Microsoft > >> > Defy all challenges. Microsoft(R) Visual Studio 2008. > >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> > _______________________________________________ > >> > Semediawiki-user mailing list > >> > Sem...@li... > >> > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > >> > > >> > > >> > >> > >> > >> -- > >> Roses are red,Violets are blue,I'm schizophrenic,and so am I. > >> > >> > ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2008. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> Semediawiki-user mailing list > >> Sem...@li... > >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > > > > -- > > Sergey Chernyshev > > http://www.sergeychernyshev.com/ > > > > -- > Roses are red,Violets are blue,I'm schizophrenic,and so am I. > |
From: Robert M. <mra...@gm...> - 2008-06-02 20:37:07
|
This is what we've done. I've actually had to install four additional extensions. Basically, I'm still griping because n-ary is handled with such difficulty. If the long n-ary data was passed individually then it could be handled with nothing more than Extension:Parser Functions. As it is, you need to learn Loops, StringFunctions (or RegexParserFunctions), Variables and CharacterEscapes. The development of these is in no way connected to SMW and none of them are documented on S-MW.org. I really think this is a bad idea, since those extension could fork or die at any time, and then SMW users would be up Poop Creek. Wouldn't it be better if you could just do something like this: {{#ask: [[Category:Educated Person]] |?Undergraduate degree |?Master's degree |?Doctorate degree |format = template |1 = New York University |N-ary = explode |template = Men of Letters }} An example person might be [[Michael F. Singer]] [[Undergraduate degree::Bachelor's of Arts; Mathematics; 1970; New York University]] [[Master's Degree::Master's of Arts; Mathematics; 1972; University of California at Berkeley]] [[Doctorate degree::Ph.D; Mathematics; 1974; University of California at Berkeley; Functions Satisfying Elementary Relations; Maxwell Rosenlicht]] [[Category:Educated Person]] When {{Template:Men_of_Letter}} is called, every time it is called, {{{1}}} is "New York University". When it comes to Dr. Singer, {{{2}}} will be his pagename, {{{3}}} will be Bachelor's of Arts, {{{4}}} will be Mathematics, etc. That way, it can be easily dwelt with, without the extra step of chopping up the n-ary data. Sergey, do you think this would be a good idea? -Robert On Mon, Jun 2, 2008 at 11:45 AM, Sergey Chernyshev <sem...@an...> wrote: > OK, so you're talking about formatting templates that transform the results > of the query, not the templates that just have queries within them. > > I didn't work that much with formatting templates, but in general, as I > understand, you get results as numbered parameters - then in there, you can > use them to trigger logic. If you need MW variables to be run in context of > specific page rather then default (which is meaningless since template is > called by ASK parser function and not just being inserted into the page), > then you might want to write your own parser functions or reuse existing > ones that match MW variables - here's the example: > http://www.mediawiki.org/wiki/Extension:PathFunctions > > Hope this helps. > > Sergey > > > On Fri, May 30, 2008 at 3:20 PM, Robert Murphy <mra...@gm...> > wrote: >> >> OK. I can't think of an example other than my own stuff, so here goes: >> >> Imagine a gazillion sentences made up of Greek words. Each word has a >> dictionary form and a particular way it's used in each instances. >> Each sentence has a page, full of [[Uses Parsed Greek::Greek:Word; >> Greek:Parsing]] (each word and each parsing have an individual page in >> the Greek namespace). If I want to query against my data for all the >> ways Greek:One is used in each sentence, I >> >> {{#ask: [[Category:Greek sentence]] [[Uses Parsed Greek::Greek:One; ?]] >> |?Uses Parsed Greek >> }} >> >> This, unfortunately, returns a huge swath of other data, namely, how >> each and every other word is used (it is, however, limited to >> sentences that use Greek:One). There's seems to be no easy way to >> limit what is returned. >> So, I made a monster-bloated template that parses over the n-ary data >> and finds the Greek:Parsing for Greek:One. This template is the >> template= from an #ask query. However, I didn't want to hard-code in >> "Greek:One", so I did the only variable I could think of >> {{BASEPAGENAME}}. Now, this template can only be called as part of an >> #ask from the Greek:Word page to find out how that word is used. >> If #ask when format=template could just pass an extra variable, then >> my elaborate template could look for usages of that word and not have >> to be bound to use {{MAGIC_WORDS}}. >> >> -Robert >> http://reformedword.org/Greek:One - example page >> http://reformedword.org/Template:Greek_Chopper - my twisted template >> >> On Fri, May 30, 2008 at 11:33 AM, Sergey Chernyshev >> <sem...@an...> wrote: >> > Hmm. I think I'll need to see an example of the problem you're trying to >> > solve to understand your question - it seems that there might be several >> > issues - some connected with passing parameters and some connected with >> > multi-value properties (they are not really n-ary relations). >> > >> > Sergey >> > >> > >> > On Fri, May 30, 2008 at 2:18 PM, Robert Murphy >> > <mra...@gm...> >> > wrote: >> >> >> >> So -is- there a way to pass an additional bit of data in a query? >> >> Sifting through n-ary data could be a lot easier if you could just >> >> pass even one value along with each template call in an #ask: >> >> >> >> >> >> On Fri, May 30, 2008 at 10:49 AM, Sergey Chernyshev >> >> <sem...@an...> wrote: >> >> > Actually, this problem went away once ASK was rewritten as parser >> >> > function >> >> > and you can use it all as with any other parser function. Basically, >> >> > that >> >> > was the main reason for parser function development. >> >> > >> >> > Sergey >> >> > >> >> > >> >> > On Fri, May 30, 2008 at 4:50 AM, Rolf Lampa <rol...@ri...> >> >> > wrote: >> >> >> >> >> >> The documentation says that parameters can NOT be used in queries, >> >> >> not in "any case. See this page >> >> >> >> >> >> >> >> >> >> >> >> http://semantic-mediawiki.org/wiki/Help:Semantic_search#Using_templates_and_variables >> >> >> >> >> >> The text doesn't seem to reveal the whole truth, though. The text >> >> >> says: >> >> >> >> >> >> >> == Using templates and variables == >> >> >> >> >> >> >> >> Within a query, arbitrary templates and variables can be used. >> >> >> >> This can be used to create a standard query that displays all >> >> >> >> future events (where "future" gets its meaning from the current >> >> >> date): >> >> >> >> >> >> <snip> It goes on to say: >> >> >> >> >> >> >> Many other uses are possible, especially when using queries >> >> >> inline. >> >> >> >> However, it is in *no case possible* to use template parameters >> >> >> (the >> >> >> >> things in {{{ }}}) within a query. *Sorry*. >> >> >> >> >> >> But, parameters /can/ be used in a query, although not directly. I >> >> >> suggest >> >> >> assigning parameter values to temporary variables, and then use the >> >> >> variables in the query instead, like so: >> >> >> >> >> >> // 1. Assign {{{param values}}} to temp variables : >> >> >> >> >> >> {{#vardefine: tmp_pageclass | {{{1|}}} }} >> >> >> {{#vardefine: tmp_property | {{{2|}}} }} >> >> >> >> >> >> // 2. In this way the variables (params) actually /can/ be used in >> >> >> the >> >> >> query: >> >> >> >> >> >> {{#ask: [[Category:{{#var:tmp_pageclass}}]] >> >> >> | [[{{#var:tmp_property}}::+]] [[{{#var:tmp_property}}::*]] >> >> >> }} >> >> >> >> >> >> Tested, and it works. Perhaps a hint to use "param-variables" like >> >> >> this >> >> >> should be added to the documentation as well. >> >> >> >> >> >> Regards, >> >> >> >> >> >> // Rolf Lampa >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------- >> >> >> This SF.net email is sponsored by: Microsoft >> >> >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> >> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> >> _______________________________________________ >> >> >> Semediawiki-user mailing list >> >> >> Sem...@li... >> >> >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >> >> > >> >> > >> >> > >> >> > -- >> >> > Sergey Chernyshev >> >> > http://www.sergeychernyshev.com/ >> >> > >> >> > >> >> > ------------------------------------------------------------------------- >> >> > This SF.net email is sponsored by: Microsoft >> >> > Defy all challenges. Microsoft(R) Visual Studio 2008. >> >> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> > _______________________________________________ >> >> > Semediawiki-user mailing list >> >> > Sem...@li... >> >> > https://lists.sourceforge.net/lists/listinfo/semediawiki-user >> >> > >> >> > >> >> >> >> >> >> >> >> -- >> >> Roses are red,Violets are blue,I'm schizophrenic,and so am I. >> >> >> >> >> >> ------------------------------------------------------------------------- >> >> This SF.net email is sponsored by: Microsoft >> >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> >> _______________________________________________ >> >> Semediawiki-user mailing list >> >> Sem...@li... >> >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >> > >> > >> > >> > -- >> > Sergey Chernyshev >> > http://www.sergeychernyshev.com/ >> >> >> >> -- >> Roses are red,Violets are blue,I'm schizophrenic,and so am I. > -- Roses are red,Violets are blue,I'm schizophrenic,and so am I. |
From: Rolf L. <rol...@ri...> - 2008-05-30 18:34:05
|
OK, that happened before I started to look into SMW. And now also the documentation is up to date. // Rolf Lampa Sergey Chernyshev skrev: > Actually, this problem went away once ASK was rewritten as parser > function and you can use it all as with any other parser function. > Basically, that was the main reason for parser function development. > > Sergey > > > On Fri, May 30, 2008 at 4:50 AM, Rolf Lampa <rol...@ri... > <mailto:rol...@ri...>> wrote: > > The documentation says that parameters can NOT be used in queries, > not in "any case. See this page > http://semantic-mediawiki.org/wiki/Help:Semantic_search#Using_templates_and_variables > > The text doesn't seem to reveal the whole truth, though. The text > says: > |
From: S P. <in...@sk...> - 2008-06-06 11:02:56
|
Robert Murphy wrote: > So -is- there a way to pass an additional bit of data in a query? 1. Rolf Lampa suggested #vardefine, which from the useful table in http://www.mediawiki.org/wiki/Extension:Parser_function_extensions is part of VariablesExtension. 2. Another approach is to create a different template for each different "bit of data", and have all these in turn call one main template. So your inline query would be |format=template |template=NYU Letterman Then Template:NYU_Letterman would invoke the generic Template:Generic_letterman, passing its additional bit of data: {{Generic letterman|1={{{1}}}|2={{{2}}}|...|userparam=NYU}} I made a demo at http://sandbox.semantic-mediawiki.org/wiki/Test_query 3. If these workarounds aren't good enough and there's enough interest in this feature, it's certainly possible to implement an arbitrary userparam (I think a few lines in three SMW_QueryPrinter files) so you would just invoke |format=template |template=Generic letterman |userparam=whatever you want to pass to your template File an enhancement bug at https://bugzilla.wikimedia.org if you want this. -- =S Page |
From: Samuel R. <sa...@ri...> - 2008-06-11 05:38:00
|
A new extension to produce the markup, I'd like to be able to link the SMW data with it but I needed to keep moving forward with the site. Samuel Richardson T: (0405) 472 748 richardson.co.nz On 11/06/2008, at 1:29 PM, Sergey Chernyshev wrote: > Are you creating the data for KML export using SMW data or just use > templates to produce another type of markup? > > Sergey > > > On Tue, Jun 10, 2008 at 7:21 PM, Samuel Richardson <sa...@ri... > > wrote: > Sergey, > > I've come up with a work around fix for my site by installing the > KML export extension and configuring Google Maps to read in the KML > files produced by it, as a side result I now have a set of KML files > available for other people to use :) > > Samuel > > > > On Wed, Jun 11, 2008 at 2:45 AM, Sergey Chernyshev <sem...@an... > > wrote: > For now, RSS formatter is quite weak and doesn't support anything > beyond the title and date so the only approach is to implement more > search results to be associated with RSS item. > > I'll be happy to discuss details of this. > > Sergey > > > > On Mon, Jun 9, 2008 at 11:58 PM, Samuel Richardson <sa...@ri... > > wrote: > Yes, I came to a similar conclusion. Any ideas on the best method to > go about this? > > Samuel Richardson > > T: (0405) 472 748 > > richardson.co.nz > > On 10/06/2008, at 11:39 AM, Sergey Chernyshev wrote: > >> I think one approach would be to generate GeoRSS and use RSS >> feeding into the Google Map. >> >> Sergey >> >> >> On Mon, Jun 9, 2008 at 8:06 PM, Samuel Richardson <sa...@ri... >> > wrote: >> Hello List, >> >> I've been using the excellent Semantic Maps extension in conjunction >> with the Semantic Forms plug in to geolocate items in my Wiki. I'd >> been linking these together using the DynamicPageList extension to >> generate Google maps, you can see an example of this here: >> >> http://www.melpedia.com.au/wiki/Art_Galleries >> >> This generates nice maps with clickable points that can display a >> preview image and description. The problem I've run in to is that >> once >> I get past about 60 points on the map the DPL extension causes the >> MySQL database to run out of memory. It would be much more efficient >> to directly link the SMW ask queries to generate the entries inside >> the Google Map. I created a query that generated all the needed items >> and linked that to a custom template. That template lives here: >> >> http://www.melpedia.com.au/wiki/Template:GoogleMapCategory_SMW_GenerateMap >> >> And an example output of that template: >> >> http://www.melpedia.com.au/wiki/Restaurants >> >> The problem I have is the extra <p> tags being generated in the >> template are stopping the Google Maps extension from correctly >> parsing >> the output of the template (I've removed the GoogleMaps tag at the >> moment so you can correctly see the template output). Google Maps >> takes content in the following format: >> >> -31, -31 Title >> Content for the pop up box. >> >> The outputted code is generating: >> >> <p>-31, 31 Title >> >> Which is enough to upset the parsing. Does anyone have any ideas >> about >> how I could go about linking SMW and Google Maps? Either get my first >> example working or another approach that I could take? (Perhaps I >> could transform the XML output of the pages into KML?) >> >> Thanks, >> >> Samuel Richardson >> >> T: (0405) 472 748 >> >> richardson.co.nz >> >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> _______________________________________________ >> Semediawiki-user mailing list >> Sem...@li... >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >> >> >> >> -- >> Sergey Chernyshev >> http://www.sergeychernyshev.com/ > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > -- > Sergey Chernyshev > http://www.sergeychernyshev.com/ > > > > -- > Samuel Richardson > Freelance Web Developer > www.richardson.co.nz | 0405 472 748 > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > -- > Sergey Chernyshev > http://www.sergeychernyshev.com/ |
From: Sergey C. <sem...@an...> - 2008-06-21 16:46:49
|
I think it's a good question of how SMW can support some custom formats and KML specifically since SMW supports geo types natively. Sergey On Wed, Jun 11, 2008 at 1:37 AM, Samuel Richardson <sa...@ri...> wrote: > A new extension to produce the markup, I'd like to be able to link the SMW > data with it but I needed to keep moving forward with the site. > > Samuel Richardson > > T: (0405) 472 748 > > richardson.co.nz > > On 11/06/2008, at 1:29 PM, Sergey Chernyshev wrote: > > Are you creating the data for KML export using SMW data or just use > templates to produce another type of markup? > > Sergey > > > On Tue, Jun 10, 2008 at 7:21 PM, Samuel Richardson <sa...@ri...> > wrote: > >> Sergey, >> >> I've come up with a work around fix for my site by installing the KML >> export extension and configuring Google Maps to read in the KML files >> produced by it, as a side result I now have a set of KML files available for >> other people to use :) >> >> Samuel >> >> >> >> On Wed, Jun 11, 2008 at 2:45 AM, Sergey Chernyshev < >> sem...@an...> wrote: >> >>> For now, RSS formatter is quite weak and doesn't support anything beyond >>> the title and date so the only approach is to implement more search results >>> to be associated with RSS item. >>> >>> I'll be happy to discuss details of this. >>> >>> Sergey >>> >>> >>> >>> On Mon, Jun 9, 2008 at 11:58 PM, Samuel Richardson <sa...@ri...> >>> wrote: >>> >>>> Yes, I came to a similar conclusion. Any ideas on the best method to go >>>> about this? >>>> >>>> Samuel Richardson >>>> >>>> T: (0405) 472 748 >>>> >>>> richardson.co.nz >>>> >>>> On 10/06/2008, at 11:39 AM, Sergey Chernyshev wrote: >>>> >>>> I think one approach would be to generate GeoRSS and use RSS feeding >>>> into the Google Map. >>>> >>>> Sergey >>>> >>>> >>>> On Mon, Jun 9, 2008 at 8:06 PM, Samuel Richardson <sa...@ri...> >>>> wrote: >>>> >>>>> Hello List, >>>>> >>>>> I've been using the excellent Semantic Maps extension in conjunction >>>>> with the Semantic Forms plug in to geolocate items in my Wiki. I'd >>>>> been linking these together using the DynamicPageList extension to >>>>> generate Google maps, you can see an example of this here: >>>>> >>>>> http://www.melpedia.com.au/wiki/Art_Galleries >>>>> >>>>> This generates nice maps with clickable points that can display a >>>>> preview image and description. The problem I've run in to is that once >>>>> I get past about 60 points on the map the DPL extension causes the >>>>> MySQL database to run out of memory. It would be much more efficient >>>>> to directly link the SMW ask queries to generate the entries inside >>>>> the Google Map. I created a query that generated all the needed items >>>>> and linked that to a custom template. That template lives here: >>>>> >>>>> >>>>> http://www.melpedia.com.au/wiki/Template:GoogleMapCategory_SMW_GenerateMap >>>>> >>>>> And an example output of that template: >>>>> >>>>> http://www.melpedia.com.au/wiki/Restaurants >>>>> >>>>> The problem I have is the extra <p> tags being generated in the >>>>> template are stopping the Google Maps extension from correctly parsing >>>>> the output of the template (I've removed the GoogleMaps tag at the >>>>> moment so you can correctly see the template output). Google Maps >>>>> takes content in the following format: >>>>> >>>>> -31, -31 Title >>>>> Content for the pop up box. >>>>> >>>>> The outputted code is generating: >>>>> >>>>> <p>-31, 31 Title >>>>> >>>>> Which is enough to upset the parsing. Does anyone have any ideas about >>>>> how I could go about linking SMW and Google Maps? Either get my first >>>>> example working or another approach that I could take? (Perhaps I >>>>> could transform the XML output of the pages into KML?) >>>>> >>>>> Thanks, >>>>> >>>>> Samuel Richardson >>>>> >>>>> T: (0405) 472 748 >>>>> >>>>> richardson.co.nz >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------- >>>>> Check out the new SourceForge.net Marketplace. >>>>> It's the best place to buy or sell services for >>>>> just about anything Open Source. >>>>> http://sourceforge.net/services/buy/index.php >>>>> _______________________________________________ >>>>> Semediawiki-user mailing list >>>>> Sem...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >>>>> >>>> >>>> >>>> >>>> -- >>>> Sergey Chernyshev >>>> http://www.sergeychernyshev.com/ >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------- >>>> Check out the new SourceForge.net Marketplace. >>>> It's the best place to buy or sell services for >>>> just about anything Open Source. >>>> http://sourceforge.net/services/buy/index.php >>>> _______________________________________________ >>>> Semediawiki-user mailing list >>>> Sem...@li... >>>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >>>> >>>> >>> >>> >>> -- >>> Sergey Chernyshev >>> http://www.sergeychernyshev.com/ >>> >> >> >> >> -- >> Samuel Richardson >> Freelance Web Developer >> www.richardson.co.nz | 0405 472 748 >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> _______________________________________________ >> Semediawiki-user mailing list >> Sem...@li... >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >> >> > > > -- > Sergey Chernyshev > http://www.sergeychernyshev.com/ > > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > -- Sergey Chernyshev http://www.sergeychernyshev.com/ |
From: S P. <in...@sk...> - 2008-06-06 11:21:30
|
Summary: adding parts=exploded parameter for inline queries with templates would make the template receive the separate parts of each value, similar to service links. In the thread "How to: Using parameters in queries", Robert Murphy wrote: > I'm still griping because n-ary is handled > with such difficulty. If the long n-ary data was passed individually > then it could be handled with nothing more than Extension:Parser > Functions. I have a hard time figuring out the specifics of what you want, but I think you point out an important limitation. With format=template, one has no control over the individual field values passed to your template, it's just the wiki text of each item. You've found that you don't get the individual pieces of a many-valued property so you can process them. Another user might want to get the number and units of a linear value separately. SMW already deals with this in a different context. Most datatypes already can provide the individual elements of a value to Service links <http://semantic-mediawiki.org/wiki/Help:Service_links#Information_passed_for_each_placeholder> So, if inline queries had a new "parts=exploded" option to send the same individual elements of each value to a template, you and others would have more formatting control. There's currently a glitch in this: many-valued properties don't currently provide individual bits of a value for service links (bug 14426, I provided a patch). It's not as simple as it sounds. E.g. some parts that datatypes return for service links are URL-encoded because service links are specifically for fabricating hyperlinks. -- =S Page |
From: Robert M. <mra...@gm...> - 2008-06-06 11:35:27
|
THANK YOU! I really appreciate you taking the time to understand what I've been saying. Perhaps I could've expressed it more clearly... Anyway, should I submit an enhancement request? This is the lynch pin holding up my wiki! A service link wouldn't help me, unless I rolled my own CGI to handle the results. I would really like templates to be able to handle very large, n-ary data. -Robert On Fri, Jun 6, 2008 at 4:20 AM, S Page <in...@sk...> wrote: > Summary: adding parts=exploded parameter for inline queries with templates > would make the template receive the separate parts of each value, similar to > service links. > > > In the thread "How to: Using parameters in queries", Robert Murphy wrote: > >> I'm still griping because n-ary is handled >> with such difficulty. If the long n-ary data was passed individually >> then it could be handled with nothing more than Extension:Parser >> Functions. >> > > I have a hard time figuring out the specifics of what you want, but I think > you point out an important limitation. > > With format=template, one has no control over the individual field values > passed to your template, it's just the wiki text of each item. You've found > that you don't get the individual pieces of a many-valued property so you > can process them. Another user might want to get the number and units of a > linear value separately. > > SMW already deals with this in a different context. Most datatypes already > can provide the individual elements of a value to Service links < > http://semantic-mediawiki.org/wiki/Help:Service_links#Information_passed_for_each_placeholder > > > > So, if inline queries had a new "parts=exploded" option to send the same > individual elements of each value to a template, you and others would have > more formatting control. > > There's currently a glitch in this: many-valued properties don't currently > provide individual bits of a value for service links (bug 14426, I provided > a patch). > > It's not as simple as it sounds. E.g. some parts that datatypes return for > service links are URL-encoded because service links are specifically for > fabricating hyperlinks. > > -- > =S Page > -- Roses are red,Violets are blue,I'm schizophrenic,and so am I. |
From: Sergey C. <sem...@an...> - 2008-06-09 21:14:28
|
OK, now I understand what you want to do - you want to reuse one formatting template for multiple #ask queries and with each call to #ask you want to pass different values for some parameter that will be used in a template in addition to the query results. Let me know if that's correct summary. First of all, try to use #vardefine as S Page suggested, if that doesn't work for you, then yes, it might make sense to pass additional parameters to formatting template through #ask call, I'll probably suggest named parameters instead of numbered as it'll be easier to distinguish them from query results. Once again, S Page suggested correct way of going for it, file a bug and maybe even a patch, it'll definitely speed up the process. Sergey On Fri, Jun 6, 2008 at 7:01 AM, S Page <in...@sk...> wrote: > Robert Murphy wrote: > > So -is- there a way to pass an additional bit of data in a query? > > 1. Rolf Lampa suggested #vardefine, which from the useful table in > http://www.mediawiki.org/wiki/Extension:Parser_function_extensions is > part of VariablesExtension. > > > 2. Another approach is to create a different template for each different > "bit of data", and have all these in turn call one main template. > So your inline query would be > |format=template > |template=NYU Letterman > > Then Template:NYU_Letterman would invoke the generic > Template:Generic_letterman, passing its additional bit of data: > {{Generic letterman|1={{{1}}}|2={{{2}}}|...|userparam=NYU}} > > I made a demo at http://sandbox.semantic-mediawiki.org/wiki/Test_query > > > 3. If these workarounds aren't good enough and there's enough interest > in this feature, it's certainly possible to implement an arbitrary > userparam (I think a few lines in three SMW_QueryPrinter files) so you > would just invoke > |format=template > |template=Generic letterman > |userparam=whatever you want to pass to your template > > File an enhancement bug at https://bugzilla.wikimedia.org if you want > this. > > -- > =S Page > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > -- Sergey Chernyshev http://www.sergeychernyshev.com/ |
From: Samuel R. <sa...@ri...> - 2008-06-10 00:06:24
|
Hello List, I've been using the excellent Semantic Maps extension in conjunction with the Semantic Forms plug in to geolocate items in my Wiki. I'd been linking these together using the DynamicPageList extension to generate Google maps, you can see an example of this here: http://www.melpedia.com.au/wiki/Art_Galleries This generates nice maps with clickable points that can display a preview image and description. The problem I've run in to is that once I get past about 60 points on the map the DPL extension causes the MySQL database to run out of memory. It would be much more efficient to directly link the SMW ask queries to generate the entries inside the Google Map. I created a query that generated all the needed items and linked that to a custom template. That template lives here: http://www.melpedia.com.au/wiki/Template:GoogleMapCategory_SMW_GenerateMap And an example output of that template: http://www.melpedia.com.au/wiki/Restaurants The problem I have is the extra <p> tags being generated in the template are stopping the Google Maps extension from correctly parsing the output of the template (I've removed the GoogleMaps tag at the moment so you can correctly see the template output). Google Maps takes content in the following format: -31, -31 Title Content for the pop up box. The outputted code is generating: <p>-31, 31 Title Which is enough to upset the parsing. Does anyone have any ideas about how I could go about linking SMW and Google Maps? Either get my first example working or another approach that I could take? (Perhaps I could transform the XML output of the pages into KML?) Thanks, Samuel Richardson T: (0405) 472 748 richardson.co.nz |
From: Sergey C. <sem...@an...> - 2008-06-10 01:39:41
|
I think one approach would be to generate GeoRSS and use RSS feeding into the Google Map. Sergey On Mon, Jun 9, 2008 at 8:06 PM, Samuel Richardson <sa...@ri...> wrote: > Hello List, > > I've been using the excellent Semantic Maps extension in conjunction > with the Semantic Forms plug in to geolocate items in my Wiki. I'd > been linking these together using the DynamicPageList extension to > generate Google maps, you can see an example of this here: > > http://www.melpedia.com.au/wiki/Art_Galleries > > This generates nice maps with clickable points that can display a > preview image and description. The problem I've run in to is that once > I get past about 60 points on the map the DPL extension causes the > MySQL database to run out of memory. It would be much more efficient > to directly link the SMW ask queries to generate the entries inside > the Google Map. I created a query that generated all the needed items > and linked that to a custom template. That template lives here: > > http://www.melpedia.com.au/wiki/Template:GoogleMapCategory_SMW_GenerateMap > > And an example output of that template: > > http://www.melpedia.com.au/wiki/Restaurants > > The problem I have is the extra <p> tags being generated in the > template are stopping the Google Maps extension from correctly parsing > the output of the template (I've removed the GoogleMaps tag at the > moment so you can correctly see the template output). Google Maps > takes content in the following format: > > -31, -31 Title > Content for the pop up box. > > The outputted code is generating: > > <p>-31, 31 Title > > Which is enough to upset the parsing. Does anyone have any ideas about > how I could go about linking SMW and Google Maps? Either get my first > example working or another approach that I could take? (Perhaps I > could transform the XML output of the pages into KML?) > > Thanks, > > Samuel Richardson > > T: (0405) 472 748 > > richardson.co.nz > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > -- Sergey Chernyshev http://www.sergeychernyshev.com/ |
From: Samuel R. <sa...@ri...> - 2008-06-10 03:59:13
|
Yes, I came to a similar conclusion. Any ideas on the best method to go about this? Samuel Richardson T: (0405) 472 748 richardson.co.nz On 10/06/2008, at 11:39 AM, Sergey Chernyshev wrote: > I think one approach would be to generate GeoRSS and use RSS feeding > into the Google Map. > > Sergey > > > On Mon, Jun 9, 2008 at 8:06 PM, Samuel Richardson <sa...@ri... > > wrote: > Hello List, > > I've been using the excellent Semantic Maps extension in conjunction > with the Semantic Forms plug in to geolocate items in my Wiki. I'd > been linking these together using the DynamicPageList extension to > generate Google maps, you can see an example of this here: > > http://www.melpedia.com.au/wiki/Art_Galleries > > This generates nice maps with clickable points that can display a > preview image and description. The problem I've run in to is that once > I get past about 60 points on the map the DPL extension causes the > MySQL database to run out of memory. It would be much more efficient > to directly link the SMW ask queries to generate the entries inside > the Google Map. I created a query that generated all the needed items > and linked that to a custom template. That template lives here: > > http://www.melpedia.com.au/wiki/Template:GoogleMapCategory_SMW_GenerateMap > > And an example output of that template: > > http://www.melpedia.com.au/wiki/Restaurants > > The problem I have is the extra <p> tags being generated in the > template are stopping the Google Maps extension from correctly parsing > the output of the template (I've removed the GoogleMaps tag at the > moment so you can correctly see the template output). Google Maps > takes content in the following format: > > -31, -31 Title > Content for the pop up box. > > The outputted code is generating: > > <p>-31, 31 Title > > Which is enough to upset the parsing. Does anyone have any ideas about > how I could go about linking SMW and Google Maps? Either get my first > example working or another approach that I could take? (Perhaps I > could transform the XML output of the pages into KML?) > > Thanks, > > Samuel Richardson > > T: (0405) 472 748 > > richardson.co.nz > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > -- > Sergey Chernyshev > http://www.sergeychernyshev.com/ |
From: Sergey C. <sem...@an...> - 2008-06-10 16:45:28
|
For now, RSS formatter is quite weak and doesn't support anything beyond the title and date so the only approach is to implement more search results to be associated with RSS item. I'll be happy to discuss details of this. Sergey On Mon, Jun 9, 2008 at 11:58 PM, Samuel Richardson <sa...@ri...> wrote: > Yes, I came to a similar conclusion. Any ideas on the best method to go > about this? > > Samuel Richardson > > T: (0405) 472 748 > > richardson.co.nz > > On 10/06/2008, at 11:39 AM, Sergey Chernyshev wrote: > > I think one approach would be to generate GeoRSS and use RSS feeding into > the Google Map. > > Sergey > > > On Mon, Jun 9, 2008 at 8:06 PM, Samuel Richardson <sa...@ri...> > wrote: > >> Hello List, >> >> I've been using the excellent Semantic Maps extension in conjunction >> with the Semantic Forms plug in to geolocate items in my Wiki. I'd >> been linking these together using the DynamicPageList extension to >> generate Google maps, you can see an example of this here: >> >> http://www.melpedia.com.au/wiki/Art_Galleries >> >> This generates nice maps with clickable points that can display a >> preview image and description. The problem I've run in to is that once >> I get past about 60 points on the map the DPL extension causes the >> MySQL database to run out of memory. It would be much more efficient >> to directly link the SMW ask queries to generate the entries inside >> the Google Map. I created a query that generated all the needed items >> and linked that to a custom template. That template lives here: >> >> http://www.melpedia.com.au/wiki/Template:GoogleMapCategory_SMW_GenerateMap >> >> And an example output of that template: >> >> http://www.melpedia.com.au/wiki/Restaurants >> >> The problem I have is the extra <p> tags being generated in the >> template are stopping the Google Maps extension from correctly parsing >> the output of the template (I've removed the GoogleMaps tag at the >> moment so you can correctly see the template output). Google Maps >> takes content in the following format: >> >> -31, -31 Title >> Content for the pop up box. >> >> The outputted code is generating: >> >> <p>-31, 31 Title >> >> Which is enough to upset the parsing. Does anyone have any ideas about >> how I could go about linking SMW and Google Maps? Either get my first >> example working or another approach that I could take? (Perhaps I >> could transform the XML output of the pages into KML?) >> >> Thanks, >> >> Samuel Richardson >> >> T: (0405) 472 748 >> >> richardson.co.nz >> >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> _______________________________________________ >> Semediawiki-user mailing list >> Sem...@li... >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >> > > > > -- > Sergey Chernyshev > http://www.sergeychernyshev.com/ > > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > -- Sergey Chernyshev http://www.sergeychernyshev.com/ |
From: Samuel R. <sa...@ri...> - 2008-06-10 23:21:08
|
Sergey, I've come up with a work around fix for my site by installing the KML export extension and configuring Google Maps to read in the KML files produced by it, as a side result I now have a set of KML files available for other people to use :) Samuel On Wed, Jun 11, 2008 at 2:45 AM, Sergey Chernyshev < sem...@an...> wrote: > For now, RSS formatter is quite weak and doesn't support anything beyond > the title and date so the only approach is to implement more search results > to be associated with RSS item. > > I'll be happy to discuss details of this. > > Sergey > > > > On Mon, Jun 9, 2008 at 11:58 PM, Samuel Richardson <sa...@ri...> > wrote: > >> Yes, I came to a similar conclusion. Any ideas on the best method to go >> about this? >> >> Samuel Richardson >> >> T: (0405) 472 748 >> >> richardson.co.nz >> >> On 10/06/2008, at 11:39 AM, Sergey Chernyshev wrote: >> >> I think one approach would be to generate GeoRSS and use RSS feeding into >> the Google Map. >> >> Sergey >> >> >> On Mon, Jun 9, 2008 at 8:06 PM, Samuel Richardson <sa...@ri...> >> wrote: >> >>> Hello List, >>> >>> I've been using the excellent Semantic Maps extension in conjunction >>> with the Semantic Forms plug in to geolocate items in my Wiki. I'd >>> been linking these together using the DynamicPageList extension to >>> generate Google maps, you can see an example of this here: >>> >>> http://www.melpedia.com.au/wiki/Art_Galleries >>> >>> This generates nice maps with clickable points that can display a >>> preview image and description. The problem I've run in to is that once >>> I get past about 60 points on the map the DPL extension causes the >>> MySQL database to run out of memory. It would be much more efficient >>> to directly link the SMW ask queries to generate the entries inside >>> the Google Map. I created a query that generated all the needed items >>> and linked that to a custom template. That template lives here: >>> >>> >>> http://www.melpedia.com.au/wiki/Template:GoogleMapCategory_SMW_GenerateMap >>> >>> And an example output of that template: >>> >>> http://www.melpedia.com.au/wiki/Restaurants >>> >>> The problem I have is the extra <p> tags being generated in the >>> template are stopping the Google Maps extension from correctly parsing >>> the output of the template (I've removed the GoogleMaps tag at the >>> moment so you can correctly see the template output). Google Maps >>> takes content in the following format: >>> >>> -31, -31 Title >>> Content for the pop up box. >>> >>> The outputted code is generating: >>> >>> <p>-31, 31 Title >>> >>> Which is enough to upset the parsing. Does anyone have any ideas about >>> how I could go about linking SMW and Google Maps? Either get my first >>> example working or another approach that I could take? (Perhaps I >>> could transform the XML output of the pages into KML?) >>> >>> Thanks, >>> >>> Samuel Richardson >>> >>> T: (0405) 472 748 >>> >>> richardson.co.nz >>> >>> >>> ------------------------------------------------------------------------- >>> Check out the new SourceForge.net Marketplace. >>> It's the best place to buy or sell services for >>> just about anything Open Source. >>> http://sourceforge.net/services/buy/index.php >>> _______________________________________________ >>> Semediawiki-user mailing list >>> Sem...@li... >>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >>> >> >> >> >> -- >> Sergey Chernyshev >> http://www.sergeychernyshev.com/ >> >> >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> _______________________________________________ >> Semediawiki-user mailing list >> Sem...@li... >> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >> >> > > > -- > Sergey Chernyshev > http://www.sergeychernyshev.com/ > -- Samuel Richardson Freelance Web Developer www.richardson.co.nz | 0405 472 748 |
From: Sergey C. <sem...@an...> - 2008-06-11 03:29:59
|
Are you creating the data for KML export using SMW data or just use templates to produce another type of markup? Sergey On Tue, Jun 10, 2008 at 7:21 PM, Samuel Richardson <sa...@ri...> wrote: > Sergey, > > I've come up with a work around fix for my site by installing the KML > export extension and configuring Google Maps to read in the KML files > produced by it, as a side result I now have a set of KML files available for > other people to use :) > > Samuel > > > > On Wed, Jun 11, 2008 at 2:45 AM, Sergey Chernyshev < > sem...@an...> wrote: > >> For now, RSS formatter is quite weak and doesn't support anything beyond >> the title and date so the only approach is to implement more search results >> to be associated with RSS item. >> >> I'll be happy to discuss details of this. >> >> Sergey >> >> >> >> On Mon, Jun 9, 2008 at 11:58 PM, Samuel Richardson <sa...@ri...> >> wrote: >> >>> Yes, I came to a similar conclusion. Any ideas on the best method to go >>> about this? >>> >>> Samuel Richardson >>> >>> T: (0405) 472 748 >>> >>> richardson.co.nz >>> >>> On 10/06/2008, at 11:39 AM, Sergey Chernyshev wrote: >>> >>> I think one approach would be to generate GeoRSS and use RSS feeding into >>> the Google Map. >>> >>> Sergey >>> >>> >>> On Mon, Jun 9, 2008 at 8:06 PM, Samuel Richardson <sa...@ri...> >>> wrote: >>> >>>> Hello List, >>>> >>>> I've been using the excellent Semantic Maps extension in conjunction >>>> with the Semantic Forms plug in to geolocate items in my Wiki. I'd >>>> been linking these together using the DynamicPageList extension to >>>> generate Google maps, you can see an example of this here: >>>> >>>> http://www.melpedia.com.au/wiki/Art_Galleries >>>> >>>> This generates nice maps with clickable points that can display a >>>> preview image and description. The problem I've run in to is that once >>>> I get past about 60 points on the map the DPL extension causes the >>>> MySQL database to run out of memory. It would be much more efficient >>>> to directly link the SMW ask queries to generate the entries inside >>>> the Google Map. I created a query that generated all the needed items >>>> and linked that to a custom template. That template lives here: >>>> >>>> >>>> http://www.melpedia.com.au/wiki/Template:GoogleMapCategory_SMW_GenerateMap >>>> >>>> And an example output of that template: >>>> >>>> http://www.melpedia.com.au/wiki/Restaurants >>>> >>>> The problem I have is the extra <p> tags being generated in the >>>> template are stopping the Google Maps extension from correctly parsing >>>> the output of the template (I've removed the GoogleMaps tag at the >>>> moment so you can correctly see the template output). Google Maps >>>> takes content in the following format: >>>> >>>> -31, -31 Title >>>> Content for the pop up box. >>>> >>>> The outputted code is generating: >>>> >>>> <p>-31, 31 Title >>>> >>>> Which is enough to upset the parsing. Does anyone have any ideas about >>>> how I could go about linking SMW and Google Maps? Either get my first >>>> example working or another approach that I could take? (Perhaps I >>>> could transform the XML output of the pages into KML?) >>>> >>>> Thanks, >>>> >>>> Samuel Richardson >>>> >>>> T: (0405) 472 748 >>>> >>>> richardson.co.nz >>>> >>>> >>>> >>>> ------------------------------------------------------------------------- >>>> Check out the new SourceForge.net Marketplace. >>>> It's the best place to buy or sell services for >>>> just about anything Open Source. >>>> http://sourceforge.net/services/buy/index.php >>>> _______________________________________________ >>>> Semediawiki-user mailing list >>>> Sem...@li... >>>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >>>> >>> >>> >>> >>> -- >>> Sergey Chernyshev >>> http://www.sergeychernyshev.com/ >>> >>> >>> >>> ------------------------------------------------------------------------- >>> Check out the new SourceForge.net Marketplace. >>> It's the best place to buy or sell services for >>> just about anything Open Source. >>> http://sourceforge.net/services/buy/index.php >>> _______________________________________________ >>> Semediawiki-user mailing list >>> Sem...@li... >>> https://lists.sourceforge.net/lists/listinfo/semediawiki-user >>> >>> >> >> >> -- >> Sergey Chernyshev >> http://www.sergeychernyshev.com/ >> > > > > -- > Samuel Richardson > Freelance Web Developer > www.richardson.co.nz | 0405 472 748 > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > -- Sergey Chernyshev http://www.sergeychernyshev.com/ |