search

cwrc / HuViz

LOD visualization tool for humanities datasets
8 stars 1 forks source link

propose recogito folksonomic tag export via JSON-LD #344

Open smurp opened 5 years ago

smurp commented 5 years ago

Currently the JSON-LD export from Recogito does not contain any of the folksonomic linking tags. Since these are very interesting to users and further these will be very appealing as links in HuViz a proposal for how these might be conveyed in the JSON-LD export would be of benefit.

We will use the following example for reference:

and the jsonld export for it...

smurp commented 5 years ago

First challenge: link URL

What URL should be used to represent the folksonomic relation?

Options

Use the URL of the Recogito document itself as the basis of the folksonomic URL.

For existing linking tags such as spokeTo a path for predicates could be constructed such as: https://recogito.pelagios.org/document/hxwv6a6awnflgj/predicate/ then the linking tag could be appended, resulting in: https://recogito.pelagios.org/document/hxwv6a6awnflgj/predicate/spokeTo

In the event that the tag contains characters which require escaping then such escaping must become part of the predicate URL, eg: the tag contain a space would become: https://recogito.pelagios.org/document/hxwv6a6awnflgj/predicate/contains%20a%20space

There is the hazard that such escaping may make unfortunate predicate URLs which actually offend some RDF standard relating to predicates. @smurp will investigate.

Use the tag itself if it is an URL (going forward these are great)

Ideally Recogito will provide support (encouragement and/or requirement) for the specification of predicate URLs as the values of such tags. In that case then such predicate URLs would become available in the semantic exports from Recogito – as JSON-LD or TTL.

Second challenge: structure of annotation in export

How should Recogito use Open Annotation to format the folksonomic links being exported?

Options

coming soon

SusanBrown commented 5 years ago

This sounds like a good way to handle it, to me.

On Oct 8, 2019, at 8:12 AM, Shawn Murphy notifications@github.com<mailto:notifications@github.com> wrote:

First challenge: link URL

What URL should be used to represent the folksonomic relation?

Options Use the URL of the Recogito document itself as the basis of the folksonomic URL.

For existing linking tags such as spokeTo a path for predicates could be constructed such as: https://recogito.pelagios.org/document/hxwv6a6awnflgj/predicate/ then the linking tag could be appended, resulting in: https://recogito.pelagios.org/document/hxwv6a6awnflgj/predicate/spokeTo

Use the tag itself if it is an URL (going forward these are great)

TO BE CONTINUED...

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/cwrc/HuViz/issues/344?email_source=notifications&email_token=AAEFJICLDWI5LPVV3OO4PITQNSPMDA5CNFSM4I6DECTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAUQWIY#issuecomment-539560739, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAEFJIEZVLZV4YKPTHH3BMLQNSPMDANCNFSM4I6DECTA.

smurp commented 4 years ago

The latest recommendation of JSON-LD provides some guidance on this issue https://www.w3.org/TR/json-ld11/#relationship-to-rdf

I need to digest this more, but the first point is that blank nodes as predicates are obsoleted (already illegal in RDF if I recall correctly).

The recommendation now encourages mechanisms such as:

I suspect that we don't want to go to the trouble (in the case of recogito) of using the ./well-known/ Skolemization approach, since by being referencable at the /.well-known/ path it seems needy of storage and management external to the document and consequently is lumbering (as opposed to agile) and pointless.

So we're still left with one of: