linkedpipes / visualizations

LinkedPipes Visualization offers vocabulary based Linked Data visualizations
https://visualization.linkedpipes.com
GNU General Public License v2.0
1 stars 0 forks source link

DCV: mixed label languages #27

Closed jakubklimek closed 8 years ago

jakubklimek commented 8 years ago

image

Those are labels from dereferencing. Maybe the issue is there?

Related to https://github.com/ldvm/LDVMi/issues/93?

jirihelmich commented 8 years ago

The visualizer goes through all the languages (currently cs, en, and no language). Firstly, it shifts the currently selected language to first position. Then it loops through the list of languages and tries to find any label in the given ordering of languages.

Are all the labels present in both en and cs?

jakubklimek commented 8 years ago

http://linked.opendata.cz/generated/resource/age/Y0 http://linked.opendata.cz/generated/resource/age/Y1T4

jirihelmich commented 8 years ago

Could you provide a source of the data? I tried yesterdays TTL and LOD.cz and it's not there.

jakubklimek commented 8 years ago

http://visualization.linkedpipes.com/example/datacube.ttl http://visualization.linkedpipes.com/example/dsd.ttl

jirihelmich commented 8 years ago
skos:prefLabel  "10-14 let"@cs ,
        "10-14 years"@en ,
        "10-14 years"@cs ;
jakubklimek commented 8 years ago

Ow... that is the temporary fix... ok, will clear that and try again

jirihelmich commented 8 years ago

There's a bug in extraction as well, but this won't make it better...

jakubklimek commented 8 years ago

OK, fixed the data (deleted the temporary fix), however, it is still happening.

Moreover, weird thing is happening when switching languages in menu: Czech: image English: image

Notice that only 0 and 25-29 changes, and it changes to skos:notation, not a label

jirihelmich commented 8 years ago

It's queried like this:


 SELECT DISTINCT ?l ?spl ?sn ?sna ?st
 WHERE {
     OPTIONAL { <$uri> rdfs:label ?l . }
     OPTIONAL { <$uri> skos:prefLabel ?spl . }
     OPTIONAL { <$uri> skos:notation ?sn . }
     OPTIONAL { <$uri> schema:name ?sna . }
     OPTIONAL { <$uri> schema:title ?st . }
 }

And labels are taken in this ordering: sn, l, spl, sna, st and then set to a map, so I think that the priority is actually reversed.

You can choose the expected priority, I will replace it.

jakubklimek commented 8 years ago

This does not make sense because it behaves differently for each concept, even though each of the age categories, for example, has both skos:prefLabel in Czech and English and skos:notation.

As to the priority, it should be ?spl, ?sna, ?l, ?sn, ?dct, ?st where ?dct is dcterms:title

jirihelmich commented 8 years ago

Extractor rewritten. It previously took just the first result from the result set, which was basically the randomization. Now it assembles the whole labels table and chooses the most suitable one.

jakubklimek commented 8 years ago

The priorities are not correct. For regions from ruian, ?sn is displayed instead of ?sna. image