Dr Nicholas Allott OMTP Chief Technology Officer
6
© OMTP All rights reserved Slide 1 To consistently and securely open up access from web applications to device and network resident capabilities Dr Nicholas Allott OMTP Chief Technology Officer
description
To consistently and securely open up access from web applications to device and network resident capabilities. Dr Nicholas Allott OMTP Chief Technology Officer. sco scope. Web Package. Widget Package. Browser. Web runtime. Web engine. JavaScript Extension. Policy Management. - PowerPoint PPT Presentation
Transcript of Dr Nicholas Allott OMTP Chief Technology Officer
© OMTP All rights reserved Slide 1
To consistently and securely open up access from web applications to device and network resident
capabilities
Dr Nicholas Allott OMTP Chief Technology Officer
© OMTP All rights reserved Slide 2
Browser Web runtime
Secure Access
Web engine
Widget Package
Operating Systems
sco scope
Syst
em
Events
Com
ms
His
tory
Applic
ati
on
Invoke
Mess
agin
g
Galle
ry
Pers
iste
nce
Phone S
tatu
s
PIM
Loca
tion
Use
r In
tera
ctio
n
Applic
ati
on
Sett
ings
DynamicAPI
New API
JavaScript Extension JscriptErrors
Events
Cam
era
Policy
Web Package
© OMTP All rights reserved Slide 3
sco standards mapping
Browser Web runtime
Secure Access
Web engine
Syst
em
Events
Com
ms
His
tory
Applic
ati
on
Invoke
Mess
agin
g
Galle
ry
Pers
iste
nce
Phone S
tatu
s
PIM
Loca
tion
Use
r In
tera
ctio
n
Applic
ati
on
Sett
ings
DynamicAPI
New API
JavaScript Extension JscriptErrors
Events
Cam
era
Policy
Web Package
Widget Package
W3C: Security Workshop
W3C: Web Applications
OAA
W3C: Web Applications
OAA
W3C: HTML etc
OAA: Style guidelines
W3
C:
GEO
W3
C:
DC
CI
W3
C:
WebA
pps
OM
A:
WTA
I
OMA: DevMng
OM
A:
WTA
I
W3C: Web Applications
OASIS: XACML
IETF: OCSP
??
OM
A:
WTA
I
© OMTP All rights reserved Slide 4
Approach
• Rapid convergence of existing implementations
• Open source as – Mechanism of collaboration– Proof of “implementability”– Resource to encourage market adoption
• Security– User controlled– Fit for purpose– Strong enough
• Open practices – Royalty Free IPR policy
• W3C as preferred body for standardising required interfaces
© OMTP All rights reserved Slide 5
Follow up Resources• Interfaces Requirements
– http://www.omtp.org/Bondi/PublicDraft.aspx
• Architecture and Security Requirements– http://www.omtp.org/Bondi/PublicDraft.aspx
• Engage in Development – http://www.omtp.org/Bondi/RIQuestionaire.aspx
• Developer Information (TBC)– http://bondi.omtp.org
• Join– http://www.omtp.org/Membership/Join.aspx
• Contact Details– Nick Allott - [email protected]
© OMTP All rights reserved Slide 6
Background Member Companies
