shapetrees / specification

Specification for Shape Trees
https://shapetrees.org
Other
13 stars 5 forks source link

Is Shape Tree matching based on URI Template necessary? #26

Closed joshdcollins closed 3 years ago

joshdcollins commented 3 years ago

Given the inclusion of the shape tree hint (Link header with relation http://shapetrees.org/#TargetShapeTree) request header which allows clients to explicitly specify the intended shape tree being matched, is the URI Template scheme necessary?

Are there valid use cases where this is preferred or necessary?

joshdcollins commented 3 years ago

An argument I'm finding in favor of removing the URI template matching is a shape tree implementation's interaction with an ecosystem.

I'm working off the assumption that no server would/should make ecosystem calls from the server -- meaning they would need to executed within a client. If the shapetree selection isn't explicit, it would require some context from the server to know which ShapeTree was used for validation (likely by means of response Link header?).

joshdcollins commented 3 years ago

Based on live conversations with @justinwb and @ericprud it was decided to remove the URI Template matching. Use cases were identified that would lead to data inconsistencies if two clients interacted with the same data using two different approaches (shape tree hint vs. name matching).

Reassigning this ticket to myself to update spec to remove it.