MIME Type Definition Group Name: PRO WG

Slides:



Advertisements
Similar presentations
XML in the real world (2) SOAP. What is SOAP? ► SOAP stands for Simple Object Access Protocol ► SOAP is a communication protocol ► SOAP is for communication.
Advertisements

SOAP SOAP is a protocol for accessing a Web Service. SOAP stands for Simple Object Access Protocol * SOAP is a communication protocol * SOAP is for communication.
SOAP Lee Jong-uk. Introduction What is SOAP? The features of SOAP The structure of SOAP SOAP exchange message model & message Examples of SOAP.
SOAP Quang Vinh Pham Simon De Baets Université Libre de Bruxelles1.
Problem of Current Notification Group Name: ARC WG Source: Heedong Choi, LG Electronics, Meeting Date: ARC 9.0 Agenda Item: TBD.
WG 3 Progress Report at TP12 Group Name: oneM2M TP12 Source: Raymond Forbes, LM Ericsson, Meeting Date: to
WG PRO Progress Report at TP17 Group Name: oneM2M TP17 Source: Raymond Forbes, LM Ericsson, Meeting Date: to
HTTP Binding Proposals, Questions, and Examples Group Name: WG3 Source: Phillip Brown, InterDigital Meeting Date: (PRO#12.0) Agenda Item: HTTP.
Client, Server, HTTP, IP Address, Domain Name. Client-Server Model Client Bob Yahoo Server yahoo.com/finance.html A text file named finance.html.
TP2653 Adv Web Programming SOAP and WSDL. SOAP Simple Object Access Protocol – Lightweight XML-based messaging protocol – A protocol for accessing a Web.
Method of Converting Resource definitions into XSD Group Name: WG3 (PRO) Source: Shingo Fujimoto, FUJITSU, Meeting Date:
OneM2M-MP Data_Model_Repository Establishing Data Model Repository for oneM2M Group Name: Method and Procedure Sub-commitee Source: WG3 chair.
Resource Announcement Procedures Group Name: WG2 Source: Rajesh Bhalla, Hao Wu - ZTE Meeting Date: Agenda Item: TBD.
2-levels Access control for HTTP binding Group Name: WG4 (& WG2/WG3 for information) Source: Shingo Fujimoto, FUJITSU, Meeting.
James Holladay, Mario Sweeney, Vu Tran. Web Services Presentation Web Services Theory James Holladay Tools – Visual Studio Vu Tran Tools – Net Beans Mario.
OneM2M-ARC Enhancement_on_resources Some thoughts on oneM2M resources Group Name: WG2 Source: Norio Uchida, NEC, Barbara.
Announcement Resources ARC Announcement_Issues Group Name: WG2 Source: Barbara Pareglio, NEC Meeting Date: Agenda Item: Input Contribution.
Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:
WG 3 Progress Report at TP13 Group Name: oneM2M TP13 Source: Raymond Forbes, LM Ericsson, Meeting Date: to
Introduction to the SharePoint 2013 REST API. 2 About Me SharePoint Solutions Architect at Sparkhound in Baton Rouge
1 Web Service Description Language (WSDL) 大葉大學資工系.
Management of CMDH Policies Group Name: WG5-MAS Source: Wolfgang Granzow, Qualcomm, Meeting Date: Agenda Item: Management.
App-ID Discussion Group Name: ARC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 31 July 2014 Agenda Item: TBD.
Copyright © 2013 Curt Hill SOAP Protocol for exchanging data and Enabling Web Services.
1 Web Services Web and Database Management System.
Supporting long polling Group Name: ARC WG Source: SeungMyeong, LG Electronics, Meeting Date: x-xx Agenda Item: TBD.
Customized Resource Types MAS Group Name: MAS + ARC + PRO WGs Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date:
Discussion on the problem of non- Blocking Synchronous mode Group Name: ARC WG Source: Yuan Tao, Mitch Tseng, Huawei Technologies Meeting Date: ARC 15.2.
Node-Specific Resource Group Name: ARC&MAS Source: LGE, Meeting Date: Agenda Item: Contribution.
Matching Resources with CSFs Group Name: WG2 (ARC) Source: Hongbeom Ahn, LG Electronics, Meeting Date:
WG 3 Progress Report at TP15 Group Name: oneM2M TP15 Source: Raymond Forbes, LM Ericsson, Meeting Date: to
Discussion on XSD implementation conventions (document number PRO R01) Group Name: PRO Source: Wolfgang Granzow, Meeting.
Abierman-netconf-mar07 1 NETCONF WG 68 th IETF Prague, CZ March 19, 2007.
Management of Semantic Instances in resources using SPARQL update operation with HTTP verbs Group Name: MAS 19 Source: Minwoo Ryu, jaeho Kim, Sungchan.
PRO/ARC and TST/PRO joint sessions at TP20 Group Name: oneM2M TP20 Source: Peter Niblett, IBM Meeting Date:
Introduction to Web Services Presented by Sarath Chandra Dorbala.
Lecture VI: SOAP-based Web Service CS 4593 Cloud-Oriented Big Data and Software Engineering.
Protocol Issues related to Plugtest Group Name: TST Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date: Agenda.
The “application” Profile Type (draft-channabasappa-sipping-app-profile-type-01) Sumanth Channabasappa Josh Littlefield Salvatore Loreto 70th IETF, Vancouver,
WG 3 Progress Report at TP10 Group Name: oneM2M TP10 Source: Raymond Forbes, LM Ericsson, Meeting Date: to
WG2 PRO Status Report at TP19 Group Name: oneM2M TP19 Source: Peter Niblett, IBM Meeting Date: to Agenda Item: TP19, Item 10.3, Reports.
Call for input from WGs on things to test Group Name: TST Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date:
Authorization Architecture Discussion Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 28 MAY, 2014 Agenda.
SOAP, Web Service, WSDL Week 14 Web site:
DM Execute Group Name: WG2/WG5 Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item: TBD.
Discussion of open issues for WebSocket binding Group Name: PRO WG Source: Qualcomm Inc., Wolfgang Granzow, Nobu Uchida Meeting Date: PRO#22,
TS-0004 guideline for new resource type definition Group Name: PRO WG Source: SeungMyeong JEONG, LG Electronics Meeting Date: Agenda Item: TS.
Joint PRO/ARC session at TP20 Group Name: oneM2M TP20 Source: Peter Niblett, IBM Meeting Date:
Call to Action To increase market adoption of oneM2M, more publically available CSEs, AEs, tools and guides are needed for developers and systems integrators.
oneM2M interop 3 issues and optimizations
End-to-End Security for Primitives
Content from Python Docs.
Group multicast fanOut Procedure
2nd Interoperability testing issues
WEB SERVICES From Chapter 19 of Distributed Systems Concepts and Design,4th Edition, By G. Coulouris, J. Dollimore and T. Kindberg Published by Addison.
oneM2M Service Layer Protocol Version Handling
MAF&MEF Interface Specification discussion of the next steps
Discussion to clarify online/offline behavior
Hypertext Transfer Protocol
CIGI Drafting Group Agenda
CMDH Refinement Contribution: oneM2M-ARC-0397R01
Discussion on XSD open issues
Service Layer Dynamic Authorization [SLDA]
WEB API.
An introduction to oneM2M
HTTP Request Method URL Protocol Version GET /index.html HTTP/1.1
Summary of the MAF and MEF Interface Specification TS-0032
WEB SERVICES From Chapter 19, Distributed Systems
PLE Comment Resolution
BINDing URIs to SIP AORs
Presentation transcript:

MIME Type Definition Group Name: PRO WG Source: SeungMyeong JEONG, LG Electronics, seungmyeong.jeong@lge.com Meeting Date: 02 Sep 2014 Agenda Item: TBD

Introduction Why do we define MIME types? IANA’s recommendation that different protocol uses different MIME type S/W sees content-type header field to check protocol S/W then uses corresponding XSDs to validate message bodies

oneM2M MIME types We have defined 3 MIME types application/vnd.onem2m-resource-data+xml application/vnd.onem2m-response-status+xml application/vnd.onem2m-partial-updates+xml GET /CSE1Base/container1 HTTP/1.1 Host: http://m2m.sp1.com From: CSE2/AE21 X-M2M-RI: 001 Accept: application/vnd.onem2m-resource-data+xml Content-Type: application/vnd.onem2m-resource-data+xml <xml> <content> <attributeName>latest</attributeName> </content> </xml> HTTP Request 200 OK X-M2M-RI: 001 Content-Type: application/vnd.onem2m-resource-data+xml Content-Length: 115 <xml> <container> <currentNrOfInstances>2</currentNrOfInstances> <currentByteSize>95</currentByteSize> <latest>CSE1/container1/a1bx3</latest> </container> </xml> HTTP Response Example of MIME type usage following the HTTP binding TS

Is it used for request? Or also for response? type1: resource-data application/vnd.onem2m-resource-data+xml (6.7.1) This data type is used for XML-based data to represent the oneM2M resource. Top Level Element Child Element Name Element Type Note resourceData resourceTypeId xs:string   (Choice of defined m2m resource Types) Resource type which is included. Seems good, but what about request/response parameters that will be carried in message bodies? Is it used for request? Or also for response?

type2: response-status application/vnd.onem2m-response-status+xml (6.7.2) This data type is used for XML-based data m2m:responseStatus to represent the response status. See clause 6.3.2.3 for XSD definition of m2m:responseStatus . Seems like it is used in responses. What about a response also containing resource representation

type3: partial-updates application/vnd.onem2m-partial-updates+xml (6.7.3) This data type is used for XML-based data m2m:partialUpdates to represent the instruction to perform partial update. See clause 6.3.2.3 for XSD definition of m2m:partialUpdates Is this the subset of “resource-data”? Is this to distinguish full resource update and partial update? with different MIME type?

Discussion What was the reason to have 3 different types? How does those 3 types works in detail?

Suggestion If we see the needs to distinguish three different types, specify more information in clause 6.7 If we don’t have to the needs, We can have generic “application/vnd.onem2m+xml” and if it is needs, we can also have “application/vnd.onem2m+json” If “partial-update” is for differentiation from full/normal update operation, defining a new parameter seems better to register a new MIME type