You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is, to my understanding, somewhat problematic to couple the namespace to a specific version of one specific implementing library. Didn't we agree to move away from this practice?
Generally, the namespace is just some unique identifier. Hence, the library version is not strictly illegal and should work in principle. However, it can cause trouble if a new version of the library writes files with a namespace that refers to some older library. In SBML there would be a namespace declaration consisting of the Level and Version of the corresponding SBML specification. So, SBGNML could also use such a schema, for instance, "http://sbgn.org/sbgnml/0.3".
@amazein @ibalaur What was the reasoning for having the annotation xmlns as libsbgn? Is this how SBML and others do it?
The text was updated successfully, but these errors were encountered: