You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder what the impact would be if we would have a content-type profile for TREE, in which the member extraction algorithm would go much faster. We should experiment with https://github.com/pietercolpaert/TREE-profiles and compare the performance to see whether this is indeed worth the while.
The text was updated successfully, but these errors were encountered:
We will add this in the spec and a PR can be opened. However: 1) only an efficiency gain and a promise by a server, not a semantic decision. 2) We should also allow hypermedia at the bottom as well instead of only at the top. Maybe through the tree:view triple.
I wonder what the impact would be if we would have a content-type profile for TREE, in which the member extraction algorithm would go much faster. We should experiment with https://github.com/pietercolpaert/TREE-profiles and compare the performance to see whether this is indeed worth the while.
The text was updated successfully, but these errors were encountered: