Project

General

Profile

Feature #1770

Updated by Bernhard Koschiček-Krombholz over 1 year 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 to represent each node as a JSON-LD. Especially for non place entities, entities this would allow for a much better machine-readable machine readable representation. 

 Before implementing LOUD as a format, some topics needs to be discussed. 

 *Discussion:* 
 * Is the Content of E33 linked with P190? (https://linked.art/model/base/#names-and-identifiers-for-a-resource) 
 * Are all descriptions P190 linked to E33? (https://linked.art/model/object/aboutness/#description) 
 * How do Maybe we define time discuss this in which case? P4, P82, P173, P191 or something else? (https://linked.art/model/base/#time-span-details) 
 * How to handle multiple external reference systems of a type? (make multiple entries for same type with different link?)   
 * What to do with additional information? Should we keep strictly to LOUD model or add additional fields?  
 * Should we add links to the other mentioned resources? 
 next developer meeting?

Back