These two are a bit too similar/hard to distinguish and that is 🙅♀️🙅♀️🙅♀️. We want to keep contactDetailCategory and widen it a bit to incorporate some of the functionality from contactDetailType. The resulting property will be primarily used to state the mechanism of contact, rather than the purpose of the communiqué, although it does have a little wiggle room to distinguish between different types of the same communication medium, e.g., mobile phone vs. home phone.
[x] Update contactDetailCategory's examples to include some of the work phone/home phone/mobile phone type scenarios
[x] Remove contactDetailType from termlist/skos mapping docs/wherever else it may appear
essvee
commented
1 year ago
See meeting notes: 2nd March 23 Original defs: https://github.com/tdwg/cd/issues/331, https://github.com/tdwg/cd/issues/330 Current master defs: https://github.com/tdwg/cd/blob/review/standard/terms/ltc_standard_terms_draft.csv#L43
These two are a bit too similar/hard to distinguish and that is 🙅♀️🙅♀️🙅♀️. We want to keep contactDetailCategory and widen it a bit to incorporate some of the functionality from contactDetailType. The resulting property will be primarily used to state the mechanism of contact, rather than the purpose of the communiqué, although it does have a little wiggle room to distinguish between different types of the same communication medium, e.g., mobile phone vs. home phone.