![]() I really struggle when I see the examples and the discussion above. My question is: why do we have typeStatus in the HISPID name space that can either be only the status as per the vocabulary or include the typified name, when we could use the DWC namespace/concept for the latter? or is that too simplistic. Having typeStatus in the HISPID namespace allows us to transfer the type status including or excluding the typified name depending on what circumstances require. In contrast to Darwin Core, in HISPID typeStatus and typifiedName have been separated. TypeStatus has been placed in the HISPID namespace, even though it is available in Darwin Core, because our use is different. ISOTYPE of Babingtonia bidwillii A.R.Bean, fid. There is no way to indicate in the DwC Identification History extension to indicate which identification is the current one and which one is the correct type designation. ![]() Even with the type designations in the Identification History extension you still need the current typeStatus in the Occurrence core, just like the current Identification, because, if type designations are identifications, they can be wrong as well, just like other determinations. While in theory you can provide the type designation information in the Identification History extension, you cannot do that for data delivery to AVH (well, you could provide it that way, but it won't end up where you want it to). The HISPID term was added because other people wanted something different. I am perfectly happy with just the Darwin Core term. Typestate reflects how the legal operations on imperative objects can change at runtime as their internal statechanges. If you want to split it up in type of type ('Holotype') and typified name ('Dicranum robustum Hook.f. From settings you can configure how the tweak works that includes selecting a custom overlay display duration, choosing between fade and slide overlay animations, hiding text after delay and disabling TypeStatus when Messages app is open. Darwin Core usage, in the Occurrence core at least, is 'Holotype of Dicranum robustum Hook.f. TypeStatus 2 works on all screens that show the status bar, including the lockscreen. ![]() What we need to agree on here is whether the Darwin Core usage of the term works for us or not. It is the approach we have taken for every term. So do I, but it it is a motherhood statement that has nothing in it to disagree with and has no bearing on the question at hand. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |