I imported the core vocabularies through evoc before creating a SV view. But when I created my view, my SPARQL endpoint seems to use this vocabulary for Dublin Core: http://purl.org/dc/elements/1.1/ while evoc imports this one: http://purl.org/dc/terms/. *

So I tried something rather straightforward: import the one I need through the import form using the 'dc' as my prefix. This results into two entries with the same 'dc' prefix. See included screenshot.

(*) On an unrelated note: I have to use http://purl.org/dc/elements/1.1/ as PREFIX in SNORQL instead of the namespace imported through evoc.

CommentFileSizeAuthor
Screen shot 2011-05-26 at 16.25.33.png50.58 KBnetsensei

Comments

netsensei’s picture

netsensei commented

Okay, I figured out the sidenote: has to do with the fact that the endpoint I'm querying, is still using the legacy DCMES instead of the actual terms namespace.

scor’s picture

scor commented
Title: Conflicting namespace prefixes when importing a vocabulary » Evoc and RDF namespace form should not allow conflicting namespaces for the same prefix
Version: 7.x-2.0-alpha1 » 7.x-2.x-dev

yes, you cannot have two different namespaces with the same prefix, that's an issue that #766872: Check for conflicting namespaces should help with. The only work around would be import the second dc namespace (http://purl.org/dc/elements/1.1/) with a different prefix (dce or dcelements)... this namespace is older and phasing out, but a lot of older systems are using it still. Changing issue title to reflect the bug at hand here.