►
From YouTube: Adaptive Cards developer community call-January 2020
Description
This month's agenda included:
-A look at the Roadmap: https://aka.ms/ACRoadmap
-We’ve been blogging more: https://adaptivecards.io/blog
-DEMO: Schema-Driven Adaptive Cards
For more information, visit https://adaptivecards.io
A
A
Why
the
heck
am
I
wearing
suspenders
and
all
sorts
of
things
I'm
in
the
Microsoft
vein
Coover
office,
where
they
run
a
really
cool
internship
program
up
here
and
we're
getting
five
interns
for
adaptive
cards,
so
we're
kicking
it
off
and
we're
doing
a
hackathon
up
here
in
Canada
called
lumber
hacks,
so
everyone's
wearing
suspenders
and
dressing
like
like
Lumberjacks,
and
it's
actually
when
I
pretty
fun
time
got
a
giant
surface
screen
with
just
a
bonfire.
So
it's
like
the
most
expensive,
fake
fire
I've
ever
seen,
so
so.
A
A
These
calls
I
can't
thank
Dane
enough
for
setting
them
off
they're,
just
a
cool
way
for
me
to
interact
with
everybody
in
a
kind
of
low
stress
environment
like
let's
just
share
stuff
and
have
a
conversation,
so
they
might
come
in
we'll
see
if
they
do
I'm
trying
to
make
myself
available
and
right
by
the
lot
of
you.
So
with
that
said
thanks
for
joining.
If
this
is
your
first
call
or
if
it's
a
recurring,
call
or
write
here,
you're
a
repeat
guest,
we
meet
every
month
on
the
second
Thursday
of
the
month.
A
This
is
the
first
of
2020.
The
next
call
will
be
February
13th
at
nine
am
they're,
always
at
9
a.m.
Pacific
time.
You
found
this
link.
If
you
want
to
share
this
link
with
your
friends.
It's
just
a
kms,
slash
adaptive
cards,
community
call
and
you'll
meet
the
team
behind
of
cards.
I
normally
have
a
slide
in
here
about
me,
but
I'm
Matt,
hiding
derp
I'll,
probably
be
your
your
host
most
of
the
time,
but
we
like
to
bring
in
guests
as
we
can
so
with
that
said,
the
college
ended
for
today.
I'll.
A
Do
a
quick
look:
this
will
be
a
repeat
thing.
So
if
you
hear
all
the
time
you
know
you
can
zone
out
for
this
first
few
minutes,
because
I
do
always
want
to
get
people
on
the
same
page
and
make
sure
everyone
has
an
idea
of
you
know
what
we're
what
we're
looking
at.
So
there
is
some
repeat
stuff
that
will
go
through
months.
Go
on,
but
I'll
do
a
quick
look
at
the
roadmap
and
a
quick
call
out
that
we
have
been
blogging
more.
We've
got
a
couple
on
deck.
A
A
While
I'm
helping
the
teams
as
a
coach
I,
also
set
aside
some
time
and
admittedly
I'll
check
who's
on
the
call
too
so
my
boss
doesn't
know
I've
been
avoiding
email.
I'm,
not
gonna
lie
I've,
been
avoiding
email
to
get
a
hack
on
some
of
these
things.
So
I
could
build
a
demo
for
this.
So
we're
gonna
explore
this
concept
of
schema,
driven
UI,
so
schema
driven.
You
guys
have
existed
forever,
but
I
wanted
to
see
if
I
get
hacker
owned
on
this
concept
of
schema,
driven
adaptive
cards
and
that
doesn't
make
sense
to
you.
A
Hopefully
it
will
buy
by
the
end
of
the
demo
and,
like
I
said,
depending
on
time's
going,
we
might
show
some
more
stuff
like
a
feature
in
development,
around
input
evolution.
So,
okay,
let's
hop
into
it
so
designer
improvements.
I
just
want
to
call
out
this
link.
This
link
existed.
Let
me
paste
it
into
the
chat.
A
Perfect,
so
this
is
just
a
link
you
can
put
it
now.
I
actually
haven't
clicked
on
it
since
before
Christmas.
So
hopefully
it's
the
works,
but
it
is
an
evolution
of
all
the
things
we're
doing
in
the
designer
to
help
with
data
binding
and
templating.
This
problem
that,
if
you're
using
an
address
cards
you
have
likely
come
across
in
that
the
designer
has
every
feature
it's
the
latest
and
greatest
because
it's
a
web
app.
A
It's
always
on
the
latest
version,
which
means
you
can
do
things
in
adaptive
cards
that
you
might
not
be
able
to
do
in
an
app
like
teams
which
might
be
version
1.00,
where
they
still
are
on
version
1.0,
we're
actively
working
on
the
1.2
rollout,
just
a
tee
off
a
question.
If
people
are
gonna,
ask
that
how
are
things
going
with
that
rollout?
A
C
And
right
now
we're
working
on
an
extension
which
should
be
supporting
right
now
is
putting
chrome
but
will
be
shifted
to
chromium.
Ok
doing
is
anything
like
we're
doing
on
five
cards
like
any.
We
are
working
on
Expedia,
calm
yeah,
so
if
you
like,
you
can
apply
it.
So
we
understand
which
will
basically
generate
a
card
yeah.
C
C
A
C
A
C
C
A
Yeah,
that's
okay,
I'm
wearing
so
cool,
so
yeah.
Maybe
some
more
people
will
come
in.
You
know
again
you're
just
kind
of
getting
your
hands
dirty
with
the
APIs
cards,
getting
a
feel
for
it,
and
hopefully
you
know
they'll
do
a
share
out
yeah
I'm,
so
I'm
walking
through
the
the
people
on
the
call
what
we're
working
on
so
again
I,
it's
kind
of
just
saying
so
this
designer
there's
some
improvements
coming
to
help
you
deal
with
the
differences
of
versioning.
So
versioning
is
a
problem.
A
A
That
I
built
as
I
was
sitting
in
this
room
earlier,
but
I've
been
talking
to
some
of
these
interns
here
and
you
know
it's.
It's
always
interesting
as
you
line
back
to
the
beginning
and
like
try
and
explain
adaptive
cards
I'm
still,
not
that
good
at
doing
this
for
three
years
and
I
still
can't
quite
get
it
down
to
like
a
five
minute
explanation.
A
You
have
to
pull
that
JSON
out
and
then
do
something
with
it.
You
either
send
it
to
teams
you
sent
it
to
Outlook,
you
send
it
to
your
own
apps
and
then
even
those
apps
are
on
running
on
different
platforms.
So,
even
if
you
send
it
to
teams,
you
know
it
might
land
on
iOS
Android
and
their
desktop.
So
that's
effectively
the
life
cycle,
depending
on
what
you're
doing
with
it
out
of
cards,
you
may
only
care
about
this
left
half
of
the
quadrant
or,
if
you're,
a
team's
developer.
A
You
certainly
care
about
the
right
half
and
some
of
you
if
you're
rendering
cards
in
your
own
apps
you
care
about
the
full
spectrum,
so
you're
using
every
piece
of
adaptive
cards.
So
this
this
helps
me
you
know.
Picturing,
the
JSON
in
the
center
helps
me
kind
of
frame
or
scope
the
conversation
as
we're
having
people
and
it
helps
figure
out,
or
at
least
tease
out
which
part
of
this
lifecycle
are.
We
focused
on
or
really
what
part
am
I
am
I
talking
about.
A
So
with
that
said,
the
the
demo
I'm
going
to
build
is
really
on
this
left
side
and
and
that's
actually,
what
a
lot
of
the
interns
are
working
on
as
this
concept
of
oK
you've
built
this
JSON
and
now
you're,
sending
it
to
an
app
and
that's
great
and
that
all
works.
But
you
had
to
build
that
JSON
the
template
service,
as
we've
talked
about
a
little
bit
and
I'll,
do
a
quick
recap.
A
A
Do
it
and
the
template
service
is
helping
with
that,
and
in
that
vein,
we've
also
I
started
to
explore
this
concept
of
schema,
driven
adaptive
cards
and
so
again
the
whole
hope
on
this
is
to
build
a
card
for
you
without
you
having
to
do
any
work,
the
rest
of
the
equation,
the
rest
of
this
lifecycle
all
stays
exactly
the
same.
You
got
the
JSON
you're,
sending
it
to
teams
you're,
saying
I,
like
all
of
this
stays
exactly
this
it's.
How
did
the
Jason
get
created?
Did
you
have
to
do
it?
A
Could
you
leverage
other
people's
work?
That's
really
the
part
we're
talking
about
to
really
help
people
just
really
just
get
productive
with
adaptive
cards
quickly.
If
someone
else
has
already
done
something
similar.
So
with
that
said,
let
me
switch
over
to
a
demo.
This
is
something
that
I've
been
talking
with
the
interns
as
well
as
their
they're.
Getting
you
know
started
with
software
engineering.
The
reality
is
even
with
adaptive
cards.
You
know
we
like
to
think
it's.
It's
new
and
inventive,
and.
A
Similar
in
a
lot
of
ways,
a
lot
of
the
things
we're
doing
someone's
done
before
and
thankfully
I
I
took
my
own
advice
and
and
searched
for
who
else's
is
doing
schema
and
driven
you
eyes.
So
actually,
let
me
take
a
quick
step
back
and
describe
schema
driven
you
guys
so
when
I
say
schema,
driven
UI.
This
is
a
concept.
That's
existed
in
our
industry
for
a
long
time.
It's
you've
got
a
schema
back
in
when
XML
was
king.
A
It
was
you
know,
XS,
DS
and
schemas
like
that,
but
there's
some
kind
of
schema
that
describes
your
data
and
now,
with
JSON
being
the
primary
thing,
a
lot
of
people
are
using
JSON
schema.
So
this
is,
you
can
search
for
this
I
just
searched
for
a
react.js
on
schema
form.
This
is
a
tool
that
someone
wrote
for
react
that
takes
in
the
JSON
schema.
So
this
is
saying
you
know
a
title,
a
registration
form,
so
my
registration
form.
A
On
the
right
or
it's
not
a
card,
the
form
this
generator
on
the
right
is
being
built
based
on
on
the
schema,
so
my
you
know
form
I
can
say
what
fields
are
required
again
I'm,
describing
now
the
shape
of
my
data.
This
has
nothing
to
do
with
UI.
This
is
just
describing
the
shape
of
my
data,
so
the
properties
in
this
data,
our
first
name,
which
is
a
string.
It
has
a
title
and
it
has
a
default
value
if
I
want
to
make
first
name
required.
A
So
take
this
concept
and
let's
see
if
we
can
do
the
same
thing
with
adaptive
guards,
and
that's
that's
really.
The
the
hackathons
I
was
kind
of
telling
everybody
I've
been
hacking
away
in
a
hackathon
as
well.
So
this
is
the
thing
that
I
built
up
now.
We're
gonna,
take
this
same
concept,
so
we're
gonna.
Take
this
JSON
schema
again.
Json
schema
has
nothing
to
do
with
UI.
It's
it's
just
a
standard
way
of
describing
a
schema
over
data,
so
we're
gonna.
Take
this
form.
A
We
just
built
and
I'm
gonna
head
over
to
postman
and
let
me
just
make
sure
everything's
working
before
I
unwind
it
okay,
perfect.
So
as
a
quick
refresher,
the
adaptive
card
templates
service
templating
is
a
proof-of-concept
service
that
we're
continuing
to
iterate
on.
That
makes
it
easy
for
people
to
discover,
share,
contribute
and
collaborate
on
card
templates
and
again
as
a
really
quick
refresher
on
what
the
heck
is.
A
template.
The
only
difference
between
a
template
and
a
card
is
that
a
template
has
a
template.
Has
these
curly
brace
tokens?
A
It
has
some
data
that
will
be
provided
at
runtime
and
we
have
a
preview
mode
in
the
designer
that
lets
you
preview,
this
card
template
with
some
sample
data
so
down
here.
This
is
a
design
time
experience
so
that
you
can
see
what
your
card
template
will.
Look
like.
This
is
the
card
as
you've
always
seen,
whereas
it
has
these
curly
brace
titles,
the
curly
brace.
A
That's
that's
the
dynamic
token
that
we
will
be
provided
at
runtime,
but
sample
data
gives
you
a
really
nice
design
time
experience
to
just
see
what
your
card
will
look
like
with
different
types
of
data,
so
this
we've
released
in
preview.
You
can
get
started
with
templating
I,
believe
the
URL
and
just
check
it.
A
KC,
templating
I
think.
B
A
Kms,
like
AC,
templating
and
it'll,
take
you
to
this
page
to
get
started
with
templating,
so
templating
exists,
you
can
get
started
with
it
today.
You
can
play
with
it
in
the
designer
and
it
just
helps
you
create
this
card
that
now
you
can
reuse
fill
it
with
different
data.
You
don't
have
to
put
your
content
inside
the
card,
or
do
some
other
you
know
invent
your
own
mechanism
for
for
putting
in
that
dynamic
data
in
the
card.
A
That's
templating,
the
templates
service
is
something
that
tries
to
put
all
this
together
and
provide
a
place
and
I'll
show
that
as
well.
We
have
a
github
repository
called
adaptive
card
templates.
It's
a
separate
github
repository
where
all
of
our
templates
currently
are,
and
this
is
where
the
templates
live.
It's
just
a
flat
JSON
file,
so
once
you've
created
a
template,
we
typically,
you
know
you
can
put
it
in
this.
A
You
can
put
it
in
this
get
up
repository
and
then
the
service
would
would
make
it
available
to
you
at
templates
that
adaptive
card
style
and
so
I
always
struggle
with
how
much
recap
you
want
to
give.
Hopefully,
everyone's
mostly
following
along,
if
you
haven't
seen
this
before-
but
this
is
what
I
have
here-
is
a
local
version
of
this
service
and
I've
added
a
new
method
or
endpoint
to
the
service.
That's
called
from
schema,
so
what
postman
is
doing?
A
This
is
just
a
tool
if
you're
not
familiar
with
postman,
to
do
HTTP
request,
it
makes
it
very
easy
to
HTTP
request,
and
so
what
I'm
doing
now
to
get
rather
I'm
doing
the
post
so
I'm
doing
a
post
to
this
URL.
This
is
my
local
version,
but
by
the
end
of
the
day,
by
the
end
of
the
hackathon
before
I
kick
my
suspenders
off
I
will
have
deployed
this
to
the
service.
So
you
everyone
on
the
call
will
be
able
to
to
play
with
this
and
will
iterate
it.
A
The
reason
I
really
wanted
to
show
this
very
raw
is
because
I
think
this
is
a
neat
concept
and
the
challenge
you
always
have
with
scheme
and
driven
UI
is
well
how
do
I
customize
it?
You
know
how
what
type
of
levers
do
I
have
you
generated
this
UI,
but
you
know
how
do
I
tweak
it
or
how
do
I
make
it?
Quite
quite
mine,
there's
always
the
trade-off
when
you're
generating
something.
How
do
you
still
give
that
level
of
customization
and
control?
A
So
here's
what
exists
today,
I'm
doing
an
HTTP
POST
to
this
URL
and
my
post
body
is
exactly
pasted
from
I'll
just
grab
the
exact
one
we
were
just
making.
This
react
form
my
farm,
a
simple
form
example
and
I'm
just
going
to
take
this
I'm
going
to
take
this
schema
as
it
is:
I'm
gonna
put
it
in
the
post
body,
so
I'm
going
H
to
be
posed
to
the
service
at
from
Stila
and
when
I
get
back
should
be
an
adaptive
card.
A
So
this
is
the
response,
and
I
will
just
paste
this
into
the
card
designer
and
here's
what
we
get.
So
we
get
my
form
a
form
for
editing
my
form.
It's
got
first
name,
it's
got
label,
it's
got
that
default
value
of
Chuck
and
it's
got
to
put
in
some
submit
and
cancel
buttons,
but
it
generate
a
form
for
me.
It
said:
here's
here's,
my
just
pure
schema
as
in
here's,
the
properties,
here's
the
title:
here's
the
default
and
we
generated
the
adaptive
card
for
you.
This
all
lends
itself
into
you'll
notice.
A
Some
things
are
missing
like
well.
How
does
the
required
stuff
work?
We
don't
have
the
the
asterisk
in
there
that
actually
lends
it's
nice
self
nicely
to
what
Becky
on
the
call
a
developer
on
our
team
is
actively
working
on
this
concept
of
input
evolution
and
how
can
we
really
evolve
our
input
stories
such
that
you
can
have
required
required
hints
or
whether
this
field
should
be
required
or
whether
it
should
have
some
kind
of
regular
expression
to
validate
to
really
add
the
client-side
validation
as
well
as
how
should
the
label
be
presented?
A
You
know
should,
if
it's
required,
do
you
want
to
have
little
asterisk,
or
do
you
prefer
that
you're
required
labels
are
bold
and
so
we're
starting
to
tease
apart?
You
know
what
does
it
really
mean
to
describe
the
semantics
of
collecting
data,
because
right
now,
what
you'll
see
is
this
this
input
for
for
Chuck
down
here
it
has
a
text
box
above
it
for
my
first
name
text
block.
Rather
so
this.
C
A
So
a
screen
reader
would
interpret
this
title,
but
you
you
lose
things
like
accessibility
as
well
as
this
ability
to
kind
of
reflow.
Well,
if
I'm,
on
a
really
wide
but
short
screen,
because
adaptive
cards
can
be
delivered
to
devices
or
apps
with
different
visual
characteristics.
What
if
I
want
the
label
next
to
the
input
or
as
it
gets
narrower
I
want
it
to?
A
You
know
stack
up
like
it
does,
so
we
have
no
ability
to
do
that
today
with
adaptive
cards,
because
it
just
says:
hey
here's,
my
text
block
and
here's
the
text
and
there's
really
no
correlation,
or
rather
the
input
is
there's
no
correlation
between
them.
So
I
think
this
lends
itself
nicely
to
the
things
that
Becky's
working
on
and
since
we
actually
seem
to
have,
you
know
plenty
of
time
left
over
I
might
kick
it
over
to
her
really
quickly.
A
B
B
I'm
gonna
go
ahead
and
grab
the
screen
from
you:
okay,
it's
okay,
Matt,
all
right!
So
there's
a
couple
of
things
we're
looking
at
for
inputs.
The
first
is
is
that
was
talking
about
the
semantic
association
between
labels
and
inputs,
and
this
is
you
know
this
is
a
prototype,
and
this
is
just
one
approach
that
we're
considering.
But
what
you
can
see
here
on
this
input,
I've
added
a
label
property
and
that's
being
rendered
above
here
you
can
see.
B
We've
also
marked
this
input
as
required,
and
that
adds
a
little
red
star
here
to
the
label.
Now,
there's
a
number
of
ways
we
could
represent
that
UI,
but
for
the
purposes
of
this
demo,
what
we're
doing
is
putting
a
little
red
star
there
we're
still
having
a
lot
of
discussions
around
how
that
formatting
would
take
place,
whether
there's
some
level
of
host
control
there,
whether
there's
some
level
of
card
author
input,
so
those
are
some
of
the
issues
we're
discussing
on
that.
B
You
can
also
see
we've
added
this
required
property
and
an
error
message
property.
So
if
you
were
to
go
into
this
field
and
not
fill
it
out,
it
could
tell
you:
hey
name
is
required
and
that's
that
error
message
from
here,
so
you
can
see
if
you
try
to
send
without
filling
out
your
form.
You
would
get
all
these
error
messages
that
the
card
author
has
specified
has
not
talked
about
we're
also
gonna
have
some
sort
of,
in
addition
to
required
some
sort
of
type
specific
validation.
B
Required
input
we
also
the
image,
validation,
also
lets
us
and
for
some
of
the
hints
and
requirements
that
we
have
always
had
in
our
schema,
but
that
have
not
always
been
enforced
on
all
platforms,
so
examples
for
number
inputs,
we've
always
had
minute
max
and
some
some
platforms
supported
that
and
some
didn't
as
we
call
out
in
our
spec,
but
with
the
input
validation,
we
can
use
that
validation
to
validate
those
requirements
as
well.
So
those
are
some
of
the
things
we're
looking
at
here.
B
A
Are
some
of
the
major
like
what
are
the
key
discussion
points
or
what
are
some
things
that
you
would
like
to
draw
attention
to?
If
some
people
on
this
call
you
know
input
is
such
is
orders
of
magnitude
the
most
commented
on
feature
in
product
board.
It's
got
some
58
votes,
which
is
just
crazy
compared
to
the
rest
of
our
herb.
So
there's
certainly
a
lot
of
people
who
have
inputs
input
on
inputs.
What
are
some
of
the
kind
of
things
you'd
like
to
draw
attention
to
or
help
us
get
clarity
on?
Well,.
B
I
would
say
the
first
thing
is
labels,
as
we're
mentioned
before,
and
how
those
are
formatted.
It's
you
know
we're
trying
to
tease
apart
whether
it's
important
to
hosts
to
have
say
required
input
labels
be
formatted
the
same
way,
maybe
in
other
parts
of
their
app
as
they
are
in
cars
that
they're
receiving
from
their
card
authors.
So
one
of
the
things
we're
looking
at
is
how
do
hosts
want
to
see
that
kind
of
formatting
happened?
B
Do
they
have
to
you
know,
does
it
do
they
want
to
be
able
to
choose
between
required
and
bold
versus
required,
have
a
star?
Are
they
pretty
much?
Okay
with
star
for
everybody
and
all
so
on
the
Curt
author
side?
How
much
control
do
Curt
authors
need
and
want?
There
is
sort
of
a
attention
there
between
whether
you
know
if
we
give
the
card
off
there's
full
formatting
of
their
labels
and
the
coast
wants
to
put
all
their
labels
in
bold
that
if
that
are
required,
there's
there's
attention
there.
B
So
that's
one
issue
where
we're
trying
to
kind
of
tease
things
apart.
So
if
people
have
inputs
or
strong
feelings
on
that,
that's
one
topic
also
on
when
to
do
validation.
So
in
this
sample
here
that
I
was
just
showing
you
I
was
validating,
as
as
you
tab
through
the
form.
So
every
time
you
get
something
wrong
so
to
speak.
We
pop
up
the
error
messages.
B
Another
possible
approach.
If
it'll
checkbox
here
to
check
it,
is
to
not
show
errors
until
you
actually
get
to
the
end
and
choose
send
I've,
seen
some
research
that
says
it's
better
to
to
show
the
inputs
as
you're
going,
but
there
was
also
some
concern
within
the
team,
whether
that
was
too
distracting,
and
it
would
be
better
to
hold
the
errors
till
the
end.
So
I
think
those
are
some
of
the
big
design
issues
that
we're
still
working
through.
Is
there
something
else
you
have
in
mind?
Matt
no.
A
I
think
that's
exactly
you
know
the
the
the
the
Becky
alluded
to
it,
but
the
the
debate
we're
having
is
is
a
is
an
existential
one.
That's
existed
in
all
of
adaptive
cards.
You
know
how
far
should
the
pendulum
swing
for
card
author
control
versus
host
control
when
we
originally
came
up
with
the
text
block
colors,
you
know
we
have
good
attention
warning.
We
have
six
colors,
you
know
we
were
like.
Is
that
gonna
be
enough?
Our
car
authors
gonna
have
enough.
A
Certainly
there
will
be
people
that
want
more
and
it's
you
know
how
do
you?
How
do
you
manage
that?
You
know
how
do
we
totally
properly
design
and
try
and
get
as
good
as
we
can?
You
know
that
address
that
that
that
inherent
tension
of
control
and
flexibility
and
I
think
this
is
the
biggest
one
we've
had
since
probably
the
color
debate
from
a
few
years
ago,
so
it'd
be
great.
Now
that
we
have
actual
customers
to
actually
hear
from
you.
A
Maybe
you
know
from
Cisco
on
this
call
and
your
rear
rendering
cards
in
your
own
apps
as
well
so
it'd,
be
great
for
us
to
you,
know,
make
sure
we're
talking
to
both
types
of
audiences,
try
and
understand
their
their
needs
out
of
inputs
and
and
try
and
come
up
with
a
solution
that
that
does
its
best
to
address
everyone's
needs.
So
the
comment
on
that
github
poll
request
would
be
a
fantastic
way
to
chime
in
and,
as
this
discussion
was
going
on,
so
there
was
a
question:
I
was
quickly
flipped.
A
B
A
Think
we
have
it's
ya,
know
we
have
it
and
I'll
just
do
what
some
of
the
advice
that
the
interns
were
given
is.
If
so,
don't
try
and
answer
it
on
the
spot,
just
say:
no,
we
don't
know
it
actually.
I
can't
say
that
we
thought
about
that,
but
Dennis.
If
you
are
aware,
let
me
just
send
this
link
AKMs
a.k.a
teachers.
A
This
is
I'll,
actually
just
pull
it
up
right
now,
a
kms
/,
AC
features
or
AC
roadmap
right.
This
is
a
tool
we
use
called
product
board
to
have
anyone
vote
and
submit
oh
I'm,
not
sharing
the
screen
again,
okay,
good!
He
knows
he
knows
the
board.
Well,
I'm
gonna
share
it
again
for
people
who
don't
this
is
your
best
place
to
just
submit
an
idea,
the
more
detail
you
you
can
provide.
You
know
what
would
you
like
to
do?
Ideally,
maybe
like
a
comp
or
a
screenshot.
A
Have
to
create
an
account,
you
don't
have
to
do
anything
else.
It
gives
us
a
way
to
communicate
back
with
you
for
clarification,
and
you
know
and
discussion
on
it
and
as
it's
part
of
our
planning,
it
moves
over
to
this
roadmap
tab,
where
you
can
kind
of
see
what's
launched.
What's
in
development,
what's
coming
when
I,
don't
know
why?
Oh,
the
input
stuff
occurs
all
this
stuff
back.
He
just
showed
as
an
FYI
we're
looking
at
we're,
calling
it
q2
2020.
A
You
know.
None
of
this.
Obviously
I
can't
commit
to
release
dates
or
anything
as
things
are
being
so.
This
is
this
is
our
plan,
but
it's
not
guaranteed.
The
Microsoft
build
conference
is
probably
what
you
can
expect.
You
know
it's
a
good
opportunity
for
teams
or
on
Microsoft
to
a
line
around
releases.
I
think
we've
announced
the
dates
it's
usually
late
spring,
like
April
or
May.
I
can
traverse
with
an
ounce
of
dates,
but
you
can
expect
basically
a
lot
of
these
big.
A
These
big
evolution
they're
features
like
input,
evolution,
templating,
accessibility,
we're
looking
at
responsive
UI,
all
they're,
all
really
related.
You
know
when
you
think
of
like
the
input
evolution
and
this
association
of
take
text
blocks
and
labels.
It
gives
us
a
lot
more
freedom
to
start
addressing
the
the
varying
display
characteristics
of
different
host
of
adaptive
cards
as
we
get
closer
to
a
world
where
a
single
card
can
truly
adapt
in
in
really
expressive
ways,
and
that
becomes
even
more
important
to
get
that
right
as
we
get
into
things.
A
A
Need
to
make
sure
that
generated
card
is
going
to
work
great
on
narrow
screens
wide
screens,
Microsoft
teams
outlook.
So
we
need
some
of
these
semantics
and
from
we
need
some
more
semantic
information.
We
need
things
like
responsive
UI,
so
that's
kind
of
a
high
level
where
we're
the
team's
investing
their
time
and
energy
in
2020.
A
Were
there
any
the
other
thing
I
want
to
add.
I
started
this
whole
thing
so,
as
I
was
building
out
this
that
schema
generated
code,
I
went
on
to
github
and
search
for
JSON
schema
and
I
found
this
project
I've
been
trying
to
reach
out
to
these
folks,
but
their
email
server
is
blocking
me
not
really
sure
why.
But
it's
a
fire
department
in
in
the
UK
I
believe
who
has
written
this
tool
called
card
script,
which
is
based
on
adaptive
cards.
A
It's
actually
built
on
adaptive
cards
and
they
had
written
this
I
I
forked,
her
Jack
changed
it
a
little
bit
and
basically,
that
entire
demo
that
I
showed
the
schema
driven.
You
I
was
standing
on
on
their
shoulders,
so
I
can't
give
them
a
big
enough.
Shout
out.
I
was
trying
to
reach
out
to
them
before
this
call,
but
it
was
really
cool.
Someone
wrote
this
code
from
JSON
schema.
They
call
it
card
script,
but
it's
it's
an
adaptive
card
as
you
can
it's
an
adaptive
card
with
additional
things.
A
Someone
else
has
possibly
done
this
I
didn't
think
they'd
do
it
for
adaptive
cards,
but
so
I
was
able
to
find
that
and
it
made
it
so
my
hackathon
day
yesterday
was
spend
the
fun
stuff
not
on
parsing
JSON
and
all
the
JSON
schema
kind
of
interesting
stuff,
so
that
was
really
neat
I'm
hoping
to
reach
out
to
them.
They
clearly
built
this
for
a
reason:
it'd
be
great
if
we
can
work
together
and
find
a
way
to
deliver
it,
so
that
was
really
cool
that
they
had
written
that
and
so
yeah.
A
A
A
C
What
are
you
were
gonna?
What
can
adapt
if
Christ
says
father
I?
Don't
we're
in
a
hackathon
we're
trying
to
build
a
just
extension,
so
we
can
get
all
the
cards
the
user
wants
from
the
website
he's
visiting,
but
it'd
be
like
restoration
for
the
reservation
or
buying
a
plane
ticket
cool,
so
just
try
to
collect
them
all
into
a
success,
show
where
you
can
see
them
and
possibly
share
them
in
the
future,
so
yeah.
How.
C
I
think
we
will
have
a
product
ready,
but
it's
not
gonna
be
able
to
work
with
all
the
websites.
Oh
yeah
sure
yeah,
we're
probably
gonna.
Have
some
websites
manually
coded
so
I
can
extract
the
data
from
them,
because
we
didn't
figure
out
how
we
can
just
make
a
robust
engine
in
a
way.
Yeah
I've
actually
got
the
data
from
all
the
websites.
I
know
everyone.
So.
A
Yeah
awesome
well,
yeah
I
would
offer
you
see,
but
I
think
we're
just
kind
of
wrapping
up.
So
everyone
on
the
call
please
go
to
that
length.
I
showed
a
kms,
/
AC
features
help
us
and
you
know,
look
at
the
features
we're
working
on
boat
on
them.
Tell
us
you
know
it's.
Our
teams,
prioritizing
things.
I
had
a
link
to
a
survey.
Okay,
I
do
before
QA
I.
A
A
It's
not
a
long
survey
I'm,
not
it's!
It
shouldn't
take
very
much
your
time,
hopefully,
but
it
would
be
a
great
way
to
tell
us.
You
know
how
satisfied
are
you
with
what
you're
doing
with
the
community
cause
the
good
form
to
kind
of
communicate
with
us?
It
would
be
great
if
you
could
give
us
some
feedback
on
that.
We'll
continue
using
these
as
we
dive
into
more
features
like
input,
evolution,
here's
some
links
check
out
our
ignite
session.
A
The
road
map
features
templating
I,
think
I
covered
all
that
we'll
meet
again
on
February
13th
and
with
that
I
think
we'll
take
it
to
questions
so
actually
yeah.
Why
don't
you
grab
that
seat?
If
you
want
to
hang
out
we'll
see
if
we
get
any
Q&A
questions
but
yeah,
that's
anyone
feel
free
to
unmute.
If
you'd
like
or
or
chat
and
data,
did
we
just
have
any
questions
that
you
want
me
to
look
back
on
on
the
thread
at
all
I.
C
A
Unfortunately,
SVG
is
not
a
currently
supported
feature.
It
might
work
on
some
platforms
like
I,
think
it
works
in
JavaScript
just
because
the
browser
will
interpret
an
SVG
image,
but
it
wouldn't
work
across
every
adaptive
card
endpoint.
Unfortunately,
it
is
something
we're
looking
at
I.
Think
if
you
look
in
our
feature
portal,
it
is
one
of
the
items
in
there.
I
will
say,
though,
actually
has
a
clarifying
question.
David.
A
Are
you
using
SVG's
to
draw
random
graphics,
or
are
you
looking
to
use
them
as
like
glyph
icons
like
like
typically
icons
as
with
expects,
and
while
these
hopefully
typing
yeah?
So
we
see
a
lot
of
that,
so
the
mobile
glyphs
and
icons
is
one
of
the
main
features
we
are
looking
at
here,
and
you
know
this.
This
whole
concept
there's
a
bunch
of
ways
we
can.
We
can
go
about
it.
A
lot
of
people
are
moving
to
fonts
a
standard
font
face
that
has
thousands
of
things
so
I
personally
know
across
this
website.
A
Use
font
awesome
we're
I'm
going
to
reach
out
to
these
folks.
It's
an
open
icon
pack,
I'm
gonna
reach
out
to
these
folks
and
we're
at
least
considering-
and
this
is
just
me
spitballing
right
now,
but
we
are
considering
standardizing
on
a
open
icon
pack,
because
then
it
means
now.
You
can
share
these
icons
between
between
hoes
between
apps.
So,
for
example,
if
you
want
to
have
an
email
icon,
you
go
to
fund
Ison,
awesome,
calm,
search
for
mail
and
a
whole
bunch
of
well.
A
If
it
doesn't
say
Pro,
you
can
use
it,
so
they
have
a
bunch
of
different
icons
that
you
can
represent
email
or
you
know,
shipping
and
they're
completely
free
and
they're
scalable,
infinitely
scalable
and
colorable,
but
they
are
represented
as
a
font
pack.
So
it's
it's
interesting
that
people
are
kind
of
using
fonts
to
do
these
things
now,
so
we're
seeing
SVG
go
a
little
bit
by
the
wayside,
so
we
really
start
investing
our
energy
on
seeing.
If
the
font
mechanism
world
will
work.
A
So,
okay,
so
you're
using
material
design,
icons
yeah!
So
so
it's
actively
being
investigated.
We
don't
have
more
to
share.
But
again,
if
you
do
click
on
that
feature
in
our
roadmap,
it
would
be
fantastic.
If
you
can,
you
know,
provide
some
information
like
how
you're
using
it.
If
you
say
it's
critical
for
you,
we
are
using
this
this
portal,
the
people
who
submit
ideas
to
this
we're
using
this
as
a
outreach
opportunity
as
we
do
evolve
this
feature
and
start
planning
it.
A
You
could
presumably
expect
an
email
from
someone
on
our
team.
Saying
hey.
You
know
just
like
Becky
walk
us
through
our
input,
validations
back
to
the
people
interested
in
a
feature,
we're
really
trying
to
get
active
engagement
to
make
sure
we
do
it
right,
while
it's
still
baking.
So
if
you
want
to
submit
your
thoughts
there,
that's
a
good
opportunity
for
us
to
find
you
later
so
there's
a
question:
what's
the
business
use
case
of
this
technology,
that's
a
good
question.
A
I've
had
to
talk
about
that
a
lot
here
as
I
introduce
this
technology
to
the
interns
and
I'm
working
with
right
now
and
for
Microsoft.
It's
really
reducing
costs
for
our
partner
teams
like
Outlook,
like
Microsoft
teams.
These
Microsoft
teams
that
that
we're
all
using
today
is
is
really
only
as
good
as
the
third
party
software
plugging
into
it.
Like
most
platforms
right,
there
are
extensible
platforms
and
they're
they're
enhanced
by
third
parties
integrating
with
them.
You
know
as
an
example
as
we
go
into
my
developer
channel
here,
you
know
github
as
your
DevOps.
A
It's
a
very
easy
feed
for
me
to
see
what's
going
on
in
the
development
of
the
project.
So
these
these
companies,
plug
into
teams
and
enhance
the
power
of
teams
and
adaptive
cards,
is
a
fantastic
way
for
teams
to
build
an
extensible
platform
that
they
know
will
be
safe.
They
know
it'll
be
fast,
you're,
not
running
arbitrary
code,
and
they
know
it
will
look
and
feel
like
teams
this.
This
this
card
looks
and
feels
like
teams,
because
it's
an
adaptive
card.
A
It's
not
just
a
freeform
piece
of
UI,
where
github
can
just
send
anything
they
want,
because
then
they
could
make
it
look
poorly,
which
would
make
people
think
poorly
of
teams.
Potentially.
So
really
that's
where
we
see
the
use
case
of
this
product.
You've
got
an
app
most
cases,
it's
not
the
only
use
case,
but
that
is
the
main
reason
why
we
give
it
away
for
free
because
and
it's
open
source,
because
it
saves
teams
money
and
helps
them
build.
What
they
were
would
need,
teams
and
outlook.
A
You
know
and
Cortana,
and
all
these
platforms
who
want
to
open
themselves
up
to
extensibility,
with
all
the
guarantees
that
the
content
will
be
native.
The
content
will
be
fast.
The
content
will
look
and
feel
good
and
for
those
card
authors,
the
github
and
everyone
they
can
write
this
card
once
and
and
no
it'll
look
great
on
multiple
apps.
It
saves
them
reduce
costs
for
them
as
well,
for
teams
adaptive
cards
or
in
the
messy
extensions
preview.
A
A
But
if
you
want
to
reach
out
to
me,
Alexandre
I
can
try
and
I
don't
work
on
teams,
but
I'm
pretty
sure
it
works
in
messaging
extensions.
I've
only
seen
it
work,
though
so
I
unfortunately
can't
answer
any
specific
details.
But
if
you
want
to
shoot
me,
an
email
I
can
try
not
to
melt
and
try
and
get
the
bottom
of
that.
But
I
think
it
does
work.
A
Any
other
thoughts
or
questions
I
know
there
was
one
in
here.
What
about
presents
I'm,
not
actually
sure
what
you
mean
by
presents
cooking
could
elaborate
on
that,
and
we
have
an
idea
when
action
HTP
will
be
supported
in
Microsoft
teams,
we're
using
it
out
of
cards
to
retrieve
data
and
post
that
back
to
endpoints.
It
works
great
in
Outlook.
A
That's
a
fantastic
question,
probably
to
can't
really
dive
into
it
in
this
call,
but
it's
a
definitely
a
topic.
I
think
you're
going
to
hear
from
David
Chloe's
on
this
call
right
now.
Yeah
supporting
this
is
supporting
a
scenario
of
this
want
to
do.
This
is
something
David's
actively
working
on
driving
I.
Don't
think
we
have
anything
really
to
share
yet,
but
I'm
sure
it'll
be
a
topic
of
one
of
these
calls.
So
yeah.
C
So
suffice
to
say
that
we've
heard
that
that
feedback
multiple
times
in
the
past.
We
we
do
understand
that
there
is
currently
an
incompatibility
between
the
the
to
action
models
used
by
you,
know,
outlook
and
teams,
and
we
do
want
to
solve
that
problem.
So
indeed,
in
the
hopefully
not
too
distant
future,
we
should
be
able
to
share
what
we
envision
as
a
solution
for
that
yeah.
Absolutely.
A
We
totally
totally
hear
your
pain
and
we
hope
we're
coming
up
with
an
even
better
solution
and
then
necessarily
just
the
action
ation.
Okay.
Well,
thank
you
to
you
for
joining
I'll.
Let
you
get
back
to
hacking
thanks
everyone
for
jumping
on
the
call
in
2020.
We
hope
to
see
you
next
month
and
the
call
will
be
live
on
YouTube
on
office
double
YouTube,
so
you
can
re-watch
it
or
share
with
your
friends.
I'll
write
a
blog
post,
summarizing
everything
and
we'll
see
you
all
next
month.
Thanks
a
lot
all
right.