I need to allocate external references as requirements (these happen to be selected Bluetooth Profiles and Services, as listed on https://www.bluetooth.org/Technical/Specifications/adopted.htm). What’s the recommended mechanism for best interaction of those kind of references with eaDocX?

What I’d like to do is have an Element in the model which summarizes each BT profile/service spec, and has at least a “trace” relationship to the various components (or a “realize”), and have those elements gathered up in one package from which eaDocX produces a table listing spec names, versions, summary sentences, and clickable links to the actual downloadable specs

I’ve done some poking around; nothing seems right (my best so far is a Class stereotyped as a “web page” and I store the URL in the Files proprty, but I can’t get that eaDocX’ed into a hyperlink in the final doc) so I’m wondering if there’s already a “best practice” for external specification handling eaDocX?