Hi Uze Choi, A key difference is that the Protocol Plugin Manager solves the resource representation problem of devices running non-OIC protocols (MQTT for ex.) - in an OIC network of devices. Web Service Interface is intended to provide OIC devices, with a simple and consistent way to consume exisiting web services.
BR, Sanjeev ------- Original Message ------- Sender : Uze Choi<uzchoi at samsung.com> S6/Principal Engineer/IoT Solution Lab./Samsung Electronics Date : May 28, 2015 09:23 (GMT+09:00) Title : RE: [dev] Initial Discussion on Web Service Interface. Hi Sanjeev, New project looks very good movement from the IoTivity point of view. Anyway, on addition to Sakari questions, I also some queries for this project. Shortly, This looks like Web protocol bridge with plugin structure. As you may know, there is a service that is the protocol plugin manager in the primitive service project. Could you share the different point from this existing service? BR, Uze Choi -----Original Message----- From: [email protected] [mailto:iotivity-dev- bounces at lists.iotivity.org] On Behalf Of Poussa, Sakari Sent: Wednesday, May 27, 2015 9:19 PM To: as2902.b at samsung.com; iotivity-dev at lists.iotivity.org Subject: Re: [dev] Initial Discussion on Web Service Interface. Hi Sanjeev, Daniel, I am glad to see your new project proposal. The Intel web team has been thinking and prototyping something similar so I think we can help in this project in order to create something re-useable. However, before committing to the project I?d like to understand a bit more. Below are some initial questions and comments. * Use cases - it would be good to document some use cases what problems the web services solves and to whom. Once we have the use cases documented, the below questions might be more clear. * Goals: * Managing web service user and application identities: does this mean a headless (gateway) device running IoTivity stack and some applications on top of the stack? Is the purpose to bind the user identities to applications? If so, why? This sounds like security type of use case. * Enable IoTivity applications to consume web service API: In this case, is the IoTivity application running on the same device as the web service, or on a different device? Is the web service API a RESTful API? What is the functionality of the API? * Enable plugin model for web services into an IoTivity network: This I don?t quite understand. Is the plugin (like .so file) for the existing IoTivity stack to enhance the functionality to include the web service interface? * bridging messages between OIC schema and web service specific schema: This is difficult to understand wo/ knowing how the web service schema looks like. If the web service interface is a REST API why don?t we use OIC schema as one piece of it. This way apps without the IoTivity stack (like web browsers) can discover and access OIC devices on the network (i.e. OIC over HTTP) * Features * Web Service User/Application Credential Management: I am not sure if it is a good idea to start building a user authentication service as part of the IoTivity project. * A consistent interface mechanism for IoTivity apps to access web services: Again, I assume the web service is a REST API. Does the consistent API mean that you will provide a high level API library for the apps to talk to the web services. This API library is language specific so you will provide C++, Java and JavaScript? * Plugin model for adding web services support: Agin, the plugin needs more context in order to understand this better. * A template based model for OIC to webservice schema translation: What is a template? Raml? UX? We can use the wiki for documenting the opens I listed above. What is you implementation plan? Do you user node.js or something else ? Sakari From: SANJEEV BA <as2902.b at samsung.com<mailto:[email protected]>> Reply-To: "as2902.b at samsung.com<mailto:as2902.b at samsung.com>" <as2902.b at samsung.com<mailto:as2902.b at samsung.com>> Date: Tuesday, May 26, 2015 at 13:43 To: "iotivity-dev at lists.iotivity.org<mailto:iotivity- dev at lists.iotivity.org>" <iotivity-dev at lists.iotivity.org<mailto:iotivity- dev at lists.iotivity.org>> Subject: [dev] Initial Discussion on Web Service Interface. Dear All, We have created a new wiki page for this activity at https://wiki.iotivity.org/web_service_interface The initial set of goals and features we are targetting are as follows. Goals - Managing web service user and application identities - Enable IoTivity applications to consume web service API. - Enable plugin model for web services into an IoTivity network. - Mechanism for bridging messages between OIC schema and web service specific schema (Human Readable Text, CBOR, JSON, XML etc) We plan to implement the following features. - Web Service User/Application Credential Management (For ex., OAuth tokens, twitter handles and user ID) - A consistent interface mechanism for IoTivity apps to access web services. - Plugin model for adding web services support. - A template based model for OIC to webservice schema translation. The wiki page will serve as the primary source of documentation for this development activity. We welcome comments and suggestions from the community. BR Sanjeev ------- Original Message ------- Sender : Daniel Park<soohong.park at samsung.com<mailto:soohong.park at samsung.com>> S6/Principal Engineer/Open Source Group/Samsung Electronics Date : May 26, 2015 13:30 (GMT+09:00) Title : [dev] New project is approved by ISG Hi all, Based upon the IoTivity governance, ISG received a new propoject proposal as attached and reviewed it and finally approved it for our new project. I am so glad to announce the new project and look forward having further propojects proposals from the community. Pls join in the new project and contribute your valuable ideas to that. Daniel (on behalf of ISG) --- Soohong Daniel Park, Ph.D. Samsung Electronics, Software R&D Center [cid:Z5JE7EUABGFC at namo.co.kr]
