Hi. Le mardi 14 décembre 2010 à 10:00 -0500, Steve K Speicher a écrit :
> This would be useful, it just takes someone from WG to own/drive it. > In the meantime, I've added an item in [1] (CmSpecBacklog#Resource_history) > Some things to consider when defining this: > - audit trails/history definitions that include what action had been > invoked > - how much detail needs to be exposed on what properties were modified? > - is this queryable? > I've added these to the backlog too. > We do have on our backlog [1] various properties like this and they came > out of the evaluation [2] we looking at common properties across many > different CM providers. I would recommend we start with some concrete > scenarios in CM, possibly creating a minimal definition for this and then > evaluating along the way how/when it should be a common resource > definition / property. > > [1] - http://open-services.net/bin/view/Main/CmSpecBacklog -- Olivier BERGER <[email protected]> http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingénieur Recherche - Dept INF Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)
