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

Fixity uris #202

Merged
merged 2 commits into from Dec 11, 2013
Merged

Fixity uris #202

merged 2 commits into from Dec 11, 2013

Conversation

cbeer
Copy link
Contributor

@cbeer cbeer commented Dec 10, 2013

Update the fixity RDF response to use a PREMIS vocabulary, and use a hash-uri as the subject so it is "resolvable".

Also, switch back to using the "info:fedora/" namespace for the DefaultGraphSubjects (part of this PR because without it the fixity URIs generated using the DefaultGraphSubjects were invalid).

@cbeer
Copy link
Contributor Author

cbeer commented Dec 10, 2013

"info:fedora2" + expected + "/bad");
actual = testObj.getPathFromGraphSubject(mockSubject);
assertNull(actual);
// test a non-existent path
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there any reason to remove this test? Is there any expected difference between a bad path with a bogus namespace and one with a good namespace?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The diff is a little confusing. The check that was removed was "test a non-existent path", which isn't actually logic we have in any of the GraphSubject impls, and was only passing because it was also a "bad subject" like the above.

@escowles escowles merged commit 10a89f2 into master Dec 11, 2013
@escowles escowles deleted the fixity-uris branch December 11, 2013 21:15
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

2 participants