Right, but there can be identical assertions made to the same place and I could trust both. If I'm at a location and attest to the veracity of a neighboring assertion are you saying that because they assertions are the same that two attestations (one for each assertion) should be signed.

Assertions can't be identical unless they are from the same key. Attestations can also be attested to. 🙃

Ok not identical but 2 entities can assert the same thing (Is there a spec for the actual assertion events?) What I'm trying to ask is if btc map and county gov say person x runs business as location y. I am there. I trust both entities. I click "verify" which would sign an assertion. Where would that attestation be linked to? Assertion a or b or both?

The spec is agnostic on the Assertion Event - it can literally be any other event of any kind. It's covered on the nostrhub link above. The Assertion Event, to be useful, should be domain specific and as detailed as necessary such that a valid/invalid assesment can be made via an Attestation. In your case directly above, you're not signing the assertion - that is the place event itself published by the merchant. You would either be attesting to it directly, or attesting to the other attestations as you trust them implicitly. Both are fine.

I feel like we are talking past each other. Are you saying that 2 entities cannot assert the same thing? Because that does not mirror reality. My understanding of the attestation spec above is that an attestation only can apply to 1 assertion, but if there are 2 assertions that are the same, how would that be handled, considering that a user attesting to the fact that the sky is blue isn't relevant whether God or the devil made that assertion.