A.2.1 XSD storage <_container >

According to clause 7.2.1.1 the IPE creates a <container> resource that acts as a XSD-storage and that is a child resource of the IPE's <AE> .

Derived from the IRI of the ontology: http://www.XYZ.com/WashingMachines, following the rule given in table 7.2.1.2-1 the resource name for that <container> resource (in the table the placeholder is called &XSDSTORAGE;) will be www.XYZ.com_WashingMachines.

The IPE will also create <contentInstance> resources as child-resources of the XSD-storage <container> resource with the following resource names (see &XSDFILE; in table 7.2.1.2-1):

• XYZ_Cool.xsd ... contains the XSD for the <flexContainer> resource of the Interworked Device type XYZ_Cool
• SwitchOnService.xsd ... contains the XSD for the <flexContainer> resource of the Service type SwitchOnService
• MonitorService.xsd ... contains the XSD for the <flexContainer> resource of the Service type MonitorService
• ToggleBinary.xsd ... contains the XSD for the <flexContainer> resource of the Operation type ToggleBinary

When the IPE crates a new <flexContainer> specialization of these types then the attribute containerDefinition will contain the absolute, hierarchical address of the <contentinstance> that contains the related XSD.
E.g. for the SwitchOnService it could have the value: //m2m.service.com/IN-CSE0001/bigFatCse/name_of_IPE_AE/ww.XYZ.com_WashingMachines/SwitchOnService.xsd