Persistent storage in the browser (from last week)

there is the obvious, and there is the rest:

• domain associated with no path
• background sync
• sql and no-sql limitless assync
• ...

R may listen (thank you Richard!)

https://gist.github.com/hadley/144c406871768d0cbe66b0b810160528

Managing Concept IDs (Nicole)

Nicole, we have a specific proposal. Is started with our conversation at https://observablehq.com/@episphere/fhir and that example is now moved to https://episphere.github.io/quest/concept/frogGirl.json. Note there are some errors on the concept document, to assess how serious we are bout this ;-). The reference document for jsonld and other information exchange formalisms is the NATIONAL INFORMATION EXCHANGE MODEL, niem.github.io, an official website of the United States Government. For example, on json-ld see http://niem.github.io/json/reference/json-ld/context.

The key reference textbook for the field as a whole is http://workingontologist.org

Bringing RDF together with genome graphs, folks might want to check this out: https://github.com/jervenbolleman/spodgi

GitFlow

... an interesting derivation on last week's talk: the MonoRepo approach.

Quest

Nick's first week: https://episphere.github.io/quest

WebAssembly

... there are some surprises here: https://youtu.be/fh9WXPu0hw8.

... cool example: https://youtu.be/kZrl91SPSpc

I am not sure if we can ignore this anymore - it is coming to NPM and is being used by cloud companies such as cloudflare as an alternative to Docker. The key difference is that it runs in the browser. Lets review this together (maybe watching the 30 min video and commenting/annotating it here along the way)

...

ES6 Import/export (Nick)

Nick will lead a re-discussion of import/export. Note this is a repeat discussion of an excellent session led by Bhaumik, who already uses ES6 modules extensively in Connect. We should make it as hands-on as possible, this is one of the core bits of ES6 that is not sticking as cleanly as one might expect. Let's find out why it doesn't feel as much as "of the web" as the predecessor require. Is it just because node and the browser share the same V8 engine but are (temporarily?) diverging in code re-usability models?

___

Announcements

Steve's Genomic Cloud presentation (report back)

...