603-05 : EDGAR Filer Manual v65 6.3.5 page 6-7

Created by: SEC Office of Structured Disclosure

The ampersand character

The ampersand character must begin a valid XML predefined entity or numeric character reference. XML with invalid predefined entity or numeric character references are treated as if an invalid character had appeared. For example, &&; is invalid XML.

REMARK: the files e60305001ng-20111231.xml and e60305002ng-20111231_lab.xml are not even good XML, so don't try to process them as such.

REMARK: this testcase is also a convenient place to test compliance with EFM section 5.2 listing a few common but disallowed characters.

Variations

Number Name Description References Data Inputs Result Outputs
_001ng Instance has bad XML (€) in footnote, NOGOOD. Tests that incorrect characters are caught, NOGOOD.    
_002ng Label linkbase has bad XML (€) in label, NOGOOD. Tests that incorrect characters are caught, NOGOOD.    
_003gd Instance has one of every legal EDGAR character, GOOD. Tests that legal EDGAR characters are allowed, GOOD.  
    valid
 
_004ng 6.3.5, Instance has the bad Character no-break space (hex 7F), NOGOOD. Instance has the bad Character no-break space (hex 7F); tests where exactly that is caught in the processing pipeline, NOGOOD.    
_005ng 6.3.5, Instance has the EDGAR disallowed Character circumflex (hex 5E), NOGOOD. Instance has the EDGAR disallowed Character circumflex (hex 5E); tests where exactly that is caught in the processing pipeline, NOGOOD.    
_006ng 6.3.5, Instance has the EDGAR disallowed BOM mark, NOGOOD. Instance has the EDGAR disallowed BOM mark (first three bytes), and tests where exactly that is caught in the processing pipeline, NOGOOD.