Two possible versions of an inventory file are shown. The first (inventory1.jsonld) contains all information in the 'Version' object. "members" within the version provide an inventory of the member files for that version, while "state" provides the full state of the object at that version.
inventory2.jsonld is the original proposal. "members" in the Version object track all the members of the object (analagous to "state" in the previous proposal. In this example they are addressed by digest, but they could also be addressed by filepath.
Considerations:
- How do we represent the "state" of the object at a given version?
- If a user requests "version 4", what do they get back? A list of filepaths?
- What happens if a user requests two files in the same path with the same name, with only the root being different? (e.g., v1/foo.txt, v2/foo.txt) Can 'object-relative' filepaths be duplicates, even though their storage filepaths are different?
Nice properties of the above:
additions
, noincludes
for a full copy)v#
dir ==additions
, just run through these to check contentadditions
andincludes