BS IEC 62014-5:2015 pdf download-Quality of Electronic and Software Intellectual Property Used in System and System on Chip (SoC) Designs.
1.5.2 Notational conventions The keywords required, shall, shall not, should, should not, recommended, may, and optional in this document are to be interpreted as described in the IETF Best Current Practices document 14, RFC 2119 [B4]. 1.5.3 Syntax examples Any syntax examples shown in this standard are for information only and are only intended to illustrate the use of such syntax. 1.5.4 Graphics used to document the schema The W3C ® Web site specifies the XML schema language used to define the QIP XML schemas. 3, 4, 5 Normative details for compliance to the QIP standard are contained in the schema files. Within this document, pictorial representations of the information in the schema files illustrate the structure of the schema and define any constraints of the standard. With the exception of scope and visibility issues, the information in the figures and the schema files is intended to be identical. Where the figures and schema are in conflict, the XML schema file shall take precedence. 1.5.4.1 Elements and attributes The element is the fundamental building block on which this standard is based. An element may be either a leaf element, which is a container for information, or a branch element, which may contain further branch elements or leaf elements. A leaf or branch element may also contain attributes. Attributes are containers for information within the containing element. 1.5.4.2 Types A type is a designation of the format for the contents of an element or attribute. There are two different styles of types that can be defined. A type may be assigned to a leaf element or an attribute. This type is called a simpleType and defines the format of data that may be stored in this container. A type may also be assigned to a branch element. This type is called a complexType and defines further elements and attributes contained in the branch element.