5. Mindsets
Systems Thinking Integration Facilitation
A Maker Mindset
Assume you have permission
to tinker
Make, maintain and grow
useful connections
Surface goals big & inviting
enough to motivate action
Be The Change
Interrogate perceived
boundary conditions
Identify new paradigms
supported by both sides of
double-binds
Inspire others, modeling how
to navigate through shifting
paradigms
āYes. And..ā
Augment rather than change
discrete systems
Seek connections and overlaps
that add value beyond the
immediate context
Help others avoid negation
6. Who puts xAPI solutions together?
Technology Partners āØ
Vendors, consultants, tool providers, etc.
āØ
Your Team āØ
Stakeholders, team members, customers.
7. How xAPI solutions happenā¦
ā¢ Use a tool that is built with xAPI, natively, from the ground-up
( āNativeā )
ā¢ Leverage an existing data source that is modiļ¬ed, extended or
translated into xAPI ( āModiļ¬edā )
ā¢ Build Your Own ( āBYOā )
8. Native Modiļ¬ed BYO
Technology
Partners
xAPI from
ground-up
APIs or other
data sources
that can
translate to xAPI
WhateverāØ
You Want
Your Team
Balancing
wants, needs
and
sustainability
Creating &
maintaining
middleware
Practices,
Resourcing &
Scaling
9. Native Modiļ¬ed BYO
Technology
Partners
xAPI from
ground-up
APIs or other
data sources
that can
translate to xAPI
WhateverāØ
You Want
Your Team
Balancing
wants, needs
and
sustainability
Creating &
maintaining
middleware
Practices,
Resourcing &
Scaling
10. Questions for technology partners
If thereās support for xAPI from the ground-upā¦
ā¢ What activities are designed?āØ
āØ
āØ
āØ
āØ
āØ
āØ
āØ
11. Common Needs
Social Custom mobile applications Play existing courses Create new courses
Track/report progress
Oļ¬-the-shelf applications
integration
Testing Competency management
See the learnerās journey See content usage Work activities Sensors
Simulations Recruitment Compliance activity Reporting
12. Questions for technology partners
If thereās support for xAPI from the ground-upā¦
ā¢ What activities are designed?
ā¢ How are activities tracked?āØ
āØ
āØ
āØ
āØ
āØ
14. Questions for technology partners
If thereās support for xAPI from the ground-upā¦
ā¢ What activities are designed?
ā¢ How are activities tracked?
ā¢ What data points are in each statement?āØ
āØ
āØ
āØ
16. Questions for technology partners
If thereās support for xAPI from the ground-upā¦
ā¢ What activities are designed?
ā¢ How are activities tracked?
ā¢ What data points are in each statement?
ā¢ How do I input or change endpoint credentials?āØ
āØ
17. Prompt Hack Fixed
Youāll have a prompt to input one
or multiple LRS endpoint
credentials.
As an example, while thereās a
default conļ¬guration, thereās
JavaScript or other code as an
interface that can be amended
with knowledge of how the
technology works.
The technology is in a published
or executable-only state (a .exe
ļ¬le, a .swf ļ¬le ā something
server side) that makes it diļ¬cult
if not impossible to change.
18. Questions for technology partners
If thereās support for xAPI from the ground-upā¦
ā¢ What activities are designed?
ā¢ How are activities tracked?
ā¢ What data points are in each statement?
ā¢ How do I input or change endpoint credentials?
ā¢ How does it rely on the LMS or other software applications?
19. Native Modiļ¬ed BYO
Technology
Partners
xAPI from
ground-up
APIs or other
data sources
that can
translate to xAPI
WhateverāØ
You Want
Your Team
Balancing
wants, needs
and
sustainability
Creating &
maintaining
middleware
Practices,
Resourcing &
Scaling
20. Questions for your team
If considering a tool built with xAPI from the ground-upā¦
ā¢ Is whatās baked-in going to be enough?
ā¢ Does the right data align across tools?
ā¢ If notā¦ āØ
can we support our own unbiased reporting, āØ
knowing the caveats?
21. Native Modiļ¬ed BYO
Technology
Partners
xAPI from
ground-up
APIs or other
data sources
that can
translate to
xAPI
WhateverāØ
You Want
Your Team
Balancing wants,
needs and
sustainability
Creating &
maintaining
middleware
Practices,
Resourcing &
Scaling
22. Questions for technology partners
If thereās support for APIs or other data sources that can translate to
xAPIā¦
ā¢ What APIs does the technology oļ¬er?
ā¢ Of theseā¦āØ
Can we capture the right activities?
ā¢ What data will ļ¬ll in the gaps in information we need?
23. Native Modiļ¬ed BYO
Technology
Partners
xAPI from
ground-up
APIs or other
data sources
that can
translate to xAPI
WhateverāØ
You Want
Your Team
Balancing wants,
needs and
sustainability
Creating &
maintaining
middleware
Practices,
Resourcing &
Scaling
24. Questions for your team
If considering a tool built for APIs or other data sources that can translate to xAPIā¦
ā¢ Can we get enough from this/these APIs?
ā¢ How much value will we get from this system?
ā¢ What resources will we haveā¦
ā¢ to do custom API development?
ā¢ to keep up our code with the diļ¬erent specs, ongoing?
ā¢ to build the translation layer?
25. Native Modiļ¬ed BYO
Technology
Partners
xAPI from
ground-up
APIs or other
data sources
that can
translate to xAPI
WhateverāØ
You Want
Your Team
Balancing wants,
needs and
sustainability
Creating &
maintaining
middleware
Practices,
Resourcing &
Scaling
26. Questions for technology partners
If your technology partner will build whatever you wantā¦
ā¢ What learning experience are you designing?
ā¢ What interactions are needed to support the learning experience
design?
27. Native Modiļ¬ed BYO
Technology
Partners
xAPI from
ground-up
APIs or other
data sources
that can
translate to xAPI
WhateverāØ
You Want
Your Team
Balancing wants,
needs and
sustainability
Creating &
maintaining
middleware
Practices,
Resourcing &
Scaling
28. Questions for your team
If you can build whatever you wantā¦
ā¢ What learning experience are you designing?
ā¢ What interactions are needed to support the learning experience design?
ā¢ What interactions are needed but donāt evidence or disprove the learning
experience?
ā¢ What recipes exist?
ā¢ What is the data model and information architecture it should conform with?
ā¢ What is our ability to support this at scale?
29. How do I vet technology
partners for xAPI projects?
30. When considering technology partnersā¦
ā¢ Consider the know-how and investment of those who contribute to the
actual specāØ
(example: https://github.com/adlnet/xAPI-Spec/graphs/contributors)
ā¢ Consider those who can demonstrate xAPI interoperabilityāØ
(example: http://tincanapi.com/2015/04/16/tale-three-lrss/)
ā¢ Consider those who stay current with the specāØ
(example: https://github.com/aaronesilvers/IEEE/blob/master/
2014_State_of_xAPI_Tools_Survey_Responses.csv)
ā¢ Consider those who wonāt lock you into one size ļ¬ts allāØ
(example: http://connectionsforum.com/case-studies/)
33. The Data Interoperability Standards Consortium
(Data Interoperability) is the international, nonproļ¬t organization
that will handle the operations and maintenance of xAPI into
perpetuity.
36. DISCās Focus Areas
Services Partnerships Certiļ¬cation Stewardship
ā¢ Schema to validate proļ¬les
ā¢ Recognize and document
community-of-practice
activities, normalizing
proļ¬les by domain (vs
global approaches)āØ
ā¢ Federated registry and
associated APIs, freely
available for individuals;
fee-based for products
ā¢ Relationships with
stakeholder groups
wanting to leverage xAPI in
their own specs
ā¢ Supporting interests
beyond just US DoD
ā¢ Identiļ¬es software and
hardware that conforms to
requirements of the xAPI
speciļ¬cation
ā¢ Guarantees xAPIās value
proposition
ā¢ Supports xAPIās relevancy
to market needs
ā¢ Provides resources and
vehicles to support xAPI
adoption
37. RENEWCERTIFICATION
Concept: Certiļ¬cation
APPLICATIONIMPLEMENTINDUSTRY KNOWLEDGE
Vendor is
interested in
oļ¬ering a
product or
service using
xAPI.
Vendor
makes
contact with
DISC with
request for
information.
Vendor
develops
xAPI
functionality
in their
product or
service.
Vendor
applies for
certiļ¬cation
testing of
their product
or service.
Vendor
successfully
earns a
digital badge
certifying
product
authentically.
Vendor
renews
certiļ¬cation
to keep
current with
any changes
to xAPI.
38. Workstreams
INFORMATION CERTIFICATION SPECIFICATION COMMUNICATION
Vocabulary
and Proļ¬le
Services
Index of
Certiļ¬ed
Products
Maintaining
Requirements
Third-Party
Testing
Program
Maintenance
Strategic
Evolution
Communities
of Practice
Working
Groups
2017 2017 Ongoing 2017 Ongoing Ongoing Ongoing 2017
Supporting Vendors Informing Customers Delivering Market Relevance Engaging Contributors