When selecting a datasource in the list, its type should be visually clear so you can distinguish between SPARQL endpoint, TPF interface, LD docs, etc. A fallback scenario would be adding a prefix in the text.

In order to use tiles from Mapbox, you must also request an access token.
These can be obtained from Mapbox access documentation.

We want to;

• Make the access token configurable from the settings.json file
• Have the token accessed and used within the src/ldf-client-ui.js file line 117

While we already have the option to login with a Solid WebID via the settings, it would be useful to also have an entry in the datasources list.

To quote @pmcb55:

So I was just thinking, could it also be added as an option in the 'Choose datasources:' dropdown menu (just visually, so instead of the current text (when you click on that dropdown) of 'Select a preset datasource, or type custom URL', it becomes 'Select a preset datasource, type custom URL, or log into a Solid Pod', and if you select a 'Solid Pod' option from that dropdown, the UI for 'Solid authentication:' appears.

Dependabot doesn't seem to be automatically bumping to the latest Comunica query engine version anymore.

Just like in LinkedDataFragments/jQuery-Widget.js@5c20c56

Currently, a running execution time counter is shown on top of the query results.
For traversal cases (such as link traversal and TPF), a running count of the number of HTTP requests would also be valuable to have.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency babel-loader to v9
• Update dependency webpack-cli to v5
• Update dependency webpack-dev-server to v5
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

The devDependency webpack was updated from 4.35.3 to 4.36.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Copy of LinkedDataFragments/jQuery-Widget.js#4

we deploy a web client, generated via this module with some custom queries and settings, see this repo.

I noticed several dependabot security alerts caused by this module's dependency [email protected].
When I checked its repo, I found out it is deprecated in favour of https://github.com/TriplyDB/Yasgui.

Not sure how straightforward it is to replace yasgui-yasqe with @triply/yasgui in terms of compatibility, but it seems desirable.

I just installed via npm install -g @comunica/web-client-generator and ran

$ comunica-web-client-generator

First this logs a long list of warnings originating from Components.js in the form:

[Components.js] warn: Detected remote context lookup for 'https://linkedsoftwaredependencies.org/bundles/npm/@comunica/runner/^1.0.0/components/context.jsonld' in /Users/phivk/.nvm/versions/node/v12.20.0/lib/node_modules/@comunica/web-client-generator/config/config-default.json. This may indicate a missing or invalid dependency, or an invalid context URL.

followed by the following error:

[Components.js] error: Detected fatal error. Generated 'componentsjs-error-state.json' with more information.
ErrorResourcesContext: Could not find (valid) component types for config "urn:comunica:my" among its types, or a requireName
configTypes: https://linkedsoftwaredependencies.org/bundles/npm/@comunica/runner/Runner
config: {
  term: NamedNode { termType: 'NamedNode', value: 'urn:comunica:my' },
  properties: {
    'http://www.w3.org/2000/01/rdf-schema#seeAlso': [
      [Resource], [Resource],
      [Resource], [Resource],
      [Resource], [Resource],
      [Resource], [Resource],
      [Resource], [Resource],
      [Resource], [Resource],
      [Resource], [Resource],
      [Resource], [Resource],
      [Resource], [Resource],
      [Resource], [Resource]
    ],
    'http://www.w3.org/1999/02/22-rdf-syntax-ns#type': [ [Resource] ],
    'https://linkedsoftwaredependencies.org/bundles/npm/@comunica/runner/actor': [
      [Resource], [Resource], [Resource], [Resource], [Resource],
      [Resource], [Resource], [Resource], [Resource], [Resource],
      [Resource], [Resource], [Resource], [Resource], [Resource],
      [Resource], [Resource], [Resource], [Resource], [Resource],
      [Resource], [Resource], [Resource], [Resource], [Resource],
      [Resource], [Resource], [Resource], [Resource], [Resource],
      [Resource], [Resource], [Resource], [Resource], [Resource],
      [Resource], [Resource], [Resource], [Resource], [Resource],
      [Resource], [Resource], [Resource], [Resource], [Resource],
      [Resource], [Resource], [Resource], [Resource], [Resource],
      [Resource], [Resource], [Resource], [Resource], [Resource],
      [Resource], [Resource], [Resource], [Resource], [Resource],
      [Resource], [Resource], [Resource], [Resource], [Resource],
      [Resource], [Resource], [Resource], [Resource], [Resource],
      [Resource], [Resource], [Resource], [Resource], [Resource],
      [Resource], [Resource], [Resource], [Resource], [Resource],
      [Resource], [Resource], [Resource], [Resource], [Resource],
      [Resource], [Resource], [Resource], [Resource], [Resource],
      [Resource], [Resource], [Resource], [Resource], [Resource]
    ],
    'http://usefulinc.com/ns/doap#name': []
  }
}
    at ConfigPreprocessorComponentMapped.canHandle (/Users/phivk/.nvm/versions/node/v12.20.0/lib/node_modules/@comunica/web-client-generator/node_modules/componentsjs/lib/preprocess/ConfigPreprocessorComponent.js:37:23)
    at ConfigPreprocessorComponentMapped.canHandle (/Users/phivk/.nvm/versions/node/v12.20.0/lib/node_modules/@comunica/web-client-generator/node_modules/componentsjs/lib/preprocess/ConfigPreprocessorComponentMapped.js:28:38)
    at ConfigConstructorPool.getRawConfig (/Users/phivk/.nvm/versions/node/v12.20.0/lib/node_modules/@comunica/web-client-generator/node_modules/componentsjs/lib/construction/ConfigConstructorPool.js:68:53)
    at ConfigConstructorPool.instantiate (/Users/phivk/.nvm/versions/node/v12.20.0/lib/node_modules/@comunica/web-client-generator/node_modules/componentsjs/lib/construction/ConfigConstructorPool.js:46:34)
    at ComponentsManager.instantiate (/Users/phivk/.nvm/versions/node/v12.20.0/lib/node_modules/@comunica/web-client-generator/node_modules/componentsjs/lib/ComponentsManager.js:42:54)
    at compileConfig (/Users/phivk/.nvm/versions/node/v12.20.0/lib/node_modules/@comunica/web-client-generator/node_modules/componentsjs/lib/util/CompileUtil.js:27:53)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async /Users/phivk/.nvm/versions/node/v12.20.0/lib/node_modules/@comunica/web-client-generator/bin/generate.js:37:5

system setup:

• Node version v12.20.0
• macOS 10.15.7

Any help would be appreciated :)

Login to Solid Pods times out after 5 minutes.

This is because https://github.com/rubensworks/solid-client-authn-js/blob/e4b4737d02f656795a1bd611e632e2b357a41937/packages/browser/src/util/worker/WorkerToWindowHandler.ts#L103-L127 means that the token refresh flow to keep authenticated for longer periods does not work.

See eg http://query.linkeddatafragments.org/#transientDatasources=%2F%2Ffragments.dbpedia.org%2F2016-04%2Fen;https%3A%2F%2Fruben.verborgh.org%2Fprofile%2F&query=SELECT%20%3Fperson%20%3Fdate%0AWHERE%20%7B%0A%20%20ruben%3Ame%20dbpedia-owl%3AbirthPlace%20%3Fplace%3B%0A%20%20%20%20%20%20%20%20%20%20%20dbpedia-owl%3AbirthDate%20%20%3FdateR.%0A%20%20%3Fperson%20%20dbpedia-owl%3AbirthPlace%20%3Fplace%3B%0A%20%20%20%20%20%20%20%20%20%20%20dbpedia-owl%3AbirthDate%20%20%3Fdate.%0A%20%20FILTER(%3Fdate%20%3E%20%3FdateR)%0A%7D

In firefox, I get CORS blocked errors like on https://data.linkeddatafragments.org/viaf. (Reason: CORS request did not succeed). (both HTTP and https)

