...

1. Status
   colour Blue title Phase 2

    Single resource bags
   

2. Status
   colour Blue title Phase 2

    The structure and scope of accepted and produced BagIt bags must be configurable (resource)
   1. Clarification: structure relates to required and optional tagfiles in the bag
   2. Clarification: scope relates to contents of the bag, e.g. single object or object and all members based on specific membership predicate

3. Status
   subtle true colour Blue title Phase 3

   Multi-resource bags

4. Status
   subtle true colour Blue title Phase 3

   Unambiguously support linking between resources within a bag, and from resources in the bag to resources outside the bag
   1. e.g. for bagged resources A and B, if A contains statement <A> myns:rel <B>, then it is unambiguous that B is a resource in the bag.  Suppose some archive ingests the bag and exposes its contents as web resources with URIs P and Q. If the archive preserves intra-bag links, resource P will have statement <P> myns:rel <Q>.  Likewise, if A contains external link <A> myns:rel2 <http://example.org/outside/the/bag>, then an archive that preserves links will have <P> myns:rel2 <http://example.org/outside/the/bag>

Verification Tool

1. Status
   colour Blue title Phase 2

   Verify same number of resources on disk as in fcrepo

2. Status
   colour Blue title Phase 2

   Verify same number of resources in fcrepo as on disk

3. Status
   colour Blue title Phase 2

   Verify same checksum for binaries

4. Status
   colour Blue title Phase 2

   Verify same triples for containers

5. Status
   colour Blue title Phase 2

   Record which resources have been verified

6. Status
   colour Blue title Phase 2

   Verify fcrepo to fcrepo

7. Status
   colour Blue title Phase 2

   Verify disk to disk

8. Status
   colour Blue title Phase 2

   Use generated config file as sole input StatuscolourBluetitlePhase 2

Considerations

• Import/export performance as is possible under the assumption that this work is done via the REST interface

...