Feature #1770
Updated by Bernhard Koschiček-Krombholz almost 2 years ago
We could use https://linked.art/ as a format for further API developments, as it offers a JSON-LD format for the CIDOC CRM that is very easy to understand, very comprehensible and would in a very simple way allow representing each node as a JSON-LD. Especially for non place entities, this would allow for a much better machine-readable representation.
h2. Q&A
Q: How do we define time in which case? P4, P82, P173, P191 or something else? (https://linked.art/model/base/#time-span-details)
A: Link physical objects and actors with dates (mapping with event with E63/E64 and P92/93) -> *For simplicity, currently implemented with "P4 has time-span":https://cidoc-crm.org/Property/p4-has-time-span/version-7.1.1*
Q: What to do with additional information? Should we keep strictly to LOUD model or add additional fields?
A: For types with external reference systems, just add a field with external reference
Q: *P127 has broader term* doesn't exist in LOUD. So we have problems to display Types as single entity, e.g. /api/cidoc_class/E55
A: Use skos:broader
Q: Place coordinates also need a link property. When to use "P189 approximates":https://cidoc-crm.org/Property/p189-approximates/version-7.1.1 and "P168 place is defined by":https://cidoc-crm.org/Property/p168-place-is-defined-by/version-7.1.1. P168 only takes one geometry, P189 can have an array. For example implementations, see "Place at linked.art":https://linked.art/model/place/
A:
Q: Which property have the comments of the timespans? My guess is "P3 has note":https://cidoc-crm.org/Property/p3-has-note/version-7.1.1
A: