Abstract: A processor-implemented method for the ownership transfer and tracking of tangible assets using a blockchain is described. In an embodiment, the method includes generating a root node associated with a tangible asset via a processor. The root node has a first hash value that represents a storage location of the root node, data associated with a tangible asset, and a second hash value that represents a storage location of the subsidiary node. The method also includes storing a hierarchical hash-linked tree structure in a non-transitory, processor-readable memory. The hierarchical hash-linked tree structure can include multiple nodes. The multiple nodes include the root node and the subsidiary node. The subsidiary node has the second hash value, and data associated with a tangible sub-asset of the tangible asset.

Abstract: Techniques for generating application interfaces based on semantic-level data are described herein. Application developers may semantically define an application flow. Based on the definition, a system may identify a template of a multipage navigable interface that is compatible with the flow. If multiple templates are compatible, then a template may be recommended or automatically selected based on the semantic information provided by the developer. The system may generate, based on the template and the semantic definition, a multipage navigable interface. The template may encapsulate some design and functional elements in a manner that is independent of the semantic definition.

Abstract: Techniques for component-based software engineering, and more particularly, to techniques for enhancing component based development systems by making components self-aware with respect to the applications that they may be consumed in or other peer components within the applications. An exemplary technique includes determining an addition of one or more components to an interface of an application; identifying an asset definition within metadata of a component of the one or more components added to the interface of the application, where the asset definition provides self-wiring or self-configuring instructions for an asset that needs to be created for the component within a predefined scope when the component is added to the interface; and creating the asset for the component based on the asset definition.

Abstract: Templates for mapping data events to API calls is leveraged in a digital medium environment. For instance, to enable communication between an event-driven architecture (EDA) system and an application programming interface (API) system, the described techniques utilize templates that enable EDA events to be mapped to API communications and API communications to be mapped to EDA events.

Abstract: Templates for mapping data events to API calls is leveraged in a digital medium environment. For instance, to enable communication between an event-driven architecture (EDA) system and an application programming interface (API) system, the described techniques utilize templates that enable EDA events to be mapped to API communications and API communications to be mapped to EDA events.

Abstract: Techniques for generating application interfaces based on semantic-level data are described herein. Application developers may semantically define an application flow. Based on the definition, a system may identify a template of a multipage navigable interface that is compatible with the flow. If multiple templates are compatible, then a template may be recommended or automatically selected based on the semantic information provided by the developer. The system may generate, based on the template and the semantic definition, a multipage navigable interface. The template may encapsulate some design and functional elements in a manner that is independent of the semantic definition.

Abstract: Techniques are provided for encapsulating a user experience design for user interfaces of an application, where the user experience design comprises a look and feel of the application and a plurality of functional elements of the application. A plurality of rules for implementing the one or more user interfaces may be defined, and the rules may be based at least in part on the user experience design. Additionally, a pattern may be generated based at least in part on the plurality of rules. The pattern may be deployed to a distributed network of computing devices, and reused in the design of multiple other applications. The new user interfaces for those applications may be generated based at least in part on the pattern, where the additional applications comply with the look and feel and the plurality of functional elements of the other applications that share the pattern.

Abstract: Techniques for component-based software engineering, and more particularly, to techniques for enhancing component based development systems by making components self-aware with respect to the applications that they may be consumed in or other peer components within the applications. An exemplary technique includes determining an addition of one or more components to an interface of an application; identifying an asset definition within metadata of a component of the one or more components added to the interface of the application, where the asset definition provides self-wiring or self-configuring instructions for an asset that needs to be created for the component within a predefined scope when the component is added to the interface; and creating the asset for the component based on the asset definition.

Abstract: A motorized vehicle assembly includes an axle comprising a channel extending along a central axis of the axle, a socket positioned within the channel of the axle, and a motorized wheel configured to be mounted on an end the axle. The motorized wheel includes a boss configured to engage the end of the axle when the motorized wheel is mounted on the axle, an electric motor, a tire mounted on the rotor, and a plug positioned within the boss, the plug configured to engage with the socket when the motorized wheel is mounted on the axle. The electric motor includes a stator fixed to the boss and a rotor surrounding the stator, the rotor configured to rotate relative to the stator. The electric motor is configured to cause the rotor to rotate relative to the stator to cause the tire to rotate.

Abstract: Techniques for component-based software engineering, and more particularly, to techniques for enhancing component based development systems by making components self-aware with respect to the applications that they may be consumed in or other peer components within the applications. An exemplary technique includes determining an addition of one or more components to an interface of an application; identifying an asset definition within metadata of a component of the one or more components added to the interface of the application, where the asset definition provides self-wiring or self-configuring instructions for an asset that needs to be created for the component within a predefined scope when the component is added to the interface; and creating the asset for the component based on the asset definition.

