Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
Steve Coppin and Standards at #digibury
Search
#digibury
September 13, 2012
Education
94
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Steve Coppin and Standards at #digibury
Standards: No brainer, right?
#digibury
September 13, 2012
More Decks by #digibury
See All by #digibury
Jim Ang: What we learn about technology from people living with dementia
digibury
0
210
PiPurr
digibury
0
210
A context aware app for Android
digibury
0
220
Cost-effective e-commerce with Drupal Commerce
digibury
1
180
Emulators and Simulators
digibury
0
150
Work-fu
digibury
2
390
Other Decks in Education
See All in Education
Soluciones al examen de Geografía 2026. JUNIO (Convocatoria Ordinaria)
juanmartin2026
1
11k
FA26 CLU MS Clinical Psychology New Student Orientation
jdbedics
0
170
Introduction to M&A
bvr7352
0
220
Soluciones al examen de Geografía 2026. JULIO (Convocatoria Extraordinaria)
juanmartin2026
1
20k
AIがコードを書く時代に、何を教えるのか / What Should We Teach in the Age of AI-Generated Code?
ichiroc
1
570
Geografía y fútbol. Atlanta. la megalópolis del fútbol
juanmartin2026
1
12k
遊ぶかね欲しさの犯行(ルビ:労働)です
shirayanagiryuji
0
270
An Experiment in "Cross-Cultural Exchange" as a Method for Content Creation
naoji_taniguchi_ksk_0827
0
220
医療事務養成の専門学校でのAI教育 非エンジニアの学生にAIを1年間使ってもらって、感じたこと
naochim2026
0
120
[2026前期火5] 論理学(京都大学文学部 前期 第12回)「証明を走らせる:カリー・ハワード対応」
yatabe
0
320
焦燥を平穏に変えるエンジニアのための哲学
ichimichi
7
6.9k
「答えを出す」より「わかる」をつくる
kzkmaeda
1
300
Featured
See All Featured
The Illustrated Guide to Node.js - THAT Conference 2024
reverentgeek
1
540
Evolution of real-time – Irina Nazarova, EuRuKo, 2024
irinanazarova
9
1.6k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
659
62k
VelocityConf: Rendering Performance Case Studies
addyosmani
331
25k
The innovator’s Mindset - Leading Through an Era of Exponential Change - McGill University 2025
jdejongh
PRO
1
340
[RailsConf 2023] Rails as a piece of cake
palkan
59
7k
Lightning talk: Run Django tests with GitHub Actions
sabderemane
0
260
Leveraging Curiosity to Care for An Aging Population
cassininazir
1
520
Primal Persuasion: How to Engage the Brain for Learning That Lasts
tmiket
0
490
A Tale of Four Properties
chriscoyier
163
24k
Pawsitive SEO: Lessons from My Dog (and Many Mistakes) on Thriving as a Consultant in the Age of AI
davidcarrasco
0
250
The Spectacular Lies of Maps
axbom
PRO
1
1k
Transcript
STANDARDS No brainer, right? @steve_coppin
My team • Learning and Research Systems Development • Formerly
known as Integrations • Experience with several integration projects
Why standardise? • Faster implementations • Lower costs for consumers
• Easier to maintain • More support available
Definitely not IMS LTI Contextual launch based integration for Learning
Management Systems • Led by professional standards body • Behind closed doors development
DEFINITELY NOT IMS LTI and the big bang attempt
DEFINITELY NOT IMS LTI and the insubordinate wingman
Definitely not RMAS Message based integration standard for research tools
• Led by group of academic institutions • Advised by two professional standards bodies • Behind closed doors development
DEFINITELY NOT RMAS and the two approaches
DEFINITELY NOT RMAS and the ulterior motives
How we think it should be done.. • Release little
and often • Be open and communicate • Have clear use cases
Why it still might not work.. • “Our forums are
going to be really great” • “We are going to focus on integrating with our own tools”
Contact
[email protected]
@steve_coppin