diff --git a/CDT-notification-v0_8_0.xsd b/CDT-notification-v0_8_0.xsd index c9bbd28319c1a02e49deabdde22e24e87c3f05a4..e3ed157d9618129f0e279e2bfb641ae0b2622241 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"/>