Browse Prior Art Database

ImagePointe™ File Image Identifyer, Analyzer & Interpreter Disclosure Number: IPCOM000172984D
Publication Date: 2008-Jul-23
Document File: 3 page(s) / 77K

Publishing Venue

The Prior Art Database


ImagePointe™ is a file type interpreter developed to: provide a single application to interpret a variety of file formats; provide a text based interface that is compatible in any environment; restrict viewing of the actual images for privacy and security concerns; identify data anomalies; and, conversion from one file format to different, compatible, file types.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 3


© 2008 Viewpointe Archive Services, LLC. All rights reserved.

May not be copied or distributed without express written permission.

[This page contains 2 pictures or other non-text objects]

Page 2 of 3

ImagePointe was developed to provide support information for troubleshooting image files used as part of

Viewpointe's business processes. ImagePointe's development was guided by several business & technical


  Provide a single application that would interpret a variety of file formats
Provide a text based interface that could be used in any environment
Restrict viewing of actual images due to privacy and security concerns
Provide a consistent interface that could be used to determine if a file is correctly formatted
Provide an ability to drill down to individual items to look for data anomalies that would cause process

  failure within the business.
Provide an ability to convert from one file format to a different, compatible, file type. Certain conversions,

by necessity, are either one-way or are restricted from one type of file to another. This is due to data

loss occurring during the conversion making it impossible to recover the original file.

ImagePointe accomplishes the above business & technical requirements by using a flexible object model

with the following components:

A file type interpreter that analyzes the contents of the file and from that determines which of the

supported type models is compatible with the given file. The algorithm does not rely on a filename or a

file extension because files can be mislabeled causing production issues; so the internal structure of the

  file is used to look for known patterns.
Each time a new file type is added to the supported list, the model provides for an identification algorithm

  to identify files of the new type.
File type models can be hieratical; for example, a TIFF image model can be contained within another file

type. This way any file type that has a TIFF formatted image embedded in it can provide information

  about the TIFF as well as the parent file type
Several file type models allow for sibling files to be logically merged. The relationship between the files

is dictated by a filename convention. This occurs most often when metadata and images are stored in

  separate but logically connected files.
When sibling files are involved, ImagePointe can work with either pair if only one is available, or merge

the two files into a single virtual file. The appropriate menu options will appear to the user based on what

  has been parsed.
Each file type model has built in verification rules that produce warnings to the user if the file format does

not meet industry standards. This could include verification of trailer counts, bounds checking of

particular parameters, completeness of sibling files, or any other metric that could impact...