Abstract: Systems and methods for activating and using dynamic cards are disclosed. In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for activating a dynamic transaction instrument may include: (1) receiving, from an electronic device, an identification of an inactive financial instrument to activate; (2) receiving, from the electronic device, at least one parameter that restricts the use of the inactive financial instrument after it is activated; and (3) activating the inactive financial instrument subject to the at least one parameter by associating, at a backend, an account with the inactive financial instrument.

Abstract: Systems and methods for activating and using dynamic cards are disclosed. In one embodiment, in an information processing apparatus comprising at least one computer processor, a method for activating a dynamic transaction instrument may include: (1) receiving, from an electronic device, an identification of an inactive financial instrument to activate; (2) receiving, from the electronic device, at least one parameter that restricts the use of the inactive financial instrument after it is activated; and (3) activating the inactive financial instrument subject to the at least one parameter by associating, at a backend, an account with the inactive financial instrument.

Abstract: Systems and methods access non-compatible content repositories that are not natively accessible to a content management system. A metadata registry maintains metadata about content stored in both compatible and non-compatible repositories. For content in a non-compatible repository, the metadata indicates a repository interface capable of accessing the non-compatible repository. The content manager communicates with the repository interfaces to access the content in non-compatible repositories. The content manager may receive a request for content in a non-compatible repository, refer to the metadata registry to select a repository interface to employ, transmit a request for the requested content to the selected repository interface, and receive the requested content from the repository interface. A repository interface registry maintains information about available repository interfaces.

Abstract: Systems and methods access non-compatible content repositories that are not natively accessible to a content management system. A metadata registry maintains metadata about content stored in both compatible and non-compatible repositories. For content in a non-compatible repository, the metadata indicates a repository interface capable of accessing the non-compatible repository. The content manager communicates with the repository interfaces to access the content in non-compatible repositories. The content manager may receive a request for content in a non-compatible repository, refer to the metadata registry to select a repository interface to employ, transmit a request for the requested content to the selected repository interface, and receive the requested content from the repository interface. A repository interface registry maintains information about available repository interfaces.

Abstract: Systems access non-compatible content repositories that are not natively accessible to a content management system. A metadata registry maintains metadata about content stored in both compatible and non-compatible repositories. For content in a non-compatible repository, the metadata indicates a repository interface capable of accessing the non-compatible repository. The content manager communicates with the repository interfaces to access the content in non-compatible repositories. The content manager may receive a request for content in a non-compatible repository, refer to the metadata registry to select a repository interface to employ, transmit a request for the requested content to the selected repository interface, and receive the requested content from the repository interface. A repository interface registry maintains information about available repository interfaces.

Abstract: Systems and methods access non-compatible content repositories that are not natively accessible to a content management system. A metadata registry maintains metadata about content stored in both compatible and non-compatible repositories. For content in a non-compatible repository, the metadata indicates a repository interface capable of accessing the non-compatible repository. The content manager communicates with the repository interfaces to access the content in non-compatible repositories. The content manager may receive a request for content in a non-compatible repository, refer to the metadata registry to select a repository interface to employ, transmit a request for the requested content to the selected repository interface, and receive the requested content from the repository interface. A repository interface registry maintains information about available repository interfaces.

Abstract: An application programming interface accesses page analysis functionality of a block selection program and accesses data structures resulting therefrom. The application programming interface includes plural page analysis functionality which manipulate block selection functions including functions to analyze a document page, to create a hierarchical tree structure corresponding to the analyzed document page, and to return a pointer which is a block ID or a root node of the analyzed page. Plural hierarchical tree structure accessing functions traverse the hierarchical tree structure, and locate desired nodes in the hierarchical tree structure.

Abstract: A combustible bayonet type primer for combustible cannon cartridge cases comprises a primer head assembly adapted to be inserted in a cartridge case, a tubular housing made of a combustible material, an igniter strand axially disposed in said housing, and a confining means for confining one end of the igniter strand so that the initial ignition rate is about 1000 m/s. The ignited strand in turn ignites a black powder charge contained within a cloth bag within the tubular housing. The housing is an unpressurized container for the igniter strand and the black powder charge and is consumed during the burn of the propellant bed along with the igniter strand and the combustible case.