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.
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.
Used to denote if contents
are encrypted. When this optional attribute is absent, it is assumed to be
false.
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><xs:any namespace="##other" processContents="skip"/></xs:sequence><xs:attribute ref="id" use="optional"/><xs:attribute ref="filename" use="optional"/><xs:attribute ref="isEncrypted" use="optional"/></xs:complexType>
Schema location
IC-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