Abstract: A content management system (CMS) includes information in a document that correlates each element for which a content rule needs to be checked with the corresponding content rule. By including information in the document regarding which content rules apply to the elements in the document, the CMS does not process any rules that do not apply to the document. When the document is checked into the CMS repository, only the content rules specified in the document are checked. An editor allows checking an element against the content rules as a document is created. If the editor is on a client computer system, and the editor checks all content rules that correspond to the elements in a document, the document may be modified to indicate the checking of the content rules has already been performed, which allows the CMS to write the document to the repository without checking the content rules.

Abstract: A content management system (CMS) provides a way to include data from an external source as an object in the repository managed by the CMS. The CMS includes an external data mechanism that processes a document with a query to a data source external to the repository. The external data mechanism executes the query, and creates one or more objects in the repository according to the type of data returned as defined by classification rules. Each object containing data returned from the query is linked to that query via a formal relationship in the CMS. When an object that has a formal relationship with a query is checked out of the repository, the query corresponding to the object may be executed, and the data returned from the query may be stored in the object. In the alternative, the data may be used directly if a corresponding lifecycle policy indicates the corresponding query should not be executed.

Abstract: A content management system (CMS) for computer software provides automatic notification and correlation of changes in a design document with corresponding code, and provides automatic notification and correlation of changes in the code with one or more corresponding design documents. Traceability rules are defined that correlate which portions of the code correspond to which portions of the design document. A traceability update policy governs whether interested parties are notified of a change to either the design document or the corresponding code, and whether the change to one causes an automatic update to the other. The result is a content management system that helps keep the code and corresponding design documents consistent with each other so the system has accurate and consistent information at all times.

Abstract: A content management system (CMS) allows a CMS administrator to access data from an external source, such as a web page, and to correlate the external data with an attribute for a document type. When a user authors a document of that type in the CMS, the user may select from a picklist that includes values retrieved from the external data source. A metadata acquisition policy associated with the attribute may specify one or more criteria for determining if and when changes to the external data source should be automatically reflected in the attribute, and if notifications of changes to the external data should be provided to a CMS administrator.

Abstract: A content management system (CMS) autonomically updates one or more templates based on characteristics of documents in the repository, and based on specified criteria in an autonomic template update policy. At an appointed time, the CMS finds a template in the repository, retrieves an autonomic template update policy corresponding to the template, and determines from characteristics of documents in the repository whether the criteria in the autonomic template update policy allows autonomically updating the template. If the criteria are met, the template is autonomically updated without intervention by a CMS administrator. The result is a CMS where templates autonomically change as the content in the repository changes.

Abstract: A content management system (CMS) includes a component identification mechanism for identifying components in a component-centric way that takes into account specified conditions for a link location in a compound document as well as component relationships and conditions. By using the relationships and conditions, a more intelligent choice may be made when identifying components for a particular link location. The identifying of components for a given link location in a compound document may be used by the content management system when auto-population is enabled, and may be used by the content management system to provide a list of candidate components to a user when auto-suggestion is enabled.

Abstract: A content management system (CMS) autonomically generates structure for a document when a synchronization rule references structure that does not exist in the document. A dynamic structure policy specifies at least one criterion that determines if and how the structure is autonomically generated. By autonomically generating structure in a document, a CMS administrator or CMS user (such as the author) is relieved of the manual task of generating the structure before the synchronization rule can be successfully processed. Once dynamically generated, the added structure may be auto-populated with dummy data or with default data specified in the autonomic structure policy.

Abstract: A content management system (CMS) includes an autonomic rule generation mechanism that autonomically analyzes existing content and generates rules according to a defined rule generation policy. Autonomically generated rules may include bursting rules, synchronization rules and linking rules. By autonomically generating rules based on the characteristics of content in the repository, the CMS can dramatically improve the ease and efficiency of managing a CMS.

