Feature #1770

Updated by Bernhard Koschiček-Krombholz over 1 year ago

We could use 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. 

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

 * -Is the Content of E33 linked with P190? ( 
 * -Are all descriptions P190 linked to E33? ( 
 ** just use content: "" for description 
 * How do we define time in which case? P4, P82, P173, P191 or something else? ( 
 * 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? 

 * Link physical objects and actors with dates (mapping with event with E63/E64 and P92/93) 
 * Description is just "content": "TEXT" 
 * For types with external reference systems, just add a field with external reference