Forums

Hi,

As you might guess, I can only second Franks Opinion.

Option 2 would create a whole lot of work if a user decided to export an
L2V4 model he/she loaded to e.g. L1V2 because we would have to write
code that makes sure that the source model as well as the target model
are valid and this is not trivial for all models.

I like the behavior as it has been so far which is option 1). libSBML
should raise warnings and errors, but it should still allow the conversion.

It is just a fact that SBML allows users to encode invalid models and
there are quite a few of those out there, especially when it comes to
units and we would very much like to be able to handle those invalid
models in the future as well.

Ralph


Frank Bergmann wrote:
> Hello all ...
>
>
>
>> There are three options:
>>
>> 1) allow conversion regardless of the validity of either the source or
>> the target
>>
>> 2) disallow conversion from a valid model to an invalid model but
>> allow
>> conversion of valid to valid and invalid to invalid models
>>
>> 3) only allow conversions of a valid model that will produce a valid
>> model
>>
>> QUESTION: Which option seems preferable ?
>>
>
> I have gone to record about this before. So let me do it again, I
> prefer to be able to convert between ALL levels and versions (and yes
> that if it does not cause too much trouble even a conversion to 1.1
> could be attempted). Translating this view into a number, this would
> mean that I'd have to go with 1). Of course we don't like invalid
> models and so all violations should be logged to the ListOfErrors to
> be fixed later.
>
>
>> Pre-empting the replies I know I will get (for all you "I don't care
>> about units" people) there is of course the next question:
>>
>> QUESTION: if we go with option 3 should it be possible to ignore
>> certain
>> validation checks when determining the validity of the models ?
>>
>>
>
> If indeed we go with option 3, then ... as you might have guessed from
> my answer above ... yes please allow me to ignore some of the checks.
>
> best
> Frank
>
>
>> Thanks
>>
>> Sarah, Akiya & Mike
>>
>> ____________________________________________________________
>> To manage your libsbml-development list subscription, visit
>> https://utils.its.caltech.edu/mailman/listinfo/libsbml-development
>>
>> For a web interface to the libsbml-development mailing list, visit
>> http://sbml.org/Forums/
>>
>> For questions or feedback about the libsbml-development list,
>> contact sbml-team@caltech.edu
>>
>>
>
> ____________________________________________________________
> To manage your libsbml-development list subscription, visit
> https://utils.its.caltech.edu/mailman/listinfo/libsbml-development
>
> For a web interface to the libsbml-development mailing list, visit
> http://sbml.org/Forums/
>
> For questions or feedback about the libsbml-development list,
> contact sbml-team@caltech.edu
>
>
>

____________________________________________________________
To manage your libsbml-development list subscription, visit
https://utils.its.caltech.edu/mailman/listinfo/libsbml-development

For a web interface to the libsbml-development mailing list, visit
http://sbml.org/Forums/

For questions or feedback about the libsbml-development list,
contact sbml-team@caltech.edu