While identificationVerificationStatus isn't subject to one of the ~100 high-priority tests at this point, we're hoping to use it let data providers have input in to our, as aggregators, interpretation of the taxonomy they provide. I think this is an interesting test case of how communication can happen through the data shared and is a good warm-up to the coming of annotations for everything.
Of course, it needs a controlled vocab. @tucotuco pointed me to this one:
http://hiscom.github.io/hispid/vocabulary/identification_verification_status.xml
@pzermoglio and I have looked at the contents of this field in GBIF, iDigBio et al and the data is thin and mostly not in any kind of vocabulary. I think any proposed standardization would not be at odds with existing data and our use of new terms in our workflows and providers providing data with new terms won't break any existing things. In that way I think it's actually much easier than continent or basisOfRecord etc.
While identificationVerificationStatus isn't subject to one of the ~100 high-priority tests at this point, we're hoping to use it let data providers have input in to our, as aggregators, interpretation of the taxonomy they provide. I think this is an interesting test case of how communication can happen through the data shared and is a good warm-up to the coming of annotations for everything.
Of course, it needs a controlled vocab. @tucotuco pointed me to this one:
http://hiscom.github.io/hispid/vocabulary/identification_verification_status.xml
@pzermoglio and I have looked at the contents of this field in GBIF, iDigBio et al and the data is thin and mostly not in any kind of vocabulary. I think any proposed standardization would not be at odds with existing data and our use of new terms in our workflows and providers providing data with new terms won't break any existing things. In that way I think it's actually much easier than continent or basisOfRecord etc.