Hi Manoj
Let me extend the mail participation scope regarding extended data type definition. First of all, I wonder CBOR has a restriction of data type such as binary data from the design concept. Anyway, each Json object should be meaningful entity such as ID, name, or color which has semantic mean. Once Base64 value type is accepted as one of the data type, a representation of payload will be single fragmentation of some meaningful asset. For example, icon file data need to be serialized with multiple representations, then property of each representation could be ?fragment_iconfile? rather than ?iconfile?. This looks beyond the concept of currently defined OCF data model. BR, Uze Choi From: Manoj Verma [mailto:[email protected]] Sent: Sunday, June 12, 2016 9:16 PM To: ashok.channa at samsung.com; uzchoi at samsung.com Subject: Re: FW: RE: [cftg] RE: Re: [dev] AV streaming on Iotivity. Currently in iotivity we are using json objects which after serialized by CBOR(it's only valid for ASCII messages not binary data) send to gateway. So, when we talk about AV Streaming we need to consider or define new data type either that will be base 64 or something else, which will be compatible for both binary as well as ASCII. In case of AV Streaming we can use iotivity with mqtt as it support binary payload, similarly the gateway able to detect the type of protocol and proceed accordingly. Steaming could be arguable. However, there is no way to provide information of small icon aound 1KB when it comes to file. At least some extended data format needs to be considered as soon as possible. BR. Uze Choi --------- Original Message --------- Sender : Lofgren, Scott O <scott.o.lofgren at intel.com> Date : 2016-06-11 09:17 (GMT+9) Title : RE: [cftg] RE: Re: [dev] AV streaming on Iotivity. There are many ways of standardized streaming -- OCF should pick what they believe is optimal and refer to it - last I heard this was UPnP AV4 (which is part of OCF) and DLNA -- Scott -----Original Message----- From: cftg at openconnectivity.org [mailto:[email protected]] On Behalf Of Thiago Macieira Sent: Friday, June 10, 2016 4:58 PM To: cftg at openconnectivity.org; uzchoi at samsung.com Cc: ?? <ashok.channa at samsung.com>; Manoj Verma <manoj.kumar.mbm at gmail.com>; iotivity-dev at lists.iotivity.org Subject: Re: [cftg] RE: Re: [dev] AV streaming on Iotivity. AV streaming should be implemented using other protocols. Please use RTP/RTSP or whatever is most suitable for your device. OCF should be used to discover the device that supports streaming and to obtain the parameters of the stream. On sexta-feira, 10 de junho de 2016 23:51:07 PDT ??? wrote: > Prior to implementation, data type should be defined for this streaming. > According to OCF spec, the most similar one is the string data type > with 16 bytes length which does not map with streaming use case. Let > me include cfg mailing list. > BR, Uze Choi > > > --------- Original Message --------- > Sender : ?? <ashok.channa at samsung.com> Senior Technical > Manager/SRI-Bangalore-IoTivity/???? Date : 2016-06-11 00:19 (GMT+9) > Title : Re: [dev] AV streaming on Iotivity. > > Hello, > > Is there any default support for AV Streaming in current iotivity > stack or we need to think in that prospective? --> Currently we don't > have any AV Streaming support except block wise transfer which can be > used for comparatively bigger blocks but not for video streaming. > Proposal and contributions always welcome. > > Regards, > Ashok > ------- Original Message ------- > Sender : Manoj Verma<manoj.kumar.mbm at gmail.com> Date : Jun 10, 2016 > 19:16 (GMT+05:30) Title : [dev] AV streaming on Iotivity. > > Hello all, > > [AV Streaming] > > Video Streaming over COAP. > > Is there any default support for AV Streaming in current iotivity > stack or we need to think in that prospective? > > > Thanks and regard > > Manoj Kumar (NEC Technmologies) > > > ---------------------------------------------------------------------- > ------ > ------ Sr. Technical Manager, Software Architect. > SRI-B, IoT Division/ IoTivity, Samsung Electronics Co., Ltd. > +91-9880709710 > ---------------------------------------------------------------------- > ------ > ------ > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center <http://v70ext.samsung.net/mail/ext/v1/external/status/update?userid=uzchoi&do=bWFpbElEPTIwMTYwNjExMDIxMDQyZXBjbXMxcDQ1MmRlMzgyZWJjZmRjZmMzODRjYjAxNmY0YWE1OTEwNiZyZWNpcGllbnRBZGRyZXNzPW1hbm9qLmt1bWFyLm1ibUBnbWFpbC5jb20_> -------------- next part -------------- HTML ?????? ??????????????... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160614/c310f646/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 33527 bytes Desc: ?????? ?? ????????. URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160614/c310f646/attachment.png>
