SLIDE 1
If a standard falls in the forest and there is nobody there to adopt it, is it still a standard?
What We Need are Standards in the Cloud If a standard falls in the - - PowerPoint PPT Presentation
What We Need are Standards in the Cloud If a standard falls in the - - PowerPoint PPT Presentation
What We Need are Standards in the Cloud If a standard falls in the forest and there is nobody there to adopt it, is it still a standard? My name is Benjamin Black And I have no standards. Lets talk about something interesting, instead:
SLIDE 2
SLIDE 3
SLIDE 4
My name is Benjamin Black
SLIDE 5
And I have no standards.
SLIDE 6
Let’s talk about something interesting, instead:
SLIDE 7
Technology adoption.
SLIDE 8
Customer-centric view
SLIDE 9
Why adopt a technology?
SLIDE 10
Utility:
SLIDE 11
Does this solve my problem?
SLIDE 12
Interoperability:
SLIDE 13
Can I combine vendors+products to solve my problem?
SLIDE 14
Independence:
SLIDE 15
Can I be totally free of vendor lock-in?
SLIDE 16
Utility Interoperability Independence
SLIDE 17
These are not equal.
SLIDE 18
A hierarchy of needs.
SLIDE 19
Utility
Interoperability
Independence
SLIDE 20
Some problems need not go past UTILITY.
SLIDE 21
e.g., SQL (in reality)
SLIDE 22
Some problems can’t achieve UTILITY without INTEROP.
SLIDE 23
e.g., TCP/IP
SLIDE 24
The cycle:
SLIDE 25
1] Disruption.
SLIDE 26
MASSIVE UTILITY
SLIDE 27
(and a lot of imperfection)
SLIDE 28
Rapid adoption
(by definition)
SLIDE 29
2] Competition.
SLIDE 30
EXPLORATION
SLIDE 31
Endless variety
SLIDE 32
Goal: Discovery
SLIDE 33
Not just of solutions.
SLIDE 34
But of the complete problem.
SLIDE 35
Many ‘standards’
SLIDE 36
(meaning no standard)
SLIDE 37
The seeds of interop are sown.
SLIDE 38
We are currently in this stage.
SLIDE 39
3] Maturation.
SLIDE 40
FORMALIZATION
SLIDE 41
Our itch having been scratched, we turn to less pressing matters.
SLIDE 42
Independence
SLIDE 43
Successful standards formalize what is already true.
SLIDE 44
Standards are side-efgects
SLIDE 45
- f successful technology.
SLIDE 46
There are no successful standards absent successful implementations.
SLIDE 47
All successful standards are de facto standards.
SLIDE 48
TANSTAAFL
SLIDE 49
Rate of Innovation Degree of Standardization
Utility Interoperability Independence
SLIDE 50
(the innovation moves elsewhere)
SLIDE 51
Standardize too soon, and you lock to the wrong thing.
SLIDE 52
Unclear that it is even possible to standardize ‘too late’.
SLIDE 53
We have missed an important question:
SLIDE 54
What do we even mean by ‘standard’?
SLIDE 55
Standard Standard specification Standard committee
SLIDE 56
Standard:
SLIDE 57
What everybody uses.
SLIDE 58
Utility + Disruption Standard
SLIDE 59
Standard specification:
SLIDE 60
What someone hopes you’ll use.
SLIDE 61
Interoperability Standard specification
SLIDE 62
Standard committees:
SLIDE 63
The legislative branch.
SLIDE 64
Independence Standard committee
SLIDE 65
Concerned with:
SLIDE 66
Licensing Patent grants Open process Interoperable implementations Open source etc.
SLIDE 67
Special bonuses:
SLIDE 68
Politiks Permanent seats Preferential votes Secret handshakes etc.
SLIDE 69
If you don’t achieve UTILITY...
SLIDE 70
Customers won’t bother.
SLIDE 71
They want their problems solved.
SLIDE 72
Standard committees don’t build.
SLIDE 73
We can only discover the right standards by
building and exploring.
SLIDE 74
To discover the right standards, we must
eschew standards.
SLIDE 75
Go do.