#3 change log

[Allyson Lister]

When you make changes to the ontology, do you post a changelog to the sbo mailing list? It would be helpful to know exactly what's changed with each release.

Or, barring that, is there a timestamp associated with each class name that we could use to see a last updated date? Or, failing that, is there a timestamp in the OBO/OWL file with the last updated date of the entire ontology?

[Melanie Courtot]

Logged In: YES
user_id=1572691
Originator: NO

We are doing changes dynamically directly in the database and don't keep an history of modification.
Would an option be to provide an md5 checksum with the files (easily added via the shell script used to generate them) and you could then check if the md5 sum provided matches yours to know when to download a new version?

[Allyson Lister]

Logged In: YES
user_id=1562499
Originator: YES

An md5 checksum provided with the file would be a great idea. Thanks :)

[Nicolas Le Novère]

Logged In: YES
user_id=1045203
Originator: NO

Actually we do keep an unformal log of changes through comments. We will change that soon, recording every changes, together with timestamps.

[Allyson Lister]

Logged In: YES
user_id=1562499
Originator: YES

that sounds fantastic! thanks :)

[Camille Laibe]

Sorry for the last reply.
A timestamp is available in all the exports (OBO, OWL and XML) and a change log has been implemented (cf. "Recent changes" in the left menu of the online browser).