search

chin-rcip / collections-model

Linked Open Data Development at the Canadian Heritage Information Network - Développement en données ouvertes et liées au Réseau canadien d'information sur le patrimoine
Creative Commons Zero v1.0 Universal
12 stars 1 forks source link

Issue #4 - Paper Files Location & AiC #4

Closed chin-rcip closed 4 years ago

chin-rcip commented 4 years ago

Philippe Michon Jun 21st at 8:38 AM

  1. For AiC, we need to manage paper files location. We could manage it with a complete CIDOC CRM path something like: "We have some documents about this person and they are located there". It's quite a lot more nodes for not that much semantic. So we seem to prefer a simpler approach like: e21->p1->e33->p2->e55 (Location of the paper files). I know that Stephen modeled the complex path so we could vet with the team what they prefer.

Stephen Hart 2 months ago I've modeled it in the pur CIDOC cru, with the path: E39Actor->P70iisDocumentedBy->E31Document->E22Man-madeObject->P54hasCurrentPermanentLocation->E53Place But I'm not convinced by the P1 is identified by, as the files concerning the actor is not an identifier. The property P62 Depicts has domain E24 Physical man-made thing and range E1 Entity, but it is only for images, not texts.

Stephen Hart 2 months ago Therefore I am not sure what's the easiest solution. A simple P3 has note can not be tagged with an E55 Type to identify it as the file location, so it's not a good solution either

Philippe Michon 2 months ago I made a mistake in my first reply I meant e21->p67i->e33->p2->e55 (file location). But I think Stephen's proposal is not so complicated and valid :slightly_smiling_face:

chin-rcip commented 4 years ago

This have been implemented in the v1.5 of the TM