This patent application is assigned to 3s International, Llc.
The following quote was obtained by the news editors from the background information supplied by the inventors: "Content management systems are widely utilized to manage the ever increasing volume of digital data assets of organizations. Digital data assets can be categorized into 2 different categories: structured and unstructured. Although there is no strict line separating the two, structured data normally can be processed by computers while unstructured data normally requires direct human interactions. Typical examples of structured data are information stored in relational database tables. Typical examples of unstructured data are digital documents such as PDF documents, Microsoft Office documents, digital pictures, scanned images, AutoCAD drawings, video and voice recording etc. Typically, human intelligence is required process, utilize and comprehend the content of unstructured digital data. Content management systems use special software applications called content viewers to provide the interface between humans and the unstructured data, allowing human users to carry out activities including, but not limited to, displaying (or playing in the case of an audio or audiovisual document), viewing, processing, printing, annotating, play and collaborating on the documents.
"There are many content viewers available. Some content viewers are created to handle documents in a specific format, such as Adobe Acrobat and Adobe Reader. Some content viewers are created to display various formats of documents, such as commercially available content viewers from IGC, Daeja and Snowbound. Some of the content viewers are standalone applications, while others are browser plug-ins built on top of various browser plug-in technologies. Some content viewers rely on servers to render the documents for display, while others render the documents in their native formats within the viewer itself.
"Modern content viewers come with a lot more features than simply displaying the documents. Annotation is one of the most important features that many industry leading content viewers provide. This is because annotations provide extra information visually on top of the document content displayed in a content viewer, thus allowing end users to comment and collaborate with other users using annotations. Annotations are also referred to as markups. The action to put annotations on top of a document displayed in a content viewer is commonly referred to as annotating or marking up. There are many types of annotation marks that can be applied to a document, including, but not limited to, lines, arrows, different shapes (rectangles, circles, ovals, polygons etc), polylines, freehand drawings, text, sticky notes, rubber stamps, redactions etc. They provide different ways to annotate or mark up documents. Annotation marks may look as though they are part of the document content when displayed within a content viewer, although annotation contents are normally stored separately from the documents that they are applied to.
"Each separate annotation applied to a document is commonly referred to as an annotation object. Each annotation object defines a few user interface attributes such as position, size, shape, color, transparency, orientation, font and the text if the annotation is textual. Each annotation object also defines some attributes that are not explicitly user interface related, for instance page index to indicate on which page of the document the annotation object has been applied. Some annotation objects carry information such as the name of the user who created the annotation object, and the date/time the annotation object was created. Certain of this information helps the document custodian manage the security of the annotation objects. Annotations are overlaid on top of the document. They can be seen as part of the document content displayed from within a content viewer.
"Although annotation data is normally persisted as separate content from the document content in a content management repository, annotation objects are not standalone objects. Annotation data is meaningless without the context of the document content that they are applied to.
"Due to lack of international standards, the formats of annotation contents are proprietary to the content viewers used to generate the annotation contents. Each content viewer has its own native format for annotation contents to be displayed in the viewer. Some annotation contents are pure text, some are XML based, and some are even binary. Although most industry leading content viewers support some common annotation types such as lines, arrows, rectangles, oval, freehand, text etc, the definitions of these common types are often different from one annotation format to another. Some formats may support a few annotation types that other formats do not support. Additionally, different annotation formats may have different units, schemes and specifications for annotation attributes such as page index, annotation object index, date & time, line width, color, font size, coordinates, binary data encoding schemes, text encoding schemes etc. Annotation contents created from one viewer are often not compatible with annotation contents from another viewer. This situation creates serious issues when an organization decides to switch from one content viewer to another, or uses more than one type of content viewer simultaneously across a content management system. Annotation contents generated from one content viewer are usually not visible from another content viewer. From the end user's perspective this is a data loss scenario. Today, annotation data loss is one of the top concerns for organizations when they consider switching content viewers.
"This invention provides a systematic approach to the annotation data loss issue described above. Methods and apparatus for annotation content conversions are revealed in order to prevent annotation data loss to the level of physically possible with various levels of implementation efforts across a content management system. This invention also brings the transparency into annotation contents among different components of a content management system."
In addition to the background information obtained for this patent application, VerticalNews journalists also obtained the inventor's summary information for this patent application: "One embodiment of this invention provides a method for annotation content conversions. With the introduction of an intermediary annotation format, comprising an interface for converting an annotation originally applied in any of a variety of annotation formats to a standard intermediary annotation format, and an interface for converting annotations persisted in the standard intermediary format to any of several target formats, the implementation of annotation content conversions from annotation content of the source format to the annotation content of the target format can be modularized, and the annotation content conversions become by-directional. One advantage of this approach is that it results in significant reduction of redundant code when conversions are required among more than two annotation formats.
"Another embodiment of this invention provides a method for storing annotation content in a content management repository. An annotation storage format and on demand annotation conversion apparatus unifies the annotation contents generated from different content viewer. This makes searching annotation contents easier to implement for a content management system, by enhancing the transparency of annotation contents which would otherwise have been a black box to other components of a content management system.
"Another embodiment of the invention provides an apparatus for converting all annotation contents in an annotation content repository created by content viewer A to corresponding annotation contents in the format native to content viewer B, so that after content viewer A is replaced by viewer B in the content management system, legacy annotation contents are still retained and displayable from within content viewer B. Annotation contents conversion is performed directly against the annotation content repository in the fashion of batch processing without the requirement of the presence of both content viewers. The conversion process creates new annotation contents in the content management repository, and relationships between annotation contents and the associated document contents are retained during the process of the conversion.
"Another embodiment of the invention provides an apparatus for converting annotation contents on demand as requested by the client specifically but not limited to the content viewer. This embodiment can be integrated into application servers, content servers, or annotation servers, from where annotation contents are delivered to the requesting clients. This embodiment can also be integrated into a client side component including but not limited to content viewer plug-ins, and image rendering servers where annotation contents are rendered on top of the document content. This embodiment is able to handle differences between the annotation format native to content viewers and the formats of annotations stored in the annotation content repository.
BRIEF DESCRIPTION OF THE DRAWINGS
"It is to be noted that the appended drawings illustrate only the typical embodiments of this invention and are therefore not to be considered limiting of its scope, for the invention may admit to other equally effective embodiments.
"FIG. 1 illustrates one embodiment of this invention with the annotation conversion tool deployed and connected directly to the annotation content repository of a content management system. The annotation conversion tool, after execution, converts all annotation contents of a specified format stored in the annotation repository of a content management system to corresponding annotation contents of another specified format in the fashion of batch processing.
"FIG. 2A illustrates another embodiment of this invention being used in a content management system where an application server, or a content server, or both are responsible for processing annotation content requests initiated from the client side and delivering the requested annotation contents to the requesting clients. With the implementation and integration of the annotation conversion library, requested annotation contents get converted from the format stored in the annotation content repository to the format that the clients request in the fashion of on-demand processing.
"FIG. 2B illustrates another embodiment of this invention being used in a content management system where a dedicated annotation server is responsible for processing annotation content request from the client side and delivering the requested annotation contents to the requesting clients. With the implementation and integration of the annotation conversion library, requested annotation contents get converted from the format stored in the annotation content repository to the format that the clients request in the fashion of on-demand processing.
"FIG. 2C illustrates another embodiment of this invention being used in a content management system where annotation contents of a unified storage format are stored in the annotation content repository and an application server, or a content server or both are responsible for handling and delivering annotation content requests initiated from content viewers. With the implementation and integration of the annotation conversion library, requested annotation contents get converted from the storage format to the format that the content viewers requests before delivering them to the content viewers for display. Also annotation contents generated from within the content viewers are converted from the format native to the content viewer to the storage format before the annotation contents are saved into the annotation content repository.
"FIG. 3 illustrates another embodiment of this invention being used in a content management system where the client side specifically but not limited to content viewers making annotation content requests from the server side which delivers annotation contents of unspecified format. With,the implementation and integration of the annotation conversion library, annotation contents delivered from the server side get detected on the fly and converted to the native format that the content viewer is able to recognize and display.
"FIG. 4A shows multiple annotation contents are stored in the annotation content repository of a content management system. Single annotation content may contain one or more annotation objects.
"FIG. 4B shows an annotation object having many attributes.
"FIG. 5 illustrates annotation object conversion process comprised of many sub-conversions of the values of annotation attributes with different unit systems, schemes and specifications between two different annotation content formats.
"FIG. 6 is a flowchart illustrating the batch processing of annotation content conversions of annotation contents in a content management repository.
"FIG. 7 is a flowchart illustrating the conversion of single annotation content from format A to format B in accordance with one embodiment of the present invention.
"FIG. 8 is a flowchart illustrating the conversion of annotation content by dynamically detecting the input format in accordance with one embodiment of the present invention.
"FIG. 9A illustrates direct annotation content conversion from format A to format B.
"FIG. 9B illustrates the two-step conversion method for by-directional and modularized annotation content conversion among multiple annotation formats.
"FIG. 10 illustrates a sample high level implementation of annotation content from format A to format B."
URL and more information on this patent application, see: He, Xiaopeng. Method and Apparatus for Annotation Content Conversions. Filed
Keywords for this news article include: 3s International Llc., Information Technology, Information and Data Aggregation, Information and Data Loss and Recovery.
Our reports deliver fact-based news of research and discoveries from around the world. Copyright 2014, NewsRx LLC
Most Popular Stories
- Top Hispanic Tech Companies Push for the Top
- 5 Notable Hispanic Technology Executives
- FAA to Appeal Court Decision Allowing Commercial Drone Use
- Tesla's Alt-Energy Future Aims for Massive Lithium-Ion Battery Production
- California Establishes Center for Coffee Study
- Social Media Can Help a Company's Credit Line
- Spotify Picking up Echo Nest
- Rand Paul Tops Presidential Straw Poll at Conservative PAC Conference
- Lawful Immigrants Defend Driver's Licenses
- Arriola Takes Charge at SoCalGas