Menu

#293 wrong namespace used for the protein modification ontology

closed
5
2022-07-13
2015-10-07
No

Apply to SBML Level 2 Version 5 release 1 and SBML Level 3 Version 2 draft (August 2014)

In page 105 of the L2V5 specs, there is an error in one of the example of nested annotations. Identifiers.org url should be used and more importantly the namespace used for the protein modification ontology is wrong (it is not 'obo.mod' but 'psimod').

Here is the xml in the specs:

<species id="user-content-S1" metaid="_000004" compartment="cell" hasonlysubstanceunits="false" boundarycondition="false" constant="false">
<annotation>
<rdf:rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:bqbiol="http://biomodels.net/biology-qualifiers/">
<rdf:description rdf:about="#_000004">
<bqbiol:isversionof>
<rdf:bag>
<rdf:li rdf:resource="urn:miriam:uniprot:P04551">
<bqbiol:isversionof>
<rdf:bag>
<rdf:li rdf:resource="urn:miriam:obo.mod:MOD%3A00047">
</rdf:li></rdf:bag>
</bqbiol:isversionof>
</rdf:li></rdf:bag>
</bqbiol:isversionof>
</rdf:description>
</rdf:rdf>
</annotation>
</species>

It should be changed to:

<species id="user-content-S1" metaid="_000004" compartment="cell" hasonlysubstanceunits="false" boundarycondition="false" constant="false">
<annotation>
<rdf:rdf xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:bqbiol="http://biomodels.net/biology-qualifiers/">
<rdf:description rdf:about="#_000004">
<bqbiol:isversionof>
<rdf:bag>
<rdf:li rdf:resource="http://identifiers.org/uniprot/P04551">
<bqbiol:isversionof>
<rdf:bag>
<rdf:li rdf:resource="http://identifiers.org/psimod/MOD:00047">
</rdf:li></rdf:bag>
</bqbiol:isversionof>
</rdf:li></rdf:bag>
</bqbiol:isversionof>
</rdf:description>
</rdf:rdf>
</annotation>
</species>

The same problem happen in the L3V2 draft, on page 108-109

Thanks

Discussion

  • Lucian Smith

    Lucian Smith - 2016-01-05
    • labels: --> Level 3 Version 1 Core
    • status: open --> pending
    • assigned_to: Lucian Smith
    • Group: Reported-Proposed --> Accept-formatting-and-typos
     
  • Lucian Smith

    Lucian Smith - 2016-01-05

    Thanks! This is now fixed in SVN for L3v2, and will be incorporated into the forthcoming specification.

    I'm not sure what the best thing to do for L2v5 is. Would it be possible to make this change, and incorporate it into a new release of the spec, instead of a whole new version?

     
  • Michael Hucka

    Michael Hucka - 2016-01-06

    Yes, I believe it would be acceptable to issue a new release of the specification. The SBML Development Process says this about releases, and making a new release for this issue is perfectly in line with this principle:

    "After a period of time, an accumulation of issues may warrant the development of a new release of Version 4, ..."

    (and yes, it needs to be updated to talk about version 5.)

     
  • Lucian Smith

    Lucian Smith - 2017-12-06
    • labels: Level 3 Version 1 Core --> Level 2 Version 5 Core
    • status: pending --> accepted
     
  • Lucian Smith

    Lucian Smith - 2017-12-06

    With the release of L3v2, this issue is fixed there. However, it remains in l2v5, so I added a tag for that specification instead, so we can add it to the list of errata there, possibly for a later release of that spec.

     
  • Lucian Smith

    Lucian Smith - 2018-12-04

    This is now fixed in the SVN for L2v5 as well; whenever we do a new release of that, those changes will go in.

     
  • Matthias König

    Matthias König - 2018-12-05

    Please update the identifiers urls to the https versions. Unsecure connections should be avoided whenever possible (and could also become unavailable at some point, e.g., as happened when EBI moved completely to https).

    Otherwise agree with the change.

     
  • Sarah Keating

    Sarah Keating - 2018-12-05

    I agree with Matthias - change to https and then okay

     
  • Claudine CHAOUIYA

    I agree with this change

     
  • Lucian Smith

    Lucian Smith - 2018-12-05

    There are a lot of 'http://' lines in the SBML spec, and I'm not sure how many can and/or should be changed to 'https://'. Can we get away with changing all of them except the namespace URLs?

     
  • Fengkai Zhang

    Fengkai Zhang - 2018-12-05

    I agree with the change. Regarding http://identifiers.org or https://identifiers.org in namespace urls, I would not consider it is a major issue at least for now. Both ways would be ok. The identifiers.org website now redirects http to https and this redirection service should be a feature maintained by identifier.org for a long term.

     
  • Lucian Smith

    Lucian Smith - 2018-12-05

    OK, went through all the URLs in the spec and updated them to use https if possible. This was, notably, not possible with sbml.org and biomodels.net and a few others; identifiers.org was one of the few ones where https actually worked. However, that was for l3 and l2; adding a new issue for that.

     
  • Lucian Smith

    Lucian Smith - 2018-12-05
    • status: accepted --> pending
     
  • Lucian Smith

    Lucian Smith - 2022-07-13
    • status: pending --> closed
     

Log in to post a comment.

MongoDB Logo MongoDB