Abstract: Systems and techniques are disclosed for improving the management of data contracts during a software development lifecycle. A system can include a data contract metadata store, components for interacting with the metadata store to support development tool integration, and interchange features for verified build processes. A service can be provided that receives a developer package from a development client application, parses the developer package to generate data contract metadata, modifies a data contract metadata store in accordance with at least one command received with the developer package, and communicates notification data, when included with the data contract metadata, to a notification service.

Abstract: The extract and transformation operation performed on multiple data sources. In the extract operation, a computing system periodically performs an extraction operation on the data sources, perhaps as defined by metadata. The transformation operation is performed on at least some the extracted data, and is periodically performed, perhaps also in a manner that is defined by metadata. When performing each iteration of the transformation operation, the computing system performs a transformation operation on valid data, marks other data as suspect (due to a dependency on data that is not present), and completes transformation on yet other data that had previously been marked as suspect or perhaps reaffirms its suspect status if the needed data is still not available.

Abstract: The extract and transformation operation performed on multiple data sources. In the extract operation, a computing system periodically performs an extraction operation on the data sources, perhaps as defined by metadata. The transformation operation is performed on at least some the extracted data, and is periodically performed, perhaps also in a manner that is defined by metadata. When performing each iteration of the transformation operation, the computing system performs a transformation operation on valid data, marks other data as suspect (due to a dependency on data that is not present), and completes transformation on yet other data that had previously been marked as suspect or perhaps reaffirms its suspect status if the needed data is still not available.

Abstract: This invention features pyrimidine compounds of formula (I): 1

Abstract: This invention features pyrimidine compounds of formula (I): aryl, or heteroaryl; each of R2 and R4, independently, is Rc, halogen, nitro, cyano, isothionitro, SRc, or ORc; or R2 and R4, taken together, is carbonyl; R3 is Rc, alkenyl, alkynyl, ORc, OC(O)Rc, SO2Rc, S(O)Rc, S(O2)NRcRd, SRc, NRcRd, NRcCORd, NRcC(O)ORd, NRcC(O)NRcRd, NRcSO2Rd, CORc, C(O)ORc, or C(O)NRcRd; R5 is H or alkyl; n is 0, 1, 2, 3, 4, 5, or 6; X is O, S, S(O), S(O2), or NRc; Y is a covalent bond, CH2, C(O), C═N—Rc, C═N—ORc, C═N—SRc, O, S, S(O), S(O2), or NRc; Z is N or CH; one of U and V is N, and the other is CRc; and W is O, S, S(O), S(O2), NRc, or NC(O)Rc; in which each of Ra and Rb, independently, is H, alkyl, aryl, heteroaryl; and each of Rc and Rd, independently, is H, alkyl, aryl, heteroaryl, cyclyl, heterocyclyl, or alkylcarbonyl.

Abstract: This invention features pyrimidine compounds of formula (I): 1 2