Peter Kovalik
Well-known member
Do you happen to know what is "Chaves et al. (2013)" ?
Daniel, I think Van has accidentally inherited that text from Proposal #593.
:t: Daniel, Richard good catch. Fixed now.
Do you happen to know what is "Chaves et al. (2013)" ?
Daniel, I think Van has accidentally inherited that text from Proposal #593.
:t: Daniel, Richard good catch. Fixed now.
... and barring additional tweaks, removes previous misconceptions on relationships in the genus
The result of adopting a generic approach to proposal writing?Hmm ! this part is still there Peter :
The result of adopting a generic approach to proposal writing?
Nov 1 Post proposed splits of Black-fronted Fig Parrot and Dusky-cheeked Fig Parrot from Orange-breasted Fig Parrot
IOC World Bird List: Nov 3 Decline Fig Parrot splits: await full study.IOC diary
Nov 1 Post proposed splits of Black-fronted Fig Parrot and Dusky-cheeked Fig Parrot from Orange-breasted Fig Parrot
IOC World Bird ListS. Next version will evidently be v4.
www.worldbirdnames.org/updates/update-diary/Don't see the point myself in changing from 3 to 4 unless something really major is going to happen (e.g. radical format change in the lists) otherwise stick with 3.x until a good reason
Nov 4: Future updates will be aligned to calendar year, e.g. v4.1 – 4.4 (2014)
Nov 4: Future updates will be aligned to calendar year, e.g. v4.1 – 4.4 (2014)
It's outstanding value – it's free!So zero value whatsoever
The proposed alignment of version number to calendar year has value for bibliographic purposes and especially doi registration, I am told. To your point, our thought also is to schedule major annual revisions - of higher classification, for example - for the Jan update. Comments most welcome.
Thanks also for spotting the consistency problem of 4.0 vs 4.1. V4.0 will be reserved for the "database" element of the doi registration. v4.1-4.5 will refer to "data sets" of that database. I'm on a steep tech learning curve here, so expect this all to evolve in the months ahead.
The proposed alignment of version number to calendar year has value for bibliographic purposes and especially doi registration, I am told. To your point, our thought also is to schedule major annual revisions - of higher classification, for example - for the Jan update. Comments most welcome.
Thanks also for spotting the consistency problem of 4.0 vs 4.1. V4.0 will be reserved for the "database" element of the doi registration. v4.1-4.5 will refer to "data sets" of that database. I'm on a steep tech learning curve here, so expect this all to evolve in the months ahead.
The proposed alignment of version number to calendar year has value for bibliographic purposes and especially doi registration, I am told. To your point, our thought also is to schedule major annual revisions - of higher classification, for example - for the Jan update. Comments most welcome.
Thanks also for spotting the consistency problem of 4.0 vs 4.1. V4.0 will be reserved for the "database" element of the doi registration. v4.1-4.5 will refer to "data sets" of that database. I'm on a steep tech learning curve here, so expect this all to evolve in the months ahead.