Structuring an electronic document for efficient identification and use of document parts

• US 20060259854A1
• Filed: 05/10/2005
• Published: 11/16/2006
• Est. Priority Date: 05/10/2005
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Walker, Charles Scott, Villaron, Shawn, Jones, Brian, Rothschiller, Chad
• Application Number:
  US11/125,907
• Publication Number:
  US 20060259854A1
• Time in Patent Office: Days
• US Class Current: 715/234
• CPC Class Codes: G06F 40/131 Fragmentation of text files, e.g. creating reusable text-blocks; Linking to fragments, e.g. using XInclude; Namespaces

Abstract

Methods and computer-readable mediums structure an electronic document for identification and use of document parts. A method involves organizing parts of the electronic document as separate parts. The separate parts include resources internal and/or external to where the document is located. The method also involves representing a link between any of the parts as a relationship to be processed listed in a relationship part associated with a source part of the relationship. This relationship part contains a list of relationships for the source part and processing a relationship returns content of a target part of the relationship. Each relationship is also associated with a relationship type. Still further, the method involves representing via the relationship part how one or more parts relate to other separate parts, tracking internal resources, and tracking external resources. Thus, applications can infer the structure of the document by traversing the relationships.

Claims

1. A method for structuring an electronic document for identification or use of document parts by a variety of applications, the method comprising:

organizing parts of an electronic document as a collection of separate parts associated with an electronic document container wherein the parts comprise at least one of a resource internal to the document or a resource external to where the document is located;

representing a link between any of the parts as a relationship listed in a relationship part associated with a part of the document that is a source part of one or more relationships to be processed wherein the relationship part contains a list of relationships for the source part and wherein processing the relationships returns content of a part that is a target part of a relationship;

representing via the relationships part how one or more separate parts of the collection relate to other separate parts;

tracking the resource internal to the document via an internal relationship; and

tracking the resource external to where the document is located via an external relationship;

whereby applications discovering a structure of the document can infer the structure by traversing the relationships without parsing any source part or target part of the document.

2. The method of claim 1, wherein processing the relationships comprises returning a location of the part that is the target part of the relationship.

3. The method of claim 2, wherein processing the relationships further comprises returning an indication as to whether the target part is internal or external to the document.

4. The method of claim 2, wherein processing the relationships further comprises returning a relationship type associated with a relationship.

5. The method of claim 2, wherein processing the relationships further comprises returning an identifier utilized to reference the relationship within the source part.

6. The method of claim 1, further comprising dictating by internal relationships which of the separate parts are loaded by the applications when the document is loaded.

7. The method of claim 1, further comprising controlling which of the relationships are valid based on confirming whether a target part referenced by the source part via a relationship listed in the relationship part matches the relationship listed.

8. The method of claim 7, wherein controlling which of the relationships are valid comprises severing one of the relationships that does not match the target part wherein severing one of the relationships effectively removes the target part from the collection.

9. The method of claim 7, further comprising binding a lifetime of the target part to the source part.

10. The method of claim 1, further comprising dictating by at least one of relationship type or target mode which of the separate parts is loaded when applications load the document.

11. The method of claim 1, further comprising relating at least one of the parts to a main content part of the collection wherein the at least one part represents a data structure capable of being referenced by any part of the document.

12. The method of claim 1, wherein representing a link between any of the parts as a relationship listed in a relationship part comprises expressing the list of relationships in extensible markup language (XML).

13. The method of claim 3, wherein each relationship type comprises an absolute uniform resource identifier that uniquely defines a role of a relationship and wherein discovering a structure of the document comprises:

loading each relationship type associated with a relationship;

navigating through at least one of the relationship parts;

traversing at least one list of relationships; and

locating one of the separate parts to be at least one of audited, modified, deleted, or copied without parsing any source part or any target part of the document.

14. A computer-readable medium having control logic stored therein for causing a computer to structure an electronic document, the control logic comprising computer-readable program code for causing the computer to:

organize parts of a document as a collection of separate parts wherein the parts comprise at least one of a resource internal to the document or a resource external to where the document is located;

represent a link between any of the parts as a relationship listed in a relationship part associated with a part of the document that is a source part of one or more relationships to be processed wherein the relationship part contains a list of relationships for the source part and wherein processing the relationships returns content of a part that is a target part of a relationship; and

represent via the relationship part how one or more separate parts of the collection relate to other separate parts;

whereby an application can infer a structure of the document by traversing the relationships without parsing any source part or any target part of the document.

15. The computer-readable medium of claim 14, further comprising computer-readable program code for causing the computer when representing via the relationship part how one or more separate parts of the collection relate to other separate parts to:

track the resource internal to the document via an internal relationship; and

track the resource external to where the document is located via an external relationship.

16. The computer-readable medium of claim 14, further comprising computer-readable program code for causing the computer to dictate by internal relationships which of the parts are loaded by the application when the document is loaded.

17. The computer-readable medium of claim 14, wherein a relationship type comprising an absolute uniform resource identifier that uniquely defines a role of a relationship is associated with each relationship.

18. A computer-readable medium having computer-executable components, comprising:

a first component that is arranged to identify from a source part of an electronic document a target part of the document in a relationship with the source part wherein the relationship defines a link between the source part and the target part and wherein the first component is unique within a relationship part containing a list of relationships associated with the source part;

a second component comprising a uniform resource identifier (URI) arranged to define a role of the relationship;

a third component comprising a second URI arranged to point to the target part; and

a fourth component arranged to specify whether the third component points to one of a resource inside the electronic document or a resource outside the electronic document.

19. The computer-readable medium of claim 18, wherein the third component comprises one of an absolute URI or a relative URI when the third component comprises the absolute URI, the fourth component points to the resource outside the electronic document;

and

wherein when the third component comprises the relative URI, the second URI is implied by a value of the fourth component.

20. The computer-readable medium of claim 19, wherein when the fourth component specifies that the third component points to the resource inside the electronic document, the third component comprises the relative URI resolved against a path to the source part;

and

wherein when the fourth component specifies that the third component points to the resource outside the electronic document, the third component comprises one of the absolute URI or the relative URI resolved against a location of the electronic document.