Systems and methods for creating enhanced documents for perfect automated parsing

System and method for creating enhanced documentation for perfectly automated profiling

SYSTEMS AND METHODS FOR CREATING ENHANCED DOCUMENTS FOR PERFECT AUTOMATED PARSING

The following disclosure generally relates to systems and methods for creating enhanced electronic documents that allow for flawless parsing of enhanced documents using automated methods.

Electronic documents are usually stored in file formats such as Microsoft Word's DOCX format or Adobe Acrobat's PDF format that allows rendering of documents in a way that is visually appealing to human readers. But these formats typically store information in an unstructured manner, which makes it difficult for automated parsing software (or parsers) to interpret electronic documents accurately, leading to misinterpretation or misclassification of data. For example, job seekers often prepare a precisely formatted resume (for example, as a DOCX or PDF file) that they can upload as part of their online job application submission process. Formatted resumes are often processed through Applicant Tracking Systems (ATS) or other resume review systems, which may attempt to use parsing software to parse the resume to extract important information from the resume. The resume review system may use the extracted information to filter resumes for review by the recruiting party's human resources personnel based on pre-selected qualifications or other analysis. If the information is not correctly extracted from the job applicant's resume, the resume may never be sent to human reviewers, or the human reviewers may be viewing incorrect information about the job applicant. While some file formats allow information to be stored in a structured way (for example, according to a defined XML or JSON schema), which can improve machine readability, these raw text data formats cannot capture how such information will be presented visually to individuals. Therefore, there is a need to be able to create electronic documents that are visually appealing to human readers and that can be accurately interpreted by a parser.

The enhanced document creation system disclosed in the present invention attempts to encrypt the document content according to a defined schema, optionally encrypt the resulting structured data into an encrypted byte string, and encrypt the encrypted byte Strings are embedded in documents as invisible metadata to address the above limitations faced when applying automatic parsing techniques to unstructured documents. The resulting file can be fully and accurately parsed by an enhanced file parsing system capable of extracting, decrypting and decoding embedded file metadata. In some embodiments, the enhanced file creation system may store encoded (and optionally encrypted) file content associated with the file identifier, which may alternatively be embedded in the file as invisible metadata. In this case, the enhanced document parsing system may extract the embedded document identifier, request the encoded content associated therewith from the enhanced document creation system, and decode the structured material received from the enhanced document creation system (and decrypt) to perfectly dissect the file. In this way, a single file can be created, allowing individuals to present the file content in their preferred visual way for maximum impact, while also ensuring that a parser or other similar tool can accurately capture the file content without discarding or misrepresents anything.

