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

Element AssertionGroup / HandlingAssertion

Namespace | urn:us:gov:ic:tdf
Annotations | A specific type of assertion designed to be used for access, rights, and handling instructions. It is expected that handling instructions should never have metadata about themselves and they should never be encrypted. Therefore, unlike regular assertions, handling assertions do not support statement metadata or encryption.
Diagram |
Type | HandlingAssertionType
Properties |
content | complex
minOccurs | 0
maxOccurs | unbounded
Model | HandlingStatement , ( Binding+ | ReferenceList )
Children | Binding , HandlingStatement , ReferenceList
Instance |
    <HandlingAssertion appliesToState="" id="" scope="" xmlns="urn:us:gov:ic:tdf">
      <HandlingStatement>{1,1}</HandlingStatement>
      <Binding>{1,unbounded}</Binding>
      <ReferenceList>{1,1}</ReferenceList>
    </HandlingAssertion>
Attributes |
QName | Type | 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 encrypted blob state vs. actual data by using an attribute appliesToState
id | xs:ID | optional | A unique local identifier used for binding and signing purposes. Not guaranteed 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. Please see the "Assertion Scopes" section in the DES document for more information.
Source |
    <xs:element name="HandlingAssertion" type="HandlingAssertionType" maxOccurs="unbounded" minOccurs="0">
      <xs:annotation>
        <xs:documentation>
          <p xmlns="http://www.w3.org/1999/xhtml" ism:classification="U" ism:ownerProducer="USA">A specific type of assertion designed to be used for access, rights, and handling instructions. It is expected that handling instructions should never have metadata about themselves and they should never be encrypted. Therefore, unlike regular assertions, handling assertions do not support statement metadata or encryption.</p>
        </xs:documentation>
      </xs:annotation>
    </xs:element>
Schema location | BASE-TDF.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.

Element AssertionGroup / Assertion

Namespace | urn:us:gov:ic:tdf
Annotations | Used to express metadata about the objects expressed in the scope attribute of the assertion. An assertion also supports metadata about the assertion statement for the purposes of indicating any handling instructions pertinent to the statement itself. Also supports encrypted statements and binding the statement with objects in its scope.
Diagram |
Type | AssertionType
Properties |
content | complex
minOccurs | 0
maxOccurs | unbounded
Model | StatementMetadata{0,2} , EncryptionInformation* , ( StringStatement | Base64BinaryStatement | ReferenceStatement | StructuredStatement ) , ( Binding+ | ReferenceList )
Children | Base64BinaryStatement , Binding , EncryptionInformation , ReferenceList , ReferenceStatement , StatementMetadata , StringStatement , StructuredStatement
Instance |
    <Assertion id="" scope="" type="" xmlns="urn:us:gov:ic:tdf">
      <StatementMetadata appliesToState="">{0,2}</StatementMetadata>
      <EncryptionInformation sequenceNum="">{0,unbounded}</EncryptionInformation>
      <StringStatement filename="" id="" isEncrypted="">{1,1}</StringStatement>
      <Base64BinaryStatement filename="" id="" isEncrypted="" mediaType="">{1,1}</Base64BinaryStatement>
      <ReferenceStatement id="" isEncrypted="" mediaType="" totalBlocks="" uri="">{1,1}</ReferenceStatement>
      <StructuredStatement filename="" id="" isEncrypted="">{1,1}</StructuredStatement>
      <Binding>{1,unbounded}</Binding>
      <ReferenceList>{1,1}</ReferenceList>
    </Assertion>
Attributes |
QName | Type | Use | Annotation
--- | --- | --- | ---
id | xs:ID | optional | A unique local identifier used for binding and signing purposes. Not guaranteed 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. Please see the "Assertion Scopes" section in the DES document for more information.
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 relevance 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:element name="Assertion" type="AssertionType" maxOccurs="unbounded" minOccurs="0">
      <xs:annotation>
        <xs:documentation>
          <p xmlns="http://www.w3.org/1999/xhtml" ism:classification="U" ism:ownerProducer="USA">Used to express metadata about the objects expressed in the scope attribute of the assertion. An assertion also supports metadata about the assertion statement for the purposes of indicating any handling instructions pertinent to the statement itself. Also supports encrypted statements and binding the statement with objects in its scope.</p>
        </xs:documentation>
      </xs:annotation>
    </xs:element>
Schema location | BASE-TDF.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.

Element Group AssertionGroup

Namespace | urn:us:gov:ic:tdf
Annotations | The group of possible Assertion elements in a TDO or TDC.
Diagram |
Used by |
Complex Types | TrustedDataCollectionType , TrustedDataObjectType
Model | HandlingAssertion* , Assertion*
Children | Assertion , HandlingAssertion
Source |
    <xs:group name="AssertionGroup">
      <xs:annotation>
        <xs:documentation>
          <p xmlns="http://www.w3.org/1999/xhtml" ism:ownerProducer="USA" ism:classification="U">The group of possible Assertion elements in a TDO or TDC.</p>
        </xs:documentation>
      </xs:annotation>
      <xs:sequence>
        <xs:element name="HandlingAssertion" type="HandlingAssertionType" maxOccurs="unbounded" minOccurs="0">
          <xs:annotation>
            <xs:documentation>
              <p xmlns="http://www.w3.org/1999/xhtml" ism:classification="U" ism:ownerProducer="USA">A specific type of assertion designed to be used for access, rights, and handling instructions. It is expected that handling instructions should never have metadata about themselves and they should never be encrypted. Therefore, unlike regular assertions, handling assertions do not support statement metadata or encryption.</p>
            </xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="Assertion" type="AssertionType" maxOccurs="unbounded" minOccurs="0">
          <xs:annotation>
            <xs:documentation>
              <p xmlns="http://www.w3.org/1999/xhtml" ism:classification="U" ism:ownerProducer="USA">Used to express metadata about the objects expressed in the scope attribute of the assertion. An assertion also supports metadata about the assertion statement for the purposes of indicating any handling instructions pertinent to the statement itself. Also supports encrypted statements and binding the statement with objects in its scope.</p>
            </xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:group>
Schema location | BASE-TDF.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