ACTION-232

Hi all,

As per my Action-232, I reviewed the Use Cases document to check that
excluding setter operations would not arm one of our UC too much.

It seems to me that we can safely exclude setters for the first version
of our specifications. They are identified as requirement r02, which has
been appears only in two UC:

- curltural heritage
- user generated metadata

and even in those use cases, it is never emphasized that the *setting*
of metadata should be done through a generic API, independant from the
underlying format.

  pa