query-c440b163e647f8a8c181d9521bf6abde

rq turtle/ttl

Incorrect URI's to confirm that). That's the URI that third-party sites should use in their RDF to link here. Other way around holds too. For this item: rdf://www.wikidata.org/entity/Q42 (look in the s , not httphttp://www.wikidata.org/entity/Q42 has a concept URI as (Q42)Douglas Adams I was wondering what URI's are currently incorrect. Let's take Wikidata as an example. this conversationAfter RDF)http://data.bibliotheken.nl/doc/thes/p068744307.rdf (http://data.bibliotheken.nl/id/thes/p068744307 URI is (P1006)Nationale Thesaurus voor Auteursnamen ID The RDF)https://viaf.org/viaf/113230702/rdf.xml (http://viaf.org/viaf/179734837 URI is (P214)VIAF ID The (etc.) , it's consistently https. Why is this important? The URI is the way to connected different data sets. Inconsistencies will show up when doing federated queries. I already corrected a couple and these should be checked and maybe switched from https to http for the formatter URI: (P496)ORCID iD It's not always http, for example if you look at

Use at

PREFIX wdt: <http://www.wikidata.org/prop/direct/>
PREFIX wd: <http://www.wikidata.org/entity/>
SELECT ?property ?formatter WHERE {
  ?property wdt:P1921 ?formatter .
  FILTER REGEX(?formatter, "https") .
  # Add the properties here where the URI really starts with https 
  VALUES (?exceptprop) {
    (wd:P496) # ORCID is explicit https (
  }
  FILTER (?property!=?exceptprop) .
  } ORDER BY ?formatter
LIMIT 100

Query found at

graph TD classDef projected fill:lightgreen; classDef literal fill:orange; classDef iri fill:yellow; v4("?exceptprop") v1("?formatter"):::projected v2("?property"):::projected f0[["?property != ?exceptprop"]] f0 --> v2 f0 --> v4 f1[["regex(?formatter,'https')"]] f1 --> v1 v2 --"wdt:P1921"--> v1 bind2[/VALUES ?exceptprop/] bind2-->v4 bind20(["wd:P496"]) bind20 --> bind2