| ### Showing:
Annotations
Attributes
Diagrams
Facets
Instances
Properties
Source
Used by

Element AssertionType / StatementMetadata

Namespace | urn:us:gov:ic:tdf
Annotations | Intended for access, rights, handling or other metadata that applies to the assertion statement. Use EDH security options whenever an assertion already has a unique enterprise identifer or is intended for potential extraction and should be able stand on it's own as a separate referencable object. Use arh security only when assertions are not intended to be extracted and do not require enterprise identifiers.
Diagram |
Properties |
content: | complex
minOccurs: | 0
maxOccurs: | 2
Model | edh:Edh | edh:ExternalEdh | arh:Security | arh:ExternalSecurity
Children | arh:ExternalSecurity, arh:Security, edh:Edh, edh:ExternalEdh
Instance |
    <StatementMetadata appliesToState="" xmlns="urn:us:gov:ic:tdf" xmlns:edh="urn:us:gov:ic:edh" xmlns:arh="urn:us:gov:ic:arh">
      <edh:Edh edh:DESVersion="" DESVersion="" ntk:DESVersion="" arh:DESVersion="">{1,1}</edh:Edh>
      <edh:ExternalEdh edh:DESVersion="" DESVersion="" ntk:DESVersion="" arh:DESVersion="">{1,1}</edh:ExternalEdh>
      <arh:Security compliesWith="" createDate="" DESVersion="" ntk:DESVersion="" arh:DESVersion="" noticeDate="" noticeReason="" noticeType="" resourceElement="" SchemaguideSecurityAttributesGroup="" unregisteredNoticeType="">{1,1}</arh:Security>
      <arh:ExternalSecurity compliesWith="" createDate="" DESVersion="" ntk:DESVersion="" arh:DESVersion="" excludeFromRollup="true" noticeDate="" noticeReason="" noticeType="" resourceElement="" SchemaguideSecurityAttributesGroup="" unregisteredNoticeType="">{1,1}</arh:ExternalSecurity>
    </StatementMetadata>
Attributes |
QName | Type | Fixed | Default | Use | Annotation
--- | --- | --- | --- | --- | ---
appliesToState | CVEnumTDFAppliesToState |  |  | optional | Used to indicate if the statement metadata applies to encrypted or unencrypted data. If a TDO payload or assertion statement is encrypted, there are in fact two potentially different markings needed for decision making, analysis and querying, one describing the handling required for the encrypted blob, and the other for the handling required for the unencrypted (and in effect external) state. In cases where statements and/or payloads are encrypted, allow handling assertions and statement metadata elements to indicate whether their marks apply to the encypted blob state vs. actual data by using an attribute appliesToState
Source |
    <xs:element maxOccurs="2" minOccurs="0" name="StatementMetadata">
      <xs:annotation>
        <xs:documentation>
          <p xmlns="http://www.w3.org/1999/xhtml" ism:classification="U" ism:ownerProducer="USA">Intended for access, rights, handling or other metadata that applies to the assertion statement. Use EDH security options whenever an assertion already has a unique enterprise identifer or is intended for potential extraction and should be able stand on it's own as a separate referencable object. Use arh security only when assertions are not intended to be extracted and do not require enterprise identifiers.</p>
        </xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:choice>
          <xs:element ref="edh:Edh" minOccurs="1" maxOccurs="1"/>
          <xs:element ref="edh:ExternalEdh" minOccurs="1" maxOccurs="1"/>
          <xs:element ref="arh:Security" minOccurs="1" maxOccurs="1"/>
          <xs:element ref="arh:ExternalSecurity" minOccurs="1" maxOccurs="1"/>
        </xs:choice>
        <xs:attribute name="appliesToState" type="tdfstate:CVEnumTDFAppliesToState" use="optional">
          <xs:annotation>
            <xs:documentation>
              <p xmlns="http://www.w3.org/1999/xhtml" ism:classification="U" ism:ownerProducer="USA">Used to indicate if the statement metadata applies to encrypted or unencrypted data. If a TDO payload or assertion statement is encrypted, there are in fact two potentially different markings needed for decision making, analysis and querying, one describing the handling required for the encrypted blob, and the other for the handling required for the unencrypted (and in effect external) state. In cases where statements and/or payloads are encrypted, allow handling assertions and statement metadata elements to indicate whether their marks apply to the encypted blob state vs. actual data by using an attribute appliesToState</p>
            </xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:complexType>
    </xs:element>
Schema location | IC-TDF.xsd

Complex Type AssertionType

