Abstract: Digital image generation through use of capture support data is described. In one example, an image capture device is configured to obtain capture support data from an imaging support system via a network through inclusion of a pre-capture system. The pre-capture system, for instance, is configured to obtain capture support data from an imaging support system via a network. The capture support data is configured for use by digital image processor along with raw image data received from an image sensor to generate a digital image, e.g., that is configured for rendering.

Abstract: Techniques and systems for digital image generation and capture hint data are described. In one example, a request is formed by an image capture device for capture hint data. The request describes a characteristic of an image scene that is to be a subject of a digital image. A communication is received via a network by the image capture device in response to the request. The communication includes capture hint data that is based at least in part of the characteristic. The capture hint data is displayed by a display device of the image capture device. The digital image of the image scene is then captured by the image capture device subsequent to the display of the capture hint data.

Abstract: Digital image generation through use of capture support data is described. In one example, an image capture device is configured to obtain capture support data from an imaging support system via a network through inclusion of a pre-capture system. The pre-capture system, for instance, is configured to obtain capture support data from an imaging support system via a network. The capture support data is configured for use by digital image processor along with raw image data received from an image sensor to generate a digital image, e.g., that is configured for rendering.

Abstract: Techniques and systems for digital image generation and capture hint data are described. In one example, a request is formed by an image capture device for capture hint data. The request describes a characteristic of an image scene that is to be a subject of a digital image. A communication is received via a network by the image capture device in response to the request. The communication includes capture hint data that is based at least in part of the characteristic. The capture hint data is displayed by a display device of the image capture device. The digital image of the image scene is then captured by the image capture device subsequent to the display of the capture hint data.

Abstract: A user interface for building a componentized workflow model. Each step of the workflow is modeled as an activity that has metadata to describe design time aspects, compile time aspects, and runtime aspects of the workflow step. A user selects and arranges the activities to create the workflow via the user interface. The metadata associated with each of the activities in the workflow is collected to create a persistent representation of the workflow. Users extend the workflow model by authoring custom activities.

Abstract: Designing and executing a workflow having flow-based and constraint-based regions. A user selects one or more activities to be part of a constraint-based region. Each constraint-based region has a constraint associated therewith. The workflow is executed by executing the flow-based region and the constraint-based region. The flow-based region executes sequentially. The constraint is evaluated, and the constraint-based region executes responsive to the evaluated constraint.

Abstract: Designing and executing a workflow having flow-based and constraint-based regions. A user selects one or more activities to be part of a constraint-based region. Each constraint-based region has a constraint associated therewith. The workflow is executed by executing the flow-based region and the constraint-based region. The flow-based region executes sequentially. The constraint is evaluated, and the constraint-based region executes responsive to the evaluated constraint.

Abstract: A user interface for building a componentized workflow model. Each step of the workflow is modeled as an activity that has metadata to describe design time aspects, compile time aspects, and runtime aspects of the workflow step. A user selects and arranges the activities to create the workflow via the user interface. The metadata associated with each of the activities in the workflow is collected to create a persistent representation of the workflow. Users extend the workflow model by authoring custom activities.

Abstract: Designing and executing a workflow having flow-based and constraint-based regions. A user selects one or more activities to be part of a constraint-based region. Each constraint-based region has a constraint associated therewith. The workflow is executed by executing the flow-based region and the constraint-based region. The flow-based region executes sequentially. The constraint is evaluated, and the constraint-based region executes responsive to the evaluated constraint.

Abstract: Designing and executing a workflow having flow-based and constraint-based regions. A user selects one or more activities to be part of a constraint-based region. Each constraint-based region has a constraint associated therewith. The workflow is executed by executing the flow-based region and the constraint-based region. The flow-based region executes sequentially. The constraint is evaluated, and the constraint-based region executes responsive to the evaluated constraint.

Abstract: A method for distributed inventory management includes receiving information regarding a number of participants in a value chain and information regarding one or more items relevant in the value chain. The method also includes modeling relationships between two or more of the participants based on the received information and modeling the one or more items based on the received information. Furthermore, the method includes receiving inventory data from the participants relating to the one or more items, processing the inventory data based on the models of the relationships and the items to generate inventory information related to one or more of the participants, and communicating the generated inventory information to one or more of the participants. The inventory information at least partially includes information regarding inventory data of participants other than those participants to which the inventory information is communicated.

Abstract: Building a componentized workflow model via an application programming interface. Each step of the workflow is modeled as an activity that has metadata to describe design time aspects, compile time aspects, and runtime aspects of the workflow step. A user selects and arranges the activities to create the workflow via the application programming interfaces. The metadata associated with each of the activities in the workflow is collected to create a persistent representation of the workflow. Users extend the workflow model by authoring custom activities. Users also compile the workflow via the application programming interface.

Abstract: Building a componentized workflow model. Each step of the workflow is modeled as an activity that has metadata to describe design time aspects, compile time aspects, and runtime aspects of the workflow step. A user selects and arranges the activities to create the workflow via user interfaces or application programming interfaces. The metadata associated with each of the activities in the workflow is collected to create a persistent representation of the workflow. Users extend the workflow model by authoring custom activities. The workflow may be compiled and executed.