This page describes a potential set of questions to help evaluate use cases, present them in a clear and uniform way, and distill into requirements. The goal is to explore possible ways in which a common pattern for asynchronous interactions can be used to address each use case as concretely as possible, but falling short of providing a true specification or extension design.
Would this asynchronous interaction expose any new resources, or involve existing ones (e.g. URI of a fedora resource, as defined via the Fedora HTTP API)? How do asynchronous and non-asynchronous aware clients interact with the resource?
Under what conditions should an asynchronous interaction be invoked? The current understanding of 'invoke' means "direct an HTTP request for a resource." If this particular use case uses 'invoke' in a different way, please define.
Examples of preconditions include:
Are there any deployment or implementation-related details that may be relevant?
Examples include:
What requirements may this use case place on the repository container, the core Fedora API, or the API extension architecture?
What do you see as a potential value proposition of this use case in a common pattern for asynchronous interactions?
Examples include: