Update Structure Document

[edwbaker]

Following discussion in latest MG meeting:

Structure document needs updating:

• Reflect the fact that service access points and regions of interest result in a schema that is not flat.
• Application Profile (sounds and ROIs - @edwbaker and @danstowell to work on)
• Application Profile (CameraTrap DP)
• Include JSON-LD examples

[baskaufs]

I want to put a reference here to another interesting discussion that's been going on for a while that is related to the grouping of related images in a IIIF manifest. I'm not entirely sure how it fits in, but one of the aspects of structuring image data is how we indicate that multiple images are grouped in some way. For example, designating sequences if images is important in Camtrap DP. This issue is related to how metadata for multiple related images would be represented in a GBIF record if there were a IIIF manifest that described the images.

[baskaufs]

See also #200

[baskaufs]

For reference, the final CTAF guidelines for linking DwC records to IIIF manifests using the AC multimedia extension are out. We should take a careful look at it as we consider the role that IIIF can play within AC. In particular, how can IIIF Annotations be used to associate a particular region of interest with occurrence or other records?