OpenAtlas

It is a good idea. I looked into it and I would appreciate, if we can go through it together.

Regarding the Question "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

":

As I understand, LOUD uses SKOS "broader" and "narrower" instead of P127:

Type: {
@id: "crm:E55_Type",
@context: {
part: {
@id: "skos:narrower",
@type: "@id",
@container: "@set" 
},
part_of: {
@id: "skos:broader",
@type: "@id",
@container: "@set" 
},
member_of: {
@id: "la:member_of",
@type: "@id",
@container: "@set" 
}
}
}

Would this solve the problem?

Regarding the question on the coordinates of a place I suggest we use the following approach from the example https://linked.art/model/place/#buildings-and-immovable-objects

{
@context: "https://linked.art/ns/v1/linked-art.json",
id: "https://thanados.net/entity/12344",
type: "PhysicalThing",
_label: "My House",
classified_as: [
{
id: "https://thanados.net/vocabulary/12345",
type: "Type",
_label: "Building" 
}
],
former_or_current_location: {
type: "Place",
_label: "Location of my House",
defined_by: "POLYGON((165.74 -33.55, -179.96 -33.55, -179.96 -47.8, 165.74 -47.8, 165.74 -33.55))" 
}
}

I oversaw, that former_or_current_location can also be an array/set. Thank you.

Thank you for implementing, it is already online on the development demo (https://demo-dev.openatlas.eu) and can be tested there, e.g. https://demo-dev.openatlas.eu/api/entity/20701?format=loud