Mapping (I)
Allows clients to create a hierarchical collection of referential resources to a specific configuration
- doesn’t require the Configuration-Id header
Allows clients to create a hierarchical collection of referential resources to a resource’s version history
- doesn’t require the Configuration-Id or Version-Id header
- clients can navigate the version graph using PROPFIND on the mapped collection