👂 🎴 🕸️
This
guide
is
organized
into
several
sections
''
each
approachable
independently
:
a
brief
introduction
to
the
core
ideas
(<
a
href
=
„
/
422
/
knot
“
>
Brief
Introduction
a
>)''
the
project
'
s
own
path
and
motivations
(<
a
href
=
„
/
427
/
knot
“
>
Path
to
Kastalia
a
>)''
how
the
system
is
built
on
the
server
side
(<
a
href
=
„
/
432
/
knot
“
>
Backend
a
>)
and
in
the
browser
(<
a
href
=
„
/
435
/
knot
“
>
Frontend
a
>)''
a
catalogue
of
available
<
a
href
=
„
/
437
/
knot
“
>
Templates
a
>''
the
vocabulary
of
<
a
href
=
„
/
438
/
knot
“
>
Predicates
a
>
that
knots
use
to
relate
to
one
another
''
and
the
free
-
form
<
a
href
=
„
/
445
/
knot
“
>
Attributes
a
>
a
knot
can
carry
.<
br
><
br
>
Start
wherever
your
curiosity
points
you
--
the
graph
''
true
to
its
own
philosophy
''
has
no
single
correct
entry
point
.
Attributes
are
the
free
-
form
''
per
-
knot
metadata
stored
in
the
attributes
hstore
column
.
A
handful
of
names
recur
often
enough
across
templates
to
be
worth
knowing
:
template
(
which
.
tt
file
should
render
this
knot
)''
public
(
whether
anonymous
visitors
may
see
it
)''
creator
and
epoch
(
who
made
it
and
when
)''
img
url
(
an
illustration
)''
ogg
url
and
presentation
timeline
(
audio
narration
and
its
synced
slide
-
navigation
events
''
used
by
mainframe
)''
and
voice
/
age
/
gender
/
motherlang
/
consent
(
speaker
metadata
for
recordings
).<
br
><
br
>
Because
attributes
is
schemaless
''
nothing
stops
a
template
from
inventing
its
own
attribute
name
for
its
own
purposes
--
these
are
simply
the
ones
already
in
wide
use
across
the
existing
templates
.
What
a
visitor
actually
sees
is
produced
entirely
by
server
-
rendered
Template
::
Toolkit
templates
--
there
is
no
separate
client
-
side
application
framework
.
This
section
covers
Template
Toolkit
'
s
role
in
Kastalia
specifically
;
the
companion
<
a
href
=
„
/
437
/
knot
“
>
Templates
a
>
section
of
this
guide
catalogues
the
individual
.
tt
files
and
what
each
one
is
for
.
Kastalia
did
not
appear
out
of
nowhere
.
This
section
gathers
the
three
threads
that
''
braided
together
''
led
to
the
system
as
it
exists
today
:
the
philosophical
commitments
that
shaped
its
design
(<
em
>
Philosophy
em
>)''
the
fictional
and
speculative
works
that
fed
its
imagination
(<
em
>
Fiction
em
>)''
and
the
plain
factual
record
of
how
the
project
actually
unfolded
over
time
(<
em
>
History
em
>).
Kastalia
Knowledge
Management
System
''
or
simply
``
Kastalia
KMS
''''
is
a
system
for
collaborative
web
-
publishing
''
data
-
management
and
archivation
of
structured
information
in
a
form
of
a
so
-
called
``
knowledge
graph
''.
<
br
><
br
>
Kastalia
'
s
knowledge
graph
(
KG
)
is
composed
of
things
-
also
called
``
knowledge
units
''
or
``
knots
``
-
and
relations
between
things
-
also
called
``
bounds
''.<
br
><
br
>
Diverse
combinations
of
``
knots
''
and
``
bounds
''
can
be
obtained
by
executing
different
kinds
of
``
templates
''''
ultimately
providing
``
views
''
which
end
up
in
the
browser
of
a
human
user
.<
br
><
br
>
To
the
one
who
understands
it
and
masters
it
''
Kastalia
KMS
is
a
strongly
generative
system
providing
theoretically
infinite
flexibility
in
both
content
structuration
as
well
as
interface
design
.
A
non
-
exhaustive
sample
of
the
templates
this
system
actually
uses
''
to
give
a
sense
of
the
range
:<
br
><
br
><
strong
>
knot
strong
>
is
the
plain
default
view
''
rendering
a
knot
'
s
content
and
its
children
as
an
ordinary
document
.<
br
><
strong
>
mainframe
strong
>
turns
a
knot
and
its
children
into
a
live
''
broadcastable
slide
deck
''
with
optional
audio
narration
''
a
classroom
-
cast
mode
''
and
cross
-
referenced
-
knot
preview
-
on
-
hover
.<
br
><
strong
>
reveal2
strong
>
is
an
older
slide
-
deck
template
built
directly
on
reveal
.
js
.<
br
><
strong
>
semester
strong
>
renders
a
whole
course
'
s
session
list
''
including
a
'
live
'
badge
for
whatever
is
currently
being
cast
.<
br
><
strong
>
play
strong
>
and
<
strong
>
read
strong
>
are
built
around
spoken
-
word
recordings
linked
via
is
uttered
as
and
illustrates
.<
br
><
strong
>
arbre
strong
>
renders
a
knot
'
s
neighbourhood
as
a
graph
diagram
.<
br
><
br
>
Separately
''
several
domains
each
define
their
own
fixed
<
em
>
canonical
em
>
template
(
console
''
treehouse
''
arena
''
atlas
''
and
so
on
)
that
every
.
knot
-
suffixed
URL
on
that
domain
uses
regardless
of
the
knot
'
s
own
template
attribute
--
see
domain
template
in
config
.
yml
.
Kastalia
'
s
backend
is
a
Perl
application
built
on
the
Dancer2
web
framework
''
storing
its
graph
in
PostgreSQL
.
This
section
describes
the
two
layers
that
matter
most
:
the
<
em
>
SQL
core
em
>
(
the
actual
table
/
enum
design
behind
knots
and
bounds
)
and
the
<
em
>
PERL
Core
em
>
(
the
routes
and
helper
functions
that
read
and
write
it
).
This
file
was
created
for
the
benefit
of
all
AIEDucators
''
teachers
''
students
''
developers
and
parents
wanting
to
use
Kastalia
Knowledge
Management
System
(
KMS
)
creation
of
their
own
knowledge
graphs
''
archives
of
more
complex
curricular
and
/
or
meta
-
curricular
structures
.
[Impressum, Datenschutz, Login] Other subprojects of udk.ai linkring: fibel.digital baumhaus.digital gardens.digital refused.science teacher.solar