@satra, are there any implications for using `prov:atLocation` instead of `prov:location`? 

The [prov-o example](https://dvcs.w3.org/hg/prov/raw-file/default/ontology/Overview.html#Location) notes that a `prov:Location` is a subclass of `Thing` and not a `prov:Entity`, so the only scenario I see so far where there would be an issue is if conversion utilities infer that if the value of `prov:location` is a IRI, then that IRI is a `prov:Location`...