Page History

...

1. Status
   colour Blue title Phase 1

   Support transacting in RDF
   

2. Status
   colour Blue title Phase 1

   Support allowing the option to include Binaries

3. Status
   colour Blue title Phase 1

   Support references from exported resources to other exported resources

4. Status
   colour Blue title Phase 2

   Support transacting in BagIt bags

5. Status
   colour Blue title Phase 1

   Support import into a non-existing Fedora container

6. Status
   colour Blue title Phase 32

   Support import into an existing, empty Fedora container

7. Status
   colour Blue title Phase 3

   Support import into an existing, non-empty Fedora container with various policies: add, overwrite, delete, version, skip

8. Status
   colour Blue title Phase 3

   Support export of resource versions

9. Status
   colour Blue title Phase 3

   Support import of resource versions

10. Status
    colour Blue title Phase 1

    Support export of resource and its "members" based on the ldp:contains predicate

11. Status
    colour Blue title Phase 32

    Support  Support export of resource and its "members" based on a user-provided membership predicate
12. Support recursive RDF insert/updates with LDP Indirect Container specified POST (and PUT / PATCH?) (ref: FCREPO-2042)

...

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
   colour Blue title Phase 3

   Multi-resource bags

4. Status
   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>

...