Re: [Obo-discuss] data-version tag in obo-format sourced ontologies

[Erick A. <eri...@gm...>]

is that "friendly" release name captured in OBI itself?

Erick

On 22 February 2011 07:52, Alan Ruttenberg <ala...@gm...> wrote:
> OBI also uses a "friendly" release name in addition to the version.
> For example we've named major releases after cities we've met in.
>
> Do others use similar practices? Is it worth having a convention for
> such names and ask
> Bioportal to pick it up too?
>
> -Alan
>
> On Monday, February 21, 2011, Chris Mungall <cjm...@lb...> wrote:
>> Note that there have been a number of fragmented discussions of this issue on and off various lists, please consider consolidating them here. This email is primarily aimed at those of you creating and maintaining ontologies.
>>
>> The data-version tag (which correspondings to VersionIRI in OWL) is the recommended way of publishing a stable version number in OBO-Format sourced ontologies.
>>
>> Note that obo-edit will not attempt to generate this for you - this isn't a good idea in an asynchronous editing environment. We also don't recommend you use any kind of cvs/svn auto-generated tag (e.g. $Version$), as this introduced a dependency on the repository and repository location.
>>
>> The recommended way to do this is to implement the following two steps:
>>
>>          (1) arrange things such that there is a distinct editors version and release version of the ontology
>>          (2) add the data-version tag on release.
>>
>> Note that (1) is a good idea regardless of the data-version tag. Most ontology producers implement this already. We can help in cases where this isn't implemented.
>>
>> For (2) there are a number of different options. The recommendation is to do this automatically rather than manually. There is no prescribed release frequency, daily works well (this doesn't preclude also having additional landmark releases). For version naming recommendations, see:
>>
>>         http://www.obofoundry.org/id-policy.shtml
>>
>> i.e. ISO-8601 dates (YYYY-MM-DD).
>>
>> Note that GO data-version tags precede this policy, but may change to it in future.
>>
>> Some groups implement their own pipeline here (GO, OBI). There's no point re-implementing the wheel here. GO will soon be using a generic ontology release manager that will in addition take care of producing derived files (obo/owl, subsets, MIREOTed ontologies, etc) - if you want to implement data-version today, I'll make available a minimal release script that should be easy for anyone to run. All this will do will be auto-populate a data-version tag based on the current date. Contact me or obo...@ob... for details.
>>
>> Cheers
>> Chris
>>
>>
>> ------------------------------------------------------------------------------
>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
>> Pinpoint memory and threading errors before they happen.
>> Find and fix more than 250 security defects in the development cycle.
>> Locate bottlenecks in serial and parallel code that limit performance.
>> http://p.sf.net/sfu/intel-dev2devfeb
>> _______________________________________________
>> Obo-discuss mailing list
>> Obo...@li...
>> https://lists.sourceforge.net/lists/listinfo/obo-discuss
>>
>
> ------------------------------------------------------------------------------
> Index, Search & Analyze Logs and other IT data in Real-Time with Splunk
> Collect, index and harness all the fast moving IT data generated by your
> applications, servers and devices whether physical, virtual or in the cloud.
> Deliver compliance at lower cost and gain new business insights.
> Free Software Download: http://p.sf.net/sfu/splunk-dev2dev
> _______________________________________________
> Obo-discuss mailing list
> Obo...@li...
> https://lists.sourceforge.net/lists/listinfo/obo-discuss
>