Software versioning

Abstract: In response to receiving a request for data stored according to a first version of a data type, a second version of the data type supported by the requester is determined, and the requested data is transformed from the first version to the second version to provide access to the data.

Abstract: Version management for manufacturing system software involves a two-part data structure, having two identifiers that are separately and automatically modified, depending upon the changes or modifications that are made, respectively, to top-level and lower-level subsets of manufacturing system programs. According to various other aspects of the present invention, methods for managing revisions involve automatically assigning a version designator under preselected conditions, automatically notifying personnel having a need to know of the change, and managing revisions by way of a revision compare function.

Abstract: Modelling and version control both play key roles in industrial-scale software development, yet their integration has proved difficult Significant effort has been expended on improving file-based merging of modellers’ work, but empirical research shows the results of that approach still leave much to be desired in practice Approaches based on multi-user modelling databases have often foundered by locking too broadly, thus preventing work on different elements in the same model, or by handling versioning themselves, leading to a silo This article presents an approach to combining multi-user modelling with any external version control system, with no merging and no lock-outs

Abstract: New polymers are disclosed which absorb or emit photons in the visible or ultraviolet spectrum. The polymers when bound to ligands or receptors are useful as reagents for the detection of substances in physiological fluids. Also disclosed are methods of preparing said polymers and reagents and methods of employing said reagents in immunoassay systems.