-
Notifications
You must be signed in to change notification settings - Fork 0
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
Convene an Identifiers Task Group #14
Comments
Everyone present on the Tuesday 2017-Oct-03 meeting of the TAG at TDWG 2017 expressed interest in participating in this task group: Paul Morris, Dimitris Koureas, Jonathan Rees, Dag Endresen, Joel Sachs, Pier Buttigieg, Jeff Gerbracht, Steve Baskauf, Stan Blum. |
@dkoureas has agreed to be the convener of this task group, starting January 2018. |
I'm also interested in participating in this task group. The GUID AS is not easily found on the portal. The http://www.tdwg.org/standards/150 link is now https://www.tdwg.org/standards/guid-as/ but the PDF link from there is broken. |
Cool. Keep me posted. If there is/was a TAG and/or identifiers meetup at TDWG kindly post the minutes somewhere. Sorry I couldn't make it. |
Thanks all,
Will invite people who already expressed their interest to join the group
as of January 2019. In the meantime will work with Paul to draft the new
charter of the TG.
Kind regards,
Dimitris
*--*
*Dr Dimitris Koureas, FLS*
*Programme Director - Department Head*
International Biodiversity Infrastructures
Naturalis Biodiversity Center, P.O. Box 9517, 2300 RA Leiden, NL
Coordinator, Distributed System of Scientific Collections (DiSSCo
<http://dissco.eu/>)
Chair, Biodiversity Information Standards Organisation (TDWG
<http://tdwg.org/>)
Research Data Alliance (RDA <http://www.rd-alliance.org/>) - Technical
Advisory Board member
*ORCID*: 0000-0002-4842-6487 | *Linkedin*: linkedin.com/in/dkoureas
*Twitter*: @DimitrisKoureas | *Tel*: +31 (0) 71 751 9251
…On Thu, 30 Aug 2018 at 15:59, Jonathan A Rees ***@***.***> wrote:
Cool. Keep me posted. If there is/was a TAG and/or identifiers meetup at
TDWG kindly post the minutes somewhere. Sorry I couldn't make it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#14 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ALmnQOPpCwoBYB3kYDVFTYaGD1tOD1ldks5uV---gaJpZM4PvDep>
.
|
The link to the GUID AS is https://github.com/tdwg/guid-as/blob/master/guid/tdwg_guid_applicability_statement.pdf . I've submitted a pull request to fix it on the website. |
This effort has been idle, as far as I can tell, for quite a while. What does one do in order to join and participate in the group? Is there any charter or work plan? |
Hi @jar398 I'm wondering what @stanblum might have to say here. See for example, this ticket tdwg/cd#40 regarding the need for PID system for collections. (We need help in this group to take on that particular issue, and could use your expertise as well as that of others originally interested. This group would also be able to contribute to the work of the Alliance for Bio .... and others |
Thoughts following on to today's TAG meeting where @baskaufs wanted to know if this issue could be closed: I've just done a quick review of the TDWG web site and the 2010 GUID applicability statement and I don't see what the issue is. Up until 2016 there was a statement on the web site saying LSIDs were preferred, and I had complained about it a few times, but that was gone by 2017. Everything seems consistent and acceptable now: the GUID applicability statement looks OK, and the recommendation is to use of one of the systems on the R1 list, which includes both HTTP and LSID. So I'm inclined to say close. A few people on the TAG call today said they thought LSIDs should be deprecated, but this was not unanimous. Maybe the TG's purpose would just be to discuss this and decide whether such an action is warranted? I have some thoughts (resisting putting them in this issue since they're not on topic). If this is the only open question maybe we could deal with it in a new github issue instead of creating a TG? @debpaul The question of identifier strategies for particular efforts or domains should probably be addressed by those particular efforts or domains (such as CD), yes? When we speak of 'identifiers' we do not usually intend to include the design of completely general metadata formats. The question of persistence often comes up in this context but it never has a technical solution because it is not a technical problem. Someone thought something needed to be done or this issue wouldn't exist. I was at these meetings but don't remember and unfortunately don't have notes. To make sure I haven't missed anything I must appeal to @dkoureas, @ghwhitbread, or anyone else who might remember. |
This issue is being closed with further discussion to take place at #36 |
An open call for nominations.
A task group to revise the GUID applicability statement
Nominations from:
@godfoder
@jgerbracht
...
The text was updated successfully, but these errors were encountered: