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

matching literal pattern when no lang or datatype #4

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dougli1sqrd
Copy link
Collaborator

No description provided.

@dougli1sqrd dougli1sqrd requested a review from balhoff August 23, 2017 20:51
Copy link

@cmungall cmungall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does arachne ever reason with datatypes?

Not really sure of the consequences of changing the defaults here

@@ -43,13 +43,14 @@ object ArachneBridge {
case BlankNode(id) => factory.createBNode(id)
case org.geneontology.rules.engine.Literal(value, _, Some(lang)) => factory.createLiteral(value, lang)
case org.geneontology.rules.engine.Literal(value, uri @ org.geneontology.rules.engine.URI(_), _) => factory.createLiteral(value, uriFromArachne(factory, uri))
case org.geneontology.rules.engine.Literal(value, _, _) => factory.createLiteral(value)
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it's possible to reach this pattern.

@balhoff
Copy link
Owner

balhoff commented Aug 24, 2017

No, Arachne doesn't do any reasoning with datatypes yet. Basically we just want to try to avoid accidentally creating duplicate triples when translating back and forth from sesame. I think we need to make the datatype URI optional in Arachne.

@dougli1sqrd I think we should probably just fix that in Arachne.

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

Successfully merging this pull request may close these issues.

3 participants