@cpendery I'm going to grab this one and start updating the conflicts - then I'll get a review and hopefully we should be good to go to get this merged.

@cpendery I'm going to grab this one and start updating the conflicts - then I'll get a review and hopefully we should be good to go to get this merged.

Thank you!! This one does run into the same issue with Hex that Cocoapods supports both Swift and ObjectiveC, so I've just used Swift everywhere for the language. I'll update the purl-spec pr later today with some information on identifying source languages

@cpendery I'm going to grab this one and start updating the conflicts - then I'll get a review and hopefully we should be good to go to get this merged.

Thank you!! This one does run into the same issue with Hex that Cocoapods supports both Swift and ObjectiveC, so I've just used Swift everywhere for the language. I'll update the purl-spec pr later today with some information on identifying source languages

That's cool. If it looks like it's going to take a while to evolve the specification on your submission to them then I think we can find ways to keep the detail of what language is captured on our internal model. I'll ask @wagoodman if he has any preferences here.

Approving and merging this now with the caveat that there is some work to be done on the PURL side for language identification.