| ### Showing:
Annotations
Attributes
Diagrams
Source

Attribute Group ResourceNodeAttributeOptionGroup

Namespace | urn:us:gov:ic:ism
Annotations | An attribute group to be used on the element that represents the resource node of an instance document. This node's ISM attributes would be used to generate banner marks and the E.O. 13526 classification authority block. Implementing Schemas might use this on the Root node or any other node. This group has all the attributes as optional. It could be used in a schema where many nodes may be the resource element. When the element is acting as the resource element it should have attributes used similar to ResourceNodeAttributeGroup.
Diagram |
Attributes |
QName | Type | Use | Annotation
--- | --- | --- | ---
SchemaguideSecurityAttributesOptionGroup | xsd:NMTOKEN | optional | This attribute is only a placeholder so that all the ISM attributes are not shown in the schemaGuide for every element. If you refer to the documentation of the attribute group it will say what attributes should be here.
compliesWith | ismcomplies:CVEnumISMCompliesWith | optional | The ISM rule sets a document complies with This attribute is used at the resource level. The permissible values for this simple type are defined in the ISM Complies With CVE: CVEnumISMCompliesWith.xml
createDate | xsd:date | optional | The date when ISM metadata was added or updated This date is used by some constraint rules to determine if ISM markings are valid. For example, this date is used to check deprecation of some marks.
exemptFrom | ismexempt:CVEnumISMExemptFrom | optional | Specific exemptions within an ISM rule set that are claimed for a document This attribute is used on the resource node of a document in conjunction with @compliesWith. The permissible values for this simple type are defined in the ISM Exempt From CVE: CVEnumISMExemptFrom.xml
externalNotice | xsd:boolean | optional | An indicator that an element contains a security-related notice for information NOT contained in document This flag allows for a notice to exist in a document without the data that would normally require the notice. For example, a document could contain a FISA notice without FISA data present. Source citations are a common use case for this attribute.
noAggregation | xsd:boolean | optional | When true, an indicator that there is no classification by compilation across any combination of portions extracted from the document.
noticeDate | xsd:date | optional | A date associated with a notice (for example, the DoD Distribution notice date)
noticeProseID | ismnoticeprose:CVEnumISMNoticeProse | optional | An indicator that can be used to identify a security-related notice in an out-of-band fashion without actually having the notice text in the record but rather a notice text prose identifier. This prose identifier maps to the notice text which is stored in a CVE. The permissible values for this attribute are defined in the ISM Notice Prose CVE: CVEnumISMNoticeProse.xml
noticeReason | restriction of xsd:string | optional | A reason associated with a notice (for example, the DoD Distribution reason)
noticeType | ismnotice:CVEnumISMNotice | optional | An indicator that the containing element contains a security-related notice. This attribute is used to categorize which of the required notices is specified in the element. These categories include those described in the Intelligence Community Markings System Register and Manual, as well as additional well-defined and formally recognized security notice types described in other directives, such as US-Person and DoD Distribution. The element could contain any structure that the implementing schema defines, and rendering details are relegated to the implementing schema. The permissible values for this attribute are defined in the ISM Notice CVE: CVEnumISMNotice.xml
resourceElement | xsd:boolean | optional | This attribute is used to designate which element has the ISM attributes representing the classification for the entire resource. Every document must have at least one element with this indicator as true. It should be rare that a document has more than one. Mainly this would occur in some sort of aggregation schema. In the aggregation case, the first @resourceElement attribute in XML document order is the one used for all constraint rules.
unregisteredNoticeType | restriction of xsd:string | optional | A notice that is of a category that is not described in the Intelligence Community Markings System Register and Manual and/or is not sufficiently defined to be represented in the Controlled Value Enumeration CVEnumISMNotice.xml. This attribute can be used by specifications that import ISM to represent a wider variety of security-related notices.
Source |
    <xsd:attributeGroup name="ResourceNodeAttributeOptionGroup">
      <xsd:annotation>
        <xsd:documentation>
          <xhtml:p ism:ownerProducer="USA" ism:classification="U">An attribute group to be used on the element that represents the resource node of an instance document. This node's ISM attributes would be used to generate banner marks and the E.O. 13526 classification authority block. Implementing Schemas might use this on the Root node or any other node. This group has all the attributes as optional. It could be used in a schema where many nodes may be the resource element. When the element is acting as the resource element it should have attributes used similar to ResourceNodeAttributeGroup.</xhtml:p>
        </xsd:documentation>
      </xsd:annotation>
      <xsd:attributeGroup ref="ISMResourceAttributeOptionGroup"/>
      <xsd:attributeGroup ref="SecurityAttributesOptionGroup"/>
      <xsd:attributeGroup ref="ISMNoticeAttributeGroup"/>
    </xsd:attributeGroup>
Schema location | IC-ISM.xsd Copy and paste this link to your file browser, clicking the link MAY open in the browser. Opening in an XML aware editor is best.

## This document has been approved for Public Release by the Office of the Director of National Intelligence. See Distribution Notice for details. Click Here