Re: [T2TRG] Composition of media types

Abhijan Bhattacharyya <abhijan.bhattacharyya@tcs.com> Sun, 18 March 2018 17:52 UTC

Return-Path: <prvs=6084f8ed5=abhijan.bhattacharyya@tcs.com>
X-Original-To: t2trg@ietfa.amsl.com
Delivered-To: t2trg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 186C31270FC for <t2trg@ietfa.amsl.com>; Sun, 18 Mar 2018 10:52:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level:
X-Spam-Status: No, score=-4.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=tcs.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Mc-idffRZpb for <t2trg@ietfa.amsl.com>; Sun, 18 Mar 2018 10:51:59 -0700 (PDT)
Received: from inkolg01.tcs.com (inkolg01.tcs.com [121.241.215.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E7A01241F5 for <t2trg@irtf.org>; Sun, 18 Mar 2018 10:51:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tcs.com; i=@tcs.com; q=dns/txt; s=default; t=1521395517; x=1552931517; h=mime-version:in-reply-to:references:subject:from:to:cc: message-id:date; bh=gP2EB9eSSeTClyugseDXFX7BO6KEKccymmxCw25rHZY=; b=edPv4RQhJM0CxWD0SHtSWxqt1D6pBMjAUCJnVSwvJMGJ12fVUOG4iVnF EWj0ROmThKnikMAadSRhA4Esf87ruQYHrzfymAjDy2LBOJIQHQKOaIIXb JQ6kEmMmaRgJHXEDHk8g4QHS76yGxL3nillpGbw9h5cZcjxup1uqEIaJQ U=;
IronPort-PHdr: 9a23:+QsAhh0F+H2px6dMsmDT+DRfVm0co7zxezQtwd8ZseMfK/ad9pjvdHbS+e9qxAeQG9mDt7Qd0qGP6/yocFdDyK7JiGoFfp1IWk1NouQttCtkPvS4D1bmJuXhdS0wEZcKflZk+3amLRodQ56mNBXdrXKo8DEdBAj0OxZrKeTpAI7SiNm82/yv95HJbAhEmDWwbalvIBmrogndq9UajIR/Iast1xXFpWdFdf5Lzm1yP1KTmBj85sa0/JF99ilbpuws+c1dX6jkZqo0VbNXAigoPGAz/83rqALMTRCT6XsGU2UZiQRHDg7Y5xznRJjxsy/6tu1g2CmGOMD9UL45VSi+46ptVRTlkzkMOSIn/27Li8xwlKNbrwynpxxj2I7ffYWZOONjcq/BYd8WQGxMVdtTWSNcGIOxd4QAAOkbM+laoYnzulsAowW9CweiA+3g1iRFiWXq0aAgyekhFR3K0BEmEtkTsHrUttL1NKIKXO2p16bIzTTDb/FM1jf79YPFbxAhruuQXbJsa8Xe1UkvGBnfjlSQqY3qJS6e2+MXvGeA7+pgVOCvhHQhqw1ruTevxt0jipXVho0P1l/E9T92wJw1JNy4UkF2esKkH4dLty2AK4R2RcYiTnhutS0nxLMGvpu7czILyJQh3xPfauaHc5SG4h75U+aROzh4iGpkeL2hmxay/1KsyurmVsm7yFpKsjZKksLWun8R0BzT79CLSvpj8Ui/xzmDzQfT6vtLIUwslarUMYUhwr0umZoXtUTPBCj2mF/5jKOOd0Ur5Pan5Pr9brn8oZ+cLYB0hwfjOaotgsyyGfk0PwoQU2SB5Oix16fv8VP3TblQgfA7lLTSvorAKsQBvKG5BhdY0oMk6xmiETiryM8YnXwbLFJdfxKHkpTpN0nOIP/mCfe/hEyhnjRzyf7DJ7PvBIjDI2TFnrnve7hz8UlSxhQvwNxC/55UC7cBL+zvWkLpqdDVDAE1Pxapz+vkEtlxyI0TVXiAD6OBNaPdq16I5uYhI+mWY48VvS7wJOI+6P7ujH85m0USfa+z0ZQMaHC3BOhmI1mDbnXwgtcOC30Kvwo+TePwk1CCTSJcZ22oU60g4TE7DZqqDZ3fSYC1nLyBwCC7E4VKZmxYFlCMC3joep6FW/cWdCKSLNVtkjseVbiuU4Uhzw2htBfmy7p7KerZ4jEXuoj429hy/ODTiRAz9T1uA8SayWGNQDI8omRdbDYsx7xypwRXzU2G2K5+y6hTHNZUz+9bU0E9L5GKnMJgDNWncwjBf9WATh6MQty6HTg6Ttsr0s4HKxJ0EdWjjBnFmSCqCqMJnreLDYYl46v0w3PqYc16ziCVh+Eak1A6T54XZiWdjall+l2WXtaRng==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2BwAACGpq5a/wQXEqxdGQEBAQEBAQEBAQEBAQcBAQEBAYQ2gRqNd497gRaBf4QTjW4UgX4jAQqEIE0Cg1Y0GAECAQEBAQEBAgGBEoI4JAGCSAEBAQQBASdFCxAFBg0BAwMBAigHJx8JCAYKAQgZAoUMqE4BAQGDAw+EboNngg6FM4FwRnWFM4MeAQEDgSdcgxSCNQONJYMHiAoJgXOEFIJliFGLIYkwiC8OEIIKcE+CMwEPCZBqbJBKAQEB
X-IPAS-Result: A2BwAACGpq5a/wQXEqxdGQEBAQEBAQEBAQEBAQcBAQEBAYQ2gRqNd497gRaBf4QTjW4UgX4jAQqEIE0Cg1Y0GAECAQEBAQEBAgGBEoI4JAGCSAEBAQQBASdFCxAFBg0BAwMBAigHJx8JCAYKAQgZAoUMqE4BAQGDAw+EboNngg6FM4FwRnWFM4MeAQEDgSdcgxSCNQONJYMHiAoJgXOEFIJliFGLIYkwiC8OEIIKcE+CMwEPCZBqbJBKAQEB
X-IronPort-AV: E=Sophos;i="5.48,326,1517855400"; d="scan'208,217";a="306908194"
MIME-Version: 1.0
Sensitivity:
Importance: High
X-Priority: 1 (High)
In-Reply-To: <5B7FA8DC-71CC-4014-BACF-407E9BCB4057@tzi.org>
References: <5B7FA8DC-71CC-4014-BACF-407E9BCB4057@tzi.org>
From: Abhijan Bhattacharyya <abhijan.bhattacharyya@tcs.com>
To: Carsten Bormann <cabo@tzi.org>
Cc: t2trg@irtf.org
Message-ID: <OFB8901DF2.62DAD823-ON65258254.00601DC8-65258254.00622122@tcs.com>
Date: Sun, 18 Mar 2018 23:21:50 +0530
X-Mailer: Lotus Domino Web Server Release 9.0.1FP8HF242 May 5, 2017
X-MIMETrack: Serialize by http on InKolM02/TCS(Release 9.0.1FP8HF242 | May 5, 2017) at 03/18/2018 23:21:50, Serialize complete at 03/18/2018 23:21:50, Itemize by http on InKolM02/TCS(Release 9.0.1FP8HF242 | May 5, 2017) at 03/18/2018 23:21:50, Serialize by Router on InKolM02/TCS(Release 9.0.1FP8HF242 | May 5, 2017) at 03/18/2018 23:21:51, Serialize complete at 03/18/2018 23:21:51
Content-Type: multipart/alternative; boundary="=_alternative 0062211F65258254_="
Archived-At: <https://mailarchive.ietf.org/arch/msg/t2trg/yZ-G4yTMKtC6wvLWI8eQiPCNFfM>
Subject: Re: [T2TRG] Composition of media types
X-BeenThere: t2trg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IRTF Thing-to-Thing Research Group <t2trg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/t2trg>, <mailto:t2trg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/t2trg/>
List-Post: <mailto:t2trg@irtf.org>
List-Help: <mailto:t2trg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/t2trg>, <mailto:t2trg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Mar 2018 17:52:02 -0000

Hi Carsten,

>Two new drafts that may be of interest to the RG:
>
>	The Series Transfer Pattern (STP)
>
>	https://tools.ietf.org/html/draft-bormann-t2trg-stp-00
>
>describes ways in which &#8220;event streams&#8221; or &#8220;time series&#8221; can be
>mapped to REST, using a small set of media types to operate on
>collections of data.

I think this draft addresses an important aspect. A standardized approach would be indeed valuable. 
A small observation on the two bullets in the "Objectives" section:
While "completeness" and "latency minimization" are two competing objectives, probably they converge in the "error concealment" aspect. As you have mentioned in the both the bullets, just when the application designer makes reliability an 'illusion', the latency minimization is taken care of. So, probably, in future, an observation can be documented on the role of end-application intelligence in terms of creating the seamless feel of truthfulness to the end-user in the context of STP.    

Another point. Just wondering whether studies like the following would be worth considering in respect to this kind of work (probably I mentioned about this to you when we met in Bangalore last year):
http://ieeexplore.ieee.org/abstract/document/8016232/  
  |
 V

"Semantic data exchange between collaborative robots in fog environment: Can CoAP be a choice?", Sounak Dey, Abhijan Bhattacharyya, Arijit Mukherjee, Global Internet of Things Summit (GIoTS), June, 2017, pp.1-6

Abstract:"The transition of Internet from human-centric exchanges to the Internet  of Things has posed several interesting challenges regarding the  communication model and data exchange pattern. The emergence of edge/fog  computing as a compute model has further highlighted the need of a  uniform model to cater to the inherent heterogeneity of participating  devices. In several domains, the devices may range from standard compute  and communication devices to gateways/switches, as well as  robots/drones and other types of autonomous entities. In scenarios like  disaster management, warehouse automation, surveillance etc. use of  robots/drones/AGVs/UAVs is steadily increasing in order to minimise  potentially hazardous human intervention. Optimality of data exchange  and further processing is a desired feature in such scenarios,  especially in outdoor disaster situations where availability of the  back-end cloud infrastructure can not be guaranteed. In this paper, we  demonstrate a real life robotic data exchange model based on Resource  Description Framework (RDF). We further perform a comparative analysis  of network performance between TCP in Robot Operating System (ROS) and  block-wise extension to Constrained Application Layer Protocol (CoAP)  for bidirectional exchange of such RDF data in a disaster situation  where robotic entities accomplish search and rescue missions in  collaboration with fog devices. The causal analysis presented in this  paper puts a stepping stone for potential future enhancement of CoAP."


Thank you,

With Best Regards
 Abhijan Bhattacharyya
 Associate Consultant
 Scientist, TCS Research
 Tata Consultancy Services
 Building 1B,Ecospace
 Plot -  IIF/12 ,New Town, Rajarhat,
 Kolkata - 700160,West Bengal
 India
 Ph:- 033 66884691
 Cell:- +919830468972
 Mailto: abhijan.bhattacharyya@tcs.com
 Website: http://www.tcs.com
 ____________________________________________
 Experience certainty.	IT Services
 			Business Solutions
 			Consulting
 ____________________________________________
 

-----"T2TRG" <t2trg-bounces@irtf.org> wrote: -----

>To: t2trg@irtf.org
>From: Carsten Bormann 
>Sent by: "T2TRG" 
>Date: 03/18/2018 09:01PM
>Subject: [T2TRG] Composition of media types
>
>Two new drafts that may be of interest to the RG:
>
>	The Series Transfer Pattern (STP)
>
>	https://tools.ietf.org/html/draft-bormann-t2trg-stp-00
>
>describes ways in which &#8220;event streams&#8221; or &#8220;time series&#8221; can be
>mapped to REST, using a small set of media types to operate on
>collections of data.
>
>	The application/maybe media type
>
>	https://tools.ietf.org/html/draft-bormann-core-maybe-00
>
>describes a media type that works like the Haskell &#8220;Maybe&#8221;
>construction [1]:
>An object of another media type is either there or (not yet, no
>longer) there.
>(This was motivated by the &#8220;Pending&#8221; discussion, and the idea of
>course came from Klaus, while all breakage is mine.)
>
>The underlying theme is that we can build media types that support
>specific interaction patterns out of others, with very little
>overhead of doing so.
>
>Grüße, Carsten
>
>[1]: https://wiki.haskell.org/Maybe
>
>_______________________________________________
>T2TRG mailing list
>T2TRG@irtf.org
>https://www.irtf.org/mailman/listinfo/t2trg
>
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you