Abstract: Systems and methods are provided for managing and tracking process pipelines and other flows in a way that reduces the requirement for a central controlling process to manage every step of the associated pipeline flow and the state associated with each running instance. Job information and pipeline state are tracked by each worker involved in the pipeline. This enables some key capabilities within these process pipelines such as dynamic process re-writing and cross security domain job execution.

Abstract: A motorized vehicle assembly includes an axle comprising a channel extending along a central axis of the axle, a socket positioned within the channel of the axle, and a motorized wheel configured to be mounted on an end the axle. The motorized wheel includes a boss configured to engage the end of the axle when the motorized wheel is mounted on the axle, an electric motor, a tire mounted on the rotor, and a plug positioned within the boss, the plug configured to engage with the socket when the motorized wheel is mounted on the axle. The electric motor includes a stator fixed to the boss and a rotor surrounding the stator, the rotor configured to rotate relative to the stator. The electric motor is configured to cause the rotor to rotate relative to the stator to cause the tire to rotate.

Abstract: A low voltage high current permanent magnet DC electromagnetic heteropolar motor, including (a) at least one permanent magnet rotor; (b) a shaft in mechanical communication with the rotor such that axial rotation of the rotor causes axial rotation of the shaft; (c) at least one stator winding; (d) a plurality of switches, each functioning to provide commutation switching for the stator so as to generate a torque on the rotor and thereby cause said axial rotation of the shaft, wherein a terminal voltage of said machine is equal to the voltage of one electrochemical cell, and wherein the power of said machine is at least 1 kW.

Abstract: A low voltage high current permanent magnet DC electromagnetic heteropolar motor, including (a) at least one permanent magnet rotor; (b) a shaft in mechanical communication with the rotor such that axial rotation of the rotor causes axial rotation of the shaft; (c) at least one stator winding; (d) a plurality of switches, each functioning to provide commutation switching for the stator so as to generate a torque on the rotor and thereby cause said axial rotation of the shaft, wherein a terminal voltage of said machine is equal to the voltage of one electrochemical cell, and wherein the power of said machine is at least 1 kW.

Abstract: Techniques for component-based software engineering, and more particularly, to techniques for enhancing component based development systems by making components self-aware with respect to the applications that they may be consumed in or other peer components within the applications. An exemplary technique includes determining an addition of one or more components to an interface of an application; identifying an asset definition within metadata of a component of the one or more components added to the interface of the application, where the asset definition provides self-wiring or self-configuring instructions for an asset that needs to be created for the component within a predefined scope when the component is added to the interface; and creating the asset for the component based on the asset definition.

Abstract: A motorized vehicle assembly includes an axle comprising a channel extending along a central axis of the axle, a socket positioned within the channel of the axle, and a motorized wheel configured to be mounted on an end the axle. The motorized wheel includes a boss configured to engage the end of the axle when the motorized wheel is mounted on the axle, an electric motor, a tire mounted on the rotor, and a plug positioned within the boss, the plug configured to engage with the socket when the motorized wheel is mounted on the axle. The electric motor includes a stator fixed to the boss and a rotor surrounding the stator, the rotor configured to rotate relative to the stator. The electric motor is configured to cause the rotor to rotate relative to the stator to cause the tire to rotate.

Abstract: A powered skateboard having a powered wheel. The powered wheel formed of a motor within tire of the wheel. The powered wheel fixed to a truck of the powered skateboard. The powered skateboard including at least one onboard battery to provide electrical power to the powered wheel.

Abstract: Systems and methods are provided for managing and tracking process pipelines and other flows in a way that reduces the requirement for a central controlling process to manage every step of the associated pipeline flow and the state associated with each running instance. Job information and pipeline state are tracked by each worker involved in the pipeline. This enables some key capabilities within these process pipelines such as dynamic process re-writing and cross security domain job execution.

Abstract: Techniques are provided for encapsulating a user experience design for user interfaces of an application, where the user experience design comprises a look and feel of the application and a plurality of functional elements of the application. A plurality of rules for implementing the one or more user interfaces may be defined, and the rules may be based at least in part on the user experience design. Additionally, a pattern may be generated based at least in part on the plurality of rules. The pattern may be deployed to a distributed network of computing devices, and reused in the design of multiple other applications. The new user interfaces for those applications may be generated based at least in part on the pattern, where the additional applications comply with the look and feel and the plurality of functional elements of the other applications that share the pattern.

Abstract: Systems and methods are provided for managing and tracking process pipelines and other flows in a way that reduces the requirement for a central controlling process to manage every step of the associated pipeline flow and the state associated with each running instance. Job information and pipeline state are tracked by each worker involved in the pipeline. This enables some key capabilities within these process pipelines such as dynamic process re-writing and cross security domain job execution.