Dynamic schema assembly to accommodate application-specific metadata

• US 8,244,694 B2
• Filed: 09/12/2006
• Issued: 08/14/2012
• Est. Priority Date: 09/12/2006
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Petri, John E.
• Primary Examiner(s): Kim, Charles
• Assistant Examiner(s): MUELLER, KURT A
• Application Number:
  US11/531,096
• Publication Number:
  US 20080065678A1
• Time in Patent Office: 2,163 Days
• Field of Search: 707/694
• US Class Current: 707/694
• CPC Class Codes: G06F 16/83 Querying

Abstract

Embodiments of the invention provide a method, system, and article of manufacture for the dynamic schema assembly for documents managed by a content management system (CMS). In one embodiment, a transient, application specific markup schema is dynamically generated when a user accesses a data object managed by the CMS. For example, users may perform operations such as checking out a document from the CMS, viewing a document in the CMS or exporting a document from the CMS. The transient schema is configured to accommodate application-specific metadata, without directly changing or interfering with a base schema associated with the data object.

Claims

1. A computer-implemented method for providing dynamic schema assembly to accommodate application specific metadata in data objects managed by a content management system (CMS), comprising:

receiving a request to access a document from the CMS, wherein the document is associated with a base storage schema, wherein content of the document is composed according to the base storage schema, wherein the base storage schema specifies a valid set of markup language tags and markup language attributes for use in the document;

modifying an instance of the document by embedding the application specific metadata in the document, wherein the application specific metadata includes at least one of a markup language tag and a markup language attribute that is not valid according to the base storage schema;

modifying the base storage schema associated with the document to accommodate the application specific metadata by adding the at least one markup language tag and markup language attribute from the application specific metadata to the base storage schema, thereby creating a transient schema, wherein the modified instance of the document is valid according to the transient schema;

providing the modified instance of the document and the transient schema separately to a requesting application in response to the request;

receiving the modified instance of the document back from the requesting application;

stripping the application specific metadata from the modified instance of the document, wherein the modified, stripped instance of the document received back from the requesting application is valid according to the base storage schema; and

storing the modified, stripped instance of the document in the CMS.

2. The computer-implemented method of claim 1, wherein the CMS stores the document as one or more individual document fragments, and wherein generating the modified instance of the document further comprises assembling the one or more document fragments, and wherein the application specific metadata specifies boundaries between the one or more fragments.

3. The computer-implemented method of claim 1, wherein the application specific metadata specifies read/write rules for portions of the modified instance of the document enforced by the client application.

4. The computer-implemented method of claim 1, wherein rewriting the base storage schema comprises adding elements to the schema describing the application specific metadata.

5. The computer-implemented method of claim 1, wherein the document is an XML document, and wherein the base storage schema is an XML schema.

6. The computer-implemented method of claim 1, wherein storing the modified, stripped instance of the document in the CMS comprises bursting the modified instance of the document received back from the client application, into one or more document fragments according to the application specific metadata, and storing each fragment in the CMS.

19. The computer-implemented method of claim 1:

wherein the markup language tags are chosen from the group consisting of html tags and XML tags; and

wherein the markup language attributes are chosen from the group consisting of html attributes and XML attributes.

7. A computer-readable storage medium containing a program which, when executed, performs an operation for providing dynamic schema assembly to accommodate application specific metadata in data objects managed by a content management system (CMS), the operation comprising:

receiving a request to access a document from the CMS, wherein the document is associated with a base storage schema, wherein content of the document is composed according to a the base storage schema, and wherein the base storage schema specifies a valid set of markup language tags and markup language attributes for use in the document;

modifying an instance of the document by embedding the application specific metadata in the document, wherein the application specific metadata includes at least one of a markup language tag and a markup language attribute that is not valid according to the base storage schema;

modifying the base storage schema associated with the document to accommodate the application specific metadata by adding the at least one markup language tag and markup language attribute from the application specific metadata to the base storage schema, thereby creating a transient schema, wherein the modified instance of the document is valid according to the transient schema;

providing the modified instance of the document and the transient schema separately to a requesting application in response to the request;

receiving the modified instance of the document back from the requesting application;

stripping the application specific metadata from the modified instance of the document, wherein the modified, stripped instance of the document received back from the requesting application is valid according to the base storage schema; and

storing the modified, stripped instance of the instance of the document in the CMS.

8. The computer-readable storage medium of claim 7, wherein the CMS stores the document as one or more individual document fragments, and wherein generating the modified instance of the document further comprises assembling the one or more document fragments, and wherein the application specific metadata specifies boundaries between the one or more fragments.

9. The computer-readable storage medium of claim 7, wherein the application specific metadata specifies read/write rules for portions of the modified instance of the document enforced by the client application.

10. The computer-readable storage medium of claim 7, wherein rewriting the base storage schema comprises adding elements to the schema describing the application specific metadata.

11. The computer-readable storage medium of claim 7, wherein the document is an XML document, and wherein the base storage schema is an XML schema.

12. The computer-readable storage medium of claim 7, wherein storing the modified, stripped instance of the document in the CMS comprises bursting the modified instance of the document received back from the client application into one or more document fragments according to the application specific metadata, and storing each fragment in the CMS.

13. A system, comprising:

a processor; and

a memory containing a content management system (CMS) configured to perform a method for providing dynamic schema assembly to accommodate application specific metadata in data objects managed by a content management system (CMS), comprising;

receiving a request to access a document from the CMS, wherein the document is associated with a base storage schema, wherein content of the document is composed according to the base storage schema, and wherein the base storage schema specifies a valid set of markup language tags and markup language attributes for use in the document,

modifying an instance of the document by embedding the application specific metadata in the document, wherein the application specific metadata includes at least one of a markup language tag and a markup language attribute that is not valid according to the base storage schema;

modifying the base storage schema associated with the document to accommodate the application specific metadata by adding the at least one markup language tag and markup language attribute from the application specific metadata to the base storage schema, thereby creating a transient schema, wherein the modified instance of the document is valid according to the transient schema,

providing the modified instance of the document and the transient schema separately to a requesting application in response to the request,

receiving the modified instance of the document back from the requesting application,

stripping the application specific metadata from the modified instance of the document, wherein the modified, stripped instance of the document received back from the requesting application is valid according to the base storage schema, and

storing the modified, stripped document in the CMS.

14. The system of claim 13, wherein the CMS stores the document as one or more individual document fragments, and wherein generating the modified instance of the document further comprises assembling the one or more document fragments, and wherein the application specific metadata specifies boundaries between the one or more fragments.

15. The system of claim 13, wherein the application specific metadata specifies read/write rules for portions of the modified instance of the document enforced by the client application.

16. The system of claim 13, wherein rewriting the base storage schema comprises adding elements to the schema describing the application specific metadata.

17. The system of claim 13, wherein the document is an XML document, and wherein the base storage schema is an XML schema.

18. The system of claim 13, wherein storing the modified, stripped instance of the document in the CMS comprises bursting the modified instance of the document received back from the client application into one or more document fragments according to the application specific metadata, and storing each fragment in the CMS.