Use case: Identifier resolution requires chaining of several services that often operate independently, and are often opaque to users (especially web browser clients that do not have visibility of redirects). Since a resolver has knowledge of downstream targets, it is in a good position to perform some basic evaluation of target availability.
Requires:
- Simple mechanism for testing a target availability (e.g.
PidDefinition entries should include a test case)
- Background process for running tests in a non-invasive manner
- Document structure for test result collation
- Mechanism for sharing test results
- Mechanism for pushing notification of issues
See also #35
Use case: Identifier resolution requires chaining of several services that often operate independently, and are often opaque to users (especially web browser clients that do not have visibility of redirects). Since a resolver has knowledge of downstream targets, it is in a good position to perform some basic evaluation of target availability.
Requires:
PidDefinitionentries should include a test case)See also #35