npm ERR! Error: No compatible version found: sparql-client-2@'github:eddieantonio/node-sparql-client'
npm ERR! Valid install targets:
npm ERR! ["0.4.0","0.4.1","0.4.2","0.5.0","0.5.1","0.6.0","0.6.1","0.6.2"]
npm ERR! at installTargetsError (/usr/share/npm/lib/cache.js:719:10)
npm ERR! at /usr/share/npm/lib/cache.js:638:10
npm ERR! at saved (/usr/share/npm/node_modules/npm-registry-client/lib/get.js:142:7)
npm ERR! at /usr/lib/nodejs/graceful-fs/polyfills.js:133:7
npm ERR! at Object.oncomplete (fs.js:107:15)
npm ERR! If you need help, you may report this log at:
npm ERR! http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR! [email protected]

npm ERR! System Linux 3.16.0-77-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /root/TripleWave
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm http 200 https://registry.npmjs.org/ps-node/-/ps-node-0.0.5.tgz
npm ERR!
npm ERR! Additional logging details can be found in:

npm-debug-log file
https://drive.google.com/open?id=1gs40PYPBRjk8u7IqjhAaLcuxTSGuepOp

WebSocket connection falls after a while if no data is transmitted.
To prevent this we should:
- increase the timeout
- create a keep alive message that is periodically streamed by triplewave

extends profiling functions with the following

step
linear

distributions

gaussian
poissonian

I get some problems with the 'let' statements, is it maybe because of node version?
Using 4.2.6

/home/jpc/git/TripleWave/app.js:15
let cache = null;
^^^

SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode

Hi,

Wikimedia is planning to decommission the socket.io based RCStream in July this year.
A new service called EventStreams is available in its place.

• https://blog.wikimedia.org/2017/03/20/eventstreams/
• https://wikitech.wikimedia.org/wiki/EventStreams
• https://phabricator.wikimedia.org/T156919

While implementing an alternative version of the SparqlDataGen I noticed that:

• some methods are can be generalised.
• the description of the endpoint from which tw retrieves the data from can be improved

I suggest to:

• add in the .property file and/or in the GeneriDataGen constructor
  -- the response format from the server (JSON-LD is quite standard but other format might be possible RDF+XML)
  -- the files for the queries that indicates the selecting template and the construct template
• abstract the following methods
  -- send next
  -- load file
• make private the following methods
  -- select indices (query file is the only exposed parameter)

Context should be configurable from either the properties file or the register endpoint

make the /start endpoint able to receive a parameter pointing to a stream URI

"path" parameter in configuration files is not evaluated in
sgraph URL, which results as "http://hostname:port/sgraph"
instead of "http://hostname:port//sgraph"

In case of updatable stores for rdf streams,
it makes senso to have a DataGen that periodically query the
source considering new data to stream out.

Currently, when delay mode is set,
a listener is waiting for connection but, since the execution pipeline is undefined,
it cannot be used.

At the moment, only start.sh works with triplewave 2.0

^

Hi,

What are the requirements to get the generated RDF outputed via a websocket? Is an Apache or Nginx required for this?

Suppose I want to transform this JSON:

{
  "id": 0,
  "user": {"name": "Joe"}
}

How can I use the name of the user in the mappings? Is something like ... rr:column "user.name" possible?

On OSX 10.10.x and with node v6.3.0 these errors may occur during the installation of TripleWave:

• While installing the dependency node-icu-charset-detector you could see ../node-icu-charset-detector.cpp:5:10: fatal error: 'unicode/ucsdet.h' file not found (tested on OSX 10.10), see here
• While installing the dependency node-iconv you could see ../node_modules/nan/nan.h:601:20: error: no type named 'GCPrologueCallback' in 'v8::Isolate'(tested on 10.10), please ignore..

Both errors do NOT block the installation of TripleWave and do NOT impact the execution in any way.

Probably we need to clean up the depedencies.