Download directly for more content description... Mapping of Conceptual Elements to Physical HTML Structures . metadata within HTML intelligence content. The HTML meta element provides a. standard . The Developer's Guide addresses the technical implementation details for this HTML encoding. The topics that are detailed in the following sections include: HTML Encoding Guidelines, Metadata Elements, Mapping of Conceptual Elements to Physical HTML Structures, Example of an HTML document with Metadata Tags, IC Metadata Versioning Guidelines, Tag Sequence and Clustering, Mandatory Metadata, Populating Security Metadata, Special Values, Repeatable Metadata, Delimited content Values, Domain-specific Metadata Content, Electronic Metadata and HTML Link Elements. This implementation expands and refines the conceptual elements defined in the ICS for Information Resource Metadata, resulting in a physical model for information resource metadata within HTML intelligence content. The HTML meta element provides a standard format for applying metadata to HTML documents shared between producers and consumers. This Implementation Profile is an implementation of the World Wide Web Consortium’s (W3C) specification of HTML. The standard uses the meta element as defined in the W3C HTML 4.01 Recommendation. This profile is an implementation of the W3C HTML meta element (e.g., tag) specification. Each piece of metadata is represented by a meta element in the head of the HTML document. The attribute name and content are used to store values. Throughout this document the term metadata element is used to refer to a meta element with a name attribute populated with a specific value. For example, the metadata element IL.secur.classif refers to a meta element with a name of IL.secur.classif. This shorthand technique simplifies references to the different metadata discussed. In the example above, within the name attribute, the prefix {IL.} designates a metadata element prescribed by this Implementation Profile and {xxx} represents the name of the specific metadata element. The value of the content attribute is represented by {yyy}. Note that lowercase is used for the meta element name and its attribute names—name and content. This lowercasing is purposeful to ensure compatibility with both HTML and XHTML document type definitions. The sequence of the attributes is not significant. In the above example, name is specified before content, but the two attributes could be reversed. This implementation focuses on the meta element attributes name and content, though the W3C HTML recommendation offers four additional attributes—http-equiv, scheme, lang, and dir. These four additional attributes should not be used for the meta elements specified in this Implementation Profile. Most applications in the IC do not make use of these additional attributes.