The Solid Protocol defines a document-oriented interface to access Linked Data subject to usage control policies that define who can read or write it. Common use cases with different read and write granularities cannot easily be supported with a one-to-one mapping from http  interface to a document-based storage system. We propose an interpretation of the Solid Protocol with Derived Data Resources, which are a server-side selection of data from different underlying resources. This demo covers our implementation in the Community Solid Server, detailing its more granular data control. Our implementation can guide other proposals, and the evolution of the specification to support the growing demand of Solid use cases with divergent read/write patterns.