em: vs. commenting out attributes

[alexduryee]

Should commented-out values/attributes (e.g. some transliterations, lastDateTimeVerified) get the "em:" treatment?

[fordmadox]

I went back and forth on those options.

For @transliteration, the new way to manage those in EAC 2 is to link them to a convention declaration. That way, a user can say a bit more about the transliteration, if needed, and the transliteration scheme is only listed once. For @lastDateTimeVerified, on the elements that it no longer is allowed, I can promote those to an attribute in the migration namespace (changing the default prefix value from em to eac1, as discussed). Not sure why I settled on comment in the first place, but I think it was because I was trying to use the "any attribute in any namespace" option sparingly. That said, I think this one makes sense to keep as an attribute that can be accessed more easily than a comment.