1. Extensible metadata per asset version in order to reflect things like workflow as discussed here:[[BR]][http://mail-archives.apache.org/mod_mbox/lenya-dev/200312.mbox/%3c1072877417.4649.62.camel@gideon.rkunet.org%3e]

1. Extensible metadata per asset version in order to reflect things like workflow as discussed here:<<BR>>[[http://mail-archives.apache.org/mod_mbox/lenya-dev/200312.mbox/%3c1072877417.4649.62.camel@gideon.rkunet.org%3e]]

Moving of single assets and collections in the repository (without breaking contracts). The moving of assets could be implemented via metadata see 1.5.). This requirement serves as basis to implement staging of assets.

If access control is a concern of the Repository I propose it to be reflected in the rep. API, because otherwise Lenya has to deal with it. This is an important decision.

2.) MediumPriority

Locking of assets. This is essential for concurrent actions on assets.

Simple transactions

3.) LowPriority

Complex metadata queries

Observation - add listeners to specific events in the repository based on both the type of event and on the location in the repository.