►
From YouTube: The Baseline Protocol: July 2023 General Assembly
Description
The Baseline Protocol July 2023 General Assembly will take place on Wednesday, 5/24, at 12 PM EST, 6 PM CET and 10.30 PM IST!
The Baseline Protocol community members will cover updates from the Core Devs, Outreach Team, Technical Steering Committee, and other work groups!
We invite you to tune in, join the live audience, and share your own updates.
B
B
So
keep
that
in
mind
with
some
of
our
next
updates
and
future
gas
and
shows
that
we
there's
a
lot
of
work
group
work
going
on
in
those
meetings
that
happen
weekly.
But
in
the
grand
scheme
with
monthly
updates,
they
seem
a
little
less
Grand
when
you're
explaining
them.
But
there's
a
lot
of
heavy
lifting
that
goes
into
it.
B
So
with
that
I'll
start
with
some
Outreach
updates.
Mark
cattle
was
unable
to
join
today,
but
the
Outreach
team
has
been
kind
of
chugging,
along
mainly
focused
on
paying
attention
to
the
events
going
on
for
the
rest
of
the
year
and
which
companies
and
community
members
are
attending
and
what
type
of
Baseline
presence
is
appropriate
for
the
type
of
participation
that
we're
having
at
those
events
or
the
focus
and
whatnot.
B
B
All
of
the
Outreach
efforts
that
have
been
done
in
the
past
were
hopefully
done
so
in
a
way
where
they're
Evergreen
and
can
be
picked
up
for
anyone
looking
at
conducting
their
own
research
or
outlining
how
Baseline
can
be
used
for
a
specific
use
case
or
even
as
high
level
as
identifying
industries
that
Baseline
can
be
applied
to.
So
if
anyone
is
interested
in
any
of
the
Outreach
adjacent
activities
with
the
Baseline
protocol,
please
let
us
know,
because
there
is
lots
of
content
in
the
drive
that
can
be
used.
B
We
also
have
one
blog
coming
up
next
week
from
the
TSC,
which
may
be
mentioned
again
in
a
later
update,
but
meron
from
sap
who's
on
the
technical
steering
committee
published
a
piece
that
is
currently
called
Global
Supply
Chain
coordination
via
Baseline
protocol
and
consensus,
controlled,
State
machine.
So
it
dives
into
the
problems
that
companies
face
synchronizing
systems
of
Records
or
the
lack
of
synchronization.
B
Several
deliverables
came
out
of
that
that
are
patterns
and
diagrams
that
can
be
applied
to
various
use
cases
as
well.
So
his
blog
is
a
really
great
wrap-up
of
those
efforts
that
were
done
by
many
many
participants
from
different
companies.
So
keep
an
eye
out
for
that
one,
and
with
that
yawa
Bible
hand
over
to
you
for
some
core
Dev
updates.
C
A
C
C
It
has
been
one
of
the
bigger
of
the
milestones
which
has
been
taking
up
quite
a
bit
of
development
time
on
man
hours,
but
to
sort
of
get
a
better
understanding
of
where
this
Milestone
is
at
and
what
is
left.
A
a
GitHub
Milestone
has
been
created
inside
the
repo
and
all
of
the
issues
pertaining
to
this
Milestone
and,
what's
left,
to
be
completed
for
this
Milestone
have
been
created
and
tagged
within
this
Milford
milestone
in
the
GitHub
repo.
C
C
So
there's
a
handful
of
issues
here.
I
think
six
with
this
needs
work
tag.
So
these
means
it's
sort
of
a
shell
issue.
It's
just
giving
a
broad
overview
of
something
that
will
need
to
be
completed
so
that
someone
in
the
work
group
can
grab
it
pick.
It
up.
Add
details
to
it
and
then
put
it
in
their
name
and
get
to
work
on
it
outside
of
those
six.
C
C
Yes,
examples:
BPI
interop
here
we
go
so
within
this
file
structure,
which
has
been
pushed
I
think
since
the
last
year,
or
so
there
are
schemas
that
have
been
added,
as
well
as
some
workflow
diagram
and
a
nice
readme
here
to
kind
of
give
an
understanding
of
what
this
work
group
is
working
on
times
that
they
meet
in
case.
Anyone
would
like
to
sit
in
or
join
on
the
efforts
and
then
give
an
idea
of
the
current
use
case
in
progress.
C
C
Pertaining
again
to
that
interrupt
sort
of
space
that
we
were
just
looking
at
and
another
will
be
this
transaction
execution
infrastructure,
and
this
is
SRI
related
as
far
as
the
Milestone
form
issue,
that
this
is
being
linked
to
is
it's
just
completing
this
sort
of
transaction
execution
layout
here
that's
been
outlined
within
this
issue
686
here
and
just
to
kind
of
show
sort
of
the
workflow
of
how
these
things
work.
So
there's
the
issue
right.
C
C
C
C
E
A
D
D
All
of
that
that
says
the
prerequisite
and
once
everything
is
configured
right
all
through
Bri
one
in
terms
of
what's
there
like.
How
do
you
get
this
back
into
a
form?
You
can
use
right
to
trigger
the
protocol
message
yourself
right,
so
there's
a
postman
collection
there
and
that's
where
I
I
recommend
folks
to
start
off
with
if
you're.
If
you
want
to
work
through
this
yourself
is
go
from
the
postman
and
you'll.
Follow
these
execution
steps
you'll
get
your
access
tokens
in
order
right
and
from
there
you
can.
D
Is
explained
here
in
terms
of
what
EnV
file
you
need
to
maintain
and
even
as
far
as
this
isn't
as
like
pictured,
but
this
is
included
right
to
say
like
hey,
if
you
want
to
do
it
in
sap,
which
is
where
we've,
where
I
originally
built
this
out,
there's
that
too
right
now,
so
you
can
at
least
get
a
look
at
it.
And
cool
thing
to
know
about
this
use
case
is
where,
where
does
this
data
come
from
out
of
sap?
D
Well,
there's
this
table
called
lfbk
right
that
that
holds
the
the
vendor
bank
records
right
and
now,
if
there's
a
change
request,
it
may
come
from
a
different
place.
But
if
you
look
online
for
the
lfbk
table,
you
know
that's
where
that's,
where
you'd
find
this
data
right
for
this
given
use
case.
So-
and
this
is
a
very
simple
protocol
messaging
message-
you
know
from
from
the
sap
side
in
terms
of
how
that
works,
but
there
you
go,
there's
a
lot,
there's
a
lot
to
unpack
there.
D
I
think
most
folks,
though,
when
you're
looking
at
this,
you
would
most
likely
just
do
the
node.js
call
and
then
just
do
node
create
protocol
message,
and
it
would
run
this
run
this
code
so
check
it
out.
I
hope,
I,
hope
you
guys
do
that
and
enjoy
it
and
yeah
it's
kind
of
a
a
Gateway
into
other
things.
D
B
D
Yeah,
so
with
with
interop
in
general
right,
what
we're
working
towards
is
is
yeah
more
of
this
kind
of
Hands-On
work
of
of
you
know,
emitting
the
protocol
messages
and,
and
also
really
well
understanding
like
what's
under
the
hood
right
in
terms
of
you
know
getting
into
the
the
did
and
key
agreement.
So
there's
still
some
requirements.
Analysis
work
going
on,
but
I
think
we
we
are
just
getting
far
enough
now,
with
both
Bri
one
and
and
I
think
this
can
be
said
of
Bri
3.
D
Where
there's
you
know
more
traffic
coming
through
right,
you
know
just
getting
and
getting
the
identity
pieces
aligned
I
think
getting
the
identity
part
is
is,
is
a
key
key
task
ahead
of
us
right
now
in
terms
of
making
sure
the
credentials
work
across.
You
know
different
bpis,
so,
but
luckily
for
us,
you
know,
andreas's
Insight
on
on
digs
is
extremely
valuable
for
for
all
of
us
there.
So
that's
that's
more
of
what's
going
on
in
interrupt
there.
B
Great
thank
you.
Alrighty
I
will
take
the
technical
steering
committee
update
so
I
mentioned
we
have
our
next
blog
coming
out.
I
think
it
was
a
great
addition
to
the
TSC
responsibilities
to
require
each
member
to
publish
a
Blog
once
in
the
year.
It
brings
some
really
great
thought
leadership
and
content
behind
Baseline
and
ensures
that
we
are
continuously
bringing
content
forward
for
the
external
Community,
because,
even
if
things
aren't
glamorous
and
exciting
all
the
time,
they
still
are
moving
and
progressing,
and
the
Baseline
protocol
is
becoming
more
usable
than
ever
before.
B
Now
so
really
excited
that
we're
able
to
pump
out
those
vlogs
and
Andreas
did
just
hop
on
so
I'll
wrap
up
another
TSC
update
and
then
I'll
hand
up
over
to
him
to
to
finish
up
so
on
the
TSC,
as
mentioned
it's
summertime.
So
a
few
meetings
didn't
have
Quorum,
as
you
can
expect,
but
the
main
items
going
on
are
around
the
fundraising
needed
for
the
roadmap
items.
B
So
we
have
community
members,
TSC
members
chatting
with
different
organizations
to
find
the
best
way
to
fund
the
work,
we're
seeing
if
there's
a
potential
to
have
a
get
coin.
Grant
round
and
we're
also
reaching
out
to
different
companies
in
our
networks
to
see
if
there
are
others
with
interest
in
the
in-kind
contribution
buckets
to
have
devs
that
are
on
the
bench
or
other
Technical
and
non-technical
resources
to
contribute
to
the
efforts,
because
that
is
another
very
viable
path
forward.
To
keep
progressing
on.
B
Our
roadmap
is
similar
to
some
of
us
who
aren't
always
doing
these
efforts
for
Grant
work,
but
to
contribute
time
and
thought
behind
these
efforts
that
are
needed
for
the
roadmap.
This
year,
Andreas
we'll
hand
over
to
you
to
wrap
any
TSC
updates.
I
just
covered
the
blog
and
what
you
just
heard,
and
then
you
can
shift
into
standards
as
well,
and
we
completed
interop.
E
E
So
we'll
we'll
we'll
need
to
get
get
familiar
with
that
and
and
prepare
a
grant
request.
The
that's
a
quadratic
running
round
so
other
than
that
continuing
the
conversation
with
Oasis
to
see
if
they
can
help
us
with
with
making
connections
to
companies.
That,
unfortunately,
has
been
delayed
because
of
because
of
personal
health
issues
on
the
Oasis
side.
E
So
let
me,
then,
if
there
are
no
more
questions
on
on
the
TSC
I
can
just
quickly
flip
over.
If
someone
has
one
please,
please,
post
them
on
on
mine
will
answer
them
after
the
standards
update
so
from
from
standards
point
of
view.
Actually
we
have
five
open
PR's
that
still
need
to
be
reviewed.
The
editors
have
been,
you
know,
had
other
priorities
that
they
needed
to
worry
about.
So
I've
not
progressed
around.
E
Writing
more
testability
statements
we'll
have
to
hopefully
get
get
some
time
and
and
in
the
fall
to
wrap
that
up.
It
has
definitely
taken
longer
than
hoped
for,
but
as
I
find
time
I
will
I
will
continue
to
add
to
that.
Hopefully,
you
know
somehow
we'll
get
it
done
by
the
end
of
the
year
and
everything
worked,
but
other
priorities
have
taken
hold
here
other
than
that
there's
not
much
from
the
standards
track.
E
You
know
would
be
great
if
people
want
to
pitch
in
the
PRS
they're
open
review
them,
if
you
want
to,
if
you
want
to
grab
a
section
or
subsection
in
the
standard
Nest
at
testability
statements
and
in
the
spirit
of
of
what's
in
the
pr
is,
please
feel
free,
we're
always
happy
and
and
if
people
want
to
contribute.
So
that's
that's
on
that
front.
So,
back
to
you,
Sono.
B
E
E
The
other
interesting
thing
is
that
from
that
is
that
the
concept
of
of
dows
for
Enterprises
or
you
know
really
automated
digital
co-ops
cooperatives
is
gaining
more
and
more
traction
and
they
are
around
again
business
process,
automation
also
again
using
under
under
zero
knowledge.
So
it's
it's!
It's
a
it's
a
different.
It's
a
different
type
of
of
Baseline
pattern,
implementation,
which
is
interesting.
E
The
way
that
it
it
is
starting
to
to
emerge.
So
the
you
know.
Luckily,
the
standard
captures
those
those
that
pattern
to
the
the.
The
upshot
is
that
you
know
we
can
there.
There
are
now
different
ways
how
to
how
to
effectively
Implement
the
Baseline
pattern,
also
also
with
with
other
Technologies
to
actually
which
is
really
nice
to
to
to
see
and
that
that
concept
is
gaining
more
and
more
traction
on
the
on
the
Enterprise
side.
They're,
not
quite
there.
Yet
they're.
D
Okay,
great
updates,
I'm
so
curious.
What's
behind
the
Enterprise
architecture,
because
it's
like
I'm,
always
the
architecture,
guy
I,
I,
love
figuring
out
what
kind
of
obscure
systems
that
companies
are
running
that
need
to
to
get
to
get
on
on
baselining
and
ZK
right.
There's
always
so
many
weird
weird
things
out
there
more
mainframes
than
you
than
you
realize
out
out
in
the
world
that
are
still
running
critical
business
processes.
But
don't
have
you
know
good
synchronization
to
the
people
that
really
need
it
up
or
Downstream.