[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ietf
Subject:    OMA IETF MIF API Workshop - Room info
From:       Hui Deng <denghui02 () gmail ! com>
Date:       2012-03-26 17:28:50
Message-ID: CANF0JMBijns_ks33Qfie55GUo2cQtENBkdjdRYmYjGAsVfxzAA () mail ! gmail ! com
[Download RAW message or body]

OMA IETF MIF API Workshop

Time: Tuesday: 18:10-20:00
Location: room 212/213

1) Program
1.1) OMA OpenCMAPI activity (Thierry Berisot, OMA)
1.2) IETF MIF API Design (Ted Lemon, IETF)
1.3) IETF API related consideration (TBD)
1.4) OMA API Program (Liliana Dinale, OMA)
1.5) Vendor's today implementation (Maybe)
1.6) Next step between IETF and OMA (Thierry, Margaret, and Hui)

2) Purpose
2.1) From IETF, this workshop would help to explain the API related topic,
and clarify what is recommended and not recommended to do and standardized,
if possible, either publish a information document or adding word into the
current MIF api draft about how to use those MIF API for Internet developer=
.
and some current practices information how today smart terminal is doing.

2.2) From OMA perspective, to socialize OMA=92s published specifications an=
d
current ongoing standards activities in the area of APIs. To make sure that
the standards landscape for APIs is coordinated and harmonized. To solicit
feedback about OMA=92s specification for Authorization4APIs, which is built
on IETF OAuth as well as OpenCMAPI.

3) Outcomes:
3.1) Future work about how to use those MIF API in an IETF information
 document or inside current MIF API documentfor Internet developers.

3.2) Outcomes OMA: Improved understanding of each others=92 activities,
 and a coordinated approach going forward

3.3) Better mutual understanding of the work of both organizations,
 and how to cooperate in the future.

[Attachment #3 (text/html)]

<p>OMA IETF MIF API Workshop<br>=A0<br>Time: Tuesday: 18:10-20:00<br>Locati=
on: room 212/213<br>=A0<br>1) Program<br>1.1) OMA OpenCMAPI activity (Thier=
ry Berisot, OMA) <br>1.2) IETF MIF API Design (Ted Lemon, IETF)<br>1.3) IET=
F API related consideration (TBD) <br>
1.4) OMA API Program (Liliana Dinale, OMA) <br>1.5) Vendor&#39;s today impl=
ementation (Maybe)<br>1.6) Next step between IETF and OMA (Thierry, Margare=
t, and Hui)<br>=A0<br>2) Purpose<br>2.1) From IETF, this workshop would hel=
p to explain the API related topic,<br>
and clarify what is recommended and not recommended to do and standardized,=
 <br>if possible, either publish a information document or adding word into=
 the <br>current MIF api draft about how to use those MIF API for Internet =
developer.<br>
and some current practices information how today smart terminal is doing. <=
br>=A0<br>2.2) From OMA perspective, to socialize OMA=92s published specifi=
cations and <br>current ongoing standards activities in the area of APIs. T=
o make sure that <br>
the standards landscape for APIs is coordinated and harmonized. To solicit =
<br>feedback about OMA=92s specification for Authorization4APIs, which is b=
uilt <br>on IETF OAuth as well as OpenCMAPI.<br>=A0<br>3) Outcomes:<br>3.1)=
 Future work about how to use those MIF API in an IETF information <br>
=A0document or inside current MIF API documentfor Internet developers.</p>
<p>3.2) Outcomes OMA: Improved understanding of each others=92 activities,<=
br>=A0and a coordinated approach going forward</p>
<p>3.3) Better mutual understanding of the work of both organizations, <br>=
=A0and how to cooperate in the future.<br></p>


[prev in list] [next in list] [prev in thread] [next in thread]