From 841458e1d43682a53fdc23cab812137c148ca120 Mon Sep 17 00:00:00 2001 From: wgranzow <wgranzow@qti.qualcomm.com> Date: Tue, 27 Jan 2015 18:00:36 +0100 Subject: [PATCH] correction (removal of responsePrimitive) --- CDT-notification-v0_8_0.xsd | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/CDT-notification-v0_8_0.xsd b/CDT-notification-v0_8_0.xsd index c9bbd28..e3ed157 100644 --- a/CDT-notification-v0_8_0.xsd +++ b/CDT-notification-v0_8_0.xsd @@ -39,20 +39,6 @@ oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PR <xs:element name="aggregatedNotification" type="m2m:aggregatedNotification" /> - <!-- TODO: The element defined below cannot be denoted "responsePrimitive" as defined in Table 7.4.1.1.1-2 of TS-0004. - This causes conflict due to two global components with the same name. Whatever element name is used, - it introduces an extra wrapping level around the requestPrimitive object. - I guess this can be avoided only by allowing the m2m:responsePrimitive to be included into a - primitiveContent directly - --> - <xs:element name="notificationContent" > - <xs:complexType> - <xs:sequence> - <xs:element ref="m2m:responsePrimitive" minOccurs="1" maxOccurs="unbounded"/> - </xs:sequence> - </xs:complexType> - </xs:element> - <xs:complexType name="aggregatedNotification"> <xs:sequence> <xs:element name="notification" type="m2m:notification" minOccurs="0" maxOccurs="unbounded"/> -- GitLab