04.04.2013 Views

ANSI/NIST-ITL 2-2008 - National Institute of Standards and ...

ANSI/NIST-ITL 2-2008 - National Institute of Standards and ...

ANSI/NIST-ITL 2-2008 - National Institute of Standards and ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Part 2 <strong>ANSI</strong>/<strong>NIST</strong>-<strong>ITL</strong> 2-<strong>2008</strong><br />

210.1.4 Element <br />

Cross-reference: Part 1, Section 10.1.3 Fields 2.003 <strong>and</strong> above: User-defined fields<br />

This is a optional complex element. The user-defined content elements are nested within, as<br />

described in the subsections below.<br />

<br />

[. . . Domain <strong>and</strong> other descriptive elements . . .]<br />

<br />

210.1.4.1 Element <br />

This element shall only contain content defined by the Domain owner specified in the Type-1<br />

record element . Individual XML elements, required for given<br />

transaction types, including tag names <strong>and</strong> content, shall conform to the specifications set forth<br />

by the agency to whom the exchange package is being sent. Each user-defined XML element<br />

used in the Type-2 record <strong>and</strong> its format shall conform to the requirements contained in Section<br />

208.2.2.<br />

Complex element is abstract, <strong>and</strong> as such is unusable by<br />

itself. Implementers should define, in an extension schema, a substitution element containing<br />

user-defined child elements from the user’s domain.<br />

A substitution element should be defined in a user’s extension schema similar to this:<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

The element would then appear in an instance document like this:<br />

<br />

Text<br />

Text<br />

<br />

210.1.4.2 Element <br />

This element shall contain additional content not defined by a Domain owner, but necessary for<br />

information exchange between certain parties. Individual XML elements, required for given<br />

transaction types, including tag names <strong>and</strong> content, shall conform to the specifications set forth<br />

by the agency to whom the exchange package is being sent. Each user-defined XML element<br />

35

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!