Hi Anne-Marie,

@authfilenumber does seem to be the appropriate place to insert a URI for a controlled access term. I have recently adopted this approach for our finding aids that link to our authority URIs (described in EAC-CPF). See http://numismatics.org/archives/ark:/53695/nnan0028 / http://numismatics.org/archives/ark:/53695/nnan0028.xml for example. The @source attribute requires a NMTOKEN, but the list isn't restricted in the schema. It could be anything, really, that conforms to that datatype (see http://www.liquid-technologies.com/DTD/Datatypes/NMTOKENS.aspx for a definition). We're using viaf, pleiades, geonames, aat, lcsh, etc.

In EAD 3, the @vocabularysource attribute is explicitly designated for capturing URIs that define controlled access terms.


On Tue, Jun 24, 2014 at 4:26 PM, Anne-Marie Viola <[log in to unmask]> wrote:
Here at the Image Collections and Fieldwork Archives (ICFA) at Dumbarton Oaks (http://www.doaks.org/library-archives/icfa) we are using the ICA-AtoM CMS (https://www.ica-atom.org) to produce EAD XML finding aids, which we plan to share with Harvard's union catalog for finding aids. 

In reviewing these export files, I just noted that our exports include the source note for each subject term in the @source attribute; our source notes are typically links (developed on the principles of linked, open data). It appears that this is problematic as the files aren't validating with HTML in that attribute. Would @authfilenumber be a better choice for these URL's, as it looks like they can accept CDATA? Does anyone know what the NMTOKEN values are for @source?

Thank you,
Anne-Marie H. Viola
Metadata & Cataloguing Specialist,
Image Collections and Fieldwork Archives (ICFA)
Dumbarton Oaks Research Library and Collection
1703 32nd Street, NW Washington, DC 20007