Proprietary extensions SHALL NOT place any objects, elements, attributes, etc. in the standardized SEP XML namespace ("urn:ieee:std:2030.5:ns") and instead SHALL be placed in a different XML namespace.
The following examples demonstrate allowed and disallowed extensions. In these examples, “SEPElement{#}” is used to demonstrate elements that are defined in the SEP schema. “MFEElement{#}” and “MFENS” are used to demonstrate elements and namespaces that are proprietary extensions respectively.
The example given in Figure 7 demonstrates allowed and disallowed (crossed out) element extensions.
Figure 7 —Allowed and disallowed extension
Proprietary extensions SHALL NOT extend enumerations defined in the IEEE 2030.5 schema.
Proprietary extensions made to standardized objects (in a proprietary namespace) defined in the IEEE 2030.5 schema SHALL be able to be ignored. That is, a device that does not understand a proprietary extension can safely ignore the extension.
Proprietary extensions made to standardized objects (in a proprietary namespace) defined in the IEEE 2030.5 schema SHALL NOT change the semantics of elements and attributes defined in the IEEE 2030.5 schema.