Abstract: Metadata is generated that contains attribute values for a first document that in turn contains one or more key words. The attribute values of the first document are based on contextual information such as attribute values associated with other documents that contain at least one of the key words. Once generated, the metadata may be associated with the first document. Related techniques, apparatuses, and articles are also described.

Abstract: A system includes execution of a software application based on metadata defining a first plurality of software components, reception of second metadata defining the first plurality of software components, determination, based on the second metadata, of a second plurality of the first plurality of software components for which the second metadata is different from the first metadata, and for which the second metadata is associated with elements of the software application, and generation of the elements of the software application based on the second metadata of the second plurality of software components.

Abstract: The present disclosure describes methods, systems, and computer program products for implementing web services. One method includes identifying a REST service for integration with a business application, identifying a set of metadata associated with the REST service, and generating a REST client proxy object associated with the REST service for use in consuming the REST service with the business application, where an instantiation of the REST client proxy object is consumable via the business application. In some instances, the method may include consuming the REST service using an instantiation of the generated REST client proxy object associated with the REST service. Further, the identified set of metadata associated with the REST service may include a service structure document and a metadata document. Generating the REST client proxy object may include generating at least one business configuration object and/or at least one authentication proxy artifact associated with the REST service.

Abstract: All metadata relevant to user interface functionality needed to provide a specific unit of business functionality can be stored in one of a plurality of autonomous metadata containers retained on at least one data storage device. After a subset of available business functionality to be provided to a user is determined, a set of the plurality of autonomous metadata containers required to provide the subset of available business functions can be identified. A user interface view can be generated to present a view associated with each of the set of the plurality of autonomous metadata containers, and the generated user interface view can be provided for display to the user. Related systems, articles of manufacture, and computer-implemented methods are described.

Abstract: Upon receiving a request for a user interface view from a user interface, a user identity and a user authorization class for a user of the user interface can be checked against a user registry and an authorization class registry, respectively. A user interface view component can be retrieved according to the user identity and the user authorization class. The user interface view can be generated by aggregating the retrieved user interface view component with at least one other user interface view component consistent with the user identity and user authorization class, and the generated user interface view can be returned for display to the user via the user interface. Related systems, articles of manufacture, and computer-implemented methods are described.

Abstract: A plurality of registrations corresponding to a user interface component can be stored. Based on at least one of a layer of a software architecture to which a specific user of a user interface has authorized access, an assignment of a work center view to the user, and business data, it can be determined that the user interface presented to the user should include a navigation target to the user interface component. At run time, a navigation link to the user interface component can be dynamically generated according to a relevant registration selected from the plurality of registrations. The user interface incorporating the navigation link to the user interface component can be displayed. Related systems, articles of manufacture, and computer-implemented methods are described.

Abstract: Metadata is generated that contains attribute values for a first document that in turn contains one or more key words. The attribute values of the first document are based on contextual information such as attribute values associated with other documents that contain at least one of the key words. Once generated, the metadata may be associated with the first document. Related techniques, apparatuses, and articles are also described.