Abstract: A content management system (CMS) allows defining multi-element burst rules that allow multiple elements to be bursted to a single object. A multi-element burst mechanism performs the bursting of multiple elements when a multi-element burst rule is processed. A multi-element burst policy allows a user to specify conditions that govern the function of the multi-element burst mechanism. The result is a CMS that includes multiple elements in a single object, thereby enhancing reusability of content in the CMS.

Abstract: A method and apparatus for improving the efficiency of document transformation processes is disclosed. For example, more efficient XML transformations may be performed against a source document that has incurred minor or incremental changes. Rather than apply a transform (e.g., an XSLT document) to a complete document each time any fragment of the source document is modified, a document management system may be configured to apply the transform only to the modified portions of the document.

Abstract: A content management system (CMS) provides a way to minimize accesses to a repository when reconstituting a document. When a document is first reconstituted, the CMS reads links in the document, reads the corresponding objects from the repository, then stores the values of those objects in fallback elements in the document. In addition, a list is generated that provides both original links to the objects in the repository and voidable links to those object, and the document is then modified, if needed, to reference the voidable links. When the document needs to be subsequently reconstituted, the repository is queried to determine which of the objects corresponding to the original links have not changed since the last reconstitution. If the object has not changed, the voidable link in the list is invalidated for the object, causing the fallback element to be used without accessing the repository.

Abstract: Method, article and apparatus for the reusability of data objects such as XML document fragments managed by a content management system (CMS). Embodiments of the invention may be used to enforce validation requirements for a multi-context XML fragment (i.e., for a fragment referenced in two or more documents managed by the CMS). When changes are made to a multi-context fragment, the CMS may detect any validation problems and take corrective action to resolve the validation problem.

Abstract: A content management system (CMS) includes rule conditions that determine when the rules are applied, and additionally includes alteration instructions for dynamically changing content in the repository and alteration conditions that determine when the alteration instructions will be executed. Rule conditions and alteration conditions may include values from metadata related to content, values from anywhere in the content, values from the metadata of objects linked into the content, values from anywhere in the content of objects linked into the content, the user's current role, or literal values. Rule conditions and alteration conditions may also include various operators, including equals, not equals, greater than, less than, greater than or equal, less than or equal, contains, exists, and starts with, along with the negation of each of these operators. Providing rule conditions and alteration instructions and conditions provides great flexibility and power that greatly improves the functionality of a CMS.

Abstract: Method and apparatus for chaining configuration sets in a content management system (CMS). A CMS groups configuration rules from multiple configuration sets and for rule inheritance between configuration sets. The configuration sets provide a set of processing rules or artifacts used with content managed by the CMS, (e.g., a collection of XML documents).

Abstract: In an embodiment, a link to a current page is received from a user. In response to receiving the link, a descendant page of the current page is selected that meets a policy associated with the domain of the current page. The current page and the descendant page are retrieved and displayed. The current page and the descendant page are simultaneously viewable. The current page and the descendant page are in the same domain. In various embodiments, the descendant page is specified by a server, by the user, or is on a most-frequently traversed path in the domain. In various embodiments, the descendant page is a terminal page on the most-frequently traversed path or is at a level on the path that is specified by the policy.

Abstract: A mechanism to efficiently classify and pre-process rules, encode and embed portions of the rules in the client page, and process them with minimal return trips to the server. One embodiment of the invention comprises a method for providing web applications, comprising generating a rules mapping for a web application view; and transmitting the web application view to a client device.

Abstract: In an embodiment, an upgrade rule associated with a configuration set is found, and a document associated with the upgrade rule is found. The configuration set includes a schema and an upgrade transformation, and the upgrade transformation specifies a change that was made to the schema. The document includes a lifecycle state and an element. If the upgrade rule indicates an automatic upgrade, then a mutability rule associated with the lifecycle state of the document is found and a decision is made whether the mutability rule allows the document to be changed. If the mutability rule allows the document to be changed, the element in the document is changed to include the change specified by the upgrade transformation at a time specified by the upgrade rule.