nias3
solution overview | January 2020
background
teacher workload / burden
separation of static & dynamic
uses of data
difficulty of standardisation
syllabus alignment as a first target.
standards
establishment | reference | event
infrastructure
multi-model | lifelong/bi-temporal | cooperative
reform
progress | outcomes | agency
trust
privacy | security | integrity
physical
information
cognitive
establishment
reference
events
individual
school
system
intra-system
TRUST system | places | machines | people
empower, empower, empower
Many systems operate across both analog and digital regimes. A tree integrates a wide range of inputs as continuous functions, but if you cut down that tree, you find that it has been counting the years digitally all along.
can we do better?
You never change things by fighting the existing reality.
To change something, build a new model that makes the existing model obsolete.
R. Buckminster Fuller
establishment
reference
events
establishment
reference
events
static
dynamic
nias3
one way in
one way out
publish()
any data
automatic linking
graphQl()
automatic schema generation
graphql primer
....
an API service for data
technology / storage agnostic
successor to REST
privacy & encryption as standard
without privacy
privacy policy as data
with privacy
demo
gql
input & data
services...
alignment/classifier
lesson planner, alignment
multi-model
day-book
traversal
data as signal - load from 0
accept the dynamic
wellbeing
tasks
syllabus
observations
assessments
progress
data as signal
ephemeral processing;
play & improvise
establishment
reference
events
n3 deep dive
layout
individual
school
system
intra-system
N3 nodes can run as self-contained services on a single machine to allow inter-application interoperability
N3 nodes can be run at a school level to allow interoperability and aggregation of data for analytics
N3 nodes form a distributed network to allow sharing and interoperability across an enterprise
N3 systems can communicate across organisational boundaries to share student information between organisations and systems
n3 components
n3w
publish()
query()
contexts
crdt
streaming / syncing
data-store
n3 components
deep6
crdt
gql
context
streaming
privacy
web
all deployed in single n3w binary
deep6
publish()
file, http request, stream
query()
findById() findByValue() findByType() findByPredicate() traversalWithId() traversalWithValue()
hexastore extended with
automated linking
Hexastore: Sextuple Indexing for Semantic Web Data Management
crdt manager
version-vector map-based
ensures causal consistency of
all updates across a distributed
network
graphQL manager
Attaches to read stream of
crdt manager
creates gql-schema and
therefore data access to
data objects seen by the context.
Adds universal query info
object to access all
data through d6 methods.
context manager
Creates safe bounded areas for
data sharing.
Protected by symmetric keys and jwt tokens for access.
Applies privacy per context.
Passes data through
CRDT-layer and into
streaming engine.
Reads data from streaming layer, via CRDT into context data-store (deep6)
streaming
NATS 2.0
high-performance
clustering/syncing/scalability
distributed authn/authz
privacy
Enforces POD/PPOD
data policy controls.
Data can be redacted/replaced
dynamically or
permanently
n3w web-server
the single user binary
that wraps the whole lot
together
createContext()
publish()
query()
15Mb
20Mb in use
high performance
implications
standards
establishment | reference | event
infrastructure
multi-model | lifelong/bi-temporal | cooperative
reform
progress | outcomes | agency
trust
privacy | security | integrity
nias3 overview
By matt_farmer
nias3 overview
short nias3 overview
