Handle missing schema classes
Happens when: client gets an item from the Pod, either directly or as edge of other item
Current behaviour: If schema is defined locally (central schema or registered in PodClient), everything works If schema cannot be found, PodClient throws an error.
Desired behaviour: Needs some discussion Current behaviour is often issue when an item has an edge to another item with an unknown schema. Possible approach: have a flag in pod to ignore, throw warning, or error when encountering unknown Schema.