from emails between GL and CG:

Ciao Gerard,
sorry for the late reply... (overwhelmed... as usual... :o)
I try to give some quick answer... tomorrow we'll have more time for discussion...




1. DataCollection has 1 Experiment. 
Is it possible for there to be multiple DataCollection-s with the same Experiment?
If not DataCollection and Experiment together can correspond to
SimDB:/simdb/experiment/Experiment.
DataCollection, with its collections of Data and Tools could maybe be a
SimDB:/simdb/Project, apart from the restriction
on having only 1 Experiment 
Are the Data of a DataCollection those produced by the experiment?

Answer:
Datacollection is my "data object", and I would say that corresponds to SimDB
Experiment. There can be only one Datacollection, but multiple Data inside it. The
Experiment you see in my schema is just a list of general properties of the
DataCollection... It may be at the same level of e.g. UUID, but we wanted to keep it
inside the Source section. No relation between my:Experiment and SimDB:Experiment...


2. How should we interpret the collection of Tools.
Here an Experiment can be joined to multiple Tools through the common
DataCollectionTools. 
In SimDB and Experiment corresponds to 1 Protocol, the actual executable.
A Project can have multiple protocols and corresponding experiments .
We used to have a CompositeProtocol, but no firm use cases were ever proposed that
could not be (better) interpreted 
using a Project. Do you have one here?

Answer:
Not sure of what Project is... Let's discuss tomorrow :o)
 
3.
Some explicit SimDB features missing from IRA, though they may end up in the Info
string.
- a full description of the protocol. In IRA model Tools can not be reused, has to
be redefined. 
- indication of the properties that are being calculated in the experiment and are
available in the Product.
- target: the goal of the experiment
- what physics is used in the experiment

Answer:
In fact at the moment we didn't go to that level of details. For the moment we were
happy with putting all that info in the INFO textual section. Of course this poses
strong limitations, expecially for the description of the properties. We are working
to overcome/improve/extend it... Since at the moment we had only a download service,
it was sufficient. Now we are working to add visualization, and so further info is
definitely needed!!!

See you tomorrow for (many) more details