Method and apparatus for declarative updating of self-describing, structured documents

• US 10,061,754 B2
• Filed: 06/08/2017
• Issued: 08/28/2018
• Est. Priority Date: 12/18/2001
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: Open Invention Network LLC
• Inventors: Sulistio, Muljadi, Wei, Yang, Schwarzhoff, Kelly Lane, Ding, Yuan
• Primary Examiner(s): Stork, Kyle
• Application Number:
  US15/618,041
• Publication Number:
  US 20170351647A1
• Time in Patent Office: 446 Days
• CPC Class Codes: G06F 40/14 Tree-structured documents parsing G06F40/205; validation G06F40/226
• CPC Class Codes: G06F 40/154 Tree transformation for tree-structured or markup documents, e.g. XSLT, XSL-FO or stylesheets
• CPC Class Codes: G06F 40/166 Editing, e.g. inserting or deleting

Abstract

The present invention includes a method and device for updating a self-describing, structured document. A further aspect of the present invention is enabling client-based modification of the document. Additional aspects of the present invention are described in the claims, specification and drawings.

Claims

1. A method including:

transmitting, to a server, a selection of a field-tagged document, wherein the selected field-tagged document has a selected incoming document type;

transmitting, to the server, a reply document type;

applying a first style sheet to generate a draft reply document and building an in-memory representation of the draft reply document;

applying a second style sheet to generate an interface that supports editing of the in-memory representation of the draft reply document; and

accepting edits, updating the in-memory representation of the draft reply document, marshalling it into field-tagged format, and either persisting it for later use or sending it as a reply to the field-tagged document.

2. The method of claim 1, wherein:

the method further includes receiving and causing display of a list of available reply document types for selection and generation in draft, responsive to the selected incoming document type; and

the reply document type is transmitted to the server, responsive to a selection of one of the available reply document types.

3. The method of claim 1, further including identifying the first and second style sheets using the document type and the draft reply document.

4. The method of claim 1, wherein the second style sheet uses hidden fields to identify nodes of the in-memory representation of the draft reply document to which edits are applied.

5. The method of claim 1, wherein the second style sheet uses hidden fields to identify field names of the draft reply document to which edits are applied.

6. The method of claim 1, further including:

error checking the draft reply document and generating an error report of any errors detected either as an in-memory representation of the errors detected or an error report document; and

applying a third style sheet to merge the draft reply document and the error report and generate an interface that juxtaposes error messages with parts of the draft reply document containing errors.

7. The method of claim 6, wherein:

the applying of the third style sheet further includes generating an interface that supports editing of the in-memory representation of the draft reply document; and

the method further includes accepting edits, updating the in-memory representation of the draft reply document, marshalling it into field-tagged format, and either persisting it for later use or sending it as a reply to the field-tagged document.

8. A method including:

receiving a draft field-tagged document, wherein the draft field-tagged document has a document type;

receiving and causing display of an interface that supports editing of an in-memory representation of the draft field-tagged document, wherein the interface has been generated by applying a first style sheet to the in-memory representation of the draft field-tagged document; and

accepting and transmitting, to a server, edits to update the in-memory representation of the draft field-tagged document,

wherein the first style sheet uses hidden fields to identify nodes of the in-memory representation of the draft field-tagged document to which edits are applied.

9. The method of claim 8, further including identifying the first style sheet using the document type of the draft field-tagged document.

10. The method of claim 8, further including further selecting the first style sheet from among a hierarchy of generic and customized style sheets using a rule selector keyed to the document type.

11. The method of claim 8, wherein the first style sheet uses hidden fields to identify nodes of the in-memory representation of the draft field-tagged document to which edits are applied.

12. The method of claim 8, further including:

error checking the updated draft field-tagged document and generating an error report of any errors detected either as an in-memory representation of the errors detected or an error report document; and

applying a second style sheet to merge the updated draft field-tagged document and the error report and generate an interface that juxtaposes error messages with parts of the updated draft field-tagged document containing errors.

13. The method of claim 12, wherein:

the applying of the second style sheet further includes generating an interface that supports editing of the in-memory representation of the draft field-tagged document; and

the method further includes accepting edits, updating the in-memory representation of the draft document, marshalling it into field-tagged format, and either persisting it for later use or sending it as a reply to the field-tagged document.

14. A method including:

receiving a specification of a document type for a field-tagged document to draft;

receiving and causing display of an interface that supports editing of an in-memory representation of the field-tagged document to draft, wherein the interface has been generated by applying a first style sheet to the in-memory representation of the field-tagged document to draft; and

accepting and transmitting, to a server, edits to update the in-memory representation of the field-tagged document to draft,

wherein the first style sheet uses hidden fields to identify nodes of the in-memory representation of the draft field-tagged document to which edits are applied.

15. The method of claim 14, further including identifying the first style sheet using the document type of the field-tagged document to draft.

16. The method of claim 14, further comprising:

error checking the updated field-tagged document to draft and generating an error report of any errors detected either as an in-memory representation of the errors detected or an error report document; and

applying a second style sheet to merge the updated field-tagged document to draft and the error report and generate an interface that juxtaposes error messages with parts of the field-tagged document to draft containing errors.

17. The method of claim 14, wherein the first style sheet uses hidden fields to identify field names of the field-tagged document to draft to which edits are applied.

18. A system comprising:

a first processor;

a style sheet repository of style sheets applicable to document types adapted to generate an interface that supports editing of an in-memory draft field-tagged document, the style sheet repository coupled in communication with the first processor; and

a non-transitory memory coupled with the first processor and storing code which when executed by the first processor implement;

code that implements a user interaction that is configured to run on the first processor to transmit, to a server, a selection of a field-tagged document of a particular document type and a reply document type; and

code that implements a transformation that is coupled to the user interaction model and configured to (i) select a first style sheet from the style sheet repository, (ii) apply the first style sheet to generate a draft reply document and build an in-memory representation of the draft reply document and (iii) apply a selected second style sheet to generate an interface that supports editing of the in-memory representation of the draft reply document,

wherein the code that implements user interaction is further configured to cause display of the interface that supports the editing of the in-memory representation of the draft reply document and to accept edits to the in-memory representation of the draft reply document from a user, and

wherein the code that implements transformation is further configured to update the in-memory representation of the draft reply document, marshal it into field-tagged format, and either persist it for later use or send it as a reply to the field-tagged document.