I assumed https://newbedev.com/firefox-cross-origin-request-blocked-despite-headers would solve the issue, but doing the suggested action "You can do this by visiting the blocked link once and addibng the exception." didn't help

With 6972d08 I run into this issue when trying to run yarn run dev as instructed:

klimek@KUBA-1:~/jQuery-Widget.js$ node -v
v15.2.1
klimek@KUBA-1:~/jQuery-Widget.js$ npm -v
7.0.8
klimek@KUBA-1:~/jQuery-Widget.js$ yarn install
yarn install v1.22.5
[1/4] Resolving packages...
[2/4] Fetching packages...
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
info [email protected]: The platform "linux" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "@comunica/actor-init-sparql > @comunica/[email protected]" has unmet peer dependency "@comunica/utils-datasource@^1.2.0".
warning "@comunica/actor-init-sparql > @comunica/[email protected]" has unmet peer dependency "@comunica/utils-datasource@^1.0.0".
warning " > @comunica/[email protected]" has unmet peer dependency "@comunica/bus-init@^1.0.0".
warning " > @comunica/[email protected]" has unmet peer dependency "@comunica/core@^1.0.0".
[4/4] Building fresh packages...
$ comunica-compile-config config/config-default.json > comunica-engine.js
Done in 42.30s.
klimek@KUBA-1:~/jQuery-Widget.js$ yarn run dev
yarn run v1.22.5
$ npm run prepare && webpack-dev-server --config webpack.config.js --mode development

> prepare
> comunica-compile-config config/config-default.json > comunica-engine.js

node:internal/modules/cjs/loader:922
  throw err;
  ^

Error: Cannot find module 'webpack-cli/bin/config-yargs'
Require stack:
- /home/klimek/jQuery-Widget.js/node_modules/webpack-dev-server/bin/webpack-dev-server.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:919:15)
    at Function.Module._load (node:internal/modules/cjs/loader:763:27)
    at Module.require (node:internal/modules/cjs/loader:991:19)
    at require (node:internal/modules/cjs/helpers:92:18)
    at Object.<anonymous> (/home/klimek/jQuery-Widget.js/node_modules/webpack-dev-server/bin/webpack-dev-server.js:80:1)
    at Module._compile (node:internal/modules/cjs/loader:1102:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1131:10)
    at Module.load (node:internal/modules/cjs/loader:967:32)
    at Function.Module._load (node:internal/modules/cjs/loader:807:14)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:76:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/home/klimek/jQuery-Widget.js/node_modules/webpack-dev-server/bin/webpack-dev-server.js'
  ]
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: packageRules[0]: packageRules cannot combine both matchUpdateTypes and rangeStrategy. Rule: {"matchSourceUrlPrefixes":["https://github.com/comunica/comunica"],"groupName":"Comunica monorepo packages","matchUpdateTypes":["minor","patch"],"rangeStrategy":"update-lockfile","automerge":true,"stabilityDays":0,"schedule":null,"prConcurrentLimit":0,"branchConcurrentLimit":0}

The dependency @comunica/runner was updated from 1.4.4 to 1.6.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@comunica/runner is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Many people seem to be unaware that next to selecting sources from the dropdown, you can also type in custom source URLs.

We should add some kind of visual indicator that you can actually type things in here.

Is it possible to configure the port when doing yarn run start?

Issue type:

• 🐛 Bug

Description:

In the comunica demo website one can contruct a SPARQL query and then bookmark, copy&paste .. the URL to another window/website/blog post. This browser URL does not contain the new lines in the SPARQL code. The bookmarked URL will not work without editing. E.g. a copy and pastes URL:

https://comunica.github.io/comunica-feature-link-traversal-web-clients/builds/solid-default/#datasources=https:%2F%2Fbellow2.ugent.be%2Ftest%2Fscholix%2Facademic.oup.com%2Finbox%2F&query=PREFIX as: https:%2F%2Fwww.w3.org%2Fns%2Factivitystreams#PREFIX scholix: http:%2F%2Fwww.scholix.org%2FSELECT ?subject ?pred ?objectWHERE { ?id a as:Announce ; %09%09 as:object ?x . ?x as:relationship ?pred ; as:subject ?subject ; as:object ?object .}

