From c49eba239d6115d1bfb0ece3e6e4aa9af8d4f2df Mon Sep 17 00:00:00 2001 From: simigami <simigami2@naver.com> Date: Thu, 7 Dec 2023 15:50:17 +0900 Subject: [PATCH] br tag fixes for Annex A --- .../TR-0051-modification_for_MD_Conversion.md | 32 +++++++++---------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/Conversed_MD/TR-0051-modification_for_MD_Conversion.md b/Conversed_MD/TR-0051-modification_for_MD_Conversion.md index 6e0033c..20b795e 100644 --- a/Conversed_MD/TR-0051-modification_for_MD_Conversion.md +++ b/Conversed_MD/TR-0051-modification_for_MD_Conversion.md @@ -1525,10 +1525,10 @@ In this clause, notification examples are provided for the understanding of noti |API Name |Notification procedure when the <subscription> resource has notificationEventType set to 1(Hosting CSE sends notification when the subscribed-to resource has been updated) | |Target Resource |Update Target: Requested <container> resource<br />Notification Target: originator | |<br />Description |Figure below depicts the procedure for notification.<br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />Initial condition: MN(Hosting CSE) has a <container> resource. The originator is AE1 in this clause, but can be CSE.<br /><br />Step 01: The originator sends a <subscription> resource CREATE request to the <container> resource on the Registrar CSE. In the request, notificationEventType set to 1 and notificationURI attribute set to originator. The Registrar CSE creates a <subscription> resource and sends back a response.<br />Step 02: An AE2 sends an UPDATE request to the <container> resource. The Registrar CSE updates a <container> resource and sends back a response.<br />Step 03: The Hosting CSE sends notification as soon as update succeed. The originator sends back an ACK message. | -|**S** **tep 01**<br /><br /><br /><br /> |**Resource Structure** **before Sending Request**<br /><br />  | -|**S** **tep 01**<br /><br /><br /><br /> |**Call Flow** | -|**S** **tep 01**<br /><br /><br /><br /> |**HTTP Header Information**<br /><br />Header and Value pair information:<br />Accept : application/ json<br />X-M2M-RI : Request ID<br />X-M2M-Origin : AE-ID of request originator<br />Content-Type : application/json;ty=23<br />X-M2M-RVI : Release Version Indicator<br /><br /><br /><br /><br /> | -|**S** **tep 01**<br /><br /><br /><br /> |**Example**<br /><br />**API/NOTI/NET1/STEP01**<br /><br />**HTTP Request:**<br /><br />POST /mn-name/cont\_temp? HTTP/1.1<br />Host: 192.168.0.10:8282<br />X-M2M-Origin: CAE5630283216026458665<br />Content-Type: application/json;ty=23<br />Accept: application/json<br />X-M2M-RI: 1234<br />X-M2M-RVI: 2a<br /><br />{<br /> "m2m:sub": {<br /> "enc": {<br /> "net": <a href="#_ref_1">[1]</a><br /> },<br /> "nu": ["AE1"],<br /> "rn": "cont\_sub"<br /> }<br />}<br /><br /><br />**HTTP Response:**<br /><br />201 Created<br />Content-Location: mn-name/cont\_temp<br />Content-Type: application/json<br />X-M2M-RI: 1234<br />X-M2M-RVI: 2a<br />X-M2M-RSC: 2001<br /> | +|**S** **tep 01** |**Resource Structure** **before Sending Request**<br /><br />  | +|**S** **tep 01** |**Call Flow** | +|**S** **tep 01** |**HTTP Header Information**<br /><br />Header and Value pair information:<br />Accept : application/ json<br />X-M2M-RI : Request ID<br />X-M2M-Origin : AE-ID of request originator<br />Content-Type : application/json;ty=23<br />X-M2M-RVI : Release Version Indicator<br /><br /><br /><br /><br /> | +|**S** **tep 01** |**Example**<br /><br />**API/NOTI/NET1/STEP01**<br /><br />**HTTP Request:**<br /><br />POST /mn-name/cont\_temp? HTTP/1.1<br />Host: 192.168.0.10:8282<br />X-M2M-Origin: CAE5630283216026458665<br />Content-Type: application/json;ty=23<br />Accept: application/json<br />X-M2M-RI: 1234<br />X-M2M-RVI: 2a<br /><br />{<br /> "m2m:sub": {<br /> "enc": {<br /> "net": <a href="#_ref_1">[1]</a><br /> },<br /> "nu": ["AE1"],<br /> "rn": "cont\_sub"<br /> }<br />}<br /><br /><br />**HTTP Response:**<br /><br />201 Created<br />Content-Location: mn-name/cont\_temp<br />Content-Type: application/json<br />X-M2M-RI: 1234<br />X-M2M-RVI: 2a<br />X-M2M-RSC: 2001<br /> | |**S** **tep 02**<br /><br /> |**Resource** **Structurebefore** **Sending Request**<br /><br /><br /> | |**S** **tep 02**<br /><br /> | | |**S** **tep 02**<br /><br /> |**HTTP Header Information**<br /><br />Header and Value pair information:<br />Accept : application/ json<br />X-M2M-RI : Request ID<br />X-M2M-Origin : AE-ID of request originator<br />Content-Type : application/json<br />X-M2M-RVI : Release Version Indicator | @@ -1548,10 +1548,10 @@ In this clause, notification examples are provided for the understanding of noti |**API Name** |Notification procedure when the <subscription> resource has notificationEventType set to 2(Hosting CSE sends notification when the subscribed to resource has been deleted) | |**Target Resource** |Delete Target: Requested <container> resource<br />Notification Target: originator | |<br />**Description** |Figure below depicts the procedure for notification.<br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />Initial condition: MN(Hosting CSE) has a <container> resource. The originator is AE1 in this clause, but can be CSE.<br /><br />Step 01: The originator sends a <subscription> resource CREATE request to the <container> resource on the Registrar CSE. In the request, notificationEventType set to 2 and notificationURI attribute set to originator. The Registrar CSE creates a <subscription> resource and sends back a response.<br />Step 02: An AE2 sends a DELETE request to the <container> resource. The Registrar CSE deletes a <container> resource and sends back a response.<br />Step 03: The Hosting CSE sends notification as soon as delete succeed. The originator sends back an ACK message. | -|**S** **tep 01**<br /><br /><br /><br /> |**Resource Structure** **before Sending Request**<br /><br />  | -|**S** **tep 01**<br /><br /><br /><br /> |**Call Flow**<br /> | -|**S** **tep 01**<br /><br /><br /><br /> |**HTTP Header Information**<br /><br />Header and Value pair information:<br />Accept : application/ json<br />X-M2M-RI : Request ID<br />X-M2M-Origin : AE-ID of originator<br />Content-Type : application/json;ty=23<br />X-M2M-RVI : Release Version Indicator | -|**S** **tep 01**<br /><br /><br /><br /> |**Example**<br /><br />**API/NOTI/NET2/STEP01**<br /><br />**HTTP Request:**<br /><br />POST /mn-name/cont\_temp? HTTP/1.1<br />Host: 192.168.0.10:8282<br />X-M2M-Origin: CAE5630283216026458665<br />Content-Type: application/json;ty=23<br />Accept: application/json<br />X-M2M-RI: 1234<br />X-M2M-RVI: 2a<br /><br />{<br /> "m2m:sub": {<br /> "enc": {<br /> "net": <a href="#_ref_2">[2]</a><br /> },<br /> "nu": ["AE1"],<br /> "rn": "cont\_sub"<br /> }<br />}<br /><br /><br />**HTTP Response:**<br /><br />201 Created<br />Content-Location: mn-name/cont\_temp<br />Content-Type: application/json<br />X-M2M-RI: 1234<br />X-M2M-RVI: 2a<br />X-M2M-RSC: 2001<br /> | +|**S** **tep 01** |**Resource Structure** **before Sending Request**<br /><br />  | +|**S** **tep 01** |**Call Flow**<br /> | +|**S** **tep 01** |**HTTP Header Information**<br /><br />Header and Value pair information:<br />Accept : application/ json<br />X-M2M-RI : Request ID<br />X-M2M-Origin : AE-ID of originator<br />Content-Type : application/json;ty=23<br />X-M2M-RVI : Release Version Indicator | +|**S** **tep 01** |**Example**<br /><br />**API/NOTI/NET2/STEP01**<br /><br />**HTTP Request:**<br /><br />POST /mn-name/cont\_temp? HTTP/1.1<br />Host: 192.168.0.10:8282<br />X-M2M-Origin: CAE5630283216026458665<br />Content-Type: application/json;ty=23<br />Accept: application/json<br />X-M2M-RI: 1234<br />X-M2M-RVI: 2a<br /><br />{<br /> "m2m:sub": {<br /> "enc": {<br /> "net": <a href="#_ref_2">[2]</a><br /> },<br /> "nu": ["AE1"],<br /> "rn": "cont\_sub"<br /> }<br />}<br /><br /><br />**HTTP Response:**<br /><br />201 Created<br />Content-Location: mn-name/cont\_temp<br />Content-Type: application/json<br />X-M2M-RI: 1234<br />X-M2M-RVI: 2a<br />X-M2M-RSC: 2001<br /> | |**S** **tep 02**<br /><br /> |**Resource Structure** **before Sending Request**<br /> | |**S** **tep 02**<br /><br /> |**Call Flow**<br /> | |**S** **tep 02**<br /><br /> |**HTTP Header Information**<br /><br />Header and Value pair information:<br />Accept : application/ json<br />X-M2M-RI : Request ID<br />X-M2M-Origin : AE-ID of request originator<br />X-M2M-RVI : Release Version Indicator | @@ -1571,10 +1571,10 @@ In this clause, notification examples are provided for the understanding of noti |**API Name** |Notification procedure when the <subscription> resource has notificationEventType set to 3 (Hosting CSE sends notification when the direct child resource has been created) | |**Target Resource** |Create <contentIntance> target: Requested <container> resource<br />Notification Target: originator | |<br />**Description** |Figure below depicts the procedure for notification.<br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br /><br />Initial condition: MN(Hosting CSE) has a <container> resource. The originator is AE1 in this clause, but can be CSE.<br /><br />Step 01: The originator sends a <subscription> resource CREATE request to the <container> resource on the Registrar CSE. In the request, notificationEventType set to 3 and notificationURI attribute set to originator. The Registrar CSE creates a <subscription> resource and sends back a response.<br />Step 02: An AE2 sends a CREATE request of the <contentInstance> resource to the <container> resource. The Registrar CSE creates a <contentInstance> resource and sends back a response.<br />Step 03: The Hosting CSE sends notification as soon as create succeed. The originator sends back an ACK message. | -|**S** **tep 01**<br /><br /><br /><br /> |**Resource Structure** **before Sending Request**<br /><br />  | -|**S** **tep 01**<br /><br /><br /><br /> |**Call Flow**<br /> | -|**S** **tep 01**<br /><br /><br /><br /> |**HTTP Header Information**<br /><br />Header and Value pair information:<br />Accept : application/ json<br />X-M2M-RI : Request ID<br />X-M2M-Origin : AE-ID of originator<br />Content-Type : application/json;ty=23<br />X-M2M-RVI : Release Version Indicator | -|**S** **tep 01**<br /><br /><br /><br /> |**Example**<br /><br />**API/NOTI/NET3/STEP01**<br /><br />**HTTP Request:**<br /><br />POST /mn-name/cont\_temp? HTTP/1.1<br />Host: 192.168.0.10:8282<br />X-M2M-Origin: CAE5630283216026458665<br />Content-Type: application/json;ty=23<br />Accept: application/json<br />X-M2M-RI: 1234<br />X-M2M-RVI: 2a<br /><br />{<br /> "m2m:sub": {<br /> "enc": {<br /> "net": <a href="#_ref_3">[3]</a><br /> },<br /> "nu": ["AE1"],<br /> "rn": "cont\_sub"<br /> }<br />}<br /><br /><br />**HTTP Response:**<br /><br />201 Created<br />Content-Location: mn-name/cont\_temp<br />Content-Type: application/json<br />X-M2M-RI: 1234<br />X-M2M-RVI: 2a<br />X-M2M-RSC: 2001<br /> | +|**S** **tep 01** |**Resource Structure** **before Sending Request**<br /><br />  | +|**S** **tep 01** |**Call Flow**<br /> | +|**S** **tep 01** |**HTTP Header Information**<br /><br />Header and Value pair information:<br />Accept : application/ json<br />X-M2M-RI : Request ID<br />X-M2M-Origin : AE-ID of originator<br />Content-Type : application/json;ty=23<br />X-M2M-RVI : Release Version Indicator | +|**S** **tep 01** |**Example**<br /><br />**API/NOTI/NET3/STEP01**<br /><br />**HTTP Request:**<br /><br />POST /mn-name/cont\_temp? HTTP/1.1<br />Host: 192.168.0.10:8282<br />X-M2M-Origin: CAE5630283216026458665<br />Content-Type: application/json;ty=23<br />Accept: application/json<br />X-M2M-RI: 1234<br />X-M2M-RVI: 2a<br /><br />{<br /> "m2m:sub": {<br /> "enc": {<br /> "net": <a href="#_ref_3">[3]</a><br /> },<br /> "nu": ["AE1"],<br /> "rn": "cont\_sub"<br /> }<br />}<br /><br /><br />**HTTP Response:**<br /><br />201 Created<br />Content-Location: mn-name/cont\_temp<br />Content-Type: application/json<br />X-M2M-RI: 1234<br />X-M2M-RVI: 2a<br />X-M2M-RSC: 2001<br /> | |**S** **tep 02**<br /><br /> |**Resource Structure** **before Sending Request**<br /> | |**S** **tep 02**<br /><br /> |**Call Flow**<br /> | |**S** **tep 02**<br /><br /> |**HTTP Header Information**<br /><br />Header and Value pair information:<br />Accept : application/ json<br />X-M2M-RI : Request ID<br />X-M2M-Origin : AE-ID of originator<br />Content-Type : application/json<br />X-M2M-RVI : Release Version Indicator | @@ -1597,11 +1597,11 @@ In this clause, notification examples are provided for the understanding of noti -|**S** **tep 01**<br /><br /><br /><br /> |**Resource Structure** **before Sending Request** <br /> | +|**S** **tep 01** |**Resource Structure** **before Sending Request** <br /> | |-|-| -|**S** **tep 01**<br /><br /><br /><br /> |**Call Flow**<br /> | -|**S** **tep 01**<br /><br /><br /><br /> |**HTTP Header Information**<br /><br />Header and Value pair information:<br />Accept : application/ json<br />X-M2M-RI : Request ID<br />X-M2M-Origin : AE-ID of originator<br />Content-Type : application/json;ty=23<br />X-M2M-RVI : Release Version Indicator<br /> | -|**S** **tep 01**<br /><br /><br /><br /> |**Example**<br /><br />**API/NOTI/NET4/STEP01**<br /><br />**HTTP Request:**<br /><br />POST /mn-name/cont\_temp? HTTP/1.1<br />Host: 192.168.0.10:8282<br />X-M2M-Origin: CAE5630283216026458665<br />Content-Type: application/json;ty=23<br />Accept: application/json<br />X-M2M-RI: 1234<br />X-M2M-RVI: 2a<br /><br />{<br /> "m2m:sub": {<br /> "enc": {<br /> "net": <a href="#_ref_4">[4]</a><br /> },<br /> "nu": ["AE1"],<br /> "rn": "cont\_sub"<br /> }<br />}<br /><br /><br />**HTTP Response:**<br /><br />201 Created<br />Content-Location: mn-name/cont\_temp<br />Content-Type: application/json<br />X-M2M-RI: 1234<br />X-M2M-RVI: 2a<br />X-M2M-RSC: 2001<br /> | +|**S** **tep 01** |**Call Flow**<br /> | +|**S** **tep 01** |**HTTP Header Information**<br /><br />Header and Value pair information:<br />Accept : application/ json<br />X-M2M-RI : Request ID<br />X-M2M-Origin : AE-ID of originator<br />Content-Type : application/json;ty=23<br />X-M2M-RVI : Release Version Indicator<br /> | +|**S** **tep 01** |**Example**<br /><br />**API/NOTI/NET4/STEP01**<br /><br />**HTTP Request:**<br /><br />POST /mn-name/cont\_temp? HTTP/1.1<br />Host: 192.168.0.10:8282<br />X-M2M-Origin: CAE5630283216026458665<br />Content-Type: application/json;ty=23<br />Accept: application/json<br />X-M2M-RI: 1234<br />X-M2M-RVI: 2a<br /><br />{<br /> "m2m:sub": {<br /> "enc": {<br /> "net": <a href="#_ref_4">[4]</a><br /> },<br /> "nu": ["AE1"],<br /> "rn": "cont\_sub"<br /> }<br />}<br /><br /><br />**HTTP Response:**<br /><br />201 Created<br />Content-Location: mn-name/cont\_temp<br />Content-Type: application/json<br />X-M2M-RI: 1234<br />X-M2M-RVI: 2a<br />X-M2M-RSC: 2001<br /> | |**S** **tep 02**<br /><br /> |**Resource Structure** **before Sending Request**<br /> | |**S** **tep 02**<br /><br /> |**Call Flow**<br /> | |**S** **tep 02**<br /><br /> |**HTTP Header Information**<br /><br />Header and Value pair information:<br />Accept : application/ json<br />X-M2M-RI : Request ID<br />X-M2M-Origin : AE-ID of originator<br />X-M2M-RVI : Release Version Indicator<br /> | -- GitLab