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
Support the LDP API (and clean up our internals in the process) #496
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@@ -59,6 +60,7 @@ | |||
* | |||
* @author awoods | |||
*/ | |||
@Ignore |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update to Modeshape 4.0.0.Final
Added fixity properties to the fcr:fixity result page.
cbeer
force-pushed
the
ldp-resource
branch
2 times, most recently
from
October 6, 2014 05:05
ebe622c
to
1479026
Compare
Travis is failing because of a dependency on fcrepo-module-auth-rbacl, fixed in a pull request on that project. |
resource would conflict
…es in the response
… other preferences
…tion Also, when exposing a description, include a Link to the binary.
…against. - On create, any triples included should be appended to the document - On update, the provided triples should be diff'ed against the default serialization When PUT'ing to an endpoint, it is important to include the original serialization, or fcrepo4 can assume the request removes those triples.
Previously, JAX-RS endpoints were responsible for logging out as appropriate.
Previously, we inserted exception information into a RDF model for future (possible) use, and relied on the client to check it. Instead, we should handle this exceptional case using exceptions, which may be aggregated by some consumers (e.g. JcrPropertyStatementListener) into a single exception.
… a MalformedRdfException
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fedora 4 should be LDP compliant. To become compliant (and keep things reasonable), we need to clean up our HTTP API internals for consistency and clarity.
https://www.pivotaltracker.com/story/show/79973150
https://www.pivotaltracker.com/story/show/79703120
https://www.pivotaltracker.com/story/show/59232134
https://www.pivotaltracker.com/story/show/76048574
https://www.pivotaltracker.com/story/show/60441592
https://www.pivotaltracker.com/story/show/71751536
https://www.pivotaltracker.com/story/show/70600504
https://www.pivotaltracker.com/story/show/78034072
https://www.pivotaltracker.com/story/show/61391216