Frank Bergmann

hello tobias, i'll have a look and add some test cases ...

for me it works with the additional line, so i've committed it. If you have a specific error, we should add it as test case, so we can ensure it...

thanks for letting me know, I have to say i was really surprised how hard it seems to be to get the namespace uri's in Java. I'll have a look...

added test code, and unified the way non-files are treated, i hope this resolves the issue.

Hello Yun, indeed the namespaces currently don't resolve anymore to an actual xsd file. But they don't necessarily have to. They are necessary, just for the xml parser to know...

We could change the API such that `checkConsistencyWithStrictUnits` gets an override flag, that will be passed on. That way callers can decide whether those unit issues are warnings / errors....

We always had options to turn on / off different validators. when I look at it it looks that `checkConsistencyWithStrictUnits` runs the same checks as checkConsistency, however it turns off...

Thinking about this a bit longer, I propose 2 changes: * add a new `LIBSBML_CAT_STRICT_UNITS_CONSISTENCY`, that can be used with the normal internal validator by running `SBMLDocument::setConsistencyChecks`. Then we can...

The tolerances are saved in the COPASI file, so basico and CopasiUI would use the same ones. To get a hold of the tolerances, there would be different ones: *...

I cant reproduce this here, and would need more information