Abstract: An intelligent conflict detection system. The system provides semantic expression of edits and history-aware conflict detection in a large-scale service allowing multiple users to simultaneously work with the same document, which may result in conflicting edits. When submitted, changes to a version of a document are compared to all versions of the document created since the document was sourced. Edits to documents are expressed as intents describing the changes in terms of an action and object of that action based on a characteristic of the data being edited. Comparing the intent of current edits against the historical intent of the edits made in prior versions originating from the same source document allows the system to intelligently assess whether the edits are in conflict. History-aware semantic analysis results in users being prompted less frequently to resolve conflicts, which improves the user experience.

Abstract: An intelligent conflict detection system. The system provides semantic expression of edits and history-aware conflict detection in a large-scale service allowing multiple users to simultaneously work with the same document, which may result in conflicting edits. When submitted, changes to a version of a document are compared to all versions of the document created since the document was sourced. Edits to documents are expressed as intents describing the changes in terms of an action and object of that action based on a characteristic of the data being edited. Comparing the intent of current edits against the historical intent of the edits made in prior versions originating from the same source document allows the system to intelligently assess whether the edits are in conflict. History-aware semantic analysis results in users being prompted less frequently to resolve conflicts, which improves the user experience.

Abstract: An intelligent conflict detection system. The system provides semantic expression of edits and history-aware conflict detection in a large-scale service allowing multiple users to simultaneously work with the same document, which may result in conflicting edits. When submitted, changes to a version of a document are compared to all versions of the document created since the document was sourced. Edits to documents are expressed as intents describing the changes in terms of an action and object of that action based on a characteristic of the data being edited. Comparing the intent of current edits against the historical intent of the edits made in prior versions originating from the same source document allows the system to intelligently assess whether the edits are in conflict. History-aware semantic analysis results in users being prompted less frequently to resolve conflicts, which improves the user experience.

Abstract: An intelligent conflict detection system. The system provides semantic expression of edits and history-aware conflict detection in a large-scale service allowing multiple users to simultaneously work with the same document, which may result in conflicting edits. When submitted, changes to a version of a document are compared to all versions of the document created since the document was sourced. Edits to documents are expressed as intents describing the changes in terms of an action and object of that action based on a characteristic of the data being edited. Comparing the intent of current edits against the historical intent of the edits made in prior versions originating from the same source document allows the system to intelligently assess whether the edits are in conflict. History-aware semantic analysis results in users being prompted less frequently to resolve conflicts, which improves the user experience.

Abstract: A software application written for a server environment is transformed into one which runs in a rich client environment. An entity model defines data sources as they are accessed from the server and as they are accessed from the clients. An application programming interface defines stereotyped interfaces which provide the same functionality on the server and the clients. A metadata model describes the components which make up the application and defines the differences in structure between the server and clients. The metadata model also defines mappings between components used on the server and clients. Settings and context information which tailor the activation and functionality of the components is also captured in the metadata model. Automated transformation is performed by using the mappings to identify the component set to use for the clients, selecting the client version of the application programming interfaces, and selecting the appropriate settings and context information.

Abstract: A computing device having a dynamic metadata model includes an interface module, an algorithm module and a registration module. The interface module includes an interface that defines one or more API functions for obtaining metadata using an algorithm. At least one of the API functions is used with a plurality of algorithms. Each of the plurality of algorithms is associated with a business system. The algorithm module includes one or more algorithms that implement the API functions defined in the interface. The one or more algorithms provide metadata without accessing a metadata database. Each of the one or more algorithms is associated with a business system. The metadata is associated with API functions of the business system. The registration module registers the one or more algorithms on the computing device.

Abstract: An enterprise system may separate the executable functionality existing in backend applications, and the separation may be at differing levels of granularity. The separated functions of the application may be registered in a catalog in the form of metadata objects. Once the executable functionality has been registered, the authorization information for each granular functional object may be associated with authorization information. In this manner, the authorization of a service of an application may be made on a feature by feature (or object by object) basis in a unified manner.

Abstract: A data store catalogue service model is disclosed for exposing disparate data store services to clients without requiring explicit knowledge on how to interact with each disparate service. The data store catalogue service model may maintain interaction details for each data store service that clients may access for interacting with those services. The model may also maintain metadata that may describe the different types of services available for access by clients, the data types used by those services, how to access the data provided by the services, and how to communicate semantically with the services for accessing the service's data. Additionally, the data store may include metadata that enables clients to interact with one or more registered data stores in a number of ways, such as for discovering registered data store services, entities, classes, and/or any associations between related entities within the same or among disparate services.

Abstract: A system facilitates the search engine to search for pieces of information in various databases and application documents without the need to know the specific protocols to communicate with the various databases and application documents, such as Microsoft Excel documents. Despite the multitude of possible protocols which a crawler would have to use to connect to the databases, the system includes a unifying application programming interface to unify the way to access pieces of information in the databases and application documents.

Abstract: A computing device having a dynamic metadata model includes an interface module, an algorithm module and a registration module. The interface module includes an interface that defines one or more API functions for obtaining metadata using an algorithm. At least one of the API functions is used with a plurality of algorithms. Each of the plurality of algorithms is associated with a business system. The algorithm module includes one or more algorithms that implement the API functions defined in the interface. The one or more algorithms provide metadata without accessing a metadata database. Each of the one or more algorithms is associated with a business system. The metadata is associated with API functions of the business system. The registration module registers the one or more algorithms on the computing device.

Abstract: An adaptive picker for selecting data in disparate information systems is provided. The adaptive picker may be implemented by an application to pick items from one or more data stores, which are associated with other applications. The adaptive picker determines items provided by the data store that are available for picking and the types of data associated with the items. The adaptive picker receives key information provided by a user through the first application and searches for the available items based on the key information. The adaptive picker also filters the items to identify a desired item. The adaptive picker can determine the filtering capabilities associated with the data stores and automatically adapt to these filtering capabilities. The adaptive picker can retrieve a desired item with a key information search that matches the key information with a unique identifier associated with desired item. The key information search enables a user to pick an item without browsing.

Abstract: A software application written for a server environment is transformed into one which runs in a rich client environment. An entity model defines data sources as they are accessed from the server and as they are accessed from the clients. An application programming interface defines stereotyped interfaces which provide the same functionality on the server and the clients. A metadata model describes the components which make up the application and defines the differences in structure between the server and clients. The metadata model also defines mappings between components used on the server and clients. Settings and context information which tailor the activation and functionality of the components is also captured in the metadata model. Automated transformation is performed by using the mappings to identify the component set to use for the clients, selecting the client version of the application programming interfaces, and selecting the appropriate settings and context information.

Abstract: Systems and methods for annotating documents in provided in a collaborative application with data from disparate information systems are provided. The collaborative application enables the annotation of a document with data provided by another application. Particularly, the collaborative application enables a user to pick an item from a data store associated with another application. An association is established between the document and the picked item and retrieves data associated with the picked item from the data store. The document is annotated with the retrieved data. Because of the association, the collaborative application can determine that the picked item in the data store has been modified by the other application. The collaborative application may retrieve modified data associated with the picked item from the data store and update the annotation data associated with the document with the modified data.

Abstract: A computer-implemented method for fulfillment in a distributed supply chain environment includes receiving an available-to-promise (ATP) request comprising a plurality of request line-items each corresponding to a desired product, and generating one or more component ATP requests using at least one rule and based on the request line-items. At least one of the rules identifies a sourcing constraint associated with a customer. The method also includes communicating the component ATP requests to at least one supplier associated with the desired product. The supplier is determined according to at least one rule identifying the sourcing constraint.