Abstract: Various embodiments support or provide for binding markdown data content to an action. In particular, some embodiments provide a document editor for binding an action to content of a document, such as a markdown document. Such embodiments can enable a user to edit or generate a document using markdown syntax that links and binds the document to metadata, which enables some embodiments to enhance the content the document beyond what standard markdown permits, such as a user invokable action.

Abstract: Various embodiments support or provide for a software environment in which one or more software components (e.g., APIs) can be relationally composed together by logic (e.g., as defined using a computer language) to form an operation that abstracts details of the composition, such as details relating to the multiple API calls being made in the composition, to implement the logic of the operation. Depending on the embodiment, a particular software component environment can comprise one or more of the following: a data connector to an external software service; stored authentication information to establish access to the external software service; an operation having defined logic for using at least one data connector or another operation (e.g., from operation repository); or an endpoint for deploying the operation for access.

Abstract: Various embodiments support or provide for binding markdown data content to an action. In particular, some embodiments provide a document editor for binding an action to content of a document, such as a markdown document. Such embodiments can enable a user to edit or generate a document using markdown syntax that links and binds the document to metadata, which enables some embodiments to enhance the content the document beyond what standard markdown permits, such as a user invokable action.

Abstract: Various embodiments support or provide for interactive electronic documentation (or an electronic document) for operational activities associated with a system or service, such as one monitored or maintained by a system administrator or engineer. In particular, some embodiments provide for an interactive electronic document associated with a runbook, which can comprise a set of actions (e.g., list of operations, procedures, steps, and the like) to be performed with respect to a system or service in connection with an operational event, such as a system/service incident, scheduled maintenance, or a support operation.

Abstract: Various embodiments support or provide for a software environment in which one or more software components (e.g., APIs) can be relationally composed together by logic (e.g., as defined using a computer language) to form an operation that abstracts details of the composition, such as details relating to the multiple API calls being made in the composition, to implement the logic of the operation. Depending on the embodiment, a particular software component environment can comprise one or more of the following: a data connector to an external software service; stored authentication information to establish access to the external software service; an operation having defined logic for using at least one data connector or another operation (e.g., from operation repository); or an endpoint for deploying the operation for access.

Abstract: Various embodiments support or provide for a software environment in which one or more software components (e.g., APIs) can be relationally composed together by logic (e.g., as defined using a computer language) to form an operation that abstracts details of the composition, such as details relating to the multiple API calls being made in the composition, to implement the logic of the operation. Depending on the embodiment, a particular software component environment can comprise one or more of the following: a data connector to an external software service; stored authentication information to establish access to the external software service; an operation having defined logic for using at least one data connector or another operation (e.g., from operation repository); or an endpoint for deploying the operation for access.

Abstract: Various embodiments support or provide for a software environment in which one or more software components (e.g., APIs) can be relationally composed together by logic (e.g., as defined using a computer language) to form an operation that abstracts details of the composition, such as details relating to the multiple API calls being made in the composition, to implement the logic of the operation. Depending on the embodiment, a particular software component environment can comprise one or more of the following: a data connector to an external software service; stored authentication information to establish access to the external software service; an operation having defined logic for using at least one data connector or another operation (e.g., from operation repository); or an endpoint for deploying the operation for access.

Abstract: Various embodiments support or provide for interactive electronic documentation (or an electronic document) for operational activities associated with a system or service, such as one monitored or maintained by a system administrator or engineer. In particular, some embodiments provide for an interactive electronic document associated with a runbook, which can comprise a set of actions (e.g., list of operations, procedures, steps, and the like) to be performed with respect to a system or service in connection with an operational event, such as a system/service incident, scheduled maintenance, or a support operation.

Abstract: Various embodiments support or provide for binding markdown data content to an action. In particular, some embodiments provide a document editor for binding an action to content of a document, such as a markdown document. Such embodiments can enable a user to edit or generate a document using markdown syntax that links and binds the document to metadata, which enables some embodiments to enhance the content the document beyond what standard markdown permits, such as a user invokable action.

Abstract: A method and associated computer system and computer program product. An image is obtained of a product recommender who is interacting with a product. The product recommender is identified based on the image. Information on the product is provided based on the identified product recommender.

Abstract: Various embodiments support or provide for a software environment in which one or more software components (e.g., APIs) can be relationally composed together by logic (e.g., as defined using a computer language) to form an operation that abstracts details of the composition, such as details relating to the multiple API calls being made in the composition, to implement the logic of the operation. Depending on the embodiment, a particular software component environment can comprise one or more of the following: a data connector to an external software service; stored authentication information to establish access to the external software service; an operation having defined logic for using at least one data connector or another operation (e.g., from operation repository); or an endpoint for deploying the operation for access.

Abstract: Various embodiments support or provide for a software environment in which one or more software components (e.g.. APIs) can be relationally composed together by logic (e.g,, as defined using a computer language) to form an operation that abstracts details of the composition, such as details relating to the multiple API calls being made in the composition, to implement the logic of the operation. Depending on the embodiment, a particular software component environment can comprise one or more of the following: a data connector to an external software service; stored authentication information to establish access to the external software service; an operation having defined logic for using at least one data connector or another operation (e.g., from operation repository); or an endpoint for deploying the operation for access.

Abstract: A method and associated computer system and computer program product. An image is obtained of a product recommender who is interacting with a product. The product recommender is identified based on the image. Information on the product is provided based on the identified product recommender.

Abstract: An imitating natural plant fiber, preparation method thereof and the fabric made of it are provided. The preparation method includes the following steps: rolling and milling the mixture of plural first polyolefine chips, constant thermoplastic elastomer (TPE) and plural microcapsules which encapsulate essential oil extracted from natural plant in the twin-screw extruder, thus plural masterbatches can be made; melting and mixing the above masterbatches and plural second polyolefine which is same as the first one, thus a composite can be made, wherein the final content of the microcapsules is 1-32% by weight; and producing fibers by spinning, cooling, heat stretching, and heat setting. The fiber and the fabric made of it have durable natural plant aroma.

Abstract: A functional fiber, preparation method thereof and the fabric made of it are provided. The preparation method includes the following steps: rolling and milling plural first polyolefine chips, constant thermoplastic elastomer (TPE) and plural functional particles into plural masterbatches in twin-screw extruder; melting and mixing the plural functional masterbatches and plural second polyolefine chips which are the same as the first polyolefine into the composite material, wherein the final content of the plural functional particles are 1-10 wt. % based on the weight of the composite material; producing fibers with the composite material by spinning, cooling, heat stretching, and heat setting. The fiber may be made into fabric. The fiber and fabric have the function of deodorization, antibiosis, mildew-proof or generating negative ion and further improve the air filtration effect.