Abstract: A virtual content repository (VCR) is a logical representation of one or more individual content repositories. The VCR uses a common Application Programming Interface (API) and a Service Provider Interface (SPI) to provide a single access point to one or more individual content repositories. The API describes how applications can interface with program logic and functionality provided by the content management system and the SPI describes how a content repository can be integrated into the VCR. A SPI adapter can be interposed between the at least one non-compliant repository in the VCR and the SPI. The SPI adapter can map a request to the non-compliant repository and provide content received from the non-compliant repository to originators of the requests.

Abstract: A virtual content repository (VCR) is a logical representation of one or more individual content repositories. The VCR uses a common Application Programming Interface (API) and a Service Provider Interface (SPI) to provide a single access point to one or more individual content repositories. The API describes how applications can interface with program logic and functionality provided by the content management system and the SPI describes how a content repository can be integrated into the VCR. A SPI adapter can be interposed between the at least one non-compliant repository in the VCR and the SPI. The SPI adapter can map a request to the non-compliant repository and provide content received from the non-compliant repository to originators of the requests.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for providing extensions to a Service Provider Interface (SPI) in a content management system. These mechanisms and methods for providing extensions to a Service Provider Interface (SPI) in a content management system can enable embodiments to integrate one or more of a plurality of content repositories into a virtual content repository (VCR) by mapping requests to access content received via a common Application Programming Interface (API) to at least one JSR-170 compliant repository and at least one SPI compliant repository. The ability of embodiments to provide so integrate disparate content repositories can enable one or more of navigation, CRUD operations (create, read, update, delete), versioning, workflows, and searching operations to operate on a plurality of repositories as though the plurality of repositories were one repository.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for providing linked property types in a content management system. These mechanisms and methods for providing linked property types in a content management system can enable users to specify a new property definition type, which refers to another node instance in the content management system. By specifying a link property definition type on a type, the user can then relate a node instance of the modeled type (link source) to any other node instance (link target) in the system. For example, a user can create a type Article with property definitions such as title, body and authorLink. The authorLink property definition can be a link type property definition. Then the user could define an Author content type. When an instance of an Article is created (anArticle), the authorLink property associated with anArticle could refer to a node instance of an Author.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for providing nested variables in a content management system. These mechanisms and methods for providing nested variables in a content management system can enable users to model types that can be used within other type definitions. This differs from the Type Inheritance feature in that types that make use of the nested type feature do not extend their functionality but define a property definition having a value defined by all property definitions in the nested type. For example, user can create a type address with property definitions such as street, city, zip code, etc. The user can then create another type person that has property definitions such as “name” and home address and business address. The two address property definitions can be represented by the address type, each with the address type's property definitions. Embodiments may further provide the ability to have abstract types and link property types.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for providing content management security to federated content repositories in a content management system and for interacting with a virtual content repository. These mechanisms and methods can enable embodiments to provide secure access to repositories based upon policies defined at a federated repository level and to secure repository access at the federated level based upon policies defined for differing classes of users. These abilities of embodiments can enable users to create services and applications by integrating content from unsecured repositories.

Abstract: In accordance with embodiments, there are provided mechanisms and methods for providing lightweight loading for managing content in federated content repositories. These mechanisms and methods for providing lightweight loading for managing content in federated content repositories can enable embodiments to provide subset(s) of content determined to satisfy the request from one or more content repositories integrated into a VCR. The ability of embodiments to provide subset(s) of content determined to satisfy the request can enable displaying content responsive to a request in a format appropriate to the requestor's request.