Enterprise application transactions as shared active documents

• US 7,124,354 B1
• Filed: 03/24/2000
• Issued: 10/17/2006
• Est. Priority Date: 03/24/2000
• Status: Expired due to Fees

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Ramani, Sriram, Sarukkai, Sekhar
• Primary Examiner(s): Hong, Stephen
• Assistant Examiner(s): Basehoar, Adam L.
• Application Number:
  US09/533,781
• Time in Patent Office: 2,398 Days
• Field of Search: 715/501.1, 715/513, 705/26, 705/27, 705/28, 705/29, 705/75, 705/77, 709/203, 709/201, 707/1, 707/104.1
• US Class Current: 715/205
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06Q 10/00 Administration; Management
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders

Abstract

The present invention is directed to a method for a creating an active document that encapsulates a transaction and the transaction'"'"'s current status. The active document includes a first set of data fields, where the data fields represent attributes of a parent transaction and include a sub-identifier field; and a first set of metadata, where the first set of metadata populates the first set of data fields and describes the attributes represented by the first set of data fields, the sub-identifier filed including metadata from the first set of metadata that identifies a secondary transaction, linking data generated by the secondary transaction to the active document.

Claims

1. A method for creating an active document that encapsulates a transaction and the transaction'"'"'s current status, comprising:

creating a parent transaction resource, wherein the parent transaction resource represents and encapsulates data of one parent transaction and is linked to data generated by one or more secondary transactions and wherein the data generated by the one or more a secondary transactions are used to change contents of the parent transaction resource if corresponding contents of the one or more secondary transactions are updated, wherein the creating the parent transaction resource comprising;

generating a first set of data fields, wherein the first set of data fields represent attributes of the parent transaction and include one or more sub-identifier fields, one or more data fields that are updated with data from the one or more secondary transactions and data fields that are independent of the one or more secondary transactions and are not updated with data from the one or more secondary transactions; and

populating the first set of data fields with a first set of metadata, wherein the metadata describes the attributes represented by the data fields, the first set of metadata including;

one or more sub-identifiers that populate the sub-identifier fields, wherein the sub-identifiers identify the one or more secondary transaction resources and include linking data generated by the one or more secondary transaction resources to link the one or more secondary transaction resources to the parent transaction resources, wherein the linking data generated by the one or more secondary transaction resources is used to change contents of the parent transaction resources if corresponding contents of the one or more secondary transaction resources have been changed;

an identifier, wherein the identifier identifies the parent transaction resource;

one or more permissions that identify one or more client computers that are permitted to access the parent transaction resource through a network, wherein the parent transaction resource is stored on a core connected to the client computers via the network; and

resource handler metadata, wherein the resource handler metadata identifies a resource handler that physically accesses the parent transaction resource from the core.

2. The method of claim 1 further comprising:

creating a sub-transaction resource, wherein the sub-transaction resource represents a secondary transaction, the creating a sub-transaction resource comprising;

generating a second set of data fields, wherein the second set of data fields represent attributes of the secondary transaction and include an identifier field; and

populating the second set of data fields with a second set of metadata, wherein the metadata describes the attributes represented by the data fields and includes transaction specific data that corresponds to at least one of the first set of data fields in the parent transaction resource.

3. The method of claim 2, further comprising:

linking the parent transaction resource and the secondary transaction resource so that changes made to the transaction specific data are made in the corresponding at least one of the first set of data fields in the parent transaction resource.

4. The method of claim 3, wherein the linking comprises:

populating the sub-identifier field with metadata that identifies the secondary transaction; and

populating the identifier field with metadata that identifies the parent transaction.

5. The method of claim 2, further comprising:

registering the parent transaction resource and the sub-transaction resource in a repository, whereby the first set of metadata and the second set of metadata may be accessed and updated.

6. The method of claim 1, wherein the creating is conducted by submitting code written in a programming language that supports extensible markup language, the code comprising the first set of data fields and the first set of metadata.

7. The method of claim 6, wherein the programming language is Java, C++, Perl or Python.

8. The method of claim 1, wherein the parent transaction is related to the secondary transaction, the method further comprising:

tracking multiple related transactions using the active document.

9. An active document encapsulating a transaction and the transaction'"'"'s current status, comprising:

a parent transaction resource, wherein the parent transaction resource represents and encapsulates data of one parent transaction and is linked to data generated by one or more secondary transaction resources and wherein the data generated by the one or more secondary transaction resources are used to change contents of the parent transaction resource if corresponding contents of the one or more secondary transaction resources are updated, the parent transaction resource comprising;

a first set of data fields, wherein the data fields represent attributes of a parent transaction and include a sub-identifier field, one or more data fields that are updated with data from the one or more secondary transaction resources and data fields that are independent of the one or more secondary transaction resources and are not updated with data from the one or more secondary transaction resources; and

a first set of metadata, wherein the first set of metadata populates the first set of data fields and describes the attributes represented by the first set of data fields, the sub-identifier field including metadata from the first set of metadata that identifies the one or more secondary transaction resources, the metadata in the sub-identifier field including linking data generated by the one or more secondary transaction resources to link the one or more secondary transaction resources to the parent transaction resources, wherein the linking data generated by the one or more secondary transaction resources is used to change contents of the parent transaction resources if corresponding contents of the one or more secondary transaction resources have been changed, the first set of metadata further including;

an identifier, wherein the identifier identifies the parent transaction resource;

one or more permissions that identify one or more client computers that are permitted to access the parent transaction resource through a network, wherein the parent transaction resource is stored on a physical machine connected to the client computers via the network; and

resource handler metadata, wherein the resource handler metadata identifies a resource handler that physically accesses the parent transaction resource from the physical machine.

10. The active document of claim 9, wherein the sub-identifier field links the parent transaction resource to a first secondary transaction resource which comprises a second set of data fields and a second set of metadata that populates the second set of data fields, whereby changes to the first secondary transaction resource are reflected in the parent transaction resource.

11. The active document of claim 10, wherein the second set of data fields includes a sub-identifier field that links the first secondary transaction resource to a second secondary transaction resource which includes a third set of data fields and a third set of metadata that populates the third set of data fields, whereby changes to the second secondary transaction resource are reflected in the first secondary transaction resource.

12. The active document of claim 10 wherein changes to the first secondary transaction resource are reflected in only one data field in the parent transaction resource.

13. The active document of claim 9, wherein the first set of metadata is stored in a repository that is accessed by the core.

14. The active document of claim 13, wherein the core matches the sub-identifier field to one of the one or more secondary transaction resources and updates the first set of data fields by populating at least one data field in the first set of data fields with the data generated by the secondary transaction resource.

15. The active document of claim 9, wherein the active document is written in extensible markup language and is capable of being displayed by a web browser.

16. The active document of claim 9, wherein the data fields include a permissions fields which includes the permissions.

17. The active document of claim 9, wherein the data fields include a second sub-identifier field that includes metadata that identifies a second secondary transaction resource, linking data generated by the second secondary transaction resource to the parent transaction resource.