Is PersonalIdentificationDocument in Name logical?

This came up in the Generate mapping project.

It is odd that Ed-Fi places a PersonalIdentificationDocument in Name. That implies that “name” is a identifying property, and it is not.

Further, the definition of PersonalIdentificationDocument on Name is "The documents presented as evident to verify one's personal identity; for example: drivers license, passport, birth certificate, etc." - this definition is not specific to name verification, but could be used for other data verification.

By this same logic, PersonalIdentificationDocument might also be placed under Address or BirthData, and in so doing you can see the model starts to get over-complicated fast. You could link such an collection in lots of places.

I don't think that's what the field needs. It seems better to attach such files to a "person" entity, with the implied meaning that this document(s) was (were) used to validate attributes on this person.