Get access to the xml: attribute groups for xml:lang. This element contains the individual application, service, os and hardware definitions which will be used in an a-la-cart fashion to define specific platform support rulesets. This unique constraint keeps all ids used in this schema unique. This will help eliminate any confusion between using product and platform ids. The productIdKey is used to insure that all product ids are unique. A references to the product ids are used to build platform-definitions in an ala-cart fashion. The platformIdKey is used externally to reference a specific platform-definition identified by a platform id. A listing of all supported platforms An application or user-level program component product, part of a platform. Examples: Microsoft Word, Mozilla A system or network service that is a component of a benchmark platform. Examples: Apache HTTPD, Microsoft Exchange, IBM MQSeries Message Server The operating system for a benchmark platform. Examples: Microsoft Windows XP, Sun Solaris, Cisco IOS. A hardware chassis or designation that is part of the specification of a benchmark platform. Examples: Cisco C3725, Juniper M7. Type for a string with an xml:lang attribute. (Note: changed this to allow any xml: attribute because xml:lang is a bit narrow, and also would require the validation processor to download the XML namespace schema every time. We cannot count on XCCDF or other benchmark users have a live Internet connection at all times.) An individual product or component that makes up the overall platform. For more information see the subtypes below. A product consists of: a name, a version designator, zero or more named properties, and zero or more remarks. The organization responsible for development and maintenance of the product The product family the software or device belongs to. This will be used along with the optional model and level elements to determine version-range comparisons. Example: "Windows", "routers", "portal server". The product's model which will differentiate major versions of software. This may be useful when defining that all versions of software of a specific model are acceptable. The product's level which will differentiate functional capabilities across the same software version. Example: "enterprise", "home" The version designation for a platform component. This is the type for the version element: the element content is a version name or number, and the operator attribute specifies how that version applies. For example, to say 'IOS 12.1 or later', the content would be "12.1" and the operator attribute would be "greater than or equal to". Allowed operators for version elements. These are valid only for quasi-numeric version numbers, but the schema doesn't enforce it.