-
Notifications
You must be signed in to change notification settings - Fork 314
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
SWRL variable IRIs violate URN spec #732
Comments
That string is used as a marker for variable IRIs - the SWRL classes use IRIs for variable identifiers, and so they're forced to have something to replace the "?" used, for example, in Manchester syntax. (Protege has no responsibility for that :-) ) The fact that it only has one colon is an error, one that most tools don't care about... |
ignazio1977
added a commit
that referenced
this issue
Jan 20, 2018
ignazio1977
added a commit
that referenced
this issue
Jan 20, 2018
ignazio1977
added a commit
that referenced
this issue
Jan 20, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OWL API produces SWRL variables with IRIs like
urn:swrl#foo
(at least it reads these into?foo
, maybe they're only created by Protégé?). But a URN should have two colons:Could they be changed to
urn:swrl:foo
orurn:swrl:var#foo
? We ran into one tool that complains abouturn:swrl#foo
.The text was updated successfully, but these errors were encountered: