Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Avoiding the need for Rosetta Stones
Search
Harish Pillay
March 18, 2009
Technology
0
34
Avoiding the need for Rosetta Stones
Presented at Open Standards Day 2009, March 18, 2009
Harish Pillay
March 18, 2009
Tweet
Share
More Decks by Harish Pillay
See All by Harish Pillay
InnerSource Summit 2024: Thoughts on AI and InnerSource
harishpillay
1
11
AI and Open Source for Kids
harishpillay
0
25
Talk on Open Source
harishpillay
1
10
Generic AI Talk
harishpillay
0
55
A (short) History of AI
harishpillay
1
200
Is AI The New DevOps
harishpillay
0
51
OSPO and Public Policy
harishpillay
0
170
What's happening in the multipolar world?
harishpillay
1
100
TraceTogether_Why_open_sourcing_matters.pdf
harishpillay
0
23
Other Decks in Technology
See All in Technology
BLADE: An Attempt to Automate Penetration Testing Using Autonomous AI Agents
bbrbbq
0
320
B2B SaaSから見た最近のC#/.NETの進化
sansantech
PRO
0
910
iOS/Androidで同じUI体験をネ イティブで作成する際に気をつ けたい落とし穴
fumiyasac0921
1
110
ExaDB-D dbaascli で出来ること
oracle4engineer
PRO
0
3.9k
リンクアンドモチベーション ソフトウェアエンジニア向け紹介資料 / Introduction to Link and Motivation for Software Engineers
lmi
4
300k
【令和最新版】AWS Direct Connectと愉快なGWたちのおさらい
minorun365
PRO
5
760
Zennのパフォーマンスモニタリングでやっていること
ryosukeigarashi
0
160
あなたの知らない Function.prototype.toString() の世界
mizdra
PRO
0
120
The Rise of LLMOps
asei
8
1.7k
DynamoDB でスロットリングが発生したとき/when_throttling_occurs_in_dynamodb_short
emiki
0
260
Why App Signing Matters for Your Android Apps - Android Bangkok Conference 2024
akexorcist
0
130
DynamoDB でスロットリングが発生したとき_大盛りver/when_throttling_occurs_in_dynamodb_long
emiki
1
440
Featured
See All Featured
Docker and Python
trallard
40
3.1k
Bash Introduction
62gerente
608
210k
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
159
15k
Teambox: Starting and Learning
jrom
133
8.8k
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
226
22k
VelocityConf: Rendering Performance Case Studies
addyosmani
325
24k
A designer walks into a library…
pauljervisheath
204
24k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
42
9.2k
Why Our Code Smells
bkeepers
PRO
334
57k
Building Flexible Design Systems
yeseniaperezcruz
327
38k
The Language of Interfaces
destraynor
154
24k
GraphQLとの向き合い方2022年版
quramy
43
13k
Transcript
ITSC, an industry partnership supported by IDA Singapore and SPRING
Singapore Avoiding the Need for Rosetta Stones Harish Pillay Red Hat Asia Pacific
[email protected]
Open Standards Day 2009 March 18, 2009
<a story of three parts>
<part 1>
<circa 3000 bc>
In the beginning ...
the invention of writing ...
on both stone and papyrus ...
helped establish the ...
Great Egyptian civilization.
They helped discover science ...
Math, philosophy, astronomy ...
Architecture and jurisprudence.
None
<end of part 1>
<part 2>
<johannes gutenberg>
<johannes gutenberg> Source wikipedia, public domain
<circa 1439 ad>
<invented the moving type and press>
<the method of dissemination of knowledge changed>
<which lead to an explosion of endeavours in scientific, medical,
mathematical, astronomical, business and trade which touched all activities of humans>
<but, there was a growing realization that knowledge was being
rediscovered, reinvented>
<end of part 2>
<part 3>
<circa 1822>
<in the Egyptian town of Rosetta>
<... a chance discovery of ...>
<a large black stone with inscriptions ...>
<that were in three ancient languages ...>
<two of which were still readable and the third wasn't
...>
<that stone, the Rosetta Stone helped decipher ...>
None
<in the beginning the invention of writing on both stone
and papyrus helped establish the great Egyptian Civilization. They helped discover science, math, philosophy, astronomy, architecture and jurisprudence>
<and today, you can just go to http://carl-fh.com/hiero/ and get
a translation>
<the hardwork has been done>
<did the world learn a lesson?>
<in a word, ...>
<YES>
<but it was quickly forgotten in the late twentieth century>
<because the software industry felt that document formats should ...>
<capture knowledge and have it stored in formats that only
the maker of the tools knew how to read – to extract revenue>
<the world felt that it was not a tenable state
of affairs and ...>
<in the early twenty first century, it was painfully obvious
that we needed a fully open, published, unencumbered document format to store the world's knowledge>
<Open Document Format was thus born as ISO 26300:2006>
<one fully documented, fully open, completely unencumbered format for the
world with room to innovate and grow>
<conclusion>
<humanity cannot afford to wait for a Rosetta Stone to
be discovered to read electronically created and stored information>
<it is GOOD that there are multiple open, published and
unencumbered document, image, audio standards>
<what is NOT GOOD are document formats that are lacking
in openness, published status and being encumbered such as the OOXML even as an ISO standard>
<longevity and fidelity of data is paramount - you would
want to have your documents, images, audio, video readable 100, 500, 10,000 years hence>
<a set of fully documented, fully open, completely unencumbered document
format for the world>
<>
<thank you>
<harish pillay,
[email protected]
>