Environment:

Vivaldi | 5.2.2623.39 (Stable channel) (x86_64)
macOS Version 10.15.7 (Build 19H1824)

Comunica 2.1.0

Crash log:

The devDependency webpack was updated from 4.39.3 to 4.40.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

When loading the widget, if the first query selected is one with multiple datasources, only one of those datasources is selected.

When the query gets selected through the dropdown box, all the datasources appear though. But in my use case there is only 1 query so it is actually impossible to select another query... unless you refresh the page weirdly enough. When refreshing the page suddenly "select a query" box is empty (might be another bug), and the query can be selected again (in which case the missing datasources appear).

Currently, only the default Comunica SPARQL config can be loaded in the widget. We should make it easier for other configs to be loaded instead.

When switching between queries with similar names, the query text area does not update:
Replicate at http://comunica.kasperzutterman.com/

Replication steps:

• Select "Buurt in Gemeente" query
• Select "Buurt in Gemeente met @ reverse" query
  After this, the "Buurt in Gemeente" query is still showing in the GrapQL Query text area
  

the default proxy value is hardcoded as http://proxy.linkeddatafragments.org/
which leads to "mixed content" errors when trying to use it when the widget was deployed on https server (like e.g. https://query.linkeddatafragments.org/)

by using the document.location.protocol one can have this button automatically switch to a working alternative

this slightly changes the meaning of 'set default' 'set to some adapted default to be actually working in this setting' :)

am working up a PR with this suggestion

After running a SPARQL query that generates a label of this format:

I ran a GraphQL query that generates labels of this format:

Unfortunately, the labels of a previous query were still showing on the resulting map of the new query

When an error occurs during query execution (error event is called), the error message is just appended to the results box. We should make error messages really clear.

Something similar to this would be ideal:

When attempting to log in with the default Inrupt broker, an Invalid client_id error is thrown.

This is probably because we are not supplying a client id here: https://github.com/comunica/jQuery-Widget.js/blob/master/src/ldf-client-ui.js#L348-L352

Related:

• https://solid.github.io/solid-oidc/#clientids
• https://docs.inrupt.com/developer-tools/api/javascript/solid-client-authn-browser/interfaces/ILoginInputOptions.html#clientid

On initial page load of http://query.linkeddatafragments.org/#datasources=https%3A%2F%2Flinked.open.gent%2Fparking&query=SELECT%20WHERE%20%7B%0A%20%20%3Fs%20%3Fp%20%3Fo.%0A%7D%0ALIMIT%20100, I get:

Parse error on line 14:
...g/ontology/>SELECT WHERE {  ?s ?p ?o.
----------------------^

Seems like concatenation gone wrong. (I also wonder to what extent we need this concatenation, since YASGUI automatically adds prefixes.)

We should somehow display (possible in the footer) what the current loaded Comunica version is. This will be useful for debugging.

The network logs show that queries are still being executed even after you have pressed the stop button.

We seem to be calling destroy(), so it may be an issue deeper down in Comunica.

Now that we have https://github.com/comunica/actor-http-solid-auth-fetch, we could add a "login" button to the query client.

However, solid-auth-client is rather big, so we might only want to load it if "login" is actually clicked.

The interesting consequence here is that some queries will have fewer results when logged out, and more when logged in.

The dummy source with label explaining you can type in sources can be clicked on (#71), and entered as a source.

When switching query type tabs, the written query should be translated automatically (when possible).

This should always work for GraphQL -> SPARQL, but not always for SPARQL -> GraphQL.

Step 4/8 : RUN cd ${dir} && npm install --unsafe-perm
---> Running in e0c6fb523108

npm WARN notice [SECURITY] jquery has the following vulnerability: 1 high. Go here for more details: https://www.npmjs.com/advisories?search=jquery&version=2.2.4 - Run npm i npm@latest -g to upgrade your npm version, and then npm audit to get more info.
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @comunica/actor-abstract-bindings-hash@^1.9.3
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of '@comunica/actor-query-operation-distinct-hash'
npm ERR! notarget

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-10-16T13_40_43_625Z-debug.log
Removing intermediate container e0c6fb523108
The command '/bin/sh -c cd ${dir} && npm install --unsafe-perm' returned a non-zero code: 1
Build failed

When entering an url in the source field, e.g. https://dbpedia.org/sparql and select it, both the url as the source from the dropdown that matches this url get added, and can't be removed anymore afterwards by pressing the X.

http://query.linkeddatafragments.org/#datasources=https%3A%2F%2Flinked.open.gent%2Fparking&query=SELECT%20WHERE%20%7B%0A%20%20%3Fs%20%3Fp%20%3Fo.%0A%7D%0ALIMIT%20100 does not stop if you write the query yourself instead of following the link (it seems that #35 is not always triggered).

Every time we receive results containing WKT geo results, we should show them on a map.
This map should only become visible, as soon as there is at least one WKT string present in the results.

We should show this map before the raw "Query results".

Technology-wise, we can use Leaflet.js, for which its documentation explains how to visualize WKT strings.

Concretely, we should do the following:

1. Check results and find strings annotated with a WKT datatype (http://www.openlinksw.com/schemas/virtrdf#Geometry or http://www.opengis.net/ont/geosparql#wktLiteral)
2. Once at least one WKT string is found in the results, display a Leaflet map above the query results (because it's hidden by default)
3. For each incoming result (they come in in a streaming way), show it live on the map.
4. As a next step, also allow custom labels to be added to points/shapes on the map. This could be done in a similar way to Yasgui's geo plugin. For example, if the WKT string was present in a variable ?wkt, then we should look for a variable ?wktLabel; and if it exists, use that as a label for displaying this result on the map.
5. Figure out how to handle this for GraphQL-LD results instead of SPARQL results.

Query examples:

• Single point
• Points forming a shape
• Multiple results with WKT strings

Inspired by https://triply.cc/docs/yasgui#geo

Errors are displayed as part of the RDF, making the RDF invalid:
http://query.linkeddatafragments.org/#datasources=https%3A%2F%2Flinked.open.gent%2Fparking&query=CONSTRUCT%20WHERE%20%7B%0A%20%20%3Fs%20%3Fp%20%3Fo.%0A%7D%0ALIMIT%20100

Suggestion: prefix the warning with #

Currently, only TPF hypermedia sources are required. Comunica also supports other types of sources, so support for this should be implemented here as well.

Some email clients trip over them

getting this error message during running "yarn install" on my ubuntu 18.04.1 LTS
so, the installation was failed

/bin/sh: 1: comunica-compile-config: not found
error Command failed with exit code 127.

By defining the sources as something like //data.ldf.org/dataset, we could allow the widget to be run simultaneously on HTTP and HTTPS.

This tool should be useful here: https://github.com/rubensworks/relative-to-absolute-iri.js

Afterwards, we should update all of our default datasources that have distinct http/https versions.

While the query is running the counter and clock are updating, but when the map is shown these fields freeze. Only when I press Stop Execution it gets updated.

Sample Query

This problem occurs on Google Chrome, on Firefox this isn't an issue.

Since #3 comunica integrates nicely with YASQE. Is there also a possibility to integrate YASR to display the query results?

When you resize the query and/or context text area, it visually breaks the vertical layout.
This can be prevented by making the text areas only vertically resizable.

The dependency @comunica/runner was updated from 1.9.0 to 1.9.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@comunica/runner is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

It would be a nice feature if map labels could be populated with query results as shown in the image.

The HTTP requests (and requests to other source types) should be logged.

The devDependency webpack was updated from 4.36.0 to 4.36.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

webpack is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

If we now want to build a custom widget, we have to fork the repo, and make changes in the repo directly.

It would be easier if we had some kind of CLI tool in which we can pass a config and settings file, which directly outputs a static website.