> > (peter wrote)
> >
> > 2. Need ability to edit metadata on website models –e.g. for sensible
> > defaults on time integration parameters and graphical
We need to be very careful to preserve a relationship between a
simulation and the data obtained from it. I see a problem occurring
where we ha
Hi Matt,
To repond to your points:
1) I think the current state in the simulation metadata specification is that
it is recommended best practice to specify a rdf ID for every simulation,
mainly driven by the example of being able to define graphs for that
simulation. Do you think we need to ma
Are the models/metadata/simulation-results in any sort of Version
Control System (Subversion comes to mind)?
By including VCS tags in the text of the model/metadata/simulation-
results, then whenever these files are read/printed, the version
number and date can be also displayed. With a versi
Bob Gustafson wrote:
> Are the models/metadata/simulation-results in any sort of Version
> Control System (Subversion comes to mind)?
>
Models are assigned a 'version' and a 'variant', and the model curation
workflow means that models are never changed or deleted, instead a copy
of the model
Nickerson, David Phillip wrote:
> Hi Matt,
>
> To repond to your points:
>
> 1) I think the current state in the simulation metadata specification is that
> it is recommended best practice to specify a rdf ID for every simulation,
> mainly driven by the example of being able to define graphs for
