Integrate AF7 RDF

[no-reply]

Okay, I've done the leg work on this:

• AF-Crosswalks is fine
• Hydra Derivatives is fine
• Hybag is fine after some minor fixes that improve the gem either way
• Hydra Access Controls is decidedly NOT FINE

The problem is with the deprecation of #delegate and #delegate_to, which are littered throughout the access controls that ships with hydra-head 6.4.0. As near as I can tell, this is the only problem. I think it leaves us with an obvious next step: Fork hydra-head 6.4.0 and patch all the delegates.

This will leave us running our own hydra-head branch until we choose to upgrade. AF could be pinned back the gem as soon as our RDF code is in.

I'm out Wednesday the 5th. @terrellt, if you can fix hydra-head, that's great. If not, I'll get this done by the end of the week.

[no-reply]

Nevermind, this was easier than I thought:

This passes the hydra-access-controls tests, but there's some issue about tmp files that fails for hydra-core on v6.4.0: https://github.com/no-reply/hydra-head/tree/AF7-RDF

This uses the above, and our AF branch. It needs to be updated to use the latest Hybag as soon as that gem is released. It also fails a bunch of stuff and I can't look at it any more right now: https://github.com/OregonDigital/oregondigital/tree/feature/af7

[tpendragon]

Added a bunch of commits to the AF7 branch. In so doing I found two bugs - one with persisting to repositories (pull request is in for @no-reply's rdf fork and feature/af7 is locked to mine for now) and one with ActiveFedora::Rdf::Identifiable and custom Base URIs. There are notes in the commit - but for now, the tests pass! Huzzah.