Validate message content rule area (container)

Rule Name:

Replace any tabs in message body with 3 spaces

Position:

Under: Validate message content rule area

Name:

MSG_RemoveTabs

Default:

Checked

Usage:

The message body field is parsed and any occurrences of tab characters are replaced with three spaces. Spaces are preferred over tabs so that when printed in a mono-spaced type the listing appears correct.  If changes were made, a note is added to the log and displayed. 

Rule Name:

Replace any non-ASCII chars (values >127) with pure ASCII

Position:

Under: Validate message content rule area

Name:

MSG_JustASCII

Default:

Checked

Usage:

The message body field is parsed and any occurrences of characters with hex values above 127 are replaced. The replacement strings are taken from similar characters when possible (for example, the right hanging quote symbol is replaced with a straight quote).  If changes were made, a note is added to the log and displayed. 

Rule Name:

Indent trailing lines in structure by 3 spaces (pretty print)

Position:

Under: Validate message content rule area

Name:

MSG_IndentLines

Default:

Checked

Usage:

The message body field is parsed and all lines following after the first line are indented at least three spaces to present some white space along the left edge of the listing.  A rather primitive pretty print.  If changes were made, a note is added to the log and displayed. 

Rule Name:

Remove duplicative ASN name entries when found in the message body

Position:

Under: Validate message content rule area

Name:

Remove_DupeNames2

Default:

Checked

Usage:

If the proper name of the entry appears in both the ASN name field and the message body field, it is removed from the 2^nd field as well as the delimiter.  If changes were made, a note is added to the log and displayed.

Rule Name:

Error on multiple ASN entries per single record

Position:

Under: Validate message content rule area

Name:

MSG_MultiEntry

Default:

Checked

Usage:

It is allowed to have only one complete ASN entry per record, more than this is problematic, even if the definitions are simply the “stubs” of what is defined above.  This rule checks for this occurrence by the very primitive means of detecting multiple “::=” patterns in the listing.  If found, a warning is given.

Rule Name:

Align start and end brackets on separate lines

Position:

Under: Validate message content rule area

Name:

MSG_Align

Default:

UN-Checked (not released)

Usage:

Not yet defined.

This rule has not yet been completed.

Rule Name:

Indent each element entry by 3 spaces

Position:

Under: Validate message content rule area

Name:

MSG_Indent

Default:

UN-Checked (not released)

Usage:

Not yet defined.

This rule has not yet been completed.

Rule Name:

Check for (illegal) content in the DataType field and moves it, if found 

Position:

Under: Validate message content rule area

Name:

MSG_DataType

Default:

Checked

Usage:

Looks for any content in the data type field (which should be empty in this record type) and if found nags the user about it.  It may move the data type to the message body field if that seems logical based on the contents.  If changes are made, a summary is given.

Rule Name:

Warn on finding unlimited SEQUENCE OF streams

Position:

Under: Validate message content rule area

Name:

MSG_SeqLimits

Default:

Checked

Usage:

Looks at the message body for any content where a SEQUENCE OF occurs without any boundary or restriction information on its allowed length.  Such use is strongly frowned upon in ITS because a message with this encoding cannot be fully tested (it could be in infinite length).  If found, a warning is given.

Rule Name:

Require 2 part declarations [instance TypeDef form]

Position:

Under: Validate message content rule area

Name:

MSG_RequireNames

Default:

UN-Checked (not released)

Usage:

Not yet defined.
This rule has not yet been completed.

Rule Name:

Align each element and type def (pretty print)

Position:

Under: Validate message content rule area

Name:

MSG_AlignContent

Default:

UN-Checked (not released)

Usage:

Not yet defined.

This rule has not yet been completed.

Rule Name:

Auto add XML Local Content Keyword after each ...

Position:

Under: Validate message content rule area

Name:

MSG_LocalContent

Default:

UN-Checked (not released)

Usage:

Not yet defined.

This rule has not yet been completed.

Rule Name:

Force element comments to next line, aligned with TypeDef

Position:

Under: Validate message content rule area

Name:

MSG_Comments

Default:

UN-Checked (not released)

Usage:

Not yet defined.

This rule has not yet been completed.

Rule Name:

Run ASN.1 complier to validate entry (slow)

Position:

Under: Validate message content rule area

Name:

MSG_Validate

Default:

UN-Checked (not released)

Usage:

Not yet defined.

This rule has not yet been completed.

Rule Name:

Warn when unable to link to included elements

Position:

Under: Validate message content rule area

Name:

MSG_Links

Default:

UN-Checked (not released)

Usage:

Not yet defined.

This rule has not yet been completed.

Rule Name:

Process in-line element declarations using Data Type rules (above)

Position:

Under: Validate message content rule area

Name:

MSG_Locals

Default:

UN-Checked (not released)

Usage:

Not yet defined.

This rule has not yet been completed.

Rule Name:

Add element names to local dictionary

Position:

Under: Validate message content rule area

Name:

MSG_Terms

Default:

UN-Checked (not released)

Usage:

Not yet defined.

This rule has not yet been completed.