You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jena.apache.org by Claude Warren <cl...@xenei.com> on 2017/04/01 11:20:12 UTC
Fuseki prefixes
I see that the qonsole-config.js where the prefixes for the queries is
defined. However, I want to know if there is a configuration option that
would allow me to change the list without modification of the source code.
Specifically we have a data-driven problem whereby the prefixes are not
known until query time. Is there a method that will allow us to set them
for the fuseki queries?
A mechanism to gather prefixes over time and persist them would be
sufficient I think, provided we could add prefixes programatically.
Claude
--
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren
Re: Fuseki prefixes
Posted by Claude Warren <cl...@xenei.com>.
Sorry for the confusion, yes it is in the UI that I want to add the
prefixes.
we = my development team + customer.
Customer adds data to a graph, enhancing data produced by the application.
They can specify any namespace they wish for the enhancing data.
I want to collect those namespaces (for simplicity assume that each
namespace is only associated with one prefix) and modify the fuseki query
page to present the prefixes to the user in order to reduce the complexity
of typing queries.
if the qonsole-config.js is not used where does the UI load the default
prefixes that it displays on startup?
Claude
On Sun, Apr 2, 2017 at 11:20 AM, Andy Seaborne <an...@apache.org> wrote:
> Claude,
>
> Do you mean prefixes in the UI?
>
> At one point you seem to be talking about sending the query by API.
>
> On 01/04/17 12:20, Claude Warren wrote:
>
>> I see that the qonsole-config.js where the prefixes for the queries is
>> defined.
>>
>
> Is qonsole-config.js evenloaded? It comes from qonsole which the UI does
> not currently use [*].
>
> However, I want to know if there is a configuration option that
>> would allow me to change the list without modification of the source code.
>>
>
> For the UI, no.
>
> Specifically we have a data-driven problem whereby the prefixes are not
>> known until query time. Is there a method that will allow us to set them
>> for the fuseki queries?
>>
>
> So changing the prefixes used by the UI aren't going to help anyway.
>
> (who is "we"?)
>
> A mechanism to gather prefixes over time and persist them would be
>> sufficient I think, provided we could add prefixes programatically.
>>
>
> This bit makes me think it is not about the UI.
> If programmatically is involved, what's the relationship to the UI?
>
> All queries are self-contained with PREFIX on the front.
>
> yasqe makes the query sticky so the prefixes are sticky.
>
> No UI can be universal to all use cases - maybe you need to have your own
> with features that are specific to your needs. Maybe some features turn out
> to be sufficiently general to migrate to the open source code.
>
>
>> Claude
>>
>>
>
> [*] I'd like to see qonsole return - first as an alternative "query2"
> interface, along side the "query" tab.
>
> The storage-sticky yasqe query pane is nice. My usage is as a dev-admin is
> to jump from dataset to dataset though and its stickiness is at best no
> help and needs to be avoided. I'd like a query UI that is more neutral to
> the dataset. A browser-side history mechanism would be really helpful.
>
--
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren
Re: Fuseki prefixes
Posted by Andy Seaborne <an...@apache.org>.
Hi Chris,
Your right. Apparently, I don't know how to call grep correctly!
Andy
On 02/04/17 14:58, Chris Tomlinson wrote:
> Andy,
>
> In at least one configuration qonsole-config.js is loaded.
>
> We\u2019re using fuseki.war from apache-jena-fuseki-2.5.0.tar.gz in Tomcat 8 and we update the qoncole-config.js in tomcat/webapps/fuseki/js/app/ with the various prefixes used in our application. In this configuration it is loaded in the query tab.
>
> Chris
>
>
>> On Apr 2, 2017, at 5:20 AM, Andy Seaborne <an...@apache.org> wrote:
>>
>>
>> Is qonsole-config.js evenloaded? It comes from qonsole which the UI does not currently use [*].
>
>
Re: Fuseki prefixes
Posted by Chris Tomlinson <ch...@gmail.com>.
Andy,
In at least one configuration qonsole-config.js is loaded.
We’re using fuseki.war from apache-jena-fuseki-2.5.0.tar.gz in Tomcat 8 and we update the qoncole-config.js in tomcat/webapps/fuseki/js/app/ with the various prefixes used in our application. In this configuration it is loaded in the query tab.
Chris
> On Apr 2, 2017, at 5:20 AM, Andy Seaborne <an...@apache.org> wrote:
>
>
> Is qonsole-config.js evenloaded? It comes from qonsole which the UI does not currently use [*].
Re: Fuseki prefixes
Posted by Andy Seaborne <an...@apache.org>.
Claude,
Do you mean prefixes in the UI?
At one point you seem to be talking about sending the query by API.
On 01/04/17 12:20, Claude Warren wrote:
> I see that the qonsole-config.js where the prefixes for the queries is
> defined.
Is qonsole-config.js evenloaded? It comes from qonsole which the UI does
not currently use [*].
> However, I want to know if there is a configuration option that
> would allow me to change the list without modification of the source code.
For the UI, no.
> Specifically we have a data-driven problem whereby the prefixes are not
> known until query time. Is there a method that will allow us to set them
> for the fuseki queries?
So changing the prefixes used by the UI aren't going to help anyway.
(who is "we"?)
> A mechanism to gather prefixes over time and persist them would be
> sufficient I think, provided we could add prefixes programatically.
This bit makes me think it is not about the UI.
If programmatically is involved, what's the relationship to the UI?
All queries are self-contained with PREFIX on the front.
yasqe makes the query sticky so the prefixes are sticky.
No UI can be universal to all use cases - maybe you need to have your
own with features that are specific to your needs. Maybe some features
turn out to be sufficiently general to migrate to the open source code.
>
> Claude
>
[*] I'd like to see qonsole return - first as an alternative "query2"
interface, along side the "query" tab.
The storage-sticky yasqe query pane is nice. My usage is as a dev-admin
is to jump from dataset to dataset though and its stickiness is at best
no help and needs to be avoided. I'd like a query UI that is more
neutral to the dataset. A browser-side history mechanism would be really
helpful.