Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change <annotation> namespace #7

Open
cannin opened this issue Jun 30, 2020 · 3 comments
Open

Change <annotation> namespace #7

cannin opened this issue Jun 30, 2020 · 3 comments

Comments

@cannin
Copy link

cannin commented Jun 30, 2020

@amazein @ibalaur What was the reasoning for having the annotation xmlns as libsbgn? Is this how SBML and others do it?

 <extension>
  <annotation xmlns="" xmlns:ns2="http://sbgn.org/libsbgn/0.2">
    <rdf:RDF ... >
@cannin cannin changed the title Change annotation namespace Change <annotation> namespace Jun 30, 2020
@draeger
Copy link

draeger commented Jul 1, 2020

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?

@cannin
Copy link
Author

cannin commented Jul 1, 2020

@draeger What would SBML do in this scenario? Especially since the annotation tag is meant to be borrowed from SBML.

@draeger
Copy link

draeger commented Aug 5, 2020

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".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants