Maybe squash the clean up commit? I know that would make @awoods happy.

Whoa! Hang on! Why is this test showing up in the core codebase and not in the indexer codebase?

I put it in FedoraResourceImplIT as what it's really testing is the code in NodeRDFContext creating RDF for a fedora resource - specificly that adding a mixin (with a supertype) to an object will show that supertype as one of its own rdf:types. It just happens to be using indexing:indexable as that supertype.

Okay, but then, just to be clear, how about changing the types involved to something not obviously related to indexing, like "dummytype" and "dummysupertype" or the like? Reusing the indexing vocabulary is liable to confuse people-- it confused me.

sure, would a comment to the effect of "confirming the types of a supertype are inherited, using the real use case of indexing:indexable" suffice?

I would really prefer to use an independent nomenclature. I know it's a bit of work, and if you're caught up with other things, I can send a PR for this PR to do it. I really want to keep indexing's nose out of the core codebase.

ok

Resolved with: 14eb8b3

Addresses: https://www.pivotaltracker.com/story/show/65151184