Configuration and Testing Results - Fax Connect II
Company : __________________________
Profiles:
Feature Set |
Requirement Level |
Condition |
Support |
Interworking |
||||
Section 2: TIFF and Fax |
||||||||
Required Tiff Fields (2.2.1) |
MUST |
1. Support is provided for all required TIFF fields whose values are not mode dependent |
|
|
||||
Additional Required TIFF Fields for Fax (2.2.2) |
MUST |
2. Support is provided for all additional TIFF fields that are required for Fax, but whose values are mode dependent |
|
|
||||
Recommended Fields (2.2.3) |
MAY |
3. Support is provided for recommended TIFF fields (please specify field names).
|
|
|
||||
New Fields (new) |
MAY |
4, Support is provided for new fields (please specify field names and applicable profiles per field)
|
|
|
||||
Section 3: Minimal Black-and-White Fax Mode (Profile S) |
||||||||
Profile S (3.) |
MUST |
5. Support is provided for a Profile S Writer |
|
|
||||
MUST |
6. Support is provided for a Profile S Reader |
|
|
|||||
Profile S Fields (3.1.1, 3.1.2) |
MUST |
7. Support is provided for the additional required fields for Profile S |
|
|
||||
RTC Exclusion (3.4.1) |
SHOULD NOT |
8. Implementations which wish to maintain strict conformance with TIFF and compatibility with the historical use of TIFF for fax SHOULD NOT include the RTC sequence when writing TIFF files. |
|
|
||||
MAY |
9. Implementations which need to support "transparency" of T.4-generated image data MAY include RTCs when writing TIFF files if the flag settings of the T4Options field are set for non-byte aligned data |
|
|
|||||
MUST/ |
10. Minimal set readers MUST be able to process files which do not include RTCs and SHOULD be able to process files which do include RTCs. |
|
|
|||||
File Structure (3.5) |
MUST |
11. Support provided for required Profile S file structure, including LSByte-first order (little- endian) byte order and mandatory ordering of IFDs, long fields, and image data. |
||||||
File Summary (3.6) |
MUST |
12. The Baseline and Extension fields and field values MUST be supported by all implementations. |
|
|
||||
Section 4. Extended Black-and-White fax mode (Profile F) |
||||||||
F Profile (4.) |
MAY |
13. Support is provided for Profile F Reader |
|
|
||||
MAY |
14. Support is provided for a Profile F Writer |
|
|
|||||
Required Fields (4.2) |
MUST |
15. Support is provided for the required Profile F fields and legal values are used. |
|
|
||||
Guidelines (4.4.6) |
SHOULD |
16. Support is provided for the guidelines for reading and writing Profile F files. |
|
|
||||
Section 5: Lossless JBIG Black-and-White Fax Mode (Profile J) |
||||||||
J Profile (5.) |
MAY |
17. Support is provided for Profile J Reader: |
|
|
||||
MAY |
18. Support is provided for a Profile J Writer: |
|
|
|||||
MUST |
19. Support is provided for the required Profile J fields and legal values are used. |
|
|
|||||
Section 6: Base Color Fax Mode (Profile C) |
||||||||
C Profile (6.) |
MAY |
19. Support is provided for Profile C Reader: |
|
|
||||
MAY |
20. Support is provided for a Profile C Writer: |
|
|
MUST |
21. Support is provided for the required Profile C fields and legal values are used. |
|
|
|
Section 7: Lossless Color Mode (Profile L) |
||||||||
L Profile (7.) |
MAY |
22. Support is provided for Profile L Reader: |
|
|
||||
MAY |
23. Support is provided for a Profile L Writer: |
|
|
|||||
MUST |
24. Support is provided for the required Profile L fields and legal values are used. |
|
|
|||||
Section 8: Mixed Raster Content Mode (Profile M) |
||||||||
M Profile (8.) |
MAY |
25. Support is provided for Profile M Reader: |
|
|
||||
MAY |
26. Support is provided for a Profile M Writer: |
|
|
|||||
MUST |
27. Support is provided for the required Profile M fields and legal values are used. |
|
|