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

Ldpath support #99

Merged
merged 1 commit into from Jul 18, 2013
Merged

Ldpath support #99

merged 1 commit into from Jul 18, 2013

Conversation

cbeer
Copy link
Contributor

@cbeer cbeer commented Jul 13, 2013

This first path at LDPath support allows you to POST an LDPath Program and have it evaluated against an object's graph.

Far from brilliant, but it works.


@Component
@Scope("prototype")
@Path("/{path: .*}/fcr:ldpath")
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'd like to name this something better.. fcr:transform, maybe.. and use ConNeg to figure out it should run the program. Any better ideas?

@cbeer
Copy link
Contributor Author

cbeer commented Jul 14, 2013

Ok. I think this is my first pass at how this feature could work. If we like the general idea, I'll clean it up and ship it.


final InputStream ldpathProgram = LDPathService.getLdpathProgram(session, program, object.getNode());

if (ldpathProgram == null) {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

We should probably have a different error for when the node requested was found, but the program wasn't. At the very least, a different exception

Transform a Node's property graph to some other format. Out of the box,
we have an LDPath implementation (and a JSON output that is solr
friendly) and SPARQL-Query
@cbeer cbeer merged commit 0ad4c4b into master Jul 18, 2013
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.

None yet

1 participant