GeographicOrigin - rename class and properties

[essvee]

See meeting notes: 9th March 23 Original defs: https://github.com/tdwg/cd/issues?q=is%3Aissue+is%3Aopen+Geography+label%3AClass%3AGeographicOrigin Current master defs: https://github.com/tdwg/cd/blob/review/standard/terms/ltc_standard_terms_draft.csv#L58 SKOS mappings: https://github.com/tdwg/cd/blob/review/standard/terms/ltc_skos_mapping.csv#L120

We want to make 'GeographicOrigin' more generic (aka rename it 'Location', so we can use it to denote where other things happened, this change was advised after reviewing the ltc:Event class.

Question:

• I hate to be that guy, but does this make ltc:StorageLocation a bit confusing, given that they'll have similar names but totally different purposes/compositions? What about renaming it to GeographicContext instead, so it lines up with GeologicalContext?

• [ ] ~Rename the class and properties and update the definition so it's more obvious that this class can be used to denote the location of activities/events other than 'this thing was collected here', e.g., 'this event occurred here'~

• [ ] ~Add a has... field to ltc:Event~

• [ ] ~Leave ObjectGroup.hasGeographicOrigin as-is, but update the definition to say it contains one or more instances of ltc:Location, not ltc:GeographicOrigin... ~

[essvee]

Updated: see notes from March 31st

tl;dr rename to 'GeographicContext' - less confusing, echoes GeologicalContext nicely

• [x] Rename the class and properties and update the definition so it's more obvious that this class can be used to denote the location of activities/events other than 'this thing was collected here', e.g., 'this event occurred here'~
• [x] Add a hasGeographicContext field to ltc:Event~
• [x] Change ObjectGroup.hasGeographicOrigin to ObjectGroup.hashasGeographicContext and update the definition accordingly

[mswoodburn]

Updated in local branch