RubenVerborgh

diff --git 1/v1.0.6.css 2/v2.0.6.css
index a813751..bd0c9ab 100644
--- 1/v1.0.6.css
+++ 2/v2.0.6.css
@@ -1,27 +1,42 @@
+/**
+ * Ribbon theme for Shower HTML presentation engine
+ * shower-ribbon v2.0.6, https://github.com/shower/ribbon
+ * @copyright 2010–2016 Vadim Makeev, http://pepelsbey.net/
+ * @license MIT

RubenVerborgh

var i = 2e5, start = new Date();
void setImmediate(function next(i) {
  if (i > 0)
    setImmediate(next, i - 1);
  else
    console.log((new Date() - start) / 1000);
}, i);

RubenVerborgh

immediate = require('./lib/index');

var i = 2e7;
immediate(function next(i) {
  if (i > 0)
    immediate(next, i - 1);
}, i);

RubenVerborgh

Index: src/reader.c
===================================================================
--- src/reader.c	(revision 505)
+++ src/reader.c	(working copy)
@@ -760,14 +760,24 @@
 		return r_err(reader, SERD_ERR_BAD_SYNTAX, "unexpected `%c'\n", c);
 	}
 	Ref ref = push_node(reader, SERD_LITERAL, "", 0);
-	push_byte(reader, ref, eat_byte_safe(reader, c));
-	while ((c = peek_byte(reader)) && in_range(c, 'a', 'z')) {

RubenVerborgh

<div vocab="http://schema.org" typeof="BlogPosting" resource="https://ruben.verborgh.org/blog/2016/06/22/querying-history-with-linked-data/">


<!-- Try adding and removing the line below: -->
  <meta property="publisher" resource="https://ruben.verborgh.org/profile/#me">


  <p resource="https://ruben.verborgh.org/profile/#me" typeof="Person">
    <span property="name">Ruben Verborgh</span>

RubenVerborgh

const N3 = require('n3'),
      fs = require('fs');

const stream = fs.createReadStream('file.ttl');

var first = true;
console.log('{');
const triples = new N3.Parser().parse(stream, (error, triple) => {
  if (triple) {
    if (first)

RubenVerborgh

Dear all,

Our Semantic Web team at Ghent University – imec is looking for 2 new colleagues. Please tell your friends, colleagues, master students, etc. about these opportunities!

OUR OFFER

• a research position on Big and Transport data (https://www.iminds.be/en/about-us/jobs/jobs-overview/vacancy-for-big-andtransport-data-projects)
• a research position on reasoning (https://www.iminds.be/en/about-us/jobs/jobs-overview/vacancy-for-reasoning-related-projects)

RubenVerborgh

proxy_cache_path /mnt/tmp/cache/nginx levels=1:2 keys_zone=fragments-cache:100m max_size=20g inactive=600m;
proxy_temp_path /mnt/tmp/nginx;

upstream fragments-node {
  server 127.0.0.1:4000;
}

server {
  server_name fragments.dbpedia.org;

RubenVerborgh

curl -H "Accept: text/html" http://fragments.dbpedia.org/2016-04/en
curl -H "Accept: text/turtle" http://fragments.dbpedia.org/2016-04/en
curl -H "Accept: application/json" http://fragments.dbpedia.org/2016-04/en
curl -H "Accept: application/ld+json" http://fragments.dbpedia.org/2016-04/en
curl -H "Accept: application/n-triples" http://fragments.dbpedia.org/2016-04/en
curl -H "Accept: application/trig" http://fragments.dbpedia.org/2016-04/en
curl -H "Accept: application/n-quads" http://fragments.dbpedia.org/2016-04/en

RubenVerborgh

Best practices for self-publishing scholarly metadata

For the ESWC2017 workshop on Enabling Decentralised Scholarly Communication, I'm proposing a discussion session on with the following topic: How to best mark up scholarly articles and webpages that we publish ourselves, in order to result in maximally useful data? I aim to discuss questions such as those I presented at LDOW2017, which include the following:

• How do we prioritize what to publish as RDF?