1. It is not clear what "shares the same URI / IRI conventions" means. This is the only place in the ActivityPub spec where a connection to IRIs is made, and all other statements refer to URIs. The section 3.1. (Object identifiers) says that identifiers must be URIs.
2. Section 2.2 (IRIs and URLs) of ActivityStreams says "This specification uses IRIs", but it doesn't say how it uses them. That statement may refer to names of properties and types, for example, which can be IRIs. What follows after that is just nonsense: "URI may be used wherever an IRI is named". ActivityPub's "shares same conventions" might mean that relative URIs are not allowed, but that's anybody's guess.
4. The vast majority of implementations use URIs for IDs and encode non-ASCII characters.
cc @reiver