On Mon, Jun 3, 2013 at 2:34 PM, Robert Munteanu <[email protected]> wrote: > ...I'm not sure how we would achieve a fine control over > serialisation. Is think something you would see as user-controllable?...
Maybe just a someNamespace:deepSerialize resource property would be sufficient? If it's set on a subtree, that subtree gets serialized as a single file, otherwise each resource is serialized in a single file. -Bertrand
