Schema documentation for component StructuredValueType

Namespace

urn:us:gov:ic:tdf

Annotations

Intended for structured content encoded in the same data encoding of the encapsulating TDO (i.e. If the encoded format is XML this is intended for XML values). For signable StructuredValueType elements, it can be safer to declare namespaces locally to the section being signed to reduce risk in moving sections between documents. Explicit namespace declarations should be used and c14n11 normalization should be preferred when signing since c14n11 normalization does not perform any namespace re-writing and as a result, signed assertions can not be copied between documents unless the namespaces used are identical, or the assertion locally overrides them. Older c14n 1.0 has two approaches to namespace re-writing, either of which could in some circumstances break signatures when copying signed assertions between documents.

Diagram

Used by

Element

StatementGroup/StructuredStatement

Model

( CdsManifestAssertion | AnalysisAssertion )

Children

AnalysisAssertion , CdsManifestAssertion

Attributes

QName	Type	Use	Annotation
id	restriction of 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.

Source

<xs:complexType name="StructuredValueType">
  <xs:annotation>
    <xs:documentation>
      <p xmlns="http://www.w3.org/1999/xhtml" ism:classification="U" ism:ownerProducer="USA">Intended for structured content encoded in the same data encoding of the encapsulating TDO (i.e. If the encoded format is XML this is intended for XML values). For signable StructuredValueType elements, it can be safer to declare namespaces locally to the section being signed to reduce risk in moving sections between documents. Explicit namespace declarations should be used and c14n11 normalization should be preferred when signing since c14n11 normalization does not perform any namespace re-writing and as a result, signed assertions can not be copied between documents unless the namespaces used are identical, or the assertion locally overrides them. Older c14n 1.0 has two approaches to namespace re-writing, either of which could in some circumstances break signatures when copying signed assertions between documents.</p>
    </xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <!--Replacing:
<xs:any namespace="##other" processContents="skip"/>
-->
    <!-- CdsManifest: Remove xs:any and force assertion to be cdsm:CdsManifestAssertion or anlys:AnalysisAssertion and keep Xsat Happy.  -->
    <xs:choice>
      <xs:element ref="cdsm:CdsManifestAssertion"/>
      <xs:element ref="anlys:AnalysisAssertion"/>
    </xs:choice>
  </xs:sequence>
  <xs:attribute ref="id" use="optional"/>
  <!--Replacing:
<xs:attribute ref="filename" use="optional"/>
-->
  <!-- CdsManifest: Remove attribute filename since nothing it was only used for Base64 and String which were tailored out.  -->
  <!--Replacing:
<xs:attribute ref="isEncrypted" use="optional"/>
-->
  <!-- CdsManifest: Remove attribute isEncrypted since nothing in CdsManifest allows encryption.  -->
</xs:complexType>

Schema location

CDSM-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.

Showing:

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