FIG. 1 illustrates an exemplary environment 100 in which the present invention may be deployed. As shown, the environment 100 may include one or more users 101, each user having a user device 102 (eg, a personal computer, cellular phone, PDA, etc.) that the user 101 may use Comes with enhanced document creation system 110 and document submission system 160 . Enhanced document creation system 110 may host document creation platform 180 that user 101 may interface with via Internet 140 (eg, using a web browser on user device 102) to create and format initial documents 150, view and update the file, and export the file as an enhanced file 151. For example, the enhanced document creation system 110 may host a resume creation platform (eg, www.myperfectresume.com or www.zety.com) that the user 101 can use to create, view, and update resumes, as well as output resumes as enhanced resume documents. . As another example, the enhanced document creation system 110 may host a tax return preparation platform through which users 101 may prepare their personal income tax returns. <br /> For example, the document creation platform 180 may allow the user 101 to create the initial document 150 by presenting the user 101 with a fillable form, a guide prompting the user 101 to enter certain information, a WYSWIG editor, and the like. In response to a user request to output the original document 150 in a specific file format (eg, in the DOCX format of Microsoft Word or the PDF format of Adobe Acrobat), the enhanced document creation system 110 may output the original document 150 as an enhanced document 151, namely By encoding the file content according to a defined schema and embedding the structured content into the enhanced file 151 as invisible metadata. The enhanced document creation system 110 may optionally encrypt the structured content prior to embedding the structured content in the enhanced document 151 . In some embodiments, the enhanced document creation system 110 may store the encoded (and optionally encrypted) content associated with the output document identifiers in the document repository 116 . The output file identifier may be embedded in the enhanced file 151 in place of (or in addition to) the embedded encoded content itself, and may be used later for requests from the enhanced file creation system 110 (eg, through the enhanced file parsing system 130 ) the encoded content. <br /> User 101 may then submit enhanced document 151 to document submission system 160 . For example, document submission system 160 may provide a document submission platform 190 that user 101 may interface with via Internet 140 (eg, using a web browser on user device 102) to upload and process enhancements in a particular manner type file 151. For example, document submission system 160 may be a job application board that may provide user 101 with the ability to search for job postings and apply for jobs by uploading resumes and other application documents (eg, cover letters, letters of recommendation, etc.), and then Can be processed through ATS or other resume filtering systems. <br /> The file submission system 160 can call the enhanced file parsing system 130 to extract and process the embedded metadata to fully and accurately parse the enhanced file 151, which the file submission system 160 can utilize to further process the enhanced file 151. For example, enhanced document parsing system 130 may provide a public or external service (eg, SOAP or REST web service) that document submission system 160 may invoke to parse enhanced document 151 . For example, job application boards board) may receive the enhanced resume uploaded by the user and send it to the enhanced resume parsing system 130 as part of the profiling request. The enhanced resume parsing system 130 can determine whether the resume is actually an enhanced resume, and can extract and (if necessary) decrypt the embedded metadata, and return the extracted encoded resume content to the job application board. In some embodiments, the enhanced document parsing system 130 may further process the extracted content to place it in a form usable by a job application board (eg, mapping some or all fields and elements based on a defined schema to another job pattern used by the application board). The job application board may use the structured data returned by the enhanced parsing system 130 to automatically complete one or more fields of the job application form for the user (eg, some or all of the elements and fields in the structured mapping of elements and fields of the application table). As another example, the file submission system 160 may be the previously described tax return preparation platform that may allow the user 101 to submit enhanced tax return files for previous years. The tax return preparation platform may utilize the enhanced document parsing system 130 to extract and process the embedded metadata to fully and accurately extract the information contained in the enhanced tax return document. The tax preparation platform can then use this information to calculate and/or populate fields in the current return that the user 101 is preparing. <br /> In embodiments where the output file identifier is embedded in the enhanced file 151 , the enhanced file parsing system 130 may extract the file identifier and request the relevant encoded content from the enhanced file creation system 110 . For example, enhanced document creation system 110 may provide a public or external service (eg, SOAP or REST web service) that document parsing system 130 may invoke to request encoded content (eg, by passing an extracted document identifier). Enhanced document creation system 110 may pass the requested content back to enhanced document parsing system 130, which may then pass the encoded content back to document submission system 160 for further processing. As part of the request to the enhanced document creation system 110, the enhanced document parsing system 130 may be able to specify the format (eg, JSON, HTML, RTF, or TXT format) of the encoded content that should be returned. As before, the enhanced document parsing system 130 may further process the encoded content to place it in the form expected by the document submission system 160 (eg, mapping some or all fields and elements to another document submission based on a defined schema). mode used by system 160). <br /> Enhanced document creation system 110 may also require enhanced document parsing system 130 to authenticate itself as part of the request (eg, by passing a unique license key associated with enhanced document parsing system 130, or using some other suitable authentication mechanism). Enhanced document creation system 110 can also verify that enhanced document 151 has not been altered since it was originally exported to provide an additional layer of security and ensure that the encoded content passed back to enhanced document parsing system 130 is accurate. For example, an enhanced resume can be modified by a user after export, or can be reused by another person, but can retain the exported file identifier as embedded metadata. In this case, the encoded content associated with the output file identifier will no longer correspond to the content of the enhanced file 151 and should not be passed back to the enhanced file parsing system 130 . To perform this verification, the enhanced document creation system 110 may ask the enhanced document parsing system 130 to provide the hash value of the enhanced document 151 uploaded by the user as part of the request, the enhanced document creation system 110 may then convert the enhanced document The hash value of 151 is compared with the hash value of the encoded content stored in the file database 116 . If the hash values match, the enhanced document creation system 110 may pass the encoded content back to the enhanced document parsing system 130, but if the hash values do not match, an appropriate error message may be sent instead. In alternative embodiments, enhanced file parsing system 130 may provide enhanced file 151 along with the request, and enhanced file creation system 110 may be responsible for computing hash values for enhanced file 151 . <br /> Although document submission system 160 and enhanced document parsing system 130 are shown as separate systems, this need not be the case, and the components and/or functions of document parsing system 130 may be integrated within document submission system 160 itself. For example, the logical components of file parsing system 130 described below may be provided on file submission system 160 (eg, as an executable library that may be used by file submission system 160). In some embodiments, document submission system 160 may provide a widget as part of document submission platform 190 (eg, installed on a job application form) through which user 101 will be able to submit enhanced documents directly 151 to be perfectly parsed (ie, the widget operates as the enhanced file parsing system 130). User 101 may have one or more options through which widgets may submit or otherwise provide enhanced document 151 to document submission system 160 . For example, the user 101 may be able to upload a previously output enhancement file 151 through the widget. <br /> In some embodiments, the widget can see if the user has a relationship with the enhanced document creation system 110 or the document creation platform 180, and can allow the user to select enhanced documents 151 submitted directly from there. For example, user 101 may be able to retrieve enhanced document 151 directly from enhanced document creation system 110 (eg, through a public or external REST or SOAP service). Where the user 101 has created a plurality of enhanced documents 151 through the document creation platform 180, the user 101 may be prompted to select the document they would like to submit. Conversely, if user 101 has not created enhanced document 151, user 101 may be redirected to document creation platform 180 to create his enhanced document. <br /> In several cases, the widget may require the user to be authenticated to be able to submit or otherwise provide the enhanced file 151 to the file submission system 160 . For example, the widget may detect the presence of a cookie, instruct the user 101 to log in to the document creation platform 180, and may prompt the user 101 to confirm whether the user wishes to submit the enhanced document 151. In this way, user 101 can control whether enhanced document 151 is provided to document submission system 160, and enhanced document creation system 110 can track and facilitate the use of enhanced document 151. If no such cookie is detected, the user 101 may be prompted to log in to the document creation platform 180 before being allowed to proceed. In other embodiments, the gadget may require the user to delegate persistent access to enhanced document 151 from document creation system 110 (eg, through-hole OAuth or similar access delegation protocol) to document submission system 160 . In this manner, the user 101 may, for example, grant the document submission system 160 to check for an updated version of the enhanced document 151 in the future, receive notifications of subsequent document revisions, or receive other relevant information about the user 101 and/or the enhanced document (e.g. , the ability of the document submission system 160 to check the user's job search status, likelihood of an interview, etc.). The document creation platform 180 may also require the document submission system 160 to authenticate itself (eg, using a previously provided license key or similar authentication mechanism) before transmitting the enhanced document 151, thereby providing another layer for the exchange of user information safety. <br /> Once the user uploads, selects, or creates the enhanced file 151 that they want to submit to the file submission system 160, the widget can extract the encoded content embedded therein. In the event that the user 101 has chosen to retrieve the enhanced file 151 directly from the enhanced file creation system 110, the enhanced file creation system 110 may simply return the encoded content itself. The widget, in turn, can map one or more fields within the encoded content to corresponding fields in the document submission platform 190 (eg, to corresponding fields in a job application form). <br /> The enhanced document creation system 110 may include one or more communication interfaces 111 (eg, WiFi communication interfaces or LAN interfaces), one or more processors 112, memory 113, storage 114, which may include a surface library 114a, and One or more databases, including user database 117 , encrypted password database 115 and file database 116 . Memory 113 may include file creation platform logic 120, encoding logic 121, desensitization logic 122, rendering logic 123, encryption logic 124, embedding logic 125, and license server logic 126, which processor 112 may utilize They are used to provide system functions as described below. <br /> For example, the document creation platform logic 120 may allow the enhanced document creation system 110 to provide a document creation platform 180 through which the user 101 may create the initial document 150. For example, enhanced document creation system 110 may utilize document creation platform logic 120 to render user 101 a website or portal with fillable form elements or fields that user 101 may fill out, select, or otherwise complete. For example, the document creation platform logic 120 may present the user with a resume building tool, which may prompt the user to select a resume template, or may automatically select a resume template based on one or more attributes of the user 101, which may be stored in the use user database 117 (eg, as part of a user profile). <br /> Based on the selected template, the document creation platform logic 120 may then generate a resume form with one or more blank sections having one or more fields or other form elements for the user 101 to complete. For example, these sections may address the user's personally identifiable information, educational background, work experience, etc. As another example, document creation platform 180 may present user 101 with a list of parts that user 101 may choose to include in initial document 150 . Through the document creation platform 180, the user 101 can select a section or paragraph to be edited, and a text entry form for the section or paragraph can be presented. The user 101 can then modify the text of the portion and adjust the formatting input (eg, positioning, style, etc.). In some cases, resume forms may be dynamic in nature, for example, allowing users to add or remove sections (eg, for each college or university attended, or each job they have held). <br /> The document creation platform 180 may also allow the user 101 to include one or more graphical elements in the initial document 150 . For example, user 101 may be asked to upload a profile image to be included in initial file 150, or graphical elements may be generated by file creation platform logic 120 in response to one or more user inputs provided through file creation platform 180 . For example, as shown in Figure 3, the resume building tool may present user 101 with a number of slider controls corresponding to particular skills that user 101 may have, which user 101 may adjust based on their level of proficiency Floater control. As another example, as shown in Figure 4, a resume building tool may prompt users of specific skills or hobbies they may possess, and may present icons, emojis, monograms, images, gifs, or other representations of those skills, hobbies graphics, or other attributes, which the user can then choose to include in the resume. The selected graphic may include a corresponding description, which the user 101 may be able to change. In other cases, the resume building tool may allow users 101 to upload their own images or graphic elements, and as part of the upload process, the user may be prompted to provide a description and/or identify skills, hobbies, or other attributes associated therewith. <br /> In some embodiments, the document creation platform 180 may provide the user with the ability to save the initial document 150 in the document repository 116 in a particular state, and may utilize the document encoding logic 121 to do so. In this case, the file creation platform 180 may allow the user 101 to restore previously saved files for viewing, exporting, or further modification. The document creation platform 180 can also allow the user 101 to provide an existing non-enhanced document, which the enhanced document creation system 110 can parse using parsing software. Information extracted by parsing the document may be analyzed by document generation platform logic 120 to identify the presence of one or more sections, and seed or prepopulate fillable form elements of initial document 150 corresponding to the identified sections. The original document 150 may then be encoded as structured material and embedded into the enhanced document 151 using document encoding logic 121 discussed below. User 101 can also edit the pre-populated file content before it is encoded and embedded in enhanced file 151, eg, to correct any errors or omissions due to automatic parsing of non-enhanced files. <br /> The document encoding logic 121 may in turn be used to encode the initial document 150 into a structure according to a defined schema (eg, a proprietary or standardized XML or JSON schema) based on the known semantic meaning of each table element and the content within it through association data. For example, document encoding logic 121 may map each section or paragraph of a resume completed by user 101 to specific elements and fields within a defined schema. For example, the job history section of the resume may contain records of the user's work, with paragraphs or subsections corresponding to each position held by the user 101 . Each position can also contain elements corresponding to the employer's name, employment dates, and experience description. Based on the semantics of each element (eg, belonging to a job history section or asking for an employer's name), the document encoding logic 121 can encode the user input into structured data according to a structured schema. <br /> File encoding logic 121 may store the encoded file in file repository 116 . In some embodiments, the document encoding logic 121 may encode and store the initial document 150 based on user input provided through the document creation platform 180 (eg, by clicking a save button). Although in other cases, the document encoding logic 121 may encode and store each form element of the initial document 150 on the fly, as done by the user (eg, when the form element loses focus). In this way, the document creation platform 180 can maintain the state of the original document 150 and allow the user 101 to update and modify the document in multiple sessions. The encoded file may be stored in the file repository 116 in association with a file identifier, which may be used as a version identifier for a particular instance of the encoded file. <br /> In the event that the initial file 150 includes graphical elements-which are often difficult to interpret and are often ignored by conventional parsers-the file encoding logic 121 can map visual indicators in the graphical elements to fields within the definition schema value of . For example, FIG. 2 illustrates a graphical element 210 showing the user's 101 proficiency in various design skills that a user may include in a resume that may be presented by the document creation platform 180 in response to presentations to the user 101. A set of questions or prompts related to their design capabilities. Enhanced document creation system 110 may in turn encode graphical elements 210 as structured material 220 . Similarly, FIG. 5 illustrates graphical elements 510 showing various roles performed by user 101 in previous jobs, which enhanced document creation system 110 may encode into structured material 520 . <br /> As another example, FIG. 3 shows a graphical element 310 consisting of a series of slider controls 311-314 that a user can adjust to reflect their level of skill or expertise in a particular subject. As shown, the file encoding logic 121 may encode the graphical element 310 into structured data 320, wherein the value of each slider control 311a-311d is reflected in the "Skilled Skilled" in the corresponding slider control 321a-321d of the encoded file Degree" fields 322a-322d. FIG. 4 illustrates another example in which the user may select a graphical element 410 from a list of graphical elements 401 provided to the user in response to a prompt regarding the user's skill 402 . Graphical elements may have associated descriptions 411, which may be provided or modified by the user 101 through a selection process. When exported as an enhanced file 451, only the graphical elements will be visible, but additional information associated with the graphical elements (eg, their descriptions) can still be encoded as structured data 420 and embedded therein. In some cases, the schema may specify that the graphical element itself is also included in the structured data (eg, as a byte string, or a reference to the location of the graphical element in the visible portion of the enhanced document). For example, a user's profile image could be encoded in structured data as a graphical element with a description field that could take the value "profile image", and a base64 representation field that could contain an image A byte string representation of . <br /> In some embodiments, the file encoding logic 121 may also augment the encoded content based on the semantics of the various file elements. For example, a resume created using the previously described resume creation tool may indicate that a job applicant has extensive experience as a cashier. To improve the chances that the resume is not ignored by any software filters (eg, filters applied by ATS) and presented to human reviewers, the document encoding logic 121 may additionally characterize the experience as "money handling" or "customer relationship" in in the encoding file. Enhanced documents 151 augmented in this manner can also help provide an enhanced or improved matching experience (eg, for employers looking for qualified job candidates), as the expanded information can make the document more likely to be responsive to a particular document search or query (for example, searching or querying the resume database, etc.). These additional descriptors may not be rendered visually in the enhanced file 151, but will persist in the encoded content embedded therein. <br /> In other embodiments, enhanced document creation system 110 may allow user 101 to designate content within original document 150 to be invisible, redacted, or otherwise hidden. For example, actively employed job seekers may not want their current employers to know they are looking for new opportunities and may therefore be reluctant to distribute their resumes. User 101 may be able to redact or hide certain information (eg, their personally identifiable information, the name of their current employer, letters of recommendation, or any other information they would like to protect) to make it invisible on the resume, while still Include it as encoded content embedded in it. In some cases, document creation system 110 may include a flag or parameter in enhanced document 151 that indicates that user consent is obtained to embed information within enhanced document 151 and/or to allow processing of the embedded information, eg, through The enhanced document creation platform 180 presents the user 101 with terms of service or an opt-in prompt. Additionally, as described below, the enhanced document 151 may have an interactive method by which feedback regarding the enhanced document 151 may be provided. In this case, the enhanced document 151 may allow the recruiter or recruiter to request access to view such information, which may be communicated directly or indirectly to the user 101 of the enhanced document 151 for consent. <br /> In yet other embodiments, the enhanced document creation system 110 may individually prompt the user 101 to provide additional content beyond the initial document 150, which the document encoding logic 121 may include as the encoded content. In this manner, enhanced document 151 may carry additional information suitable for extraction by enhanced document parsing system 130, while maintaining the visual appearance of original document 150 when rendered. For example, users 101 will often try to limit the length of their resumes to one page, but this often requires omitting potentially relevant information, such as second skills or prior work experience, which may ultimately harm job candidates' ability to be found and hired Chance. As another example, the enhanced document creation system 110 may include alternate versions of content in different languages. <br /> In yet another embodiment, the enhanced file creation system 110 may automatically select what content in the initial file 150 will be visible and/or included as encoded content. For example, the user 101 may be able to provide a job description or the URL of a specific job application, which the enhanced document creation system 110 may analyze to determine which content in the original document 150 is most relevant for visual rendering, while the document encoding Logic 121 includes all, some or none of the remaining content as encoded content. <br /> In some cases, enhanced document creation system 110 may automatically include relevant information as encoded content that may aid or assist in processing enhanced document 151 . For example, job applicants are often asked to provide basic bibliographic information (eg, mailing address, work authorization status, etc.) or submit a cover letter with a resume. Repeatedly entering this information when applying for multiple jobs can be a laborious and monotonous task, often preventing job seekers from completing job applications. Such information may have been previously captured (eg, during the registration process, or when completing a different job application) and stored in the user database 117 as part of the user profile, but may be accessed as encoded content Inclusion within enhanced document 151 allows enhanced document parsing system 130 to automatically extract and provide this information to document submission system 160 to simplify the job seeker's application process. As another example, where the enhanced document 151 may be an order purchasing or fulfillment form used by a business, the enhanced document creation system 110 may be able to include related invoices, delivery forms, and receipts (eg, containing an itemized breakdown of the order) , and associated cost and shipping information) as coded content. <br /> FIG. 6 provides a high-level view of a proprietary schema that the enhanced document creation system 110 may use to encode the initial document 150. Proprietary mode can provide a hierarchical coding structure, as shown, in which a document can be broken down into documents, sections, paragraphs, and document data elements, each with specific fields. Because the enhanced file parsing system 130 may be implemented or deployed by different entities, custom mappings for specific instance or implementation-specific schemas may be required. To reduce or eliminate the necessary amount of customization and allow parsing enhancements to be available for a wider number of enhanced file parsing systems 130, some embodiments may utilize open standards. In this case, the document encoding logic 121 may translate the material encoded according to the proprietary schema used by the document creation platform 180 into an open standard schema. For example, enhanced document creation system 110 may translate material encoded according to the schema shown in FIG. 6 into HR-JSON or HR-XML schemas published by the HR Open Standards Consortium. However, such a standardized schema may not by itself accommodate the complete set of elements and values that may be defined in a proprietary schema, and may be extended to accommodate additional structure, functionality, or behavior. <br /> Desensitization logic 122 may allow enhanced document creation system 110 to desensitize encoded documents to ensure that enhanced document 151 does not include sensitive user information (eg, SSN, photos, personally identifying information, etc.). For example, the desensitization logic 122 may process the encoded file (ie, after the original file 150 has been encoded and stored in the file repository 116) and mark any sensitive user information for exclusion from translation to open standards mode (if any if such a translation occurs), and/or exclude the encoded file before rendering it. <br /> Rendering logic 123 may allow enhanced document creation system 110 to render encoded documents (or desensitized or translated documents, as the case may be) in a particular archive format (eg, DOCX format for Microsoft Word or PDF format for Adobe Acrobat), which is In some embodiments, it may be specified by the user 101 . For example, rendering logic 123 may be used to generate an intermediate archive from encoded content, where the visual appearance of the file content (ie, the positioning and styling of the file content) may be provided by a skin definition associated with the original file 150, The surface definition may be stored in and retrieved from the surface library 114a. For example, the enhanced document creation system 110 may generate an HTML archive that includes different HTML elements with specified CSS styles and linked CSS style sheets to control the location and style (ie, visual appearance) of the document content. The enhanced document creation system 110 may then convert the intermediate file into a specific file format, such as the DOCX format of Microsoft Word or the PDF format of Adobe Acrobat. By doing so, the enhanced document creation system 110 can utilize publicly available conversion libraries, such as Aspose (for HTML to DOCX conversion) or ABCpdf (for HTML to PDF conversion). <br /> In some embodiments, rendering logic 123 may allow enhanced document creation system 110 to include one or more interactive methods (eg, in the form of interactive buttons, hyperlinks, etc.) by which feedback related to enhanced document 151 may be provided. For example, once a job applicant submits a job application, they wait for a response from the recruiter. The response may never come, and the user 101 may be concerned that the resume never reaches the human reviewer (eg, if it was not properly parsed). By providing interactive buttons or other means of interaction within the resume itself, human reviewers may be able to take action quickly and automatically, for example, notifying users 101 that their resume has been reviewed and/or whether they are considered for the position, The user 101 is automatically contacted to schedule an interview or request a referral, etc. The provided interaction method can also utilize the content embedded in the document through the embedding logic 125 . For example, enhanced document 151 may provide a mechanism whereby a human reviewer can determine if an updated version of enhanced document 151 is available and request the updated version if available (eg, by calling an API to the public and passing an encryption key or embedding Export File Identifier in Enhanced File 151). <br /> Enhanced document creation system 110 may additionally or alternatively provide an interface (eg, in the form of a public or external REST or SOAP service) through which feedback regarding enhanced document 151 may be provided. For example, through this interface, the document submission system 160 and/or the enhanced document parsing system 130 can update the processing status of the enhanced document creation system 110 to the processing status of the enhanced document 151 (eg, received, processed, approved/rejected, or other custom state) (eg, by passing a state indicator, an encryption key or an output file identifier, and a license key if required by the API). The enhanced document creation system 110 may also provide an interface through which the user 101 may receive and respond to feedback regarding the enhanced document 151 . In this way, enhanced document creation system 110 may allow two-way communication between user 101 and document submission system 160 and/or the party operating it. <br /> Encryption logic 124 may allow enhanced file creation system 110 to generate encryption keys (eg, by using an encryption key generation algorithm like PBKDF2), which may be used to encrypt encoded files (eg, using encryption like AES) algorithm) to create an encrypted byte string of encoded content. In embodiments where the encoded file is desensitized and/or translated, encryption logic 124 may encrypt the desensitized and/or translated content. The generated encryption key may use an encryption cipher, which may be stored in and retrieved from the encryption cipher database 115, and may also use a randomly generated salt or initialization vector. In embodiments where the enhanced document creation system 110 acts as an encryption license server, the generated encryption key may be assigned a unique encryption key identifier and stored in the encryption password database 115 in association with the original document 150, This could similarly be a unique file identifier assigned. Enhanced file creation system 110 may generate a new encryption key each time original file 150 is output as enhanced file 151 (eg, as a user updates or modifies original file 150). In this manner, the encryption key identifier may also serve as a version identifier to identify each version of the original file 150 that is output. In some embodiments, enhanced file creation system 110 may store encoded files (or desensitized or translated files) in association with export file identifiers in file repository 116 upon output. In this manner, enhanced file creation system 110 can maintain each version of original file 150 that has been exported. <br /> Embedding logic 125, in turn, may allow enhanced file creation system 110 to embed encoded and optionally encrypted content into rendered files as invisible metadata. For example, the embedding logic 125 may prepend any salt or initialization vector used to generate the key at the beginning of the encrypted byte string. Alternatively, in embodiments where the enhanced document creation system 110 functions as an encryption license server, the embedding logic 125 may prepend an encryption key identifier associated with the generated encryption key. The modified byte string can then be written to the converted document as invisible metadata (eg, "custom properties" written to a Microsoft Word DOCX or Adobe Acrobat PDF file). In embodiments where enhanced file creation 110 stores the encoded file as it is output, embedding logic 125 may additionally or alternatively embed an output file identifier associated with the output encoded file. Although the embedding of encrypted content has been described above, it should be understood that encoded content need not be encrypted and can be embedded as an unencrypted string of bytes. <br /> Certain file formats may limit the form in which invisible metadata is written to the converted file, eg, requiring pairs of ID-values or limiting the size or length of the value (eg, strings less than 255 characters long). Embedding logic 125 may allow enhanced file creation system 110 to determine the file format of the converted file and manipulate the byte string to conform to any constraints that format may impose on invisible metadata stored therein. <br /> In some embodiments, the embedding logic 125 may allow the enhanced document creation system 110 to embed custom code or macro code to perform certain functions. For example, enhanced document creation system 110 may create a macro code that will generate an alert message when user 101 is about to modify enhanced document 151 to warn user 101 of any changes made outside of document creation platform 180 May result in imperfect file parsing. In some cases, enhanced document creation system 110 may prevent user 101 from making any changes. In other embodiments, enhanced document creation system 110 may embed within enhanced document 151 a macro code that will allow changes made in the visual appearance of the document to be synchronized with the embedded content contained therein. For example, the macro code may send the updated content to the enhanced file creation system 110 (eg, via an API or web service), which may perform an encoding process to produce updated encoded content, which may optionally be encrypted and Embedded back into the enhanced file 151 . <br /> The license server logic 126 may allow the enhanced document creation system 110 to act as a license server, allowing the enhanced document creation system 110 to control whether the enhanced document parsing system 130 Invisible metadata in enhanced file 151 of . By limiting the ability to extract and/or decrypt embedded content, which may include sensitive user information (in embodiments where desensitization is not performed) or other personal details not visible to human readers, enhanced document creation The system 110 enables the user's information to be protected even after it is exported, and allows only authorized persons to obtain the content. License server logic 126 may also allow enhanced document creation system 110 to expire encryption keys and output document identifiers, which effectively operate to expire embedded content. In this manner, the enhanced document creation system 110 can prevent the extraction and use of user information that may no longer be accurate (eg, if the user's contact information has been changed, or if errors in the document are corrected). <br /> License server logic 126 may provide enhanced document creation system 110 with the ability to create a unique license key for a particular parser or parser's particular application, which parser may need to submit with any request. The license server logic 126 may also allow the enhanced document creation system 110 to limit the use of the license key to specific systems (eg, based on domain, IP address subnet, etc.), placing the use of the license key on a specific request rate or amount (eg, maximum daily or hourly amount or overall maximum amount). License server logic 126 may allow enhanced document creation system 110 to delete, disable, and/or enable license keys. By deactivating a key, it may no longer be authorized for use, but may remain in the system, for example for audit trail purposes. <br /> Enhanced document creation system 110 may provide an external service (eg, SOAP or REST web service) that document parsing system 130, with an authorized license key, may invoke to request an encryption key corresponding to a particular encryption identifier . Upon successful verification of the license key, which may involve checking that the license key exists, is currently active, and has not exceeded access limits, the enhanced file creation system 110 may extract the encrypted password from the encrypted password based on the requested encryption identification. The repository 115 retrieves the encryption key and passes it back to the enhanced file parsing system 130 that made the request. In embodiments where enhanced file creation 110 stores the encoded file upon export, enhanced file parsing system 130 may be able to invoke the service to request the encoded content itself (eg, by providing the encoded export with a valid license key) file-related output file identifier or encryption key identifier). For example, in response to a user request to expire a particular enhanced document 151 output from the enhanced document creation system 110, the license server logic 126 may also allow the enhanced document creation system 110 to base the encryption key identifier or associated document on the The identifier expires or deletes the encryption key or encoded content. <br /> In some embodiments, enhanced document creation system 110 may allow document submission system 160 and/or enhanced document parsing system 130 to register enhanced document 151 with enhanced document creation system 110 (eg, via an API registration notification URL to the public). ), so that when the user 101 updates or otherwise changes the original file 150 and outputs the file as an updated enhanced file 151, the enhanced file creation system 110 can automatically notify the file submission system 160 and/or the enhanced file parsing system 130. In other embodiments, the document submission system 160 and/or the enhanced document parsing system 130 may be able to query the enhanced document creation system 110 (eg, by calling an API to the public and passing an encryption key or output document identifier), To see if an updated version of the enhanced file 151 is available, or to request an alternative format of the enhanced file 151 (eg, in HTML, RTF, or TXT format), which may be better handled. <br /> Enhanced document creation system 110 may also receive notifications (or other feedback) from document submission system 160 and/or enhanced document parsing system 130 regarding the status of enhanced document 151 . For example, the file submission system 160 and/or the enhanced file parsing system 130 may provide the enhanced file creation system 110 with a notification that the enhanced file 151 was received and successfully parsed, an error occurred when attempting to parse the enhanced file, or the file was of some kind The manner is a notification of corruption, or some other notification related to the state of the file (eg, by triggering a notification URL included within the embedded content of the enhanced file 151 or calling a public API provided by the enhanced file creation system 110). The document submission system 160 and/or the enhanced document parsing system 130 may provide additional contextual information along with the notification. For example, where user 101 submits a resume through a job application board, the notification may not only indicate the status of the resume (eg, as received, successfully profiled, or under review) but also provide additional details about the submission (eg, identifying the submitted resume) company or position). The enhanced document creation system 110 may also take one or more actions in response to receiving the notification. For example, if an error occurs that would prevent the enhancement file 151 from being parsed, the user 101 may be automatically notified to allow the user 101 to resubmit the enhancement file 151 or take other corrective action. As another example, enhanced document creation system 110 may modify or update the document identifier of enhanced document 151 to be associated with document submission system 160 and/or enhanced document parsing system 130 from which status notifications were received. <br /> The enhanced file parsing system 130 may include one or more communication interfaces 131 (eg, WiFi communication interface or LAN interface), one or more processors 132 , memory 133 , and storage device 134 . Memory 133 may include metadata extraction logic 135, decryption logic 136, verification logic 137, and decoding logic 138, which may be employed by processor 132 to provide the system functions described below. <br /> Metadata extraction logic 135 may allow enhanced document parsing system 130 to extract metadata embedded within enhanced document 151 . For example, enhanced file parsing system 130 may extract embedded metadata from enhanced file 151 to obtain a single extracted byte string. In the case where the embedded content is encrypted, the enhanced file parsing system 130 may split the extracted byte string into the salt and initialization vector and encrypted content. Where the metadata consists of a series of pairs of ID-values, the enhanced file parsing system 130 may first concatenate the values in order (eg, based on IDs) to form a single extracted byte string. Alternatively, in embodiments in which the enhanced document creation system 110 functions as an encryption license server, the enhanced document parsing system 130 may split the byte string into an encryption key identifier and encrypted encoded content. <br /> In the case where the output file identifier is embedded in the enhanced file 151, the metadata extraction logic 135 may contact the enhanced file creation system 110 to request the encoded content initially stored by the file creation system 110 when exporting the file (also That is, associated with the output file identifier). For example, enhanced document parsing system 130 can query enhanced document creation system 110 by calling an API to the public and passing the output document identifier along with other request parameters. For example, the request may indicate that the desired format of the encoded content should be returned and/or include a license key authorizing the enhanced file parsing system 130 . In some embodiments, enhanced document parsing system 130 may also indicate the extent of the requested content, eg, whether enhanced document creation system 110 should return extended content, hidden user content, or supplemental content, as described above. <br /> Enhanced document parsing system 130 may attempt to automatically extract embedded metadata from a received document, assuming it is an enhanced document 151, or it may first, for example, based on indicators provided in the visible portion of the document (eg, key words or phrases, symbols, graphics, etc.) to detect whether the received document is an enhanced document 151. In some cases, although indicators appear in visible portions of the document, they may be hidden or obfuscated to prevent identification and inspection by human reviewers (eg, through the use of small font sizes and/or transparent or low-contrast colors). The enhanced file parsing system 130 can also determine whether the extracted byte string is the encoded content itself or an output file identifier, and can process the extracted metadata accordingly. The enhanced document parsing system 130 can also determine whether the encoded content is encrypted and can process the material accordingly. <br /> The decryption logic 136 may allow the enhanced file parsing system 130 to decrypt the encrypted content when the enhanced file creation system 110 extracts or returns the content. For example, the enhanced file parsing system 130 may regenerate the encryption key using the encrypted password obtained from the enhanced file creation system 110 and the salt and initialization vector extracted from the metadata of the enhanced file 151 . Alternatively, in embodiments where the enhanced document creation system 110 acts as an encryption license server, the enhanced document parsing system 130 may submit to the enhanced document creation system 110 the encrypted identification including the license key and the extracted metadata properties of the document , which may return the requested encryption key. The enhanced file parsing system 130 may then decrypt the encrypted encoded content using the regenerated or returned encryption key. <br /> Validation logic 137 may allow enhanced file parsing system 130 to determine whether the visible content of enhanced file 151 has been modified since its creation, in which case the encoded content may no longer be accurate. In this case, the enhanced file parsing system 130 can revert to conventional parsing methods. For example, enhanced document parsing system 130 may extract all literal characters in the visible content of enhanced document 151 and all literal characters in each element in the encoded content into separate strings. Literal characters can be extracted in their exact order of appearance and can include spaces. Enhanced file parsing system 130 may then calculate a hash value for each word string (eg, using the MD5 hash algorithm), and compare the two values together to determine if there are any differences. <br /> In the case where the output file identifier is embedded in the enhanced file 151 and the associated encoded content is requested from the enhanced file creation system 110, the enhanced file parsing system 130 may send the hash value of the enhanced file 151 to the enhanced file creation System 110 as part of its request. As described, the enhanced document creation system 110 may calculate a hash value for the associated encoded content stored in the document database 116 and compare the received hash value to the calculated hash value to determine the enhanced document 151 Has it been changed since its output. If the hash values do not match, the enhanced document creation system 110 can respond with an error message, and the enhanced document parsing system 130 can revert to conventional parsing methods. <br /> Decoding logic 138, in turn, may allow enhanced document parsing system 130 to decode the extracted and optionally decrypted content, and may provide the resulting structured material to document submission system 160 as needed. In some cases, enhanced document parsing system 130 may process the extracted content to place it in a form expected by document submission system 160 (eg, mapping some or all fields and elements to another document submission based on a defined schema) mode used by system 160). <br /> FIG. 7 depicts the high-level logic flow that the enhanced document creation system 110 may use to create the initial document 150. The process may begin by determining whether user 101 wants to create a new document or work from an existing document, eg, based on user input provided through document creation platform 180 (700). If user 101 decides to create a new document, enhanced document creation system 110 may select a document template based on one or more user attributes in a user profile associated with user 101, which may be obtained from a user database 117 (710). The enhanced document creation system 110 may create an initial document 150 according to the selected template, which may be encoded according to a defined schema and stored in the document repository 116 as a structured document (711). <br /> Alternatively, if user 101 decides to work from an existing file, user 101 may upload a non-enhanced file through file creation platform 180 (720). Enhanced document creation system 110 may use document parsing software to parse the document to extract information from the non-enhanced document (721). Enhanced file creation system 110 can analyze the extracted information to determine the existence of one or more parts in the uploaded file, and can create an initial file 150 with equivalent parts (722). The initial document 150 may be encoded according to a defined schema and stored in the document repository 116 as a structured document in association with a unique document identifier. Enhanced document creation system 110 may also populate sections within initial document 150 with information extracted using parsing software (723). The enhanced document creation system 110 can encode the populated portion according to the defined schema and update the structured document in the document repository 116 and can assign new document identifiers. <br /> Enhanced document creation system 110 may then present initial document 150 to user 101 through document creation platform 180 for user 101 to view, export, or further modify it (730). For example, user 101 may have the ability to select one or more sections of original document 150 for editing, and based on the user's selection of a particular section (740), enhanced document creation system 110 may present user 101 with that section The corresponding form is available for editing by the user 101 (732). User 101 can edit the content and format of the section through the form presented to user 101 (741). Once complete, enhanced document creation system 110 may encode the portion and update the structured document in document repository 116 accordingly (732). The process may continue until it is determined that user 101 has completed editing the file (730). <br /> FIG. 8 depicts a high-level logic flow that enhanced document creation system 110 may use to output enhanced document 151 . The process may begin by creating, via the file creation platform 180 provided by the enhanced file creation system 110, an initial file 150, which may be encoded according to a defined schema and stored as a structured file in association with a unique file identifier. File repository 116 (801). In response to the user's request to export the initial document 150 (803), the enhanced document creation system 110 may retrieve the structured document from the document database 117 and decompose the document by removing any sensitive information (eg, SSN, photos, etc.). Sensitive (802). Enhanced document creation system 110 may then translate the structured document into a standardized schema (804). The enhanced document creation system 110 can use this desensitized document to render the original document 150 into a specific archive format (eg, DOCX format for Microsoft Word or PDF format for Adobe Acrobat) (806), which, in some embodiments, can be used by The operator 101 specifies (807). can be defined according to a specific surface (skin) that can be loaded from the surface library 114a. definition) to render the initial document 150 (808). The enhanced document creation system 110 may then determine whether to embed the structured document into the rendered document (created at 806) or to embed a document identifier associated with the structured document. (809). If the structured document is to be embedded, the enhanced document creation system 110 may further determine whether the structured document is to be encrypted (810). If so, the structured file may be encrypted into an encrypted byte string according to a particular encryption algorithm (811), which in some embodiments may rely on encryption retrieved from encrypted password repository 115 Password (812). The output file identifier, structured file, or encrypted structured file may then be embedded as a byte string into the rendered file (created at 806), forming enhanced file 151 (813). <br /> FIG. 9 provides an exemplary logic flow of an embodiment that the enhanced document creation system 110 may use to render structured documents. As shown, the process may begin by generating an intermediate archive based on a structured document (901), where the positioning and styling of the document content (eg, layout, font, line width, spacing, margins, etc.) 114a retrieves file associated surface definitions (902). For example, the enhanced document creation system 110 may generate an HTML archive that includes different HTML elements with specified CSS styles and linked CSS style sheets to control the location and style (ie, visual appearance) of the document content. The enhanced document creation system 110 may then convert the intermediate file into a specific file format, such as Microsoft Word's DOCX format (903) or Adobe Acrobat's PDF format (904), which may depend on the file format specified by the user 101 (905) ). <br /> FIG. 10 provides an exemplary logic flow of an embodiment of an enhanced document creation system 110 that may be used to encrypt a structured document. As shown, the process may begin with the enhanced file creation system 110 using an encryption key generated by an encryption key generation algorithm such as PBKDF2 (1001), which may employ a salt when generating the encryption key , an initialization vector, and one or more of a password as parameters. Therefore, generating the encryption key may also require generating a random 128-bit salt (1002), generating a random 128-bit initialization vector (1003), and retrieving the encrypted password from the encrypted password database 115 (1004). The enhanced file creation system 110 may then encrypt the encoded content using an encryption algorithm such as AES (1005) to create an encrypted byte string of structured files. <br /> 11 depicts an exemplary logic flow of an embodiment that an enhanced file creation system 110 may use to embed encrypted content in a rendered file. As shown, the process may begin with the enhanced file creation system 110 prepending a randomly generated salt and initialization vector to the encrypted byte string (1101). In embodiments where the enhanced file creation system 110 functions as an encryption license server, the process may additionally or alternatively involve pre-adding an encryption key identifier to the encrypted byte string. The enhanced file creation system 110 may then determine, based on the archive format of the converted file, whether any restrictions are placed on the forms in which the metadata may be embedded in the converted archive format (1102). For example, Microsoft Word DOCX files and Adobe Acrobat PDF files may store metadata as "custom properties" in pairs of ID-values, while "custom properties" in Microsoft Word DOCX files are further limited to 255 characters string length, or less. In the case of an Adobe Acrobat PDF archive, the enhanced file creation system 110 may write the encrypted byte string together with a pre-added salt and initialization vector as a single pair of ID-values to form the enhanced file 151 ( 1104). Alternatively, in Microsoft Word DOCX In the case of a file, the enhanced file creation system 110 may split the encrypted byte string into multiple strings (1103), which may be written to the conversion file as a series of number-to-ID-values, An enhanced file 151 is thus formed (1105). Although the embedding of encrypted content is described above, it should be understood that encoded content need not be encrypted and can be embedded as an unencrypted byte string, or the output file identifier can be embedded as a byte string. <br /> 12 depicts a high-level logic flow that a file parsing system may follow to parse an enhanced file. As shown, the process may begin with the submission of enhanced file 151, eg, through file submission system 160 (1201). File submission system 160 may pass enhanced file 151 to enhanced file parsing system 130 for parsing, eg, by invoking a public or external service. Enhanced file parsing system 130 may extract embedded metadata from enhanced file 151 to obtain a single extracted byte string (1202). Where the metadata consists of a series of pairs of ID-values, the enhanced file parsing system 130 may first concatenate the values in order (eg, based on IDs) to form a single extracted byte string. <br /> Enhanced file parsing system 130 may then determine whether the extracted byte string represents the output file identifier or structured content (1203), and in the latter case may further determine whether the structured content is encrypted (1204) ). If the extracted byte string represents the output file identifier, enhanced file parsing system 130 may request an associated structured file from enhanced file creation system 110 (1205). With the extracted metadata encrypted, enhanced file parsing system 130 may split the byte string into the salt and initialization vector and encrypted content (1206). Enhanced document parsing system 130 can obtain an encryption key used to generate an encryption key used to encrypt the content (eg, by requesting it from enhanced document creation system 110) (1207), and can use the encryption key and the salt and initialization vector extracted from the invisible metadata of the enhanced file 151 to regenerate the encryption key (1208). Alternatively, in embodiments where enhanced document creation system 110 functions as an encryption license server, enhanced document parsing system 130 may split the byte string into encryption key identifiers and encrypted content. Enhanced file parsing system 130 may then submit a request for an encryption key to enhanced file creation system 110, the request including the license key for enhanced file parsing system 130 and from invisible metadata embedded in the file Extracted encrypted identifier. Enhanced document parsing system 130 may then use the generated or returned encryption key to decrypt the encrypted content extracted from the metadata of enhanced document 151 to obtain a structured document (1209). <br /> Once the structured document has been obtained, enhanced document parsing system 130 may determine whether enhanced document 151 has been modified since it was first created (1210). If a determination is made that the file has not been modified, the enhanced file parsing system 130 can decode the structured file and extract individual content elements as needed (1211). Alternatively, if a determination is made that the enhanced document 151 has been modified, the enhanced document parsing system 130 may use conventional parsing techniques to parse the visible content of the enhanced document 151 (1212). <br /> 13 depicts an exemplary logic flow that the enhanced file parsing system 130 may use to determine whether to modify a previously exported file. The process may begin with enhanced document parsing system 130 extracting all literal characters in the visible content of enhanced document 151 into a single string (1301). The enhanced document parsing system 130 may also extract all literal characters (including whitespace) in elements of the structured document into a single string, where the elements are processed in the exact order in which they appear in the structured document (1302 ). The enhanced file parsing system 130 may then calculate a hash value for each word string using the MD5 hash algorithm (1303a, 1303b), and compare the equivalent values (1304). If the computed hash value is the same, the file has not been modified. Conversely, if the hash value is different, the visible content of the enhanced file 151 has been altered in some way. In embodiments where the output file identifier is embedded in the enhanced file 151, similar processing may be employed. For example, the enhanced document parsing system 130 may calculate a hash value for the visible content of the enhanced document 151 (as in 1301, 1303a) and use the calculated hash value as a request for a structured document related to the output document identifier. A portion is sent to the enhanced document creation system 110 . The enhanced document creation system 110 may then calculate the hash value of the structured document associated with the output document identifier stored in the document repository 116 (as in 1302, 1303b), and may parse the system 130 from the enhanced document The received hash value is compared with the calculated hash value to determine if the file has been modified (eg, 1304). If the hash values match, the enhanced document creation system 110 can determine that the enhanced document 151 has not been modified since it was exported, and can return the structured document to the enhanced document parsing system 130 . <br /> While specific embodiments of the invention have been described above, it should be understood that the invention may be practiced otherwise than as described. The described embodiments and references in the specification to "one embodiment," "an embodiment," "an exemplary embodiment," "some embodiments," etc. indicate that the characteristic, each embodiment may not necessarily include that particular feature, structure, or characteristic. Furthermore, such terms are not necessarily referring to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, whether or not explicitly described, changes in such feature, structure, or characteristic in connection with other embodiments are understood to be within the art Usually within the knowledge of the knowledgeable. <br /> The description provided above is intended to be illustrative and not restrictive. Accordingly, it will be apparent to those of ordinary skill in the art that the present invention may be modified as described without departing from the scope of the claims set forth below. For example, while the embedding of encrypted content may have been described above, it should be understood that encoded content need not be encrypted and may be embedded as an unencrypted string of bytes. Furthermore, although the above description is provided with reference to the creation and parsing of enhanced resume files, the present invention is not so limited and can naturally extend to other contexts. For example, the Enhanced Document Creation and Analysis System can be used to create enhanced tax filings. <br /> The foregoing descriptions of specific embodiments will fully disclose the general nature of the invention so that those of ordinary skill in the art can readily modify and/or adapt various applications such as the specific embodiments without undue experimentation and without departing from General Concept of the Invention. Therefore, such adaptations and modifications are intended to be within the scope and meaning of equivalents of the disclosed embodiments based on the teaching and guidance presented herein. It is to be understood that the phraseology or terminology herein is for the purpose of description and not limitation, and thus the phraseology or terminology of this specification should be interpreted by those skilled in the art based on the teaching and guidance. <br /> The breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the appended claims and their equivalents.

<p>100: Environment <br /> 101: User <br /> 102: User device <br /> 110: Enhanced File Creation System <br /> 111: Communication interface <br /> 112: Processor <br /> 113: Memory <br /> 114: Storage Device <br /> 114a: Surface Libraries <br /> 115: Encrypted Password Database <br /> 116: Document Repository <br /> 117:User database <br /> 120: File Creation Platform Logic <br /> 121: Coding logic <br /> 122: Desensitization Logic <br /> 123: Rendering logic <br /> 124: Encryption logic <br /> 125: Embedded Logic <br /> 126: License server logic <br /> 130: Enhanced File Analysis System <br /> 131: Communication interface <br /> 132: Processor <br /> 133: Memory <br /> 134: Storage Device <br /> 135:Metadata extraction logic <br /> 136: Decryption logic <br /> 137: Validation logic <br /> 138: Decoding logic <br /> 140: Internet <br /> 150: Initial file <br /> 151: Enhanced file <br /> 160: Document Submission System <br /> 180: Bearer file creation platform <br /> 190: Document Submission Platform <br /> 210: Graphic Elements <br /> 220: Structured Data <br /> 310: Graphic Elements <br /> 311a: Scroller controls <br /> 311b: Scroller controls <br /> 311c: Scroller controls <br /> 311d: Scroller controls <br /> 320: Structured Data <br /> 321a: Scroller controls <br /> 321b: Scroller controls <br /> 321c: Floating block control <br /> 321d: Scroller Control <br /> 322a: Field <br /> 322b:Field <br /> 322c: Field <br /> 322d:Field <br /> 401: Graphical elements of lists <br /> 402: User Skill <br /> 410: Graphic Elements <br /> 411: Description <br /> 420: Structured Data <br /> 451: Enhanced file <br /> 510: Graphic Elements <br /> 520: Structured Data <br /> 700: Process <br /> 710: Process <br /> 711: Process <br /> 720: Process <br /> 721: Process <br /> 722: Process <br /> 723: Process <br /> 730: Process <br /> 731: Process <br /> 732: Process <br /> 740: Process <br /> 741: Process <br /> 801: Process <br /> 802: Process <br /> 803: Process <br /> 804: Process <br /> 806: Process <br /> 807: Process <br /> 808: Process <br /> 809: Process <br /> 810: Process <br /> 811: Process <br /> 812: Process <br /> 813: Process <br /> 901: Process <br /> 902: Process <br /> 903: Process <br /> 904: Process <br /> 905: Process <br /> 1001: Process <br /> 1002: Process <br /> 1003: Process <br /> 1004: Process <br /> 1005: Process <br /> 1101: Process <br /> 1102: Process <br /> 1103: Process <br /> 1104: Process <br /> 1105: Process <br /> 1201: Process <br /> 1202: Process <br /> 1203: Process <br /> 1204: Process <br /> 1205: Process <br /> 1206: Process <br /> 1207: Process <br /> 1208: Process <br /> 1209: Process <br /> 1210: Process <br /> 1211: Process <br /> 1212: Process <br /> 1301: Process <br /> 1302: Process <br /> 1303A: Process <br /> 1303B: Process <br /> 1304: Process </p>

The accompanying drawings, which are incorporated herein and form part of the specification, illustrate one or more aspects of the invention and, together with the description, will further serve to explain the principles of the invention and to enable those of ordinary skill in the relevant art to construct and Use the present invention. <br /> [FIG. 1] illustrates an exemplary environment in which the file creation and file parsing techniques of the present invention may be used. <br /> [Fig. 2] illustrates a first example of a graphic element encoded according to a defined pattern. <br /> [Fig. 3] illustrates a second example of graphic elements encoded according to a defined pattern. <br /> [Fig. 4] illustrates a third example of a graphic element encoded according to a defined pattern. <br /> [Fig. 5] illustrates a fourth example of a graphic element encoded according to a defined pattern. <br /> [FIG. 6] A high-level view illustrating an exemplary schema that an enhanced file creation system may use to encode an initial file. <br /> [Fig. 7] depicts the high-level logic flow that the enhanced document creation system can use to create the initial document. <br /> [FIG. 8] depicts a high-level logic flow that the enhanced document creation system can use to output an initial document as an enhanced document. <br /> [FIG. 9] depicts an exemplary logic flow that an enhanced document creation system may use to render structured documents. <br /> [FIG. 10] depicts an exemplary logic flow that the enhanced document creation system may use to encrypt structured documents. <br /> [FIG. 11] depicts an exemplary logic flow that an enhanced file creation system may use to embed encrypted content in a rendered file. <br /> [FIG. 12] depicts a high-level logic flow that an enhanced document parsing system may follow to parse an enhanced document. <br /> [FIG. 13] depicts an exemplary logic flow that an enhanced file parsing system may use to determine whether an enhanced file is to be modified. <br /> The features and advantages of the disclosed embodiments will become apparent to the reader from the detailed description set forth below, when taken in conjunction with the drawings, in which like reference characters refer to corresponding elements throughout. In the drawings, like reference numerals generally refer to identical, functionally similar, and/or structurally similar elements. Unless otherwise indicated, the drawings provided in this disclosure are not necessarily to be construed as being drawn to scale.

<bio-deposit />

<sequence-list-text />