Project

General

Profile

Question #1382

API: Other jsonld mappings beside linked-places

Added by Bernhard Koschicek 7 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
Low
Category:
API
Target version:
-
Start date:
2020-10-12
Estimated time:

Description

For a while now, I searched for a suitable mappings for our other main categories (actor, source, reference, event). Sure there are schemas and mappings for contemporary persons or events but nothing really historical. Also linked traced (https://github.com/LinkedPasts/linked-traces-format) will not be suitable for us.

OA-dev session: Even if we do new json formats for actors, source etc. we only apply them to the direct entity view or download from the UI. The communication with the frontend will still be with the linked places geojson format.

If you have any suggestions, please say so. Otherwise, we need to write our own mapping.


Related issues

Related to Feature #1386: API: Flask restful frameworkClosed2020-10-15Actions

History

#1

Updated by Bernhard Koschicek 7 months ago

  • Status changed from New to Acknowledged
  • Subject changed from Other jsonld mappings beside linked-places to API: Other jsonld mappings beside linked-places
#2

Updated by Alexander Watzinger 7 months ago

In the Meeting 2020-05-06 the prosopogrAPhI was suggested.

#3

Updated by Bernhard Koschicek 7 months ago

Yes you are right, didn't find it. We can try using it for Actors. Maybe we have to enrich it. I will do it this or next week.

#4

Updated by Bernhard Koschicek 7 months ago

#5

Updated by Bernhard Koschicek 7 months ago

  • Description updated (diff)
#6

Updated by Bernhard Koschicek 4 months ago

Alexander Watzinger wrote:

In the Meeting 2020-05-06 the prosopogrAPhI was suggested.

I looked into prosopogrAPhI but found it not really useful to us, since OA is not based on a factoid model. The information given is quite sparsely compared to what OA can and have to present to stay connected to other entities. I looked into https://apis.acdh.oeaw.ac.at/person/49290 and their model would be more suitable. But it is not JSON-LD compatible, since they have no context.

So right now, I see only Person from schema.org suitable for the task. But in reality, I think we need a real use case to develop our own json-ld format respectively adept the linked-places format.

And if other mappings are really wanted we need to make a workshop to develop these mappings with use cases and specialists.

tl;dr
I push back this issuse on my personal timeline, since right now, we don't have a real use case.

#7

Updated by Bernhard Koschicek about 2 months ago

  • Status changed from Acknowledged to Closed

We further use LP for our entity view. Nothing better was found or suggested. If there is a need for another format, a new ticket with a concrete example is needed.

#8

Updated by Bernhard Koschicek about 1 month ago

  • Target version deleted (API)

Also available in: Atom PDF