Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Already prefixed URIs are enclosed in <> #67

Open
KonradHoeffner opened this issue Jan 24, 2017 · 1 comment
Open

Already prefixed URIs are enclosed in <> #67

KonradHoeffner opened this issue Jan 24, 2017 · 1 comment
Labels

Comments

@KonradHoeffner
Copy link
Contributor

KonradHoeffner commented Jan 24, 2017

I have a column that contains URIs that are already prefixed, such as owl:Class or foaf:Person. Using uri(?column), I then get <owl:Class> instead of just owl:Class.

@Aklakan
Copy link
Member

Aklakan commented Jan 19, 2021

Hm, this is not really a bug but rather a new type of term contruction: a function that for a given input IRI and a prefix mapping returns a set of candidate lookups.

E.g
The expression

FILTER(?s = <http://example.org/foo>)
WITH ?s = NSIRI(?someColumn)

w.r.t. the prefix mapping

eg: <http://example.org>
ex: <http://example.org>

would translate / expand to the SQL condition
"someColumn" IN ('eg:foo/', 'ex:foo/')

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants