Thanks for a complete list of requirements! I have included some comments into the document using track-changes.
#4 Resolvability: A plain web page with information about the entity is a useful minimum requirement. However, we might perhaps want to mention already in #4 that an additional machine readable service is preferred?
#9 Compatibility: Naming accession numbers simply as "identifiers" could contribute to missunderstandings. An accession number is not a PUID! There are proposals to build the PUID strings to include the accession number/catalogue number. I think such a strategy should be advised against. I suggest to rather name the accession numbers as "non-unique and local identifiers" to avoid potential missunderstandings.
#10 Multiple resolution: I am not sure I fully understand this requirement. A minimum and good-enough requirement for the resolver could be to simply provide some information about the entity. Providing links to other destinations with information about
the entity is absolutely useful, but I suggest to rephrase from the mandatory "must" to an optional "can".
W1 -Task Force on Permanent Unique Identifiers: Requirements
Welcome to week 1 of the electronic consultation on the Permanent Unique Identifiers (PUID) in the context of the Global Information System of the International Treaty on Plant Genetic Resources for Food and Agriculture (GLIS).
This first round of the consultation will focus on the definition of the requirements that we think a suitable PUID type should satisfy to meet our needs.
We attach a table with an initial list of requirements and, more in general, points to be considered in week 2 when we will evaluate the three candidate PUID types: ARK, DOI and LSID.
During the discussion, please take into consideration the following issues:
- Our initial focus will be PGRFA Accessions. The PUID requirements should therefore be primarily dictated by this context. However, we could expect GLIS to grow and expand to other classes of entities such as gene sequences, traits, people, institutions, technologies etc. It would be good to keep this growth in mind during the discussion.
- As you will see, the table includes obvious requirements that are supported by all three candidate PUID types; they are there for completeness
- Some of the requirements are indeed related to the metadata structure associated to the PUID that we will discuss in week 3
We look forward to receiving your comments on the subject.
To unsubscribe from the GLIS-PGRFA-L list, click the following link:
https://listserv.fao.org/cgi-bin/wa?SUBED1=GLIS-PGRFA-L&A=1