Page History

...

For feed 2, we want to allow for the repository to contain multiple image collections, much in the same spirit as extending the functionality of the demo image collection.  Each image collection is represented by its own object in the repository, as are individual image items.  Collection membership is determined by the presence of an 'isMemberOf' relationship from an image to a collection.  Specifically, let's suppose that we wanted the following characteristics:

1. We want to extend the functionality provided by the demo image collection by allowing these collections to be modified using the atom publishing protocol.
   1. Existing demo SDefs and SDeps from the image collection remain unchanged
   2. Images added/modified via AtomPub are considered FULL_SIZE
2. There exists a ServiceDocument that enumerates all the image collections in the repository and their collection feed URIs (as provided by the APP)
3. Each image collection has a collection feed URI
4. In accordance with the APP images may be added, removed, or replaced through through this feed
   1. Adding an object to the feed implies adding a new object to the repository - but the client shall have no awareness of this process
   2. Deleting an object from the feed implies purging the image object from the repository - but the client shall have no awareness of this process

...