Scenario 1 (continued)
- That EAD CLD might be
- rendered in multiple formats (HTML, PDF….)
- used in local resource discovery service by repository
- submitted to domain service e.g. Archives Hub
- mapped/transformed to simple, high-level CLD which might be used in cross-domain service
- Challenge of semantic interoperability
- mapping properties
- some loss of specificity but possible?
- mapping “value space”: name rules, thesauri etc
- “granularity” issues - comparing like with like?