Bill de hÓra wrote:
PaceServiceMayHaveWorkspaces
-1. Having at least one workspace gives clients and servers something
to agree on. A burden of proof is required here (imo). The argument that
forcing servers to expose a workspace will result in junk interop is not
made. The conceivable cases mentioned are not enumerated.
PaceServiceShouldHaveWorkspaces
As above.
The spec says that the "The content of [the introspection document] can
vary based on aspects of the client request, including, but not limited
to, authentication credentials." If at least one workspace and
collection is required, how then can the server signal that no
workspaces or collections are available for the calling user while
allowing the server to provide extension metadata that still might be
useful for the client (e.g. how to provision new
workspaces/collections)? Without this modification, the only way of
signaling that no collections are available for the authenticated user
would be to return a 204 No Content.
- James
