data.schemas.5.0.NTK.IC-NTK.xsd Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of ddmsence Show documentation
Show all versions of ddmsence Show documentation
DDMSence (pronounced "dee-dee-em-Essence") is the only open-source Java library that fully supports the
DoD Discovery Metadata Specification (DDMS).
The newest version!
Intelligence Community Technical Specification XML Data Encoding Specification for
Need-To-Know Metadata (NTK.XML)
Notices
distEditionBlockReplace
Description
W3C XML Schema for the XML Data Encoding Specification for intelligence Need-To-Know
metadata (NTK.XML).
Introduction
This XML Schema file is one component of the XML Data Encoding Specification (DES).
Please see the document titled
XML Data
Encoding Specification For Need-To-Know Metadata
for a complete
description of the encoding as well as list of all components.
It is envisioned that this schema or its components, as well as other parts of the
DES may be overridden for localized implementations. Therefore, permission to use,
copy, modify and distribute this XML Schema and the other parts of the DES for any
purpose is hereby granted in perpetuity.
Please reference the preceding two paragraphs in all copies or variations. The
developers make no representation about the suitability of the schema or DES for any
purpose. It is provided "as is" without expressed or implied warranty.
If you modify this XML Schema in any way label your schema as a variant of NTK.XML.
Please direct all questions, bug reports,or suggestions for changes to the points of
contact identified in the document referenced above.
Implementation Notes
The document element for NTK is ntk:Access . However, the NTK schema is not a standalone construct; it
should be imported into a parent XML schema.
Creators
Office of the Director of National Intelligence Intelligence Community Chief
Information Officer
A way of describing a formalized Need to Know required for a
document. NTK requires being inside a schema that implements ISM therefore some
element in the implementing schema MUST have ism:ISMRootNodeAttributeGroup and
ism:ResourceNodeAttributeGroup since both of those are required for a valid ISM
implementation. In addition the root node of the implementing schema must have
ntk:NTKRootNodeAttributeGroup specified.
A way of describing a formalized Need to Know required for an EXTERNAL
document. NTK requires being inside a schema that implements ISM therefore some
element in the implementing schema MUST have ism:ISMRootNodeAttributeGroup and
ism:ResourceNodeAttributeGroup since both of those are required for a valid ISM
implementation. In addition the root node of the implementing schema must have
ntk:NTKRootNodeAttributeGroup specified.
A system name followed by 1 or more group values representing the
groups that a user wanting access to the document must be a member of. Logic for the
group list being boolean AND vs OR is System defined.
A string representing a group, the string must be portion marked.
A system name followed by 1 or more Individual values representing
the people that a user wanting access to the document must be a member of.
A string representing a person, the string must be portion marked.
A system name followed by 1 or more values representing a profile
that a user wanting access to the document must meet. Logic for the profile list
being boolean AND vs OR is System defined.
A list of words, codes and/or phrases: a
lexicon.
The version number of the DES
A unique XML identifier used to assign an XML
unique identifier to an element, such as a paragraph, note or table.
A cross-reference to a unique identifier used to
point from one element to one or more other elements. The value of the attribute
must be one or more XML unique identifiers that are the value(s) of id
attribute(s) elsewhere in the document.
A user-defined property within an element for
general purpose processing used with block objects to provide supplemental
information over and above that conveyed by the element name. This attribute is
analogous to HTML's "class" attribute.
Used for portion marking access requirements with a format of a
namespace-prefix followed by sets of key-value pairs. The '|'
character is used to separate the key-value pairs and the '^'
character is used to join keys with their values. Multiple
namespace-prefixed sets can be used.
For example:
ntk:access="namespace1|key1^value1|key2^value1|key2^value2"
ntk:access="namespace1|key1^value1 namespace2|key1^value1|key2^value2"
ntk:access="namespace1|key1^value1|key2^val2 namespace1|key1^value3"
Formal Change List
Change History
Version
Date
By
Description
7
2012-5-28
ODNI/OCIO/ME/D&I
Updated NTK attribute to use a schema restriction regex instead of schematron rule NTK-ID-00005 [artf12287].
7
2012-4-06
ODNI/OCIO/ME/D&I
Add NTK attribute for use on portions [artf12287].
7
2012-3-19
ODNI/OCIO/ME/D&I
Changed DESVersion
attribute from xsd:int to ism:ShortStringType.
Changed declaration of AccessProfileValueType to be simple content. [artf12153].
6
2011-12-13
Hodges, ODNI/OCIO/ICEA
Extracting out attributes and elements to move towards NIEM
compliance
5
2011-07-07
Colbert, ODNI/OCIO/ICEA
Added version information to header
4
2011-04-22
Colbert, ODNI/OCIO/ICEA
Explicitly declared minOccurs and maxOccurs where
appropriate.
3
2011-01-31
Sun, ODNI/OCIO/ICEA
(CR 2011-01) Remove unused ddms namespace declaration