Thanks Eric. I'm working right now to finish up the PR so we can have a group discussion/review. I demoed geo_concerns to Trey and Esme, and got some positive feedback. They both agreed that using FileSet as is instead of subclassing into different FileSet types was the way to go if there wasn't a really good reason to do it. FileSet is hard-coded into curation_concerns and hydra-works in many places. If there were good use cases for abstracting it out, that could happen, but it would be a pretty hefty undertaking.
As for ordered_members, I think you are correct. I can't think of a reason, at this point, why geo_works need to be in a particular order. As you probably know, behavior around ordered and unordered members is under active discussion.
- Eliot