Top-level Type and Group definitions. A ComplexType representing Nouns used along with pre-defined verbs to define BOD messages. Essentially an element of a larger domain model for an application. The path includes an indicator of the level of the text, either at the noun, instance, level or at the component, class level. Localized text (labels, help, etc.) for a Noun, Type, or use of a Type. Describes how a sub-type derives from a super-type. A name-value element within a CodeList. The pointer to the file that contains the schema element. Describes a complexType of a schema. A container in which a choice of only one of the items can appear. Container in which all elements must appear in the order listed. Defines a named group of elements to be defined once and references from many places by name (like a macro.) Defines a named group of attributes to be defined once and references from many places by name (like a macro.) A customization to the available metadata about a Type or usage of a Type. Metadata is merged from various sources. Any "global" metadata associated with a Type definition is applied first. Next any point-of-use metadata is overlaid. Each kind of metadata also can be defined at various levels. From the most general standard OAGIS to the most specific for a given customer deployment. We start with general and overlay each available level up to the most specific. Gives details on the business key(s) of a Noun. Identifies a property that is part of a Key. Customized (Infor-level only) metadata about a Noun. Must be kept in sync with the POJO: com.infor.oagis.nouns.metadata.NounData Describes situation in which an alternate element is allowed to appear. Indicates if this elements values myust come from an enumerated list. Default is False. Mandatory indicates that the element is required for a Sync BOD only. Default is False. Indicates that this element should never be used in an Infor BOD. If set indicates that this element represents a sensible point at which to flatten for creating a simpler view of the data. The value is the path within the Noun to the key property that, when combined with key data "above" the flattening point, make the data below the flattening point unique. For example consider a SalesOrder Noun with a OrderLine Element as a flattening point that calls out the LineNumber property as it key. Only used when the value has a fixed length. Total number of digits to the right of the decimal indicator. Total number of digits allowed in a numeric value. This element is not used when the valid values of the code are defined in the code fortress. They are only used when the codes are defined in a code list or through documentation. The default value for an element when the element is not included. Minimum value for an element. The value entered is valid. Minimum value for an element. The value entered is valid. A regular expression that can be used to validate data on input. Identifies the source of the valid values for a code. Local means that the customer can define the values, CodeList means that the valid values are in either the Infor or OAGIS CodeList.xsd file, Documentation means that the values are by convention and are only documented as the valid values. Metadata customizations can be defined at various levels. INFOR - Additional standard metadata as defined by Infor BOD Librarians. APPLICATION - Metadata used by a specific application. CUSTOMER - Metadata specific to a given customer deployment. This is typically added by Infor PSO, but may possibily be added by the customer themselves. Kind of generalization possible in XSD schemas. Extension in which additions to base are listed. Restriction in which differences from base are listed. Different kinds of localized text that can be defined. Label - UI label. ColumnLabel - UI grid column header. Description - General description. Help - Help text. Category of noun. Master data such as ItemMaster. Transactional data such as PurchaseOrder. Balance data such as InventoryBalance.