Re: WoT-OIC collaboration

> On 12 Nov 2015, at 23:44, Daniel Park <soohong.park@samsung.com> wrote:
> 
> Thanks Dave and Joerg, 
>  
> Please see my response inline;
Likewise.
> ------- Original Message -------
> Sender : Dave Raggett<dsr@w3.org <mailto:dsr@w3.org>>
> Date : 2015-11-11 20:32 (GMT+09:00)
> Title : Re: WoT-OIC collaboration
>  
> Hi Daniel,
> 
> We’re setting up a Communications task force for the W3C Web of Things Interest Group to help with liaisons, and we should be able to get you some draft text for a collaboration soon.
>  
> (Daniel), yes, please let me know and as I said we have *Liaison Task Group* within OIC and they can work with me for this topic.

I am swamped with work right now, but we will get there. I am copying my colleague Yingying Chen who  will lead the communications and collaboration task force. Note that we decided to change the name to better fit its mission. 

> Whilst we had a presentation on OIC a few months back at our Sunnyvale face to face, I think it would be valuable to invite an OIC representative to present the core approach at an upcoming IG teleconference.  In particular, I am thinking about the Thing description task force which would be interested to hear about the resource model for OIC, and the APIs and Protocols task force which would be interested in the messaging scheme and its bindings to HTTP and CoAP. If that is okay with you, I will introduce you to the corresponding leads for the two task forces.
>  
> (Daniel) Yes, we are aiming for the same direction, and I look forward to collaborating with your relevant leaders.

I am copying the respective task force leads: Sebastian chairs the Thing Description task force and Johannes chairs the APIs and Protocols Binding task force. You should be able to work with them to identify suitable timeslots for OIC presentations.

> On looking at the recently released OIC specification, it looks like OIC’s approach would fit nicely within the broader scope of the Web of Things.  The Web of Things is innovative in separating the application model of things from the transfer and transport layers. This enables servers to select the protocols and communication patterns best suited to the context, e.g. pull, push, pub-sub and peer to peer. REST fits well into this architecture, as one of the building blocks, but the application developers are shielded from having to work at the level of REST interfaces. This allows for transparent use of REST protocols, non-REST protocols (e.g. MQTT and XMPP) and even non-IP based transports.
>  
>  
> (Daniel) so I need to talk with you to hold a joint F2F (OIC Open Source Working Group and W3C WoT, and more if needed) in early next year. F2F is very productive to come up with common results and understand each other more than before. What do you think?

Our face to face plans are listed at:

     https://www.w3.org/WoT/IG/wiki/Main_Page#Face_to_Face_Meetings

Our next face to face will be in Nice, France on 26-28th January. The April meeting is likely to be at MIT, in Cambridge MA, and the July meeting is likely to be in Beijing, China. Perhaps Joerg can talk to the suggestion of a joint meeting?

—
   Dave Raggett <dsr@w3.org <mailto:dsr@w3.org>>