Namespace | urn:us:gov:ic:tdf
Diagram |
Used by |
Element | AssertionGroup/Assertion
Model | StatementMetadata{0,2} , EncryptionInformation{0,1} , (StringStatement | Base64BinaryStatement | ReferenceStatement | StructuredStatement) , (Binding | ReferenceList)
Children | Base64BinaryStatement, Binding, EncryptionInformation, ReferenceList, ReferenceStatement, StatementMetadata, StringStatement, StructuredStatement
Attributes |
QName | Type | Fixed | Default | Use | Annotation
--- | --- | --- | --- | --- | ---
id | xs:ID |  |  | optional | A unique local identifier used for binding and signing purposes. Not guarenteed to be unique across multiple TDC/TDOs but must be unique within a single instance of either.
scope | restriction of xs:string |  |  | required | The grouping of objects to which the assertion applies.
type | xs:string |  |  | optional | The logical grouping to which the assertion belongs. The Assertion type attribute is intended to provide additional context, allowing various systems to pre-determine relenvance of assertions without parsing or reading all of the assertions. Type might include categorizations such as discovery, mission, or task order to allow various systems to determine which assertions are relevant for them to parse.
Source |
    <xs:complexType name="AssertionType">
      <xs:sequence>
        <xs:element maxOccurs="2" minOccurs="0" name="StatementMetadata">
          <xs:annotation>
            <xs:documentation>
              <p xmlns="http://www.w3.org/1999/xhtml" ism:classification="U" ism:ownerProducer="USA">Intended for access, rights, handling or other metadata that applies to the assertion statement. Use EDH security options whenever an assertion already has a unique enterprise identifer or is intended for potential extraction and should be able stand on it's own as a separate referencable object. Use arh security only when assertions are not intended to be extracted and do not require enterprise identifiers.</p>
            </xs:documentation>
          </xs:annotation>
          <xs:complexType>
            <xs:choice>
              <xs:element ref="edh:Edh" minOccurs="1" maxOccurs="1"/>
              <xs:element ref="edh:ExternalEdh" minOccurs="1" maxOccurs="1"/>
              <xs:element ref="arh:Security" minOccurs="1" maxOccurs="1"/>
              <xs:element ref="arh:ExternalSecurity" minOccurs="1" maxOccurs="1"/>
            </xs:choice>
            <xs:attribute name="appliesToState" type="tdfstate:CVEnumTDFAppliesToState" use="optional">
              <xs:annotation>
                <xs:documentation>
                  <p xmlns="http://www.w3.org/1999/xhtml" ism:classification="U" ism:ownerProducer="USA">Used to indicate if the statement metadata applies to encrypted or unencrypted data. If a TDO payload or assertion statement is encrypted, there are in fact two potentially different markings needed for decision making, analysis and querying, one describing the handling required for the encrypted blob, and the other for the handling required for the unencrypted (and in effect external) state. In cases where statements and/or payloads are encrypted, allow handling assertions and statement metadata elements to indicate whether their marks apply to the encypted blob state vs. actual data by using an attribute appliesToState</p>
                </xs:documentation>
              </xs:annotation>
            </xs:attribute>
          </xs:complexType>
        </xs:element>
        <xs:group ref="EncryptionInformationGroup"/>
        <xs:group ref="StatementGroup"/>
        <xs:group ref="BindingGroup" minOccurs="0"/>
      </xs:sequence>
      <xs:attribute ref="scope" use="required"/>
      <xs:attribute name="type" type="xs:string">
        <xs:annotation>
          <xs:documentation>
            <p xmlns="http://www.w3.org/1999/xhtml" ism:ownerProducer="USA" ism:classification="U">The logical grouping to which the assertion belongs. The Assertion type attribute is intended to provide additional context, allowing various systems to pre-determine relenvance of assertions without parsing or reading all of the assertions. Type might include categorizations such as discovery, mission, or task order to allow various systems to determine which assertions are relevant for them to parse.</p>
          </xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute ref="id" use="optional"/>
    </xs:complexType>
Schema location | IC-TDF.xsd

Attribute AssertionType / StatementMetadata / @appliesToState

Namespace | urn:us:gov:ic:tdf
Annotations | Used to indicate if the statement metadata applies to encrypted or unencrypted data. If a TDO payload or assertion statement is encrypted, there are in fact two potentially different markings needed for decision making, analysis and querying, one describing the handling required for the encrypted blob, and the other for the handling required for the unencrypted (and in effect external) state. In cases where statements and/or payloads are encrypted, allow handling assertions and statement metadata elements to indicate whether their marks apply to the encypted blob state vs. actual data by using an attribute appliesToState
Type | CVEnumTDFAppliesToState
Properties |
use: | optional
Facets |
enumeration | encrypted | Data that has been encrypted
enumeration | unencrypted | Data in plain text
Used by |
Element | AssertionType/StatementMetadata
Source |
    <xs:attribute name="appliesToState" type="tdfstate:CVEnumTDFAppliesToState" use="optional">
      <xs:annotation>
        <xs:documentation>
          <p xmlns="http://www.w3.org/1999/xhtml" ism:classification="U" ism:ownerProducer="USA">Used to indicate if the statement metadata applies to encrypted or unencrypted data. If a TDO payload or assertion statement is encrypted, there are in fact two potentially different markings needed for decision making, analysis and querying, one describing the handling required for the encrypted blob, and the other for the handling required for the unencrypted (and in effect external) state. In cases where statements and/or payloads are encrypted, allow handling assertions and statement metadata elements to indicate whether their marks apply to the encypted blob state vs. actual data by using an attribute appliesToState</p>
        </xs:documentation>
      </xs:annotation>
    </xs:attribute>
Schema location | IC-TDF.xsd

Attribute AssertionType / @type

Namespace | urn:us:gov:ic:tdf
Annotations | The logical grouping to which the assertion belongs. The Assertion type attribute is intended to provide additional context, allowing various systems to pre-determine relenvance of assertions without parsing or reading all of the assertions. Type might include categorizations such as discovery, mission, or task order to allow various systems to determine which assertions are relevant for them to parse.
Type | xs:string
Properties |
content: | simple
Used by |
Complex Type | AssertionType
Source |
    <xs:attribute name="type" type="xs:string">
      <xs:annotation>
        <xs:documentation>
          <p xmlns="http://www.w3.org/1999/xhtml" ism:ownerProducer="USA" ism:classification="U">The logical grouping to which the assertion belongs. The Assertion type attribute is intended to provide additional context, allowing various systems to pre-determine relenvance of assertions without parsing or reading all of the assertions. Type might include categorizations such as discovery, mission, or task order to allow various systems to determine which assertions are relevant for them to parse.</p>
        </xs:documentation>
      </xs:annotation>
    </xs:attribute>
Schema location | IC-TDF.xsd

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