System and method for maintaining componentized content

• US 20050080804A1
• Filed: 02/10/2003
• Published: 04/14/2005
• Est. Priority Date: 10/30/2001
• Status: Abandoned Application

• Current Assignee: Interwoven Incorporated (HP Inc.)
• Original Assignee: Interwoven Incorporated (HP Inc.)
• Inventors: Jia, Jack Shilian, Bradshaw, Robert David Jr., Park, Britt, Cochrane, Kevin Vincent, Zhong, Meili
• Application Number:
  US10/504,004
• Publication Number:
  US 20050080804A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A system and method is provided for creating component to save storage space, and to efficiently organize and maintain content. In one embodiment, a system is provided that is configured to manage the componentization (802) of content within entities that share common content. The system includes a content control (118) module configured to manage the editing (236) of content and their state such as whether and when they were modified (606) or mutated (610). Alternatively, the system may include a repository (700) configured to manage the indexing (702) and searching of component (704).

Claims

1. A method of dynamically composing a componentized electronic document comprising steps of:

(a) receiving a document containing an entity skeleton and tags that reference to components;

(b) locating component references in said entity skeleton;

(c) identifying one or more components according to component tags;

(d) determining a component which has a changed state;

(e) based on said changed state, mapping to a component content corresponding to said determined component;

(f) retrieving said corresponding component content from a memory location; and

(g) incorporating said retrieved component content into said document.

2. The method according to claim 1, wherein step (c) comprises the step of:

identifying a component by analyzing a component tag according to a category and a unique identification indicator.

3. The method according to claim 1, wherein step (e) comprises the steps of:

checking whether said corresponding component content is located in a buffer;

if said corresponding component content is not located in a buffer, continuing on step (f);

if said corresponding content is located in a buffer, determining whether said corresponding component content has been updated;

if said corresponding content is updated, then retrieving said updated component content from said buffer and continuing on step (g); and

if said corresponding component content is not updated, then continuing on step (f).

4. The method according to claim 1, wherein said entity is configured in an XML format containing text and graphical data.

5. The method according to claim 1, wherein said components are shared with other entities to provide universal Consistence among documents that incorporate said components.

6. The method according to claim 1, wherein said entity skeleton Is configured to contain references to components in predetermined locations within said entity skeleton.

7. The method according to claim 1, wherein said entity skeleton includes non-componentized content within said entity skeleton.

8. A system configured to manage content componentization of electronic documents that share common content, each of said documents having an entity skeleton comprising componentized content and tags that identify said componentized content, said system comprising:

a content control module configured to manage content;

an editing application configured to manage content editing;

a component control module configured to manage components and to track changes in states of said components, wherein each of said components has its corresponding content;

a repository configured to manage indexing, searching and retrieving of said components; and

a component storage configured to store indexed components;

wherein when a component is updated, each and every of said documents that reference said updated component is automatically updated upon rendering.

9. The system according to claim 8, wherein said repository comprises an index module configured to manage component indexing and a query module configured to manage component searching.

10. The system according to claim 8, further comprising a version module configured to indicate state Information and version information of a component.

11. The system according to claim 8, further comprising a development server configured to develop documents having website content, said development server being communicatively connected to a global network which can be accessed by users.

12. The system according to claim 8, wherein said Index module manages component indexing according to tags associated with individual components, and wherein said query module manages component searching by setting parameters according to one or more query rules.