pebsconsulting

Keybase proof

I hereby claim:

• I am joeltg on github.
• I am joelg (https://keybase.io/joelg) on keybase.
• I have a public key ASAT5TnVT1VjbgzrxQPWCTHhakVO_WvhLQ2fWl2pFMnUPwo

To claim this, I am signing this object:

pebsconsulting

const jsonld = require("jsonld")
const dagPB = require("ipld-dag-pb")

const dagOptions = { format: "dag-pb", hashAlg: "sha2-256" }

function parseJSON(bytes, callback) {
	const string = bytes.toString("utf8")
	let res = null,
		error = null
	try {

pebsconsulting

Technical Notes and Roadmap

Data model

Split into two stages to allow IPLD to develop further:

1. Now: JSON-LD file-based model. JSON-LD is the future of RDF and it's already popular. The simplest, most future-friendly and semantically-idiomatic model to get the Underlay started now is to publish JSON-LD files that:

• are flattened relative to one top-level context,
• address every node with either absolute or fragment-relative URIs (no blank or path-relative nodes),
• link to other nodes with the IPFS URI scheme dweb:/ipfs/Qm..., using fragments for nodes within documents: dweb:/ipfs/Qm...#node-id
• use the PROV vocabulary with named graphs to capture "first-class" provenance as JSON-LD itself
• are persisted to IPFS with the files API, and

pebsconsulting

Underlay Interfaces

Every interface implementation is a class with at least two static properties type: string[] and data: {[property: string]: string}, and (depending on the interface(s) it implements) zero or more public async functions. Every interface class will be constructed with new Class(options: {}).

Namespace

Indicates a service that manages some context-scoped concept of identity

• type: ["http://underlay.mit.edu/interface/namespace"]
• data.namespace: string
  • a static property containing the URI of the namespace indexed by the resolver
  • "http://www.wikidata.org/"

pebsconsulting

apt update
apt upgrade -y
apt install -y make git jq
wget https://dl.google.com/go/go1.11.1.linux-amd64.tar.gz
tar -C /usr/local -xzf go1.11.1.linux-amd64.tar.gz
rm go1.11.1.linux-amd64.tar.gz
echo "export PATH=\$PATH:/usr/local/go/bin:/root/go/bin" >> /etc/profile
source /etc/profile
go get -u github.com/ipfs/ipfs-update
ipfs-update install latest

pebsconsulting

Schema translations

I'm going to use the words "schema" and "ontology" interchangeably and there's nothing you can do to stop me.

There's lots of structured data out in the wild, but it's only structured internally, relative to itself. For example, IMDB will let you download CSVs of its archives, but they're in IMDB's own schema, with made-up IMDB names for all the columns. If you're consuming their data, you still need to read their interface docs and transform the data into an externally compatible format. Their data is only usable intentionally.

What we'd really love is for data to also be usable incidentally - reachable, retrievable, and interpretable from outside worlds without any human in the loop. One way to achieve this is through standardization (getting IMDB to switch all their property names to fully-qualified URIs in some standardized movie-ish ontology), but a far more practical & scalable strategy is through self-des

pebsconsulting

package loader

import (
	"io"
	"net/url"

	ipfs "github.com/ipfs/go-ipfs-api"
	"github.com/piprate/json-gold/ld"
)

pebsconsulting

if ( $post->post_parent )
{
	wp_redirect( get_permalink( $post->post_parent ), 301 );
}
else
{
	wp_redirect( site_url(), 301 ) );
}
die();

pebsconsulting

// this is now a module:
// https://github.com/WebReflection/backtick-template#es2015-backticks-for-es3-engines--


var template = require('backtick-template');

// just string
const info = 'template';
`some ${info}` === template('some ${info}', {info});

pebsconsulting

using System;
using System.IO;
using System.Net;

public static class FileDownloader
{
    private const string GOOGLE_DRIVE_DOMAIN = "drive.google.com";
    private const string GOOGLE_DRIVE_DOMAIN2 = "https://drive.google.com";

    // Normal example: FileDownloader.DownloadFileFromURLToPath( "http://example.com/file/download/link", @"C:\file.txt" );