digitalcourage.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Diese Instanz wird betrieben von Digitalcourage e.V. für die Allgemeinheit. Damit wir das nachhaltig tun können, erheben wir einen jährlichen Vorausbeitrag von 1€/Monat per SEPA-Lastschrifteinzug.

Server stats:

856
active users

Sebastian Lasse

Hey @edsu
just read, watched & enjoyed inkdroid.org/2015/05/20/skos-a
Personally I am also using cause of the skohub.io approach @acka47

What I wonder about:
Can't we say in SKOS:
- This wikidata property wd:P… is the same than this skos:Concept
or
- This skos:Concept is described by wikidata entity wd:Q…

Basically my software maps Linked Data and other SKOS in this way but how about wikidata or even non-LD-APIs ?
Does anybody know, what is the best way to describe such ?

inkdroid.orgSKOS and Wikidata

@sl007 @acka47 I'm not sure I understand the question. It might help to see some examples.

@edsu @acka47

The concrete example is that we have published the first part of the Vocabulary at the page redaktor.github.io/vocab/
following the skohub.io approach.

What I would now like to express in the turtle files in huge github.com/redaktor/vocab/blob is e.g.
for a movie Director:

concept 012011
can appear as wikidata property
P57

or

concept 012011
is described by wikidata entity
Q3455803

@sl007 @acka47 ok, I understand now, and I don't know the answer. I think in semweb land that pushes into reification, which was never something I really understood very well.

Is there a reason why you wouldn't want to use one of the skos:mappingRelation to link to wikidata.org/wiki/Q3455803 instead?

www.wikidata.orgdirectordirector of a creative work

@edsu @acka47

Because the SKOS spcs. said “By convention, the SKOS mapping properties are only used to link concepts in different concept schemes.”
but I would like to link SKOS with a Link and not a "different concept scheme".
Maybe got something wrong.

@sl007 @acka47 would it be bad to infer that Wikidata is a concept scheme? It looks like the Library of Congress doesn't think so, e.g.

id.loc.gov/authorities/subject

I haven't kept track of how other people are linking to Wikidata from SKOS. It seems like if you did you'd want to link to something that's a resource and not a property?

@edsu @acka47

So. This is interesting.
Well, of course I had looked in LOC :)
But I expected it to be directly in the SKOS concepts like in our example
id.loc.gov/vocabulary/relators is this id.loc.gov/vocabulary/relators

@edsu @acka47

It seems like if you did you'd want to link to something that's a resource and not a property?

Well, both.
Linking resources for public, but also telling my ActivityPub software internally which wd property maps to e.g. which LOC relator.

@sl007 @edsu For linking skos:Concepts to things, there is foaf:focus. We use it for example in nwbib.de/spatial

@edsu @sl007 Yes, linking SKOS concepts to properties seems incorrect but I understand why Sebastian would like to add a link to the property. I don't know of a property made for this. Of course you can always add it to the skos:definition for humans to see the relation. Or you create your own property to state this relation...