Skip to content

Lacking specification of rules of HTTP methods for Description Resource #673

Open
@renyuneyun

Description

@renyuneyun

Issue Content

I'm finding some use cases for the Description Resource (DR), but found that the way how they can be manipulated is not made clear in the spec. In particular, the following questions are unanswered (assuming permission is met):

  1. (Prerequisite of the rest) Is the user allowed to modify the DR?
  2. What HTTP requests are supported for a DR?
    • I presume OPTIONS, GET, POST, PUT and PATCH are all supported in the same way as a normal resource when the DR exists?
  3. Can I send a DELETE request to the DR, and what would happen?
  4. If, for some reason, there is no DR for a resource yet (but server has capacity), how can I create a DR?
  5. Am I allowed to associate a different DR with the resource on a custom location?

Also, this sentence is not clear enough:

Servers MUST NOT directly associate more than one description resource to a subject resource.

Does this mean the server can indirectly associate more than one DR to a subject resource? If so, how?
Or, does this mean the user (rather than the server) can associate more than one DR?

Generalization

Actually, this question can be generalized to all Auxiliary Resources (AR): what ARs can be modified by the users, and are they subject to the same mechanism?

Related topics

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions