Comment describing your root element CPE_SpecificationType is a modularized data type to provide a consistent approach to uniquesly specifying the identity of a specific platform using the Common Platform Enumeration (CPE) naming standard. http://cpe.mitre.org/ This field contains the plain language descriptive title of the relevant platform. This field holds a shortform descriptor for the language that the Title field is expressed in. Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility. See RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry at http://www.iana.org/assignments/lang-tag-apps.htm for further information. The union allows for the 'un-declaration' of xml:lang with the empty string. This field aggregates the descriptive metadata for this CPE Name instance. This date/time represents the last time that any CPE property has been modified. This field contains the internal NVD status of a CPE. This field contains the NVD specific unique identifier for a CPE. This is provided as a long-term identifier that can be used to map different versions of CPE syntax to a CPE with the same meaning. This is not a replacement of a CPEName. Use of a CPEName is still the standard ID naming scheme for CPE 2.x. This field contains the XML CPE metadata namespace descriptor for the CPE namespace relevant to this CPE Name use. This field contains the CPE Name value for the relevant platform. A CPE Name is a percent-encoded URI with each name starting with the prefix (the URI scheme name) "cpe:". The remainder of the name consists of colon separated values representing the CPE part, vendor, product, version, update, edition and language (i.e. cpe:/ {part} : {vendor} : {product} : {version} : {update} : {edition} : {language}). This field contains the XML namespace descriptor for the CPE namespace relevant to this CPE Name use. Block is a Structured_Text element consisting of one of Text_Title, Text, Code_Example_Language, or Code followed by another Block element. Structured_Text elements help define whitespace and text segments. Presentation Element: This element is used to definebold-faced title for a subsequent block of text. Presentation Element: This element is used to define a paragraph of text. Presentation Element: This element is used to identify the programming language being used in the following block of Code Presentation Element: This element is used to define a line of code. Presentation Element: This element is used to define an image. This element provides the location of the image file. This element provides a title for the image. Block is a Structured_Text element consisting of one of Text_Title, Text, Code_Example_Language, or Code followed by another Block element. Structured_Text elements help define whitespace and text segments. Block is a Structured_Text element consisting of one of Text_Title,Text, Code_Example_Language, or Code followed by another Block element. Structured_Text elements help define whitespace and text segments. This attribute identifies the nature of the content containedwithin the Block. The References_List_Type contains one or more Reference elements, each of which provide further reading and insight into the item. This should be filled out as appropriate. Each Reference subelement should provide a single source from which more information and deeper insight can be obtained, such as a research paper or an excerpt from a publication. Multiple Reference subelements can exist. The sole attribute of this element is the id. The id is optional and translates to a preceding footnote below the context notes if the author of the entry wants to cite a reference. Not all subelements need to be completed, since some are designed for web references and others are designed for book references. The fields Reference_Author and Reference_Title should be filled out for all references if possible. Reference_Section and Reference_Date can be included for either book references or online references. Reference_Edition, Reference_Publication, Reference_Publisher, and Reference_PubDate are intended for book references, however they can be included where appropriate for other types of references. Reference_Link is intended for web references, however it can be included for book references as well if applicable. This element identifies an individual author of the material being referenced. It is not required, but may be repeated sequentially in order to identify multiple authors for a single piece of material. This element identifies the title of the material beingreferenced. It is not required if the material does not have a title. This element is intended to provide a means of identifying the exact location of the material inside of the publication source, such as the relevant pages of a research paper, the appropriate chapters from a book, etc. This is useful for both book references and internet references. This element identifies the edition of the material being referenced in the event that multiple editions of the material exist. This will usually only be useful for book references. This element identifies the publication source of the reference material, if one exists. This element identifies the publisher of the reference material, if one exists. This element identifies the date when the reference was included in the entry. This provides the reader with a time line for when the material in the reference, usually the link, was valid. The date should be of the format YYYY-MM-DD. This field describes the date when the reference was published YYYY. This element should hold the URL for the material being referenced, if one exists. This should always be used for web references, and may optionally be used for book and other publication references. The id attribute is optional and is used as a mechanism forciting text in the entry. If an id is provided, it is placed between brackets and precedes this reference and the matching id should be used inside of the text for the attack pattern itself where this reference is applicable. All reference ids assigned within an entry must be unique. PersonnelType is an abstracted data type to standardize the description of sets of personnel. This field contains information describing the identify, resources and timing of involvement for a single contributor. This field describes the role played by this contributor. This field contains the name of this contributor. This field contains the email of this contributor. This field contains a telephone number of this contributor. This field contains the organization name of this contributor. This field contains a description (bounding) of the timing of this contributor's involvement. This field contains the start date for this contributor's involvement. This field contains the end date for this contributor's involvement. This field contains information describing the location at which the contributory activity occured.